diff --git a/scripts/build_keyword_index.py b/scripts/build_keyword_index.py index 0d0497d..137e098 100644 --- a/scripts/build_keyword_index.py +++ b/scripts/build_keyword_index.py @@ -50,7 +50,34 @@ # the deck appends a tracer/phase suffix to form the actual keyword name. # TVDP is documented as such: real decks write e.g. TVDPFSEA (free tracer # SEA), TVDPSIGS (solution tracer IGS), TVDPFWT1 (free tracer WT1). -TEMPLATE_KEYWORD_NAMES = frozenset({"TVDP"}) +# FIP is similar: the manual states "FIP as the first three characters +# followed by up to a five letter character string", producing deck tokens +# like FIPZON, FIPGL, FIPNL, FIPUNIT, FIPHC, …. +TEMPLATE_KEYWORD_NAMES = frozenset({"TVDP", "FIP"}) + +# Keywords whose record body is conventionally spread across multiple +# lines, with only the line carrying '/' completing the record. opm-common's +# size_type rarely flags these (the items aren't ``size_type: "ALL"``), but +# real decks routinely split them — MESSAGES is the canonical fixed-record +# case (12-13 INT values across two lines), and VFPPROD/VFPINJ's axis and +# BHP-table records each span many lines: +# +# VFPPROD +# 1 1535 LIQ WCT GOR THP PUMP METRIC BHP / +# 100.0 123.0 ... 228.0 +# 280.0 ... 5000.0 / +# ... +# +# Tag these explicitly so per-line missing-'/' diagnostics are suppressed. +VARIADIC_RECORD_KEYWORDS = frozenset({"MESSAGES", "VFPPROD", "VFPINJ"}) + +# Multi-record keywords whose block ends with the trailing record's '/' +# rather than a separate standalone '/'. opm-common classifies them as +# 'list' (size = None/string sentinel) but real decks never close them +# with a standalone '/' — the next keyword is what ends the block. +# Reclassified to 'fixed' (size_count = records_meta.length) so the +# diagnostics engine doesn't demand a closing terminator. +NO_LIST_TERMINATOR_KEYWORDS = frozenset({"VFPPROD", "VFPINJ"}) def _has_variable_arity_item(opm_items: list[dict]) -> bool: @@ -1041,15 +1068,30 @@ def _summary_size_shape(mnemonic: str) -> tuple[str, Optional[int]]: Field-scope mnemonics (F-prefix: FOPR, FWPR, …) are written bare with no terminating '/' — ``size_kind: 'none'``. - Every other scope (G/W/C/L/R/B/A/N/S…) takes a *single* record that - is either a list of names (``WOPR \\n 'W1' 'W2' /``) or just a bare - '/' meaning "all" (``WOPR \\n /``). That's ``size_kind: 'fixed'`` - with ``size_count: 1`` — modelling it as 'list' wrongly demands a - second standalone '/' to close the block. + Every other scope (G/W/C/L/R/B/A/N/S…) takes an optional block whose + payload is a list of names — well, group, region, completion, … + — spread freely across one or more lines and closed by a single '/': + + WOPR + 'PROD1' + 'PROD2' + / + + The body is OPTIONAL: ``WOPR \\n GMWIN \\n /`` (two bare mnemonics + stacked, single closing '/') is a real and widespread pattern in OPM + decks. Callers pair ``size_kind: 'array'`` with ``optional_body = + True`` for these entries so the diagnostics engine skips the + close-block terminator check when no values were given but still + flags a forgotten '/' once names are listed. """ if mnemonic.startswith("F"): return "none", None - return "fixed", 1 + return "array", None + + +def _summary_optional_body(mnemonic: str) -> bool: + """Whether the SUMMARY mnemonic's record body may be omitted entirely.""" + return not mnemonic.startswith("F") def _parse_performance_table(rows, section_fodt: Path) -> dict: @@ -1161,6 +1203,8 @@ def _row_starting_with(label: str): } if size_count is not None: entry["size_count"] = size_count + if _summary_optional_body(mnemonic): + entry["optional_body"] = True out[mnemonic] = entry return out @@ -1264,6 +1308,8 @@ def _cell(i): } if size_count is not None: entry["size_count"] = size_count + if _summary_optional_body(mnemonic): + entry["optional_body"] = True if is_templated: entry["templated"] = True out[mnemonic] = entry @@ -1342,6 +1388,65 @@ def build_index(manual_dir: Path) -> dict: for e in targets: e["templated"] = True + # Mark keywords whose single record canonically spans multiple lines + # so per-line missing-'/' diagnostics are suppressed (MESSAGES, …). + for name in VARIADIC_RECORD_KEYWORDS: + entry = index.get(name) + if entry is None: + continue + targets = entry if isinstance(entry, list) else [entry] + for e in targets: + e["variadic_record"] = True + + # Reclassify list-kind keywords that don't end with a standalone '/' + # as 'fixed' (size_count = records_meta length) so closeKw doesn't + # demand a final terminator. VFPPROD/VFPINJ: the trailing variadic + # record's '/' is the natural end of the block. + for name in NO_LIST_TERMINATOR_KEYWORDS: + entry = index.get(name) + if entry is None: + continue + targets = entry if isinstance(entry, list) else [entry] + for e in targets: + if e.get("size_kind") != "list": + continue + records_meta = e.get("records_meta") + if records_meta: + e["size_kind"] = "fixed" + e["size_count"] = len(records_meta) + + # UDQ SUMMARY mnemonics are documented under placeholder names of the + # form ``UX{2,}`` (FUXXXXXX, WUXXXXXX, …) — the trailing + # X's stand for the user-defined UDQ name (up to six characters). Real + # decks write e.g. ``WUWI1`` or ``FUOIL``. Strip the trailing X's so + # the entry is keyed/named by the prefix alone (``WU``, ``FU``, …) and + # mark it templated so the standard ``+[A-Z0-9]+`` fallback + # resolves deck tokens like WUWI1 to the WU template entry. + # Lazy quantifier on the prefix so ``FUXXXXXX`` splits as ("FU", "XXXXXX"), + # not ("FUXXXX", "XX"). ``[A-Z]+`` would otherwise consume the X's first. + udq_placeholder_re = re.compile(r"^([A-Z]+?)X{2,}$") + udq_renames: list[tuple[str, str]] = [] + for name in list(index.keys()): + m = udq_placeholder_re.match(name) + if not m: + continue + prefix = m.group(1) + if prefix in index: + # Prefix entry already exists from some other path; leave the + # placeholder alone rather than risk overwriting real data. + continue + udq_renames.append((name, prefix)) + for old_name, new_name in udq_renames: + entry = index.pop(old_name) + if isinstance(entry, list): + for e in entry: + e["name"] = new_name + e["templated"] = True + else: + entry["name"] = new_name + entry["templated"] = True + index[new_name] = entry + print(f"\nIndexed {total} keywords ({skipped} skipped)") return index diff --git a/scripts/test_build_keyword_index.py b/scripts/test_build_keyword_index.py index 4a4ece5..ddcd463 100644 --- a/scripts/test_build_keyword_index.py +++ b/scripts/test_build_keyword_index.py @@ -39,6 +39,7 @@ _opm_item_for_param, _classify_size, _summary_size_shape, + _summary_optional_body, NS, SECTION_MAP, ) @@ -1146,10 +1147,12 @@ def test_field_scope_gets_size_kind_none(self, tmp_path): assert entry["size_kind"] == "none" assert "size_count" not in entry - def test_well_and_group_scope_get_size_kind_fixed_one(self, tmp_path): - # Group/well/region/etc. mnemonics take a single record (a list of - # names or just '/'); modelling them as 'list' would wrongly demand - # a closing standalone '/'. They're 'fixed' with size_count=1. + def test_well_and_group_scope_get_size_kind_array(self, tmp_path): + # Group/well/region/etc. mnemonics take an optional list of names + # spread across one or more lines and closed by a single '/'. That's + # ``size_kind: 'array'`` plus ``optional_body: True`` so a bare + # ``WOPR`` stacked back-to-back with another mnemonic is accepted + # but a forgotten closing '/' after listed names is still flagged. body = self._fgwcl_table( _row("Flow", "Gas-Oil Ratio", "GOR", "", "GGOR", "WGOR", "", "", ""), @@ -1157,8 +1160,9 @@ def test_well_and_group_scope_get_size_kind_fixed_one(self, tmp_path): fodt = self._write_section_fodt(tmp_path, body) out = parse_summary_mnemonics(fodt) for kw in ("GGOR", "WGOR"): - assert out[kw]["size_kind"] == "fixed" - assert out[kw]["size_count"] == 1 + assert out[kw]["size_kind"] == "array" + assert "size_count" not in out[kw] + assert out[kw]["optional_body"] is True def test_skips_empty_scope_cells(self, tmp_path): # Only WOPT exists for this row; the empty Field/Group cells must @@ -1218,8 +1222,9 @@ def test_picks_up_network_model_gpr(self, tmp_path): fodt = self._write_section_fodt(tmp_path, body) out = parse_summary_mnemonics(fodt) assert "GPR" in out - assert out["GPR"]["size_kind"] == "fixed" - assert out["GPR"]["size_count"] == 1 + assert out["GPR"]["size_kind"] == "array" + assert "size_count" not in out["GPR"] + assert out["GPR"]["optional_body"] is True def test_tags_tracer_rows_as_templated(self, tmp_path): # Tracer mnemonics (FTPR, WTPC, …) are templates — the user appends @@ -1256,10 +1261,11 @@ def test_picks_up_field_group_control_mode_table(self, tmp_path): out = parse_summary_mnemonics(fodt) for kw in ("FMCTP", "GMCTP", "FMCTW", "GMCTW", "FMCTG", "GMCTG"): assert kw in out - # Field-scope stays bare; group-scope takes a single record. + # Field-scope stays bare; group-scope takes an optional list of names. assert out["FMCTP"]["size_kind"] == "none" - assert out["GMCTP"]["size_kind"] == "fixed" - assert out["GMCTP"]["size_count"] == 1 + assert out["GMCTP"]["size_kind"] == "array" + assert "size_count" not in out["GMCTP"] + assert out["GMCTP"]["optional_body"] is True # Description spans pair Field/Group correctly. assert "Production Group" in out["FMCTP"]["summary"] assert "Production Group" in out["GMCTP"]["summary"] @@ -1278,11 +1284,13 @@ def test_picks_up_well_control_mode_table(self, tmp_path): body = _table(title, groups, mnem, desc) fodt = self._write_section_fodt(tmp_path, body) out = parse_summary_mnemonics(fodt) - assert out["WSTAT"]["size_kind"] == "fixed" - assert out["WSTAT"]["size_count"] == 1 + assert out["WSTAT"]["size_kind"] == "array" + assert "size_count" not in out["WSTAT"] + assert out["WSTAT"]["optional_body"] is True assert "Well Status" in out["WSTAT"]["summary"] assert "Well Mode of Control" in out["WMCTL"]["summary"] - assert out["WMCTL"]["size_kind"] == "fixed" + assert out["WMCTL"]["size_kind"] == "array" + assert out["WMCTL"]["optional_body"] is True def test_picks_up_performance_table(self, tmp_path): # The "OPM Flow Simulation Performance" table has a different @@ -1328,9 +1336,9 @@ def test_handles_aquifer_and_recovery_table_titles(self, tmp_path): for kw in ("FAQR", "AAQR", "ALQR", "ANQR", "FOE", "ROE"): assert kw in out assert out["FAQR"]["size_kind"] == "none" - assert out["AAQR"]["size_kind"] == "fixed" and out["AAQR"]["size_count"] == 1 + assert out["AAQR"]["size_kind"] == "array" and out["AAQR"]["optional_body"] is True assert out["FOE"]["size_kind"] == "none" - assert out["ROE"]["size_kind"] == "fixed" and out["ROE"]["size_count"] == 1 + assert out["ROE"]["size_kind"] == "array" and out["ROE"]["optional_body"] is True class TestSummarySizeShape: @@ -1338,9 +1346,12 @@ def test_field_scope_none(self): assert _summary_size_shape("FOPR") == ("none", None) assert _summary_size_shape("FWPR") == ("none", None) - def test_other_scopes_fixed_one(self): + def test_other_scopes_array_optional(self): + # W/G/R/B/A-prefixed mnemonics take an optional list of names + # spread across one or more lines and closed by a single '/'. for kw in ("WOPR", "WWIR", "GGOR", "ROE", "BPR", "AAQR"): - assert _summary_size_shape(kw) == ("fixed", 1) + assert _summary_size_shape(kw) == ("array", None) + assert _summary_optional_body(kw) is True class TestAttachStringOptions: diff --git a/vscode-extension/data/keyword_index_compact.json b/vscode-extension/data/keyword_index_compact.json index c199edb..1373790 100644 --- a/vscode-extension/data/keyword_index_compact.json +++ b/vscode-extension/data/keyword_index_compact.json @@ -1 +1 @@ -{"ACTDIMS":{"name":"ACTDIMS","sections":["RUNSPEC"],"supported":null,"summary":"The ACTDIMS keyword defines the maximum number of properties associated with the ACTION keyword. The ACTION keyword allows the user to enter computational logic and calculations to the simulation run based on the how the simulation run is proceeding.","parameters":[{"index":1,"name":"MXACTNS","description":"A positive integer value that defines the maximum number of ACTION keywords defined in the input deck.","units":{},"default":"2","value_type":"INT"},{"index":2,"name":"MXLINES","description":"A positive integer value that defines the maximum number of lines in an ACTION statement.","units":{},"default":"50","value_type":"INT"},{"index":3,"name":"MXCHARS","description":"A positive integer value that defines the maximum characters in an ACTION statement.","units":{},"default":"80","value_type":"INT"},{"index":4,"name":"MXSTATMS","description":"A positive integer value that defines the maximum number of conditional statements in the ACTION statement.","units":{},"default":"3","value_type":"INT"}],"example":"-- ACTION ACTION ACTION ACTION\n-- MXACTNS MXLINES MXCHARS MXSTATMS\nACTDIMS\n2 50 80 3 /\nThe above example defines the default values for the ACTDIMS keyword.","expected_columns":4,"size_kind":"fixed","size_count":1},"ACTPARAM":{"name":"ACTPARAM","sections":["RUNSPEC"],"supported":null,"summary":"The ACTPARAM keyword defines the maximum target percent value for the ACTION series of keywords and the fractional equality tolerance for determining if two numbers are numerically equal when comparing values using the ACTION series of keywords. The ACTION keyword allows the user to enter computational logic and calculations to the simulation run based on the how the simulation run is proceeding.","parameters":[{"index":1,"name":"MXTOLS","description":"A positive real value that defines the maximum target percent number for the ACTION series of keywords. The default value of 100 means the target is not applied.","units":{"field":"percent 100.0","metric":"percent 100.0","laboratory":"percent 100.0"},"default":"Defined"},{"index":2,"name":"MXEQLS","description":"MXEQLS a real positive number greater than zero and less than one that defines the tolerance used to determine if two real values are equal for comparing values in the ACTION series of keywords. Floating-point numbers (as implemented in computers) are never exact, one cannot compare floating point numbers for exact equality. Thus, MXEQLS defines a tolerance. For example, the default value of 1 x 10-4 means that if the difference between two real values is less than 1 x 10-4 then the values are considered equal.","units":{"field":"fraction 1 x 10-4","metric":"fraction 1 x 10-4","laboratory":"fraction 1 x 10-4"},"default":"Defined"}],"example":"--\n-- ACTION ACTION\n-- MXTOLS MXEQLS\nACTPARAM\n5.0 1.0E-4 /\nThe above example defines the maximum tolerance to be 5% and the equality tolerance to be the default value of 1.0 x 10-4.","size_kind":"fixed","size_count":1},"AITS":{"name":"AITS","sections":["RUNSPEC","SCHEDULE"],"supported":false,"summary":"Turns on the commercial simulator’s intelligent time stepping.","parameters":[],"example":"","size_kind":"none","size_count":0},"AITSOFF":{"name":"AITSOFF","sections":["RUNSPEC","SCHEDULE"],"supported":false,"summary":"Turns off the commercial simulator’s intelligent time stepping.","parameters":[],"example":"","size_kind":"none","size_count":0},"ALKALINE":{"name":"ALKALINE","sections":["RUNSPEC"],"supported":false,"summary":"This keyword indicates that an alkaline phase is present in the model and to activate the Alkaline Model in the run. The keyword will also invoke data input file checking to ensure that all the required Alkaline Model input parameters are defined in the input deck.","parameters":[],"example":"--\n-- ALKALINE PHASE IS PRESENT IN THE RUN\n--\nALKALINE\nThe above example declares that the alkaline phase is active in the model to activate Alkaline Model.","size_kind":"none","size_count":0},"API":{"name":"API","sections":["RUNSPEC"],"supported":false,"summary":"This keyword switches on API tracking so that the various “oil types” are tracked in the model.","parameters":[],"example":"--\n-- ACTIVATE THE API TRACKING OPTION\n--\nAPI\nThe above example switches on the API tracking facility.","size_kind":"none","size_count":0},"AQUDIMS":{"name":"AQUDIMS","sections":["RUNSPEC"],"supported":null,"summary":"The AQUDIMS keyword defines the dimensions of the various aquifer property data. The data is normally entered on a single line and is terminated by a “/”.","parameters":[{"index":1,"name":"MXNAQN","description":"A positive integer value that defines the AQUNUM keyword maximum number of lines associated with this keyword, that is the maximum number of numerical aquifers","units":{},"default":"1","value_type":"INT"},{"index":2,"name":"MXNAQC","description":"A positive integer value that defines the AQUCON keyword maximum number of lines of connection data associated with this keyword, that is the maximum number of lines of connection data for numerical aquifers.","units":{},"default":"1","value_type":"INT"},{"index":3,"name":"NIFTBL","description":"A positive integer value that defines the AQUTAB keyword maximum number of Carter-Tracy aquifer tables associated with this keyword.","units":{},"default":"1","value_type":"INT"},{"index":4,"name":"NRIFTB","description":"A positive integer value that defines the AQUTAB keyword maximum number of rows in the Carter-Tracy aquifer tables associated with this keyword. NRIFTB must not be less than 36 in order to accommodate the default infinite acting Carter-Tracy aquifer influence function.","units":{},"default":"36","value_type":"INT"},{"index":5,"name":"NANAQ","description":"A positive integer value that defines the AQUFETP, AQUFLUX and AQUCT maximum number of analytical aquifers defined by these three keywords.","units":{},"default":"1","value_type":"INT"},{"index":6,"name":"NCAMAX","description":"A positive integer value that defines the maximum number of cells connected to an analytical aquifer.","units":{},"default":"1","value_type":"INT"},{"index":7,"name":"MXNALI","description":"A positive integer value that defines the maximum number of aquifer lists.","units":{},"default":"0","value_type":"INT"},{"index":8,"name":"MXAAQL","description":"A positive integer value that defines the maximum number of analytical aquifers in any single aquifer list as defined by (7).","units":{},"default":"0","value_type":"INT"}],"example":"--\n-- AQF AQF AQF AQF AQF AQF AQF AQF\n-- MXAQN MXNAQC NIFTBL NRIFTB NANAQU NCAMAX MXNALI MXAAQL\nAQUDIMS\n1* 1* 1* 1* 1* 1* 1* 1* /\nThe above example defines the default values for the AQUDIMS keyword.","expected_columns":8,"size_kind":"fixed","size_count":1},"AUTOREF":{"name":"AUTOREF","sections":["RUNSPEC"],"supported":false,"summary":"The AUTOREF keyword activates the Auto Refinement option and defines the parameters for this feature.","parameters":[{"index":1,"name":"NX","description":"","units":{},"default":"1","value_type":"INT"},{"index":2,"name":"NY","description":"","units":{},"default":"1","value_type":"INT"},{"index":3,"name":"NZ","description":"","units":{},"default":"1","value_type":"INT"},{"index":4,"name":"OPTION_TRANS_MULT","description":"","units":{},"default":"0","value_type":"DOUBLE"}],"example":"","expected_columns":4,"size_kind":"list"},"BIGMODEL":{"name":"BIGMODEL","sections":["RUNSPEC"],"supported":null,"summary":"The original intention in the commercial simulator was to define an optimized memory allocation method to handle large models; this has since become redundant and has been retired in the commercial simulator.","parameters":[],"example":"","size_kind":"none","size_count":0},"BIOFILM":{"name":"BIOFILM","sections":["RUNSPEC"],"supported":null,"summary":"The BIOFILM keyword activates the biofilm model for the run. Biofilm-related effects in subsurface applications such as hydrogen storage include reduced injectivity and hydrogen loss. The conceptual model includes the following mechanisms: (1) Biofilm is present in the storage site prior to injection and (2) the biofilm consumes injected H2/CO2, leading to clogging effects.","parameters":[],"example":"--\n-- ACTIVATE THE BIOFILM MODEL\n--\nBIOFILM\n--\n-- ACTIVATE THE H2STORE MODEL\n--\nWATER\nGAS\nH2STORE\nThe above example declares that the BIOFILM model is active for the run and activates the H2STORE model. For a complete example of this model, see H2STORE_BIOFILM.DATA.\n| Note This is an OPM Flow specific keyword used to investigate biofilm effects in underground applications. The module requires that either the CO2STORE or H2STORE keywords in the RUNSPEC to be active. |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"none","size_count":0},"BLACKOIL":{"name":"BLACKOIL","sections":["RUNSPEC"],"supported":null,"summary":"This keyword switches on the black-oil formulation, and is equivalent to setting the phases present in the model to be oil, vaporized oil, gas, and dissolved gas. Note if water is present in the model this needs to be explicitly stated via the WATER keyword in the RUNSPEC section (see also the LIVEOIL keywords in the RUNSPEC section). The keyword is used by the commercial simulator’s compositional THERMAL option to set the phases present in the model.","parameters":[],"example":"The following example activates the black-oil phases in the model.\n--\n-- ACTIVATE BLACK-OIL PHASES\n--\nBLACKOIL\nAlternatively one could explicitly declare the phases using the following keywords in the RUNSPEC section.\n--\n-- OIL PHASE IS PRESENT IN THE RUN\n--\nOIL\n--\n-- VAPORIZED OIL IN WET GAS IS PRESENT IN THE RUN\n--\nVAPOIL\n--\n-- GAS PHASE IS PRESENT IN THE RUN\n--\nGAS\n--\n-- DISSOLVED GAS IN LIVE OIL IS PRESENT IN THE RUN\n--\nDISGAS\nThe above example switches on the black-oil phases in the model.","size_kind":"none","size_count":0},"BPARA":{"name":"BPARA","sections":["RUNSPEC"],"supported":false,"summary":"The BPARA keyword activates the block parallel license in the commercial simulator. There is no data required for this keyword; however the keyword should be followed by the PARALLEL keyword in the RUNSPEC section, as illustrated in the example below.","parameters":[],"example":"--\n-- ACTIVATE BLOCK PARALLEL LICENSE\n--\nBPARA\n--\n-- PARALLEL MULTI-CORE OPTIONS\n-- NDMAIN MACHINE TYPE\nPARALLEL\n8 DISTRIBUTED /\nThe above example sets the number of domains (or processors) to eight and for the simulation to run in block parallel mode. This has no effect in OPM Flow input decks.","size_kind":"none","size_count":0},"BPIDIMS":{"name":"BPIDIMS","sections":["RUNSPEC"],"supported":false,"summary":"The BPDIMS keyword defines the dimensions of the interpolated grid block quantities for the BPR_X, BHD_X,BHDF_X, BSCN_X and BCTRA_X, etc. variables declared in the SUMMARY section.","parameters":[{"index":1,"name":"MXNBIP","description":"","units":{},"default":"10","value_type":"INT"},{"index":2,"name":"MXNLBI","description":"","units":{},"default":"1","value_type":"INT"}],"example":"","expected_columns":2,"size_kind":"fixed","size_count":1},"BRINE":{"name":"BRINE","sections":["RUNSPEC"],"supported":false,"summary":"The BRINE keyword activates the standard Brine Tracking model and optionally defines the water phase to have various salinities if the ECLMC keyword in the RUNSPEC section has been used to activate the Multi-Component Brine model, that allows for the water phase to have multiple water salinities. Note that the Multi-Component Brine model is not supported by OPM Flow.","parameters":[{"index":1,"name":"SALTS","description":"An optional character vector string that defines the salts to be tracked for when the Multi-Component Brine model has been activated by the ECLMC keyword in the RUNSPEC section. SALTS should be set to one or more of the following salt chemical formulae:","units":{},"default":"None","value_type":"STRING"}],"example":"The first example actives the standard Brine model and has no terminating “/”.\n--\n-- ACTIVATE STANDARD BRINE MODEL IN THE RUN\n--\nBRINE\nThe second example illustrates how to activate OPM Flow’s Salt Precipitation model.\n--\n-- ACTIVATE STANDARD BRINE MODEL IN THE RUN\n--\nBRINE\n--\n-- ACTIVATE THE OPM FLOW SALT PRECIPITATION MODEL (OPM FLOW KEYWORD)\n--\nPRECSALT\n--\n-- VAPORIZED WATER IN DRY/WET GAS IS PRESENT IN THE RUN (OPM FLOW KEYWORD)\n--\nVAPWAT\nThe third and final example activates the Multi-Component brine model with four different salts.\n--\n-- ACTIVATE MULTI-COMPONENT BRINE MODEL\n--\nECLMC\n--\n-- DEFINE WATER PHASE MULTI-COMPONENT BRINE COMPONENTS\n--\n-- SALT1 SALT2 SALT3 SALT4 SALT5\nBRINE\nNACL CACL2 MGC03 K2CO3 /\nThis option is currently not available in OPM Flow.","size_kind":"fixed","size_count":1,"variadic_record":true},"CART":{"name":"CART","sections":["RUNSPEC"],"supported":false,"summary":"CART activates the Cartesian grid geometry for the main model, as oppose to a radial geometry. This is the default geometry and therefore the keyword does have to be used to activate this type of geometry.","parameters":[],"example":"","size_kind":"none","size_count":0},"CBMOPTS":{"name":"CBMOPTS","sections":["SRUNSPEC"],"supported":false,"summary":"This keyword sets the options for the Coal Bed Methane model which is activated via the COAL keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"ADSORPTION_MODEL","description":"","units":{},"default":"TIMEDEP","value_type":"STRING"},{"index":2,"name":"ALLOW_WATER_FLOW","description":"","units":{},"default":"YES","value_type":"STRING"},{"index":3,"name":"ALLOW_PERMEAB","description":"","units":{},"default":"NOKRMIX","value_type":"STRING"},{"index":4,"name":"COUNT_PASSES","description":"","units":{},"default":"NOPMREB","value_type":"STRING"},{"index":5,"name":"METHOD","description":"","units":{},"default":"PMSTD","value_type":"STRING"},{"index":6,"name":"SCALING_VALUE","description":"","units":{},"default":"PMSCAL","value_type":"STRING"},{"index":7,"name":"APPLICATION","description":"","units":{},"default":"PMPVK","value_type":"STRING"},{"index":8,"name":"PRESSURE_CHOP","description":"","units":{},"default":"NOPMPCHP","value_type":"STRING"},{"index":9,"name":"MIN_PORE_VOLUME","description":"","units":{},"default":"5e-06","value_type":"DOUBLE"}],"example":"","expected_columns":9,"size_kind":"fixed","size_count":1},"CO2SOL":{"name":"CO2SOL","sections":["RUNSPEC"],"supported":null,"summary":"The CO2SOL keyword activates dissolved carbon dioxide (CO2) in the water phase, where CO2 is represented by the SOLVENT pseudo component, using the simulator’s CO2-Brine PVT model. This keyword is a compositional keyword in the commercial simulator but has been implemented in OPM Flow’s black-oil model.","parameters":[],"example":"The example shows the usage of CO2SOL to model CO2 injection in a live-oil reservoir. The RUNSPEC section includes the CO2SOL keyword, which activates dissolved carbon dioxide (CO2) in the water phase. The SOLVENT keyword activates the solvent pseudo component, which represents CO2. The DISGASW keyword has been used to activate dissolved CO2 in the brine.\n-- ==============================================================================\n--\n-- RUNSPEC SECTION\n--\n-- ==============================================================================\nRUNSPEC\n-- ------------------------------------------------------------------------------\n-- FLUID TYPES AND TRACER OPTIONS\n-- ------------------------------------------------------------------------------\n--\n-- ACTIVATE DISSOLVED CO2 IN WATER (OPM FLOW KEYWORD)\n--\nCO2SOL\n--\n-- SOLVENT PHASE IS PRESENT IN THE RUN\n--\nSOLVENT\n--\n-- DISSOLVED CO2 IN WATER IS PRESENT IN THE RUN (OPM FLOW KEYWORD)\n--\nDISGASW\nThe second part of the example covers the additional data required in the PROPS section, in which the CO2-gas miscible relative permeabilities are defined using the SSFN keyword. The initial temperature and salinity are defined using the RTEMP and SALINITY keywords. The oil and gas PVT properties should be defined in the normal way. No water PVT data is required.\n-- ==============================================================================\n--\n-- PROPS SECTION\n--\n-- ==============================================================================\nPROPS\n--\n-- RESERVOIR\n-- TEMPERATURE\n-- -----------\nRTEMP\n80.0 / RESERVOIR TEMP\n--\n-- SET SALINITY FOR ALL CELLS (OPM FLOW KEYWORD)\n--\nSALINITY\n0.7 /\n--\n-- SOLVENT RELATIVE PERMEABILITY TABLES\n--\nSSFN\n-- SGAS KRGT KRST\n-- FRAC\n-- -------- -------- --------\n0.0000 0.0000 0.0000\n1.0000 1.0000 1.0000 /\nThe third part of the example covers initialising the model in the SOLUTION section. Here the EQUIL keyword is used as normal to equilibrate the oil, gas and water phases, and the SSOL keyword to specify that there is initially no CO2 present in the gas phase.\n-- ==============================================================================\n--\n-- SOLUTION SECTION\n--\n-- ==============================================================================\nSOLUTION\n--\n-- DATUM DATUM OWC PCOW GOC PCGO RS RV N E300 RVW\n-- DEPTH PRESS DEPTH ---- DEPTH ---- OPT OPT OPT OPT OPT\nEQUIL\n2000.0 200.0 1900.0 0.00 2000.0 0.00 1* 1* 1* 2* 1* /\n--\n-- DEFINE INITIAL EQUILIBRATION SOLVENT SAT VALUES FOR ALL CELLS IN THE MODEL\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nSSOL\n30000*0.0 /\nFor the summary section, the CO2 storage quantity can be tracked using the solvent injection and production volumes as shown below.\n-- ==============================================================================\n--\n-- SUMMARY SECTION\n--\n-- ==============================================================================\nSUMMARY\n--\n-- EXPORT STANDARD SUMMARY VARIABLE VECTORS TO FILE\n--\nALL\n--\n-- FIELD SOLVENT INJECTION RATE\nFNIR\n--\n-- FIELD SOLVENT PRODUCTION RATE\nFNPR\n--\n-- FIELD SOLVENT INJECTION TOTAL\nFNIT\n--\n-- FIELD SOLVENT PRODUCTION TOTAL\nFNPT\nThe final part of the example covers the SCHEDULE section. The WSOLVENT keyword is used to specify the injected solvent fraction (in this case pure CO2).\n-- ==============================================================================\n--\n-- SCHEDULE SECTION\n--\n-- ==============================================================================\nSCHEDULE\n--\n-- RESTART CONTROL BASIC = 1 (LAST REPORT TIME ONLY)\n--\nRPTRST\n'BASIC=1' 'ALLPROPS' /\n--\n-- DEFINE GAS INJECTION WELL SOLVENT FRACTION\n--\n-- WELL SOLVENT\n-- NAME FRACTION\n-- --------\nWSOLVENT\nGI01 1.0000 /\n/","size_kind":"none","size_count":0},"CO2STORE":{"name":"CO2STORE","sections":["RUNSPEC"],"supported":false,"summary":"The CO2STORE keyword activates the carbon dioxide (CO2) storage model for the run to account for both carbon dioxide and water phase solubility, via the simulator’s CO2-Brine PVT model. This keyword is a compositional keyword in the commercial simulator but has been implemented in OPM Flow’s black-oil model.","parameters":[],"example":"The first example shows the standard usage of CO2STORE with Option (1) the Gas-Water model (GASWAT). Here we also activate the dissolved gas in water (DISGASW) and vaporized water in gas (VAPWAT) options in the RUNSPEC section.\n-- ==============================================================================\n--\n-- RUNSPEC SECTION\n--\n-- ==============================================================================\nRUNSPEC\n-- ------------------------------------------------------------------------------\n-- FLUID TYPES AND TRACER OPTIONS\n-- ------------------------------------------------------------------------------\n--\n-- ACTIVATE CO2 STORAGE IN THE MODEL (OPM FLOW CO2 STORAGE KEYWORD)\n--\nCO2STORE\n--\n-- ACTIVATE GAS-WATER THE MODEL (OPM FLOW KEYWORD)\n--\nGASWAT\n--\n-- DISSOLVED GAS IN WATER IS PRESENT IN THE RUN (OPM FLOW KEYWORD)\n--\nDISGASW\n--\n-- VAPORIZED WATER IN DRY/WET GAS IS PRESENT IN THE RUN (OPM FLOW KEYWORD)\n--\nVAPWAT\nThe second part of the example covers the data required for the PROPS section, in which the two-phase relative permeability functions are set using GSF and WSF keywords.\n-- ==============================================================================\n--\n-- PROPS SECTION\n--\n-- ==============================================================================\nPROPS\n--\n-- RESERVOIR\n-- TEMPERATURE\n-- -----------\nRTEMP\n80.0 / RESERVOIR TEMP\n--\n-- ROCK COMPRESSIBILITY\n--\n-- REFERENCE PRESSURE IS TAKEN FROM THE HCPV WEIGHTED RESERVOIR PRESSURE\n--\n-- REF PRES CF\n-- BARSA 1/BARSA\n-- -------- --------\nROCK\n200.0 5.0E-05 / ROCK COMPRESSIBILITY\n--\n-- GAS RELATIVE PERMEABILITY TABLES (OPM FLOW KEYWORD)\n--\nGSF\n-- SGAS KRG PCGW\n-- FRAC PSIA\n-- -------- -------- -------\n0.000 0.000 0.0\n0.080 0.001 0.0\n0.170 0.010 0.0\n0.350 0.050 0.0\n0.530 0.200 0.0\n0.620 0.350 0.0\n0.650 0.390 0.0\n0.710 0.560 0.0\n0.800 1.000 0.0 / TABLE NO. 01\n--\n-- WATER RELATIVE PERMEABILITY TABLES (OPM FLOW KEYWORD)\n--\nWSF\n-- SWAT KRW\n-- FRAC\n-- -------- --------\n0.200 0.0000\n0.400 0.1000\n0.800 0.5000\n1.000 1.0000 / TABLE NO. 01\n--\n-- SET SALINITY FOR ALL CELLS (OPM FLOW KEYWORD)\n--\nSALINITY\n0.7 /\nNo other data is required to define the fluid and rock properties in the PROPS section as the data is generated from internal analytic correlations and models by the simulator. Finally, note that units for salinity are to the 10-3, thus for metric units we have 10-3 x kg-M/kg.\nThe third part of the example covers initializing the model in the SOLUTION section. Here we set the EQUIL(EQLOPT6) parameter equal to one, to use table number one of the RVWVD keyword, in order to set the vaporized water versus depth distribution for the model.\n-- ==============================================================================\n--\n-- SOLUTION SECTION\n--\n-- ==============================================================================\nSOLUTION\n--\n-- SYSTEM IS SATURATED WITH WATER\n--\n-- DATUM DATUM OWC PCOW GOC PCGO RS RV N E300 RVW\n-- DEPTH PRESS DEPTH ---- DEPTH ---- OPT OPT OPT OPT OPT\nEQUIL\n2000.0 200.0 1800.0 0.00 1800.0 0.00 1* 1* 1* 2* 1 /\n--\n-- WATER VAPOR RATIO VS DEPTH (OPM FLOW KEYWORD)\n--\n-- DEPTH RVW\n-- STB/MSCF\n-- ------ --------\nRVWVD\n1000.0 0.000\n3000.0 0.000 / RVW VS DEPTH EQUIL REGN 01\nIn the SUMMARY section, the simulator supports summary vectors specific to CO2 storage (see Section 11.1.12 Option Specific Variables - CO2STORE/H2STORE Model) including those shown below.\n-- ==============================================================================\n--\n-- SUMMARY SECTION\n--\n-- ==============================================================================\nSUMMARY\n--\n-- EXPORT STANDARD SUMMARY VARIABLE VECTORS TO FILE\n--\nALL\n--\n-- FIELD CO2 DISOLVED IN WATER PHASE\nFWCD\n--\n-- FIELD CO2 TRAPPED IN GAS PHASE\nFGCDI\n--\n-- FIELD CO2 MOBILE IN GAS PHASE\nFGCDM\nThe final part of the example covers the SCHEDULE section. The standard WCONINJE keyword is used to set the gas injection rate, in this case 100,000 sm3/day of CO2.\n-- ===========================================","size_kind":"none","size_count":0},"COAL":{"name":"COAL","sections":["RUNSPEC"],"supported":false,"summary":"The COAL keyword actives the coal phase and the Coal Bed Methane (“CBM”) model for the run.","parameters":[],"example":"--\n-- ACTIVATE THE COAL PHASE (CBM MODEL) IN THE MODEL\n--\nCOAL\nThe above example declares that the Coal phase is active in the run and activates the CBM model option.","size_kind":"none","size_count":0},"COLUMNS":{"name":"COLUMNS","sections":["RUNSPEC","GRID","EDIT","PROPS","REGIONS","SOLUTION","SUMMARY","SCHEDULE"],"supported":null,"summary":"The COLUMNS keyword defines the input file column margins; characters outside the margins are ignored by the input parser.","parameters":[{"index":1,"name":"LEFT_MARGIN","description":"","units":{},"default":"1","value_type":"INT"},{"index":2,"name":"RIGHT_MARGIN","description":"","units":{},"default":"132","value_type":"INT"}],"example":"","expected_columns":2,"size_kind":"fixed","size_count":1},"COMPS":{"name":"COMPS","sections":["RUNSPEC"],"supported":true,"summary":"The COMPS keyword activates the Compositional Modeling Formulation, and declares the number of components active in the model.","parameters":[{"index":1,"name":"COMPS","description":"A positive integer defining the number of compositional components active in the model. Only the default value of two is currently supported by OPM Flow.","units":{},"default":"2","value_type":"INT"}],"example":"The following example shows how to request a two component compositional modeling formulation to be used with the CO2STORE and GASWAT options.\n-- ==============================================================================\n--\n-- RUNSPEC SECTION\n--\n-- ==============================================================================\nRUNSPEC\n--\n-- ACTIVATE CO2 STORAGE IN THE MODEL (OPM FLOW CO2 STORAGE KEYWORD)\n--\nCO2STORE\n--\n-- ACTIVATE COMPOSITIONAL MODELING FORMULATION (OPM FLOW KEYWORD)\n--\nCOMPS\n2 /\n--\n-- ACTIVATE GAS-WATER THE MODEL (OPM FLOW KEYWORD)\n--\nGASWAT\n| Note This keyword is only supported by OPM Flow when the two component gas-water CO2 storage model has been activated using the CO2STORE keyword and either the GASWAT or the GAS and WATER keywords in the RUNSPEC section. Secondly, although OPM Flow parses the keyword, the simulator currently ignores the data for this keyword. |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":1,"size_kind":"fixed","size_count":1},"CPR":{"name":"CPR","sections":["RUNSPEC","SUMMARY"],"supported":null,"summary":"Turns on the Constrained Pressure Residual (“CPR”)66\n Wallis, J. R., Little, T. E., and Nolen, J. S.: \"Constrained Residual Acceleration of Conjugate Residual Methods,\" paper SPE 13536 presented at the SPE Reservoir Simulation Symposium, Dallas, Texas, USA (February 10-13, 1985)., 67\n R. Scheichl, M. Roland, J. Wendebourg, Decoupling and block preconditioning for sedimentary basin simulations, Computational Geosciences 7 (2003) 295{318.and 68\n Klemetsdal, Ø.S., Møyner, O. & Lie, KA. Accelerating multiscale simulation of complex geomodels by use of dynamically adapted basis functions. Comput Geosci 24, 459–476 (2020). https://doi.org/10.1007/s10596-019-9827-z.preconditioner linear solver option, and declares how the solver should be applied. The keyword is equivalent to using the OPM Flow command line parameter --linear-solver= “cprw”. Note that if the command line has been used, then this will take precedence over the CPR keyword.","parameters":[{"index":1,"name":"CPROPTN","description":"A defined character string that determines how the CPR linear solver should be applied, and should be set to one of the following: ORIGINAL: Here the solver is applied for the whole of the simulation. ADAPTIVE: This option applies the more computational demanding CPR linear solver, only in parts of the run that would benefit from its use, for example when linear convergence is challenging. Note that OPM Flow only supports the ORIGINAL option, which is the default value in OPM Flow, whereas the default value in the commercial simulator is ADAPTIVE. .","units":{},"default":"ORIGINAL","value_type":"STRING"},{"index":2,"name":"I","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"J","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"K","description":"","units":{},"default":"","value_type":"INT"}],"example":"--\n-- ACTIVATE CONSTRAINED PRESSURE RESIDUAL LINEAR SOLVER FOR THE RUN\n--\nCPR\n/\nThe above example activates the Constrained Pressure Residual preconditioner linear solver using the default option, that is the ORIGINAL option for OPM Flow.\nTo enable the CPR preconditioner linear solver option using the command line parameter, use:\nflow --linear-solver=\"cpr\" CASENAME.DATA\nwhich should usually be combined with the -matrix-add-well-contributions=true option, that is:\nflow --linear-solver=cpr --matrix-add-well-contributions=true CASENAME.DATA\nHowever, the new CPRW preconditioner, that includes wells does not need the latter option, so in this instance use:\nflow --linear-solver=cprw CASENAME.DATA\nAs of this release the CPRW preconditioner, should be considered experimental, and the recommended configuration for running this is:\nflow --linear-solver=cprw --linear-solver-reduction=0.005 --cpr-reuse-setup=4\n--cpr-reuse-interval=10 CASENAME.DATA\nSee new Rasmussen et al.69\n Atgeirr Flø Rasmussen, Tor Harald Sandve, Kai Bao, Andreas Lauser, Joakim Hove, Bård Skaflestad, Robert Klöfkorn, Markus Blatt, Alf Birger Rustad, Ove Sævareid, Knut-Andreas Lie, Andreas Thune, The Open Porous Media Flow reservoir simulator, Computers & Mathematics with Applications, Volume 81, 2021, Pages 159-185, ISSN 0898-1221, https://doi.org/10.1016/j.camwa.2020.05.014. (https://www.sciencedirect.com/science/article/pii/S0898122120302182). for further information on the available numerical algorithms available in OPM Flow.\nAtgeirr Flø Rasmussen, Tor Harald Sandve, Kai Bao, Andreas Lauser, Joakim Hove, Bård Skaflestad, Robert Klöfkorn, Markus Blatt, Alf Birger Rustad, Ove Sævareid, Knut-Andreas Lie, Andreas Thune, The Open Porous Media Flow reservoir simulator, Computers & Mathematics with Applications, Volume 81, 2021, Pages 159-185, ISSN 0898-1221, https://doi.org/10.1016/j.camwa.2020.05.014. (https://www.sciencedirect.com/science/article/pii/S0898122120302182).","expected_columns":4,"size_kind":"list"},"DEBUG":{"name":"DEBUG","sections":["RUNSPEC","GRID","EDIT","PROPS","REGIONS","SOLUTION","SUMMARY","SCHEDULE"],"supported":false,"summary":"This keyword defines the debug data to be written to the debug file (*.DBG). This keyword is not supported by OPM Flow but has no effect on the results so it will be ignored.","parameters":[],"example":""},"DIFFUSE":{"name":"DIFFUSE","sections":["RUNSPEC"],"supported":null,"summary":"The DIFFUSE keyword activates OPM Flow’s Molecular Diffusion option based on fluid and grid data (Sandve et al.70\n Tor Harald Sandve1, Sarah E. Gasda, Atgeirr Rasmussen, and Alf Birger Rustad. Convective dissolution in field scale CO2 storage simulation using the OPM Flow simulator. Submitted to TCCS 11 – Trondheim Conference on CO2 Capture, Transport and Storage Trondheim, Norway – June 21-23, 2021.), similar to the commercial simulator. For field-scale simulations diffusion is a sub-grid phenomenon and is typically not explicitly represented in the flow equations. However, for simulations on the laboratory scale diffusion plays a direct role and therefore needs to be explicitly represented in the flow equations. Diffusion coefficients that control the diffusion depend on temperature, pressure, and salinity. In OPM Flow, the diffusion coefficients are computed internally for pure water using McLachlan and Danckwerts71\n McLachlan, C. N. S., & Danckwerts, P. V. (1972). Des...","parameters":[],"example":"--\n-- ACTIVATE MOLECULAR DIFFUSION OPTION\n--\nDIFFUSE\nThe above example switches on the molecular diffusion facility.\n| Note The option has been tested in combination with the CO2STORE keyword, but not for the general case at this point. |\n|-----------------------------------------------------------------------------------------------------------------------|","size_kind":"none","size_count":0},"DIMENS":{"name":"DIMENS","sections":["RUNSPEC"],"supported":null,"summary":"DIMENS defines the dimensions of the model entered as integer vector. The keyword can be used with all grid types.","parameters":[{"index":1,"name":"NX","description":"A positive integer value that defines the number of grid blocks in the x direction for Cartesian grids or the number of grid blocks in the r direction for radial grids","units":{},"default":"None","value_type":"INT"},{"index":2,"name":"NY","description":"A positive integer value that defines the number of grid blocks in the y direction for Cartesian grids or the number of grid blocks in the theta direction for radial grids.","units":{},"default":"None","value_type":"INT"},{"index":3,"name":"NZ","description":"A positive integer value that defines the number of grid blocks in the z direction for both Cartesian and radial grids.","units":{},"default":"None","value_type":"INT"}],"example":"--\n-- MAX MAX MAX\n-- NDIVIX NDIVIY NDIVIZ\nDIMENS\n46 112 22 /\nThe above example defines the dimensions for the Norne model of 46 cells in the x direction, 112 cells in the y direction and 22 cells in the z direction.","expected_columns":3,"size_kind":"fixed","size_count":1},"DISGAS":{"name":"DISGAS","sections":["RUNSPEC"],"supported":null,"summary":"This keyword indicates that dissolved gas is present in live74\n “Live” oil is oil that contains gas in solution, which is normally the case for most conventional oil reservoirs. However, for oil reservoirs classified as heavy oil reservoirs, the in situ dissolved gas may be negligible and oil would then be classified as gas-free oil which is commonly referred to as “dead” oil. oil in the model and the keyword should only be used if the there is both oil and gas phases in the model. The keyword may be used for oil-water and oil-water-gas input decks that contain the oil and gas phases. The keyword will also invoke data input file checking to ensure that all the required oil and gas phase input parameters are defined in the input deck.","parameters":[],"example":"--\n-- DISSOLVED GAS IN LIVE OIL IS PRESENT IN THE RUN\n--\nDISGAS\nThe above example declares that the dissolved gas in the oil phase is active in the model.","size_kind":"none","size_count":0},"DISGASW":{"name":"DISGASW","sections":["RUNSPEC"],"supported":null,"summary":"This keyword indicates that dissolved gas is present in the water phase in the model. The keyword may only be used for gas-water input decks that contain just the gas and the water phases, which must also be declared. The keyword will also invoke data input file checking to ensure that all the required gas and water phase input parameters are defined in the input deck.","parameters":[],"example":"--\n-- GAS PHASE IS PRESENT IN THE RUN\n--\nGAS\n--\n-- WATER PHASE IS PRESENT IN THE RUN\n--\nWATER\n--\n-- DISSOLVED GAS IN WATER IS PRESENT IN THE RUN (OPM FLOW KEYWORD)\n--\nDISGASW\n--\n-- ACTIVATE CO2 STORAGE IN THE MODEL (OPM FLOW CO2 STORAGE KEYWORD)\n--\nCO2STORE\nThe above example declares that the gas and water phases are present, and that the dissolved gas in the water phase is also active in the model, for modeling CO2 storage.\n| Note This is an OPM Flow specific keyword for the simulator’s Dissolved Gas in Water Model that is activated by declaring that this phase is present in the run. |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"none","size_count":0},"DISPDIMS":{"name":"DISPDIMS","sections":["RUNSPEC"],"supported":false,"summary":"The DISPDIMS key defines the maximum number of dispersion tables, and the maximum number of velocity and concentration elements per table.","parameters":[{"index":1,"name":"NUM_DISP_TABLES","description":"","units":{},"default":"1","value_type":"INT"},{"index":2,"name":"MAX_VELOCITY_NODES","description":"","units":{},"default":"2","value_type":"INT"},{"index":3,"name":"MAX_CONCENTRATION_NODES","description":"","units":{},"default":"1","value_type":"INT"}],"example":"","expected_columns":3,"size_kind":"fixed","size_count":1},"DUALPERM":{"name":"DUALPERM","sections":["RUNSPEC"],"supported":false,"summary":"The DUALPERM keyword activates the Dual Permeability option and the Dual Porosity option for the run. In a dual porosity system flow occurs between the matrix and the fracture only, whereas in a dual permeability system flow also occurs between the matrix grid blocks76\n Warren, J.E. and Root, P.J. 1963. The Behavior of Naturally Fractured Reservoirs. SPE J. 3 (3): 245–255. SPE-426-PA. http://dx.doi.org/10.2118/426-PA., 77\n Gringarten, A.C. 1984. Interpretation of Tests in Fissured and Multilayered Reservoirs With Double-Porosity Behavior: Theory and Practice. J Pet Technol 36 (4): 549-564. SPE-10044-PA. http://dx.doi.org/10.2118/10044-PA., 78\n Serra, K., Reynolds, A.C., and Raghavan, R. 1983. New Pressure Transient Analysis Methods for Naturally Fractured Reservoirs(includes associated papers 12940 and 13014 ). J Pet Technol 35 (12): 2271-2283. SPE-10780-PA. http://dx.doi.org/10.2118/10780-PA, 79\n Barenblatt, G.E., Zheltov, I.P., and Kochina, I.N. 1960. Basi...","parameters":[],"example":"--\n-- ACTIVATE DUAL PERMEABILITY MODEL\n--\nDUALPERM\nThe above example declares that the Dual Permeability option is active for the run.","size_kind":"none","size_count":0},"DUALPORO":{"name":"DUALPORO","sections":["RUNSPEC"],"supported":false,"summary":"The DUALPORO keyword activates the Dual Porosity option for the run. In a dual porosity system flow occurs between the matrix and the fracture only, whereas in a dual permeability system flow also occurs between the matrix grid blocks81\n Warren, J.E. and Root, P.J. 1963. The Behavior of Naturally Fractured Reservoirs. SPE J. 3 (3): 245–255. SPE-426-PA. http://dx.doi.org/10.2118/426-PA., 82\n Gringarten, A.C. 1984. Interpretation of Tests in Fissured and Multilayered Reservoirs With Double-Porosity Behavior: Theory and Practice. J Pet Technol 36 (4): 549-564. SPE-10044-PA. http://dx.doi.org/10.2118/10044-PA., 83\n Serra, K., Reynolds, A.C., and Raghavan, R. 1983. New Pressure Transient Analysis Methods for Naturally Fractured Reservoirs(includes associated papers 12940 and 13014 ). J Pet Technol 35 (12): 2271-2283. SPE-10780-PA. http://dx.doi.org/10.2118/10780-PA, 84\n Barenblatt, G.E., Zheltov, I.P., and Kochina, I.N. 1960. Basic Concepts in the Theory of Homog...","parameters":[],"example":"--\n-- ACTIVATE DUAL POROSITY MODEL\n--\nDUALPORO\nThe above example declares that the Dual Porosity option is active for the run.","size_kind":"none","size_count":0},"DYNRDIMS":{"name":"DYNRDIMS","sections":["RUNSPEC"],"supported":false,"summary":"The DYNRDIMS keyword defines the dimensions for the parameters used by the Dynamic Regions facility, including the maximum number of dynamic regions. The Dynamic Regions facility allows for property and reporting regions to vary as the run progresses, based on the parameters and logic defined by the DYNAMICR keyword in the SOLUTION and PROPS section.","parameters":[{"index":1,"name":"MNUMDR","description":"","units":{},"default":"0","value_type":"INT"},{"index":2,"name":"MXDYNF","description":"","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"MXDYNR","description":"","units":{},"default":"0","value_type":"INT"}],"example":"","expected_columns":3,"size_kind":"fixed","size_count":1},"ECHO":{"name":"ECHO","sections":["RUNSPEC","GRID","EDIT","PROPS","REGIONS","SOLUTION","SUMMARY","SCHEDULE"],"supported":null,"summary":"Turns on echoing of all the input files to the print file; note that this keyword is activated by default and can subsequently be switched off by the NOECHO activation keyword.","parameters":[],"example":"","size_kind":"none","size_count":0},"ECLMC":{"name":"ECLMC","sections":["RUNSPEC"],"supported":false,"summary":"The ECLMC keyword activates the Multi-Component Brine model that allows for the water phase to have multiple water salinities. The keyword should be used in conjunction with the BRINE keyword in the RUNSPEC. Both keywords must be specified to activate the Multi-Component Brine model, whereas the BRINE keyword only is required to activate the standard brine tracking model.","parameters":[],"example":"The first example activates the standard Brine Tracking model.\n--\n-- ACTIVATE STANDARD BRINE MODEL\n--\nBRINE\nThe next example shows the ECLMC and BRINE keywords for when the Multi-Component Brine model is required.\n--\n-- ACTIVATE MULTI-COMPONENT BRINE MODEL\n--\nECLMC\n--\n-- DEFINE WATER PHASE MULTI-COMPONENT BRINE COMPONENTS\n--\n-- SALT1 SALT2 SALT3 SALT4 SALT5\nBRINE\nNACL CACL2 MGC03 /\nThe above example activates the Multi-Component Brine model with three different water salinities.","size_kind":"none","size_count":0},"END":{"name":"END","sections":["RUNSPEC","GRID","EDIT","PROPS","REGIONS","SOLUTION","SUMMARY","SCHEDULE"],"supported":null,"summary":"This keyword marks the end of the input file and can occur in any section. Any keywords and data after the END keyword are ignored.","parameters":[],"example":"","size_kind":"none","size_count":0},"ENDINC":{"name":"ENDINC","sections":["RUNSPEC","GRID","EDIT","PROPS","REGIONS","SOLUTION","SUMMARY","SCHEDULE"],"supported":null,"summary":"This keyword marks the end of an include file specified on the INCLUDE keyword. When the ENDINC keyword is encountered in the INCLUDE file, input data is read from the next keyword in the current file. Any keywords and data after the ENDINC keyword in the INCLUDE file are ignored.","parameters":[],"example":"","size_kind":"none","size_count":0},"ENDSCALE":{"name":"ENDSCALE","sections":["RUNSPEC"],"supported":true,"summary":"The ENDSCALE keyword activates OPM Flow’s relative permeability end-point scaling option. The relative permeability functions are defined using the either the:","parameters":[{"index":1,"name":"DIRECT","description":"A character string that activates or deactivates directional end-point scaling option. If DIRECT is set to NODIR then directional end-point scaling is switched off and the same saturation function is used in the x, y and z directions (unless activated otherwise by the SATOPTS keyword in the RUNSPEC section). In this case the SWL, SWCR, SWU, SGL, SGCR, SGU, SOWCR and SOGCR saturation grid arrays and the KRG, KRORG, KRORW and KRW relative permeability grid cell arrays should be used to enter the grid block end-point data. If DIRECT is set to DIRECT then directional end-point scaling is switched on and different saturation functions are used in the x, y and z directions (unless activated otherwise by the SATOPTS keyword in the RUNSPEC section). Here the directional form of the SWL, SWCR, SWU, SGL, SGCR, SGU, SOWCR and SOGCR saturation grid arrays and the KRG, KRORG, KRORW and KRW relative permeability grid cell arrays should be use to enter the grid block end-point data. For example SWLX, SWLY and SWLZ for SWL. Only the default option is supported by OPM Flow.","units":{},"default":"NODIR","value_type":"STRING"},{"index":2,"name":"IRREVERS","description":"A character string that activates or deactivates non-reversible end-point scaling option. If IRREVERS is set to REVERS then the end-point scaling is set to reversible and results in the same set of end-point arrays being used for flow from the xI to xI + 1 direction as for the flow from the xI to the xI – 1 for all directions (x, y and z). Here the SWLX, SWLY and SWLZ series of keywords should be used instead of SWL type of keywords. Alternatively, if IRREVERS is set to IRREVERS then the end-point scaling is set to non-reversible and results in different sets of end-point arrays being applied for flow from the xI to xI + 1 direction and the xI to the xI – 1 direction, for all directions (x, y, z). in this case the SWLX+, SWLX-, SWLY+, SWLY- SWLZ+ and SWLZ- series of keywords should be utilized instead of SWL or the SWLX, SWLY and SWLZ set of keywords. Only the default option is supported by OPM Flow.","units":{},"default":"REVERS","value_type":"STRING"},{"index":3,"name":"NTENDP","description":"A positive integer that defines the maximum number of saturation end-point depth tables. The end-point depth tables are used to re-scale the saturation tables as a function of depth as opposed to being a grid block property. NTENDP may also be specified on the TABDIMS keyword, and if specified on both here and on the TABDIMS keyword the maximum value of the two is used. Only the default option is supported by OPM Flow.","units":{},"default":"1","value_type":"INT"},{"index":4,"name":"NNODES","description":"A positive integer the defines the maximum number entries for saturation end-point depth tables.","units":{},"default":"20","value_type":"INT"},{"index":5,"name":"MODE","description":"A positive integer that activates the options for temperature dependent saturation end-point scaling in the commercial compositional simulator. MODE should be defaulted with either 1* or zero, which means that scaling can only be performed by grid block end-point scaling properties or via saturation end-point depth tables.","units":{},"default":"0","value_type":"INT"}],"example":"-- DIRC REVERSE MAX MAX\n-- SCALE SCALE TABLES NODES\nENDSCALE\nNODIR REVERS 1* 1* /\nThe above example invokes the end-point scaling option with end-point scaling being non-directional and reversible with the default number of saturation end-point depth tables (one) with 20 entries per table.","expected_columns":5,"size_kind":"fixed","size_count":1},"ENDSKIP":{"name":"ENDSKIP","sections":["RUNSPEC","GRID","EDIT","PROPS","REGIONS","SOLUTION","SUMMARY","SCHEDULE"],"supported":null,"summary":"The ENDSKIP keyword deactivates the skipping of keywords that was activated by the SKIP, SKIP100, or SKIP300 keywords. Each SKIP keyword should be paired with an ENDSKIP keyword.","parameters":[],"example":"","size_kind":"none","size_count":0},"EOS":{"name":"EOS","sections":["RUNSPEC","PROPS"],"supported":null,"summary":"The EOS keyword specifies the Equation Of State (EOS) to be used for each EOS region. The keyword should only be used if the compositional mode has been requested using the COMPS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"EQUATION","description":"","units":{},"default":"PR","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"fixed"},"EQLDIMS":{"name":"EQLDIMS","sections":["RUNSPEC"],"supported":null,"summary":"The EQLDIMS keyword defines the maximum number of properties associated with equilibrating the model, that is initializing the model. A reservoir grid can be separated into separate regions in order to apply different pressure regimes and/or fluid contacts. Care should be taken that the different regions are not in communication if the pressures or fluid contacts are different for the various regions, as this would lead to an unstable initialization and would also imply errors in the model description as implemented.","parameters":[{"index":1,"name":"NTEQUL","description":"A positive integer value that defines the number of equilibration regions entered using the EQLNUM keyword in the REGIONS section and the number of entries associated with the EQUIL keyword in the SOLUTION section.","units":{},"default":"1","value_type":"INT"},{"index":2,"name":"NPRSVD","description":"A positive integer value setting the number of pressure versus depth entries used by OPM Flow in determining equilibration parameters. Unless there is a requirement for a very fine equilibration this parameter should be defaulted.","units":{},"default":"100","value_type":"INT"},{"index":3,"name":"NDRXVD","description":"A positive integer value that defines the maximum number of depth entries in equilibration property versus depth tables (RSVD, RVVD, PBVD or PDVD etc.) as defined in the SOLUTION section.","units":{},"default":"20","value_type":"INT"},{"index":4,"name":"NTTRVD","description":"A positive integer that defines the maximum number of TVDP tables that describe the initial tracer concentration versus depth.","units":{},"default":"1","value_type":"INT"},{"index":5,"name":"NSTRVD","description":"A positive integer that defines the maximum number of depth entries in the TVDP tables as described in (4)","units":{},"default":"20","value_type":"INT"}],"example":"--\n-- MAX MAX RSVD TVDP TVDP\n-- EQLNUM DEPTH NODES TABLE NODES\nEQLDIMS\n9 1* 20 1* 1* /\nThe above example defines nine equilibration regions the default values for the remaining parameters on the EQLDIMS keyword.","expected_columns":5,"size_kind":"fixed","size_count":1},"EQLOPTS":{"name":"EQLOPTS","sections":["RUNSPEC"],"supported":false,"summary":"The EQLOPTS keyword defines the equilibration options by stating the character command to activate an option to be used for initializing the model. Multiple commands may be utilized to activate several equilibration options following the keyword.","parameters":[{"index":1,"name":"MOBILE","description":"A character string that activates the mobile fluid critical saturation end point correction. If the MOBILE command is stated then this option is activated. This option is not supported by OPM Flow but would change the results if supported so the simulation will be stopped. Therefore this character string should be omitted.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"QUIESC","description":"A character string that activates the initial quiescence option that modifies the equilibrium calculated phase pressures to ensure that a steady state solution is obtained. This options ensures that there is no flow potential between the grid blocks in a given region, which is the normal case when block-centered equilibration is used by setting BOINIT on the EQUIL keyword to zero in the SOLUTION section. If the QUIESC command is stated then this option is activated. This option is not supported by OPM Flow but would change the results if supported so the simulation will be stopped. Therefore this character string should be omitted.","units":{},"default":"None","value_type":"STRING"},{"index":3,"name":"THPRES","description":"A character string that activates the inter-region equilibration flow option. This option allows for a threshold pressure variable entered via the THPRES keyword to define a pressure which prevents flow between regions until the THPRES value between regions is exceeded. If the THPRES command is stated then this option is activated.","units":{},"default":"None","value_type":"STRING"},{"index":4,"name":"IRREVERS","description":"A character string that activates the irreversible inter-region equilibration flow option. This option can only be invoked if the THPRES command has been stated. The option allows for different THPRES values for different directions. If the IRREVERS command is stated then this option is activated. This option is not supported by OPM Flow but would change the results if supported so the simulation will be stopped. Therefore this character string should be omitted.","units":{},"default":"None","value_type":"STRING"}],"example":"--\n-- ACTIVATE EQUILIBRATION OPTIONS\n-- MOBILE END-POINT(MOBILE) STEADY STATE(QUIESC) THRESHOLD(THPRES)\n-- IRREVERSIBLE THRESHOLD(IRREVERS)\nEQLOPTS\n'THPRES' 'IRREVERS' /\nThe above example activates the threshold pressure option with different threshold pressure for different directions.","expected_columns":4,"size_kind":"fixed","size_count":1},"EXTRAPMS":{"name":"EXTRAPMS","sections":["RUNSPEC","GRID","PROPS","REGIONS","SOLUTION","SUMMARY","EDIT","SCHEDULE"],"supported":null,"summary":"The EXTRAPMS keyword activates extrapolation warning messages for when OPM Flow extrapolates the PVT or VFP tables. Frequent extrapolation warning messages should be investigated and resolved as this would indicate possible incorrect data and may result in the simulator extrapolating to unrealistic values.","parameters":[{"index":1,"name":"LEVEL","description":"","units":{},"default":"0","value_type":"INT"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"FAULTDIM":{"name":"FAULTDIM","sections":["RUNSPEC"],"supported":null,"summary":"The FAULTDIM keyword defines the maximum number of records (or segments) that can be entered with the FAULTS keyword. The FAULTS keyword defines the faults in the grid than can be used for setting (or re-setting) transmissibility barriers across the fault planes.","parameters":[{"index":1,"name":"MFSEGS","description":"A positive integer value that defines the maximum number of records (segments) for the FAULTS keyword.","units":{},"default":"0","value_type":"INT"}],"example":"--\n-- FAULT\n-- SEGMS\n--\nFAULTDIM\n10000 /\nThe above example defines the maximum number of records that can be entered using the FAULT keyword to be 10,000 segments.","expected_columns":1,"size_kind":"fixed","size_count":1},"FIELD":{"name":"FIELD","sections":["RUNSPEC"],"supported":null,"summary":"This keyword switches on the oil FIELD system of units for the model.","parameters":[],"example":"--\n-- SWITCH ON THE FIELD SYSTEM OF UNITS FOR BOTH INPUT AND OUTPUT\n--\nFIELD\nThe above example switches on the FIELD system of units for the model.","size_kind":"none","size_count":0},"FMTHMD":{"name":"FMTHMD","sections":["RUNSPEC"],"supported":false,"summary":"This keyword switches on formatted output for the History Match Gradient output file, for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section.","parameters":[],"example":"","size_kind":"none","size_count":0},"FMTIN":{"name":"FMTIN","sections":["RUNSPEC"],"supported":null,"summary":"This keyword switches on the Format Input Files option for all input files. Similar to the commercial simulator, OPM Flow has various options for reading various input files and writing the resulting OPM Flow output files as described in Table 5.14.","parameters":[],"example":"--\n-- SWITCH ON THE FORMAT INPUT FILES OPTION\n--\nFMTIN\nThe above example switches on the format input file option.\n| Process | Keyword | Description | Files |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|\n| Input | FMTIN ","size_kind":"none","size_count":0},"FMTOUT":{"name":"FMTOUT","sections":["RUNSPEC"],"supported":null,"summary":"This keyword switches on the Format Output Files option for all output files. Similar to the commercial simulator, OPM Flow has various options for reading various input files and writing the resulting OPM Flow output files as described in Table 5.15.","parameters":[],"example":"--\n-- SWITCH ON THE FORMAT OUTPUT FILES OPTION\n--\nFMTOUT\nThe above example switches on the format output file option.\n| Process | Keyword | Description | Files |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|\n| Input | FMTIN ","size_kind":"none","size_count":0},"FOAM":{"name":"FOAM","sections":["RUNSPEC"],"supported":null,"summary":"This keyword activates the foam phase and modeling option. The keyword will also invoke data input file checking to ensure that all the required foam phase input parameters are defined in the input deck. Note in the commercial simulator the FOAM phase and model can be used in conjunction with the POLYMER and SURFACT phases; this is not the case for OPM Flow. OPM Flow’s FOAM phase and model is a standalone implementation and cannot be used in conjunction with either the POLYMER or SURFACT phases.","parameters":[],"example":"--\n-- ACTIVATE THE FOAM PHASE IN THE MODEL\n--\nFOAM\nThe above example declares that the foam phase is active in the model.","size_kind":"none","size_count":0},"FORMFEED":{"name":"FORMFEED","sections":["RUNSPEC","GRID","EDIT","PROPS","REGIONS","SOLUTION","SUMMARY","SCHEDULE"],"supported":null,"summary":"The FORMFEED keyword defines the form-feed character, or carriage control character, for the output print (*.PRT) run summary (*.RSM) files. The keyword should be place at the very top of the input file.","parameters":[{"index":1,"name":"VALUE","description":"","units":{},"default":"1","value_type":"INT"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"FRICTION":{"name":"FRICTION","sections":["RUNSPEC"],"supported":false,"summary":"The FRICTION keyword activates the Wellbore Friction option and defines the maximum number of wellbore friction wells together with the maximum number of well branches.","parameters":[{"index":1,"name":"MXWELS","description":"A positive integer defining the maximum number of wellbore friction wells for this model.","units":{},"default":"0","value_type":"INT"},{"index":2,"name":"NWFRIB","description":"","units":{},"default":"1","value_type":"INT"},{"index":3,"name":"MXBRAN","description":"A positive integer defining the maximum number of branches per well. The default value of one implies a standard well with no branches.","units":{},"default":"1"}],"example":"--\n-- WELL BRANCH\n-- MXWELS MXBRAN\nFRICTION\n5 1 /\nThe above example defines the maximum number of wellbore friction wells to be five and the maximum number of branches set to one, for standard wells.","expected_columns":2,"size_kind":"fixed","size_count":1},"FULLIMP":{"name":"FULLIMP","sections":["RUNSPEC"],"supported":null,"summary":"The FULLIMP keyword activates the Fully Implicit Solution formulation and solution options. OPM Flow uses a different numerical scheme which makes this keyword redundant; hence, OPM Flow ignores this keyword. It is documented here for completeness. The keyword as the same function as the IMPLICIT keyword in the RUNSPEC section.","parameters":[],"example":"--\n-- ACTIVATES THE FULLY IMPLICIT SOLUTION OPTION\n--\nFULLIMP\nThe above example switches on the fully implicit solution option; however, this has no effect in OPM Flow input decks.","size_kind":"none","size_count":0},"GAS":{"name":"GAS","sections":["RUNSPEC"],"supported":null,"summary":"This keyword indicate that the gas phase is present in the model and must be used for oil-gas, gas-water, oil-water-gas input decks that contain the gas phase. The keyword will also invoke data input file checking to ensure that all the required gas phase input parameters are defined in the input deck.","parameters":[],"example":"--\n-- GAS PHASE IS PRESENT IN THE RUN\n--\nGAS\nThe above example declares that the gas phase is active in the model.","size_kind":"none","size_count":0},"GASFIELD":{"name":"GASFIELD","sections":["RUNSPEC"],"supported":false,"summary":"The GASFIELD keyword activates and specifies the Gas Field Operations options and determines if extended compressors are present in the run and if the expedited first pass DCQ calculation should be used.","parameters":[{"index":1,"name":"FLAG_COMP","description":"","units":{},"default":"NO","value_type":"STRING"},{"index":2,"name":"FLAG_IT","description":"","units":{},"default":"NO","value_type":"STRING"}],"example":"","expected_columns":2,"size_kind":"fixed","size_count":1},"GASWAT":{"name":"GASWAT","sections":["RUNSPEC"],"supported":null,"summary":"This keyword activates the two-phase Gas-Water model, as such it is equivalent to using both the GAS and WATER keywords in the RUNSPEC section..","parameters":[],"example":"-- ==============================================================================\n--\n-- RUNSPEC SECTION\n--\n-- ==============================================================================\nRUNSPEC\n--\n-- ACTIVATE CO2 STORAGE IN THE MODEL (OPM FLOW CO2 STORAGE KEYWORD)\n--\nCO2STORE\n--\n-- ACTIVATE COMPOSITIONAL MODELING FORMULATION (OPM FLOW KEYWORD)\n--\nCOMPS\n2 /\n--\n-- ACTIVATE GAS-WATER THE MODEL (OPM FLOW KEYWORD)\n--\nGASWAT\nThe above example declares that the run should use the Gas-Water model, together with the CO2STORE option, and with two components.\n| Note This is an OPM Flow keyword, and should not be confused with the more general version of the GASWAT keyword used in the commercial compositional simulator. |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"none","size_count":0},"GDIMS":{"name":"GDIMS","sections":["RUNSPEC"],"supported":false,"summary":"The GDIMS keyword activates the Instantaneous Gradient option and defines the maximum dimensions as used by the GWRTWCV keyword in the SCHEDULE section. The Instantaneous Gradient option calculates derivatives of solution quantities at the current time step with respect to variations in the variables at the current time step. This is different to Gradient option that calculates the derivatives of solution quantities at the current time step with respect to variations in the variables at the initial time step, that is a time equal to zero. Consequently, the Instantaneous Gradient option can be switched on and off by the GUPFREQ keyword in the SCHEDULE section, whereas the Gradient option cannot.","parameters":[{"index":1,"name":"MAX_NUM_GRAD_PARAMS","description":"","units":{},"default":"0","value_type":"INT"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"GIMODEL":{"name":"GIMODEL","sections":["RUNSPEC"],"supported":false,"summary":"This keyword, GIMODEL, activates the Gi Pseudo Compositional option for gas condensate and volatile oil fluids.","parameters":[],"example":"--\n-- ACTIVATE THE GI PSEUDO COMPOSITIONAL OPTION\n--\nGIMODEL\nThe above example switches on the Gi Pseudo Compositional option.","size_kind":"none","size_count":0},"GRAVDR":{"name":"GRAVDR","sections":["RUNSPEC"],"supported":false,"summary":"This keyword switches on gravity drainage and imbibition modeling between the matrix and the fracture grid blocks in dual porosity and dual permeability runs. Note that either DZMTRX or DZMTRXV keywords in the GRID section should be used to set the matrix vertical dimensions if this option is activated.","parameters":[],"example":"--\n-- ACTIVATE GRAVITY DRAINAGE AND IMBIBITION FOR DUAL POROSITY MODEL\n--\nGRAVDR\nThe above example switches on the gravity drainage and imbibition option for the run.","size_kind":"none","size_count":0},"GRAVDRB":{"name":"GRAVDRB","sections":["RUNSPEC"],"supported":false,"summary":"This keyword switches on vertical discretized gravity drainage and imbibition modeling between the matrix and the fracture grid blocks in dual porosity and dual permeability runs. Note that the geometry of the matrix sub-cells should be set to VERTICAL on the NMATOPS keyword in the GRID section if this option is activated.","parameters":[],"example":"--\n-- ACTIVATE VERTICAL DISCRETIZED GRAVITY DRAINAGE AND IMBIBITION\n--\nGRAVDRB\nThe above example switches on the vertical discretized gravity drainage and imbibition option for the run.","size_kind":"none","size_count":0},"GRAVDRM":{"name":"GRAVDRM","sections":["RUNSPEC"],"supported":false,"summary":"This keyword switches on the alternative gravity drainage and imbibition modeling between the matrix and the fracture grid blocks in dual porosity and dual permeability runs. Either the GRAVDRM or GRAVDR keywords should be used to activate this standard or alternative type of formulation.","parameters":[{"index":1,"name":"OPTION1","description":"A defined character string that sets the matrix flow in and out of the matrix block option, and should be set to one of the following: YES: oil flow is bi-directional, that is oil can flow into and out of the matrix block. NO: oil flow is uni-directional, that is oil can flow out of the matrix block.","units":{},"default":"YES","value_type":"STRING","options":["YES","NO"]}],"example":"--\n-- ACTIVATE ALTERNATIVE GRAVITY DRAINAGE AND IMBIBITION MODEL\n--\n-- MATRIX\n-- OPTION\nGRAVDRM\nYES /\nThe above example switches on the alternative gravity drainage and imbibition option for the run and sets oil flow to be bi-directional, that is oil can flow into and out of the matrix block.","expected_columns":1,"size_kind":"fixed","size_count":1},"GRIDOPTS":{"name":"GRIDOPTS","sections":["RUNSPEC"],"supported":null,"summary":"GRIDOPTS activates the negative directional dependent transmissibility multipliers option, defines the maximum number of MULTNUM regions and the number of PINCHNUM regions for the model.","parameters":[{"index":1,"name":"TRANMULT","description":"A character string that activates the negative directional dependent transmissibility multipliers option by setting TRANMULT to YES. Setting the value to NO switches off this option. OPM Flow uses a positive directional dependent transmissibility formulation to describe the flow between two cells, that is for cell (I, J, K) OPM Flow calculates the x face transmissibility between (I, J, K) and (I +1, J, K) cell face. Modification to the transmissibilities in this case is accomplished by the MULTX, MULTY and MULTZ keywords. Setting TRANMULT to YES invokes the option to use a negative directional dependent multiplier scheme using the MULTX-, MULTY- and MULTZ- keywords. In this case OPM Flow applies the x face transmissibility between (I - 1, J, K) and (I, J, K) cell face when using the MULTX-, MULTY- and MULTZ- keywords. Note that if TRANMULT is defaulted, and there are negative directional dependent multiplier keywords in the input deck, then OPM Flow will continue to process the MULTX-, MULTY- and MULTZ keywords correctly. Whereas, the commercial simulator will terminate with an error.","units":{},"default":"NO","value_type":"STRING"},{"index":2,"name":"NRMULT","description":"A positive integer value that defines the maximum number of MULTNUM regions for the MULTNUM array. The MULTNUM array is used in the GRID section to define various inter-region transmissibility regions in the model and NRMULT sets the maximum number of regions which is the maximum value of an element in the MULTNUM array. Inter-region MULTNUM transmissibility multipliers can be defined using the MULTREGT and regional pore volumes multipliers can be set using the MULTREGP keyword.","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"NRPINC","description":"A positive integer value that defines the maximum number of PINCHNUM regions for the PINCHNUM array. The PINCHNUM array is used in the GRID section to define various regions in the model and NRPINC sets the maximum of regions which is the maximum value of an element in the PINCHNUM array. Each regions criteria for setting the pinch out criteria is set by the PINCHREG keyword.","units":{},"default":"0","value_type":"INT"}],"example":"–-\n-- NEG MAX MAX\n-- MULTS MULTNUM PINCHNUM\nGRIDOPTS\nNO 9 1* /\nThe above example switches off the negative directional dependent transmissibility multipliers option and defines the maximum of MULTNUM regions to be nine,. The NRPINC parameter is defaulted which means there the maximum number of PINCHREG regions is zero.","expected_columns":3,"size_kind":"fixed","size_count":1},"H2SOL":{"name":"H2SOL","sections":["RUNSPEC"],"supported":null,"summary":"The H2SOL keyword activates dissolved hydrogen (H2) in the water phase, where H2 is represented by the SOLVENT pseudo component, using the simulator’s H2-Brine PVT model. This keyword is a compositional keyword in the commercial simulator but has been implemented in OPM Flow’s black-oil model.","parameters":[],"example":"The example shows the usage of H2SOL to model H2 injection in a live-oil reservoir. The RUNSPEC section includes the H2SOL keyword, which activates dissolved hydrogen (H2) in the water phase. The SOLVENT keyword activates the solvent pseudo component, which represents H2. The DISGASW keyword has been used to activate dissolved H2 in the brine.\n-- ==============================================================================\n--\n-- RUNSPEC SECTION\n--\n-- ==============================================================================\nRUNSPEC\n-- ------------------------------------------------------------------------------\n-- FLUID TYPES AND TRACER OPTIONS\n-- ------------------------------------------------------------------------------\n--\n-- ACTIVATE DISSOLVED H2 IN WATER (OPM FLOW KEYWORD)\n--\nH2SOL\n--\n-- SOLVENT PHASE IS PRESENT IN THE RUN\n--\nSOLVENT\n--\n-- DISSOLVED H2 IN WATER IS PRESENT IN THE RUN (OPM FLOW KEYWORD)\n--\nDISGASW\nThe second part of the example covers the additional data required in the PROPS section, in which the H2-gas miscible relative permeabilities are defined using the SSFN keyword. The initial temperature and salinity are defined using the RTEMP and SALINITY keywords. The oil and gas PVT properties should be defined in the normal way. No water PVT data is required.\n-- ==============================================================================\n--\n-- PROPS SECTION\n--\n-- ==============================================================================\nPROPS\n--\n-- RESERVOIR\n-- TEMPERATURE\n-- -----------\nRTEMP\n80.0 / RESERVOIR TEMP\n--\n-- SET SALINITY FOR ALL CELLS (OPM FLOW KEYWORD)\n--\nSALINITY\n0.7 /\n--\n-- SOLVENT RELATIVE PERMEABILITY TABLES\n--\nSSFN\n-- SGAS KRGT KRST\n-- FRAC\n-- -------- -------- --------\n0.0000 0.0000 0.0000\n1.0000 1.0000 1.0000 /\nThe third part of the example covers initialising the model in the SOLUTION section. Here the EQUIL keyword is used as normal to equilibrate the oil, gas and water phases, and the SSOL keyword to specify that there is initially no H2 present in the gas phase.\n-- ==============================================================================\n--\n-- SOLUTION SECTION\n--\n-- ==============================================================================\nSOLUTION\n--\n-- DATUM DATUM OWC PCOW GOC PCGO RS RV N E300 RVW\n-- DEPTH PRESS DEPTH ---- DEPTH ---- OPT OPT OPT OPT OPT\nEQUIL\n2000.0 200.0 2100.0 0.00 2000.0 0.00 1* 1* 1* 2* 1* /\n--\n-- DEFINE INITIAL EQUILIBRATION SOLVENT SAT VALUES FOR ALL CELLS IN THE MODEL\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nSSOL\n30000*0.0 /\nFor the summary section, the H2 storage quantity can be tracked using the solvent injection and production volumes as shown below.\n-- ==============================================================================\n--\n-- SUMMARY SECTION\n--\n-- ==============================================================================\nSUMMARY\n--\n-- EXPORT STANDARD SUMMARY VARIABLE VECTORS TO FILE\n--\nALL\n--\n-- FIELD SOLVENT INJECTION RATE\nFNIR\n--\n-- FIELD SOLVENT PRODUCTION RATE\nFNPR\n--\n-- FIELD SOLVENT INJECTION TOTAL\nFNIT\n--\n-- FIELD SOLVENT PRODUCTION TOTAL\nFNPT\nThe final part of the example covers the SCHEDULE section. The WSOLVENT keyword is used to specify the injected solvent fraction (in this case pure H2).\n-- ==============================================================================\n--\n-- SCHEDULE SECTION\n--\n-- ==============================================================================\nSCHEDULE\n--\n-- RESTART CONTROL BASIC = 4 (ALL=2, YEARLY=4, MONTHLY=5, TSTEP=6)\n--\nRPTRST\n'BASIC=1' 'ALLPROPS' /\n--\n-- DEFINE GAS INJECTION WELL SOLVENT FRACTION\n--\n-- WELL SOLVENT\n-- NAME FRACTION\n-- --------\nWSOLVENT\nGI01 1.0000 /\n/","size_kind":"none","size_count":0},"H2STORE":{"name":"H2STORE","sections":["RUNSPEC"],"supported":true,"summary":"The H2STORE keyword activates the hydrogen (H2) storage model for the run to account for both hydrogen and water phase solubility. H2STORE is similar to CO2STORE, which activates the carbon dioxide (CO2) storage model.","parameters":[],"example":"The first example shows the standard useage of H2STORE with Option (1) the Gas-Water model (GASWAT). Here we also activate the dissolved gas in water (DISGASW) and vaporized water in gas (VAPWAT) options.\n-- ==============================================================================\n--\n-- RUNSPEC SECTION\n--\n-- ==============================================================================\nRUNSPEC\n-- ------------------------------------------------------------------------------ -- FLUID TYPES AND TRACER OPTIONS\n-- ------------------------------------------------------------------------------\n--\n-- ACTIVATE H2 STORAGE IN THE MODEL (OPM FLOW H2 STORAGE KEYWORD)\n--\nH2STORE\n--\n-- ACTIVATE GAS-WATER THE MODEL (OPM FLOW KEYWORD)\n--\nGASWAT\n--\n-- DISSOLVED GAS IN WATER IS PRESENT IN THE RUN (OPM FLOW KEYWORD)\n--\nDISGASW\n--\n-- VAPORIZED WATER IN DRY/WET GAS IS PRESENT IN THE RUN (OPM FLOW KEYWORD)\n--\nVAPWAT\nThe second part of the example covers the data required for the PROPS section, in which the two-phase relative permeability functions are set using GSF and WSF keywords.\n-- ==============================================================================\n--\n-- PROPS SECTION\n--\n-- ==============================================================================\nPROPS\n--\n-- RESERVOIR\n-- TEMPERATURE\n-- -----------\nRTEMP\n80.0 / RESERVOIR TEMP\n--\n-- ROCK COMPRESSIBILITY\n--\n-- REFERENCE PRESSURE IS TAKEN FROM THE HCPV WEIGHTED RESERVOIR PRESSURE\n--\n-- REF PRES CF\n-- BARSA 1/BARSA\n-- -------- --------\nROCK\n200.0 5.0E-05 / ROCK COMPRESSIBILITY\n--\n-- GAS RELATIVE PERMEABILITY TABLES (OPM FLOW KEYWORD)\n--\nGSF\n-- SGAS KRG PCGW\n-- FRAC PSIA\n-- -------- -------- -------\n0.000 0.000 0.0\n0.080 0.001 0.0\n0.170 0.010 0.0\n0.350 0.050 0.0\n0.530 0.200 0.0\n0.620 0.350 0.0\n0.650 0.390 0.0\n0.710 0.560 0.0\n0.800 1.000 0.0 / TABLE NO. 01\n--\n-- WATER RELATIVE PERMEABILITY TABLES (OPM FLOW KEYWORD)\n--\nWSF\n-- SWAT KRW\n-- FRAC\n-- -------- --------\n0.200 0.0000\n0.400 0.1000\n0.800 0.5000\n1.000 1.0000 / TABLE NO. 01\n--\n-- SET SALINITY FOR ALL CELLS (OPM FLOW KEYWORD)\n--\nSALINITY\n0.7 /\nNo other data is required to define the fluid and rock properties in the PROPS section as the data is generated from internal analytic correlations and models by the simulator. Finally, note that units for salinity are to the 10-3, thus for metric units we have 10-3 x kg-M/kg.\nThe third part of the example covers initializing the model in the SOLUTION section. Here we use the EQUIL(EQLOPT6) parameter equal to one, to use table number one of the RVWVD keyword, in order to set the vaporized water versus depth distribution for the model.\n-- ==============================================================================\n--\n-- SOLUTION SECTION\n--\n-- ==============================================================================\nSOLUTION\n--\n-- SYSTEM IS SATURATED WITH WATER\n--\n-- DATUM DATUM OWC PCOW GOC PCGO RS RV N E300 RVW\n-- DEPTH PRESS DEPTH ---- DEPTH ---- OPT OPT OPT OPT OPT\nEQUIL\n2000.0 200.0 1800.0 0.00 1800.0 0.00 1* 1* 1* 2* 1 /\n--\n-- WATER VAPOR RATIO VS DEPTH (OPM FLOW KEYWORD)\n--\n-- DEPTH RVW\n-- STB/MSCF\n-- ------ --------\nRVWVD\n1000.0 0.000\n3000.0 0.000 / RVW VS DEPTH EQUIL REGN 01\nIn the SUMMARY section, the simulator supports summary vectors specific to CO2 storage (see Section 11.1.12 Option Specific Variables - CO2STORE/H2STORE Model) many of these can also be used for H2 storage including those shown below.\n-- ==============================================================================\n--\n-- SUMMARY SECTION\n--\n-- ==============================================================================\nSUMMARY\n--\n-- EXPORT STANDARD SUMMARY VARIABLE VECTORS TO FILE\n--\nALL\n--\n-- FIELD H2 DISOLVED IN WATER PHASE\nFWCD\n--\n-- FIELD H2 TRAPPED IN GAS PHASE\nFGCDI\n--\n-- FIELD H2 MOBILE IN GAS PHASE\nFGCDM\nThe final part of the example covers the SCHEDULE section. The standard WCONINJE keyword is then used to set the gas injection rate, in this case 100,000 sm3/day of H2.\n-- ======================","size_kind":"none","size_count":0},"HMDIMS":{"name":"HMDIMS","sections":["RUNSPEC"],"supported":false,"summary":"This keyword, HMDIMS, defines the maximum parameter dimensions for the History Match Gradient option.","parameters":[{"index":1,"name":"MAX_GRAD_REGIONS","description":"","units":{},"default":"0","value_type":"INT"},{"index":2,"name":"MAX_SUB_REGIONS","description":"","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"MAX_GRADS","description":"","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"MAX_FAULTS","description":"","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"MAX_AQUIFER_PARAMS","description":"","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"MAX_WELL_PARAMS","description":"","units":{},"default":"0","value_type":"INT"},{"index":7,"name":"UNUSED","description":"","units":{},"default":"0","value_type":"INT"},{"index":8,"name":"MAX_ROCK_GRAD_PARAMS","description":"","units":{},"default":"0","value_type":"INT"},{"index":9,"name":"MAX_WELL_CONN_PARAMS","description":"","units":{},"default":"0","value_type":"INT"}],"example":"","expected_columns":9,"size_kind":"fixed","size_count":1},"HYST":{"name":"HYST","sections":["RUNSPEC"],"supported":false,"summary":"The HYST keyword activates the hysteresis option, the keyword should be avoided and the hysteresis option should be enabled by the HYSER parameter on the SATOTPS keyword in the RUNSPEC section.","parameters":[],"example":"","size_kind":"none","size_count":0},"IMPES":{"name":"IMPES","sections":["RUNSPEC"],"supported":null,"summary":"The IMPES keyword activates the Implicit Pressure Explicit Saturation formulation and solution options, commonly know as IMPES. OPM Flow uses a different numerical scheme which makes this keyword redundant; hence, OPM Flow ignores this keyword. It is documented here for completeness.","parameters":[],"example":"--\n-- ACTIVATE THE IMPES SOLUTION OPTION\n--\nIMPES\nThe above example switches on the IMPES solution option; however, this has no effect in OPM Flow input decks.","size_kind":"none","size_count":0},"IMPLICIT":{"name":"IMPLICIT","sections":["RUNSPEC"],"supported":null,"summary":"The IMPLICIT keyword activates the Fully Implicit Solution formulation and solution options. OPM Flow uses a different numerical scheme which makes this keyword redundant; hence, OPM Flow ignores this keyword. It is documented here for completeness. The keyword as the same function as the FULLIMP keyword in the RUNSPEC section.","parameters":[],"example":"--\n-- ACTIVATES THE FULLY IMPLICIT SOLUTION OPTION\n--\nIMPLICIT\nThe above example switches on the fully implicit solution option; however, this has no effect in OPM Flow input decks.","size_kind":"none","size_count":0},"INCLUDE":{"name":"INCLUDE","sections":["RUNSPEC","GRID","EDIT","PROPS","REGIONS","SOLUTION","SUMMARY","SCHEDULE"],"supported":null,"summary":"The INCLUDE keyword informs OPM Flow to continue reading input data from the specified INCLUDE file. When the end of the INCLUDE file is reached, or the ENDINC keyword is encountered in the included file, input data is read from the next keyword in the current file.","parameters":[{"index":1,"name":"IncludeFile","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"INSPEC":{"name":"INSPEC","sections":["RUNSPEC"],"supported":false,"summary":"This keyword switches on the writing of the INIT Index file that specifies and defines the format and data type written to the *.INIT data file. The *.INIT data file contains the static data specified in the GRID, PROPS and REGIONS sections. For example, the PORO, PERM and NTG arrays from the GRID section. The data is used in post-processing software, for example OPM ResInsight, to visualize the static grid properties.","parameters":[],"example":"--\n-- ACTIVATE WRITING THE INIT INDEX FILE FOR POST-PROCESSING\n--\nINSPEC\nThe above example switches on the writing of the INIT Index file for post-processing in ResInsight.","size_kind":"none","size_count":0},"LAB":{"name":"LAB","sections":["RUNSPEC"],"supported":null,"summary":"This keyword switches on the LABORATORY system of units for the model.","parameters":[],"example":"--\n-- SWITCH ON THE LABORATORY SYSTEM OF UNITS FOR BOTH INPUT AND OUTPUT\n--\nLAB\nThe above example switches on the LABORATORY system of units for the model.","size_kind":"none","size_count":0},"LGR":{"name":"LGR","sections":["RUNSPEC"],"supported":null,"summary":"The LGR keyword defines the maximum dimensions and parameters for the Local Grid Refinement (“LGR”) option.","parameters":[{"index":1,"name":"MAXLGR","description":"A positive integer value that defines the maximum number of LGRs in the model.","units":{},"default":"0","value_type":"INT"},{"index":2,"name":"MAXCLS","description":"A positive integer value that defines the maximum number of grid blocks in all the LGRs.","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"MCOARS","description":"A positive integer value that defines the maximum number of amalgamated coarse grid blocks in the model.","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"MAMALG","description":"A positive integer value that defines the maximum number of LGR amalgamations in the model.","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"MXLALG","description":"A positive integer value that defines the maximum number of LGRs in any amalgamation in the model.","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"LSTACK","description":"A positive integer that defines the maximum number of previous search directions stored by the linear solver for the LGR. See the NSTACK keyword in the RUNSPEC section for a full description.","units":{},"default":"10","value_type":"INT"},{"index":7,"name":"INTOPT","description":"A character string set to either INTERP to activate the Quandalle87\n Quandalle, Philippe & Besset, P. (1985). Reduction of Grid Effects Due to Local Sub-Gridding in Simulations Using a Composite Grid. 10.2118/13527-MS. pressure correction, or NOINTERP to deactivate this option. The option applies bi-linear interpolation to the global cells surrounding an LGR in order to improve the accuracy of the flow calculations between the LGR and the host cells. Quandalle, Philippe & Besset, P. (1985). Reduction of Grid Effects Due to Local Sub-Gridding in Simulations Using a Composite Grid. 10.2118/13527-MS.","units":{},"default":"NOINTERP","value_type":"STRING"},{"index":8,"name":"NCHCOR","description":"A positive integer value that defines the maximum number of grid blocks within a coarsened grid that overlap parallel domain boundaries for when the Parallel option has been invoked by the PARALLEL keyword in the RUNSPEC section. OPM Flow uses a different numerical scheme which makes this parameter redundant, see section 2.2Running OPM Flow 2023-04 From The Command Lineon how to run OPM Flow in parallel mode.","units":{},"default":"0","value_type":"INT"}],"example":"--\n-- LOCAL GRID REFINEMENT DIMENSIONS AND PARAMETERS\n--\n-- LGR LGR LGR LGR LGR LGR LGR LGR\n-- MAXLGR MAXCLS MCOARS MAMALG MXLALG LSTACK INTOPT NCHCOR\nLGR\n10 1000 1* 1* 1* 1* INTERP 1* /\nThe above example sets the maximum number of LGRs to 10 and the maximum number of grid blocks a LGR may contain to 1,000, and that the Quandalle pressure correction should be used to improve the flow calculation.","expected_columns":8,"size_kind":"fixed","size_count":1},"LGRCOPY":{"name":"LGRCOPY","sections":["RUNSPEC","GRID","EDIT"],"supported":null,"summary":"The LGRCOPY keyword actives the Local Grid Refinement (“LGR”) Inheritance option that allows the LGR to inherit the properties of the global or host cell containing an LGR grid block when it is defined, as opposed to the normal process of applying this transform at the end of the GRID section. LGRCOPY can be used in the RUNSPEC, GRID and EDIT sections. If used in the RUNSPEC section then the option is applied to all LGRs defined in the input file, whereas if used in the GRID or EDIT sections the keyword must be placed inside a LGR definition section, that is between a CARFIN (Cartesian LGR grid) or RADFIN/RADFIN4 (radial LGR grid) keyword and an ENDFIN keyword. In the latter case inheritance is applied on an individual LGR basis.","parameters":[],"example":"The following example activates the LGR Inheritance option for all LGRs in the model.\n-- ==============================================================================\n--\n-- RUNSPEC SECTION\n--\n-- ==============================================================================\nRUNSPEC\n--\n-- ACTIVATE LOCAL GRID REFINEMENT INHERITANCE\n--\nLGRCOPY","size_kind":"none","size_count":0},"LICENSES":{"name":"LICENSES","sections":["RUNSPEC"],"supported":false,"summary":"This keyword defines the additional software licenses that are required to invoke various licensed options in the commercial simulator at the start of the run. The commercial simulator requests a license when keywords associated with a licensed option is encountered in the input deck, this may result in the license being unavailable at the time of request and after the simulation has been initiated, resulting in the run terminating. This keyword avoids this scenario by reserving the license at the start of the run.","parameters":[{"index":1,"name":"FEATURE","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"list"},"LIVEOIL":{"name":"LIVEOIL","sections":["RUNSPEC"],"supported":false,"summary":"This keyword activates oil, free and dissolved gas in the model and therefore makes the oil phase live oil88\n “Live” oil is oil that contains gas in solution, which is normally the case for most conventional oil reservoirs. However, for oil reservoirs classified as heavy oil reservoirs, the in situ dissolved gas may be negligible and oil would then be classified as gas-free oil which is commonly referred to as “dead” oil. in the black-oil formulation, and is equivalent to setting the phases present in the model to be oil, dissolved gas, gas and water phases. Note if water is present in the model this needs to be explicitly stated via the WATER keyword in the RUNSPEC section (see also the BLACKOIL and DEADOIL keywords in the RUNSPEC section). The keyword is used by the commercial simulator’s compositional THERMAL option to set the phases present in the model.","parameters":[],"example":"The following example activates the black-oil phases in the model.\n--\n-- ACTIVATE LIVE-OIL PHASE\n--\nLIVEOIL\nAlternatively one could explicitly declare the phases using the following keywords in the RUNSPEC section.\n--\n-- OIL PHASE IS PRESENT IN THE RUN\n--\nOIL\n--\n-- DISSOLVED GAS IN LIVE OIL IS PRESENT IN THE RUN\n--\nDISGAS\n--\n-- GAS PHASE IS PRESENT IN THE RUN\n--\nGAS\n--\n-- WATER PHASE IS PRESENT IN THE RUN\n--\nWATER\nThe above example switches on the oil, dissolved gas, gas and water phases in the model.","size_kind":"none","size_count":0},"LOAD":{"name":"LOAD","sections":["RUNSPEC"],"supported":false,"summary":"The LOAD keyword loads a previously generated SAVE file to enable a fast restart. A SAVE file contains all the data from a previous run’s RUNSPEC, GRID, EDIT, PROPS and REGIONS sections, and thus there is no need for the simulator to calculate various parameters, including grid block transmissibilities etc. This allows for the current run to restart quicker than a conventional restart run using the RESTART keyword in the SOLUTION section via a RESTART file (*.UNRST or *.FUNRST etc.). The keyword should be the first keyword in the input deck and the RUNSPEC, GRID, EDIT, PROPS and REGIONS sections should be deleted from the input deck.","parameters":[{"index":1,"name":"FILE","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"REPORT_STEP","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"NOSIM","description":"","units":{},"default":"SIM","value_type":"STRING"},{"index":4,"name":"FORMATTED","description":"","units":{},"default":"UNFORMATTED","value_type":"STRING"},{"index":5,"name":"REQUEST_SAVE_OUTPUT","description":"","units":{},"default":"NO","value_type":"STRING"}],"example":"","expected_columns":5,"size_kind":"fixed","size_count":1},"LOWSALT":{"name":"LOWSALT","sections":["RUNSPEC"],"supported":false,"summary":"This keyword, LOWSALT, activates the low salt brine phase for the Brine option and also activates the Brine option. See also the BRINE keyword in the RUNSPEC section.","parameters":[],"example":"--\n-- ACTIVATE THE LOW SALT BRINE PHASE FOR THE BRINE OPTION\n--\nLOWSALT\nThe above example declares that the low salt brine phase is active in the model for the Brine option.","size_kind":"none","size_count":0},"MEMORY":{"name":"MEMORY","sections":["RUNSPEC"],"supported":null,"summary":"This keyword defines the memory allocation for the run.","parameters":[{"index":1,"name":"UNUSED","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"THOUSANDS_CHAR8","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":2,"size_kind":"fixed","size_count":1},"MESSAGE":{"name":"MESSAGE","sections":["RUNSPEC","GRID","EDIT","PROPS","REGIONS","SOLUTION","SUMMARY","SCHEDULE"],"supported":null,"summary":"The MESSAGE keyword outputs a user message to the terminal, as well as to the print (*.PRT) and debug (*.DBG) files. Note this is different to the MESSAGES keyword, that defines OPM Flows message print limits and stop limits generated by the simulator.","parameters":[{"index":1,"name":"MessageText","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","size_kind":"fixed","size_count":1,"variadic_record":true},"MESSAGES":{"name":"MESSAGES","sections":["RUNSPEC","GRID","EDIT","PROPS","REGIONS","SOLUTION","SUMMARY","SCHEDULE"],"supported":null,"summary":"The MESSAGES keyword defines the print and stops levels for various messages. The “print limits” set the maximum number of messages that will be printed, after which no more messages will be printed and the “stop limits” terminate the run when these limits are exceeded. There are six levels of message that increase in severity from informative all the way to programming errors, as outlined in Table 4.5.","parameters":[{"index":1,"name":"MESSAGE_PRINT_LIMIT","description":"","units":{},"default":"1000000","value_type":"INT"},{"index":2,"name":"COMMENT_PRINT_LIMIT","description":"","units":{},"default":"1000000","value_type":"INT"},{"index":3,"name":"WARNING_PRINT_LIMIT","description":"","units":{},"default":"10000","value_type":"INT"},{"index":4,"name":"PROBLEM_PRINT_LIMIT","description":"","units":{},"default":"100","value_type":"INT"},{"index":5,"name":"ERROR_PRINT_LIMIT","description":"","units":{},"default":"100","value_type":"INT"},{"index":6,"name":"BUG_PRINT_LIMIT","description":"","units":{},"default":"100","value_type":"INT"},{"index":7,"name":"MESSAGE_STOP_LIMIT","description":"Not supported","units":{},"default":"1000000","value_type":"INT"},{"index":8,"name":"COMMENT_STOP_LIMIT","description":"Not supported","units":{},"default":"1000000","value_type":"INT"},{"index":9,"name":"WARNING_STOP_LIMIT","description":"Not supported","units":{},"default":"10000","value_type":"INT"},{"index":10,"name":"PROBLEM_STOP_LIMIT","description":"Not supported","units":{},"default":"100","value_type":"INT"},{"index":11,"name":"ERROR_STOP_LIMIT","description":"Not supported","units":{},"default":"10","value_type":"INT"},{"index":12,"name":"BUG_STOP_LIMIT","description":"Not supported","units":{},"default":"1","value_type":"INT"},{"index":13,"name":"GROUP_PRINT_LIMIT","description":"Not supported","units":{},"default":"10","value_type":"INT"}],"example":"","expected_columns":13,"size_kind":"fixed","size_count":1},"MESSSRVC":{"name":"MESSSRVC","sections":["RUNSPEC"],"supported":false,"summary":"The MESSSRVC keyword activates or deactivates output to the database message file (*.DBPRTX). The file contains all the messages from run in binary format and is used in some post-processing software to annotate production line plots from the run.","parameters":[{"index":1,"name":"PRODUCE_MESSAGE","description":"","units":{},"default":"ON","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"METRIC":{"name":"METRIC","sections":["RUNSPEC"],"supported":null,"summary":"This keyword switches on the METRIC system of units for the model.","parameters":[],"example":"--\n-- SWITCH ON THE METRIC SYSTEM OF UNITS FOR BOTH INPUT AND OUTPUT\n--\nMETRIC\nThe above example switches on the METRIC system of units for the model.","size_kind":"none","size_count":0},"MICP":{"name":"MICP","sections":["RUNSPEC"],"supported":null,"summary":"The MICP keyword activates the Microbially Induced Calcite Precipitation (“MICP”) model for the run. MICP is a new and sustainable technology which utilizes biochemical processes to create barriers by calcium carbonate cementation, the technology has the potential to be used for sealing leakage zones in geological formations. Further information on the mathematical model can be found in the open-access publications Landa-Marbán et al89\n Landa-Marbán, D., Tveit, S., Kumar, K., Gasda, S.E., 2021. Practical approaches to study microbially induced calcite precipitation at the eld scale. Int. J. Greenh. Gas Control 106, 103256. https://doi.org/10.1016/j.ijggc.2021.103256. and 90\n Landa-Marbán, D., Kumar, K., Tveit, S., Gasda, S.E., 2021. Numerical studies of CO2 leakage remediation by micp-based plugging technology. In: Røkke, N.A. and Knuutila, H.K. (Eds) Short Papers from the 11th International Trondheim CCS conference, ISBN: 978-82-536-1714-5, 284-290..","parameters":[],"example":"--\n-- ACTIVATE THE MICROBIAL INDUCED CALCITE PRECIPITATION MODEL\n--\nMICP\n--\n-- WATER PHASE IS PRESENT IN THE RUN\n--\nWATER\nThe above example declares that the MICP model is active for the run and activates the water phase for the MICP model. For a complete example of this model, see MICP.DATA.\n| Note This is an OPM Flow specific keyword used to investigate leakage remediation. The module requires that both the MICP and WATER keywords in the RUNSPEC to be active. |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"none","size_count":0},"MINNPCOL":{"name":"MINNPCOL","sections":["RUNSPEC"],"supported":null,"summary":"The MINNPCOL keyword defines the minimum number of Newton iterations within a time step where the well production and injection targets may be updated, after which the well targets will be frozen until the time step calculations have converged and the time step is complete.","parameters":[{"index":1,"name":"MINNPCOL","description":"A positive integer that defines the minimum number of Newton iterations within a timestep where well targets may be updated.","units":{},"default":"3","value_type":"INT"}],"example":"--\n-- DEFINE THE MIN NUMBER OF ITERATIONS TO UPDATE WELL FLOW TARGETS\n--\nMINNPCOL\n3 /\nThe above example sets the MINNPCOL value to its default value of three.\n| Note This is an OPM Flow specific keyword that sets the minimum number of Newton iterations, as opposed to the NUPCOL keyword that defines the maximum number of Newton iterations within a time step, after which well targets are frozen. |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":1,"size_kind":"fixed","size_count":1},"MISCIBLE":{"name":"MISCIBLE","sections":["RUNSPEC"],"supported":true,"summary":"The MISCIBLE keyword defines the options associated with the Todd-Longstaff91\n M. R. Todd and W. J Longstaff, The Development, Testing, and Application Of a Numerical Simulator for Predicting Miscible Flood Performance\". In: J. Petrol. Tech. 24.7 (1972), pages 874-882. mixing parameters used for when polymer flooding or CO2 EOR simulation cases are being run.","parameters":[{"index":1,"name":"NTMISC","description":"A positive integer value that declares the number miscible residual oil saturations versus water saturations tables for SORWMIS keyword and the number Todd-Longstaff mixing parameters entries on the TLMIXPAR keyword.","units":{},"default":"1","value_type":"INT"},{"index":2,"name":"NSMISC","description":"A positive integer value that sets the maximum number of entries (or rows) for each SORWMIS table defined by the SORWMIS keyword.","units":{},"default":"20","value_type":"INT"},{"index":3,"name":"MISOPT","description":"A character string that defines the numerical dispersion control options for the oil and gas relative permeability curves, set to either NONE or TWOPOINT: NONE – standard single point up streaming, that is using the immediate neighbor TWOPOINT – two-point up streaming, that is using the immediate neighbor plus one cell for better numerical dispersion control but with a higher computational cost. Only the default value of NONE is supported.","units":{},"default":"NONE","value_type":"STRING"}],"example":"--\n-- NTAB MAX UPSTRM\n-- NTMISC NSMISC MISOPT\nMISCIBLE\n1 20 NONE /\nThe above example defines the default values for the MISCIBLE keyword, that is one table with a maximum of 20 rows per table using the standard one cell upstream option.","expected_columns":3,"size_kind":"fixed","size_count":1},"MONITOR":{"name":"MONITOR","sections":["RUNSPEC","SUMMARY"],"supported":null,"summary":"The MONITOR keyword activates the writing out of the run time monitoring information used by post-processing graphics software to display run time information, for example the simulated production and injection rates and cumulative values. OPM Flow does not have this functionality.","parameters":[],"example":"--\n-- ACTIVATE MONITORING OUTPUT DATA AND FILES\n--\nMONITOR\nThe above example switches on the output required for run time monitoring required by post-processing graphics software to review the simulation results in real time as the run progresses; however, this has no effect in OPM Flow input decks.","size_kind":"none","size_count":0},"MSGFILE":{"name":"MSGFILE","sections":["RUNSPEC"],"supported":false,"summary":"MSGFILE keyword activates or deactivates the message file output used by pre- and post-processing software. Note that message file processing is not available in OPM Flow.","parameters":[{"index":1,"name":"MSGOPT","description":"A positive integer set to 0 for to deactivate message file output or 1 to activate message file output.","units":{},"default":"1","value_type":"INT"}],"example":"--\n-- OUTPUT\n-- OPTN\nMSGFILE\n0 /\nThe above example deactivates the message file output, but the keyword is ignored by OPM Flow.","expected_columns":1,"size_kind":"fixed","size_count":1},"MULTIN":{"name":"MULTIN","sections":["RUNSPEC"],"supported":null,"summary":"This keyword switches on the Multiple Input Files option for all input files. Similar to the commercial simulator, OPM Flow has various options for reading various input files and writing the resulting OPM Flow output files as described in Table 5.23.","parameters":[],"example":"--\n-- ACTIVATE THE MULTIPLE INPUT FILES OPTION\n--\nMULTIN\nThe above example switches on the multiple input file option.\n| Process | Keyword | Description | Files |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|\n| Input | FMTIN ","size_kind":"none","size_count":0},"MULTOUT":{"name":"MULTOUT","sections":["RUNSPEC"],"supported":null,"summary":"This keyword switches on the Multiple Output Files option for all output files. Similar to the commercial simulator, OPM Flow has various options for reading various input files and writing the resulting OPM Flow output files as described in Table 5.24.","parameters":[],"example":"--\n-- ACTIVATE THE MULTIPLE OUTPUT FILES OPTION\n--\nMULTOUT\nThe above example switches on the multiple output file option.\n| Process | Keyword | Description | Files |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|\n| Input | FMTIN ","size_kind":"none","size_count":0},"MULTOUTS":{"name":"MULTOUTS","sections":["RUNSPEC"],"supported":false,"summary":"This keyword switches on the Multiple Output Files option for SUMMARY files only, and overwrites the UNIFOUT keyword in the RUNSPEC section that activates the Unified Output Files option for all output files.","parameters":[],"example":"--\n-- ACTIVATE MULTIPLE OUTPUT SUMMARY FILES ONLY OPTION\n--\nMULTOUTS\nThe above example switches on the multiple output file option.","size_kind":"none","size_count":0},"MULTREAL":{"name":"MULTREAL","sections":["RUNSPEC"],"supported":false,"summary":"The MULTREAL keyword activates the commercial simulator’s Multi-Realization License option.","parameters":[{"index":1,"name":"SESSION_SPEC","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"STANDARD_LICENCE","description":"","units":{},"default":"YES","value_type":"STRING"}],"example":"","expected_columns":2,"size_kind":"fixed","size_count":1},"NETWORK":{"name":"NETWORK","sections":["RUNSPEC"],"supported":null,"summary":"This keyword activates the Extended Network option and defines the maximum number of nodes and links (branches) in the network. The Extended Network option is a different facility to the Standard Network facility, as such, this keyword should only be used if the former network is required for the run.","parameters":[{"index":1,"name":"NODMAX","description":"NODMAX is a positive integer that defines the maximum number of nodes in the Extended Network model.","units":{},"default":"None","value_type":"INT"},{"index":2,"name":"NBRMAX","description":"NBRMAX is a positive integer that defines the maximum number of links in the Extended Network model.","units":{},"default":"None","value_type":"INT"},{"index":3,"name":"NBCMAX","description":"NBCMAX is a positive integer that defines the maximum number of branches that can be connected to a node in the Extended Network model, used in the commercial compositional simulator. The parameter is ignored by OPM Flow and should be defaulted or set to the default value of 20.","units":{},"default":"20","value_type":"INT"}],"example":"--\n-- ACTIVATE THE EXTENDED NETWORK OPTION AND DEFINE PARAMETERS\n--\n-- MAX. MAX NOT\n-- NODE LINK USED\nNETWORK\n10 12 1* /\nIn the above example the maximum number of nodes is set equal to ten and the maximum number of links (or branches) is set equal to 12, for the Extended Network option.","expected_columns":3,"size_kind":"fixed","size_count":1},"NINEPOIN":{"name":"NINEPOIN","sections":["RUNSPEC"],"supported":false,"summary":"The NINEPOIN keyword activates the Nine-Point Discretization formulation for the whole grid. If the keyword is absent from the run then the conventional standard five-point discretization formulation is used for the model. The nine-point scheme is based on adding additional non-neighbor connections between the diagonal neighbors in the areal plane, in order to reduce grid orientation effects92\n Yanosik, J. L. and McCracken, T. A. “A Nine-Point, Finite-Difference Reservoir Simulator for Realistic Prediction of Adverse Mobility Ratio Displacements,” paper SPE 5734, Society of Petroleum Engineers Journal (1979) 19, No. 4, 253-262..","parameters":[],"example":"--\n-- ACTIVATE THE NINE-POINT DISCRETIZATION OPTION\n--\nNINEPOIN\nThe above example switches on the Nine-Point Discretization option for the whole grid.","size_kind":"none","size_count":0},"NMATRIX":{"name":"NMATRIX","sections":["RUNSPEC"],"supported":false,"summary":"The NMATRIX keyword activates the Discretized Matrix Dual Porosity option and specifies the number of sub-grid blocks in the actual matrix grid blocks. See also the NMATOPS keyword in the GRID section that defines various parameters for this option.","parameters":[{"index":1,"name":"NMATRIX","description":"A positive integer value that specifies the number of sub-grid blocks in the actual matrix grid blocks.","units":{},"default":"1","value_type":"INT"}],"example":"--\n-- SUB-GRIDS\n-- NMATRIX\nNMATRIX\n4 /\nThe above example activates the Discretized Matrix Dual Porosity option and specifies the number of sub-grid blocks in the actual matrix grid block to be four.","expected_columns":1,"size_kind":"fixed","size_count":1},"NNEWTF":{"name":"NNEWTF","sections":["SCHEDULE"],"supported":false,"summary":"This keyword activates the Non-Newtonian Fluid phase and model for when the polymer phase is present in the model, as indicated by the POLYMER keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"NTHRBL","description":"A positive integer that defines the maximum number of Herschel-Bulkley versus polymer concentration tables to be used with the polymer model, as entered via the FHERCHBL keyword in the PROPS section. The tables are allocated to different parts of the grid by the HBNUM keyword in the REGIONS section","units":{},"default":"NTPVT","value_type":"INT"},{"index":2,"name":"NLNHBL","description":"A positive integer that defines the maximum number of rows for each table entered by the FHERCHBL keyword in the PROPS section.","units":{},"default":"2","value_type":"INT"}],"example":"--\n-- MAX MAX\n-- NTHRBL NLNHBL\nNNEWTF\n3 5 /\nThe above example defines maximum number of Herschel-Bulkley tables to be three with a maximum number of rows for each table set to five.","expected_columns":2,"size_kind":"fixed","size_count":1},"NOCASC":{"name":"NOCASC","sections":["RUNSPEC"],"supported":null,"summary":"NOCASC keyword activates the linear solver tracer algorithm for single phase tracers.","parameters":[],"example":"--\n-- TRACER SOLVER OPTION\n--\nNOCASC\nThe above example switches on the linear solver tracer algorithm; however, this has no effect in OPM Flow input decks.","size_kind":"none","size_count":0},"NODPPM":{"name":"NODPPM","sections":["RUNSPEC","GRID"],"supported":false,"summary":"The NODPPM keyword deactivates the default behavior of multiplying the fracture porosity by the fracture permeability to calculate the effective fracture permeability in dual porosity and dual permeability runs. Either the DUALPORO or DUALPERM keywords in the RUNSPEC section must be declared in the input file in order to use this keyword. If the default calculation is switched off by this keyword, then the effective fracture permeability is taken to be those entered for the fracture using the PERMX, PERMY and PERMZ keywords in the GRID section. If the keyword is absent from the input deck, then the entered PERMX, PERMY and PERMZ arrays for the fractures are multiplied by fracture PORO array values in order to obtain the effective fracture permeability.","parameters":[],"example":"--\n-- DEACTIVATE FRACTURE POROSITY-PERMEABILITY CALCULATION\n--\nNODPPM\nThe above example switches off the default behavior of multiplying the fracture porosity by the fracture permeability to calculate the effective fracture permeability.","size_kind":"none","size_count":0},"NOECHO":{"name":"NOECHO","sections":["RUNSPEC","GRID","EDIT","PROPS","REGIONS","SOLUTION","SUMMARY","SCHEDULE"],"supported":null,"summary":"Turns off echoing of all the input files to the print file. Note by default echoing of the inputs files is active. but can subsequently be switched off by the NOECHO activation keyword.","parameters":[],"example":"","size_kind":"none","size_count":0},"NOHYST":{"name":"NOHYST","sections":["RUNSPEC"],"supported":false,"summary":"The NOHYST keyword deactivates the Hysteresis option and informs the simulator to ignore the IMBNUM array in the REGIONS section.","parameters":[],"example":"--\n-- DEACTIVATE THE HYSTERESIS OPTION\n--\nNOHYST\nThe above example switches off the default behavior of multiplying the fracture porosity by the fracture permeability to calculate the effective fracture permeability.","size_kind":"none","size_count":0},"NOINSPEC":{"name":"NOINSPEC","sections":["RUNSPEC"],"supported":null,"summary":"The NOINSPEC keyword deactivates the writing out of the INIT index file (*.INSPEC). The initialization data (or static data) is written out to two files one file contains the data, *.INIT, and the second file contains an index of the data (*.INSPEC) stored in the *.INIT file. This functionality is redundant as most post-processing software require the *.INSPEC file to load the *.INIT data set.","parameters":[],"example":"--\n-- DEACTIVATE OUTPUT OF THE INIT INDEX FILE *.INSPEC\n--\nNOINSPEC\nThe above example switches off the writing of the INIT index file (*.INSPEC); however, this has no effect in OPM Flow input decks.","size_kind":"none","size_count":0},"NOMONITO":{"name":"NOMONITO","sections":["RUNSPEC","SUMMARY"],"supported":null,"summary":"The NOMONITO keyword deactivates the writing out of the run time monitoring information used by post-processing graphics software to display run time information, for example the simulated production and injection rates and cumulative values. OPM Flow does not have this functionality.","parameters":[],"example":"--\n-- DEACTIVATE MONITORING OUTPUT DATA AND FILES\n--\nNOMONITO\nThe above example switches off the output required for run time monitoring required by post-processing graphics software to review the simulation results in real time as the run progresses; however, this has no effect in OPM Flow input decks.","size_kind":"none","size_count":0},"NONNC":{"name":"NONNC","sections":["RUNSPEC"],"supported":null,"summary":"The NONNC keyword deactivates non-neighbor connections (“NNCs”) in the current run. NNCs create off-diagonal elements in the Jacobi matrix that impact the numerical efficiency of the solution algorithms, and thus if the run does not contain NNCs then there is the potential for greater computation efficiency. Unfortunately, nearly all models, except for the most simple models, generate NNCs via for example:","parameters":[],"example":"--\n-- DEACTIVATE NON-NEIGHBOR CONNECTIONS\n--\nNONNC\nThe above example switches off the NNCs.","size_kind":"none","size_count":0},"NORSSPEC":{"name":"NORSSPEC","sections":["RUNSPEC"],"supported":null,"summary":"The NORSSPEC keyword deactivates the writing out of the RESTART index file (*.RSSPEC). The restart data (pressure, saturations etc. through time for each active cell) are written out to two files one file contains the data, *.UNRST for example, and the second file contains an index of the data (*.RSSPEC) stored in the *.UNRST file. This functionality is redundant as most post-processing software require the *.RSSPEC file to load the *.UNRST data set.","parameters":[],"example":"--\n-- DEACTIVATE OUTPUT OF THE RESTART INDEX FILE *.RSSPEC\n--\nNORSSPEC\nThe above example switches off the writing of the restart index file (*.RSSPEC); however, this has no effect in OPM Flow input decks.","size_kind":"none","size_count":0},"NOSIM":{"name":"NOSIM","sections":["RUNSPEC","SCHEDULE"],"supported":null,"summary":"NOSIM switches the mode of OPM Flow to data input checking mode. In this mode the input file is read and all messages and print instructions are sent to the respective output files. The SCHEDULE section is read but the simulation is not performed.","parameters":[],"example":"The example below switches OPM Flow to no simulation mode for data checking of the input deck.\n--\n-- SWITCH NO SIMULATION MODE FOR DATA CHECKING COMMENT OUT TO RUN THE MODEL\n--\nNOSIM\nAnd the next example shows how to commented out the NOSIM activation keyword so that the simulation will proceed.\n--\n-- SWITCH NO SIMULATION MODE FOR DATA CHECKING COMMENT OUT TO RUN THE MODEL\n--\n-- NOSIM\nNote\nSimulation input decks are complex and are therefore prone to typing errors, thus before submitting a run that will take over 15 minutes or so, it is a good idea to run the model with the NOSIM option. If no errors are found then the NOSIM keyword should be commented out by placing “--” before the keyword, and then re-running the model.\nAlternatively, one could use OPMRUN to run all the jobs in the queue in NOSIM mode and have the software re-run jobs in simulation mode if there are no errors.\n| Note Simulation input decks are complex and are therefore prone to typing errors, thus before submitting a run that will take over 15 minutes or so, it is a good idea to run the model with the NOSIM option. If no errors are found then the NOSIM keyword should be commented out by placing “--” before the keyword, and then re-running the model. Alternatively, one could use OPMRUN to run all the jobs in the queue in NOSIM mode and have the software re-run jobs in simulation mode if there are no errors. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"none","size_count":0},"NOWARN":{"name":"NOWARN","sections":["RUNSPEC","GRID","EDIT","PROPS","REGIONS","SOLUTION","SUMMARY","SCHEDULE"],"supported":null,"summary":"Turns off warning messages to be printed to the print file; note that this keyword is deactivated by default and can subsequently be switched off by the WARN activation keyword. The warning messages may be turned on and off using keywords WARN and NOWARN.","parameters":[],"example":"","size_kind":"none","size_count":0},"NRSOUT":{"name":"NRSOUT","sections":["RUNSPEC"],"supported":false,"summary":"The NRSOUT keyword specifies the maximum number of elements that can be written to the RESTART file at each reporting time step.","parameters":[{"index":1,"name":"NRSOUT","description":"A positive integer value that specifies the maximum number of elements that can be written to the RESTART file at each reporting time step.","units":{},"default":"3600","value_type":"INT"}],"example":"--\n-- MAX\n-- NRSOUT\nNRSOUT\n6000 /\nThe above example sets the maximum number of elements that can be written to the RESTART file at each reporting time step to 6000.","expected_columns":1,"size_kind":"fixed","size_count":1},"NSTACK":{"name":"NSTACK","sections":["RUNSPEC","SCHEDULE"],"supported":false,"summary":"The NSTACK keyword defines the maximum number of previous search directions stored by the linear solver. Increasing the value of NSTACK may improve the efficiency of the solver on difficult problems, but will increase the memory requirements of the simulator. The default value of 10 should be sufficient for most problems; however, if OPM Flow is having issues with the convergence of the linear questions then increasing NSTACK and the value of LITMAX on the TUNING keyword may improve performance.","parameters":[{"index":1,"name":"NSTACK","description":"A positive integer that defines the maximum number of previous search directions stored by the linear solver.","units":{},"default":"10","value_type":"INT"}],"example":"--\n-- SET STACK SIZE FOR LINEAR SOLVER\n--\nNSTACK\n30 /\nThe above example sets maximum number of previous search directions stored by the linear solver to 30, this has no effect in OPM Flow input decks.\nNote\nIf the run is suffering from linear convergence problems, then check the data first for any data issues before manipulating the numerical control parameters. For example, if OPM Flow has written some WARNING messages with respect to end-point scaling, etc., then resolve these messages first before adjusting the numerical controls.\n| Note If the run is suffering from linear convergence problems, then check the data first for any data issues before manipulating the numerical control parameters. For example, if OPM Flow has written some WARNING messages with respect to end-point scaling, etc., then resolve these messages first before adjusting the numerical controls. |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":1,"size_kind":"fixed","size_count":1},"NUMRES":{"name":"NUMRES","sections":["RUNSPEC"],"supported":null,"summary":"The NUMRES keyword defines the number of reservoir grids (COORD data sets) that the simulator should process. OPM Flow currently only supports a single reservoir grid.","parameters":[{"index":1,"name":"NUMRES","description":"A positive integer that defines the number of COORD data sets to be processed by OPM Flow. OPM Flow currently only supports a single reservoir grid and so this item should be defaulted (1*) or set to one.","units":{},"default":"1","value_type":"INT"}],"example":"--\n-- DEFINE THE NUMBER OF RESERVOIR GRIDS (COORD DATA SETS)\n--\nNUMRES\n1 /\nThe above example sets the maximum number of COORD data sets to be processed to one.","expected_columns":1,"size_kind":"fixed","size_count":1},"NUPCOL":{"name":"NUPCOL","sections":["RUNSPEC","SCHEDULE"],"supported":null,"summary":"The NUPCOL keyword defines the maximum number of Newton iterations within a time step that may be used to update the well production and injection targets, after which the well targets will be frozen until the time step calculations have converged and the time step is complete.","parameters":[{"index":1,"name":"NUPCOL","description":"A positive integer that defines the maximum number of Newton iterations used to update well targets within a time step.","units":{},"default":"3","value_type":"INT"}],"example":"--\n-- DEFINE THE MAX NUMBER OF ITERATIONS TO UPDATE WELL FLOW TARGETS\n--\nNUPCOL\n3 /\nThe above example sets the NUPCOL value to its default value of 3.","expected_columns":1,"size_kind":"fixed","size_count":1},"OIL":{"name":"OIL","sections":["RUNSPEC"],"supported":null,"summary":"This keyword indicates that the oil phase is present in the model and must be used for oil-gas, oil-water, oil-water-gas input decks that contain the oil phase. The keyword will also invoke data input file checking to ensure that all the required oil phase input parameters are defined in the input deck.","parameters":[],"example":"--\n-- OIL PHASE IS PRESENT IN THE RUN\n--\nOIL\nThe above example declares that the oil phase is active in the model.","size_kind":"none","size_count":0},"OPTIONS":{"name":"OPTIONS","sections":["RUNSPEC","SCHEDULE"],"supported":true,"summary":"The OPTIONS keyword activates various program options in the commercial simulator. Currently, none of the options available in the commercial simulator are implemented in OPM Flow, and it is unlikely that this keyword will be supported in the future releases of OPM Flow.","parameters":[{"index":1,"name":"ITEM1","description":"","units":{},"default":"0","value_type":"INT"},{"index":2,"name":"ITEM2","description":"","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"ITEM3","description":"","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"ITEM4","description":"","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"ITEM5","description":"","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"ITEM6","description":"","units":{},"default":"0","value_type":"INT"},{"index":7,"name":"ITEM7","description":"","units":{},"default":"0","value_type":"INT"},{"index":8,"name":"ITEM8","description":"","units":{},"default":"0","value_type":"INT"},{"index":9,"name":"ITEM9","description":"","units":{},"default":"0","value_type":"INT"},{"index":10,"name":"ITEM10","description":"","units":{},"default":"0","value_type":"INT"},{"index":11,"name":"ITEM11","description":"","units":{},"default":"0","value_type":"INT"},{"index":12,"name":"ITEM12","description":"","units":{},"default":"0","value_type":"INT"},{"index":13,"name":"ITEM13","description":"","units":{},"default":"0","value_type":"INT"},{"index":14,"name":"ITEM14","description":"","units":{},"default":"0","value_type":"INT"},{"index":15,"name":"ITEM15","description":"","units":{},"default":"0","value_type":"INT"},{"index":16,"name":"ITEM16","description":"","units":{},"default":"0","value_type":"INT"},{"index":17,"name":"ITEM17","description":"","units":{},"default":"0","value_type":"INT"},{"index":18,"name":"ITEM18","description":"","units":{},"default":"0","value_type":"INT"},{"index":19,"name":"ITEM19","description":"","units":{},"default":"0","value_type":"INT"},{"index":20,"name":"ITEM20","description":"","units":{},"default":"0","value_type":"INT"},{"index":21,"name":"ITEM21","description":"","units":{},"default":"0","value_type":"INT"},{"index":22,"name":"ITEM22","description":"","units":{},"default":"0","value_type":"INT"},{"index":23,"name":"ITEM23","description":"","units":{},"default":"0","value_type":"INT"},{"index":24,"name":"ITEM24","description":"","units":{},"default":"0","value_type":"INT"},{"index":25,"name":"ITEM25","description":"","units":{},"default":"0","value_type":"INT"},{"index":26,"name":"ITEM26","description":"","units":{},"default":"0","value_type":"INT"},{"index":27,"name":"ITEM27","description":"","units":{},"default":"0","value_type":"INT"},{"index":28,"name":"ITEM28","description":"","units":{},"default":"0","value_type":"INT"},{"index":29,"name":"ITEM29","description":"","units":{},"default":"0","value_type":"INT"},{"index":30,"name":"ITEM30","description":"","units":{},"default":"0","value_type":"INT"},{"index":31,"name":"ITEM31","description":"","units":{},"default":"0","value_type":"INT"},{"index":32,"name":"ITEM32","description":"","units":{},"default":"0","value_type":"INT"},{"index":33,"name":"ITEM33","description":"","units":{},"default":"0","value_type":"INT"},{"index":34,"name":"ITEM34","description":"","units":{},"default":"0","value_type":"INT"},{"index":35,"name":"ITEM35","description":"","units":{},"default":"0","value_type":"INT"},{"index":36,"name":"ITEM36","description":"","units":{},"default":"0","value_type":"INT"},{"index":37,"name":"ITEM37","description":"","units":{},"default":"0","value_type":"INT"},{"index":38,"name":"ITEM38","description":"","units":{},"default":"0","value_type":"INT"},{"index":39,"name":"ITEM39","description":"","units":{},"default":"0","value_type":"INT"},{"index":40,"name":"ITEM40","description":"","units":{},"default":"0","value_type":"INT"},{"index":41,"name":"ITEM41","description":"","units":{},"default":"0","value_type":"INT"},{"index":42,"name":"ITEM42","description":"","units":{},"default":"0","value_type":"INT"},{"index":43,"name":"ITEM43","description":"","units":{},"default":"0","value_type":"INT"},{"index":44,"name":"ITEM44","description":"","units":{},"default":"0","value_type":"INT"},{"index":45,"name":"ITEM45","description":"","units":{},"default":"0","value_type":"INT"},{"index":46,"name":"ITEM46","description":"","units":{},"default":"0","value_type":"INT"},{"index":47,"name":"ITEM47","description":"","units":{},"default":"0","value_type":"INT"},{"index":48,"name":"ITEM48","description":"","units":{},"default":"0","value_type":"INT"},{"index":49,"name":"ITEM49","description":"","units":{},"default":"0","value_type":"INT"},{"index":50,"name":"ITEM50","description":"","units":{},"default":"0","value_type":"INT"},{"index":51,"name":"ITEM51","description":"","units":{},"default":"0","value_type":"INT"},{"index":52,"name":"ITEM52","description":"","units":{},"default":"0","value_type":"INT"},{"index":53,"name":"ITEM53","description":"","units":{},"default":"0","value_type":"INT"},{"index":54,"name":"ITEM54","description":"","units":{},"default":"0","value_type":"INT"},{"index":55,"name":"ITEM55","description":"","units":{},"default":"0","value_type":"INT"},{"index":56,"name":"ITEM56","description":"","units":{},"default":"0","value_type":"INT"},{"index":57,"name":"ITEM57","description":"","units":{},"default":"0","value_type":"INT"},{"index":58,"name":"ITEM58","description":"","units":{},"default":"0","value_type":"INT"},{"index":59,"name":"ITEM59","description":"","units":{},"default":"0","value_type":"INT"},{"index":60,"name":"ITEM60","description":"","units":{},"default":"0","value_type":"INT"},{"index":61,"name":"ITEM61","description":"","units":{},"default":"0","value_type":"INT"},{"index":62,"name":"ITEM62","description":"","units":{},"default":"0","value_type":"INT"},{"index":63,"name":"ITEM63","description":"","units":{},"default":"0","value_type":"INT"},{"index":64,"name":"ITEM64","description":"","units":{},"default":"0","value_type":"INT"},{"index":65,"name":"ITEM65","description":"","units":{},"default":"0","value_type":"INT"},{"index":66,"name":"ITEM66","description":"","units":{},"default":"0","value_type":"INT"},{"index":67,"name":"ITEM67","description":"","units":{},"default":"0","value_type":"INT"},{"index":68,"name":"ITEM68","description":"","units":{},"default":"0","value_type":"INT"},{"index":69,"name":"ITEM69","description":"","units":{},"default":"0","value_type":"INT"},{"index":70,"name":"ITEM70","description":"","units":{},"default":"0","value_type":"INT"},{"index":71,"name":"ITEM71","description":"","units":{},"default":"0","value_type":"INT"},{"index":72,"name":"ITEM72","description":"","units":{},"default":"0","value_type":"INT"},{"index":73,"name":"ITEM73","description":"","units":{},"default":"0","value_type":"INT"},{"index":74,"name":"ITEM74","description":"","units":{},"default":"0","value_type":"INT"},{"index":75,"name":"ITEM75","description":"","units":{},"default":"0","value_type":"INT"},{"index":76,"name":"ITEM76","description":"","units":{},"default":"0","value_type":"INT"},{"index":77,"name":"ITEM77","description":"","units":{},"default":"0","value_type":"INT"},{"index":78,"name":"ITEM78","description":"","units":{},"default":"0","value_type":"INT"},{"index":79,"name":"ITEM79","description":"","units":{},"default":"0","value_type":"INT"},{"index":80,"name":"ITEM80","description":"","units":{},"default":"0","value_type":"INT"},{"index":81,"name":"ITEM81","description":"","units":{},"default":"0","value_type":"INT"},{"index":82,"name":"ITEM82","description":"","units":{},"default":"0","value_type":"INT"},{"index":83,"name":"ITEM83","description":"","units":{},"default":"0","value_type":"INT"},{"index":84,"name":"ITEM84","description":"","units":{},"default":"0","value_type":"INT"},{"index":85,"name":"ITEM85","description":"","units":{},"default":"0","value_type":"INT"},{"index":86,"name":"ITEM86","description":"","units":{},"default":"0","value_type":"INT"},{"index":87,"name":"ITEM87","description":"","units":{},"default":"0","value_type":"INT"},{"index":88,"name":"ITEM88","description":"","units":{},"default":"0","value_type":"INT"},{"index":89,"name":"ITEM89","description":"","units":{},"default":"0","value_type":"INT"},{"index":90,"name":"ITEM90","description":"","units":{},"default":"0","value_type":"INT"},{"index":91,"name":"ITEM91","description":"","units":{},"default":"0","value_type":"INT"},{"index":92,"name":"ITEM92","description":"","units":{},"default":"0","value_type":"INT"},{"index":93,"name":"ITEM93","description":"","units":{},"default":"0","value_type":"INT"},{"index":94,"name":"ITEM94","description":"","units":{},"default":"0","value_type":"INT"},{"index":95,"name":"ITEM95","description":"","units":{},"default":"0","value_type":"INT"},{"index":96,"name":"ITEM96","description":"","units":{},"default":"0","value_type":"INT"},{"index":97,"name":"ITEM97","description":"","units":{},"default":"0","value_type":"INT"},{"index":98,"name":"ITEM98","description":"","units":{},"default":"0","value_type":"INT"},{"index":99,"name":"ITEM99","description":"","units":{},"default":"0","value_type":"INT"},{"index":100,"name":"ITEM100","description":"","units":{},"default":"0","value_type":"INT"},{"index":101,"name":"ITEM101","description":"","units":{},"default":"0","value_type":"INT"},{"index":102,"name":"ITEM102","description":"","units":{},"default":"0","value_type":"INT"},{"index":103,"name":"ITEM103","description":"","units":{},"default":"0","value_type":"INT"},{"index":104,"name":"ITEM104","description":"","units":{},"default":"0","value_type":"INT"},{"index":105,"name":"ITEM105","description":"","units":{},"default":"0","value_type":"INT"},{"index":106,"name":"ITEM106","description":"","units":{},"default":"0","value_type":"INT"},{"index":107,"name":"ITEM107","description":"","units":{},"default":"0","value_type":"INT"},{"index":108,"name":"ITEM108","description":"","units":{},"default":"0","value_type":"INT"},{"index":109,"name":"ITEM109","description":"","units":{},"default":"0","value_type":"INT"},{"index":110,"name":"ITEM110","description":"","units":{},"default":"0","value_type":"INT"},{"index":111,"name":"ITEM111","description":"","units":{},"default":"0","value_type":"INT"},{"index":112,"name":"ITEM112","description":"","units":{},"default":"0","value_type":"INT"},{"index":113,"name":"ITEM113","description":"","units":{},"default":"0","value_type":"INT"},{"index":114,"name":"ITEM114","description":"","units":{},"default":"0","value_type":"INT"},{"index":115,"name":"ITEM115","description":"","units":{},"default":"0","value_type":"INT"},{"index":116,"name":"ITEM116","description":"","units":{},"default":"0","value_type":"INT"},{"index":117,"name":"ITEM117","description":"","units":{},"default":"0","value_type":"INT"},{"index":118,"name":"ITEM118","description":"","units":{},"default":"0","value_type":"INT"},{"index":119,"name":"ITEM119","description":"","units":{},"default":"0","value_type":"INT"},{"index":120,"name":"ITEM120","description":"","units":{},"default":"0","value_type":"INT"},{"index":121,"name":"ITEM121","description":"","units":{},"default":"0","value_type":"INT"},{"index":122,"name":"ITEM122","description":"","units":{},"default":"0","value_type":"INT"},{"index":123,"name":"ITEM123","description":"","units":{},"default":"0","value_type":"INT"},{"index":124,"name":"ITEM124","description":"","units":{},"default":"0","value_type":"INT"},{"index":125,"name":"ITEM125","description":"","units":{},"default":"0","value_type":"INT"},{"index":126,"name":"ITEM126","description":"","units":{},"default":"0","value_type":"INT"},{"index":127,"name":"ITEM127","description":"","units":{},"default":"0","value_type":"INT"},{"index":128,"name":"ITEM128","description":"","units":{},"default":"0","value_type":"INT"},{"index":129,"name":"ITEM129","description":"","units":{},"default":"0","value_type":"INT"},{"index":130,"name":"ITEM130","description":"","units":{},"default":"0","value_type":"INT"},{"index":131,"name":"ITEM131","description":"","units":{},"default":"0","value_type":"INT"},{"index":132,"name":"ITEM132","description":"","units":{},"default":"0","value_type":"INT"},{"index":133,"name":"ITEM133","description":"","units":{},"default":"0","value_type":"INT"},{"index":134,"name":"ITEM134","description":"","units":{},"default":"0","value_type":"INT"},{"index":135,"name":"ITEM135","description":"","units":{},"default":"0","value_type":"INT"},{"index":136,"name":"ITEM136","description":"","units":{},"default":"0","value_type":"INT"},{"index":137,"name":"ITEM137","description":"","units":{},"default":"0","value_type":"INT"},{"index":138,"name":"ITEM138","description":"","units":{},"default":"0","value_type":"INT"},{"index":139,"name":"ITEM139","description":"","units":{},"default":"0","value_type":"INT"},{"index":140,"name":"ITEM140","description":"","units":{},"default":"0","value_type":"INT"},{"index":141,"name":"ITEM141","description":"","units":{},"default":"0","value_type":"INT"},{"index":142,"name":"ITEM142","description":"","units":{},"default":"0","value_type":"INT"},{"index":143,"name":"ITEM143","description":"","units":{},"default":"0","value_type":"INT"},{"index":144,"name":"ITEM144","description":"","units":{},"default":"0","value_type":"INT"},{"index":145,"name":"ITEM145","description":"","units":{},"default":"0","value_type":"INT"},{"index":146,"name":"ITEM146","description":"","units":{},"default":"0","value_type":"INT"},{"index":147,"name":"ITEM147","description":"","units":{},"default":"0","value_type":"INT"},{"index":148,"name":"ITEM148","description":"","units":{},"default":"0","value_type":"INT"},{"index":149,"name":"ITEM149","description":"","units":{},"default":"0","value_type":"INT"},{"index":150,"name":"ITEM150","description":"","units":{},"default":"0","value_type":"INT"},{"index":151,"name":"ITEM151","description":"","units":{},"default":"0","value_type":"INT"},{"index":152,"name":"ITEM152","description":"","units":{},"default":"0","value_type":"INT"},{"index":153,"name":"ITEM153","description":"","units":{},"default":"0","value_type":"INT"},{"index":154,"name":"ITEM154","description":"","units":{},"default":"0","value_type":"INT"},{"index":155,"name":"ITEM155","description":"","units":{},"default":"0","value_type":"INT"},{"index":156,"name":"ITEM156","description":"","units":{},"default":"0","value_type":"INT"},{"index":157,"name":"ITEM157","description":"","units":{},"default":"0","value_type":"INT"},{"index":158,"name":"ITEM158","description":"","units":{},"default":"0","value_type":"INT"},{"index":159,"name":"ITEM159","description":"","units":{},"default":"0","value_type":"INT"},{"index":160,"name":"ITEM160","description":"","units":{},"default":"0","value_type":"INT"},{"index":161,"name":"ITEM161","description":"","units":{},"default":"0","value_type":"INT"},{"index":162,"name":"ITEM162","description":"","units":{},"default":"0","value_type":"INT"},{"index":163,"name":"ITEM163","description":"","units":{},"default":"0","value_type":"INT"},{"index":164,"name":"ITEM164","description":"","units":{},"default":"0","value_type":"INT"},{"index":165,"name":"ITEM165","description":"","units":{},"default":"0","value_type":"INT"},{"index":166,"name":"ITEM166","description":"","units":{},"default":"0","value_type":"INT"},{"index":167,"name":"ITEM167","description":"","units":{},"default":"0","value_type":"INT"},{"index":168,"name":"ITEM168","description":"","units":{},"default":"0","value_type":"INT"},{"index":169,"name":"ITEM169","description":"","units":{},"default":"0","value_type":"INT"},{"index":170,"name":"ITEM170","description":"","units":{},"default":"0","value_type":"INT"},{"index":171,"name":"ITEM171","description":"","units":{},"default":"0","value_type":"INT"},{"index":172,"name":"ITEM172","description":"","units":{},"default":"0","value_type":"INT"},{"index":173,"name":"ITEM173","description":"","units":{},"default":"0","value_type":"INT"},{"index":174,"name":"ITEM174","description":"","units":{},"default":"0","value_type":"INT"},{"index":175,"name":"ITEM175","description":"","units":{},"default":"0","value_type":"INT"},{"index":176,"name":"ITEM176","description":"","units":{},"default":"0","value_type":"INT"},{"index":177,"name":"ITEM177","description":"","units":{},"default":"0","value_type":"INT"},{"index":178,"name":"ITEM178","description":"","units":{},"default":"0","value_type":"INT"},{"index":179,"name":"ITEM179","description":"","units":{},"default":"0","value_type":"INT"},{"index":180,"name":"ITEM180","description":"","units":{},"default":"0","value_type":"INT"},{"index":181,"name":"ITEM181","description":"","units":{},"default":"0","value_type":"INT"},{"index":182,"name":"ITEM182","description":"","units":{},"default":"0","value_type":"INT"},{"index":183,"name":"ITEM183","description":"","units":{},"default":"0","value_type":"INT"},{"index":184,"name":"ITEM184","description":"","units":{},"default":"0","value_type":"INT"},{"index":185,"name":"ITEM185","description":"","units":{},"default":"0","value_type":"INT"},{"index":186,"name":"ITEM186","description":"","units":{},"default":"0","value_type":"INT"},{"index":187,"name":"ITEM187","description":"","units":{},"default":"0","value_type":"INT"},{"index":188,"name":"ITEM188","description":"","units":{},"default":"0","value_type":"INT"},{"index":189,"name":"ITEM189","description":"","units":{},"default":"0","value_type":"INT"},{"index":190,"name":"ITEM190","description":"","units":{},"default":"0","value_type":"INT"},{"index":191,"name":"ITEM191","description":"","units":{},"default":"0","value_type":"INT"},{"index":192,"name":"ITEM192","description":"","units":{},"default":"0","value_type":"INT"},{"index":193,"name":"ITEM193","description":"","units":{},"default":"0","value_type":"INT"},{"index":194,"name":"ITEM194","description":"","units":{},"default":"0","value_type":"INT"},{"index":195,"name":"ITEM195","description":"","units":{},"default":"0","value_type":"INT"},{"index":196,"name":"ITEM196","description":"","units":{},"default":"0","value_type":"INT"},{"index":197,"name":"ITEM197","description":"","units":{},"default":"0","value_type":"INT"},{"index":198,"name":"ITEM198","description":"","units":{},"default":"0","value_type":"INT"},{"index":199,"name":"ITEM199","description":"","units":{},"default":"0","value_type":"INT"},{"index":200,"name":"ITEM200","description":"","units":{},"default":"0","value_type":"INT"},{"index":201,"name":"ITEM201","description":"","units":{},"default":"0","value_type":"INT"},{"index":202,"name":"ITEM202","description":"","units":{},"default":"0","value_type":"INT"},{"index":203,"name":"ITEM203","description":"","units":{},"default":"0","value_type":"INT"},{"index":204,"name":"ITEM204","description":"","units":{},"default":"0","value_type":"INT"},{"index":205,"name":"ITEM205","description":"","units":{},"default":"0","value_type":"INT"},{"index":206,"name":"ITEM206","description":"","units":{},"default":"0","value_type":"INT"},{"index":207,"name":"ITEM207","description":"","units":{},"default":"0","value_type":"INT"},{"index":208,"name":"ITEM208","description":"","units":{},"default":"0","value_type":"INT"},{"index":209,"name":"ITEM209","description":"","units":{},"default":"0","value_type":"INT"},{"index":210,"name":"ITEM210","description":"","units":{},"default":"0","value_type":"INT"},{"index":211,"name":"ITEM211","description":"","units":{},"default":"0","value_type":"INT"},{"index":212,"name":"ITEM212","description":"","units":{},"default":"0","value_type":"INT"},{"index":213,"name":"ITEM213","description":"","units":{},"default":"0","value_type":"INT"},{"index":214,"name":"ITEM214","description":"","units":{},"default":"0","value_type":"INT"},{"index":215,"name":"ITEM215","description":"","units":{},"default":"0","value_type":"INT"},{"index":216,"name":"ITEM216","description":"","units":{},"default":"0","value_type":"INT"},{"index":217,"name":"ITEM217","description":"","units":{},"default":"0","value_type":"INT"},{"index":218,"name":"ITEM218","description":"","units":{},"default":"0","value_type":"INT"},{"index":219,"name":"ITEM219","description":"","units":{},"default":"0","value_type":"INT"},{"index":220,"name":"ITEM220","description":"","units":{},"default":"0","value_type":"INT"},{"index":221,"name":"ITEM221","description":"","units":{},"default":"0","value_type":"INT"},{"index":222,"name":"ITEM222","description":"","units":{},"default":"0","value_type":"INT"},{"index":223,"name":"ITEM223","description":"","units":{},"default":"0","value_type":"INT"},{"index":224,"name":"ITEM224","description":"","units":{},"default":"0","value_type":"INT"},{"index":225,"name":"ITEM225","description":"","units":{},"default":"0","value_type":"INT"},{"index":226,"name":"ITEM226","description":"","units":{},"default":"0","value_type":"INT"},{"index":227,"name":"ITEM227","description":"","units":{},"default":"0","value_type":"INT"},{"index":228,"name":"ITEM228","description":"","units":{},"default":"0","value_type":"INT"},{"index":229,"name":"ITEM229","description":"","units":{},"default":"0","value_type":"INT"},{"index":230,"name":"ITEM230","description":"","units":{},"default":"0","value_type":"INT"},{"index":231,"name":"ITEM231","description":"","units":{},"default":"0","value_type":"INT"},{"index":232,"name":"ITEM232","description":"","units":{},"default":"0","value_type":"INT"},{"index":233,"name":"ITEM233","description":"","units":{},"default":"0","value_type":"INT"},{"index":234,"name":"ITEM234","description":"","units":{},"default":"0","value_type":"INT"},{"index":235,"name":"ITEM235","description":"","units":{},"default":"0","value_type":"INT"},{"index":236,"name":"ITEM236","description":"","units":{},"default":"0","value_type":"INT"},{"index":237,"name":"ITEM237","description":"","units":{},"default":"0","value_type":"INT"},{"index":238,"name":"ITEM238","description":"","units":{},"default":"0","value_type":"INT"},{"index":239,"name":"ITEM239","description":"","units":{},"default":"0","value_type":"INT"},{"index":240,"name":"ITEM240","description":"","units":{},"default":"0","value_type":"INT"},{"index":241,"name":"ITEM241","description":"","units":{},"default":"0","value_type":"INT"},{"index":242,"name":"ITEM242","description":"","units":{},"default":"0","value_type":"INT"},{"index":243,"name":"ITEM243","description":"","units":{},"default":"0","value_type":"INT"},{"index":244,"name":"ITEM244","description":"","units":{},"default":"0","value_type":"INT"},{"index":245,"name":"ITEM245","description":"","units":{},"default":"0","value_type":"INT"},{"index":246,"name":"ITEM246","description":"","units":{},"default":"0","value_type":"INT"},{"index":247,"name":"ITEM247","description":"","units":{},"default":"0","value_type":"INT"},{"index":248,"name":"ITEM248","description":"","units":{},"default":"0","value_type":"INT"},{"index":249,"name":"ITEM249","description":"","units":{},"default":"0","value_type":"INT"},{"index":250,"name":"ITEM250","description":"","units":{},"default":"0","value_type":"INT"},{"index":251,"name":"ITEM251","description":"","units":{},"default":"0","value_type":"INT"},{"index":252,"name":"ITEM252","description":"","units":{},"default":"0","value_type":"INT"},{"index":253,"name":"ITEM253","description":"","units":{},"default":"0","value_type":"INT"},{"index":254,"name":"ITEM254","description":"","units":{},"default":"0","value_type":"INT"},{"index":255,"name":"ITEM255","description":"","units":{},"default":"0","value_type":"INT"},{"index":256,"name":"ITEM256","description":"","units":{},"default":"0","value_type":"INT"},{"index":257,"name":"ITEM257","description":"","units":{},"default":"0","value_type":"INT"},{"index":258,"name":"ITEM258","description":"","units":{},"default":"0","value_type":"INT"},{"index":259,"name":"ITEM259","description":"","units":{},"default":"0","value_type":"INT"},{"index":260,"name":"ITEM260","description":"","units":{},"default":"0","value_type":"INT"},{"index":261,"name":"ITEM261","description":"","units":{},"default":"0","value_type":"INT"},{"index":262,"name":"ITEM262","description":"","units":{},"default":"0","value_type":"INT"},{"index":263,"name":"ITEM263","description":"","units":{},"default":"0","value_type":"INT"},{"index":264,"name":"ITEM264","description":"","units":{},"default":"0","value_type":"INT"},{"index":265,"name":"ITEM265","description":"","units":{},"default":"0","value_type":"INT"},{"index":266,"name":"ITEM266","description":"","units":{},"default":"0","value_type":"INT"},{"index":267,"name":"ITEM267","description":"","units":{},"default":"0","value_type":"INT"},{"index":268,"name":"ITEM268","description":"","units":{},"default":"0","value_type":"INT"},{"index":269,"name":"ITEM269","description":"","units":{},"default":"0","value_type":"INT"},{"index":270,"name":"ITEM270","description":"","units":{},"default":"0","value_type":"INT"},{"index":271,"name":"ITEM271","description":"","units":{},"default":"0","value_type":"INT"},{"index":272,"name":"ITEM272","description":"","units":{},"default":"0","value_type":"INT"},{"index":273,"name":"ITEM273","description":"","units":{},"default":"0","value_type":"INT"},{"index":274,"name":"ITEM274","description":"","units":{},"default":"0","value_type":"INT"},{"index":275,"name":"ITEM275","description":"","units":{},"default":"0","value_type":"INT"},{"index":276,"name":"ITEM276","description":"","units":{},"default":"0","value_type":"INT"},{"index":277,"name":"ITEM277","description":"","units":{},"default":"0","value_type":"INT"},{"index":278,"name":"ITEM278","description":"","units":{},"default":"0","value_type":"INT"},{"index":279,"name":"ITEM279","description":"","units":{},"default":"0","value_type":"INT"},{"index":280,"name":"ITEM280","description":"","units":{},"default":"0","value_type":"INT"},{"index":281,"name":"ITEM281","description":"","units":{},"default":"0","value_type":"INT"},{"index":282,"name":"ITEM282","description":"","units":{},"default":"0","value_type":"INT"},{"index":283,"name":"ITEM283","description":"","units":{},"default":"0","value_type":"INT"},{"index":284,"name":"ITEM284","description":"","units":{},"default":"0","value_type":"INT"},{"index":285,"name":"ITEM285","description":"","units":{},"default":"0","value_type":"INT"},{"index":286,"name":"ITEM286","description":"","units":{},"default":"0","value_type":"INT"},{"index":287,"name":"ITEM287","description":"","units":{},"default":"0","value_type":"INT"},{"index":288,"name":"ITEM288","description":"","units":{},"default":"0","value_type":"INT"},{"index":289,"name":"ITEM289","description":"","units":{},"default":"0","value_type":"INT"},{"index":290,"name":"ITEM290","description":"","units":{},"default":"0","value_type":"INT"},{"index":291,"name":"ITEM291","description":"","units":{},"default":"0","value_type":"INT"},{"index":292,"name":"ITEM292","description":"","units":{},"default":"0","value_type":"INT"},{"index":293,"name":"ITEM293","description":"","units":{},"default":"0","value_type":"INT"},{"index":294,"name":"ITEM294","description":"","units":{},"default":"0","value_type":"INT"},{"index":295,"name":"ITEM295","description":"","units":{},"default":"0","value_type":"INT"},{"index":296,"name":"ITEM296","description":"","units":{},"default":"0","value_type":"INT"},{"index":297,"name":"ITEM297","description":"","units":{},"default":"0","value_type":"INT"},{"index":298,"name":"ITEM298","description":"","units":{},"default":"0","value_type":"INT"},{"index":299,"name":"ITEM299","description":"","units":{},"default":"0","value_type":"INT"},{"index":300,"name":"ITEM300","description":"","units":{},"default":"0","value_type":"INT"},{"index":301,"name":"ITEM301","description":"","units":{},"default":"0","value_type":"INT"},{"index":302,"name":"ITEM302","description":"","units":{},"default":"0","value_type":"INT"},{"index":303,"name":"ITEM303","description":"","units":{},"default":"0","value_type":"INT"},{"index":304,"name":"ITEM304","description":"","units":{},"default":"0","value_type":"INT"},{"index":305,"name":"ITEM305","description":"","units":{},"default":"0","value_type":"INT"},{"index":306,"name":"ITEM306","description":"","units":{},"default":"0","value_type":"INT"},{"index":307,"name":"ITEM307","description":"","units":{},"default":"0","value_type":"INT"},{"index":308,"name":"ITEM308","description":"","units":{},"default":"0","value_type":"INT"},{"index":309,"name":"ITEM309","description":"","units":{},"default":"0","value_type":"INT"},{"index":310,"name":"ITEM310","description":"","units":{},"default":"0","value_type":"INT"},{"index":311,"name":"ITEM311","description":"","units":{},"default":"0","value_type":"INT"},{"index":312,"name":"ITEM312","description":"","units":{},"default":"0","value_type":"INT"},{"index":313,"name":"ITEM313","description":"","units":{},"default":"0","value_type":"INT"},{"index":314,"name":"ITEM314","description":"","units":{},"default":"0","value_type":"INT"},{"index":315,"name":"ITEM315","description":"","units":{},"default":"0","value_type":"INT"},{"index":316,"name":"ITEM316","description":"","units":{},"default":"0","value_type":"INT"},{"index":317,"name":"ITEM317","description":"","units":{},"default":"0","value_type":"INT"},{"index":318,"name":"ITEM318","description":"","units":{},"default":"0","value_type":"INT"},{"index":319,"name":"ITEM319","description":"","units":{},"default":"0","value_type":"INT"}],"example":"--\n-- SKIP ACTIVATE\n-- OPTIONS OPTION\nOPTIONS\n77*0 1 /\nThe above example activates the use of scratch files for pre-processing grid geometry data for non-neighbor connections. Note if multiple options are required then one can just repeat the format of the example to activate multiple options as the keyword does not overwrite previous entries. So for example:\n--\n-- SKIP ACTIVATE\n-- OPTIONS OPTION\nOPTIONS\n7*0 1 /\n--\n-- SKIP ACTIVATE\n-- OPTIONS OPTION\nOPTIONS\n77*0 1 /\n--\n-- SKIP ACTIVATE\n-- OPTIONS OPTION\nOPTIONS\n177*0 1 /\nCould be used to activate the 8, 78 and 178 options if they were available.","expected_columns":319,"size_kind":"fixed","size_count":1},"PARALLEL":{"name":"PARALLEL","sections":["RUNSPEC"],"supported":null,"summary":"The PARALLEL keyword defines the run to use parallel processing and sets the domain decomposition options. See section 2.2Running OPM Flow 2023-04 From The Command Lineon how to run OPM Flow in parallel mode.","parameters":[{"index":1,"name":"NPROCS","description":"A positive integer that defines the number of domains or parallel processors to use for this run.","units":{},"default":"1","value_type":"INT"},{"index":2,"name":"RTYPE","description":"A character string set to either SERIAL to run the parallel code in serial mode for testing the code, or DISTRIBUTED to full utilize parallel processing.","units":{},"default":"DISTRIBUTED","value_type":"STRING"}],"example":"--\n-- PARALLEL MULTI-CORE OPTIONS\n-- NDMAIN MACHINE TYPE\nPARALLEL\n2 DISTRIBUTED /\nThe above example sets the number of domains (or processors) to two and for the simulation to run in parallel mode. This has no effect in OPM Flow input decks.","expected_columns":2,"size_kind":"fixed","size_count":1},"PARTTRAC":{"name":"PARTTRAC","sections":["RUNSPEC"],"supported":false,"summary":"The PARTTRAC keyword activates the Partitioned Tracer option and defines the maximum number of partitioned tracers, the number of TRACERKP or TRACERKM partitioning tables in the PROPS section, and the maximum number of number of rows in the TRACERKP or TRACERKM partitioning tables.","parameters":[{"index":1,"name":"NPARTT","description":"","units":{},"default":"0","value_type":"INT"},{"index":2,"name":"NKPTMX","description":"","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"NPKPMX","description":"","units":{},"default":"0","value_type":"INT"}],"example":"","expected_columns":3,"size_kind":"fixed","size_count":1},"PATHS":{"name":"PATHS","sections":["RUNSPEC"],"supported":null,"summary":"PATHS allows the user to define alias directory filenames to avoid long filenames with the INCLUDE, IMPORT, RESTART or GDFILE keywords. To use the alias with the aforementioned keywords PATHS should be prefixed with the $ symbol.","parameters":[{"index":1,"name":"ALIAS","description":"A character string enclosed in quotes defining the alias.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"DIRC","description":"A character string enclosed in quotes defining the directory filename.","units":{},"default":"None","value_type":"STRING"}],"example":"--\n-- PATH PATH\n-- ALIAS DIRECTORY FILENAME\nPATHS\n'GRID' '/DISK1/NORNE/2017/GRID-INCLUDES' /\n'SCHD' '/DISK1/NORNE/2017/SCHD-INCLUDES' /\n/\nThe above example defines “GRID” and “SCHD” aliases in the RUNSPEC section than can be used in the GRID and SCHEDULE sections of the input deck. The next example shows how to use the “GRID” alias with the INCLUDE keyword in the GRID section.\n--\n-- LOAD INCLUDE FILES\n--\nINCLUDE\n'$GRID/PORO.INC' /\nINCLUDE\n'$GRID/PERMX.INC' /\nINCLUDE\n'$GRID/NTG.INC' /\nHere the porosity, permeability and net-to-gross arrays are loaded in the GRID section using the directory filename aliases declared in the RUNSPEC section.","expected_columns":2,"size_kind":"list"},"PEDIMS":{"name":"PEDIMS","sections":["RUNSPEC"],"supported":false,"summary":"The PEDIMS keyword defines the number of petro-elastic regions to be used with the PENUM keyword in the REGIONS section and the number of rows in the PEGTAB0 to PEGTAB7 keywords, as well as the number of rows in the PEKTAB0 to PEKTAB7 keywords in the PROPS section.","parameters":[{"index":1,"name":"NUM_REGIONS","description":"","units":{},"default":"0","value_type":"INT"},{"index":2,"name":"MAX_PRESSURE_POINTS","description":"","units":{},"default":"0","value_type":"INT"}],"example":"","expected_columns":2,"size_kind":"fixed","size_count":1},"PETOPTS":{"name":"PETOPTS","sections":["RUNSPEC"],"supported":false,"summary":"The PETOPTS keyword defines various Petrel and Generic Simulation (*.GSG) file options.","parameters":[{"index":1,"name":"OPTIONS","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","size_kind":"fixed","size_count":1,"variadic_record":true},"PIMTDIMS":{"name":"PIMTDIMS","sections":["RUNSPEC"],"supported":null,"summary":"PIMTDIMS keyword defines the maximum number of PIMULTAB tables and the maximum number of entries (or rows) per PIMULTAB table. The PIMULTAB keyword is used to define a well’s productivity index factor as a function of a well’s producing water cut.","parameters":[{"index":1,"name":"NTPIMT","description":"A positive integer value that defines the maximum number of PIMULTAB keywords defined in the input deck.","units":{},"default":"0","value_type":"INT"},{"index":2,"name":"NRPIMT","description":"A positive integer value defining the maximum number of entries (rows) in the PIMULTAB keyword.","units":{},"default":"0","value_type":"INT"}],"example":"--\n-- MAX MAX\n-- TABLES ENTRIES\nPIMTDIMS\n1 51 /\nThe above example defines that there is one PIMULTAB table with a maximum number of 51 rows.","expected_columns":2,"size_kind":"fixed","size_count":1},"PINTDIMS":{"name":"PINTDIMS","sections":["RUNSPEC"],"supported":null,"summary":"The PINTDIMS keyword defines the number of property tables used in the OPM Flow's Polymer Molecular Weight Transport option, that uses the polymer molecular weight in calculating the polymer viscosity, as well as accounting for formation damage due to the water and polymer injection, by adjusting the wellbore skin pressure. This keyword should only be used if the POLYMER and POLYMW keywords in the RUNSPEC section are also activated. The PINTDIMS keyword defines the maximum number of tables for the SKPRWAT, SKPRPOLY, and PLYMWINJ keywords, and the number of entries in the PLYVMH keyword. All the aforementioned keywords are in the PROPS section.","parameters":[{"index":1,"name":"NTSKWAT","description":"NTSKWAT is a positive integer that defines the number of SKPRWAT tables in the PROPS section, used to describe the relationship of wellbore skin pressure as a function of water throughput and water velocity, for the simulator's Polymer Molecular Weight Transport option.","units":{},"default":"1","value_type":"INT"},{"index":2,"name":"NTSKPOLY","description":"NTSKPOLY is a positive integer that defines the number of SKPRPOLY tables in the PROPS section, used to describe the relationship of wellbore skin pressure as a function of polymer throughput and polymer velocity, for the simulator's Polymer Molecular Weight Transport option.","units":{},"default":"1","value_type":"INT"},{"index":3,"name":"NTPMWINJ","description":"NTPMWINJ is a positive integer that defines the number of PLYMWINJ tables in the PROPS section, used to describe the relationship of the injected polymer molecular weight as a function of polymer throughput and polymer velocity, for the simulator's Polymer Molecular Weight Transport option.","units":{},"default":"1","value_type":"INT"},{"index":4,"name":"NPLYVMH","description":"NPLYVMH is a positive integer that defines the maximum number of entries (rows) in the PLYVMH table in the PROPS section, used to describe the relationship of the injected polymer viscosity as a function of polymer molecular weight and polymer concentration, for the simulator's Polymer Molecular Weight Transport option.","units":{},"default":"1"}],"example":"--\n-- POLYMER MOLECULAR WEIGHT TRANSPORT TABLES (OPM FLOW RUNSPEC KEYWORD)\n--\n-- NO. NO. NO. NO.\n-- NTSKWAT NTSKPOLY NTPMWINJ NPLYVMH\nPINTDIMS\n2 2 2 1 /\nThe above example declares two SKPRWAT, SKPRPOLY, and PLYMWINJ keywords in the PROPS section will be used, as well as the default value of one for the number of rows in the PLYVMH keyword.\n| Note This is an OPM Flow specific keyword that employs an alternative polymer flood model based on a Polymer Molecular Weight Transport equation, that is not available in the commercial simulator. |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":3,"size_kind":"fixed","size_count":1},"POLYMER":{"name":"POLYMER","sections":["RUNSPEC"],"supported":null,"summary":"This keyword indicates that the polymer phase is present in the model and to activate the polymer flooding model. The keyword will also invoke data input file checking to ensure that all the required polymer phase input parameters are defined in the input deck.","parameters":[],"example":"--\n-- ACTIVATE THE POLYMER PHASE IN THE MODEL\n--\nPOLYMER\nThe above example declares that the polymer phase is active in the model.","size_kind":"none","size_count":0},"POLYMW":{"name":"POLYMW","sections":["RUNSPEC"],"supported":null,"summary":"This keyword activates OPM Flow's Polymer Molecular Weight Transport option that uses the polymer molecular weight in calculating the polymer viscosity, as well as accounting for formation damage due to the water and polymer injection, by adjusting the wellbore skin pressure. This keyword should only be used if the POLYMER keyword in the RUNSPEC section is also activated. The keyword will also invoke data input file checking to ensure that all the required polymer phase input parameters are defined in the input deck.","parameters":[],"example":"--\n-- ACTIVATE THE POLYMER PHASE IN THE MODEL\n--\nPOLYMER\n--\n-- ACTIVATE THE POLYMER MOLECULAR WEIGHT TRANSPORT OPTION\n--\nPOLYMW\nThe above example declares that the polymer phase is present, and that the simulator's Polymer Molecular Weight Transport option should be used instead of the standard polymer model.\n| Note This is an OPM Flow specific keyword that employs an alternative polymer flood model based on a Polymer Molecular Weight Transport equation, that is not available in the commercial simulator. |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"none","size_count":0},"PRECSALT":{"name":"PRECSALT","sections":["RUNSPEC"],"supported":null,"summary":"This keyword activates the OPM Flow Salt Precipitation model that accounts for salt precipitating out of the water phase when the water is being vaporized into the gas phase and the dissolved salt reaches the solubility limit as the pressure in the reservoir is being depleted (see the VAPWAT keyword in the RUNSPEC section). This facility is an extension to the standard Brine model, and as such the BRINE keyword in the RUNSPEC must also be present in the input deck. In general, if the PRECSALT keyword has been activated in the input deck then the VAPWAT keyword should also be activated. The keyword should only be used if both water and gas phases are active in the model.","parameters":[],"example":"The first part of the example shows the keywords for the RUNSPEC section.\n-- ==============================================================================\n--\n-- RUNSPEC SECTION\n--\n-- ==============================================================================\nRUNSPEC\n-- ------------------------------------------------------------------------------\n-- FLUID TYPES AND TRACER OPTIONS\n-- ------------------------------------------------------------------------------\n--\n-- OIL PHASE IS PRESENT IN THE RUN\n--\nOIL\n--\n-- WATER PHASE IS PRESENT IN THE RUN\n--\nWATER\n--\n-- GAS PHASE IS PRESENT IN THE RUN\n--\nGAS\n--\n-- DISSOLVED GAS IN LIVE OIL IS PRESENT IN THE RUN\n--\nDISGAS\n--\n-- ACTIVATE STANDARD BRINE MODEL IN THE RUN\n--\nBRINE\n--\n-- ACTIVATE THE OPM FLOW SALT PRECIPITATION MODEL (OPM FLOW KEYWORD)\n--\nPRECSALT\nThe above example declares that the oil, water, gas, dissolved gas, and brine phases are present in the model, and activates the Brine (BRINE keyword) and Salt Precipitation (PRECSALT keyword) models.\nThe second part of the example shows the additional PVT fluid keywords require for the Salt Precipitation model in the PROPS section. Note that in addition to the Salt Precipitation model specific keywords, the standard DENSITY (or GRAVITY), PVDG, and PVTO keywords are required.\n-- ==============================================================================\n--\n-- PROPS SECTION\n--\n-- ==============================================================================\nPROPS\n--\n-- WATER SALT PVT TABLE\n--\nPVTWSALT\n-- REF PRES REF SALT\n-- PSIA LB/STB\n-- -------- --------\n3000.0 0.000 / REFERENCE DATA\n--\n-- SALTCONC BW CW VISC VISC\n-- LB/STB RB/STB 1/PSIA CPOISE GRAD\n-- -------- -------- ------- ------ ------\n0.0 1.0 3.0E-6 1.0 1.0E-6\n10.0 0.8 3.0E-6 1.0 1.0E-6 / SALT CONCENTRATION\n--\n-- SET SALT SOLUBILITY LIMIT FOR ALL CELLS (OPM FLOW KEYWORD)\n--\nSALTSOL\n-- MAX SALT\n-- SALTSOL DENSITY\n0.500 135.46867445023383 /\nIn addition, to the above the PERMFACT keyword may be used to account for the reduction in porosity and permeability due to salt precipitating into the pore space. Again, in addition to the Salt Precipitation model specific keywords, the standard ROCK, SGOF, and SWOF keywords are required.\n--\n-- PERMEABILITY FACTOR REDUCTION DUE TO SALT (OPM FLOW KEYWORD)\n--\nPERMFACT\n-- PORO PERM\n-- FACTOR FACTOR\n-- ------- --------\n0.0 0.000\n0.4 0.005\n0.6 0.010\n0.9 0.100\n1.0 1.000 / TABLE NO. 01\n/\nIn order to initialize the model in the SOLUTION section, apart from the standard equilibration keywords, the following Salt Precipitation model specific keywords should be included.\n-- ==============================================================================\n--\n-- SOLUTION SECTION\n--\n-- ==============================================================================\nSOLUTION\n--\n-- PRECIPITATED SALT VOLUME FRACTION VERSUS DEPTH (OPM FLOW KEYWORD)\n--\n-- DEPTH SALTPSAT\n-- ------ --------\nSALTPVD\n8300.0 0.010\n8450.0 0.010 / SALT VS DEPTH EQUIL REGN 01\n--\n-- DEPTH SALT-1 SALT-2 SALT-3\n-- SALTCON SALTCON SALTCON\n-- ------ ------- ------- -------\nSALTVD\n8300.0 0.500\n8450.0 0.500 / SALT VS DEPTH EQUIL REGN 01\nNote that OPM Flow does not support Multi-Component Brine model, thus there should only one column of salt concentrations.\nFinally, in the SCHEDULE section, one may optionally one can add the injections well's injection salt concentrations, as shown below.\n-- ==============================================================================\n--\n-- SCHEDULE SECTION\n--\n-- ==============================================================================\nSCHEDULE\n--\n-- DEFINE WATER INJECTION WELL SALT CONCENTRATIONS\n--\n-- WELL SALT-1 SALT-2 SALT-3 SALT-4\n-- NAME SALTCON SALTCON SALTCON SALTCON\n-- ------- ------- ------- --------\nWSALT\n'INJ' 0.0000 /\n/\nNormally, with this option one would also include vaporized water via the VAPWAT keyword in the RUNSPEC section, as well as the PVTGW keyword to define gas PVT properties for dry gas, or the PVTGWO keyword that declares ","size_kind":"none","size_count":0},"PSTEADY":{"name":"PSTEADY","sections":["RUNSPEC"],"supported":false,"summary":"The PSTEADY keyword activates Pseudo Steady State Flow Calculation option by advancing the simulator until it reaches a pseudo steady state flow and then sets the date to the date defined on this keyword, that is written to the RESTART file. Keyword also includes parameters defining the conditions for pseudo steady flow state.","parameters":[{"index":1,"name":"DAY","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"MONTH","description":"","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"YEAR","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"DIFF","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":5,"name":"PRESSURE_TOL","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":6,"name":"OIL_TOL","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":7,"name":"WATER_TOL","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":8,"name":"GAS_TOL","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":9,"name":"BRINE_TOL","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":10,"name":"MAX_TIME","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Time"},{"index":11,"name":"MIN_TIME","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Time"},{"index":12,"name":"PIM_AQUIFERS","description":"","units":{},"default":"NO","value_type":"STRING"}],"example":"","expected_columns":12,"size_kind":"fixed","size_count":1},"RADIAL":{"name":"RADIAL","sections":["RUNSPEC"],"supported":null,"summary":"RADIAL activates the radial grid geometry option for the model, if this keyword and the SPIDER keyword are omitted then Cartesian geometry is assumed by OPM Flow.","parameters":[],"example":"--\n-- DEFINE RADIAL GRID GEOMETRY\n--\nRADIAL\nThe example activates the radial grid geometry option.","size_kind":"none","size_count":0},"REGDIMS":{"name":"REGDIMS","sections":["RUNSPEC"],"supported":null,"summary":"The REGDIMS keyword defines the maximum number of regions for various region arrays used in the model. Note that the maximum number of FIPNUM regions can be defined both on this keyword and the TABDIMS keyword, if it set in both locations the maximum value is used. The reason for this type of inconsistency is due to the commercial simulator evolving with time as new features were added, but at the same time having to maintain backward input deck compatibility.","parameters":[{"index":1,"name":"NTFIP","description":"A positive integer defining the maximum number of regions in the FIPNUM region array. If additional sets of fluid in-place regions have been defined, as per the FIPxxxxx series of fluid in-place region keywords, then NTFIP should be set to the maximum number of regions in either the FIPNUM or FIPxxxxx associated arrays. Thus, if the maximum number of regions in the FIPNUM array is 12, and the maximum value in the FIPxxxxx series of arrays is 20, then 20 should be entered for NTFIP. Note that this parameter may also be set on the TABDIMS keyword as well. If NTFIP is set in both places, then the maximum value is used.","units":{},"default":"1","value_type":"INT"},{"index":2,"name":"NMFIPR","description":"A positive integer defining the total maximum number of fluid in-place regions. The number of FIPNUM regions are defined by NTFIP. However, if additional sets of fluid in-place regions are required, as per the FIPxxxxx series of fluid in-place region keywords, then these are to be defined here by adding the number of FIPxxxxx arrays to the value NTFIP. So for example, if NTFIP equals five and the number of distinct FIPxxxxx regions is three, then the value to enter for NMFIPR is eight.","units":{},"default":"1","value_type":"INT"},{"index":3,"name":"NRFREG","description":"A positive integer defining the maximum number of independent reservoir regions in the ISOLNUM region array.","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"MXNFLX","description":"A positive integer defining the maximum number of flux regions in the FLUXNUM region array. MXNFLX can also be defined on the TABDIMS keywords as well. If MXNFLX is defined both here and on the TABDIMS keyword then the maximum value of the two is used.","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"NUSREG","description":"A positive integer defining the maximum user defined regions in a commercial simulator’s compositional model. This parameter is included for compatibility and should be defaulted as it is not used in OPM Flow.","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"NTCREG","description":"A positive integer defining the maximum number of regions in the COALNUM region array. This parameter is included for compatibility and should be defaulted as it is not used in OPM Flow.","units":{},"default":"1","value_type":"INT"},{"index":7,"name":"NOPREG","description":"A positive integer defining the maximum number of regions in the OPERNUM region array.","units":{},"default":"0","value_type":"INT"},{"index":8,"name":"NWKDREG","description":"A positive integer defining the maximum number of real double-precision work arrays for use with the OPERATE and OPERATER keywords. This parameter is included for compatibility and should be defaulted as it is not used in OPM Flow.","units":{},"default":"0","value_type":"INT"},{"index":9,"name":"NWKIREG","description":"A positive integer defining the maximum number of integer work arrays for use with the OPERATE and OPERATER keywords. This parameter is included for compatibility and should be defaulted as it is not used in OPM Flow.","units":{},"default":"0","value_type":"INT"},{"index":10,"name":"NPLMIX","description":"A positive integer defining the maximum number of regions in the PLMIXNUM region array.","units":{},"default":"1","value_type":"INT"}],"example":"--\n-- MAX TOTAL INDEP FLUX TRACK CBM OPERN WORK WORK POLY\n-- FIPNUM REGNS REGNS REGNS REGNS REGNS REGNS REAL INTG REGNS\nREGDIMS\n9 12 1* 1* 1* 1* 1* 1* 1* 1* /\nThe above example defines the number of FIPNUM regions to be nine and the number of FIPxxx type of regions to be three (12 – 9), the rest of the region sizes are set to the default values.","expected_columns":10,"size_kind":"fixed","size_count":1},"RIVRDIMS":{"name":"RIVRDIMS","sections":["RUNSPEC"],"supported":false,"summary":"RIVRDIMS defines the river system array dimensions used with the REACHES keyword and other river keywords in the SOLUTION and SCHEDULE sections. The keyword also enables the River option.","parameters":[{"index":1,"name":"MAX_RIVERS","description":"","units":{},"default":"0","value_type":"INT"},{"index":2,"name":"MAX_REACHES","description":"","units":{},"default":"1","value_type":"INT"},{"index":3,"name":"MAX_BRANCHES","description":"","units":{},"default":"1","value_type":"INT"},{"index":4,"name":"MAX_BLOCKS","description":"","units":{},"default":"1","value_type":"INT"},{"index":5,"name":"MXTBPR","description":"","units":{},"default":"1","value_type":"INT"},{"index":6,"name":"MXDPTB","description":"","units":{},"default":"2","value_type":"INT"},{"index":7,"name":"MXTBGR","description":"","units":{},"default":"1","value_type":"INT"},{"index":8,"name":"NMDEPT","description":"","units":{},"default":"0","value_type":"INT"},{"index":9,"name":"MXDEPT","description":"","units":{},"default":"2","value_type":"INT"},{"index":10,"name":"NMMAST","description":"","units":{},"default":"0","value_type":"INT"},{"index":11,"name":"MXMAST","description":"","units":{},"default":"2","value_type":"INT"},{"index":12,"name":"NRATTA","description":"","units":{},"default":"0","value_type":"INT"},{"index":13,"name":"MXRATE","description":"","units":{},"default":"2","value_type":"INT"}],"example":"","expected_columns":13,"size_kind":"fixed","size_count":1},"ROCKCOMP":{"name":"ROCKCOMP","sections":["RUNSPEC"],"supported":true,"summary":"The ROCKCOMP keyword activates rock compaction and defines various rock compaction options for the run. By default OPM Flow models rock compaction via pore volume compressibility as entered on the ROCK keyword in the PROPS section. This keyword enables pressure dependent pore volume and transmissibility multipliers for rock compaction that are entered in the PROPS section using the ROCKTAB keyword. Currently OPM Flow only supports the default options for rock compaction.","parameters":[{"index":1,"name":"ROCKOPT","description":"A character string that defines the rock compaction option based on one of the following character strings: REVERS: Rock compaction is reversible with increasing pressure. The rock compaction multipliers should be entered via the ROCKTAB keyword in the PROPS section. This is the default value. IRREVERS: Rock compaction is irreversible, that is the rock expansion does not occur when the pressure subsequently increases. HYSTER: Invokes the hysteresis rock compaction option. BOBERG: Rock compaction hysteresis is modeled using the Boberg formulation93\n Beattie, C.I., Boberg, T.C., and McNab, G.S. “Reservoir Simulation of Cyclic Steam Stimulation in the Cold Lake Oil Sands,” paper SPE 18752, Society of Petroleum Engineers Journal, (1991) 6, No. 2, 200-206.. Beattie, C.I., Boberg, T.C., and McNab, G.S. “Reservoir Simulation of Cyclic Steam Stimulation in the Cold Lake Oil Sands,” paper SPE 18752, Society of Petroleum Engineers Journal, (1991) 6, No. 2, 200-206. REVLIMIT: Activates the reversible hysteresis rock compaction option that limits the pore volume subject to reversibility based on the minimum pressure in a grid block and the initial water saturation. This option is only intended to be used with the water induced compaction model, neither of which are currently supported by OPM Flow.. PALM-MAN: Rock compaction hysteresis is modeled using the Palmer-Mansoori94\n Palmer, I. and Mansoori, J. “How Permeability Depends on Stress and Pore Pressure in Coalbeds: A New Model,” paper SPE 52607, SPE Reservoir Evaluation & Engineering (1998) 1, No. 6, 539-544. and 95\n Clarkson, C.R., Pan, Z., Palmer, I. and Harpalani, S. \"Predicting Sorption-Induced Strain and Permeability Increase With Depletion for Coalbed-Methane Reservoirs\", SPE 114778-PA, SPE Journal (2010) 15, No. 1, 152–159.formulation for coal bed methane reservoirs, neither of which are supported by OPM Flow. Palmer, I. and Mansoori, J. “How Permeability Depends on Stress and Pore Pressure in Coalbeds: A New Model,” paper SPE 52607, SPE Reservoir Evaluation & Engineering (1998) 1, No. 6, 539-544. Clarkson, C.R., Pan, Z., Palmer, I. and Harpalani, S. \"Predicting Sorption-Induced Strain and Permeability Increase With Depletion for Coalbed-Methane Reservoirs\", SPE 114778-PA, SPE Journal (2010) 15, No. 1, 152–159. NONE: Deactivates rock compaction, unless the water induced compaction model has been invoked. Only the REVERS and IRREVERS options are supported by OPM Flow.","units":{},"default":"REVERS","value_type":"STRING"},{"index":2,"name":"NTROCC","description":"A positive integer that defines the number of rock compaction tables, that is the number of ROCKTAB tables to be used by OPM Flow.","units":{},"default":"1","value_type":"INT"},{"index":3,"name":"WATINOPT","description":"A character string that states if the water induced rock compaction option should be used (YES) or not (NO). If set to YES then either the ROCKTABW or the ROCK2D and ROCKWNOD keywords should be entered in the PROPS section.","units":{},"default":"NO","value_type":"STRING"},{"index":4,"name":"PORTXROP","description":"A character string that specifies the model to be used for when transmissibility is dependent on porosity, and should be set to either: EXP: An exponential porosity-transmissibility relationship should be used. CZ: The Carmen-Kozeny96\n J. Kozeny, \"Ueber kapillare Leitung des Wassers im Boden.\" Sitzungsber Akad. Wiss., Wien, 136(2a): 271-306, 1927., 97\n P.C. Carman, \"Fluid flow through granular beds.\" Transactions, Institution of Chemical Engineers, London, 15: 150-166, 1937.and 98\n P.C. Carman, \"Flow of gases through porous media.\" Butterworths, London, 1956porosity-transmissibility relationship should be used. J. Kozeny, \"Ueber kapillare Leitung des Wassers im Boden.\" Sitzungsber Akad. Wiss., Wien, 136(2a): 271-306, 1927. P.C. Carman, \"Fluid flow through granular beds.\" Transactions, Institution of Chemical Engineers, London, 15: 150-166, 1937. P.C. Carman, \"Flow of gases through porous media.\" Butterworths, London, 1956 This option is used in the commercial compositional simulator and is therefore ignored by OPM Flow.","units":{},"default":"1*","value_type":"STRING"},{"index":5,"name":"CARKZEXP","description":"The exponent constant in the Carmen-Kozeny porosity-transmissibility equation for when PORTXROP has been set to CZ. This option is used in the commercial compositional simulator and is therefore ignored by OPM Flow.","units":{},"default":"0.0","value_type":"DOUBLE"}],"example":"--\n-- ROCK NUMBER WAT POR-TRAN\n-- OPTN TABLES INDUCE OPTION\nROCKCOMP\nREVERS 5 NO 1* /\nThe above example defines the default values for the ROCKCOMP keyword with five rock compaction tables.","expected_columns":5,"size_kind":"fixed","size_count":1},"RPTCPL":{"name":"RPTCPL","sections":["RUNSPEC"],"supported":false,"summary":"This keyword activates the couple simulation reporting, that results in the simulator writing out various initialization data and simulation data in order for external “controlling programs” to interactively manage the simulation. There is no data required for this keyword but the keyword should be terminated by a “/”.","parameters":[],"example":"--\n-- ACTIVATE COUPLE SIMULATION REPORTING\n--\nRPTCPL\n/\nThe above example switches on couple simulation reporting; however, this has no effect in OPM Flow input decks.","size_kind":"fixed","size_count":1},"RPTHMD":{"name":"RPTHMD","sections":["RUNSPEC"],"supported":false,"summary":"This keyword, RPTHMD, defines the options and level of history match output that should be written to history match file (*.HMD), for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"ITEM1","description":"","units":{},"default":"0","value_type":"INT"},{"index":2,"name":"ITEM2","description":"","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"ITEM3","description":"","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"ITEM4","description":"","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"ITEM5","description":"","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"ITEM6","description":"","units":{},"default":"0","value_type":"INT"}],"example":"","expected_columns":6,"size_kind":"fixed","size_count":1},"RPTRUNSP":{"name":"RPTRUNSP","sections":["RUNSPEC"],"supported":false,"summary":"This keyword activates reporting of all the RUNSPEC options utilized in the run. There is no data required for this keyword.","parameters":[],"example":"--\n-- ACTIVATE RUNSPEC SECTION REPORTING\n--\nRPTRUNSP\nThe above example switches on RUNSPEC reporting; however, this has no effect in OPM Flow input decks.","size_kind":"none","size_count":0},"RSSPEC":{"name":"RSSPEC","sections":["RUNSPEC"],"supported":null,"summary":"The RSSPEC keyword activates the writing out of the RESTART index file (*.RSSPEC). The restart data (pressure, saturations etc. through time for each active cell) are written out to two files one file contains the data, *.UNRST for example, and the second file contains an index of the data (*.RSSPEC) stored in the *.UNRST file. This keyword is somewhat redundant as the RESTART index file is written out by default. See the NORSSPEC keyword in the RUNSPEC section that deactivates the writing out of the file.","parameters":[],"example":"--\n-- ACTIVATE OUTPUT OF THE RESTART INDEX FILE *.RSSPEC\n--\nRSSPEC\nThe above example switches on the writing of the restart index file (*.RSSPEC); however, this has no effect in OPM Flow input decks.","size_kind":"none","size_count":0},"RUNSPEC":{"name":"RUNSPEC","sections":["RUNSPEC"],"supported":null,"summary":"The RUNSPEC activation keyword marks the start of the RUNSPEC section that defines the key parameters for the simulator including the dimensions of the model, phases present in the model (oil, gas and water for example), number of tables for a given property and the maximum number of rows for each table, the maximum number of groups, wells and well completions, as well as various options to be invoked by OPM Flow.","parameters":[],"example":"-- ==============================================================================\n--\n-- RUNSPEC SECTION\n--\n-- ==============================================================================\nRUNSPEC\nThe above example marks the start of the RUNSPEC section in the OPM Flow data input file.","size_kind":"none","size_count":0},"SAMG":{"name":"SAMG","sections":["RUNSPEC"],"supported":false,"summary":"This keyword actives the algebraic multi-grid linear solve; note this solver is not available to the general public in the commercial simulator.","parameters":[{"index":1,"name":"EPS","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":2,"name":"REUSE","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":2,"size_kind":"fixed","size_count":1},"SATOPTS":{"name":"SATOPTS","sections":["RUNSPEC"],"supported":true,"summary":"The SATOPTS keyword activates OPM Flow’s relative permeability assignment options. The relative permeability functions are defined using the either the:","parameters":[{"index":1,"name":"DIRECT","description":"A character string that activates the directional relative permeability assignment option. If the DIRECT option is specified then directional relative permeability assignment is activated and different relative permeability functions are assigned to the x, y and z directions. In this case the KRNUMX, KRNUMY and KRNUMZ keywords are used for Cartesian grids to allocate the relative permeability tables. For Radial grids the KRNUMR, KRNUMT and KRNUMZ keywords should be used.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"IRREVERS","description":"A character string that activates the irreversible directional relative permeability assignment option. If the IRREVERS option is specified then the relative permeability assignment is set to irreversible and results in different sets of relative permeability tables being applied for flow in the xi to xi + 1 direction and the xi to the xi – 1 direction, for all directions (x, y, z). In this case the KRNUMX, KRNUMY and KRNUMZ keywords are used for Cartesian grids to allocate the relative permeability tables in the xi to xi + 1 flow directions etc. For Radial grids the KRNUMR, KRNUMT and KRNUMZ keywords should be used. For flow in the xi to xi – 1 flow directions, etc., the KRNUMX-, KRNUMY- and KRNUMZ- keywords are used for Cartesian grids and the KRNUMR-, KRNUMT- and KRNUMZ- are used for radial grids. Only the default option is supported by OPM Flow, that is irreversible permeability tables are not supported.","units":{},"default":"None"},{"index":3,"name":"HYSTER","description":"A character string that activates the hysteresis option. If the HYSTER and DIRECT options have been activated and the IRREVERS has not been invoked on the SATOPTS keyword, then different relative permeability functions are used for the x, y, and z directions and for the drainage and imbibition processes. Here the drainage relative permeability curves are allocated via the KRNUMX,KRNUMY and KRNUMZ keywords for Cartesian grids and the KRNUMR, KRNUMT and KRNUMZ keywords for radial grids. The imbibition relative permeability curves are allocated via the IMBNUMX, IMBNUMY and IMBNUMZ keywords for Cartesian grids and the IMBNUMR, IMBNUMT and IMBNUMZ keywords for radial grids. If the HYSTER, DIRECT and IRREVERS options have been activated, then different relative permeability functions are used for the x, y, and z directions, each flow direction and for the drainage and imbibition processes. In addition to the aforementioned relative permeability allocation keywords for the xi to xi + 1 flow direction etc., the xi to xi – 1 flow directions keywords, KRNUMX-, KRNUMY- and KRNUMZ- are used for Cartesian grids and the KRNUMR-, KRNUMT- and KRNUMZ- are used for radial grids. The imbibition relative permeability curves are allocated via the IMBNUMX-, IMBNUMY- and IMBNUMZ- keywords for Cartesian grids and the IMBNUMR, IMBNUMT and IMBNUMZ- keywords for radial grids.","units":{},"default":"None"},{"index":4,"name":"SURFTENS","description":"A character string that activates the capillary pressure surface tension pressure dependency option. Only the default option is supported by OPM Flow, that is capillary pressure surface tension pressure dependency option is not supported.","units":{},"default":"None"}],"example":"The first example actives the directional relative permeability assignment option only and hence the following keywords are used to allocate the relative permeability arrays for Cartesian grids: KRNUMX, KRNUMY, and KRNUMZ.\n--\n-- ACTIVATE RELATIVE PERMEABILITY ASSIGNMENT HYSTERESIS OPTIONS\n-- DIRECTTIONAL(DIRECT) IRREVERSIBLE(IRREVERS) HYSTERESIS(HYSTER)\nSATOPTS\n'DIRECT' /\nThe next example actives the directional and irreversible relative permeability assignment options, and hence the following keywords are used to allocate the relative permeability arrays for Cartesian grids: KRNUMX, KRNUMY, KRNUMZ, KRNUMX-, KRNUMY-and KRNUMZ-.\n--\n-- ACTIVATE RELATIVE PERMEABILITY ASSIGNMENT HYSTERESIS OPTIONS\n-- DIRECTTIONAL(DIRECT) IRREVERSIBLE(IRREVERS) HYSTERESIS(HYSTER)\nSATOPTS\n'DIRECT' 'IRREVERS' /\nFinally, the last example invokes the directional, irreversible and hysteresis assignment options.\n--\n-- ACTIVATE RELATIVE PERMEABILITY ASSIGNMENT HYSTERESIS OPTIONS\n-- DIRECTTIONAL(DIRECT) IRREVERSIBLE(IRREVERS) HYSTERESIS(HYSTER)\nSATOPTS\n'DIRECT' 'IRREVERS' 'HYSTER' /\nIn this case the drainage relative permeability curves are allocated by the KRNUMX, KRNUMY, KRNUMZ, KRNUMX-, KRNUMY-, KRNUMZ- keywords, and the imbibition relative permeability curves are allocated by the IMBNUMX, IMBNUMY, IMBNUMZ, IMBNUMX-, IMBNUMY-, IMBNUMZ- keywords.\nNote\nThis keyword activates how relative permeability curves are assigned in the model. The ENDSCALE keyword allows the end-point scaling also to vary with direction, flow direction and hysteresis process, resulting in a great deal of flexibility.\nWhether or not all these features should be used though is another question.\n| Option | Cartesian | Radial | | |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------|----------------------------------------------------------------|--------------------------------------------------------|----------------------------------------------------------------|\n| DIRECT Flow in all directions | KRNUMX KRNUMY KRNUMZ | KRNUMR KRNUMT KRNUMZ | | |\n| DIRECT and IRREVERS Flow in the i to i +1 directions. Flow in the i to i -1 directions. | KRNUMX, KRNUMY KRNUMZ KRNUMX- KRNUMY- KRNUMZ- | KRNUMR KRNUMT KRNUMZ KRNUMR- KRNUMT- KRNUMZ- | | |\n| DIRECT and HYSTER Flow in all directions. ","size_kind":"fixed","size_count":1,"variadic_record":true},"SAVE":{"name":"SAVE","sections":["RUNSPEC","SCHEDULE"],"supported":null,"summary":"This keyword activates output of a SAVE file for fast restarts which are read in by the LOAD keyword in the RUNSPEC section. No data is required for this keyword.","parameters":[{"index":1,"name":"FILE_TYPE","description":"","units":{},"default":"UNFORMATTED","value_type":"STRING"}],"example":"The first example requests that a SAVE file be written out in the RUNSPEC section; however, OPM Flow will not write a RESTART record if the SAVE keyword is encountered in the RUNSPEC section.\n-- ==============================================================================\n--\n-- RUNSPEC SECTION\n--\n-- ==============================================================================\nRUNSPEC\n--\n-- WRITE OUT SAVE FILE FOR FAST RESTARTS\n--\nSAVE\nThe second example shows how the keyword is used in the SCHEDULE section.\n-- ==============================================================================\n--\n-- SCHEDULE SECTION\n--\n-- ==============================================================================\nSCHEDULE\n-- ------------------------------------------------------------------------------\n-- SCHEDULE SECTION - 2020-01-01\n-- ------------------------------------------------------------------------------\nRPTSCHED\n'WELLS=2' 'WELSPECS' 'CPU=2' FIP=2' /\nDATES\n1 APR 2021 /\n/\n--\n-- WRITE OUT SAVE FILE FOR FAST RESTARTS\n--\nSAVE\nDATES\n1 JLY 2021 /\n1 OCT 2021 /\n/\nHere OPM Flow will write out a RESTART file instead of a SAVE file at April 1st, 2021.","expected_columns":1,"size_kind":"fixed","size_count":1},"SCDPDIMS":{"name":"SCDPDIMS","sections":["RUNSPEC"],"supported":false,"summary":"The SCDPDIMS keyword defines the number of tables used in the Scale Deposition option and the maximum number of entries for the various tables.","parameters":[{"index":1,"name":"NTSCDP","description":"NTSCDP is a positive integer that defines the number of SCDPTAB scale deposition tables used in the Scale Deposition option.","units":{},"default":"0","value_type":"INT"},{"index":2,"name":"NPSCDP","description":"NPSCDP is a positive integer that defines the maximum number of entries (or rows) in any one SCDPTAB scale deposition table defined in the input deck.","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"NTSCDA","description":"NTSCDA is a positive integer that defines the number of SCDATAB scale damage tables used in the Scale Deposition option.","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"NPSCDA","description":"NPSCDA is a positive integer that defines the maximum number of entries (or rows) in any one SCDATAB scale damage table defined in the input deck.","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"Not Used","description":"","units":{},"default":"1*","value_type":"INT"},{"index":6,"name":"Not Used","description":"","units":{},"default":"1*","value_type":"INT"},{"index":7,"name":"NTSCDE","description":"NTSCDE is a positive integer that defines the number of SCDETAB karst aquifer dissolution tables used in the Scale Deposition option.","units":{},"default":"0","value_type":"INT"}],"example":"--\n-- NO. MAX NO. MAX NOT NOT NO.\n-- NTSCDP NPSCDP NTSCDA NPSCDA USED USED NTSCDE\nSCDPDIMS\n5 10 4 10 1* 1* 3 /\nThe above example defines the number of SCDPTAB scale deposition tables to be five with a maximum number of rows for each table set to 10, the maximum number of SCDATAB scale damage tables to be four with a maximum number of 10 rows per table, and the maximum number of SCDETAB karst aquifer dissolution tables to be three.","expected_columns":7,"size_kind":"fixed","size_count":1},"SKIP":{"name":"SKIP","sections":["RUNSPEC","GRID","EDIT","PROPS","REGIONS","SOLUTION","SUMMARY","SCHEDULE"],"supported":null,"summary":"The SKIP keyword activates skipping of all keywords and input data until the ENDSKIP keyword is encountered. All keywords between the SKIP and ENDSKIP keywords are ignored.","parameters":[],"example":"","size_kind":"none","size_count":0},"SKIP100":{"name":"SKIP100","sections":["RUNSPEC","GRID","EDIT","PROPS","REGIONS","SOLUTION","SUMMARY","SCHEDULE"],"supported":null,"summary":"The SKIP100 keyword activates skipping of all keywords and input data by the commercial black-oil simulator until the ENDSKIP keyword is encountered. All keywords between the SKIP100 and ENDSKIP keywords are ignored by the commercial black-oil simulator. The SKIP100 keyword is ignored by the commercial compositional simulator.","parameters":[],"example":"","size_kind":"none","size_count":0},"SKIP300":{"name":"SKIP300","sections":["RUNSPEC","GRID","EDIT","PROPS","REGIONS","SOLUTION","SUMMARY","SCHEDULE"],"supported":null,"summary":"The SKIP300 keyword activates skipping of all keywords and input data by the commercial compositional simulator until the ENDSKIP keyword is encountered. All keywords between the SKIP300 and ENDSKIP keywords are ignored by the commercial compositional simulator. The SKIP300 keyword is ignored by the commercial black-oil simulator.","parameters":[],"example":"","size_kind":"none","size_count":0},"SMRYDIMS":{"name":"SMRYDIMS","sections":["RUNSPEC"],"supported":null,"summary":"The SMRYDIMS keyword defines the maximum number of summary vectors to be written out to the SUMMARY file (*.SUMMARY).","parameters":[{"index":1,"name":"NSUMMX","description":"A positive integer that defines the maximum number of summary vectors to be written out to the SUMMARY file (*.SUMMARY).","units":{},"default":"10000","value_type":"INT"}],"example":"--\n-- SET THE MAXIMUM NUMBER OF SUMMARY VECTORS THAT CAN BE WRITTEN OUT\n--\nSMRYDIMS\n10000 /\nThe above example sets maximum number of summary vectors that can be written out to the SUMMARY file to the default value of 10,000; however, this has no effect in OPM Flow input decks.","expected_columns":1,"size_kind":"fixed","size_count":1},"SOLVDIMS":{"name":"SOLVDIMS","sections":["RUNSPEC","GRID"],"supported":false,"summary":"The SOLVDIMS defines the unstructured Perpendicular Bisector (“PEBI”)101\n Heinemann, Z.E. and Brand, C.W. 1988. Gridding Techniques in Reservoir Simulation. Proc., First Intl. Forum on Reservoir Simulation, Alpbach, Austria, 339. and 102\n Heinemann, Z.E., Brand, C.W., Munka, M. et al. 1991. Modeling Reservoir Geometry With Irregular Grids. SPE Res Eng 6 (2): 225–232. SPE-18412-PA. http://dx.doi.org/10.2118/18412-PAgrid nested factorization solver dimensions. This keyword is generated by an external pre-processing program for generating simulation grids.","parameters":[],"example":"","size_kind":"array"},"SOLVENT":{"name":"SOLVENT","sections":["RUNSPEC"],"supported":null,"summary":"This keyword indicates that the solvent phase is present in the model and to activate the four component solvent model for this run. In addition to this keyword, the oil, water and gases phases should also be declared for the run using the OIL, WATER and GAS keywords. The keyword will also invoke data input file checking to ensure that all the required Solvent phase input parameters are defined in the input deck.","parameters":[],"example":"--\n-- SOLVENT PHASE IS PRESENT IN THE RUN\n--\nSOLVENT\nThe above example declares that the solvent phase is active in the model.","size_kind":"none","size_count":0},"SPIDER":{"name":"SPIDER","sections":["RUNSPEC"],"supported":null,"summary":"SPIDER activates the OPM Flow spider grid geometry option for the model, if this keyword and the RADIAL keyword are omitted then Cartesian geometry is assumed by OPM Flow. Note that is an OPM Flow specific keyword and option.","parameters":[],"example":"--\n-- DEFINE SPIDER GRID GEOMETRY (OPM FLOW RADIAL GRID KEYWORD)\n--\nSPIDER\nThe above example actives OPM Flow’s spider grid geometry option.","size_kind":"none","size_count":0},"START":{"name":"START","sections":["RUNSPEC"],"supported":null,"summary":"This keyword sets the start date for the simulation switches. If the DATES keyword is to be used during the simulation, then a start date should be entered.","parameters":[{"index":1,"name":"DAY","description":"A positive integer that defines the day of the month, the value should be greater than or equal to one and less than or equal to 31.","units":{},"default":"None","value_type":"INT"},{"index":2,"name":"MONTH","description":"Character string for the month and should be one of the following 'JAN', 'FEB', 'MAR', 'APR', 'MAY', 'JUN', 'JUL' (or 'JLY'), 'AUG', 'SEP', 'OCT', 'NOV', or 'DEC'","units":{},"default":"None","value_type":"STRING"},{"index":3,"name":"YEAR","description":"A positive four digit integer value of the start year, which must be specified fully by four digits, that is 1986.","units":{},"default":"None","value_type":"INT"},{"index":4,"name":"TIME","description":"","units":{},"default":"00:00:00.000","value_type":"STRING"}],"example":"--\n-- DEFINE THE START DATE FOR THE RUN\n--\nSTART\n01 'JAN' 2014 /\nThe above example sets the start date for the run to be January 1, 2014.\nNote\nWhenever possible it is a good idea to always set the start date to be at the beginning of the year as per the example. As like most simulators, OPM Flow reports are always stated at the number of days from the start date (and sometimes at a given date). If the start date is at the beginning of the year, then calculating the actual date is relatively straight forward and simple.\n| Note Whenever possible it is a good idea to always set the start date to be at the beginning of the year as per the example. As like most simulators, OPM Flow reports are always stated at the number of days from the start date (and sometimes at a given date). If the start date is at the beginning of the year, then calculating the actual date is relatively straight forward and simple. |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":4,"size_kind":"fixed","size_count":1},"SURFACT":{"name":"SURFACT","sections":["RUNSPEC"],"supported":false,"summary":"This keyword indicates that the surfactant phase is present in the model and to activate the surfactant flooding model. The keyword will also invoke data input file checking to ensure that all the required surfactant phase input parameters are defined in the input deck. See also the SURFACTW keyword in the RUNSPEC section that actives the surfactant phase, but with the changes to the wettability option activated as well.","parameters":[],"example":"--\n-- ACTIVATE THE SURFACTANT PHASE IN THE MODEL\n--\nSURFACT\nThe above example declares that the surfactant phase is active in the model.","size_kind":"none","size_count":0},"SURFACTW":{"name":"SURFACTW","sections":["RUNSPEC"],"supported":false,"summary":"This keyword indicates that the surfactant phase is present in the model and to activate the surfactant flooding mode with Changes to Wettability option activated as well. The keyword will also invoke data input file checking to ensure that all the required surfactant phase input parameters are defined in the input deck. See also the SURFACT keyword in the RUNSPEC section that actives the surfactant phase only, that is without the Changes to the Wettability option.","parameters":[],"example":"--\n-- ACTIVATE THE SURFACTANT PHASE WITH WETTABILITY CHANGES IN THE MODEL\n--\nSURFACTW\nThe above example declares that the surfactant phase is active in the model together with the wettability changes.","size_kind":"none","size_count":0},"TABDIMS":{"name":"TABDIMS","sections":["RUNSPEC"],"supported":null,"summary":"The TABDIMS keyword defines the maximum number of tables for a given table type dataset and the maximum number of entries for the various tables. The commercial simulator combines both the black-oil and compositional simulator variables on this keyword; however, although all the parameters are explained below only the black-oil parameters are used by OPM Flow.","parameters":[{"index":1,"name":"NTSFUN","description":"A positive integer that defines the number of relative permeability table sets defined in the input deck. The tables are allocated to different parts of the grid by the SATNUM keyword.","units":{},"default":"1","value_type":"INT"},{"index":2,"name":"NTPVT","description":"A positive integer that defines the number of fluid property table sets defined in the input deck. The tables are allocated to different parts of the grid by the PVTNUM keyword.","units":{},"default":"1","value_type":"INT"},{"index":3,"name":"NSSFUN","description":"A positive integer that defines the maximum number of saturation entries in the relative permeability tables defined in the input deck.","units":{},"default":"20","value_type":"INT"},{"index":4,"name":"NPPVT","description":"A positive integer that defines the maximum number of pressure entries in the PVT tables.","units":{},"default":"20","value_type":"INT"},{"index":5,"name":"NTFIP","description":"A positive integer defining the maximum number of regions in the FIPNUM region array. Note that this parameter may also be set on the REGDIMS keyword as well. If NTFIP is set in both places then the maximum value is used.","units":{},"default":"1","value_type":"INT"},{"index":6,"name":"NRPVT","description":"A positive integer that defines the maximum number of Rs and Rv entries in the PVT tables. If the DISGAS and VAPOIL options have not been activated then this parameter is ignored.","units":{},"default":"20","value_type":"INT"},{"index":7,"name":"NRVPVT","description":"A positive integer that defines the maximum number of Rv entries in the PVT tables for the commercial compositional simulator.","units":{},"default":"20","value_type":"INT"},{"index":8,"name":"NTENDP","description":"A positive integer that defines the maximum number of saturation end-point depth tables. The end-point depth tables are used to re-scale the saturation tables as a function of depth as oppose to being a grid block property. NTENDP may also be specified on the ENDSCALE keyword, and if specified on both here and on the ENDSCALE keyword the maximum value of the two is used.","units":{},"default":"1","value_type":"INT"},{"index":9,"name":"NMEOSR","description":"A positive integer that defines the maximum number of reservoir equations of states for the commercial compositional simulator.","units":{},"default":"1","value_type":"INT"},{"index":10,"name":"NMEOSS","description":"A positive integer that defines the maximum number of separator or surface equations of states for the commercial compositional simulator.","units":{},"default":"1","value_type":"INT"},{"index":11,"name":"MXNFLX","description":"A positive integer defining the maximum number flux regions in the FLUXNUM region array. MXNFLX can also be defined on the REGDIMS keywords as well. If MXNFLX is defined both here and on the REGDIMS keyword then the maximum value of the two is used.","units":{},"default":"10","value_type":"INT"},{"index":12,"name":"MXNTHR","description":"A positive integer that defines the maximum number of thermal regions for the commercial compositional simulator.","units":{},"default":"1","value_type":"INT"},{"index":13,"name":"NTROCC","description":"A positive integer that defines the number of rock compressibility entries enter by the ROCK keyword defined in the input deck. The ROCK data is allocated to different parts of the grid by the either the PVTNUM or ROCKNUM keywords in the REGIONS section. If NTROCC is defaulted then the PVTNUM array will be used to allocate the ROCK keyword data to the grid blocks; whereas, if a value is entered then the ROCKNUM array will be used instead. See also the ROCKOPTS keyword in the PROPS section that can be used to redefine if the PVTNUM, ROCKNUM or SATNUM arrays should be employed to allocate the ROCK keyword data.","units":{},"default":"1*","value_type":"INT"},{"index":14,"name":"MXNPMR","description":"A positive integer that defines the maximum number of pressure maintenance regions for the commercial compositional simulator.","units":{},"default":"0","value_type":"INT"},{"index":15,"name":"NTABKT","description":"A positive integer that defines the maximum number of temperature dependent K-value tables for the when the thermal option is activated in the commercial compositional simulator.","units":{},"default":"0","value_type":"INT"},{"index":16,"name":"NTALPHA","description":"A positive integer that defines the maximum number of transport coefficient tables for the commercial compositional simulator.","units":{},"default":"0","value_type":"INT"},{"index":17,"name":"NASPKA","description":"A positive integer that defines the maximum number of maximum number of entries in the ASPKDAM keyword tables for the commercial compositional simulator.","units":{},"default":"10","value_type":"INT"},{"index":18,"name":"MXRAWG","description":"A positive integer that defines the maximum number of maximum number of entries in the ASPREWG keyword tables for the commercial compositional simulator.","units":{},"default":"10","value_type":"INT"},{"index":19,"name":"MXRASO","description":"A positive integer that defines the maximum number of pressure maintenance regions for the commercial compositional simulator.","units":{},"default":"10","value_type":"INT"},{"index":20,"name":"","description":"Not Used","units":{},"default":"1*","value_type":"STRING"},{"index":21,"name":"MCASPP","description":"A positive integer that defines the maximum number of column entries in the ASPPW2D keyword tables for the commercial compositional simulator.","units":{},"default":"5","value_type":"INT"},{"index":22,"name":"MRASPP","description":"A positive integer that defines the maximum number of row entries in the ASPPW2D keyword tables for the commercial compositional simulator.","units":{},"default":"5","value_type":"INT"},{"index":23,"name":"MXRATF","description":"A positive integer that defines the maximum number of entries in the ASPWETF table for the commercial compositional simulator.","units":{},"default":"5","value_type":"INT"},{"index":24,"name":"MXNKVT","description":"A positive integer that defines the maximum number of composition dependent K-value tables for the commercial compositional simulator.","units":{},"default":"0","value_type":"INT"},{"index":25,"name":"RESVED","description":"Not Used","units":{},"default":"1*","value_type":"STRING"}],"example":"--\n-- NO. NO. MAX MAX MAX MAX E300\n-- NTSFUN NTPVT NSSFUN NPPVT NTFIP NRPVT BLANK NTEND\nTABDIMS\n15 9 40 30 1* 1* 1* 1 /\nThe above example defines number of relative permeability tables to be 15 with a maximum number of rows for each table set to 40, and the number of PVT tables to be nine with a maximum number of 30 rows per table.","expected_columns":25,"size_kind":"fixed","size_count":1},"TEMP":{"name":"TEMP","sections":["RUNSPEC"],"supported":null,"summary":"This keyword activates the temperature modeling option.","parameters":[],"example":"--\n-- ACTIVATE THE TEMPERATURE MODELING OPTION (OPM FLOW TEMPERATURE OPTION ONLY)\n--\nTEMP\nThe above example activates the temperature modeling option.","size_kind":"none","size_count":0},"THERMAL":{"name":"THERMAL","sections":["RUNSPEC"],"supported":null,"summary":"This keyword activates the thermal modeling option.","parameters":[],"example":"--\n-- ACTIVATE THE THERMAL MODELING OPTION (OPM FLOW THERMAL OPTION ONLY)\n--\nTHERMAL\nThe above example activates the thermal modeling option.\n| Section | Keyword | Function | OPM Flow | Commercial Simulator | |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------|----------|----------------------|--|\n| THERMAL MODEL | TEMP MODEL | THERMAL MODEL | | | |\n| RUNSPEC | ROCKDIMS | Thermal Rock Dimensions of Over and Underburden Rock Types | | | |\n| TEMP | Activate the Temperature Modeling Option | | | Black-Oil | |\n| THERMAL | Activate the Thermal Mo","size_kind":"none","size_count":0},"TITLE":{"name":"TITLE","sections":["RUNSPEC"],"supported":null,"summary":"The TITLE keyword defines the title for the input deck. The title text will be printed on all reports so as to act as a reference for the run.","parameters":[{"index":1,"name":"TITLE","description":"A character string that defines the title for the input deck","units":{},"default":"None","value_type":"STRING"}],"example":"--\n-- DEFINE THE TITLE FOR THE RUN\nTITLE\nSPE01-THEM01-OPM1810-R01 - OPM THERMAL OPTION RUN\nThe above example defines the title for the run to be “SPE01-THEM01-OPM1810-R01 - OPM THERMAL OPTION RUN”.\n| Note It is good practice to include the name of the input file in the tittle (without the extension) for when cross checking results from multiple cases. |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"none","variadic_record":true},"TRACERS":{"name":"TRACERS","sections":["RUNSPEC"],"supported":true,"summary":"The TRACERS keyword defines the number of tracers in the model and the various passive tracer tracking options.","parameters":[{"index":1,"name":"MXOILTR","description":"A positive integer defining the maximum number of passive oil tracers defined using the TRACER keyword.","units":{},"default":"0","value_type":"INT"},{"index":2,"name":"MXWATTR","description":"A positive integer defining the maximum number of passive water tracers defined using the TRACER keyword.","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"MXGASTR","description":"A positive integer defining the maximum number of passive gas tracers defined using the TRACER keyword.","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"MXENVTR","description":"A positive integer defining the maximum number of passive environmental tracers defined using the TRACER keyword. Environmental tracers are used with the Environment Tracer model that takes into account tracer adsorption and decay. Only the default value of zero is currently supported.","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"DIFFOPT","description":"A character string defining the numerical diffusion option for tracer tracking runs that should be set to: DIFF activates the numerical diffusion control options. NODIFF deactivates the numerical diffusion control options. Only the default value of NODIFF is supported","units":{},"default":"NODIFF","value_type":"STRING"},{"index":6,"name":"MXITRTR","description":"A positive integer defining the maximum number of non-linear iterations to be used when the tracer option is activated.","units":{},"default":"12","value_type":"INT"},{"index":7,"name":"MNITRTR","description":"A positive integer defining the minimum number of non-linear iterations to be used when the tracer option is activated.","units":{},"default":"1","value_type":"INT"},{"index":8,"name":"NONLIN","description":"A character string stating if passive tracers as should be linear (NO) or non-linear (YES). Only the default value of NO is supported.","units":{},"default":"No","value_type":"STRING"},{"index":9,"name":"LNCONFAC","description":"A real value defining the initial linear convergence factor. The default value of 1* means the parameter will not be utilized.","units":{},"default":"1*","value_type":"INT"},{"index":10,"name":"NLCONFAC","description":"A real value defining the initial non-linear convergence factor. The default value of 1* means the parameter will not be utilized.","units":{},"default":"1*","value_type":"INT"},{"index":11,"name":"CONFAC","description":"A real value defining the LNCONFAC and NLCONFAC convergence factors to be used after the initial convergence factor has been applied.","units":{},"default":"1.0","value_type":"DOUBLE"},{"index":12,"name":"NUMCONF","description":"A positive integer defining the maximum number of times CONFAC can be used.","units":{},"default":"0","value_type":"INT"}],"example":"--\n-- NO OIL NO WAT NO GAS NO ENV DIFF MAX MIN TRACER\n-- TRACERS TRACERS TRACERS TRACERS CONTL NONLIN NONLIN NONLIN\nTRACERS\n0 7 1 0 'NODIFF' 1* 1* 1* /\nThe above example defines seven tracers in the water phase and one tracer in the gas phase.","expected_columns":12,"size_kind":"fixed","size_count":1},"TRPLPORO":{"name":"TRPLPORO","sections":["RUNSPEC"],"supported":false,"summary":"The TRPLPORO keyword activates the Triple Porosity Model option that models matrix, fractures and vuggy porosity for carbonate reservoirs, and specifies the number of matrix porosity systems","parameters":[{"index":1,"name":"TRPLPORO","description":"A positive integer value that specifies the number of matrix porosity systems in the model. TRPLPORO should be set to either: TRPLPORO set equal to 2, if the vugs are only connected to the fractures, so that the porosity system is matrix and connected vugs, or, TRPLPORO set equal to 3, if the vugs are connected to the fractures and the matrix, so that the porosity system is matrix, connected vugs, and isolated vugs.","units":{},"default":"1","value_type":"INT"}],"example":"--\n-- TRPLPORO\n-- OPTION\nTRPLPORO\n3 /\nThe above example activates the Triple Porosity Model option and specifies the porosity system is matrix, connected vugs, and isolated vugs.","expected_columns":1,"size_kind":"fixed","size_count":1},"UDADIMS":{"name":"UDADIMS","sections":["RUNSPEC"],"supported":null,"summary":"This keyword defines the dimensions of the User Defined Arguments (“UDA”) used by OPM Flow that can be applied to various connection, group, and well keywords in the SCHEDULE section. UDAs are defined by the UDQ keyword that is used to specify values to be constants, SUMMARY variables, as defined in SUMMARY section, or a formula using various mathematical functions together with constants and SUMMARY variables.","parameters":[{"index":1,"name":"NMUDA","description":"NMUDA is a positive integer that defines the number of arguments in a SCHEDULE section keyword, that are replaced by numeric UDQ values.","units":{},"default":"0","value_type":"INT"},{"index":2,"name":"IGNORED","description":"Not used and should be defaulted.","units":{},"default":"1*","value_type":"INT"},{"index":3,"name":"MXUDA","description":"MXUDA is a positive integer that defines the maximum number of unique arguments in a keyword that are replaced by numeric UDA values. Note that MXUDA differs from NMUDA, for example: If only the oil rate argument of, say the WCONPROD keyword is specified by a UDA, then both NMUDA and MXUDA equal one. However, if a second WCONPROD uses a different UDA, then NMUDA equals two, but MXUDA would still be one. Finally, if the same two distinct UDAs are used separately in two lines of WCONPROD data, then both NMUDA and MXUDA must be set to two. As MXUDA’s default value is 100 then this only needs to be increased where the same UDA is used more than 100 times.","units":{},"default":"100","value_type":"INT"}],"example":"--\n-- USER DEFINED ARGUMENT DIMENSIONS\n-- NO. NOT TOTAL\n-- ARGS USED UDQ\nUDADIMS\n10 1* 10 /\nIn the above example both NMUDA and MXUDA are set equal to ten.","expected_columns":3,"size_kind":"fixed","size_count":1},"UDQDIMS":{"name":"UDQDIMS","sections":["RUNSPEC"],"supported":false,"summary":"This keyword defines the dimensions associated with the UDQ keyword used in OPM Flow to calculate various user defined values in the SCHEDULE section. The UDQ keyword defined variables can be constants, SUMMARY variables, as defined in the SUMMARY section, or a formula using various mathematical functions together with constants and SUMMARY variables.","parameters":[{"index":1,"name":"MXFUNS","description":"A positive integer that defines the maximum number of functions that can be included when defining a UDQ definition. This should also include any brackets that will be used in the UDQ definition.","units":{},"default":"16","value_type":"INT"},{"index":2,"name":"MXITEMS","description":"MXITEMS is a positive integer that defines the maximum number of ITEMS allowed in an UDQ definition.","units":{},"default":"16","value_type":"INT"},{"index":3,"name":"MXUDC","description":"MXUDC is a positive integer that defines the maximum number of user defined CONNECTION quantities allowed in an UDQ definition.","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"MXUDF","description":"MXUDF is a positive integer that defines the maximum number of user defined FIELD quantities allowed in an UDQ definition.","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"MXUDG","description":"MXUDG is a positive integer that defines the maximum number of user defined GROUP quantities allowed in an UDQ definition.","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"MXUDR","description":"MXUDR is a positive integer that defines the maximum number of user defined REGION quantities allowed in an UDQ definition.","units":{},"default":"0","value_type":"INT"},{"index":7,"name":"MXUDS","description":"MXUDS is a positive integer that defines the maximum number of user defined SEGMENT quantities allowed in an UDQ definition.","units":{},"default":"0","value_type":"INT"},{"index":8,"name":"MXUDW","description":"MXUDW is a positive integer that defines the maximum number of user defined WELL quantities allowed in an UDQ definition.","units":{},"default":"0","value_type":"INT"},{"index":9,"name":"MXUDA","description":"MXUDA is a positive integer that defines the maximum number of user defined AQUIFER quantities allowed in an UDQ definition.","units":{},"default":"0","value_type":"INT"},{"index":10,"name":"MXUDB","description":"MXUDB is a positive integer that defines the maximum number of user defined BLOCK quantities allowed in an UDQ definition.","units":{},"default":"0","value_type":"INT"},{"index":11,"name":"RSEED","description":"RSEED is a character string that determines if a new random number seed should be generated for restart runs for use in the UDQ functions RANDN, RANDU RRNDN and RRNDU. If RSEED is set to Y than a new seed will be generated and if set to the default value of N or 1* then the same seed of the “base” simulation will be employed. See also the RSEED integer variable on the UDQPARAM keyword in the RUNSPEC section to set the random number seed for the current run. This feature is not supported by OPM Flow.","units":{},"default":"N","value_type":"STRING"}],"example":"--\n-- USER DEFINED ARGUMENT DIMENSIONS FACILITY\n-- MAX MAX MAX MAX MAX MAX MAX MAX MAX MAX RAND\n-- FUNCS ITEMS CONNS FIELD GROUP REGS SEGTM WELL AQUF BLCKS OPT\nUDQDIMS\n50 25 0 50 50 0 0 0 0 0 N /\nIn this case the maximum number of functions that can be included when defining a UDQ definition is set to 50, maximum number of items allowed in an UDQ definition is 25, the maximum number of user defined field quantities allowed in an UDQ definition is 50, and the maximum number of user defined group quantities allowed in an UDQ definition is also 50. All other parameters are defaulted including the RSEED variable (the same seed of the “base” simulation will be employed).","expected_columns":11,"size_kind":"fixed","size_count":1},"UDQPARAM":{"name":"UDQPARAM","sections":["RUNSPEC"],"supported":false,"summary":"This keyword defines the dimensions of the User Defined Arguments (“UDA”) used by OPM Flow that can be applied to various connection, group, and well keywords in the SCHEDULE section. UDAs are defined by the UDQ keyword that is used to specify values to be constants, SUMMARY variables, as defined in SUMMARY section, or a formula using various mathematical functions together with constants and SUMMARY variables.","parameters":[{"index":1,"name":"RSEED","description":"RSEED is a positive integer greater than zero that sets a new random number seed for use in the UDQ functions RANDN, RANDU RRNDN and RRNDU. See also the RSEED character variable on the UDQDIMS keyword in the RUNSPEC section to default the random number seed for a restart run. This feature is not supported by OPM Flow.","units":{},"default":"1","value_type":"INT"},{"index":2,"name":"RANGE","description":"RANGE is a real positive value greater than or equal to one and less than or equal to 1.0 x 1020, that sets the absolute range for the user defined quantities. The default value of 1 x 1020 sets the range from -1 x 1020 to +1 x 1020.","units":{},"default":"1 x 1020","value_type":"DOUBLE"},{"index":3,"name":"DEFAULT","description":"DEFAULT is real value that is the default numerical value given to undefined UDQ variables and should be in the same range as RANGE.","units":{},"default":"0.0","value_type":"DOUBLE"},{"index":4,"name":"TOLUDQ","description":"TOLUDQ a real positive number greater than zero and less than one that defines the tolerance used to determine if two real values are equal. Floating-point numbers (as implemented in computers) are never exact, one cannot compare floating point numbers for exact equality. Thus, TOLUDQ defines a tolerance. For example, the default value of 1 x 10-4 means that if the difference between two real values is less than 1 x 10-4 then the values are considered equal.","units":{},"default":"1 x 10-4","value_type":"DOUBLE"}],"example":"--\n-- USER DEFINED DEFAULT VALUES\n-- SEED RANGE UNDEFINED COMPARISON\n-- INTG -AND+ VALUE TOLERANCE\nUDQPARAM\n1 1.0E20 0.0 1.0E-4 /\nThe example explicitly sets the default values for all four variables on the UDAPARAM keyword, namely the random seed to one, the range to 1 x 1020, the undefined UDQ variables to zero, and the comparison tolerance to 1.0 x 10-4.","expected_columns":4,"size_kind":"fixed","size_count":1},"UDTDIMS":{"name":"UDTDIMS","sections":["RUNSPEC"],"supported":true,"summary":"This keyword defines the dimensions of the User Defined Tables (“UDT”) used by OPM Flow that can be used as lookup tables when assigning values to User Defined Quantities (\"UDQ\") using the UDQ keyword in the SCHEDULE section. UDTs are defined by the UDT keyword in the SCHEDULE section.","parameters":[{"index":1,"name":"MXUDT","description":"MXUDT is a positive integer that defines the maximum number of User Defined Tables","units":{},"default":"0","value_type":"INT"},{"index":2,"name":"NUDT","description":"NUDT is a positive integer that defines the maximum number of rows in any given User Defined Table.","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"MXINTP","description":"MXINTP is a positive integer that defines the maximum number of interpolation points allowed in any given dimension.","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"MXDIMS","description":"MXDIMS is a positive integer that defines the maximum number of dimensions in any given User Defined Table. Only one dimensional tables are currently supported by OPM Flow.","units":{},"default":"0","value_type":"INT"}],"example":"--\n-- USER DEFINED TABLE DIMENSIONS\n--\n-- MAX MAX MAX MAX\n-- TABLES ROWS INTPOL DIMS\nUDTDIMS\n3 20 3 2 /\nIn the above example the maximum number of UDT tables is set to three and the maximum number of rows for each table is 20, the maximum number of interpolation points in any given dimension is set to three and the maximum number of dimensions is defined as two.","expected_columns":4,"size_kind":"fixed","size_count":1},"UNCODHMD":{"name":"UNCODHMD","sections":["RUNSPEC"],"supported":false,"summary":"UNCODHMD activates the history match gradient unencoded output for the history match gradient output file. Unencoded files allows external programs to read this file type.","parameters":[],"example":"--\n-- ACTIVATE HISTORY MATCH GRADIENT UNENCODED OUTPUT\n--\nUNCODHMD\nThe above example switches on the unified output file option.","size_kind":"none","size_count":0},"UNIFIN":{"name":"UNIFIN","sections":["RUNSPEC"],"supported":null,"summary":"This keyword switches on the Unified Input Files option for all input files. Similar to the commercial simulator, OPM Flow has various options for reading various input files and writing the resulting OPM Flow output files as described in Table 5.54.","parameters":[],"example":"--\n-- SWITCH ON THE UNIFIED INPUT FILES OPTION\n--\nUNIFIN\nThe above example switches on the unified input file option.\n| Process | Keyword | Description | Files |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|\n| Input | FMTIN ","size_kind":"none","size_count":0},"UNIFOUT":{"name":"UNIFOUT","sections":["RUNSPEC"],"supported":null,"summary":"This keyword switches on the Unified Output Files option for all output files. Similar to the commercial simulator, OPM Flow has various options for reading various input files and writing the resulting OPM Flow output files as described in Table 5.55.","parameters":[],"example":"--\n-- SWITCH ON THE UNIFIED OUTPUT FILES OPTION\n--\nUNIFOUT\nThe above example switches on the unified output file option.\n| Process | Keyword | Description | Files |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|\n| Input | FMTIN ","size_kind":"none","size_count":0},"UNIFOUTS":{"name":"UNIFOUTS","sections":["RUNSPEC"],"supported":false,"summary":"The UNIFOUTS keyword causes the SUMMARY file output files to be a unified file, as opposed to non-unified multiple files. A unified file is a single file containing output for each reporting time step. Here a single SUMMARY file will be generated, as opposed to one file per report time step. See also the MULTOUT keyword in the RUNSPEC section that sets both the SUMMARY and RESTART files to be non-unified multiple files, as opposed to unified files. Note also that UNIFOUTS keyword has precedence over the MULTOUT keyword for SUMMARY files.","parameters":[],"example":"--\n-- ACTIVATE THE UNIFIED OUTPUT SUMMARY FILE OPTION\n--\nUNIFOUTS\nThe above example switches on writing of unified SUMMARY output files.","size_kind":"none","size_count":0},"UNIFSAVE":{"name":"UNIFSAVE","sections":["RUNSPEC"],"supported":false,"summary":"The UNIFSAVE keyword causes the SAVE file output file to be a unified file, as opposed to non-unified multiple files. A unified file is a single file containing output for each reporting time step. Here a single SAVE file will be generated, as opposed to one file per report time step. See also the MULTOUT keyword in the RUNSPEC section that sets both the SUMMARY and RESTART files to be non-unified multiple files, as opposed to unified files.","parameters":[],"example":"--\n-- ACTIVATE THE UNIFIED OUTPUT SAVE FILE OPTION\n--\nUNIFSAVE\nThe above example switches on writing of unified SAVE output files.","size_kind":"none","size_count":0},"VAPOIL":{"name":"VAPOIL","sections":["RUNSPEC"],"supported":null,"summary":"This keyword indicates that vaporized oil (more commonly referred to as condensate) is present in wet103\n Natural gas that contains significant heavy hydrocarbons such as propane, butane and other liquid hydrocarbons is known as wet gas or rich gas. The general rule of thumb is if the gas contains less methane (typically less than 85% methane) and more ethane, and other more complex hydrocarbons, it is labeled as wet gas. Wet gas normally has GOR's less than 100,000 scf/stb or 18,000 Sm3/m3, with the condensate having a gravity greater than 50 oAPI. gas in the model and the keyword should only be used if the there is both oil and gas phases in the model. The keyword may be used for gas-water and oil-water-gas input decks that contain the oil and gas phases. The keyword will also invoke data input file checking to ensure that all the required oil and gas phase input parameters are defined in the input deck.","parameters":[],"example":"--\n-- VAPORIZED OIL IN WET GAS IS PRESENT IN THE RUN\n--\nVAPOIL\nThe above example declares that the vaporized oil, i.e. condensate, in the gas phase is active in the model.","size_kind":"none","size_count":0},"VAPWAT":{"name":"VAPWAT","sections":["RUNSPEC"],"supported":null,"summary":"This keyword indicates that vaporized water is present in the gas phase and the keyword should only be used if both water and gas phases are present in the model. VAPWAT should also be used in conjunction with the PRECSALT keyword in the RUNSPEC section in order to activate OPM Flow’s Salt Precipitation model. VAPWAT may be used for gas-water and oil-water-gas input decks that contain the oil, gas and water phases.","parameters":[],"example":"--\n-- VAPORIZED WATER IN DRY/WET GAS IS PRESENT IN THE RUN (OPM FLOW KEYWORD)\n--\nVAPWAT\nThe above example declares that the vaporized water is present in the gas phase and is active in the model.\n| Note This is an OPM Flow specific keyword for the simulator’s Water Vaporization Model that is activated by declaring that vaporized water is present in the run. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"none","size_count":0},"VE":{"name":"VE","sections":["RUNSPEC"],"supported":false,"summary":"This keyword actives the Vertical Equilibrium (“VE”) model for the global grid and optionally specifies the type of VE model. The VE model type can either be compressed for merging columns of grid blocks into a single grid block, or uncompressed for the standard VE model.","parameters":[{"index":1,"name":"MODEL_TYPE","description":"","units":{},"default":"NOCOMP","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"VFPIDIMS":{"name":"VFPIDIMS","sections":["RUNSPEC"],"supported":null,"summary":"VFPIDIMS keyword defines the maximum dimensions of the injection well Vertical Lift Performance (“VFP”) tables defined by VFPINJ keyword. The VFP tables for the producing wells are defined by the VFPPDIMS keyword.","parameters":[{"index":1,"name":"MXMFLO","description":"A positive integer that defines the maximum number of injection rate entries for the VFPINJ keyword.","units":{},"default":"0","value_type":"INT"},{"index":2,"name":"MXMTHP","description":"A positive integer that defines the maximum number of THP entries for the VFPINJ keyword.","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"MXVFPTAB","description":"A positive integer that defines the maximum number of VFPINJ tables entered through the VFPINJ keyword.","units":{},"default":"0","value_type":"INT"}],"example":"-- INJECTING VFP TABLES\n-- VFP VFP VFP\n-- MXMFLO MXMTHP NMMVFT\nVFPIDIMS\n10 10 12 /\nThe above example defines that the maximum number of injection rates and THP entries on the VFPINJ keyword is 10, and the number of VFPINJ tables is 12.","expected_columns":3,"size_kind":"fixed","size_count":1},"VFPPDIMS":{"name":"VFPPDIMS","sections":["RUNSPEC"],"supported":null,"summary":"VFPPDIMS keyword defines the maximum dimensions of the production well Vertical Lift Performance (“VFP”) tables defined by VFPPROD keyword. The VFP tables for the injection wells are defined by the VFPIDIMS keyword.","parameters":[{"index":1,"name":"MXMFLO","description":"A positive integer that defines the maximum number of production flow rate entries for the VFPPROD keyword.","units":{},"default":"0","value_type":"INT"},{"index":2,"name":"MXMTHP","description":"A positive integer that defines the maximum number of THP entries for the VFPPROD keyword.","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"MXMWFR","description":"A positive integer that defines the maximum number of water fraction entries (WOR, WCUT, GWR etc.) for the VFPPROD keyword.","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"MXMGFR","description":"A positive integer that defines the maximum number of gas fraction entries (GOR, GLR, OGR etc.) for the VFPPROD keyword.","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"MXMALQ","description":"A positive integer that defines the maximum number of artificial lift quantity entries for the VFPPROD keyword.","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"MXVFPTAB","description":"A positive integer that defines the maximum number of VFPPROD tables entered through the VFPPROD keyword.","units":{},"default":"0","value_type":"INT"}],"example":"-- PRODUCING VFP TABLES\n-- VFP VFP VFP VFP VFP VFP\n-- MXMFLO MXMTHP MXMWFR MXMGFR MXMALQ NMMVFT\nVFPPDIMS\n20 10 10 10 6 9 /\nHere the example shows that there are a maximum of 20 flow rates, 10 THP entries, 10 water and gas fraction entries, and six artificial lift entries for the nine VFPPROD VFP production tables.","expected_columns":6,"size_kind":"fixed","size_count":1},"VISAGE":{"name":"VISAGE","sections":["RUNSPEC"],"supported":false,"summary":"The VISAGE keyword activates the External Reservoir Geo-Mechanics VISAGE option. The keyword should not be used in input decks as the associated data is generated by an external program.","parameters":[],"example":"","size_kind":"none","size_count":0},"VISCD":{"name":"VISCD","sections":["RUNSPEC"],"supported":false,"summary":"The VISCD keyword activates the Dual Porosity Viscous Displacement option for dual porosity and dual permeability models, and therefore requires either the DUALPORO or DUALPERM keyword to be entered in the RUNSPEC section to activate either one of these options. The VISCD option is used to model the viscous displacement of fluids from the matrix by the fracture pressure gradient, for when the fracture system has a more moderate permeability, and flow to and from the matrix caused by the fracture pressure gradient acts as an additional production mechanism105\n Gilman, J. R. and Kazemi, H. “Improved Calculation for Viscous and Gravity Displacement in Matrix Blocks in Dual-Porosity Simulators,” paper SPE 16010 (includes a number of associated papers), Journal of Petroleum Technology (1988) 40, No. 1, 60-70.. Normally this mechanism is ignored as the pressure gradient in the fracture system is small due to the very high permeability of the fracture system. See the LX, LY and LZ keywo...","parameters":[],"example":"--\n-- ACTIVATE DUAL POROSITY VISCOUS DISPLACEMENT OPTION\n--\nVISCD\nThe above example activates the dual porosity viscous displacement option.","size_kind":"none","size_count":0},"WARN":{"name":"WARN","sections":["RUNSPEC","GRID","EDIT","PROPS","REGIONS","SOLUTION","SUMMARY","SCHEDULE"],"supported":null,"summary":"Turns on warning messages to be printed to the print file (*.PRT); note that this keyword is activated by default and can subsequently be switched off by the NOWARN activation keyword. The warning messages may be turned on and off using keywords WARN and NOWARN. OPM Flow always prints error messages.","parameters":[],"example":"","size_kind":"none","size_count":0},"WATER":{"name":"WATER","sections":["RUNSPEC"],"supported":null,"summary":"This keyword indicate that the water phase is present in the model and must be used for gas-water, oil-water, oil-water-gas input decks that contain the water phase. The keyword will also invoke data input file checking to ensure that all the required water phase input parameters are defined in the input deck.","parameters":[],"example":"--\n-- WATER PHASE IS PRESENT IN THE RUN\n--\nWATER\nThe above example declares that the water phase is active in the model.","size_kind":"none","size_count":0},"WELLDIMS":{"name":"WELLDIMS","sections":["RUNSPEC"],"supported":null,"summary":"WELLDIMS defines various well and group dimensions for the run. The commercial simulator combines both the black-oil and compositional simulator variables on this keyword; however, although all the parameters are explained below only the black-oil parameters are used by OPM Flow.","parameters":[{"index":1,"name":"MXWELS","description":"A positive integer defining the maximum number of wells for this model.","units":{},"default":"0","value_type":"INT"},{"index":2,"name":"MXCONS","description":"A positive integer defining the maximum number of grid block connections per well for this model.","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"MXGRPS","description":"A positive integer defining the maximum number of groups for this model.","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"MXGRPW","description":"A positive integer defining the maximum number of wells that can belong to a group in the model and the maximum number of child groups in a group. Note that MXGRPW sets both the maximum number of wells in a group and the maximum number of child groups in a group. The former applies to groups that contain wells and the latter applies to groups that contain other groups. See also the GRUPTREE keyword in the SCHEDULE section to define group hierarchy.","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"MXSTAGE","description":"A positive integer defining the maximum number of stages per separator for this model. This option is ignored by OPM Flow.","units":{},"default":"5","value_type":"INT"},{"index":6,"name":"MXSTRMS","description":"A positive integer defining the maximum number of well streams for this model. This option is ignored by OPM Flow.","units":{},"default":"10","value_type":"INT"},{"index":7,"name":"MXMIXS","description":"A positive integer defining the maximum number of mixtures for this model. This option is ignored by OPM Flow.","units":{},"default":"5","value_type":"INT"},{"index":8,"name":"MXSEPS","description":"A positive integer defining the maximum number of separators for this model. This option is ignored by OPM Flow.","units":{},"default":"4","value_type":"INT"},{"index":9,"name":"MXCOMPS","description":"A positive integer defining the maximum number of mixture components in a mixture for the model. This option is ignored by OPM Flow.","units":{},"default":"3","value_type":"INT"},{"index":10,"name":"MXDOCOMP","description":"A positive integer defining the maximum number of well completions that can cross a parallel run domain boundary when the PARALLEL option has been activated. This option is ignored by OPM Flow.","units":{},"default":"0","value_type":"INT"},{"index":11,"name":"MXWSLIST","description":"A positive integer defining the maximum number of well lists that a well may be concurrent belong to at one time for this model. This option is ignored by OPM Flow.","units":{},"default":"1","value_type":"INT"},{"index":12,"name":"MXWLISTS","description":"A positive integer defining the maximum number of dynamic well lists for this model. This option is ignored by OPM Flow.","units":{},"default":"1","value_type":"INT"},{"index":13,"name":"MXWSECD","description":"A positive integer defining the maximum number of secondary wells for this model. This option is ignored by OPM Flow.","units":{},"default":"10","value_type":"INT"},{"index":14,"name":"MXNGPP","description":"A positive integer defining the maximum number of row entries per completion in the generalized pseudo-pressure tables used for to calculate the blocking factor associated with condensate drop-out in gas condensate reservoirs. If the generalized pseudo-pressure option has not been activated then this is ignored. This option is ignored by OPM Flow.","units":{},"default":"201","value_type":"INT"}],"example":"--\n-- WELL WELL GRUPS GRUPS\n-- MXWELS MXCONS MXGRPS MXGRPW\nWELLDIMS\n60 110 18 40 /\nThe above example defines the maximum number of wells to be 60 with 110 completions per well, and maximum number of groups to be 18 with maximum number of wells per group of 40. All other parameters are defaulted.","expected_columns":14,"size_kind":"fixed","size_count":1},"WPOTCALC":{"name":"WPOTCALC","sections":["RUNSPEC"],"supported":false,"summary":"WPOTCALC defines how shut-in and stopped wells should have their well potentials calculated. Well potentials for wells under these conditions need to have their potentials calculated if they are in a Priority Drilling Queue via the WDRILPRI keyword in the SCHEDULE section, or the Prioritization option has been enabled by the PRIORITY keyword in the SCHEDULE section.","parameters":[{"index":1,"name":"FORCE_CALC","description":"","units":{},"default":"YES","value_type":"STRING"},{"index":2,"name":"USE_SEGMENT_VOLUMES","description":"","units":{},"default":"NO","value_type":"STRING"}],"example":"","expected_columns":2,"size_kind":"fixed","size_count":1},"WSEGDIMS":{"name":"WSEGDIMS","sections":["RUNSPEC"],"supported":null,"summary":"The WSEGSDIMS keyword defines the multi-segment well dimensions for the multi-segment well model and the keyword is obligatory if multi-segment wells are being employed in the model.","parameters":[{"index":1,"name":"MXWELS","description":"A positive integer defining the maximum number of multi-segment wells for this model.","units":{},"default":"0","value_type":"INT"},{"index":2,"name":"MXSEGS","description":"A positive integer defining the maximum number of segments per well for this model.","units":{},"default":"1","value_type":"INT"},{"index":3,"name":"MXBRAN","description":"A positive integer defining the maximum number of branches per multi-segment well, including the main branch groups for this model.","units":{},"default":"1","value_type":"INT"},{"index":4,"name":"MXLINKS","description":"A positive integer defining the maximum number of segment links per multi-segment well. The simulator does not currently support multi-segment chord links, and therefore this parameter is ignored.","units":{},"default":"0","value_type":"INT"}],"example":"--\n-- WELL WELL BRANCH SEGMENT\n-- MXWELS MXSEGS MXBRAN MXLINKS\nWSEGDIMS\n5 100 10 10 /\nThe above example defines the maximum number of multi-segment wells to be five with up to 100 segments per multi-segment well, a maximum number of 10 branches per multi-segment well, and up to 10 segment links per multi-segment well.","expected_columns":4,"size_kind":"fixed","size_count":1},"ACTNUM":{"name":"ACTNUM","sections":["GRID"],"supported":null,"summary":"The ACTNUM keyword specifies which grid blocks are either active or inactive. A grid block is automatically set to inactive if its pore volume is less than the value entered using the MINPV keyword. The ACTNUM keyword can be used to also make blocks with pore volumes greater than MINPV inactive.","parameters":[{"index":1,"name":"ACTNUM","description":"An array of integers equal to either 0 or 1 that define the activity of each cell in the model. A value of 0 indicates the cell is inactive. Grid blocks are ordered with the I index cycling fastest, followed by the J and K indices. Repeat counts may be used, for example 20*1.","units":{},"default":"1"}],"example":"The example below sets several cells to be inactive for a 4 x 5 x 2 model.\nACTNUM\n-- Layer 1\n0 0 1 1\n0 0 1 1\n1 1 1 1\n1 1 1 1\n1 1 1 1\n-- Layer 2\n1 1 1 1\n1 1 1 1\n1 1 1 1\n1 1 1 1\n0 0 0 0\n/\nAlternatively the EQUALS keyword could be employed to accomplish the same task, that is:\n-- -- ARRAY CONSTANT -- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\n'ACTNUM’ 1.0000 1* 1* 1* 1* 1* 1* / SET ACTIVE CELLS\n'ACTNUM’ 0.0000 1 2 1 2 1 1 / SET INACTIVE CELLS\n'ACTNUM’ 0.0000 1 4 5 5 2 2 / SET INACTIVE CELLS\n/","size_kind":"array"},"ADD":{"name":"ADD","sections":["GRID","EDIT","PROPS","REGIONS","SOLUTION"],"supported":true,"summary":"The ADD keyword adds a constant to a specified array or part of an array. The constant can be an integer or real value depending on the array type; however, the arrays that can be operated on are dependent on which section the ADD keyword is being applied in.","parameters":[{"index":1,"name":"ARRAY","description":"A character string of up to eight characters in length that defines the keyword identifying the property to be modified.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"CONSTANT","description":"An integer or real value to be added to the ARRAY in the same units as the ARRAY property.","units":{},"default":"0","value_type":"DOUBLE"},{"index":3,"name":"I1","description":"A positive integer that defines the lower bound of the array in the I-direction to be modified must be greater than or equal 1 and less than or equal to I2 and NX.","units":{},"default":"1","value_type":"INT"},{"index":4,"name":"I2","description":"A positive integer that defines the upper bound of the array in the I-direction to be modified must be greater than or equal to II and less than or equal to NX","units":{},"default":"NX","value_type":"INT"},{"index":5,"name":"J1","description":"A positive integer that defines the lower bound of the array in the J-direction to be modified must be greater than or equal 1 and less than or equal to J2 and NY.","units":{},"default":"1","value_type":"INT"},{"index":6,"name":"J2","description":"A positive integer that defines the upper bound of the array in the J-direction to be modified must be greater than or equal to JI and less than or equal to NY.","units":{},"default":"NY","value_type":"INT"},{"index":7,"name":"K1","description":"A positive integer that defines the lower bound of the array in the K-direction to be modified must be greater than or equal to one and less than or equal to K2 and NZ.","units":{},"default":"1","value_type":"INT"},{"index":8,"name":"K2","description":"A positive integer that defines the upper bound of the array in the K-direction to be modified must be greater than or equal to KI and less than or equal to NZ.","units":{},"default":"NZ","value_type":"INT"}],"example":"--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nADD\nPERMX 20.000 1* 1* 1* 1* 1* 1* / ADD 20 mD TO PERMX\n/\nThe above example adds 20 md to the PERMX property array throughout the model.\n| ADD Keyword and Variable Options by Section | | | | | | |\n|---------------------------------------------|---------|-------|---------|----------|---------|----------|\n| GRID | EDIT | PROPS | REGIONS | SOLUTION | SUMMARY | SCHEDULE |\n| DX | DEPTH | SWL | ENDNUM | PRESSURE | | |\n| DY | PORV | SWCR | EQLNUM | SWAT | | |\n| DZ | TRANX | SWU | FIPNUM | SGAS | | |\n| PERMX | TRANY | SGL | IMBNUM | RV | | |\n| PERMY | TRANZ | SGCR | MISCNUM | RS | | |\n| PERMZ | DIFFX | SGU | PVTNUM | TBLK | | |\n| MULTX | DIFFY | KRW | ROCKNUM | GI | | |\n| MULTY | DIFFZ | KRO | SATNUM | OILAPI | | |\n| MULTZ | TRANR | KRG | WH2NUM | SALT | | |\n| DR | TRANTHT | PCG | | GASCONC | | |\n| DTHETA | DIFFR | PCW | | SOLVCONC | | |\n| PERMR | DIFFTHT | | | SOLVFRAC | | |\n| PERMTHT | | | | SFOAM | | |\n| DZNET | | | | SPOLY | | |\n| PORO | | | | | | |\n| NTG | | | | | | |\n| FLUXNUM | | | | | | |\n| MULTNUM | | | | | | |\n| MPFANUM | | | | | | |\n| DIFFX | | | | | | |\n| DIFFY | | | | | | |\n| DIFFZ | | | | | | |\n| DIFFR | | | | | | |\n| DIFFTHT | | | | | | |","expected_columns":8,"size_kind":"list"},"ADDREG":{"name":"ADDREG","sections":["GRID","EDIT","PROPS","REGIONS","SOLUTION"],"supported":false,"summary":"The ADDREG keyword adds a constant to a specified array or part of an array based on cells with a specific region number. The region number array can be FLUXNUM, MULTNUM or OPERNUM and these arrays must be defined and be available before the ADDREG keyword is read by the simulator. The constant can be an integer or real value depending on the array type; however, the arrays that can be operated on are dependent on which section the ADDREG keyword is being applied in.","parameters":[{"index":1,"name":"ARRAY","description":"A character string of up to eight characters in length that defines the keyword identifying the array to be modified.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"CONSTANT","description":"An integer or real value to be added to the ARRAY in the same units as the ARRAY property for a given REGION.","units":{},"default":"0","value_type":"DOUBLE"},{"index":3,"name":"REGION NUMBER","description":"REGION NUMBER is a positive integer representing the region for which the CONSTANT in (2) should be applied.","units":{},"default":"None","value_type":"INT"},{"index":4,"name":"REGION ARRAY","description":"The REGION ARRAY to use for applying the CONSTANT in (2) based on the REGION NUMBER in (3). REGION ARRAY can have the following values: F for the FLUXNUM array M for the MULTNUM array O for the OPERNUM array","units":{},"default":"M","value_type":"STRING"}],"example":"--\n-- FIRST DEFINE THE PROPERTY ARRAYS AND MULTNUM ARRAYS FOR 10 X 10 X 20 MODEL\n--\n-- ARRAY CONSTANT -- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nPORO 0.2000 1* 1* 1* 1* 1* 1* / PORO TO 0.20 IN MODEL\nPERMX 100.00 1* 1* 1* 1* 1* 1* / PERMX TO 0.10 IN MODEL\nMULTNUM 1 1* 1* 1* 1* 1* 1* / MULTNUM IN MODEL\nMULTNUM 2 1* 5 1 5 6 6 / MULTNUM IN MODEL\nMULTNUM 3 1* 1* 1* 1* 10 10 / MULTNUM IN MODEL\n/\n--\n– NOW RESET PORO AND PERMX BASED ON THE MULTNUM REGION NUMBER\n--\n-- ADD A CONSTANT TO AN ARRAY BASED ON A REGION NUMBER\n--\n-- ARRAY CONSTANT REGION REGION ARRAY\n-- VALUE NUMBER M / F / O ADDREG\nPORO 0.050 1 M /\nPORO 0.100 2 M /\nPORO -0.050 3 M /\nPERMX 25.00 1 M /\nPERMX 100.0 2 M /\nPERMX -50.00 3 M /\n/\nThe example first defines the PORO and PERMX property arrays for the model and then sets the MULTNUM array to 1 for all cells in the model, after which selected areas of model are assigned various MULTNUM integer values. The ADDREG can then be invoked to add or subtract constant values from the PORO and PERMX arrays for the various MULTNUM regions.\n| ADDREG Keyword and Variable Options by Section | | | | | | |\n|------------------------------------------------|---------|-------|---------|----------|---------|----------|\n| GRID | EDIT | PROPS | REGIONS | SOLUTION | SUMMARY | SCHEDULE |\n| DX | DEPTH | SWL | ENDNUM | PRESSURE | | |\n| DY | PORV | SWCR | EQLNUM | SWAT | | |\n| DZ | TRANX | SWU | FIPNUM | SGAS | | |\n| PERMX | TRANY | SGL | IMBNUM | RV | | |\n| PERMY | TRANZ | SGCR | MISCNUM | RS | | |\n| PERMZ | DIFFX | SGU | PVTNUM | TBLK | | |\n| MULTX | DIFFY | KRW | ROCKNUM | GI | | |\n| MULTY | DIFFZ | KRO | SATNUM | OILAPI | | |\n| MULTZ | TRANR | KRG | WH2NUM | SALT | | |\n| DR | TRANTHT | PCG | | GASCONC | | |\n| DTHETA | DIFFR | PCW | | SOLVCONC | | |\n| PERMR | DIFFTHT | | | SOLVFRAC | | |\n| PERMTHT | | | | SFOAM | | |\n| DZNET | | | | SPOLY | | |\n| PORO | | | | | | |\n| NTG | | | | | | |\n| FLUXNUM | | | | | | |\n| MULTNUM | | | | | | |\n| MPFANUM | | | | | | |\n| DIFFX | | | | | | |\n| DIFFY | | | | | | |\n| DIFFZ | | | | | | |\n| DIFFR | | | | | | |\n| DIFFTHT | ","expected_columns":4,"size_kind":"list"},"ADDZCORN":{"name":"ADDZCORN","sections":["GRID"],"supported":false,"summary":"The ADDZCORN keyword adds a constant to the ZCORN array or part of the array based on cells defined in the specified input box. The constant can be real or integer and can be negative or positive.","parameters":[{"index":1,"name":"ADDED_VALUE","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":2,"name":"IX1","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"IX2","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"JY1","description":"","units":{},"default":"","value_type":"INT"},{"index":5,"name":"JY2","description":"","units":{},"default":"","value_type":"INT"},{"index":6,"name":"KZ1","description":"","units":{},"default":"","value_type":"INT"},{"index":7,"name":"KZ2","description":"","units":{},"default":"","value_type":"INT"},{"index":8,"name":"IX1A","description":"","units":{},"default":"-1","value_type":"INT"},{"index":9,"name":"IX2A","description":"","units":{},"default":"-1","value_type":"INT"},{"index":10,"name":"JY1A","description":"","units":{},"default":"-1","value_type":"INT"},{"index":11,"name":"JY2A","description":"","units":{},"default":"-1","value_type":"INT"},{"index":12,"name":"ACTION","description":"","units":{},"default":"BOTH","value_type":"STRING"}],"example":"","expected_columns":12,"size_kind":"list"},"AMALGAM":{"name":"AMALGAM","sections":["GRID"],"supported":false,"summary":"The AMALGAM keyword defines a Cartesian Local Grid Refinements (“LGR”) amalgamations, that is merging several LGRs into one amalgamated LGR.","parameters":[{"index":1,"name":"LGR_GROUPS","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","size_kind":"list","variadic_record":true},"AQUANCON":{"name":"AQUANCON","sections":["GRID","SOLUTION"],"supported":null,"summary":"The AQUANCON keyword defines how analytical aquifers are connected to the simulation grid, this includes the Carter-Tracy, Fetkovich and Constant Flux analytical aquifers, all of which are implemented in OPM Flow. Carter-Tracy analytical aquifers are characterized by the AQUCT keyword in the GRID section and Fetkovich analytical aquifers are defined by the AQUFETP keyword in the SOLUTION section. Finally, the Constant Flux aquifer is defined by the AQUFLUX keyword in SOLUTION section.","parameters":[{"index":1,"name":"AQUID","description":"AQUID is a positive integer greater than or equal to one and less than the maximum number of analytical aquifers as defined by the NANAQU variable on the AQUDIMS keyword in the RUNSPEC section, that defines the aquifer to be connected to the grid.","units":{},"default":"None","value_type":"INT"},{"index":2,"name":"I1","description":"A positive integer that defines the lower bound of the cells in the I-direction to be connected to the aquifer and must be greater than or equal to one and less than or equal to I2 and NX.","units":{},"default":"1","value_type":"INT"},{"index":3,"name":"I2","description":"A positive integer that defines the upper bound of the cells in the I-direction to be connected to the aquifer and must be greater than or equal to I1 and less than or equal to NX","units":{},"default":"NX","value_type":"INT"},{"index":4,"name":"J1","description":"A positive integer that defines the lower bound of the cells in the J-direction to be connected to the aquifer and must be greater than or equal to one and less than or equal to J2 and NY.","units":{},"default":"1","value_type":"INT"},{"index":5,"name":"J2","description":"A positive integer that defines the upper bound of the cells in the J-direction to be connected to the aquifer and must be greater than or equal to JI and less than or equal to NY.","units":{},"default":"NY","value_type":"INT"},{"index":6,"name":"K1","description":"A positive integer that defines the lower bound of the cells in the K-direction to be to be connected to the aquifer and must be greater than or equal to one and less than or equal to K2 and NZ.","units":{},"default":"1","value_type":"INT"},{"index":7,"name":"K2","description":"A positive integer that defines the upper bound of the cells in the K-direction to be connected to the aquifer and must be greater than or equal to KI and less than or equal to NZ.","units":{},"default":"NZ","value_type":"INT"},{"index":8,"name":"AQUFACE","description":"AQUFACE is a character string that sets the connection “face” of the cells declared by this record and should be set to one of the following: X+, Y+, or Z+ for the positive direction, or X-, Y- or Z- for the negative direction transmissibilities. I+, J+, or K+ for the positive direction, or I-, J- or K- for the negative direction transmissibilities.","units":{},"default":"None","value_type":"STRING"},{"index":9,"name":"AQUFLUX","description":"AQUFLUX is a positive real value that sets the fraction of the total influx between the aquifer and the defined cells declared on this keyword. If defaulted the cell face area for each cell is applied and if a value is declared then this value is applied to all cells declared by this record.","units":{"field":"ft2","metric":"m2","laboratory":"cm2"},"default":"1*","value_type":"DOUBLE","dimension":"Length*Length"},{"index":10,"name":"AQUCOEF","description":"AQUCOEF is a real positive values that scales the calculated connection between the aquifer and the cells declared on this record.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0","value_type":"DOUBLE","dimension":"1"},{"index":11,"name":"AQUOPT","description":"AQUOPT is a character string that sets the cell face connection and should be set to one of the following: YES: Aquifer connections can adjoin to active cells allowing for connections inside the reservoir grid. It is not recommended to use this option without thoroughly checking the connections in the model. NO: Aquifer connections cannot adjoin to active cells preventing connections inside the reservoir grid. This is the recommended and the default value.","units":{},"default":"NO","value_type":"STRING"}],"example":"The following example defines aquifer number one connected to the I+ face of various cells in the model.\n--\n-- ANALYTIC AQUIFER CONNECTION\n--\n-- ID ---------- BOX --------- CONNECT AQF AQF ADJOIN\n-- NUMBER I1 I2 J1 J2 K1 K2 FACE INFLX MULTI CELLS\nAQUANCON\n1 57 57 28 36 46 58 'I+' 1* 1* 'NO' /\n1 111 111 38 41 22 31 'I+' 1* 1* 'NO' /\n1 96 96 44 49 22 31 'I+' 1* 1* 'NO' /\n1 43 43 28 35 54 58 'I+' 1* 1* 'NO' /\n1 98 98 38 42 32 40 'I+' 1* 1* 'NO' /\n1 79 79 41 67 5 11 'I+' 1* 1* 'NO' /\n1 61 61 48 72 12 17 'I+' 1* 1* 'NO' /\n/\nSee the AQUCT keyword in the GRID section for a complete example on defining and connecting a Carter-Tracy aquifer to a simulation grid.\n| Note If the AQUANCON keyword has been utilized in the run deck then OPM Flow will write the AQUIFERA array to the *.INIT file in order to visualize the aquifer connections in OPM ResInsight. This is accomplished by setting the AQUIFERA value to 2^(AQUID-1) for cells connected to aquifer AQUID. If a cell is connected to multiple analytical aquifers then AQUIFERA is summed for all aquifers connected to a cell. Note that connecting cells to multiple aquifers is best avoided. |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":11,"size_kind":"list"},"AQUCON":{"name":"AQUCON","sections":["GRID"],"supported":null,"summary":"AQUCON keyword defines how numerical aquifers are connected to the simulation grid and these type of aquifers are characterized by the AQUNUM keyword in the GRID section. Analytical aquifers are connected to the simulation grid by the AQUANCON keyword in the GRID section, this includes the Carter-Tracy and Fetkovich analytical aquifers, both of which are implemented in OPM Flow. Both aquifer types dimensions are declared by the AQUDIMS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"AQUID","description":"AQUID is a positive integer greater than or equal to one and less than or equal to the maximum number of numerical aquifers as defined by the MXNAQN variable on the AQUDIMS keyword in the RUNSPEC section, that defines the aquifer to be connected to the grid.","units":{},"default":"None","value_type":"INT"},{"index":2,"name":"I1","description":"A positive integer that defines the lower bound of the cells in the I-direction to be connected to the aquifer and must be greater than or equal to one and less than or equal to I2 and NX.","units":{},"default":"1","value_type":"INT"},{"index":3,"name":"I2","description":"A positive integer that defines the upper bound of the cells in the I-direction to be connected to the aquifer and must be greater than or equal to I1 and less than or equal to NX","units":{},"default":"NX","value_type":"INT"},{"index":4,"name":"J1","description":"A positive integer that defines the lower bound of the cells in the J-direction to be connected to the aquifer and must be greater than or equal to one and less than or equal to J2 and NY.","units":{},"default":"1","value_type":"INT"},{"index":5,"name":"J2","description":"A positive integer that defines the upper bound of the cells in the J-direction to be connected to the aquifer and must be greater than or equal to JI and less than or equal to NY.","units":{},"default":"NY","value_type":"INT"},{"index":6,"name":"K1","description":"A positive integer that defines the lower bound of the cells in the K-direction to be to be connected to the aquifer and must be greater than or equal to one and less than or equal to K2 and NZ.","units":{},"default":"1","value_type":"INT"},{"index":7,"name":"K2","description":"A positive integer that defines the upper bound of the cells in the K-direction to be connected to the aquifer and must be greater than or equal to KI and less than or equal to NZ.","units":{},"default":"NZ","value_type":"INT"},{"index":8,"name":"AQUFACE","description":"AQUFACE is a character string that sets the connection “face” of the cells declared by this record and should be set to one of the following: X+, Y+, or Z+ for the positive direction, or X-, Y- or Z- for the negative direction transmissibilities. I+, J+, or K+ for the positive direction, or I-, J- or K- for the negative direction transmissibilities.","units":{},"default":"None","value_type":"STRING"},{"index":9,"name":"AQUMULT","description":"AQUMULT is a positive real number greater than or equal to zero that scales the OPM Flow calculated transmissibility between the AQUID aquifer and the grid cell connections defined by this record. The default value of one sets the transmissibility between the aquifer and grid cells to the OPM Flow calculated value.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0","value_type":"DOUBLE"},{"index":10,"name":"AQUOPT1","description":"AQUOPT1 is a defined integer value set to either zero or one, that defines the area to be used in calculating the connection transmissibility between the aquifer and the grid cells: A value of zero means the cross-sectional defined on the AQUNUM keyword will be used, whereas, A value of one means the cross-sectional defined by the grid cell connections defined by this record will be used.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0","value_type":"INT"},{"index":11,"name":"AQUOPT2","description":"AQUOPT2 is a character string that sets the cell face connection and should be set to one of the following: YES: Aquifer connections can adjoin to active cells allowing for connections inside the reservoir grid. It is not recommended to use this option without thoroughly checking the connections in the model. NO: Aquifer connections cannot adjoin to active cells preventing connections inside the reservoir grid. This is the recommended and the default value.","units":{},"default":"NO","value_type":"STRING"},{"index":12,"name":"VEOPT1","description":"Vertical Equilibrium Option Number 1– Not Used","units":{},"default":"1","value_type":"DOUBLE"},{"index":13,"name":"VEOPT2","description":"Vertical Equilibrium Option Number 2– Not Used","units":{},"default":"1","value_type":"DOUBLE"}],"example":"The following example defines numerical aquifer number one connected to the I+ face of various cells in the model.\n--\n-- NUMERICAL AQUIFER CONNECTIONS\n--\n-- ID ---------- BOX --------- CONNECT TRANS TRANS ADJOIN\n-- NUMBER I1 I2 J1 J2 K1 K2 FACE MULT OPTN CELLS\nAQUCON\n1 57 57 28 36 46 58 'I+' 1* 1* 'NO' /\n1 111 111 38 41 22 31 'I+' 1* 1* 'NO' /\n1 96 96 44 49 22 31 'I+' 1* 1* 'NO' /\n1 43 43 28 35 54 58 'I+' 1* 1* 'NO' /\n1 98 98 38 42 32 40 'I+' 1* 1* 'NO' /\n1 79 79 41 67 5 11 'I+' 1* 1* 'NO' /\n1 61 61 48 72 12 17 'I+' 1* 1* 'NO' /\n/\nSee the AQUNUM keyword in the GRID section for a complete example on defining and connecting a numerical aquifer to a simulation grid.\n| Note If the AQUCON keyword has been utilized in the run deck then OPM Flow will write the AQUIFERN array to the *.INIT file in order to visualize the aquifer connections in OPM ResInsight. This is accomplished by setting the AQUIFERN value to 2^(AQUID-1) for cells connected to aquifer AQUID. If a cell is connected to multiple numerical aquifers then AQUIFERN is summed for all aquifers connected to a cell. Note that connecting cells to multiple aquifers is best avoided. Finally, for cells representing the numerical aquifers themselves, AQUIFERN is set to minus AQUID. |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":13,"size_kind":"list"},"AQUCT":{"name":"AQUCT","sections":["GRID","PROPS","SOLUTION","SCHEDULE"],"supported":null,"summary":"The AQUCT keyword defines Carter-Tracy112\n Carter, R. D. and Tracy, G. W. “An Improved Method for Calculating Water Influx,” Transactions of AIME (1960) 219, 215-417. 113\n Van Everdingen, A. & Hurst, W.,.The Application of the Laplace Transformation to Flow Problems in Reservoirs. Petroleum Transactions, AIME (December, 1949).analytical aquifers, the properties of the aquifer, including the Carter-Tracy aquifer influence function associated with the aquifer, defined by the AQUTAB keyword in the PROPS section.","parameters":[{"index":1,"name":"AQUID","description":"A positive integer greater than or equal to one and less than or equal to NANAQU on the AQUDIMS keyword in the RUNSPEC section, that defines the Carter-Tracy aquifer number.","units":{},"default":"1","value_type":"INT"},{"index":2,"name":"DATUM","description":"DATUM is a single positive value that defines the Carter-Tracy reference datum depth for PRESS.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":"Length"},{"index":3,"name":"PRESS","description":"PRESS is a single positive value that defines the aquifer pressure at DATUM. If PRESS is defaulted then the simulator will set the aquifer’s initial reservoir pressure to be in equilibrium with the cells the aquifer is contacted to.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1*","value_type":"DOUBLE","dimension":"Pressure"},{"index":4,"name":"PERM","description":"PERM is a real positive number that assigns the permeability to the aquifer.","units":{"field":"mD","metric":"mD","laboratory":"mD"},"default":"None","value_type":"DOUBLE","dimension":"Permeability"},{"index":5,"name":"PORO","description":"PORO is a real positive number greater than zero and less than or equal to one that assigns the porosity to the aquifer.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":"1"},{"index":6,"name":"RCOMP","description":"RCOMP is a real number defining the total (rock and water) compressibility (Ct) at the DATUM pressure.","units":{"field":"1/psia","metric":"1/barsa","laboratory":"1/atma"},"default":"None","value_type":"DOUBLE","dimension":"1/Pressure"},{"index":7,"name":"RE","description":"RE is a real positive number that defines the Carter-Tracy aquifer external radius.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":"Length"},{"index":8,"name":"DZ","description":"DZ is a real positive number that defines the Carter-Tracy aquifer average net thickness.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":"Length"},{"index":9,"name":"ANGLE","description":"ANGLE is a real positive number that defines the angle of influence, that is the angular connection between the aquifer and the hydrocarbon reservoir. A value of 360o degrees, the default value, indicates that the aquifer completely surrounds the hydrocarbon reservoir.","units":{"field":"degrees","metric":"degrees","laboratory":"degrees"},"default":"360.0","value_type":"DOUBLE","dimension":"1"},{"index":10,"name":"PVTNUM","description":"PVTNUM is positive integer greater than zero and less than the NTPVT variable on the TABDIMS keyword in the RUNSPEC section, that defines the PVTW table allocated to the Carter-Tracy aquifer.","units":{},"default":"1","value_type":"INT"},{"index":11,"name":"AQUTAB","description":"AQUTAB is positive integer greater than zero and less than the NIFTBL variable as declared on the AQUDIMS keyword in the RUNSPEC section, that defines the AQUTAB table allocated to this Carter-Tracy aquifer. The default value of one sets the internal infinite acting Carter-Tracy aquifer influence table not the first table in the AQUTAB keyword in the PROPS section The first table in the AQUTAB keyword is considered to be table number two. The internal table, AQUTAB equal to one, is based on the Radial Flow, Constant Pressure and Constant Terminal Rate Cases for Infinite Reservoirs (Table I) in Van Everdingen and Hurst's 114\n Van Everdingen, A. & Hurst, W.,.The Application of the Laplace Transformation to Flow Problems in Reservoirs. Petroleum Transactions, AIME (December, 1949).paper. Van Everdingen, A. & Hurst, W.,.The Application of the Laplace Transformation to Flow Problems in Reservoirs. Petroleum Transactions, AIME (December, 1949).","units":{},"default":"1","value_type":"INT"},{"index":12,"name":"SALTCON","description":"SALTCON is a real positive number that defines the initial salt concentration in the aquifer, for when with simulator's Brine Model has been activated via the BRINE keyword in the RUNSPEC section. This variable is ignored by OPM Flow.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"0.0","value_type":"DOUBLE","dimension":"Concentration"},{"index":13,"name":"TEMP","description":"TEMP is a real positive number that defines the initial temperature of the aquifer at DATUM for use with OPM Flow's thermal option. The THERMAL keyword in the RUNSPEC section must be activated to use this option.","units":{"field":"oF","metric":"oC","laboratory":"oC"},"default":"1*","value_type":"DOUBLE","dimension":"Temperature"}],"example":"Given the following grid and aquifer dimensions in the RUNSPEC section:\n--\n-- MAX MAX MAX\n-- NDIVIX NDIVIY NDIVIZ\nDIMENS\n20 1 5 /\n-- AQF AQF AQF AQF AQF AQF AQF AQF\n-- MXAQN MXNAQC NIFTBL NRIFTB NANAQU NCAMAX MXNALI MXAAQL\nAQUDIMS\n1* 1* 5 100 1 1* 1* 1* /\nAnd the AQUTAB keyword in the PROPS section\n--\n-- CARTER-TRACY AQUIFER INFLUENCE TABLES\n-- (STARTS FROM TABLE NO. 2, AS DEFAULT IS TABLE NO. 1)\n--\nAQUTAB\n-- DIMLESS DIMLESS\n-- TIME PRESSURE\n-- ------- ---------\n0.01 0.112\n0.05 0.229\n0.10 0.315\n0.15 0.376\n0.20 0.424\n0.22 0.443\n0.24 0.459\n0.26 0.476\n0.28 0.492\n0.30 0.507\n0.32 0.522\n0.34 0.536\n0.36 0.551\n0.38 0.565\n0.40 0.579\n0.42 0.593\n0.44 0.607\n0.46 0.621\n0.48 0.634\n0.50 0.648\n0.60 0.715\n0.70 0.782\n0.80 0.849\n0.90 0.915\n1.00 0.982\n2.00 1.649\n3.00 2.316\n5.00 3.649\n10.00 6.982\n20.00 13.649\n30.00 20.316\n50.00 33.649\n100.00 66.982\n200.00 133.649\n300.00 200.316\n500.00 333.649\n1000.00 666.982 /\nThe Carter-Tracy aquifer is defined in the GRID or SOLUTION sections as:\n-- ==============================================================================\n--\n-- SOLUTION SECTION\n--\n-- ==============================================================================\nSOLUTION\n--\n-- CARTER-TRACY AQUIFER DESCRIPTION\n--\n-- ID DATUM AQF AQF AQF AQF AQF AQF INFL PVT AQU\n-- NUM DEPTH PRESS PERM PORO RCOMP RE DZ ANGLE NUM TAB\n--\nAQUCT\n1 2000.0 269 100.0 0.30 3.0e-5 330 10.0 360.0 1 2 /\n/\nAnd the connection of the aquifer is set in the GRID or SOLUTION sections as:\n--\n-- ANALYTIC AQUIFER CONNECTION\n--\n-- ID ---------- BOX --------- CONNECT AQF AQF ADJOIN\n-- NUMBER I1 I2 J1 J2 K1 K2 FACE INFLX MULTI CELLS\nAQUANCON\n1 1 1 1 1 1 1 J- 1.0 1.0 'NO' /\n/\nHere one Carter-Tracy aquifer is connected to a single cell (1, 1, 1) at the J- face (or X- face) of the cell.\n| Note OPM Flow includes the infinite acting Carter-Tracy aquifer influence table as a default for table number one; thus data entered on AQUTAB keyword starts from table number two. |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":13,"size_kind":"list"},"AQUNNC":{"name":"AQUNNC","sections":["GRID"],"supported":false,"summary":"The AQUNNC keyword defines Numerical Aquifer Non-Neighbor Connections.","parameters":[{"index":1,"name":"AQUIFER_ID","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"IX","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"IY","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"IZ","description":"","units":{},"default":"","value_type":"INT"},{"index":5,"name":"JX","description":"","units":{},"default":"","value_type":"INT"},{"index":6,"name":"JY","description":"","units":{},"default":"","value_type":"INT"},{"index":7,"name":"JZ","description":"","units":{},"default":"","value_type":"INT"},{"index":8,"name":"TRAN","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Transmissibility"},{"index":9,"name":"IST1","description":"","units":{},"default":"","value_type":"INT"},{"index":10,"name":"IST2","description":"","units":{},"default":"","value_type":"INT"},{"index":11,"name":"IPT1","description":"","units":{},"default":"","value_type":"INT"},{"index":12,"name":"IPT2","description":"","units":{},"default":"","value_type":"INT"},{"index":13,"name":"ZF1","description":"","units":{},"default":"","value_type":"STRING"},{"index":14,"name":"ZF2","description":"","units":{},"default":"","value_type":"STRING"},{"index":15,"name":"DIFF","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"}],"example":"","expected_columns":15,"size_kind":"list"},"AQUNUM":{"name":"AQUNUM","sections":["GRID"],"supported":null,"summary":"The AQUNUM keyword defines the properties of numerical aquifers, including which grid blocks in the model should be utilized as part of the numerical aquifer. Each row entry in the AQUNUM keyword defines one numerical aquifer. Note that a numerical aquifer may consists of more than one grid cell, in order to better describe the water influx from the aquifer to the grid.","parameters":[{"index":1,"name":"AQUID","description":"AQUID is a positive integer greater than or equal to one and less than or equal to the maximum number of numerical aquifers as defined by the MXNAQN variable on the AQUDIMS keyword in the RUNSPEC section, that defines the aquifer to be connected to the grid.","units":{},"default":"None","value_type":"INT"},{"index":2,"name":"I","description":"A positive integer that defines the cell in the I-direction that represents the AQUID aquifer, and which must be greater than or equal to one and less than or equal to NX.","units":{},"default":"None","value_type":"INT"},{"index":3,"name":"J","description":"A positive integer that defines the cell in the J-direction that represents the AQUID aquifer, and which must be greater than or equal to one and less than or equal to NY.","units":{},"default":"None","value_type":"INT"},{"index":4,"name":"K","description":"A positive integer that defines the cell in the K-direction that represents the AQUID aquifer, and which must be greater than or equal to one and less than or equal to NZ.","units":{},"default":"None","value_type":"INT"},{"index":5,"name":"AREA","description":"AREA is a real positive value that defines the cross-sectional area of the aquifer used in calculating the aquifer connection transmissibility. The actual transmissibility between the numerical aquifer and the connected grid cell is the harmonic average of the aquifer connection transmissibility and the calculated connected cell transmissibility. The value entered for AREA does not effect the visualization of the cell in OPM ResInsight, as it is only used in calculating the transmissibility. Note that the AQUOPT1 variable on the AQUCON keyword in the GRID section allows one to use the value entered for AREA or to use the grid cell cross-sectional area instead for the transmissibility calculation.","units":{"field":"ft2","metric":"m2","laboratory":"cm2"},"default":"None","value_type":"DOUBLE","dimension":"Length*Length"},{"index":6,"name":"LENGTH","description":"LENGTH is a real positive value that defines the length of the numerical aquifer. Similar to the AREA variable, LENGTH is not constrained by the original host cell size and the value entered does not effect the visualization of the cell in OPM ResInsight.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":"Length"},{"index":7,"name":"PORO","description":"PORO is a real positive number greater than zero and less than or equal to one that assigns the porosity to the numerical aquifer.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":"1"},{"index":8,"name":"PERM","description":"PERM is a real positive number that assigns the permeability to the numerical aquifer.","units":{"field":"mD","metric":"mD","laboratory":"mD"},"default":"None","value_type":"DOUBLE","dimension":"Permeability"},{"index":9,"name":"DATUM","description":"DATUM is a real positive number that sets the reference datum depth of the numerical aquifer. Similar to the AREA variable, DATUM is not constrained by the original host cell depth and the value entered does not effect the visualization of the cell in OPM ResInsight. If defaulted then the depth of cell (I, J, K) will be used","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"Cell Depth","value_type":"DOUBLE","dimension":"Length"},{"index":10,"name":"PRESS","description":"PRESS is a single positive value that defines the numerical aquifer pressure at DATUM. If PRESS is defaulted then the simulator will set the aquifer’s initial reservoir pressure to be in equilibrium with the cells the aquifer is contacted to. This is the preferred manner to initialize the numerical aquifer.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1*","value_type":"DOUBLE","dimension":"Pressure"},{"index":11,"name":"PVTNUM","description":"PVTNUM is positive integer greater than zero and less than the NTPVT variable on the TABDIMS keyword in the RUNSPEC section, that defines the PVTW table allocated to the numerical aquifer. If defaulted then the PVT tables allocated to cell (I, J, K) will be used.","units":{},"default":"Cell PVTNUM","value_type":"INT"},{"index":12,"name":"SATNUM","description":"SATNUM is positive integer greater than zero and less than the NTSFUN variable on the TABDIMS keyword in the RUNSPEC section, that defines the saturation tables allocated to the numerical aquifer. If defaulted then the saturation tables allocated to cell (I, J, K) will be used.","units":{},"default":"Cell SATNUM","value_type":"INT"}],"example":"Given the following grid and aquifer dimensions in the RUNSPEC section:\n--\n-- MAX MAX MAX\n-- NDIVIX NDIVIY NDIVIZ\nDIMENS\n96 58 28 /\n-- AQF AQF AQF AQF AQF AQF AQF AQF\n-- MXAQN MXNAQC NIFTBL NRIFTB NANAQU NCAMAX MXNALI MXAAQL\nAQUDIMS\n3 3 1* 1* 1* 1* 1* 1* /\nThe following numerical aquifer definition:\n--\n-- NUMERICAL AQUIFER DESCRIPTION\n--\n-- AQUID - LOCATION - AQF AQF AQF AQF AQF AQF PVT SATNUM\n-- NUMBER I J K AREA LENGTH PORO PERM DATUM PRES TAB TAB\n--\nAQUNUM\n1 1 3 28 5.20E03 2.0E3 0.05 0.3 1* 1* 1* 1* /\n1 1 2 28 5.20E06 2.0E6 0.05 0.3 1* 1* 1* 1* /\n1 1 1 28 5.20E09 2.0E9 0.05 0.3 1* 1* 1* 1* /\n/\ndefines one numerical aquifer consisting of three cells. The connection to the grid cells would take the form of:\n--\n-- NUMERICAL AQUIFER CONNECTIONS\n--\n-- ID ---------- BOX --------- CONNECT TRANS TRANS ADJOIN\n-- NUMBER I1 I2 J1 J2 K1 K2 FACE MULT OPTN CELLS\nAQUCON\n1 1 1 4 58 28 28 'K+' 1.3 1* 1* /\n1 2 96 1 58 28 28 'K+' 1.3 1* 1* /\n/\nthat creates a basal aquifer115\n Basal Aquifer: An aquifer located at the bottom of a geologic unit..\nBasal Aquifer: An aquifer located at the bottom of a geologic unit.\n| Note If the AQUCON keyword has been utilized in the run deck then OPM Flow will write the AQUIFERN array to the *.INIT file in order to visualize the aquifer connections in OPM ResInsight. This is accomplished by setting the AQUIFERN value to 2^(AQUID-1) for cells connected to aquifer AQUID. If a cell is connected to multiple numerical aquifers then AQUIFERN is summed for all aquifers connected to a cell. Note that connecting cells to multiple aquifers is best avoided. Finally for cells representing the numerical aquifers themselves, AQUIFERN is set to minus AQUID. |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":12,"size_kind":"list"},"AUTOCOAR":{"name":"AUTOCOAR","sections":["GRID"],"supported":false,"summary":"The AUTOCOAR keyword defines an area in the global grid that should be coarsen for when the AUTOREF keyword has been declared in the RUNSPEC section.","parameters":[{"index":1,"name":"I1","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"I2","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"J1","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"J2","description":"","units":{},"default":"","value_type":"INT"},{"index":5,"name":"K1","description":"","units":{},"default":"","value_type":"INT"},{"index":6,"name":"K2","description":"","units":{},"default":"","value_type":"INT"},{"index":7,"name":"NX","description":"","units":{},"default":"","value_type":"INT"},{"index":8,"name":"NY","description":"","units":{},"default":"","value_type":"INT"},{"index":9,"name":"NZ","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":9,"size_kind":"list"},"BCCON":{"name":"BCCON","sections":["GRID"],"supported":true,"summary":"The BCCON keyword defines the grid connections for the boundary conditions.","parameters":[{"index":1,"name":"INDEX","description":"A positive integer that identifies the boundary condition.","units":{},"default":"None","value_type":"INT"},{"index":2,"name":"I1","description":"A positive integer that defines the lower bound of the grid in the I-direction for which the boundary conditions are to be applied, must be greater than or equal 1 and less than or equal to I2 and NX.","units":{},"default":"1","value_type":"INT"},{"index":2,"name":"I2","description":"A positive integer that defines the upper bound of the grid in the I-direction for which the boundary conditions are to be applied, must be greater than or equal to II and less than or equal to NX","units":{},"default":"NX","value_type":"INT"},{"index":3,"name":"J1","description":"A positive integer that defines the lower bound of the grid in the J-direction for which the boundary conditions are to be applied, must be greater than or equal 1 and less than or equal to J2 and NY.","units":{},"default":"1","value_type":"INT"},{"index":4,"name":"J2","description":"A positive integer that defines the upper bound of the grid in the J-direction for which the boundary conditions are to be applied, must be greater than or equal to JI and less than or equal to NY.","units":{},"default":"NY","value_type":"INT"},{"index":5,"name":"K1","description":"A positive integer that defines the lower bound of the grid in the K-direction for which the boundary conditions are to be applied, must be greater than or equal to one and less than or equal to K2 and NZ.","units":{},"default":"1","value_type":"INT"},{"index":6,"name":"K2","description":"A positive integer that defines the upper bound of the grid in the K-direction for which the boundary conditions are to be applied, must be greater than or equal to KI and less than or equal to NZ.","units":{},"default":"NZ","value_type":"INT"},{"index":7,"name":"DIRECT","description":"A character string that defines the direction to apply the boundary conditions, and should be set to one of the following X, Y, or Z for the positive direction, or X-, Y- or Z- for the negative direction.","units":{},"default":"None","value_type":"INT"},{"index":8,"name":"DIRECTION","description":"","units":{},"default":"","value_type":"STRING"}],"example":"The first example shows how to set a constant pressure boundary using TYPE equal to FREE:\n--\n-- DEFINE BOUNDARY CONDITIONS CONNECTION (OPM FLOW GRID KEYWORD)\n--\n--INDEX ---------- BOX --------- BC\n-- I1 I2 J1 J2 K1 K2 DIRC\nBCCON\n1 1 1 1 1* 1 1* X- /\n2 1 1* 1 1 1 1* Y /\n/\n--\n-- DEFINE BOUNDARY CONDITIONS PROPERTIES (OPM FLOW SCHEDULE KEYWORD)\n--\n--INDEX BC BC BC BC BC\n-- TYPE PHASE RATE PRESS TEMP\nBCPROP\n1 FREE 1* 1* 1* 1* /\n2 FREE /\n/\nWith this option it is only necessary to define the boundary cells and all the other parameters (COMPONENT, RATE, PRESS, and TEMP) can be defaulted, as they are ignored when TYPE equals FREE.\nThe next example is based on NX, NY and NZ equal to 20, 1, 10 respectively, on the DIMENS keyword in the RUNSPEC section, and shows how different boundary types can be assigned to different parts of the model.\n--\n-- DEFINE BOUNDARY CONDITIONS CONNECTION (OPM FLOW GRID KEYWORD)\n--\n--INDEX ---------- BOX --------- BC\n-- I1 I2 J1 J2 K1 K2 DIRC\nBCCON\n1 1 1 1 1 1 10 X- /\n2 20 20 1 1 1 10 X /\n/\n--\n-- DEFINE BOUNDARY CONDITIONS PROPERTIES (OPM FLOW SCHEDULE KEYWORD)\n--\n--INDEX BC BC BC BC BC\n-- TYPE PHASE RATE PRESS TEMP\nBCPROP\n1 DIRICHLET GAS 1* 256.0 100.0 /\n2 FREE 4* /\n/\nThe last example shows how the DIRICHLET boundary condition option may be used:\n--\n-- DEFINE BOUNDARY CONDITIONS CONNECTION (OPM FLOW GRID KEYWORD)\n--\n--INDEX ---------- BOX --------- BC\n-- I1 I2 J1 J2 K1 K2 DIRC\nBCCON\n1 1 1 1 1* 1 1* X- /\n2 1 1* 1 1 1 1* Y /\n/\n--\n-- DEFINE BOUNDARY CONDITIONS PROPERTIES (OPM FLOW SCHEDULE KEYWORD)\n--\n--INDEX BC BC BC BC BC\n-- TYPE PHASE RATE PRESS TEMP\nBCPROP\n1 DIRICHLET WAT 1* 256.0 100.0 /\n2 DIRICHLET WAT 1* 1* 100.0 /\n/\nHere, the first line sets both the pressure and temperature at the boundary, and the second line defaults the pressure entry, so that the simulator calculated initial boundary pressure will be used.\n| Note This is an OPM Flow specific keyword and will therefore cause an error in the commercial simulator. |\n|----------------------------------------------------------------------------------------------------------|","expected_columns":8,"size_kind":"list"},"BOUNDARY":{"name":"BOUNDARY","sections":["GRID","EDIT","REGIONS","SOLUTION","SCHEDULE"],"supported":false,"summary":"The BOUNDARY keyword defines a rectangular grid for printing various arrays to the output print file (*.PRT); thus, avoiding printing all the elements in the selected array.","parameters":[{"index":1,"name":"IX1","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"IX2","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"JY1","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"JY2","description":"","units":{},"default":"","value_type":"INT"},{"index":5,"name":"KZ1","description":"","units":{},"default":"","value_type":"INT"},{"index":6,"name":"KZ2","description":"","units":{},"default":"","value_type":"INT"},{"index":7,"name":"ORIENTATION_INDEX","description":"","units":{},"default":"1","value_type":"INT"},{"index":8,"name":"DUAL_PORO_FLAG","description":"","units":{},"default":"BOTH","value_type":"STRING"}],"example":"","expected_columns":8,"size_kind":"fixed","size_count":1},"BOX":{"name":"BOX","sections":["GRID","EDIT","PROPS","REGIONS","SOLUTION","SCHEDULE"],"supported":null,"summary":"BOX defines a range of grid blocks for which subsequent data is assigned for all the cells in the defined BOX. Values are set for cells within the defined box grid using natural reading order, initially along the I-direction then J-direction and finally the K-direction. If fewer values are assigned than exist within the defined block space, then subsequent values are set starting from the next block that was not previously assigned for that property. This is the same behavior as applies to setting grid properties for an unboxed grid.","parameters":[{"index":1,"name":"I1","description":"A positive integer that defines the lower bound of the array in the I-direction to be modified must be greater than or equal 1 and less than or equal to I2 and NX.","units":{},"default":"1","value_type":"INT"},{"index":2,"name":"I2","description":"A positive integer that defines the upper bound of the array in the I-direction to be modified must be greater than or equal to II and less than or equal to NX","units":{},"default":"NX","value_type":"INT"},{"index":3,"name":"J1","description":"A positive integer that defines the lower bound of the array in the J-direction to be modified must be greater than or equal 1 and less than or equal to J2 and NY.","units":{},"default":"1","value_type":"INT"},{"index":4,"name":"J2","description":"A positive integer that defines the upper bound of the array in the J-direction to be modified must be greater than or equal to JI and less than or equal to NY.","units":{},"default":"NY","value_type":"INT"},{"index":5,"name":"K1","description":"A positive integer that defines the lower bound of the array in the K-direction to be modified must be greater than or equal to one and less than or equal to K2 and NZ.","units":{},"default":"1","value_type":"INT"},{"index":6,"name":"K2","description":"A positive integer that defines the upper bound of the array in the K-direction to be modified must be greater than or equal to KI and less than or equal to NZ.","units":{},"default":"NZ","value_type":"INT"}],"example":"--\n-- DEFINE A BOX GRID FOR THE BOTTOM LAYER OF A 100 X 100 X 20 MODEL\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1* 1* 1* 1* 20 20 / SELECT THE BOTTOM LAYER\n--\n-- DEFINE THE POROSITY AND OTHER PROPERTIES ON THE BOX GRID\n--\nPORO\n10000*0.300 /\nPERMX\n5000*100.0 5000*75.0 /\nNTG\n10000*0.500 /\n--\n-- RESET THE INPUT BOX TO BE THE FULL MODEL\n--\nENDBOX\nThe above example set the BOX grid to be the last layer in the model which means that 100 x 100, that is 10,000 values need to entered for each property.\nAlternatively, one could use the EQUALS keyword to accomplish the same thing.\n-- -- ARRAY CONSTANT -- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\n'PORO’ 0.3000 1* 1* 1* 1* 20 20 / PORO TO 0.30 IN LAYER 20\n'PERMX' 100.00 1* 1* 1 50 20 20 / PERMX TO 100. IN LAYER 20\n'PERMX' 75.00 1* 1* 51 100 20 20 / PERMX TO 75.0 IN LAYER 20\n'NTG’ 0.5000 1* 1* 1* 1* 20 20 / NTG TO 0.50 IN LAYER 20\n/\nNote\nIt is good practice to always use the ENDBOX keyword to reset the input back to the full grid when all the modifications for a sub-grid have been completed.\n| Note It is good practice to always use the ENDBOX keyword to reset the input back to the full grid when all the modifications for a sub-grid have been completed. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":6,"size_kind":"fixed","size_count":1},"BTOBALFA":{"name":"BTOBALFA","sections":["GRID"],"supported":false,"summary":"The BTOBALFA keyword defines a dual porosity matrix to fracture multiplier that is applied to all cells, for when the Dual Porosity model has been activated by either the DUALPORO or the DUALPERM keywords in the RUNSPEC section.","parameters":[{"index":1,"name":"VALUE","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"BTOBALFV":{"name":"BTOBALFV","sections":["GRID"],"supported":false,"summary":"The BTOBALFV keyword defines a dual porosity matrix to fracture multiplier that is applied to individual cells, for when the Dual Porosity model has been invoked by either the DUALPORO or the DUALPERM keywords in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"CARFIN":{"name":"CARFIN","sections":["GRID"],"supported":false,"summary":"CARFIN defines a Cartesian Local Grid Refinement (“LGR”) in a cell or a group of cells in the host grid, for when LGRs have been activated for the input deck using the LGR keyword in the RUNSPEC section. The keyword marks the start of an LGR description section and all subsequent keywords between the CARFIN and ENDFIN keywords are deemed to be associated with the current LGR and not the host grid.","parameters":[{"index":1,"name":"LGRNAME","description":"A character string of up to eight characters in length that defines the LGR name for which the LGR is being being defined.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"I1","description":"A positive integer that defines the lower index of the global or host grid in the I-direction to be refined; must be greater than or equal 1 and less than or equal to I2 and NX on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":3,"name":"I2","description":"A positive integer that defines the upper index of the global or host grid in the I-direction to be refined; must be greater than or equal 1 and II, and less than or equal to NX on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":4,"name":"J1","description":"A positive integer that defines the lower index of the global or host grid in the J-direction to be refined; must be greater than or equal 1 and less than or equal to J2 and NY on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":5,"name":"J2","description":"A positive integer that defines the upper index of the global or host grid in the J-direction to be refined; must be greater than or equal 1 and JI, and less than or equal to NY on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":6,"name":"K1","description":"A positive integer that defines the lower index of the global or host grid in the K-direction to be refined; must be greater than or equal 1 and less than or equal to K2 and NZ on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":7,"name":"K2","description":"A positive integer that defines the upper index of the global or host grid in the K-direction to be refined; must be greater than or equal 1 and KI, and less than or equal to NZ on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":8,"name":"NX","description":"A positive integer value that defines the number of LGR grid blocks in the x direction for Cartesian grids or the number of grid blocks in the r direction for radial grids","units":{},"default":"None","value_type":"INT"},{"index":9,"name":"NY","description":"A positive integer value that defines the number of LGR grid blocks in the y direction for Cartesian grids or the number of grid blocks in the theta direction for radial grids.","units":{},"default":"None","value_type":"INT"},{"index":10,"name":"NZ","description":"A positive integer value that defines the number of LGR grid blocks in the z direction for both Cartesian and radial grids.","units":{},"default":"None","value_type":"INT"},{"index":11,"name":"MXWELS","description":"A positive integer defining the maximum number of wells contained in this LGR.","units":{},"default":"None","value_type":"INT"},{"index":12,"name":"HOSTNAME","description":"A character string of up to eight characters in length that defines the host grid name for nested refinements. The default value of “GLOBAL” sets the host name to the global grid, that is for a conventional LGR. A nested refinement is when the HOSTNAME is a previously declared LGR for which the current LGR is specifying a further LGR refinement.","units":{},"default":"GLOBAL","value_type":"STRING"}],"example":"The example below defines an LGR in the global grid, named LGR-OP01 with a maximum of one well allowed in the LGR.\n--\n-- CARFIN LGR GRID COMMANDS\n--\n-- LGR ----- HOST GRID ------ -- CARFIN GRID -- MAX HOST\n-- NAME I1 I2 J1 J2 K1 K2 NX NY NZ WELLS NAME\nCARFIN\nLGR-OP01 24 24 87 87 1 50 3 3 50 1 GLOBAL /\nENDFIN\nHere the one global cell in the areal plane (24, 87) is divided into three LGR cells in the x-direction and three cells in the y-direction. Since no other property data is given, then the LGR cells take their properties from the host grid, that is the global grid.","expected_columns":12,"size_kind":"fixed","size_count":1},"COALNUM":{"name":"COALNUM","sections":["GRID"],"supported":false,"summary":"The COALNUM keyword defines the coal region numbers for each grid block used with the Coal Bed Methane option (“CBM”). OPM Flow does not have a CBM option; however, the keyword is documented here for completeness.","parameters":[{"index":1,"name":"COALNUM","description":"COALNUM defines an array of positive integers assigning a grid cell to a particular coal region. The maximum number of COALNUM regions is set by the NTCREG variable on REGDIMS keywords in the RUNSPEC section.","units":{},"default":"1"}],"example":"The example below sets three COALNUM regions for a 4 x 5 x 2 model.\n--\n-- DEFINE COALNUM REGIONS FOR ALL CELLS\n--\nCOALNUM\n2 2 1 1 2 2 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n3 3 1 1 3 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n/\nThe above will no effect in an OPM Flow input deck.","size_kind":"array"},"COARSEN":{"name":"COARSEN","sections":["GRID"],"supported":false,"summary":"The COARSEN keyword defines how a set of cells should be coarsened for when the Local Grid Refinement (“LGR”) option has been activated by LGR keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"I1","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"I2","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"J1","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"J2","description":"","units":{},"default":"","value_type":"INT"},{"index":5,"name":"K1","description":"","units":{},"default":"","value_type":"INT"},{"index":6,"name":"K2","description":"","units":{},"default":"","value_type":"INT"},{"index":7,"name":"NX","description":"","units":{},"default":"","value_type":"INT"},{"index":8,"name":"NY","description":"","units":{},"default":"","value_type":"INT"},{"index":9,"name":"NZ","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":9,"size_kind":"fixed","size_count":1},"COLLAPSE":{"name":"COLLAPSE","sections":["GRID"],"supported":false,"summary":"The COLLAPSE keyword defines the which cells can be collapsed in a collapsed Vertical Equilibrium (“VE”) run when the VE option has been invoked via the VE keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"VALUE","description":"","units":{},"default":"1","value_type":"INT"}],"example":"","expected_columns":1,"size_kind":"list"},"COORD":{"name":"COORD","sections":["GRID"],"supported":null,"summary":"COORD defines a set of coordinate lines or pillars for a reservoir grid via an array. A total of 6 x (NX+1) x (NY+1) values must be specified for each coordinate data set (or reservoir). For multiple reservoirs, where NUMRES is greater than one, there must be 6 x (NX+1) x (NY+1) x NUMRES values. In OPM Flow NUMRES can only be set to one.","parameters":[{"index":1,"name":"X1-Column","description":"Top X coordinate","units":{},"default":"None"},{"index":2,"name":"Y1-Column","description":"Top Y coordinate","units":{},"default":""},{"index":3,"name":"Z1-Column","description":"Top Z coordinate","units":{},"default":""},{"index":4,"name":"X2-Column","description":"Base X coordinate","units":{},"default":""},{"index":5,"name":"Y2-Column","description":"Base Y coordinate","units":{},"default":""},{"index":6,"name":"Z2-Column","description":"Base Z coordinate","units":{},"default":""}],"example":"--\n-- SPECIFY VERTICAL COORDINATE LINES FOR A REGULAR 3 x 2 GRID\n-- (DX = 100 and DY = 200)\n--\n-- X1 Y1 Z1 X2 Y2 Z2\n-- --- --- ---- --- --- ----\nCOORD\n0 0 1000 0 0 5000\n100 0 1000 100 0 5000\n200 0 1000 200 0 5000\n300 0 1000 300 0 5000\n0 200 1000 0 200 5000\n100 200 1000 100 200 5000\n200 200 1000 200 200 5000\n300 200 1000 300 200 5000\n0 400 1000 0 400 5000\n100 400 1000 100 400 5000\n200 400 1000 200 400 5000\n300 400 1000 300 400 5000\n/\nThe above example defines vertical coordinate lines for a regular 3 by 2 grid with DX equal to 100 and DY equal to 200.","size_kind":"array"},"COORDSYS":{"name":"COORDSYS","sections":["GRID"],"supported":false,"summary":"This keyword sets various options for when multiple grid systems are being used, as declared by the NUMRES keyword in the RUNSPEC section. OPM Flow does not support multiple grid systems. The keyword is also used to stipulate for radial grids if the completion of the circle in the THETA direction should be implemented using non-neighbor connections.","parameters":[{"index":1,"name":"K1","description":"A positive integer that defines the lower bound of the array in the K-direction for the given grid system.","units":{},"default":"None","value_type":"INT"},{"index":2,"name":"K2","description":"A positive integer that defines the upper bound of the array in the K-direction for the given grid system.","units":{},"default":"None","value_type":"INT"},{"index":3,"name":"COMPLETE","description":"COMPLETE is a defined character string that determines for radial grids if the circle should be completed in THETA direction, and should be set to COMP to complete the circle, or INCOMP for not completing the circle.","units":{},"default":"INCOMP","value_type":"STRING"},{"index":4,"name":"CONNECT","description":"A defined character string that declares how the reservoir below should be connected to the given reservoir, and should be set to JOIN to connect the two reservoirs by calculating the inter-reservoir transmissibilities, or SEPARATE to isolate the reservoirs.","units":{},"default":"SEPARATE","value_type":"STRING"},{"index":5,"name":"R1","description":"R1 is a positive integer defining the lower reservoir unit that is is connected to the given reservoir unit.","units":{},"default":"Current Reservoir Record","value_type":"INT"},{"index":6,"name":"R2","description":"R2 is a positive integer defining the upper reservoir unit that is is connected to the given reservoir unit.","units":{},"default":"","value_type":"INT"}],"example":"--\n-- DEFINE COORDINATE GRID OPTIONS\n--\n-- K1 K2 COMP CONNECT LOWER UPPER\n-- Layer Layer CIRCLE RES RES RES\nCOORDSYS\n1 1 COMP /\n/\nThe above example connects the circle in the THETA direction for the RADIAL model, for when the number of grids have been set to one via the NUMRES keyword in the SCHEDULE section.","expected_columns":6,"size_kind":"fixed"},"COPY":{"name":"COPY","sections":["GRID","EDIT","PROPS","REGIONS","SOLUTION"],"supported":false,"summary":"The COPY keyword copies an array (or part of an array) to another array or part of an array. The arrays can be integer or real valued; however, the arrays that can be operated on are dependent on which section the COPY keyword is being applied in.","parameters":[{"index":1,"name":"ARRAY-1","description":"A character string of up to eight characters in length that defines the keyword identifying the array to be copied from.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"ARRAY-2","description":"A character string of up to eight characters in length that defines the keyword identifying the array to be copied to.","units":{},"default":"None","value_type":"STRING"},{"index":3,"name":"I1","description":"A positive integer that defines the lower bound of the array in the I-direction to be modified must be greater than or equal 1 and less than or equal to I2 and NX.","units":{},"default":"1","value_type":"INT"},{"index":4,"name":"I2","description":"A positive integer that defines the upper bound of the array in the I-direction to be modified must be greater than or equal to II and less than or equal to NX","units":{},"default":"NX","value_type":"INT"},{"index":5,"name":"J1","description":"A positive integer that defines the lower bound of the array in the J-direction to be modified must be greater than or equal 1 and less than or equal to J2 and NY.","units":{},"default":"1","value_type":"INT"},{"index":6,"name":"J2","description":"A positive integer that defines the upper bound of the array in the J-direction to be modified must be greater than or equal to JI and less than or equal to NY.","units":{},"default":"NY","value_type":"INT"},{"index":7,"name":"K1","description":"A positive integer that defines the lower bound of the array in the K-direction to be modified must be greater than or equal to one and less than or equal to K2 and NZ.","units":{},"default":"1","value_type":"INT"},{"index":8,"name":"K2","description":"A positive integer that defines the upper bound of the array in the K-direction to be modified must be greater than or equal to KI and less than or equal to NZ.","units":{},"default":"NZ","value_type":"INT"}],"example":"--\n-- SOURCE DESTIN. ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nCOPY\nPERMX PERMY 1* 1* 1* 1* 1* 1* / CREATE PERMY\nPERMX PERMZ 1* 1* 1* 1* 1* 1* / CREATE PERMZ\n/\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nMULTIPLY\nPERMZ 0.50000 1* 1* 1* 1* 1* 1* / PERMZ * 0.5\n/\nThe above example copies PERMX array to the PERMY and PERMZ arrays in the GRID section for all grid blocks in the model. The PERMZ array is then multiplied by 0.5 for all grid blocks in the model.\n| COPY Keyword and Variable Options by Section | | | | | | |\n|----------------------------------------------|---------|-------|---------|----------|---------|----------|\n| GRID | EDIT | PROPS | REGIONS | SOLUTION | SUMMARY | SCHEDULE |\n| DX | DEPTH | SWL | ENDNUM | PRESSURE | | |\n| DY | PORV | SWCR | EQLNUM | SWAT | | |\n| DZ | TRANX | SWU | FIPNUM | SGAS | | |\n| PERMX | TRANY | SGL | IMBNUM | RV | | |\n| PERMY | TRANZ | SGCR | MISCNUM | RS | | |\n| PERMZ | DIFFX | SGU | PVTNUM | TBLK | | |\n| MULTX | DIFFY | KRW | ROCKNUM | GI | | |\n| MULTY | DIFFZ | KRO | SATNUM | OILAPI | | |\n| MULTZ | TRANR | KRG | WH2NUM | SALT | | |\n| DR | TRANTHT | PCG | | GASCONC | | |\n| DTHETA | DIFFR | PCW | | SOLVCONC | | |\n| PERMR | DIFFTHT | | | SOLVFRAC | | |\n| PERMTHT | | | | SFOAM | | |\n| DZNET | | | | SPOLY | | |\n| PORO | | | | | | |\n| NTG | | | | | | |\n| FLUXNUM | | | | | | |\n| MULTNUM | | | | | | |\n| MPFANUM | | | | | | |\n| DIFFX | | | | | | |\n| DIFFY | | | | | | |\n| DIFFZ | | | | | | |\n| DIFFR | | | | | | |\n| DIFFTHT | | | | | | |","expected_columns":8,"size_kind":"list"},"COPYBOX":{"name":"COPYBOX","sections":["GRID","PROPS","REGIONS"],"supported":false,"summary":"The COPYBOX keyword copies an array (or part of an array) to another part of the same array. The array can be real or integer depending on the array type; however, the array that can be operated on is dependent on which section the COPYBOX keyword is being used.","parameters":[{"index":1,"name":"ARRAY-1","description":"The name of the array to be copied This is the keyword name identifying the property and is up to eight characters in length and enclosed in quotes.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"I1","description":"A positive integer that defines the SOURCE lower bound of the array in the I-direction to be modified must be greater than or equal 1 and less than or equal to I2 and NX.","units":{},"default":"1","value_type":"INT"},{"index":3,"name":"I2","description":"A positive integer that defines the SOURCE upper bound of the array in the I-direction to be modified must be greater than or equal to II and less than or equal to NX","units":{},"default":"NX","value_type":"INT"},{"index":4,"name":"J1","description":"A positive integer that defines the SOURCE lower bound of the array in the J-direction to be modified must be greater than or equal 1 and less than or equal to J2 and NY.","units":{},"default":"1","value_type":"INT"},{"index":5,"name":"J2","description":"A positive integer that defines the SOURCE upper bound of the array in the J-direction to be modified must be greater than or equal to JI and less than or equal to NY.","units":{},"default":"NY","value_type":"INT"},{"index":6,"name":"K1","description":"A positive integer that defines the SOURCE lower bound of the array in the K-direction to be modified must be greater than or equal to one and less than or equal to K2 and NZ.","units":{},"default":"1","value_type":"INT"},{"index":7,"name":"K2","description":"A positive integer that defines the SOURCE upper bound of the array in the K-direction to be modified must be greater than or equal to KI and less than or equal to NZ.","units":{},"default":"NZ","value_type":"INT"},{"index":8,"name":"I3","description":"A positive integer that defines the DESTINATION lower bound of the array in the I-direction to be modified must be greater than or equal 1 and less than or equal to I2 and NX.","units":{},"default":"1","value_type":"INT"},{"index":9,"name":"I4","description":"A positive integer that defines the DESTINATION upper bound of the array in the I-direction to be modified must be greater than or equal to II and less than or equal to NX","units":{},"default":"NX","value_type":"INT"},{"index":10,"name":"J3","description":"A positive integer that defines the DESTINATION lower bound of the array in the J-direction to be modified must be greater than or equal 1 and less than or equal to J2 and NY.","units":{},"default":"1","value_type":"INT"},{"index":11,"name":"J4","description":"A positive integer that defines the DESTINATION upper bound of the array in the J-direction to be modified must be greater than or equal to JI and less than or equal to NY.","units":{},"default":"NY","value_type":"INT"},{"index":12,"name":"K3","description":"A positive integer that defines the DESTINATION lower bound of the array in the K-direction to be modified must be greater than or equal to one and less than or equal to K2 and NZ.","units":{},"default":"1","value_type":"INT"},{"index":13,"name":"K4","description":"A positive integer that defines the DESTINATION upper bound of the array in the K-direction to be modified must be greater than or equal to KI and less than or equal to NZ.","units":{},"default":"NZ","value_type":"INT"}],"example":"--\n-- SOURCE ------ SOURCE BOX ------ ---- DESTINATION BOX ----\n-- ARRAY I1 I2 J1 J2 K1 K2 I1 I2 J1 J2 K1 K2\nCOPYBOX\nPORO 1* 1* 1* 1* 12 14 1* 1* 1* 1* 15 17 / PORO\nPERMX 1* 1* 1* 1* 12 14 1* 1* 1* 1* 15 17 / PERMX\n/\nThe above example copies all the PORO and PERMX values in layers 12 to 14 to layers 15 and 17.\n| COPYBOX Keyword and Variable Options by Section | | | | | | |\n|-------------------------------------------------|------|-------|---------|----------|---------|----------|\n| GRID | EDIT | PROPS | REGIONS | SOLUTION | SUMMARY | SCHEDULE |\n| DX | | SWL | ENDNUM | | | |\n| DY | | SWCR | EQLNUM | | | |\n| DZ | | SWU | FIPNUM | | | |\n| PERMX | | SGL | IMBNUM | | | |\n| PERMY | | SGCR | MISCNUM | | | |\n| PERMZ | | SGU | PVTNUM | | | |\n| MULTX | | KRW | ROCKNUM | | | |\n| MULTY | | KRO | SATNUM | | | |\n| MULTZ | | KRG | WH2NUM | | | |\n| DR | | PCG | | | | |\n| DTHETA | | PCW | | | | |\n| PERMR | | | | | | |\n| PERMTHT | | | | | | |\n| DZNET | | | | | | |\n| PORO | | | | | | |\n| NTG | | | | | | |\n| FLUXNUM | | | | | | |\n| MULTNUM | | | | | | |\n| MPFANUM | | | | | | |\n| DIFFX | | | | | | |\n| DIFFY | | | | | | |\n| DIFFZ | | | | | | |\n| DIFFR | | | | | | |\n| DIFFTHT | | | | | | |","expected_columns":13,"size_kind":"list"},"COPYREG":{"name":"COPYREG","sections":["GRID","EDIT","PROPS","REGIONS","SOLUTION"],"supported":false,"summary":"The COPYREG keyword copies a specified array or part of an array based on cells with a specific region number to another array. The region number array can be FLUXNUM, MULTNUM or OPERNUM and these arrays must be defined and be available before the COPYREG keyword is read by the simulator. The property arrays can be real or integer valued depending on the property array type; however, the property arrays that can be operated on are dependent on which section the COPYREG keyword is being applied in.","parameters":[{"index":1,"name":"ARRAY-1","description":"A character string of up to eight characters in length that defines the keyword identifying the array to be copied from.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"ARRAY-2","description":"A character string of up to eight characters in length that defines the keyword identifying the array to be copied to.","units":{},"default":"None","value_type":"STRING"},{"index":3,"name":"REGION NUMBER","description":"Integer REGION NUMBER is the region for which the array data in (1) should be copied to array data in (2).","units":{},"default":"None","value_type":"INT"},{"index":4,"name":"REGION ARRAY","description":"The REGION ARRAY to use for selecting the REGION NUMBER in (3) for selecting the data to be copied. REGION ARRAY can have the following values: F for the FLUXNUM array M for the MULTNUM array O for the OPERNUM array","units":{},"default":"M","value_type":"STRING"}],"example":"--\n-- COPY AN ARRAY TO ANOTHER ARRAY BASED ON A REGION NUMBER\n--\n-- ARRAY ARRAY REGION REGION ARRAY\n-- FROM TO NUMBER M / F / O\nCOPYREG\nPERMX PERMY 1 M / COPY PERMX TO PERMY\nPERMX PERMZ 1 M / COPY PERMX TO PERMZ\n/\n--\n-- NOW RESET PERMZ BASED ON THE MULTNUM REGION NUMBER\n--\n--\n-- MULTIPLY AN ARRAY BY A CONSTANT BASED ON A REGION NUMBER\n--\n-- ARRAY CONSTANT REGION REGION ARRAY\n-- VALUE NUMBER M / F / O\nMULTIREG\nPERMX 0.95 1 M /\n/\nThe above example first copies the PERMX property array for region number one to the PERMY and PERMZ property arrays for region one using the MULTNUM array to define the region numbers. After which PERMZ property array for region one is multiplied by 0.5 using the MULTIREG keyword.\n| COPYREG Keyword and Variable Options by Section | | | | | | |\n|-------------------------------------------------|---------|-------|---------|----------|---------|----------|\n| GRID | EDIT | PROPS | REGIONS | SOLUTION | SUMMARY | SCHEDULE |\n| DX | DEPTH | SWL | ENDNUM | PRESSURE | | |\n| DY | PORV | SWCR | EQLNUM | SWAT | | |\n| DZ | TRANX | SWU | FIPNUM | SGAS | | |\n| PERMX | TRANY | SGL | IMBNUM | RV | | |\n| PERMY | TRANZ | SGCR | MISCNUM | RS | | |\n| PERMZ | DIFFX | SGU | PVTNUM | TBLK | | |\n| MULTX | DIFFY | KRW | ROCKNUM | GI | | |\n| MULTY | DIFFZ | KRO | SATNUM | OILAPI | | |\n| MULTZ | TRANR | KRG | WH2NUM | SALT | | |\n| DR | TRANTHT | PCG | | GASCONC | | |\n| DTHETA | DIFFR | PCW | | SOLVCONC | | |\n| PERMR | DIFFTHT | | | SOLVFRAC | | |\n| PERMTHT | | | | SFOAM | | |\n| DZNET | | | | SPOLY | | |\n| PORO | | | | | | |\n| NTG | | | | | | |\n| FLUXNUM | | | | | | |\n| MULTNUM | | | | | | |\n| MPFANUM | | | | | | |\n| DIFFX | | | | | | |\n| DIFFY | | | | | | |\n| DIFFZ | | | | | | |\n| DIFFR | | | | | | |\n| DIFFTHT | | | | | | |","expected_columns":4,"size_kind":"list"},"CRITPERM":{"name":"CRITPERM","sections":["GRID"],"supported":false,"summary":"The CRITPERM keyword is used to define the minimum permeability for Vertical Equilibrium(“VE”) grid cell compression, for when the Vertical Equilibrium formulation has been activated by the VE keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"VALUE","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Permeability"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"DIFFMR-":{"name":"DIFFMR-","sections":["GRID"],"supported":false,"summary":"The DIFFMR- keyword defines the negative radial direction diffusivity multipliers for cells in the current input box for when the Diffusivity option has been activated by the DIFFUSE keyword in the RUNSPEC section.","parameters":[],"example":""},"DIFFMR":{"name":"DIFFMR","sections":["GRID"],"supported":false,"summary":"The DIFFMR keyword defines the radial direction diffusivity multipliers for cells in the current input box for when the Diffusivity option has been activated by the DIFFUSE keyword in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"DIFFMTH-":{"name":"DIFFMTH-","sections":["GRID"],"supported":false,"summary":"The DIFFMR- keyword defines the negative theta direction diffusivity multipliers for cells in the current input box for when the Diffusivity option has been activated by the DIFFUSE keyword in the RUNSPEC section.","parameters":[],"example":""},"DIFFMTHT":{"name":"DIFFMTHT","sections":["GRID"],"supported":false,"summary":"The DIFFMTHT keyword defines the theta direction diffusivity multipliers for cells in the current input box for when the Diffusivity option has been activated by the DIFFUSE keyword in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"DIFFMX-":{"name":"DIFFMX-","sections":["GRID"],"supported":false,"summary":"The DIFFMX- keyword defines the negative x-direction diffusivity multipliers for cells in the current input box for when the Diffusivity option has been activated by the DIFFUSE keyword in the RUNSPEC section.","parameters":[],"example":""},"DIFFMX":{"name":"DIFFMX","sections":["GRID"],"supported":false,"summary":"The DIFFMX keyword defines the x-direction diffusivity multipliers for cells in the current input box for when the Diffusivity option has been activated by the DIFFUSE keyword in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"DIFFMY-":{"name":"DIFFMY-","sections":["GRID"],"supported":false,"summary":"The DIFFMY- keyword defines the negative y-direction diffusivity multipliers for cells in the current input box for when the Diffusivity option has been activated by the DIFFUSE keyword in the RUNSPEC section.","parameters":[],"example":""},"DIFFMY":{"name":"DIFFMY","sections":["GRID"],"supported":false,"summary":"The DIFFMY keyword defines the y-direction diffusivity multipliers for cells in the current input box for when the Diffusivity option has been activated by the DIFFUSE keyword in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"DIFFMZ-":{"name":"DIFFMZ-","sections":["GRID"],"supported":false,"summary":"The DIFFMZ- keyword defines the negative z-direction diffusivity multipliers for cells in the current input box for when the Diffusivity option has been activated by the DIFFUSE keyword in the RUNSPEC section.","parameters":[],"example":""},"DIFFMZ":{"name":"DIFFMZ","sections":["GRID"],"supported":false,"summary":"The DIFFMZ keyword defines the z-direction diffusivity multipliers for cells in the current input box for when the Diffusivity option has been activated by the DIFFUSE keyword in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"DISPERC":{"name":"DISPERC","sections":["GRID"],"supported":null,"summary":"The DISPERC keyword defines the mechanical dispersivity for all cells in the model via an array.","parameters":[{"index":1,"name":"DISPERC","description":"DISPERC is an array of real positive values that defines the mechanical dispersivity for each cell in the model. Repeat counts may be used, for example 20*1.0.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None"}],"example":"The example sets the mechanical dispersivity for all cells in the model to 1.0.\n--\n-- SET MECHANICAL DISPERSIVITY FOR ALL CELLS (OPM FLOW KEYWORD)\n--\nDISPERC\n1000*1.0 /\n| Note The option has been tested in combination with the CO2STORE, H2STORE, BIOFILM, or MICP keywords, but not for the general case at this point. |\n|---------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"array"},"DOMAINS":{"name":"DOMAINS","sections":["GRID"],"supported":false,"summary":"The DOMAINS keyword defines the parallel domain properties for when parallel processing has been invoked by the PARALLEL keyword in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"DPGRID":{"name":"DPGRID","sections":["GRID"],"supported":false,"summary":"The DPGRID keyword activates the matrix cell to fracture cell option for dual porosity runs for when a Dual Porosity model has been activated by either the DUALPORO or DUALPERM keywords in the RUNSPEC section. The keyword allows for only the matrix grid data to be entered and the missing fracture cells are set to the inputted matrix cells.","parameters":[],"example":"","size_kind":"none","size_count":0},"DPNUM":{"name":"DPNUM","sections":["GRID"],"supported":false,"summary":"In dual porosity runs only, that is not dual permeability runs, the DPNUM keyword defines which wells should be treated as single porosity cells and which cells should be treated as dual porosity cells, for when the Dual Porosity model has been activated by the DUALPORO keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"VALUE","description":"","units":{},"default":"","value_type":"INT"}],"example":"","size_kind":"fixed","size_count":1,"variadic_record":true},"DR":{"name":"DR","sections":["GRID"],"supported":false,"summary":"DR defines the size of all grid blocks in the R direction via an array for each cell in the model. The RADIAL or SPIDER keyword in the RUNSPEC section should be activated to indicate that radial or spider geometry is being used.","parameters":[{"index":1,"name":"DR","description":"DR is an array of real numbers describing the cell size in the R direction for each cell in the model in a radial grid. Repeat counts may be used, for example 10*100.0.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None"}],"example":"Given the dimensions of the grid in the RUNSPEC section to be 10,1, 8 for NX, NY and NZ respectively, we first define the inner radius of the radial model,\n--\n-- INNER RADIUS OF FIRST GRID BLOCK IN THE RADIAL DIRECTION\n--\nINRAD\n0.25\n/\nand then DR should be defined as:\n--\n-- DEFINE GRID BLOCK R DIRECTION CELL SIZE\n--\nDR\n1.75 2.32 5.01 10.84 23.39 50.55 109.21 235.92 509.68 1101.0\n1.75 2.32 5.01 10.84 23.39 50.55 109.21 235.92 509.68 1101.0\n1.75 2.32 5.01 10.84 23.39 50.55 109.21 235.92 509.68 1101.0\n1.75 2.32 5.01 10.84 23.39 50.55 109.21 235.92 509.68 1101.0\n1.75 2.32 5.01 10.84 23.39 50.55 109.21 235.92 509.68 1101.0\n1.75 2.32 5.01 10.84 23.39 50.55 109.21 235.92 509.68 1101.0\n1.75 2.32 5.01 10.84 23.39 50.55 109.21 235.92 509.68 1101.0\n1.75 2.32 5.01 10.84 23.39 50.55 109.21 235.92 509.68 1101.0\n/\nThe above example defines the size of the cells in the R direction based on 80 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.\nNote that since the first layer (K=1) must be defined and subsequent layers default to the layer above then:\n--\n-- INNER RADIUS OF FIRST GRID BLOCK IN THE RADIAL DIRECTION\n--\nINRAD\n0.25\n/\n--\n-- DEFINE GRID BLOCK R DIRECTION CELL SIZE\n--\nDR\n1.75 2.32 5.01 10.84 23.39 50.55 109.21 235.92 509.68 1101.0\n/\nis equivalent to previous example.","size_kind":"array"},"DRV":{"name":"DRV","sections":["GRID"],"supported":false,"summary":"DRV defines the size of grid blocks in the R direction via a vector as opposed to defining the property for each cell for a Radial or Spider Grid. The RADIAL or SPIDER keyword in the RUNSPEC section should be activated to indicate that radial or spider geometry is being used.","parameters":[{"index":1,"name":"DRV","description":"DRV is a vector of real numbers describing the cell size for the grid blocks in the R direction in a radial grid. Repeat counts may be used, for example 10*100.0.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None"}],"example":"--\n-- INNER RADIUS OF FIRST GRID BLOCK IN THE RADIAL DIRECTION\n--\nINRAD\n0.25\n/\n--\n-- DEFINE GRID BLOCK SIZES IN THE R DIRECTION\n--\nDRV\n1.75 2.32 5.01 10.84 23.39 50.55 109.21 235.92 509.68 1101.08 /\nThe above example defines the size of the cells in the R direction based on NX equals 10 on the DIMENS keyword in the RUNSPEC section. Note the INRAD keyword to define the inner radius of the radial grid.","size_kind":"array"},"DTHETA":{"name":"DTHETA","sections":["GRID"],"supported":false,"summary":"DTHETA defines the size of all grid blocks in the Theta direction via an array for each cell in model. The RADIAL or SPIDER keyword in the RUNSPEC section should be activated to indicate that radial or spider geometry is being used.","parameters":[{"index":1,"name":"DTHETA","description":"DTHETA is an array of real numbers describing the cell size in the THETA direction in radial grids for each cell in the model. Repeat counts may be used, for example 10*25.0","units":{"field":"degrees","metric":"degrees","laboratory":"degrees"},"default":"None"}],"example":"Given the dimensions of the grid in the RUNSPEC section to be 10, 6, 1 for NX, NY and NZ respectively, then DTHETA should be defined as:\n--\n-- DEFINE GRID BLOCK SIZES IN THE THETA DIRECTION\n--\nDTHETA\n10*60.0\n10*60.0\n10*60.0\n10*60.0\n10*60.0\n10*60.0\n/\nThe above example defines the size of the cells in the R direction based on 60 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"DTHETAV":{"name":"DTHETAV","sections":["GRID"],"supported":null,"summary":"DTHETAV defines the size of grid blocks in the THETA direction via a vector as opposed to defining the property for each cell for a Radial Grid. The RADIAL or SPIDER keyword in the RUNSPEC should be activated to indicate that radial geometry is being used.","parameters":[{"index":1,"name":"DTHETAV","description":"DTHETAV is a vector of real numbers describing the cell size for the grid blocks in the THETA direction in a radial grid. Repeat counts may be used, for example 10*100.0.","units":{"field":"degrees","metric":"degrees","laboratory":"degrees"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK SIZES IN THE THETA DIRECTION (BASED ON NY = 6)\n--\nDTHETAV\n60.0 60.0 60.0 60.0 60.0 60.0 /\nThe above example defines the size of the cells in the THETA direction based on NY equals six in the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"DUMPFLUX":{"name":"DUMPFLUX","sections":["GRID"],"supported":null,"summary":"This keyword activates the writing out of a full field (the full grid) FLUX file for later processing in a Flux Boundary run. The Flux Boundary feature allows for the segmentation of the full grid into flux boundary areas which allow for a sub-area of the grid to be run and at the same time model the flux across the boundary derived from the main grid. The object of this feature is to be able to investigate the performance of various areas of the model without having to run the full field, thus improving computational efficiency and run times, but still obtain “reasonable” results due to the incorporation of the fluxes across the boundary.","parameters":[],"example":"--\n-- ACTIVATE WRITING OUT OF A FLUX FILE\n--\nDUMPFLUX /\nThe above example switches on the writing of the FLUX output file; the keyword has no effect and is ignored by the simulator.","size_kind":"none","size_count":0},"DX":{"name":"DX","sections":["GRID"],"supported":null,"summary":"DX defines the size of all grid blocks in the X direction via an array for each cell in a Cartesian Regular Grid model.","parameters":[{"index":1,"name":"DX","description":"DX is an array of real numbers describing the cell size in the X direction for each cell in the model. Repeat counts may be used, for example 10*100.0.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK X DIRECTION CELL SIZE (BASED ON NX x NY x NZ = 300)\n--\nDX\n300*1000 /\nThe above example defines the size of the cells in the X direction based on 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"DXV":{"name":"DXV","sections":["GRID"],"supported":null,"summary":"DXV defines the size of grid blocks in the X direction via a vector as opposed to defining the X direction cell size for each cell for a Cartesian Regular Grid.","parameters":[{"index":1,"name":"DXV","description":"DXV is a vector of real numbers describing the cell size for the grid blocks in the X direction. Repeat counts may be used, for example 10*100.0.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK X DIRECTION CELL SIZE (BASED ON NX = 5)\n--\nDXV\n5*100 /\nThe above example defines the size of the cells in the X direction based on NX equals 5 on the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"DY":{"name":"DY","sections":["GRID"],"supported":null,"summary":"DY defines the size of all grid blocks in the Y direction via an array for each cell in a Cartesian Regular Grid model.","parameters":[{"index":1,"name":"DY","description":"DY is an array of real numbers describing the cell size in the Y direction for each cell in the model. Repeat counts may be used, for example 10*100.0.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK Y DIRECTION CELL SIZE (BASED ON NX x NY x NZ = 300)\n--\nDY\n300*1000 /\nThe above example defines the size of the cells in the Y direction based on 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"DYV":{"name":"DYV","sections":["GRID"],"supported":null,"summary":"DYV defines the size of grid blocks in the Y direction via a vector as opposed to defining the Y direction cell size for each cell for a Cartesian Regular Grid.","parameters":[{"index":1,"name":"DYV","description":"DYV is a vector of real numbers describing the cell size for the grid blocks in the Y direction. Repeat counts may be used, for example 10*100.0.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK Y DIRECTION CELL SIZE (BASED ON NY = 5)\n--\nDYV\n5*100 /\nThe above example defines the size of the cells in the Y direction based on NY equals 5 on the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"DZ":{"name":"DZ","sections":["GRID"],"supported":null,"summary":"DZ defines the size of all grid blocks in the Z direction via an array for each cell in a Cartesian Regular Grid model.","parameters":[{"index":1,"name":"DZ","description":"DZ is an array of real numbers describing the cell size in the Z direction for each cell in the model. Repeat counts may be used, for example 10*100.0.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK Z DIRECTION CELL SIZE (BASED ON NX x NY x NZ = 300)\n--\nDZ\n100*20.0 100*30.0 100*50.0 /\nThe above example defines the size of the cells in the Z direction based on 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"DZMATRIX":{"name":"DZMATRIX","sections":["GRID"],"supported":false,"summary":"The DZMATRIX keyword defines the matrix block height for the gravity drainage model by grid block for when the Dual Permeability or Dual Porosity models are activated by the DUALPERM and DUALPORO keywords and the Gravity Drainage option is invoked via the GRAVDR and GRAVDRM keywords. All keywords are in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"DZMTRX":{"name":"DZMTRX","sections":["GRID"],"supported":false,"summary":"The DZMTRX keyword defines a constant matrix block height for the gravity drainage model for the entire grid for when the Dual Permeability or Dual Porosity models are activated by the DUALPERM and DUALPORO keywords and the Gravity Drainage option is invoked via the GRAVDR and GRAVDRM keywords. All keywords are in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"DZMTRXV":{"name":"DZMTRXV","sections":["GRID"],"supported":false,"summary":"The DZMATRIX keyword defines the matrix block height for the gravity drainage model by grid block for when the Dual Permeability or Dual Porosity models are activated by the DUALPERM and DUALPORO keywords and the Gravity Drainage option is invoked via the GRAVDR and GRAVDRM keywords. All keywords are in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"DZNET":{"name":"DZNET","sections":["GRID"],"supported":null,"summary":"DZNET defines the net thickness of all grid blocks in the Z direction via an array for each cell in a Cartesian Regular Grid model.","parameters":[{"index":1,"name":"DZNET","description":"DZNET is an array of real numbers describing the net thickness in the Z direction for each cell in the model. Repeat counts may be used, for example 10*100.0. If the value for a grid block is not defined then the grid block size (DZ) is assigned to the missing values.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"DZ"}],"example":"--\n-- DEFINE GRID BLOCK Z DIRECTION NET THICKNESS(BASED ON NX x NY x NZ = 300)\n--\nDZNET\n100*15.0 100*25.0 00*45.0 /\nThe above example defines the net thickness of the cells in the Z direction based on 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"DZV":{"name":"DZV","sections":["GRID"],"supported":null,"summary":"DZV defines the size of grid blocks in the Z direction via a vector as opposed to defining the thickness property for each cell. The keyword is used for both Cartesian Regular Grids and Radial Grids.","parameters":[{"index":1,"name":"DZV","description":"DZV is a vector of real numbers describing the cell size for the grid blocks in the Z direction. Repeat counts may be used, for example 10*20.0.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK SIZES IN THE Z DIRECTION (BASED ON NZ = 20)\n--\nDZV\n3.0 5.0 3.0 2.0 5.0 15*3.0 /\nThe above example defines the size of the cells in the Z direction based on NZ equals 20 on the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"ENDBOX":{"name":"ENDBOX","sections":["GRID","EDIT","PROPS","REGIONS","SOLUTION","SCHEDULE"],"supported":null,"summary":"This keyword marks the end of a previously defined BOX sub-grid as defined by a previously entered BOX keyword. The keyword resets the input grid to be the full grid as defined by the NX, NY, and NZ variables on the DIMENS keyword in the RUNSPEC section.","parameters":[],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n10 10 1 6 1 1 / DEFINE BOX AREA\n--\n--\n-- DEFINE GRID BLOCK PERMZ DATA FOR THE INPUT BOX\n--\nPERMZ\n6*0.01 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe above example defines a subset of the grid and sets the cells PERMZ values to 0.01 for that area. After which the ENDBOX keyword resets the input to be the full grid.\nNote\nIt is good practice to always use the ENDBOX keyword to reset the input back to the full grid when all the modifications for a sub-grid have been completed.\n| Note It is good practice to always use the ENDBOX keyword to reset the input back to the full grid when all the modifications for a sub-grid have been completed. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"none","size_count":0},"ENDFIN":{"name":"ENDFIN","sections":["GRID","EDIT","PROPS","REGIONS","SOLUTION","SCHEDULE"],"supported":false,"summary":"The ENDFIN keyword defines the end of a Cartesian or radial local grid refinement (“LGR”) definition and a LGR property definition data set. In the GRID section the CARFIN, RADFIN, and RADFIN4 keywords defines the start of an LGR description section, whereas the REFINE keyword in the EDIT, PROPS, REGIONS, SOLUTION and SCHEDULE section defines the start. The REFINE keyword can also be used in the GRID section provided the LGR has been previously specified by the CARFIN, RADFIN, or RADFIN4 keywords.","parameters":[],"example":"The example below is based on using the CARFIN keyword in the GRID section to define an LGR in the global grid, named LGR-OP01 with a maximum of one well allowed in the LGR.\n--\n-- CARFIN LGR GRID COMMANDS\n--\n-- LGR ----- FINE GRID ------ -- CARFIN GRID -- MAX HOST\n-- NAME I1 I2 J1 J2 K1 K2 NX NY NZ WELLS NAME\nCARFIN\nLGR-OP01 24 24 87 87 1 50 3 3 50 1 GLOBAL /\nENDFIN\nHere the one global cell in the areal plane (24, 87) is divided into three LGR cells in the x-direction and three cells in the y-direction. Since no other property data is given, then the LGR cells take their properties from the host grid, that is the global grid.","size_kind":"none","size_count":0},"EQLZCORN":{"name":"EQLZCORN","sections":["GRID"],"supported":false,"summary":"The EQLZCORN keyword modifies the depth of a corner point of a grid block on the pillars defining the reservoir grid. The keyword can be only used be used with Irregular Corner-Point Grids.","parameters":[{"index":1,"name":"VALUE_ZCORN_ARRAY","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":2,"name":"IX1","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"IX2","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"JY1","description":"","units":{},"default":"","value_type":"INT"},{"index":5,"name":"JY2","description":"","units":{},"default":"","value_type":"INT"},{"index":6,"name":"KZ1","description":"","units":{},"default":"","value_type":"INT"},{"index":7,"name":"KZ2","description":"","units":{},"default":"","value_type":"INT"},{"index":8,"name":"IX1A","description":"","units":{},"default":"","value_type":"INT"},{"index":9,"name":"IX2A","description":"","units":{},"default":"","value_type":"INT"},{"index":10,"name":"JY1A","description":"","units":{},"default":"","value_type":"INT"},{"index":11,"name":"JY2A","description":"","units":{},"default":"","value_type":"INT"},{"index":12,"name":"ACTION_REQ","description":"","units":{},"default":"TOP","value_type":"STRING"}],"example":"","expected_columns":12,"size_kind":"list"},"EQUALREG":{"name":"EQUALREG","sections":["GRID","EDIT","PROPS","REGIONS","SOLUTION"],"supported":false,"summary":"The EQUALREG keyword sets a specified array to a constant for cells with a specific region number. The region number array can be FLUXNUM, MULTNUM or OPERNUM and these arrays must be defined and be available before the EQUALREG keyword is read by the simulator. The constant can be an integer or real value depending on the array type; however, the arrays that can be operated on are dependent on which section the EQUALREG keyword is being applied in.","parameters":[{"index":1,"name":"ARRAY","description":"A character string of up to eight characters in length that defines the keyword identifying the array to be modified.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"CONSTANT","description":"An integer or real value to be assigned to the ARRAY in the same units as the ARRAY property for a given REGION","units":{},"default":"0","value_type":"DOUBLE"},{"index":3,"name":"REGION NUMBER","description":"REGION NUMBER is a positive integer representing the region for which the CONSTANT in (2) should be applied","units":{},"default":"None","value_type":"INT"},{"index":4,"name":"REGION ARRAY","description":"The REGION ARRAY to use for applying the CONSTANT in (2) based on the REGION NUMBER in (3). REGION ARRAY can have the following values: F for the FLUXNUM array M for the MULTNUM array O for the OPERNUM array","units":{},"default":"M","value_type":"STRING"}],"example":"-- FIRST DEFINE MULTNUM ARRAYS FOR 10 X 10 X 20 MODEL\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nMULTNUM 1 1* 1* 1* 1* 1* 1* / MULTNUM IN MODEL\nMULTNUM 2 1* 1* 1* 1* 6 6 / MULTNUM IN MODEL\nMULTNUM 3 1* 1* 1* 1* 10 10 / MULTNUM IN MODEL\n/\n-- NOW SET PORO AND PERMX BASED ON THE MULTNUM REGION NUMBER\n--\n-- SETS A CONSTANT TO AN ARRAY BASED ON A REGION NUMBER\n--\n-- ARRAY CONSTANT REGION REGION ARRAY\n-- VALUE NUMBER M / F / O EQUALREG\nPORO 0.200 1 M /\nPORO 0.150 2 M /\nPORO 0.120 3 M /\nPERMX 100.00 1 M /\nPERMX 75.00 2 M /\nPERMX 50.00 3 M /\n/\nThe example first defines the MULTNUM array to 1 for all cells in the model, after which selected areas of model are assigned various MULTNUM integer values. The EQUALREG can then be invoked to set constant values for the PORO and PERMX arrays for the various MULTNUM regions.\n| EQUALREG Keyword and Variable Options by Section | | | | | | |\n|--------------------------------------------------|---------|-------|---------|----------|---------|----------|\n| GRID | EDIT | PROPS | REGIONS | SOLUTION | SUMMARY | SCHEDULE |\n| DX | DEPTH | SWL | ENDNUM | PRESSURE | | |\n| DY | PORV | SWCR | EQLNUM | SWAT | | |\n| DZ | TRANX | SWU | FIPNUM | SGAS | | |\n| PERMX | TRANY | SGL | IMBNUM | RV | | |\n| PERMY | TRANZ | SGCR | MISCNUM | RS | | |\n| PERMZ | DIFFX | SGU | PVTNUM | TBLK | | |\n| MULTX | DIFFY | KRW | ROCKNUM | GI | | |\n| MULTY | DIFFZ | KRO | SATNUM | OILAPI | | |\n| MULTZ | TRANR | KRG | WH2NUM | SALT | | |\n| DR | TRANTHT | PCG | | GASCONC | | |\n| DTHETA | DIFFR | PCW | | SOLVCONC | | |\n| PERMR | DIFFTHT | | | SOLVFRAC | | |\n| PERMTHT | | | | SFOAM | | |\n| DZNET | | | | SPOLY | | |\n| PORO | | | | | | |\n| NTG | | | | | | |\n| FLUXNUM | | | | | | |\n| MULTNUM | | | | | | |\n| MPFANUM | | | | | | |\n| DIFFX | | | | | | |\n| DIFFY | | | | | | |\n| DIFFZ | | | | | | |\n| DIFFR | | | | | | |\n| DIFFTHT | | | | | | |","expected_columns":4,"size_kind":"list"},"EQUALS":{"name":"EQUALS","sections":["GRID","EDIT","PROPS","REGIONS","SOLUTION"],"supported":false,"summary":"The EQUALS keyword sets a specified array or part of an array to a constant. The constant can be an integer or real value depending on the array type; however, the arrays that can be operated on are dependent on which section the EQUALS keyword is being applied in.","parameters":[{"index":1,"name":"ARRAY","description":"A character string of up to eight characters in length that defines the keyword identifying the property to be modified.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"CONSTANT","description":"An integer or real value that the ARRAY will be set to in the same units as the ARRAY property.","units":{},"default":"None","value_type":"DOUBLE"},{"index":3,"name":"I1","description":"A positive integer that defines the lower bound of the array in the I-direction to be modified must be greater than or equal to one and less than or equal to I2 and NX.","units":{},"default":"1","value_type":"INT"},{"index":4,"name":"I2","description":"A positive integer that defines the upper bound of the array in the I-direction to be modified must be greater than or equal to II and less than or equal to NX","units":{},"default":"NX","value_type":"INT"},{"index":5,"name":"J1","description":"A positive integer that defines the lower bound of the array in the J-direction to be modified must be greater than or equal to one and less than or equal to J2 and NY.","units":{},"default":"1","value_type":"INT"},{"index":6,"name":"J2","description":"A positive integer that defines the upper bound of the array in the J-direction to be modified must be greater than or equal to JI and less than or equal to NY.","units":{},"default":"NY","value_type":"INT"},{"index":7,"name":"K1","description":"A positive integer that defines the lower bound of the array in the K-direction to be modified must be greater than or equal to one and less than or equal to K2 and NZ.","units":{},"default":"1","value_type":"INT"},{"index":8,"name":"K2","description":"A positive integer that defines the upper bound of the array in the K-direction to be modified must be greater than or equal to KI and less than or equal to NZ.","units":{},"default":"NZ","value_type":"INT"}],"example":"The first example resets the PERMX, PERMY and PERMZ, arrays to 0.10, 0.10, and 0.01 for all cells in layer five, respectively.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n- I1 I2 J1 J2 K1 K2\nEQUALS\nPERMX 0.1000 1* 1* 1* 1* 5 5 / PERMX TO 0.10 IN LAYER 5\nPERMY 0.1000 1* 1* 1* 1* 5 5 / PERMY TO 0.10 IN LAYER 5\nPERMZ 0.0100 1* 1* 1* 1* 5 5 / PERMZ TO 0.01 IN LAYER 5\n/\nThe second example illustrates how to correctly setup a Cartesian Regular Grid in OPM Flow, given the DIMENS keyword in the RUNSPEC section is set to:\n--\n-- MAX MAX MAX\n-- NDIVIX NDIVIY NDIVIZ\nDIMENS\n10 10 3 /\nand the following keywords in the GRID section:\n--\n-- ACTIVATE IRREGULAR CORNER-POINT GRID TRANSMISSIBILITIES\n--\nOLDTRAN\n--\n-- DEFINE GRID BLOCK X DIRECTION CELL SIZE (BASED ON NX = 5)\n--\nDX\n300*1000 /\n--\n-- DEFINE GRID BLOCK Y DIRECTION CELL SIZE (BASED ON NY = 5)\n--\nDY\n300*1000 /\n--\n-- DEFINE GRID BLOCK SIZES IN THE Z DIRECTION\n--\nDZ\n100*20 100*30 100*50 /\n--\n-- DEFINE GRID BLOCK TOPS FOR THE TOP LAYER\n--\nTOPS\n100*8325 /\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nPERMX 500.000 1* 1* 1* 1* 1 1 / Layer #01 Properties\nPERMY 500.000 /\nPERMZ 20.000 /\nPORO 0.300 /\nNTG 1.000 /\nPERMX 50.000 1* 1* 1* 1* 2 2 / Layer #02 Properties\nPERMY 50.000 /\nPERMZ 50.000 /\nPORO 0.300 /\nNTG 1.000 /\nPERMX 200.000 1* 1* 1* 1* 3 3 / Layer #03 Properties\nPERMY 200.000 /\nPERMZ 200.000 /\nPORO 0.300 /\nNTG 1.000 /\n/\nNotice that the DX, DY, DZ and TOPS keywords are defined separately, that is they are not included in the EQUALS keyword.\n| EQUALS Keyword and Variable Options by Section | | | | | | |\n|------------------------------------------------|---------|-------|---------|----------|---------|----------|\n| GRID | EDIT | PROPS | REGIONS | SOLUTION | SUMMARY | SCHEDULE |\n| DX | DEPTH | SWL | ENDNUM | PRESSURE | | |\n| DY | PORV | SWCR | EQLNUM | SWAT | | |\n| DZ | TRANX | SWU | FIPNUM | SGAS | | |\n| PERMX | TRANY | SGL | IMBNUM | RV | | |\n| PERMY | TRANZ | SGCR | MISCNUM | RS | | |\n| PERMZ | DIFFX | SGU | PVTNUM | TBLK | | |\n| MULTX | DIFFY | KRW | ROCKNUM | GI | | |\n| MULTY | DIFFZ | KRO | SATNUM | OILAPI | | |\n| MULTZ | TRANR | KRG | WH2NUM | SALT | | |\n| DR | TRANTHT | PCG | | GASCONC | | |\n| DTHETA | DIFFR | PCW | | SOLVCONC | | |\n| PERMR | DIFFTHT | | | SOLVFRAC | | |\n| PERMTHT | | | | SFOAM | | |\n| DZNET | | | | SPOLY | | |\n| PORO | | | | | | |\n| NTG | | | | | | |\n| FLUXNUM | | | | | | |\n| MULTNUM | | | | | | |\n| MPFANUM | | | | | | |\n| DIFFX ","expected_columns":8,"size_kind":"list"},"EXTFIN":{"name":"EXTFIN","sections":["GRID"],"supported":false,"summary":"The EXTFIN keyword defines an external Unstructured Local Grid Refinement (“LGR”) in a cell or a group of cells in the global grid, and for when LGRs have been activated for the model using the LGR keyword in the RUNSPEC section. Note the global grid can be either structured, see the EXTREPGL keyword in the GRID section for global structure grids, or unstructured, see the EXTHOST keyword in the GRID section for unstructured global grids.","parameters":[{"index":1,"name":"LOCAL_GRID_REF","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"NX","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"NY","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"NZ","description":"","units":{},"default":"","value_type":"INT"},{"index":5,"name":"NREPG","description":"","units":{},"default":"","value_type":"INT"},{"index":6,"name":"NHALO","description":"","units":{},"default":"","value_type":"INT"},{"index":7,"name":"NFLOG","description":"","units":{},"default":"","value_type":"INT"},{"index":8,"name":"NUMINT","description":"","units":{},"default":"","value_type":"INT"},{"index":9,"name":"NUMCON","description":"","units":{},"default":"","value_type":"INT"},{"index":10,"name":"NWMAX","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":10,"size_kind":"fixed","size_count":1},"EXTHOST":{"name":"EXTHOST","sections":["GRID"],"supported":false,"summary":"The EXTHOST keyword defines the host global grid blocks for an external Local Grid Refinement (“LGR”) for when LGRs have been activated for the model using the LGR keyword in the RUNSPEC section, and the global grid is an unstructured grid.","parameters":[],"example":"","size_kind":"array"},"EXTREPGL":{"name":"EXTREPGL","sections":["GRID"],"supported":false,"summary":"The EXTREPGL keyword defines the host global grid blocks for an external Unstructured Local Grid Refinement (“LGR”) for when LGRs have been activated for the model using the LGR keyword in the RUNSPEC section, and the global grid is a structured grid.","parameters":[],"example":"","size_kind":"array"},"FAULTS":{"name":"FAULTS","sections":["GRID"],"supported":null,"summary":"The FAULTS keyword defines the faults in the grid geometry and the keyword is normally exported with the grid geometry COORD and ZCORN data sets from static earth modeling software. Note that the FAULTS keyword is not required to describe the structural geometry as this is already accounted for in the COORD and ZCORN data sets, but instead lists the fault traces with respect to the grid. Once the fault traces have been defined with the FAULTS keyword then the fault transmissibilities can be modified by the MULTFLT keyword. Note that without the FAULTS keyword one would still get proper cross-fault transmissibilities but they would not be modifiable using MULTFLT keyword.","parameters":[{"index":1,"name":"FLTNAME","description":"FLTNAME is a character string enclosed in quotes with a maximum length of eight characters, that defines the name of the fault.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"I1","description":"The lower bound of the fault’s I-direction range must be greater than or equal to one and less than or equal to I2 and NX.","units":{},"default":"None","value_type":"INT"},{"index":3,"name":"I2","description":"The upper bound of the fault’s I-direction range must be greater than or equal to II and less than or equal to NX","units":{},"default":"None","value_type":"INT"},{"index":4,"name":"J1","description":"The lower bound of the fault’s J-direction range must be greater than or equal to one and less than or equal to J2 and NY.","units":{},"default":"None","value_type":"INT"},{"index":5,"name":"J2","description":"The upper bound of the fault’s J-direction range must be greater than or equal to JI and less than or equal to NY.","units":{},"default":"None","value_type":"INT"},{"index":6,"name":"K1","description":"The lower bound of the fault’s K-direction range must be greater than or equal to one and less than or equal to K2 and NZ.","units":{},"default":"None","value_type":"INT"},{"index":7,"name":"K2","description":"The upper bound of the fault’s K-direction range must be greater than or equal to KI and less than or equal to NZ.","units":{},"default":"None","value_type":"INT"},{"index":8,"name":"FLTFACE","description":"Unknown Author\n 2017-06-27T13:59:19\n I am not able to review this properly, as I am not familiar enough with what is supposed to happen. I do not know if we support X-, Y-, Z- transmissibilities.\n FLTFACE is a character string enclosed in quotes with a maximum length of two characters, that classifies the fault face. I am not able to review this properly, as I am not familiar enough with what is supposed to happen. I do not know if we support X-, Y-, Z- transmissibilities. If TRANSMULT on the GRIDOPTS keyword in the RUNSPEC section is set to NO then FLTFACE can have values of X, Y, or Z. Alternatively, if TRANSMULT on the GRIDOPTS keyword in the RUNSPEC section is set to YES then FLTFACE can have values of X, Y, or Z for the positive direction, or X-, Y- or Z- for the negative direction transmissibilities.","units":{},"default":"None","value_type":"STRING"}],"example":"The example below defines two fault traces, the first being the ‘M_WEST’ fault and the second the ‘BC’ fault trace.\n--\n-- DEFINE FAULTS IN THE GRID GEOMETRY\n--\n-- FAULT ------------ FAULT TRACE -------------\n-- NAME I1 I2 J1 J2 K1 K2 FACE\nFAULTS\n'M_WEST' 5 5 3 3 1 22 'X' /\n'M_WEST' 5 5 4 4 1 22 'X' /\n'M_WEST' 5 5 5 5 1 22 'X' /\n'M_WEST' 5 5 6 6 1 22 'X' /\n'M_WEST' 5 5 7 7 1 22 'X' /\n'M_WEST' 5 5 8 8 1 22 'X' /\n'M_WEST' 5 5 9 9 1 22 'X' /\n'M_WEST' 5 5 10 10 1 22 'X' /\n'M_WEST' 5 5 11 11 1 22 'X' /\n……………………………………………..\n'BC' 43 43 8 8 1 22 'Y' /\n'BC' 42 42 9 9 1 22 'X' /\n'BC' 44 44 8 8 1 22 'Y' /\n'BC' 45 45 8 8 1 22 'Y' /\n'BC' 46 46 8 8 1 22 'Y' /\n'BC' 31 31 9 9 1 22 'Y' /\n'BC' 30 30 10 10 1 22 'X' /\n'BC' 32 32 9 9 1 22 'Y' /\n'BC' 33 33 9 9 1 22 'Y' /\n'BC' 34 34 9 9 1 22 'Y' /\n'BC' 35 35 9 9 1 22 'Y' /\n'BC' 36 36 9 9 1 22 'Y' /\n'BC' 37 37 9 9 1 22 'Y' /\n'BC' 38 38 9 9 1 22 'Y' /\n'BC' 39 39 9 9 1 22 'Y' /\n'BC' 40 40 9 9 1 22 'Y' /\n……………………………………………..\n/","expected_columns":8,"size_kind":"list"},"FILEUNIT":{"name":"FILEUNIT","sections":["GRID","EDIT","PROPS","REGIONS","SOLUTION","SCHEDULE"],"supported":null,"summary":"The FILEUNIT keyword defines the units of the data set, and is used to verify that the units in the input deck and any associated include files are consistent. The keyword does not provide for the conversion between different sets of units.","parameters":[{"index":1,"name":"FILEUNIT","description":"A character string that defines the units of the data set, and should be set to: FIELD for field units, METRIC for metric units, or LAB for laboratory units","units":{},"default":"None","value_type":"STRING"}],"example":"--\n-- ACTIVATE UNIT CONSISTENCY CHECKING\n--\nFILEUNIT\nFIELD /\nThe above example defines the data set units to be FIELD units.","expected_columns":1,"size_kind":"fixed","size_count":1},"FLUXNUM":{"name":"FLUXNUM","sections":["GRID"],"supported":null,"summary":"The FLUXNUM keyword defines the flux region numbers for each grid block, as such there must be one entry for each cell in the model. The array is used with the Flux Boundary option to define the various flux regions; however, the Flux Boundary option has not been implemented in OPM Flow. In addition, the array can be used with the EQUALREG, ADDREG, COPYREG, MULTIREG, MULTREGP and MULTREGT keywords in calculating various grid properties in the GRID section. This facility has been implemented in OPM Flow.","parameters":[{"index":1,"name":"FLUXNUM","description":"FLUXNUM defines an array of positive integers assigning a grid cell to a particular flux region. The maximum number of flux regions is set by the MXNFLX variable on the REGDIMS keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"The example below sets three FLUXNUM regions for a 4 x 5 x 2 model.\n--\n-- DEFINE FLUXNUM REGIONS FOR ALL CELLS\n--\nFLUXNUM\n2 2 1 1 2 2 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n3 3 1 1 3 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n/\nAlternatively the EQUALS keyword could be employed to accomplish the same task, that is:\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nFLUXNUM 1 1* 1* 1* 1* 1* 1* / SET REGION 1\nFLUXNUM 2 1 2 1 2 1 1 / SET REGION 2\nFLUXNUM 3 1 2 1 2 2 2 / SET REGION 3\n/","size_kind":"array"},"FLUXREG":{"name":"FLUXREG","sections":["GRID"],"supported":false,"summary":"The FLUXREG is used in conjunction with the USEFLUX keyword in runs with have multiple flux regions, to reduce the number of flux regions, that is the keyword specifies which flux regions are active and which are not in the current run.","parameters":[],"example":"","size_kind":"array"},"FLUXTYPE":{"name":"FLUXTYPE","sections":["GRID"],"supported":false,"summary":"The FLUXTYPE keyword defines the type of flux boundary to be used in the run.","parameters":[{"index":1,"name":"BC_TYPE","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"GDFILE":{"name":"GDFILE","sections":["GRID"],"supported":null,"summary":"The GDFILE keyword loads a GRID file that contains the structural data for the grid as a set of topological cuboidal cells, and EGRID files that contain structural and property data. Note OPM Flow only supports reading in EGRID files at this time.","parameters":[{"index":1,"name":"GRIDFILE","description":"A character string enclosed in quotes that defines the GRID or EGRID file to be read in and be processed by OPM Flow. Again, OPM Flow only supports reading in EGRID files.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"FMTOPT","description":"A defined character string that defines the format of the GRID or EGRID file to be read and should be set to one of the following: FORMATTED: If the file is formatted as ASCII i.e. a text file, as oppose to a binary file. The option can be abbreviated to just the letter F. UNFORMATTED: If the file is in binary format, note this option can be abbreviated to just the letter U. If the variable FMTOPT is omitted then the default is for binary file input for the commercial simulator; whereas, OPM Flow derives FMTOPT from the file extension (*.EGRID or *.FEGRID), making FMTOPT superfluous.","units":{},"default":"U","value_type":"STRING"}],"example":"The first example shown below loads the NOR-OPM-A00-GRID.EGRID file in binary format from the same directory as the data file.\n--\n-- LOAD A GRID FILE\n--\nGDFILE\n'NOR-OPM-A00-GRID.EGRID' /\nThe next example loads the same EGRID file one directory above from where the data file is located.\n--\n-- LOAD a GRID FILE\n--\nGDFILE\n'../NOR-OPM-A00-GRID.EGRID' /","expected_columns":2,"size_kind":"fixed","size_count":1},"GDORIENT":{"name":"GDORIENT","sections":["GRID"],"supported":false,"summary":"This keyword defines the grid orientation parameters for post-processing applications.","parameters":[{"index":1,"name":"I","description":"","units":{},"default":"INC","value_type":"STRING"},{"index":2,"name":"J","description":"","units":{},"default":"INC","value_type":"STRING"},{"index":3,"name":"K","description":"","units":{},"default":"INC","value_type":"STRING"},{"index":4,"name":"Z","description":"","units":{},"default":"DOWN","value_type":"STRING"},{"index":5,"name":"HAND","description":"","units":{},"default":"RIGHT","value_type":"STRING"}],"example":"","expected_columns":5,"size_kind":"fixed","size_count":1},"GETDATA":{"name":"GETDATA","sections":["GRID","EDIT","PROPS","REGIONS","SOLUTION"],"supported":false,"summary":"The GETDATA keyword loads a data array from a previously generated INIT or RESTART file and assigns the loaded array to either same array in the run or another property array.","parameters":[{"index":1,"name":"FILENAME","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"FORMATTED","description":"","units":{},"default":"UNFORMATTED","value_type":"STRING"},{"index":3,"name":"ZNAME","description":"","units":{},"default":"","value_type":"STRING"},{"index":4,"name":"ZALT","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":4,"size_kind":"fixed","size_count":1},"GRID":{"name":"GRID","sections":["GRID"],"supported":null,"summary":"The GRID activation keyword marks the end of the RUNSPEC section and the start of the GRID section that defines the key grid property data for the simulator including the grid structure, porosity, permeability and other relevant grid property data.","parameters":[],"example":"-- ==============================================================================\n--\n-- GRID SECTION\n--\n-- ==============================================================================\nGRID\nThe above example marks the end of the RUNSPEC section and the start of the GRID section in the OPM Flow data input file.","size_kind":"none","size_count":0},"GRIDFILE":{"name":"GRIDFILE","sections":["GRID"],"supported":true,"summary":"This keyword controls the output of a standard GRID or extended GRID file, as well as the extensible EGRID file for post-processing applications. The extended and extensible GRID formats are comparable; however, the extensible GRID format is more compact and is the only format supported by OPM Flow.","parameters":[{"index":1,"name":"NGRID","description":"A positive integer that controls the output of the GRID geometry file: - for no GRID file to be written out. - for the standard GRID file to be written out. - for the extended GRID file to be written out. Only the default value of zero is supported.","units":{},"default":"0","value_type":"INT"},{"index":2,"name":"NEGRID","description":"A positive integer that controls the output of the EGRID geometry file: - for no extensible GRID file to be written out. - for the extensible GRID file to be written out. Only the default value of one is supported.","units":{},"default":"1","value_type":"INT"}],"example":"--\n-- GRID FILE OUTPUT OPTIONS\n-- GRID EGRID\n-- OPTN OPTN\nGRIDFILE\n0 1 /\nThe above example defines that no GRID file will be written out and that the extensible GRID (that is the EGRID geometry format) file will be produced. This is the only configuration that OPM Flow supports","expected_columns":2,"size_kind":"fixed","size_count":1},"GRIDUNIT":{"name":"GRIDUNIT","sections":["GRID"],"supported":null,"summary":"The GRIDUNIT keyword defines the units of the grid data. It is usually output by pre-processing software when exporting the grid geometry. The data is not used by OPM Flow intrinsically, but is merely written to the output EGRID file, as specified by the GRIDFILE keyword, for the use of post-processing software like OPM ResInsight.","parameters":[{"index":1,"name":"GRIDUNIT","description":"A character string that defines the units of the coordinates stated on the MAPAXES keyword, and should be set to: FEET for field units, METRES for metric units, or CM for laboratory units.","units":{},"default":"METRES","value_type":"STRING"},{"index":2,"name":"MAPOPT","description":"A character string that defines if the grid data are measured relative to the map, or relative to the origin as stated on the MAPAXES keyword. MAPOPT should either be left blank (the default) indicating the origin is relative to the origin on the MAPAXES keyword, or set equal to MAP measured relative to the map.","units":{},"default":"1*","value_type":"STRING"}],"example":"--\n-- SET THE GRID UNITS FOR THE GRID\n--\nGRIDUNIT\nMETRES /\nThe above example defines that the GRID units to be metric.","expected_columns":2,"size_kind":"fixed","size_count":1},"HALFTRAN":{"name":"HALFTRAN","sections":["GRID"],"supported":false,"summary":"The HALFTRAN keyword activates the half block transmissibility calculation option.","parameters":[],"example":"","size_kind":"none","size_count":0},"HEATCR":{"name":"HEATCR","sections":["GRID"],"supported":null,"summary":"The HEATCR keyword defines the reservoir rock volumetric heat capacity for all cells for when OPM Flow’s thermal calculation is activated by the THERMAL keywords in the RUNSPEC section.","parameters":[{"index":1,"name":"HEATCR","description":"HEATCR is an array of real positive numbers that define reservoir rock volumetric heat capacity of a grid block. Repeat counts may be used, for example 3000*25.0","units":{"field":"Btu/ft3/°R","metric":"kJ/m3/K","laboratory":"J/cm3/K"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK RESERVOIR ROCK HEAT CAPACITY\n-- FOR ALL CELLS (BASED ON NX x NY x NZ = 300)\n-- KEYWORD IS INCOMPATIBLE WITH THE SPECROCK KEYWORD\n-- (OPM FLOW THERMAL OPTION ONLY)\n--\nHEATCR\n300*32.0 /\nThe above example defines the reservoir rock volumetric heat capacity of 32.0 for each cell in the 300 grid block model.","size_kind":"array"},"HEATCRT":{"name":"HEATCRT","sections":["GRID"],"supported":null,"summary":"The HEATCRT keyword defines the reservoir rock volumetric heat capacity temperature dependence for all cells for when OPM Flow’s thermal calculation is activated by the THERMAL keywords in the RUNSPEC section.","parameters":[{"index":1,"name":"HEATCRT","description":"HEATCRT is an array of real positive numbers that define reservoir rock volumetric heat capacity temperature dependence of a grid block. Repeat counts may be used, for example 3000*0.05","units":{"field":"Btu/ft3/°R2","metric":"kJ/m3/K2","laboratory":"J/cm3/K2"},"default":"None"}],"example":"--\n-- DEFINE RESERVOIR ROCK HEAT CAPACITY TEMPERATURE DEPENDENCE\n-- FOR ALL CELLS (BASED ON NX x NY x NZ = 300)\n-- KEYWORD IS INCOMPATIBLE WITH THE SPECROCK KEYWORD\n-- (OPM FLOW THERMAL OPTION ONLY)\n--\nHEATCRT\n300*0.05 /\nThe above example defines the reservoir rock volumetric heat capacity temperature dependence of 0.05 for each cell in the 300 grid block model.\n| [\"Heat Capacity of Rock \"=\"HEATCR\" LEFT(Temp ~-~Temp sub{ref} right)~+~{\"HEATCRT\"left(Temp ~-~Temp sub{ref} right) sup{2}} over { 2}] | (6.3) |\n|---------------------------------------------------------------------------------------------------------------------------------------|-------|","size_kind":"array"},"HMAQUNUM":{"name":"HMAQUNUM","sections":["GRID"],"supported":false,"summary":"The HMAQUNUM keyword defines the history match numerical aquifer gradient parameters for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section, and numerical aquifers have been specified in the model via the AQUNUM keyword and connected to the grid using AQUCON keyword. All keywords are in the GRID section.","parameters":[{"index":1,"name":"AQUIFER_ID","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"DERIVATIES_RESP_PORE_VOL_MULT","description":"","units":{},"default":"NO","value_type":"STRING"},{"index":3,"name":"DERIVATIES_RESP_AQUIFER_PERM_MULT","description":"","units":{},"default":"","value_type":"STRING"},{"index":4,"name":"DERIVATIES_RESP_AQUIFER_GRID_CON_TRANS","description":"","units":{},"default":"NO","value_type":"STRING"}],"example":"","expected_columns":4,"size_kind":"list"},"HMFAULTS":{"name":"HMFAULTS","sections":["GRID"],"supported":false,"summary":"The HMFAULTS keyword defines the history match faults gradient parameters for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section, and for when the FAULTS keyword in the GRID section has been used to define faults in the model.","parameters":[{"index":1,"name":"FAULT_SEGMENT","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"list"},"HMMLAQUN":{"name":"HMMLAQUN","sections":["GRID"],"supported":false,"summary":"The HMMLAQUN keyword defines the history match numerical aquifer gradient multipliers for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section, and numerical aquifers have been specified in the model via the AQUNUM keyword and connected to the grid using the AQUCON keyword. All keywords are in the GRID section.","parameters":[{"index":1,"name":"AQUIFER_ID","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"AQUIFER_PORE_VOL_MULT","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"AQUIFER_PORE_PERM_MULT","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"},{"index":4,"name":"AQUIFER_GRID_CONN_MULT","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"}],"example":"","expected_columns":4,"size_kind":"list"},"HMMLT":{"name":"HMMLT","sections":["GRID"],"supported":false,"summary":"The HMMLT series of keywords defines the history match gradient cumulative permeability multipliers, for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section. The keyword consists of the first five characters of “HMMLT” followed by a two or three character string shown in Table 6.45, that determines the permeability direction, for example, HMMLTPX.","parameters":[],"example":"| Mnemonic | Cartesian Grid | Radial Grid | | |\n|--------------|----------------|--------------|----------------|---------|\n| Grid Keyword | HMMULT Keyword | Grid Keyword | HMMULT Keyword | |\n| PX/PR | PERMX | HMMLTPX | PERMR | HMMLTPR |\n| PXY | PERMXY | HMMLTPXY | | |\n| PY/THT | PERMY | hMMLTPY | PERMTHT | HMMLTTH |\n| PZ | PERMZ | HMMLTPZ | PERMZ | HMMLTPZ |"},"HMMMREGT":{"name":"HMMMREGT","sections":["GRID"],"supported":false,"summary":"The HMMMREGT keyword multiplies the transmissibility between two regions by a constant, for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section. The constant should be a real number. Unlike the MULTREGT keyword in the GRID section, the HMMMREGT keyword modifications are cumulative.","parameters":[],"example":""},"HMMULRGT":{"name":"HMMULRGT","sections":["GRID"],"supported":false,"summary":"HMMULRGT defines the transmissibility between two regions gradient parameters, for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section.","parameters":[],"example":""},"HMMULTFT":{"name":"HMMULTFT","sections":["GRID"],"supported":false,"summary":"HMMULTFT defines the history match fault transmissibility gradient cumulative multipliers to be applied to the fault transmissibilities for faults declared by the FAULT keyword in the GRID section, for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section. The keyword allows for the re-scaling of the existing fault transmissibilities calculated by OPM Flow, or if the MULTFLT keyword has been entered, then HMMULTFT is applied to the existing MULTFLT multipliers.","parameters":[{"index":1,"name":"FAULT","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"TRANS_MULT","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"DIFF_MULT","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"}],"example":"","expected_columns":3,"size_kind":"list"},"HMMULTSG":{"name":"HMMULTSG","sections":["GRID"],"supported":false,"summary":"HMMULTSG defines the history match dual porosity sigma parameter gradient cumulative multipliers applied to the dual porosity sigma value declared by the SIGMAV and SIGMAGDV keywords in the PROPS section, for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section. In addition to the HMDIMS keyword, either the DUALPERM keyword that activates the Dual Permeability option, or the DUALPORO keyword that activates the Dual Porosity option for the run, must be declared in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"HRFIN":{"name":"HRFIN","sections":["GRID"],"supported":false,"summary":"HRFIN116\n Radial grids are not currently implemented in this version of OPM Flow, but is expected to be incorporated in a future release. defines the ratio of grid blocks for the DRV keyword in the r-direction via a vector within a Local Grid Refinement (“LGR”) as opposed to defining the size for each cell for a Radial LGR Grid. The LGR keyword in the RUNSPEC section should be activated to indicate an LGR is being used, and the keyword HRFIN should be placed in between the RADIN (or RAFDIN4) and ENDFIN keywords in the GRID section. The DRV keyword in the GRID section defines the radial grid size in terms of the length, that is feet for field units, this keyword defines the length as the ratio of the previous cell size, staring with the inner radius (INRAD).","parameters":[{"index":1,"name":"HRFIN","description":"HRFIN is a vector of real numbers describing the ratio of cell size for the grid blocks in the r-direction in a radial LGR for the DRV keyword. Repeat counts may be used, for example 2*1.5.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- INNER RADIUS OF FIRST GRID BLOCK IN THE RADIAL DIRECTION\n--\nINRAD 0.25 /\n--\n-- DEFINE GRID BLOCK DRV RATIOS IN THE R DIRECTION\n--\nHRFIN\n1.50 2.00 3.00 5.00 7.00 10.00 /\nThe above example defines the size of the cells in the R direction based on NR equals 7, resulting in NR-1 values on the RADFIN keyword in the GRID section. Note the INRAD keyword to define the inner radius of the radial grid.","size_kind":"array"},"HXFIN":{"name":"HXFIN","sections":["GRID"],"supported":false,"summary":"HXFIN defines the split ratio of grid blocks for the DXV keyword in the x-direction via a vector within a Local Grid Refinement (“LGR”) as opposed to defining the size for each cell for a Cartesian LGR Grid. The LGR keyword in the RUNSPEC section should be activated to indicate an LGR is being used, and the keyword HXFIN should be placed in between the CARFIN and ENDFIN keywords in the GRID section. The DXV keyword in the GRID section defines the grid size in terms of the length, that is feet for field units, this keyword defines the length as the ratio of the coarse cells.","parameters":[{"index":1,"name":"HXFIN","description":"HXFIN is a vector of real numbers describing the ratio of cell size for the grid blocks in the x-direction in a Cartesian LGR grid. Repeat counts may be used, for example 2*2.0.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- CARFIN LGR GRID COMMANDS\n--\n-- LGR ----- HOST GRID ------ -- CARFIN GRID -- MAX HOST\n-- NAME I1 I2 J1 J2 K1 K2 NX NY NZ WELLS NAME\nCARFIN\nLGR-OP01 24 25 86 87 1 50 5 3 50 1 GLOBAL /\n--\n-- DEFINE LGR GRID BLOCK IN THE X-DIRECTION\nNXFIN\n3 2 /\n--\n-- DEFINE GRID BLOCK LGR RATIOS IN THE X-DIRECTION\n--\nHXFIN\n1.00 2.00 3.00 2.00 1.00 /\nENDFIN\nThe above example defines the size of the cells in the x-direction based on NX equals five on the CARFIN keyword in the GRID section.","size_kind":"array"},"HYFIN":{"name":"HYFIN","sections":["GRID"],"supported":false,"summary":"HYFIN defines the split ratio of grid blocks for the DYV keyword in the y-direction via a vector within a Local Grid Refinement (“LGR”) as opposed to defining the size for each cell for a Cartesian LGR Grid. The LGR keyword in the RUNSPEC section should be activated to indicate an LGR is being used, and the keyword HYFIN should be placed in between the CARFIN and ENDFIN keywords in the GRID section. The DYV keyword in the GRID section defines the grid size in terms of the length, that is feet for field units, this keyword defines the length as the ratio of the coarse cells.","parameters":[{"index":1,"name":"HYFIN","description":"HYFIN is a vector of real numbers describing the ratio of cell size for the grid blocks in the y-direction in a Cartesian LGR grid. Repeat counts may be used, for example 2*2.0.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- CARFIN LGR GRID COMMANDS\n--\n-- LGR ----- HOST GRID ------ -- CARFIN GRID -- MAX HOST\n-- NAME I1 I2 J1 J2 K1 K2 NX NY NZ WELLS NAME\nCARFIN\nLGR-OP01 24 25 86 87 1 50 3 5 50 1 GLOBAL /\n--\n-- DEFINE LGR GRID BLOCK IN THE Y-DIRECTION\nNYFIN\n3 2 /\n--\n-- DEFINE GRID BLOCK LGR RATIOS IN THE Y-DIRECTION\n--\nHYFIN\n1.00 2.00 3.00 2.00 1.00 /\nENDFIN\nThe above example defines the size of the cells in the y-direction based on NY equals five on the CARFIN keyword in the GRID section.","size_kind":"array"},"HZFIN":{"name":"HZFIN","sections":["GRID"],"supported":false,"summary":"HZFIN defines the split ratio of grid blocks for the DZV keyword in the z-direction via a vector within a Local Grid Refinement (“LGR”) as opposed to defining the size for each cell for a Cartesian LGR Grid. The LGR keyword in the RUNSPEC section should be activated to indicate an LGR is being used, and the keyword HYFIN should be placed in between the CARFIN and ENDFIN keywords in the GRID section. The DZV keyword in the GRID section defines the grid size in terms of the length, that is feet for field units, this keyword defines the length as the ratio of the coarse cells.","parameters":[{"index":1,"name":"HYZIN","description":"HZFIN is a vector of real numbers describing the ratio of cell size for the grid blocks in the z-direction in a Cartesian LGR grid. Repeat counts may be used, for example 2*2.0.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- CARFIN LGR GRID COMMANDS\n--\n-- LGR ----- HOST GRID ------ -- CARFIN GRID -- MAX HOST\n-- NAME I1 I2 J1 J2 K1 K2 NX NY NZ WELLS NAME\nCARFIN\nLGR-OP01 24 25 86 87 1 50 5 3 100 1 GLOBAL /\n--\n-- DEFINE LGR GRID BLOCK IN THE Z-DIRECTION\nNZFIN\n50*2 /\n--\n-- DEFINE GRID BLOCK LGR RATIOS IN THE Z-DIRECTION\n--\nHZFIN\n50*2.0 /\nENDFIN\nThe above example defines the size of the cells in the z-direction based on NZ equals 100 on the CARFIN keyword in the GRID section.","size_kind":"array"},"IHOST":{"name":"IHOST","sections":["GRID"],"supported":false,"summary":"The IHIST keyword assigns Local Grid Refinements (“LGR”) to a parallel process number, for when the PARALLEL keyword has been invoked in the RUNSPEC section.","parameters":[{"index":1,"name":"LGR","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"PROCESS","description":"","units":{},"default":"0","value_type":"INT"}],"example":"","expected_columns":2,"size_kind":"list"},"IMPORT":{"name":"IMPORT","sections":["GRID","EDIT","PROPS","REGIONS","SOLUTION"],"supported":null,"summary":"The IMPORT keyword informs the simulator to import data from the specified IMPORT file. When the end of the IMPORT file is reached, input data is read from the next keyword in the current file. Normally IMPORT files are generated by grid pre-processing software and the keyword allows for both formatted and unformatted (binary) files to be loaded. The keyword can be used to import any valid grid arrays within a section, for example the EQLNUM array in the REGIONS section","parameters":[{"index":1,"name":"FILENAME","description":"A character string enclosed in quotes that defines a file to be imported and to be processed by OPM Flow.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"FMTOPT","description":"A defined character string that defines the format of the file to be imported and should be set to one of the following: FORMATTED: If the file is formatted as ASCII i.e. a text file, as oppose to a binary file. The option can be abbreviated to just the letter F. UNFORMATTED: If the file is in binary format, note this option can be abbreviated to just the letter U. If the variable FMTOPT is omitted then the default is for binary file input.","units":{},"default":"U","value_type":"STRING"}],"example":"The first example shown below loads the grid file from the same directory as the data file.\n--\n-- LOAD A IMPORT FILE\n--\nIMPORT\n'NOR-OPM-A00-GRID.EGRID' /\nThe next example loads the same file one directory above from where the data file is located.\n--\n-- LOAD A IMPORT FILE\n--\nIMPORT\n'../NOR-OPM-A00-GRID.EGRID' /\nThe final example loads the same file from a separate include subdirectory in the parent directory of the data file.\n--\n-- LOAD A IMPORT FILE\n--\nIMPORT\n'../INCLUDE/NOR-OPM-A00-GRID.EGRID' /","expected_columns":2,"size_kind":"fixed","size_count":1},"INIT":{"name":"INIT","sections":["GRID"],"supported":null,"summary":"This keyword switches on the writing of the INIT file that contains the static data specified in the GRID, PROPS and REGIONS sections. For example, the PORO, PERM and NTG arrays from the GRID section. The data is used in post-processing software, for example OPM ResInsight, to visualize the static grid properties.","parameters":[],"example":"--\n-- ACTIVATE WRITING THE INIT FILE FOR POST-PROCESSING\nINIT\nThe above example switches on the writing of the INIT file for post-processing in ResInsight.","size_kind":"none","size_count":0},"INRAD":{"name":"INRAD","sections":["GRID"],"supported":null,"summary":"INRAD defines the inner radius of the reservoir model for a radial grid geometry. The RADIAL or SPIDER keyword in the RUNSPEC should be activated to indicate that radial geometry is being used.","parameters":[{"index":1,"name":"INRAD","description":"A single real positive number defining the inner radius of a radial grid.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":"Length"}],"example":"--\n-- INNER RADIUS OF FIRST GRID BLOCK IN THE RADIAL DIRECTION\n--\nINRAD\n0.25 /\nThe above example defines the inner radius of a radial grid to be 0.25 feet.","expected_columns":1,"size_kind":"fixed","size_count":1},"IONROCK":{"name":"IONROCK","sections":["GRID"],"supported":false,"summary":"The IONROCK keyword defines the ion exchange capacity for all the cells in the model, for when the brine phase has been activated by the BRINE keyword and the Multi-Component Brine model, that allows for the water phase to have multiple water salinities, has been activated by the ECLMC keyword. Both keywords are in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"ISOLNUM":{"name":"ISOLNUM","sections":["GRID"],"supported":false,"summary":"The ISOLNUM keyword defines areas of the grid that consists of isolated reservoirs where the only form of communication between the reservoirs is via wellbore connections This enables the reservoir flow equations to be solved independently for greater computational efficiency.","parameters":[{"index":1,"name":"ISOLNUM","description":"ISOLNUM defines an array of positive integers assigning a grid cell to a particular isolated reservoir region. The maximum number of ISOLNUM regions is set by the NRFREG variable on the REGDIMS keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"The example below defines three separate independent reservoirs; the first reservoir covers the whole grid and layers 1 to 50, reservoir two cover the whole grid and layers 52 to 150, and finally the third reservoir again covers the whole grid but with layers 152 to 300. The layers 51 and 151 are shale layers made inactive by setting ISOLNUM to zero.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nISOLNUM 1 1* 1* 1* 1* 1 50 / DEFINED RESERVOIR 1\nISOLNUM 0 1* 1* 1* 1* 51 51 / DEFINED A SHALE\nISOLNUM 2 1* 1* 1* 1* 52 150 / DEFINED RESERVOIR 2\nISOLNUM 0 1* 1* 1* 1* 151 151 / DEFINED A SHALE\nISOLNUM 3 1* 1* 1* 1* 152 300 / DEFINED RESERVOIR 3\n/\nNote the above example has no effect as the keyword is ignored by the simulator.","size_kind":"array"},"JFUNC":{"name":"JFUNC","sections":["GRID"],"supported":null,"summary":"The JFUNC keyword activates the Leverett-J-Function117\n Leverett, M. C.; “Capillary Behaviour in Porous Solids”, Trans. AIME (1941) 142, 152-168. option which is a commonly used technique to normalize capillary pressure based on laboratory measured core plugs porosity and permeability values and the resulting capillary pressure data. The keyword performs the calculation based on the parameters on the this keyword combined with a cells porosity and permeability to perform the scaling globally.","parameters":[{"index":1,"name":"JFOPT","description":"A character string that defines which capillary data sets the J-Function option should be applied to, based on the following options: WATER: apply the J-Function option to the water-oil capillary pressure data only. GAS: apply the J-Function option to the gas-oil capillary pressure data only. BOTH: apply the J-Function option to the water-oil and the gas-oil capillary pressure data.","units":{},"default":"BOTH","value_type":"STRING","options":["WATER","GAS","BOTH"]},{"index":2,"name":"OWSTEN","description":"A positive real number that defines oil-water surface tension used to de-normalized J-Function data entered in the PROPS section.","units":{"field":"dynes/cm","metric":"dynes/cm","laboratory":"dynes/cm"},"default":"None","value_type":"DOUBLE","dimension":"SurfaceTension"},{"index":3,"name":"OGSTEN","description":"A positive real number that defines oil-gas surface tension used to de-normalized J-Function data entered in the PROPS section.","units":{"field":"dynes/cm","metric":"dynes/cm","laboratory":"dynes/cm"},"default":"None","value_type":"DOUBLE","dimension":"SurfaceTension"},{"index":4,"name":"ALPHA","description":"A positive real value that defines an alternative power value for the porosity term in the J-Function equation, that is instead of [sqrt{k over %varphi}]use use [{k sup 0.5} over {%varphi sup %alpha}]instead in the transformation.instead in the transformation.","units":{},"default":"0.5","value_type":"DOUBLE"},{"index":5,"name":"BETA","description":"A positive real number that defines an alternative power value for the permeability term in the J-Function equation, that is instead of [sqrt{k over %varphi}]use use [{k sup %beta} over {%varphi sup 0.5}]instead in the transformation.instead in the transformation.","units":{},"default":"0.5","value_type":"DOUBLE"},{"index":6,"name":"PERM","description":"PERM is a character string that sets the permeability array to be used in the transform, based on the following options: X: use the PERMX array. XY: use the average of the PERMX and PERMY arrays. Y: use the PERMY array. Z: use the PERMZ array. U: use the PERMJFUN array","units":{},"default":"XY","value_type":"STRING"}],"example":"--\n-- DEFINE LEVERETT J-FUNCTION PARAMETERS\n-- JFUN OILWAT GASOIL PORO PERM PERM\n-- OPTN SDENS SDEN ALPHA BETA OPTN\nJFUNC\nWATER 22.5 1* 0.5 0.5 XY /\nThe above example results in the oil-water capillary pressure data entered on the SWFN keyword in the PROPS section being treated as J-Functions, and that the J-Function should be de-normalized using an oil-water surface density of 22.5 dynes/cm, using the default power values and the average of the PERMX and PERMY values for each grid block.\n| [J ` ` (S SUB{w})~=~ {P SUB{c,res} (S SUB{w}) ~ {SQRT {k OVER φ} }}\n OVER {σ }] | (6.4) |\n|-----------------------------------------------------------------------------------------------------------|-------|\n| [J ` ` (S SUB{w})~=~ {P SUB{c,res} (S SUB{w}) ~ {SQRT {k OVER φ} }}\n OVER {σ`` cos ` ` Θ}] | (6.5) |\n|----------------------------------------------------------------------------------------------------------------------|-------|\n| [J ` ` (S SUB{w})~=~ {P SUB{c,res} (S SUB{w}) ~ {SQRT {k OVER φ} }}] | (6.6) |\n|-----------------------------------------------------------------------|-------|\n| [J ` ` (S SUB{w})~=~ {P SUB{c,res} (S SUB{w}) ~ left( {k sup %beta} OVER {φ sup %alpha} right) }\n OVER {σ }] | (6.7) |\n|---------------------------------------------------------------------------------------------------------------------------------------|-------|\n| Note If either the JFUNC or JFUNCR keywords are used to activate J-Function scaling then the ENDSCALE keyword in the RUNSPEC section must also be present in the input deck, in order for the dimensionless J-function values entered on the SWFN, SGFN or the SWOF, SGOF, SLGOF keywords to be re-scaled to capillary pressure data. Note if the ENDSCALE keyword is absent, then like the commercial simulator, J-Function scaling is not performed, and the values entered on the SWFN, SGFN or the SWOF, SGOF, SLGOF keywords are used as entered. |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":6,"size_kind":"fixed","size_count":1},"JFUNCR":{"name":"JFUNCR","sections":["GRID"],"supported":false,"summary":"JFUNCR keyword activates Leverett-J-Function119\n Leverett, M. C.; “Capillary Behaviour in Porous Solids”, Trans. AIME (1941) 142, 152-168. Saturation Table option which is a commonly used technique to normalize capillary pressure base on laboratory measured core plugs porosity and permeability values and the resulting capillary pressure data. This keyword is an extension of the JFUNC keyword in the GRID section that uses the parameters on the JFUNC keyword combined with a cell’s porosity and permeability to perform the scaling globally. In comparison, the JFUNCR allows for the J-Function parameters to be declared per saturation table number, resulting in greater flexibility.","parameters":[{"index":1,"name":"JFOPT","description":"A character string that defines which capillary data sets the J-Function option should be applied to, based on the following options: WATER: apply the J-Function option to the water-oil capillary pressure data only. GAS: apply the J-Function option to the gas-oil capillary pressure data only. BOTH: apply the J-Function option to the water-oil and the gas-oil capillary pressure data.","units":{},"default":"BOTH","value_type":"STRING","options":["WATER","GAS","BOTH"]},{"index":2,"name":"OWSTEN","description":"A positive real number that defines oil-water surface tension used to de-normalized J-Function data entered in the PROPS section.","units":{"field":"dynes/cm","metric":"dynes/cm","laboratory":"dynes/cm"},"default":"None","value_type":"DOUBLE"},{"index":3,"name":"OGSTEN","description":"A positive real number that defines oil-gas surface tension used to de-normalized J-Function data entered in the PROPS section.","units":{"field":"dynes/cm","metric":"dynes/cm","laboratory":"dynes/cm"},"default":"None","value_type":"DOUBLE"},{"index":4,"name":"ALPHA","description":"A positive real value that defines an alternative power value for the porosity term in the J-Function equation, that is instead of[sqrt{k over %varphi}] use use [{k sup 0.5} over {%varphi sup %alpha}]instead in the transformation.instead in the transformation.","units":{},"default":"0.5","value_type":"DOUBLE","dimension":"1"},{"index":5,"name":"BETA","description":"A positive real number that defines an alternative power value for the permeability term in the J-Function equation, that is instead of [sqrt{k over %varphi}]use use [{k sup %beta} over {%varphi sup 0.5}]instead in the transformation.instead in the transformation.","units":{},"default":"0.5","value_type":"DOUBLE","dimension":"1"},{"index":6,"name":"PERM","description":"PERM is a character string that sets the permeability array to be used in the transform, based on the following options: X: use the PERMX array. XY: use the average of the PERMX and PERMY arrays. Y: use the PERMY array. Z: use the PERMZ array. U: use the PERMJFUN array","units":{},"default":"XY","value_type":"STRING"}],"example":"The example below assumes NTSFUN is equal to five on the TABDIMS keyword in the RUNSPEC section.\n--\n-- DEFINE LEVERETT J-FUNCTION PARAMETERS BY SATURATION TABLES\n-- JFUN OILWAT GASOIL PORO PERM PERM\n-- OPTN SDENS SDEN ALPHA BETA OPTN\nJFUNCR\nWATER 22.5 1* 0.5 0.5 XY /\nWATER 22.5 1* 0.5 0.5 XY /\nWATER 22.5 1* 0.5 0.5 XY /\nWATER 22.5 1* 0.5 0.5 XY /\nWATER 22.5 1* 0.5 0.5 XY /\nHere the oil-water capillary pressure data entered on the SWFN keyword in the PROPS section are treated as J-Functions, and that the J-Function should be de-normalized using an oil-water surface density of 22.5 dynes/cm, using the default power values and the average of the PERMX and PERMY values for each grid block, for all five tables. Note that since all the JFUNCR parameters are the same for all saturation tables then the JFUNC keyword could be used instead in this instance.\n| [J ` ` (S SUB{w})~=~ {P SUB{c,res} (S SUB{w}) ~ {SQRT {k OVER φ} }}\n OVER {σ }] | (6.8) |\n|-----------------------------------------------------------------------------------------------------------|-------|\n| [J ` ` (S SUB{w})~=~ {P SUB{c,res} (S SUB{w}) ~ {SQRT {k OVER φ} }}\n OVER {σ`` cos ` ` Θ}] | (6.9) |\n|----------------------------------------------------------------------------------------------------------------------|-------|\n| [J ` ` (S SUB{w})~=~ {P SUB{c,res} (S SUB{w}) ~ {SQRT {k OVER φ} }}] | (6.10) |\n|-----------------------------------------------------------------------|--------|\n| [J ` ` (S SUB{w})~=~ {P SUB{c,res} (S SUB{w}) ~ left( {k sup %beta} OVER {φ sup %alpha} right) }\n OVER {σ }] | (6.11) |\n|---------------------------------------------------------------------------------------------------------------------------------------|--------|\n| Note If either the JFUNC or JFUNCR keywords are used to activate J-Function scaling then the ENDSCALE keyword in the RUNSPEC section must also be present in the input deck, in order for the dimensionless J-function values entered on the SWFN, SGFN or the SWOF, SGOF, SLGOF keywords to be re-scaled to capillary pressure data. Note if the ENDSCALE keyword is absent, then like the commercial simulator, J-Function scaling is not performed, and the values entered on the SWFN, SGFN or the SWOF, SGOF, SLGOF keywords are used as entered. |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":6,"size_kind":"fixed"},"LINKPERM":{"name":"LINKPERM","sections":["GRID"],"supported":false,"summary":"The LINKPERM keyword assigns the grid cell permeabilities entered via the PERMX, PERMY and PERMZ keywords to a cell face (I±, J±, or K±) and results in the simulator using these values directly in the calculating the transmissibility between grid blocks. This is different to the conventional way of entering permeability data that consists of entering the cell centered permeability and the simulator calculating a weighted average transmissibility based on the cell centered permeability of the up-stream and down-stream grid blocks.","parameters":[],"example":"","size_kind":"array"},"LTOSIGMA":{"name":"LTOSIGMA","sections":["GRID"],"supported":false,"summary":"The LTOSIGMA keyword defines parameters to calculate the sigma factor in conjunction with the data entered via the LX, LY and LZ keywords in the GRID section, for when the VISCD keyword has been used in the RUNSPEC section to activate the Dual Porosity Viscous Displacement option. In addition, either the DUALPORO or DUALPERM keyword should be entered in the RUNSPEC section to activate the dual porosity or dual permeability models.","parameters":[{"index":1,"name":"FX","description":"","units":{},"default":"4","value_type":"DOUBLE","dimension":"1"},{"index":2,"name":"FY","description":"","units":{},"default":"4","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"FZ","description":"","units":{},"default":"4","value_type":"DOUBLE","dimension":"1"},{"index":4,"name":"FGD","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"1"},{"index":5,"name":"OPTION","description":"","units":{},"default":"XONLY","value_type":"STRING"}],"example":"","expected_columns":5,"size_kind":"fixed","size_count":1},"LX":{"name":"LX","sections":["GRID"],"supported":false,"summary":"The LX keyword defines the size of “representative” matrix grid blocks in the X direction via an array in dual porosity and dual permeability runs, for when the VISCD keyword has been used in the RUNSPEC section to activate the dual porosity viscous displacement option. In addition, either the DUALPORO or DUALPERM keyword should be entered in the RUNSPEC section to activate the dual porosity or dual permeability models. The VISCD option is used to model the viscous displacement of fluids from the matrix by the fracture pressure gradient, for when the fracture system has a more moderate permeability, and flow to and from the matrix caused by the fracture pressure gradient acts as an additional production mechanism.","parameters":[{"index":1,"name":"LX","description":"LX is an array of real numbers describing the “representative” cell size in the X direction for each cell in the model. Repeat counts may be used, for example 10*100.0.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"0"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n10 10 1 6 1 1 / DEFINE BOX AREA\n--\n-- DEFINE DUAL POROSITY VISCOUS DISPLACEMENT X DIRECTION MATRIX SIZE\n--\nLX\n6*10.0 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe above example defines a subset of the grid and the size of the “representative” matrix cells in the X direction to 10.0 ft.; after which the ENDBOX keyword resets the input to be the full grid.","size_kind":"array"},"LXFIN":{"name":"LXFIN","sections":["GRID"],"supported":false,"summary":"The LXFIN keyword defines the parameters for automatically generating a Local Grid Refinement (“LGR”) grid in the X direction based on logarithmic block spacing, for when the LGR option has been activated by the LGR keyword in the RUNSPEC section. LXFIN should be placed in between the CARFIN and ENDFIN keywords in the GRID section.","parameters":[{"index":1,"name":"CELL_THICKNESS","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":2,"name":"SIZE_OPTION","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":2,"size_kind":"fixed","size_count":1},"LY":{"name":"LY","sections":["GRID"],"supported":false,"summary":"The LY keyword defines the size of “representative” matrix grid blocks in the Y direction via an array in dual porosity and dual permeability runs, for when the VISCD keyword has been used in the RUNSPEC section to activate the dual porosity viscous displacement option. In addition, either the DUALPORO or DUALPERM keyword should be entered in the RUNSPEC section to activate the dual porosity or dual permeability models. The VISCD option is used to model the viscous displacement of fluids from the matrix by the fracture pressure gradient, for when the fracture system has a more moderate permeability, and flow to and from the matrix caused by the fracture pressure gradient acts as an additional production mechanism.","parameters":[{"index":1,"name":"LY","description":"LY is an array of real numbers describing the “representative” cell size in the Y direction for each cell in the model. Repeat counts may be used, for example 10*100.0.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"0"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n10 10 1 6 1 1 / DEFINE BOX AREA\n--\n-- DEFINE DUAL POROSITY VISCOUS DISPLACEMENT Y DIRECTION MATRIX SIZE\n--\nLY\n6*15.0 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe above example defines a subset of the grid and the size of the “representative” matrix cells in the Y direction to 15.0 ft.; after which the ENDBOX keyword resets the input to be the full grid.","size_kind":"array"},"LYFIN":{"name":"LYFIN","sections":["GRID"],"supported":false,"summary":"The LYFIN keyword defines the parameters for automatically generating a Local Grid Refinement (“LGR”) grid in the Y direction based on logarithmic block spacing, for when the LGR option has been activated by the LGR keyword in the RUNSPEC section. LYFIN should be placed in between the CARFIN and ENDFIN keywords in the GRID section.","parameters":[{"index":1,"name":"CELL_THICKNESS","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":2,"name":"SIZE_OPTION","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":2,"size_kind":"fixed","size_count":1},"LZ":{"name":"LZ","sections":["GRID"],"supported":false,"summary":"The LZ keyword defines the size of “representative” matrix grid blocks in the Z direction via an array in dual porosity and dual permeability runs, for when the VISCD keyword has been used in the RUNSPEC section to activate the dual porosity viscous displacement option. In addition, either the DUALPORO or DUALPERM keyword should be entered in the RUNSPEC section to activate the dual porosity or dual permeability models. The VISCD option is used to model the viscous displacement of fluids from the matrix by the fracture pressure gradient, for when the fracture system has a more moderate permeability, and flow to and from the matrix caused by the fracture pressure gradient acts as an additional production mechanism.","parameters":[{"index":1,"name":"LZ","description":"LZ is an array of real numbers describing the “representative” cell size in the Z direction for each cell in the model. Repeat counts may be used, for example 10*100.0.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"0"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n10 10 1 6 1 1 / DEFINE BOX AREA\n--\n-- DEFINE DUAL POROSITY VISCOUS DISPLACEMENT Z DIRECTION MATRIX SIZE\n--\nLZ\n6*3.0 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe example defines a subset of the grid and the size of the “representative” matrix cells in the Y direction to 15.0 ft.; after which the ENDBOX keyword resets the input to be the full grid.","size_kind":"array"},"LZFIN":{"name":"LZFIN","sections":["GRID"],"supported":false,"summary":"The LZFIN keyword defines the parameters for automatically generating a Local Grid Refinement (“LGR”) grid in the Z direction based on logarithmic block spacing, for when the LGR option has been activated by the LGR keyword in the RUNSPEC section. LZFIN should be placed in between the CARFIN and ENDFIN keywords in the GRID section.","parameters":[{"index":1,"name":"CELL_THICKNESS","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":2,"name":"SIZE_OPTION","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":2,"size_kind":"fixed","size_count":1},"MAPAXES":{"name":"MAPAXES","sections":["GRID"],"supported":null,"summary":"MAPAXES specifies the origin of the map used to create the grid. It is usually output by pre-processing software when exporting the grid geometry. The data is not used by OPM Flow intrinsically, but is merely written to the output EGRID file, as specified by the GRIDFILE keyword, for the use of post-processing software like OPM ResInsight.","parameters":[{"index":1,"name":"X1","description":"X1 is a real number that defines the x co-ordinate of a point on the y-axis.","units":{},"default":"None"},{"index":2,"name":"Y1","description":"Y1 is a real number that defines the y co-ordinate of a point on the y-axis.","units":{},"default":"None"},{"index":3,"name":"X2","description":"X2 is a real number that defines the x co-ordinate of the origin.","units":{},"default":"None"},{"index":4,"name":"Y2","description":"Y2 is a real number that defines the y co-ordinate of the origin.","units":{},"default":"None"},{"index":5,"name":"X3","description":"X3 is a real number that defines the x co-ordinate of a point on the x-axis.","units":{},"default":"None"},{"index":6,"name":"Y3","description":"Y3 is a real number that defines the y co-ordinate of a point on the x-axis.","units":{},"default":"None"}],"example":"--\n-- ---------------- MAPAXES -----------------\n-- X1 Y1 X2 Y2 X3 Y3\nMAPAXES\n0.0 100.0 0.0 0.0 100.0 0.0 /\nThe above example defines the map axes to be exported to the grid file for use by post-processing software."},"MAPUNITS":{"name":"MAPUNITS","sections":["GRID"],"supported":false,"summary":"The MAPUNITS keyword defines the units of the coordinates stated on the MAPAXES keyword. It is usually output by pre-processing software when exporting the grid geometry. The data is not used by OPM Flow intrinsically, but is merely written to the output EGRID file, as specified by the GRIDFILE keyword, for the use of post-processing software like OPM ResInsight.","parameters":[{"index":1,"name":"MAPUNITS","description":"A character string that defines the units of the coordinates stated on the MAPAXES keyword, and should be set to: FEET for field units METRES for metric units, or CM for laboratory units","units":{},"default":"METRES","value_type":"STRING"}],"example":"--\n-- SET THE MAP UNITS FOR THE MAPAXES KEYWORD\nMAPUNITS\nMETRES /\nThe above example specifies the units on the MAPAXES to be the default METRES.","expected_columns":1,"size_kind":"fixed","size_count":1},"MAXVALUE":{"name":"MAXVALUE","sections":["GRID","EDIT","PROPS"],"supported":false,"summary":"The MAXVALUE keyword sets a maximum value for the specified array or part of an array. The constant can be an integer or real value depending on the array type; however, the arrays that can be operated on are dependent on which section the MAXVALUE keyword is being applied in.","parameters":[{"index":1,"name":"ARRAY","description":"A character string of up to eight characters in length that defines the keyword identifying the array to be modified.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"CONSTANT","description":"CONSTANT is a positive integer or positive real value that an ARRAY element will be reset to if an element in the defined input BOX, as defined by items (3) to (8), is greater than CONSTANT. CONSTANT has in the same units as the ARRAY property.","units":{},"default":"None","value_type":"DOUBLE"},{"index":3,"name":"I1","description":"The lower bound of the array in the I-direction to be modified must be greater than or equal to one and less than or equal to I2 and NX.","units":{},"default":"1","value_type":"INT"},{"index":4,"name":"I2","description":"The upper bound of the array in the I-direction to be modified must be greater than or equal to I1 and less than or equal to NX","units":{},"default":"NX","value_type":"INT"},{"index":5,"name":"J1","description":"The lower bound of the array in the J-direction to be modified must be greater than or equal to one and less than or equal to J2 and NY.","units":{},"default":"1","value_type":"INT"},{"index":6,"name":"J2","description":"The upper bound of the array in the J-direction to be modified must be greater than or equal to J1 and less than or equal to NY.","units":{},"default":"NY","value_type":"INT"},{"index":7,"name":"K1","description":"The lower bound of the array in the K-direction to be modified must be greater than or equal to one and less than or equal to K2 and NZ.","units":{},"default":"1","value_type":"INT"},{"index":8,"name":"K2","description":"The upper bound of the array in the K-direction to be modified must be greater than or equal to K1 and less than or equal to NZ.","units":{},"default":"NZ","value_type":"INT"}],"example":"--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nMAXVALUE\nPERMX 1.0E2 1* 1* 1* 1* 1* 1* / MAX VALUE FOR PERMX\nPERMY 1.0E2 1* 1* 1* 1* 1* 1* / MAX VALUE FOR PERMY\nPERMZ 1.0E1 1* 1* 1* 1* 1* 1* / MAX VALUE FOR PERMZ\n/\nThe above example resets the maximum values for the PERMX, PERMY and PERMZ, arrays to 100.0, 100.0 and 10.0, respectively, for all cells.\n| MAXVALUE Keyword and Variable Options by Section | | | | | | |\n|--------------------------------------------------|---------|-------|---------|----------|---------|----------|\n| GRID | EDIT | PROPS | REGIONS | SOLUTION | SUMMARY | SCHEDULE |\n| DX | DEPTH | SWL | | | | |\n| DY | PORV | SWCR | | | | |\n| DZ | TRANX | SWU | | | | |\n| PERMX | TRANY | SGL | | | | |\n| PERMY | TRANZ | SGCR | | | | |\n| PERMZ | DIFFX | SGU | | | | |\n| MULTX | DIFFY | KRW | | | | |\n| MULTY | DIFFZ | KRO | | | | |\n| MULTZ | TRANR | KRG | | | | |\n| DR | TRANTHT | PCG | | | | |\n| DTHETA | DIFFR | PCW | | | | |\n| PERMR | DIFFTHT | | | | | |\n| PERMTHT | | | | | | |\n| DZNET | | | | | | |\n| PORO | | | | | | |\n| NTG | | | | | | |\n| FLUXNUM | | | | | | |\n| MULTNUM | | | | | | |\n| MPFANUM | | | | | | |\n| DIFFX | | | | | | |\n| DIFFY | | | | | | |\n| DIFFZ | | | | | | |\n| DIFFR | | | | | | |\n| DIFFTHT | | | | | | |","expected_columns":8,"size_kind":"list"},"MINNNCT":{"name":"MINNNCT","sections":["GRID"],"supported":false,"summary":"The MINNNCT keyword defines a minimum non-neighbor connection transmissibility below which the non-neighbor connection is deleted. The keyword allows for three minimum values, one for the transmissibility, one for the diffusivity and one for the thermal transmissibility. If the keyword is absent from the input deck then no minimum cut-off is applied.","parameters":[{"index":1,"name":"CUTOFF_TRANSMISSIBILITY","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Transmissibility"},{"index":2,"name":"DIFFUSIVITY","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Length"},{"index":3,"name":"CUTOFF_THERMAL_TRANSMISSIBILITY","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Energy/AbsoluteTemperature*Time"}],"example":"","expected_columns":3,"size_kind":"fixed","size_count":1},"MINPORV":{"name":"MINPORV","sections":["GRID"],"supported":null,"summary":"MINPORV defines a minimum threshold pore volume that makes all grid blocks whose pore volume is below this value inactive in the model (inactive cells are not used in OPM Flow calculations). Note this keyword is different to the MINPVV keyword in the GRID section, that sets a minimum threshold pore volume for individual cells in the model.","parameters":[{"index":1,"name":"MINPORV","description":"MINPORV is a real positive number that defines the minimum pore volume for a cell to be active in the model.","units":{"field":"rb 1.0e-6","metric":"rm3 1.0e-6","laboratory":"rcc 1.0e-6"},"default":"Defined","value_type":"DOUBLE","dimension":"ReservoirVolume"}],"example":"--\n-- MINIMUM PORE VOLUME FOR ACTIVE CELLS\n--\nMINPORV\n500.0 /\nThe above example defines 500 rb (or m3) as the minimum pore volume for a cell to be active in the model.","expected_columns":1,"size_kind":"fixed","size_count":1},"MINPV":{"name":"MINPV","sections":["GRID"],"supported":null,"summary":"MINPV defines a minimum threshold pore volume that makes all grid blocks whose pore volume is below this value inactive in the model (inactive cells are not used in OPM Flow calculations). Note this keyword is different to the MINPVV keyword in the GRID section, that sets a minimum threshold pore volume for individual cells in the model.","parameters":[{"index":1,"name":"MINPV","description":"MINPV is a real positive number that defines the minimum pore volume for a cell to be active in the model.","units":{"field":"rb 1.0e-6","metric":"rm3 1.0e-6","laboratory":"rcc 1.0e-6"},"default":"Defined","value_type":"DOUBLE","dimension":"ReservoirVolume"}],"example":"--\n-- MINIMUM PORE VOLUME FOR ACTIVE CELLS\n--\nMINPV\n500.0 /\nThe above example defines 500 rb (or m3) as the minimum pore volume for a cell to be active in the model.","expected_columns":1,"size_kind":"fixed","size_count":1},"MINPVV":{"name":"MINPVV","sections":["GRID"],"supported":null,"summary":"MINPVV is an array that defines the minimum threshold pore volume for each cell, that makes grid blocks whose pore volume is below this value inactive in the model (inactive cells are not used in OPM Flow calculations).","parameters":[{"index":1,"name":"MINPVV","description":"MINPVV is an array of real positive numbers that defines the minimum pore volumes for each cell in the model in order for the cells to be active.","units":{"field":"rb 1.0e-6","metric":"rm3 1.0e-6","laboratory":"rcc 1.0e-6"},"default":"Defined"}],"example":"The example below shows how to define 500 rb (or m3) as the minimum pore volume for all cells in layer 19 to be active in the model, and 750 rb (or m3) as the minimum pore volume for all cells in layer 20, by using the BOX keyword to set the portion of the grid of interest.\n--\n-- DEFINE A BOX GRID FOR THE BOTTOM TWO LAYERS OF A 100 X 100 X 20 MODEL\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1* 1* 1* 1* 19 20 / SELECT THE BOTTOM LAYERS\n--\n-- MINIMUM PORE VOLUME FOR INDIVIDUAL CELLS TO BE ACTIVE\n--\nMINPVV\n10000*500.0 10000*750.0 /\n--\n-- RESET THE INPUT BOX TO BE THE FULL MODEL\n--\nENDBOX\nAlthough this will work in the commercial simulators, it does not currently work in OPM Flow, that is one cannot use the MINPVV keyword in conjunction with the BOX keyword, as shown in the aforementioned example.\nInstead one can use:\n--\n-- MINIMUM PORE VOLUME FOR INDIVIDUAL CELLS TO BE ACTIVE\n--\nMINPVV\n10000* 10000* 10000* 10000* 10000*\n10000* 10000* 10000* 10000* 10000*\n10000* 10000* 10000* 10000* 10000*\n10000* 10000* 10000*\n10000*500.0 10000*750.0 /\nTo accomplish the same thing, where the 10000* instructs the simulator to use the default value of 1.0 x 10-6 for 10,000 cells, which in this case is one layer.","size_kind":"array"},"MINVALUE":{"name":"MINVALUE","sections":["GRID","EDIT","PROPS"],"supported":false,"summary":"The MINVALUE keyword sets a minimum value for the specified array or part of an array. The constant can be an integer or real value depending on the array type; however, the arrays that can be operated on are dependent on which section the MINVALUE keyword is being applied in.","parameters":[{"index":1,"name":"ARRAY","description":"A character string of up to eight characters in length that defines the keyword identifying the array to be modified.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"CONSTANT","description":"CONSTANT is a positive integer or positive real value that an ARRAY element will be reset to if an element in the defined input BOX, as defined by items (3) to (8), is less than CONSTANT. CONSTANT has in the same units as the ARRAY property.","units":{},"default":"None","value_type":"DOUBLE"},{"index":3,"name":"I1","description":"A positive integer that defines the lower bound of the array in the I-direction to be modified must be greater than or equal to one and less than or equal to I2 and NX.","units":{},"default":"1","value_type":"INT"},{"index":4,"name":"I2","description":"A positive integer that defines the upper bound of the array in the I-direction to be modified must be greater than or equal to I1 and less than or equal to NX","units":{},"default":"NX","value_type":"INT"},{"index":5,"name":"J1","description":"A positive integer that defines the lower bound of the array in the J-direction to be modified must be greater than or equal to one and less than or equal to J2 and NY.","units":{},"default":"1","value_type":"INT"},{"index":6,"name":"J2","description":"A positive integer that defines the upper bound of the array in the J-direction to be modified must be greater than or equal to J1 and less than or equal to NY.","units":{},"default":"NY","value_type":"INT"},{"index":7,"name":"K1","description":"A positive integer that defines the lower bound of the array in the K-direction to be modified must be greater than or equal to one and less than or equal to K2 and NZ.","units":{},"default":"1","value_type":"INT"},{"index":8,"name":"K2","description":"A positive integer that defines the upper bound of the array in the K-direction to be modified must be greater than or equal to K1 and less than or equal to NZ.","units":{},"default":"NZ","value_type":"INT"}],"example":"--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nMINVALUE\nPERMX 1.0E0 1* 1* 1* 1* 1* 1* / MINIMUM PERMX\nPERMY 1.0E0 1* 1* 1* 1* 1* 1* / MINIMUM PERMY\nPERMZ 1.0E-1 1* 1* 1* 1* 1* 1* / MINIMUM PERMZ\n/\nThe above example resets the minimum values for the PERMX, PERMY and PERMZ, arrays to 1.0, 1.0 and 0.1, respectively, for all cells.\n| EQUALS Keyword and Variable Options by Section | | | | | | |\n|------------------------------------------------|---------|-------|---------|----------|---------|----------|\n| GRID | EDIT | PROPS | REGIONS | SOLUTION | SUMMARY | SCHEDULE |\n| DX | DEPTH | SWL | | | | |\n| DY | PORV | SWCR | | | | |\n| DZ | TRANX | SWU | | | | |\n| PERMX | TRANY | SGL | | | | |\n| PERMY | TRANZ | SGCR | | | | |\n| PERMZ | DIFFX | SGU | | | | |\n| MULTX | DIFFY | KRW | | | | |\n| MULTY | DIFFZ | KRO | | | | |\n| MULTZ | TRANR | KRG | | | | |\n| DR | TRANTHT | PCG | | | | |\n| DTHETA | DIFFR | PCW | | | | |\n| PERMR | DIFFTHT | | | | | |\n| PERMTHT | | | | | | |\n| DZNET | | | | | | |\n| PORO | | | | | | |\n| NTG | | | | | | |\n| FLUXNUM | | | | | | |\n| MULTNUM | | | | | | |\n| MPFANUM | | | | | | |\n| DIFFX | | | | | | |\n| DIFFY | | | | | | |\n| DIFFZ | | | | | | |\n| DIFFR | | | | | | |\n| DIFFTHT | | | | | | |","expected_columns":8,"size_kind":"list"},"MPFANUM":{"name":"MPFANUM","sections":["GRID"],"supported":false,"summary":"The MPFANUM keyword defines regions in the model where the multi-point flux discretization should be applied.","parameters":[],"example":"","size_kind":"array"},"MPFNNC":{"name":"MPFNNC","sections":["GRID"],"supported":false,"summary":"The MPFNNC keyword defines multi-point flux non-neighbor connections explicitly.","parameters":[],"example":"","size_kind":"none","size_count":0},"MULTFLT":{"name":"MULTFLT","sections":["GRID","EDIT","SCHEDULE"],"supported":null,"summary":"MULTFLT enables the transmissibilities across defined faults, as declared by the FAULTS keyword, to be modified. They keyword allows for the re-scaling of the existing fault transmissibilities calculated by OPM Flow, for example setting a fault to be completely sealing by setting the multiplier to zero.","parameters":[{"index":1,"name":"FLTNAME","description":"FLTNAME is a character string enclosed in quotes with a maximum length of eight characters, that defines the name of the fault that FLTMULT will be applied to. FLTNAME must have previously been defined using the FAULTS keyword in GRID section","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"FLT-TRS","description":"A positive real number that sets the transmissible multiplier to be applied to the FLTNAME transmissibilities positive real number that sets the transmissible multiplier to be applied to the FLTNAME transmissibilities.","units":{},"default":"1.0","value_type":"DOUBLE"},{"index":3,"name":"FLT-DIF","description":"A positive real number that sets the diffusivity multiplier to be applied to the FLTNAME diffusivities. This option should only be used if the Diffusion option has been made activate by the DIFFUSE keyword in the RUNSPEC section. OPM Flow does not support this Diffusion option.","units":{},"default":"1.0"}],"example":"--\n-- MODIFY THE TRANSMISSIBILITES ACROSS DEFINED FAULTS\n--\n-- FAULT TRANS DIFUSS\n-- NAME MULTIPLIER MULTIPLIER\nMULTFLT\n'FAULT01' 0.0 / FAULT MULTIPLIERS\n'FAULT02' 0.0 / FAULT MULTIPLIERS\n'FAULT03' 0.0 / FAULT MULTIPLIERS\n/\nThe above example sets the fault transmissibility multiplier for defined faults named FAULT01, FAULT02, and FAULT03 to zero making the faults sealing in the model.","expected_columns":2,"size_kind":"list"},"MULTIPLY":{"name":"MULTIPLY","sections":["GRID","EDIT","PROPS","REGIONS","SOLUTION"],"supported":false,"summary":"The MULTIPLY keyword multiplies a specified array or part of an array by a constant. The constant can be an integer or real value depending on the array type; however, the arrays that can be operated on are dependent on which section the MULTIPLY keyword is being applied in.","parameters":[{"index":1,"name":"ARRAY","description":"A character string of up to eight characters in length that defines the keyword identifying the property to be modified.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"CONSTANT","description":"An integer or real value to multiply the ARRAY by in the same units as the ARRAY property.","units":{},"default":"None","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"I1","description":"A positive integer that defines the lower bound of the array in the I-direction to be modified must be greater than or equal to one and less than or equal to I2 and NX.","units":{},"default":"1","value_type":"INT"},{"index":4,"name":"I2","description":"A positive integer that defines the upper bound of the array in the I-direction to be modified must be greater than or equal to II and less than or equal to NX","units":{},"default":"NX","value_type":"INT"},{"index":5,"name":"J1","description":"A positive integer that defines the lower bound of the array in the J-direction to be modified must be greater than or equal to one and less than or equal to J2 and NY.","units":{},"default":"1","value_type":"INT"},{"index":6,"name":"J2","description":"A positive integer that defines the upper bound of the array in the J-direction to be modified must be greater than or equal to JI and less than or equal to NY.","units":{},"default":"NY","value_type":"INT"},{"index":7,"name":"K1","description":"A positive integer that defines the lower bound of the array in the K-direction to be modified must be greater than or equal to one and less than or equal to K2 and NZ.","units":{},"default":"1","value_type":"INT"},{"index":8,"name":"K2","description":"A positive integer that defines the upper bound of the array in the K-direction to be modified must be greater than or equal to KI and less than or equal to NZ.","units":{},"default":"NZ","value_type":"INT"}],"example":"--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nMULTIPLY\nPERMZ 0.50000 1* 1* 1* 1* 1* 1* / PERMZ * 0.5\n/\nThe above example multiples the PERMZ property array by 0.5 throughout the model.\n| MULTIPLY Keyword and Variable Options by Section | | | | | | |\n|--------------------------------------------------|---------|-------|---------|----------|---------|----------|\n| GRID | EDIT | PROPS | REGIONS | SOLUTION | SUMMARY | SCHEDULE |\n| DX | DEPTH | SWL | ENDNUM | PRESSURE | | |\n| DY | PORV | SWCR | EQLNUM | SWAT | | |\n| DZ | TRANX | SWU | FIPNUM | SGAS | | |\n| PERMX | TRANY | SGL | IMBNUM | RV | | |\n| PERMY | TRANZ | SGCR | MISCNUM | RS | | |\n| PERMZ | DIFFX | SGU | PVTNUM | TBLK | | |\n| MULTX | DIFFY | KRW | ROCKNUM | GI | | |\n| MULTY | DIFFZ | KRO | SATNUM | OILAPI | | |\n| MULTZ | TRANR | KRG | WH2NUM | SALT | | |\n| DR | TRANTHT | PCG | | GASCONC | | |\n| DTHETA | DIFFR | PCW | | SOLVCONC | | |\n| PERMR | DIFFTHT | | | SOLVFRAC | | |\n| PERMTHT | | | | SFOAM | | |\n| DZNET | | | | SPOLY | | |\n| PORO | | | | | | |\n| NTG | | | | | | |\n| FLUXNUM | | | | | | |\n| MULTNUM | | | | | | |\n| MPFANUM | | | | | | |\n| DIFFX | | | | | | |\n| DIFFY | | | | | | |\n| DIFFZ | | | | | | |\n| DIFFR | | | | | | |\n| DIFFTHT | | | | | | |","expected_columns":8,"size_kind":"list"},"MULTIREG":{"name":"MULTIREG","sections":["GRID","EDIT","PROPS","REGIONS","SOLUTION"],"supported":false,"summary":"The MULTIREG keyword multiplies an array or part of an array by a constant for cells with a specific region number. The region number array can be FLUXNUM, MULTNUM or OPERNUM and these arrays must be defined and be available before the MULTIREG keyword is read by the simulator. The constant can be an integer or real value depending on the array type; however, the arrays that can be operated on are dependent on which section the MULTIREG keyword is being applied in.","parameters":[{"index":1,"name":"ARRAY","description":"A character string of up to eight characters in length that defines the keyword identifying the array to be modified.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"CONSTANT","description":"An integer or real value to multiply the ARRAY by in the same units as the ARRAY property for a given REGION.","units":{},"default":"0","value_type":"DOUBLE"},{"index":3,"name":"REGION NUMBER","description":"REGION NUMBER is a positive integer representing the region for which the CONSTANT in (2) should be applied.","units":{},"default":"None","value_type":"INT"},{"index":4,"name":"REGION ARRAY","description":"The REGION ARRAY to use for applying the CONSTANT in (2) based on the REGION NUMBER in (3). REGION ARRAY can have the following values: F for the FLUXNUM array M for the MULTNUM array O for the OPERNUM array","units":{},"default":"M","value_type":"STRING"}],"example":"--\n-- FIRST DEFINE THE PROPERTY ARRAYS AND MULTNUM ARRAYS FOR 10 X 10 X 20 MODEL\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nPORO 0.2000 1* 1* 1* 1* 1* 1* / PORO TO 0.20 IN MODEL\nPERMX 100.00 1* 1* 1* 1* 1* 1* / PERMX TO 0.10 IN MODEL\nMULTNUM 1 1* 1* 1* 1* 1* 1* / MULTNUM IN MODEL\nMULTNUM 2 1* 5 1 5 6 6 / MULTNUM IN MODEL\nMULTNUM 3 1* 1* 1* 1* 10 10 / MULTNUM IN MODEL\n/\n--\n-- NOW RESET PORO AND PERMX BASED ON THE MULTNUM REGION NUMBER\n--\n-- MULTIPLY AN ARRAY BY A CONSTANT BASED ON A REGION NUMBER\n--\n-- ARRAY CONSTANT REGION REGION ARRAY\n-- VALUE NUMBER M / F / O\nMULTIREG\nPORO 1.050 1 M /\nPORO 1.100 2 M /\nPORO 0.950 3 M /\nPERMX 1.25 1 M /\nPERMX 1.30 2 M /\nPERMX 0.90 3 M /\n/\nThe example first defines the PORO and PERMX property arrays for the model and then sets the MULTNUM array to 1 for all cells in the model, after which selected areas of model are assigned various MULTNUM integer values. The MULTIREG can then be invoked to multiply the PORO and PERMX arrays by a constant for the various MULTNUM regions.\n| MULTREG Keyword and Variable Options by Section | | | | | | |\n|-------------------------------------------------|---------|-------|---------|----------|---------|----------|\n| GRID | EDIT | PROPS | REGIONS | SOLUTION | SUMMARY | SCHEDULE |\n| DX | DEPTH | SWL | ENDNUM | PRESSURE | | |\n| DY | PORV | SWCR | EQLNUM | SWAT | | |\n| DZ | TRANX | SWU | FIPNUM | SGAS | | |\n| PERMX | TRANY | SGL | IMBNUM | RV | | |\n| PERMY | TRANZ | SGCR | MISCNUM | RS | | |\n| PERMZ | DIFFX | SGU | PVTNUM | TBLK | | |\n| MULTX | DIFFY | KRW | ROCKNUM | GI | | |\n| MULTY | DIFFZ | KRO | SATNUM | OILAPI | | |\n| MULTZ | TRANR | KRG | WH2NUM | SALT | | |\n| DR | TRANTHT | PCG | | GASCONC | | |\n| DTHETA | DIFFR | PCW | | SOLVCONC | | |\n| PERMR | DIFFTHT | | | SOLVFRAC | | |\n| PERMTHT | | | | SFOAM | | |\n| DZNET | | | | SPOLY | | |\n| PORO | | | | | | |\n| NTG | | | | | | |\n| FLUXNUM | | | | | | |\n| MULTNUM | | | | | | |\n| MPFANUM | | | | | | |\n| DIFFX | | | | | | |\n| DIFFY | | | | | | |\n| DIFFZ | | | | | | |\n| DIFFR | | | | | | |\n| DIFFTHT ","expected_columns":4,"size_kind":"list"},"MULTNUM":{"name":"MULTNUM","sections":["GRID"],"supported":null,"summary":"The MULTNUM keyword defines the inter-region transmissibility region numbers for each grid block, as such there must be one entry for each cell in the model. The array can be used with the EQUALREG, ADDREG, COPYREG, MULTIREG, MULTREGP and MULTREGT keywords in calculating various grid properties in the GRID section.","parameters":[{"index":1,"name":"MULTNUM","description":"MULTNUM defines an array of positive integers assigning a grid cell to a particular inter-region transmissibility region. The maximum number of MULTNUM regions is set by the NRMULT variable on the GRIDOPTS keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"The example below sets three MULTNUM regions for a 4 x 5 x 2 model.\n--\n-- DEFINE MULTNUM REGIONS FOR ALL CELLS\n--\nMULTNUM\n2 2 1 1 2 2 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n3 3 1 1 3 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n/\nAlternatively the EQUALS keyword could be employed to accomplish the same task, that is:\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nMULTNUM 1 1* 1* 1* 1* 1* 1* / SET REGION 1\nMULTNUM 2 1 2 1 2 1 1 / SET REGION 2\nMULTNUM 3 1 2 1 2 2 2 / SET REGION 3\n/\nOne can then increase PERMX by 25% in region three only.\n--\n-- MULTIPLY AN ARRAY BY A CONSTANT BASED ON A REGION NUMBER\n--\n-- ARRAY CONSTANT REGION REGION ARRAY\n-- VALUE NUMBER M / F / O\nMULTIREG\nPERMX 1.25 3 M /\n/","size_kind":"array"},"MULTPV":{"name":"MULTPV","sections":["GRID","EDIT"],"supported":null,"summary":"MULTPV multiples the pore volumes of a cell by a real positive constant for all the cells in the model via an array. An alternative to defining the complete array is to use the BOX keyword to define an area of the grid and then use the MULTPV keyword to set the multipliers just for the area defined by the BOX keyword (see the example).","parameters":[{"index":1,"name":"MULTPV","description":"MULTPV is an array of real positive numbers assigning the pore volume multipliers for each cell in the model. Repeat counts may be used, for example 20*100.0.","units":{},"default":"1.0"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n10 10 1 6 1 3 / DEFINE BOX AREA\n--\n-- SET PORE VOLUME MULTIPLIERS\n--\nMULTPV\n18*0.0500 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe above example defines a 0.05 scaling multiplier for the 18 cells defined by the preceding BOX statement. The ENDBOX keyword resets the input box to the full grid.","size_kind":"array"},"MULTR-":{"name":"MULTR-","sections":["GRID","EDIT","SCHEDULE"],"supported":null,"summary":"MULTR- multiples the transmissibility between two cell faces in the -R direction for all the cells in the model via an array, that is the keyword sets the transmissibility multiplier of block (I, J, K) between the cells (I-1, J, K) and (I, J, K). An alternative to defining the complete array is to use the BOX keyword to define an area of the grid and then use the MULTR- keyword to set the multipliers just for the area defined by the BOX keyword (see the example).","parameters":[{"index":1,"name":"MULTR-","description":"MULTR- is an array of real positive numbers assigning the transmissibility multipliers in the -R direction to each cell face in the model. Repeat counts may be used, for example 20*100.0.","units":{},"default":"1.0"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n10 10 1 6 1 1 / DEFINE BOX AREA\n--\n-- SET MULTR- TRANSMISSIBILITY MULTIPLIERS\n--\nMULTR-\n6*0.500 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe above example defines a 0.5 scaling multiplier for the six cells defined by the preceding BOX statement. The ENDBOX keyword resets the input box to the full grid."},"MULTR":{"name":"MULTR","sections":["GRID","EDIT","SCHEDULE"],"supported":null,"summary":"MULTR multiples the transmissibility between two cell faces in the +R direction for all the cells in the model via an array, that is the keyword sets the transmissibility multiplier of block (I, J, K) between the cells (I, J, K) and (I+I, J, K). An alternative to defining the complete array is to use the BOX keyword to define an area of the grid and then use the MULTR keyword to set the multipliers just for the area defined by the BOX keyword (see the example).","parameters":[{"index":1,"name":"MULTR+","description":"MULTR+ is an array of real positive numbers assigning the transmissibility multipliers in the +R direction to each cell face in the model. Repeat counts may be used, for example 20*100.0.","units":{},"default":"1.0"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n10 10 1 6 1 3 / DEFINE BOX AREA\n--\n-- SET MULTR+ TRANSMISSIBILITY MULTIPLIERS\n--\nMULTR\n18*0.300 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe above example defines a 0.3 scaling multiplier for the 18 cells defined by the preceding BOX statement. The ENDBOX keyword resets the input box to the full grid."},"MULTREGD":{"name":"MULTREGD","sections":["GRID","EDIT"],"supported":false,"summary":"The MULTREGD keyword multiplies the diffusivity between two regions by a constant. The region number array can be FLUXNUM, MULTNUM or OPERNUM and these arrays must be defined and be available before the MULTREGD keyword is read by the simulator. The constant should be a real number.","parameters":[{"index":1,"name":"REGION1","description":"A positive integer value that defines the from REGION number for which the CONSTANT in (3) should be applied.","units":{},"default":"None","value_type":"INT"},{"index":2,"name":"REGION2","description":"A positive integer value that defines the to REGION number for which the CONSTANT in (3) should be applied.","units":{},"default":"None","value_type":"INT"},{"index":3,"name":"CONSTANT","description":"A real value to multiply the diffusivity between REGION1 and REGION2.","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"},{"index":4,"name":"DIR","description":"A character string that defines the direction to apply the diffusivity multiplier between the two regions, should be set to one of the following X, Y, Z, XY, XZ, YZ, or XYZ.","units":{},"default":"XYZ","value_type":"STRING"},{"index":5,"name":"TYPE","description":"A character string that defines the type of connections the diffusivity multiplier should be applied to, should be one of the following: NNC – Only apply the diffusivity multiplier between REGION1 and REGION2 to non-neighbor connections. NONNC – Do not apply the diffusivity multiplier between REGION1 and REGION2 to non-neighbor connections. ALL - Apply the diffusivity multiplier between REGION1 and REGION2 to all connections.","units":{},"default":"ALL","value_type":"STRING"},{"index":6,"name":"REGION ARRAY","description":"The REGION ARRAY to use for applying the CONSTANT in (3) based on the regions REGION1 and REGION2 in (1 and 2). REGION ARRAY can have the following values: F for the FLUXNUM array M for the MULTNUM array O for the OPERNUM array","units":{},"default":"M","value_type":"STRING"}],"example":"--\n-- MULTIPLY DIFFUSIVITIES BETWEEN RESERVOIRS\n--\n-- REGION REGION DIFFS DIREC NNC REGION ARRAY\n-- FROM TO MULT OPT OPTS M / F / O\nMULTREGD\n1* 1* 1.05 1* 'ALL' M / ALL REGIONS\n/\nThe above example multiplies the diffusivities between all the MULTNUM regions by 1.05 in all directions and for all connections types.","expected_columns":6,"size_kind":"list"},"MULTREGH":{"name":"MULTREGH","sections":["GRID","EDIT"],"supported":false,"summary":"The MULTREGH keyword multiplies the thermal conductivity between two regions by a constant. The region number array can be FLUXNUM, MULTNUM or OPERNUM and these arrays must be defined and be available before the MULTREGT keyword is read by the simulator. The constant should be a real number.","parameters":[{"index":1,"name":"REGION1","description":"A positive integer value that defines the from REGION number for which the CONSTANT in (3) should be applied.","units":{},"default":"None","value_type":"INT"},{"index":2,"name":"REGION2","description":"A positive integer value that defines the to REGION number for which the CONSTANT in (3) should be applied.","units":{},"default":"None","value_type":"INT"},{"index":3,"name":"CONSTANT","description":"A real value to multiply the thermal conductivity between REGION1 and REGION2.","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"},{"index":4,"name":"DIR","description":"A character string that defines the direction to apply the thermal conductivity multiplier between the two regions, should be set to one of the following X, Y, Z, XY, XZ, YZ, or XYZ.","units":{},"default":"XYZ","value_type":"STRING"},{"index":5,"name":"TYPE","description":"A character string that defines the type of connections the thermal conductivity multiplier should be applied to, should be one of the following: NNC – Only apply the thermal conductivity multiplier between REGION1 and REGION2 to non-neighbor connections. NONNC – Do not apply the thermal conductivity multiplier between REGION1 and REGION2 to non-neighbor connections. ALL - Apply the thermal conductivity multiplier between REGION1 and REGION2 to all connections.","units":{},"default":"ALL","value_type":"STRING"},{"index":6,"name":"REGION ARRAY","description":"The REGION ARRAY to use for applying the CONSTANT in (3) based on the regions REGION1 and REGION2 in (1 and 2). REGION ARRAY can have the following values: F for the FLUXNUM array. M for the MULTNUM array. O for the OPERNUM array.","units":{},"default":"M","value_type":"STRING"}],"example":"--\n-- MULTIPLY THERMAL CONDUCTIVITIES BETWEEN RESERVOIRS\n--\n-- REGION REGION CONDS DIREC NNC REGION ARRAY\n-- FROM TO MULT OPT OPTS M / F / O\nMULTREGH\n1* 1* 1.05 1* 'ALL' M / ALL REGIONS\n/\nThe above example multiplies the thermal conductivities between all the MULTNUM regions by 1.05 in all directions and for all connections types.","expected_columns":6,"size_kind":"list"},"MULTREGP":{"name":"MULTREGP","sections":["GRID","EDIT"],"supported":null,"summary":"The MULTREGP keyword multiplies the pore volume of a cell by a constant for all cells with a specific region number. The region number array can be FLUXNUM, MULTNUM or OPERNUM and these arrays must be defined and be available before the MULTREGP keyword is read by the simulator. The constant should be a real number.","parameters":[{"index":1,"name":"REGION","description":"REGION is a positive integer representing the region for which the CONSTANT in (2) should be applied.","units":{},"default":"None","value_type":"INT"},{"index":2,"name":"CONSTANT","description":"A real value to multiply the pore volume by for a given REGION.","units":{},"default":"1","value_type":"DOUBLE"},{"index":3,"name":"REGION ARRAY","description":"The REGION ARRAY to use for applying the CONSTANT in (2) based on the REGION in (1). ARRAY can have the following values: F for the FLUXNUM array. M for the MULTNUM array. O for the OPERNUM array.","units":{},"default":"M","value_type":"STRING"}],"example":"--\n-- RESET PORE VOLUME FOR DIFFERENT REGIONS\n--\n-- REGION PORV REGION ARRAY\n-- NUMBER MULT M / F / O\nMULTREGP\n1 1.0456573 M / Fault Block 1\n2 0 M / Fault Block 2\n3 0.9756715 M / Fault Block 3\n4 0 M / Inactive Blocks\n/\nThe above example re-scales the pore volumes for MULTNUM regions one and three and makes regions two and four inactive by setting their pore volumes to zero.","expected_columns":3,"size_kind":"list"},"MULTREGT":{"name":"MULTREGT","sections":["GRID","EDIT","SCHEDULE"],"supported":null,"summary":"The MULTREGT keyword multiplies the transmissibility between two regions by a constant. The region number array can be FLUXNUM, MULTNUM or OPERNUM and these arrays must be defined and be available before the MULTREGT keyword is read by the simulator. The constant should be a real number.","parameters":[{"index":1,"name":"REGION1","description":"A positive integer value that defines the from REGION number for which the CONSTANT in (3) should be applied.","units":{},"default":"None","value_type":"INT"},{"index":2,"name":"REGION2","description":"A positive integer value that defines the to REGION number for which the CONSTANT in (3) should be applied.","units":{},"default":"None","value_type":"INT"},{"index":3,"name":"CONSTANT","description":"A real positive value to multiply the transmissibility between REGION1 and REGION2.","units":{},"default":"1","value_type":"DOUBLE"},{"index":4,"name":"DIR","description":"A character string that defines the direction to apply the transmissibility multiplier between the two regions, should be set to one of the following X, Y, Z, XY, XZ, YZ, or XYZ.","units":{},"default":"XYZ","value_type":"STRING"},{"index":5,"name":"TYPE","description":"A character string that defines the type of connections the transmissibility multiplier should be applied to, should be one of the following: NNC – Only apply the transmissibility multiplier between REGION1 and REGION2 to non-neighbor connections. NONNC – Do not apply the transmissibility multiplier between REGION1 and REGION2 to non-neighbor connections. ALL – Apply the transmissibility multiplier between REGION1 and REGION2 to all connections.","units":{},"default":"ALL","value_type":"STRING"},{"index":6,"name":"REGION ARRAY","description":"A single character that defines the REGION ARRAY that is used to specify the regions identified by REGION1 and REGION2. REGION ARRAY can have the following values: F for the FLUXNUM array M for the MULTNUM array O for the OPERNUM array","units":{},"default":"M","value_type":"STRING"}],"example":"--\n-- SET TRANSMISSIBILITES ACROSS DIFFERENT RESERVOIRS TO ZERO\n--\n-- REGION REGION TRANS DIREC NNC REGION ARRAY\n-- FROM TO MULT OPT OPTS M / F / O\nMULTREGT\n1* 1* 0.0 1* 'ALL' M / ALL REGIONS SEALED\n/\nThe above example isolates all regions from one another by setting the transmissibility for the MULTNUM regions to zero in all directions and for all connections types.\n| Note Note if the MULTREGT keyword is used in the EDIT section, OPM Flow will always apply the changes irrespective, of if the TRANX, TRANY and TRANZ transmissibility arrays have been entered or not in the EDIT section. This behavior is different to the commercial simulator that only applies the keyword if the transmissibility arrays have been entered in the EDIT section. |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":6,"size_kind":"list"},"MULTTHT-":{"name":"MULTTHT-","sections":["GRID","EDIT","SCHEDULE"],"supported":null,"summary":"MULTTHT- multiples the transmissibility between two cell faces in the -Theta direction for all the cells in the model via an array, that is the keyword sets the transmissibility multiplier of block (I, J, K) between the cells (I, J-1, K) and (I, J, K). An alternative to defining the complete array is to use the BOX keyword to define an area of the grid and then use the MULTTHT- keyword to set the multipliers just for the area defined by the BOX keyword (see the example).","parameters":[{"index":1,"name":"MULTTHT-","description":"MULTTHT- is an array of real positive numbers assigning the transmissibility multipliers in the -Theta direction to each cell face in the model. Repeat counts may be used, for example 20*100.0.","units":{},"default":"1.0"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n10 10 1 6 1 1 / DEFINE BOX AREA\n--\n-- SET MULTTHT- TRANSMISSIBILITY MULTIPLIERS\n--\nMULTTHT-\n6*0.500 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe above example defines a 0.5 scaling multiplier for the six cells defined by the preceding BOX statement. The ENDBOX keyword resets the input box to the full grid."},"MULTTHT":{"name":"MULTTHT","sections":["GRID","EDIT","SCHEDULE"],"supported":null,"summary":"MULTTHT multiples the transmissibility between two cell faces in the +Theta direction for all the cells in the model via an array, that is the keyword sets the transmissibility multiplier of block (I, J, K) between the cells (I, J, K) and (I, J+1, K). An alternative to defining the complete array is to use the BOX keyword to define an area of the grid and then use the MULTTHT keyword to set the multipliers just for the area defined by the BOX keyword (see the example).","parameters":[{"index":1,"name":"MULTTHT+","description":"MULTTHT+ is an array of real positive numbers assigning the transmissibility multipliers in the +Theta direction to each cell face in the model. Repeat counts may be used, for example 20*100.0.","units":{},"default":"1.0"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n10 10 1 6 1 3 / DEFINE BOX AREA\n--\n-- SET MULTTHT+ TRANSMISSIBILITY MULTIPLIERS\n--\nMULTTHT\n18*0.300 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe above example defines a 0.3 scaling multiplier for the 18 cells defined by the preceding BOX statement. The ENDBOX keyword resets the input box to the full grid."},"MULTX-":{"name":"MULTX-","sections":["GRID","EDIT","SCHEDULE"],"supported":null,"summary":"MULTX- multiples the transmissibility between two cell faces in the -X direction for all the cells in the model via an array, that is the keyword sets the transmissibility multiplier of block (I, J, K) between the cells (I-1, J, K) and (I, J, K). An alternative to defining the complete array is to use the BOX keyword to define an area of the grid and then use the MULTX- keyword to set the multipliers just for the area defined by the BOX keyword (see the example).","parameters":[{"index":1,"name":"MULTX-","description":"MULTX- is an array of real positive numbers assigning the transmissibility multipliers in the -X direction to each cell face in the model. Repeat counts may be used, for example 20*100.0.","units":{},"default":"1.0"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n10 10 1 6 1 1 / DEFINE BOX AREA\n--\n-- SET MULTX- TRANSMISSIBILITY MULTIPLIERS\n--\nMULTX-\n6*0.500 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe above example defines a 0.5 scaling multiplier for the six cells defined by the preceding BOX statement. The ENDBOX keyword resets the input box to the full grid."},"MULTX":{"name":"MULTX","sections":["GRID","EDIT","SCHEDULE"],"supported":null,"summary":"MULTX multiples the transmissibility between two cell faces in the +X direction for all the cells in the model via an array, that is the keyword sets the transmissibility multiplier of block (I, J, K) between the cells (I, J, K) and (I+I, J, K).","parameters":[{"index":1,"name":"MULTX+","description":"MULTX+ is an array of real positive numbers assigning the transmissibility multipliers in the +X direction to each cell face in the model. Repeat counts may be used, for example 20*100.0.","units":{},"default":"1.0"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n10 10 1 6 1 3 / DEFINE BOX AREA\n--\n-- SET MULTX+ TRANSMISSIBILITY MULTIPLIERS\n--\nMULTX\n18*0.300 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe above example defines a 0.3 scaling multiplier for the 18 cells defined by the preceding BOX statement. The ENDBOX keyword resets the input box to the full grid."},"MULTY-":{"name":"MULTY-","sections":["GRID","EDIT","SCHEDULE"],"supported":null,"summary":"MULTY- multiples the transmissibility between two cell faces in the -Y direction for all the cells in the model via an array, that is the keyword sets the transmissibility multiplier of block (I, J, K) between the cells (I, J-1, K) and (I, J, K). An alternative to defining the complete array is to use the BOX keyword to define an area of the grid and then use the MULTY- keyword to set the multipliers just for the area defined by the BOX keyword (see the example).","parameters":[{"index":1,"name":"MULTY-","description":"MULTY- is an array of real positive numbers assigning the transmissibility multipliers in the -Y direction to each cell face in the model. Repeat counts may be used, for example 20*100.0.","units":{},"default":"1.0"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n10 10 1 6 1 1 / DEFINE BOX AREA\n--\n-- SET MULTY- TRANSMISSIBILITY MULTIPLIERS\n--\nMULTY-\n6*0.500 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe above example defines a 0.5 scaling multiplier for the six cells defined by the preceding BOX statement. The ENDBOX keyword resets the input box to the full grid."},"MULTY":{"name":"MULTY","sections":["GRID","EDIT","SCHEDULE"],"supported":null,"summary":"MULTY multiples the transmissibility between two cell faces in the +Y direction for all the cells in the model via an array, that is the keyword sets the transmissibility multiplier of block (I, J, K) between the cells (I, J, K) and (I, J+1, K).","parameters":[{"index":1,"name":"MULTY+","description":"MULTY+ is an array of real positive numbers assigning the transmissibility multipliers in the +Y direction to each cell face in the model. Repeat counts may be used, for example 20*100.0.","units":{},"default":"1.0"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n10 10 1 6 1 3 / DEFINE BOX AREA\n--\n-- SET MULTY+ TRANSMISSIBILITY MULTIPLIERS\n--\nMULTY\n18*0.300 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe above example defines a 0.3 scaling multiplier for the 18 cells defined by the preceding BOX statement. The ENDBOX keyword resets the input box to the full grid."},"MULTZ-":{"name":"MULTZ-","sections":["GRID","EDIT","SCHEDULE"],"supported":null,"summary":"MULTZ- multiples the transmissibility between two cell faces in the -Z direction for all the cells in the model via an array, that is the keyword sets the transmissibility multiplier of block (I, J, K) between the cells (1, J, K-1) and (I, J, K). An alternative to defining the complete array is to use the BOX keyword to define an area of the grid and then use the MULTZ- keyword to set the multipliers just for the area defined by the BOX keyword (see the example).","parameters":[{"index":1,"name":"MULTZ-","description":"MULTZ- is an array of real positive numbers assigning the transmissibility multipliers in the -X direction to each cell face in the model. Repeat counts may be used, for example 20*100.0.","units":{},"default":"1.0"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n10 10 1 6 1 1 / DEFINE BOX AREA\n--\n-- SET MULTZ- TRANSMISSIBILITY MULTIPLIERS\n--\nMULTZ-\n6*0.500 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe above example defines a 0.5 scaling multiplier for the six cells defined by the preceding BOX statement. The ENDBOX keyword resets the input box to the full grid."},"MULTZ":{"name":"MULTZ","sections":["GRID","EDIT","SCHEDULE"],"supported":null,"summary":"MULTZ multiples the transmissibility between two cell faces in the +Z direction for all the cells in the model via an array, that is the keyword sets the transmissibility multiplier of block (I, J, K) between the cells (I, J, K) and (I, J, K+1).","parameters":[{"index":1,"name":"MULTZ+","description":"MULTZ+ is an array of real positive numbers assigning the transmissibility multipliers in the +Z direction to each cell face in the model. Repeat counts may be used, for example 20*100.0.","units":{},"default":"1.0"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n10 10 1 18 1 1 / DEFINE BOX AREA\n--\n-- SET MULTZ+ TRANSMISSIBILITY MULTIPLIERS\n--\nMULTZ\n18*0.300 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe above example defines a 0.3 scaling multiplier for the 18 cells defined by the preceding BOX statement. The ENDBOX keyword resets the input box to the full grid."},"NEWTRAN":{"name":"NEWTRAN","sections":["GRID"],"supported":null,"summary":"This keyword switches on Irregular Corner-Point Grid geometry transmissibility calculation, which is the default option for this type of grid. Grids defined with the COORD and ZCORN keywords will always invoke this option by default.","parameters":[],"example":"--\n-- ACTIVATE IRREGULAR CORNER-POINT GRID TRANSMISSIBILITIES\n--\nNEWTRAN\nThe above example manually activates Irregular Corner-Point Grid transmissibility calculations.","size_kind":"none","size_count":0},"NINENUM":{"name":"NINENUM","sections":["GRID"],"supported":false,"summary":"The NINENUM keyword defines areas in the grid that should use the Nine-Point Discretization formulation by setting a grid block’s NINENUM value to one, or zero for the conventional standard five-point discretization formulation, for when the Nine-Point Discretization formulation has been activated by the NINEPOIN keyword in the RUNSPEC section. There should be a NINENUM value for each grid block in the model. Note that if the if the NINEPOIN keyword in the RUNSPEC section has been invoked and the NINENUM keyword has not been used in the input deck, then all the grid will use the nine-point scheme.","parameters":[{"index":1,"name":"NINENUM","description":"NINENUM defines an integer array of zeros and ones assigning a grid cell to a particular discretization region, a value of zero for five-point or a value of one for nine-point discretization. Note that the default value of one implies a cell is included in the Nine-Point Discretization region; thus, if a cell is to use the conventional standard five-point finite difference discretization formulation, then NINENUM must be explicitly set to zero.","units":{},"default":"1"}],"example":"The example below sets a portion of the model to us the Nine-Point Discretization formulation.\n--\n-- DEFINE NINE-POINT DISCRETIZATION REGION FOR ALL CELLS\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nNINENUM’ 0 1* 1* 1* 1* 1* 1* / FIVE-POINT\nNINENUM’ 1 1* 1* 1* 1* 1 5 / NINE-POINT\n/\nHere the first line sets all the grid to us the five-point discretization formulation, all values set to zero, and then the second line sets all the cells in the layers one to five to use the nine-point discretization formulation.","size_kind":"array"},"NMATOPTS":{"name":"NMATOPTS","sections":["GRID"],"supported":false,"summary":"The NMATOPTS keyword defines the Discretized Matrix Dual Porosity parameters for when the Discretized Matrix Dual Porosity option has been activated by NMATRIX keyword in the RUNSPEC section. The option allows the matrix grid blocks to be subdivided into smaller cells for more accurate flow calculations, in particular the modeling of transient flow within the matrix grid blocks.","parameters":[{"index":1,"name":"GEOMETRY","description":"","units":{},"default":"LINEAR","value_type":"STRING"},{"index":2,"name":"FRACTION_PORE_VOL","description":"","units":{},"default":"0.1","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"METHOD","description":"","units":{},"default":"FPORV","value_type":"STRING"}],"example":"","expected_columns":3,"size_kind":"fixed","size_count":1},"NNC":{"name":"NNC","sections":["GRID"],"supported":null,"summary":"NNC enables Non-Neighbor Connections (“NNC”) to be manually defined. This keyword is normally generated by static modeling software as opposed to be manually entered in the OPM Flow input deck due to the verbosity and complexity of calculating the required parameters for this keyword.","parameters":[{"index":1,"name":"I1","description":"A positive integer that defines the first grid block in the I-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NX on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":2,"name":"J1","description":"A positive integer that defines the first grid block in the J-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NY on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":3,"name":"K1","description":"A positive integer that defines the first grid block in the K-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NZ on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":4,"name":"I2","description":"A positive integer that defines the second grid block in the I-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NX on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":5,"name":"J2","description":"A positive integer that defines the second grid block in the J-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NY on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":6,"name":"K2","description":"A positive integer that defines the second grid block in the K-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NZ on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":7,"name":"TRANSNNC","description":"TRANSNNC is a positive real number greater than or equal to zero that defines the transmissibility between the first grid block (I1, J1, K1) and the second grid block (I2, J2, K2). The default value of zero sets the transmissibility between the two cells to zero.","units":{"field":"cP.rb/day/psia","metric":"cP.rm3/day/bars","laboratory":"cP.rcc/hr/atm"},"default":"0.0","value_type":"DOUBLE","dimension":"Transmissibility"},{"index":8,"name":"ISATNUM1","description":"ISATNUM1 is a positive integer defining which saturation table number (relative permeability table) to be used for flow from the first grid block to the second grid block. The default value of zero means the existing saturation table allocated to the upstream cell (I1,J1,K1).","units":{},"default":"0","value_type":"INT"},{"index":9,"name":"ISATNUM2","description":"ISATNUM2 is a positive integer defining which saturation table number (relative permeability table) to be used for flow from the second grid block to the first grid block. The default value of zero means the existing saturation table allocated to the downstream cell (I2,J2,K2).","units":{},"default":"0","value_type":"INT"},{"index":10,"name":"IPRSNUM1","description":"IPRSNUM1 is a positive integer defining which pressure table number (PVT table) to be used for flow from the first grid block to the second grid block. The default value of zero means the existing PVT table allocated to the upstream cell (I1,J1,K1).","units":{},"default":"0","value_type":"INT"},{"index":11,"name":"IPRSNUM2","description":"IPRSNUM2 is a positive integer defining which pressure table number (PVT table) to be used for flow from the second grid block to the first grid block. The default value of zero means the existing PVT table allocated to the downstream cell (I2,J2,K2).","units":{},"default":"0","value_type":"INT"},{"index":12,"name":"FACE1","description":"FACE1 is a character string that defines the face associated with flow from the first grid block to the second grid block, where FACE1 can have values of: X+, X-, Y+, Y-, Z+, or Z-.","units":{},"default":"None","value_type":"STRING"},{"index":13,"name":"FACE2","description":"FACE2 is a character string that defines the face associated with flow from the second grid block to the first grid block, where FACE2 can have values of: X+, X-, Y+, Y-, Z+, or Z-.","units":{},"default":"None","value_type":"STRING"},{"index":14,"name":"DIFFNNC","description":"DIFFNNC is a positive real number that defines the diffusivity between the first grid block (I1, J1, K1) and the second grid block (I2, J2, K2).","units":{"field":"feet","metric":"meters","laboratory":"cm"},"default":"0.0","value_type":"DOUBLE"},{"index":15,"name":"DISPNNC","description":"DISPNNC s a positive real number that defines the dispersion coefficient [1 over ( Area x Porosity)]between the first grid block (I1, J1, K1) and the second grid block (I2, J2, K2), used with the between the first grid block (I1, J1, K1) and the second grid block (I2, J2, K2), used with the DISPERSE option.","units":{"field":"ft-2","metric":"m-2","laboratory":"cm-2"},"default":"0.0","value_type":"DOUBLE","dimension":"ContextDependent"},{"index":16,"name":"AREANNC","description":"AREANNC is a positive real number that defines the area associated with the connection between the first grid block (I1, J1, K1) and the second grid block (I2, J2, K2).","units":{"field":"ft2","metric":"m2","laboratory":"cm2"},"default":"None","value_type":"DOUBLE","dimension":"Length*Length"},{"index":17,"name":"PERMNNC","description":"AREANNC is a positive real number that defines the permeability associated with the connection between the first grid block (I1, J1, K1) and the second grid block (I2, J2, K2). This used by the non-Darcy option.","units":{"field":"mD","metric":"mD","laboratory":"mD"},"default":"None","value_type":"DOUBLE","dimension":"Permeability"}],"example":"--\n-- MANUALLY DEFINE NON-NEIGHBOR CONNECTIONS\n--\n-- ------------ BOX ----------- -- TRANSNNC --\n-- I1 J1 K1 I2 J2 K2\nNNC\n1 1 1 1 1 2 0.2500 / SET NNC FOR FAULT\n1 1 2 1 1 3 0.2500 / SET NNC FOR FAULT\n1 1 3 1 1 4 0.2500 / SET NNC FOR FAULT\n/\nThe above example defines the transmissibility between cells (1, 1, 1) and (1, 1, 2), (1, 1, 2) and (1, 1, 3) and finally between (1, 1, 3) and (1, 1, 4) to be 0.2500.","expected_columns":17,"size_kind":"list"},"NOGGF":{"name":"NOGGF","sections":["GRID"],"supported":false,"summary":"This keyword deactivates the output of a standard GRID or extended GRID file, as well as the extensible EGRID file for post-processing applications.","parameters":[],"example":"--\n-- DEACTIVATE GRID GEOMETRY OUTPUT\n--\nNOGGF\nThe above example switches off the default behavior of writing out the grid geometry files.","size_kind":"none","size_count":0},"NTG":{"name":"NTG","sections":["GRID"],"supported":null,"summary":"NTG defines the Net-to-Gross Ratio (“NTG”) for all the cells in the model via an array. The keyword can be used with all grid types.","parameters":[{"index":1,"name":"NTG","description":"NTG is an array of real numbers greater than or equal to zero and less than or equal to one, that are assigned the net-to-gross ratio values for each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 200*0.850.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK NTG DATA FOR ALL CELLS (BASED ON NX x NY x NZ = 300)\n--\nNTG\n100*1.000 100*0.850 100*0.500 /\nThe above example defines a constant NTG of 1.00 for the first 100 cells, then 0.85 for the second 100 hundred cells, and finally 0.500 for the last 100 cell, for the 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"NXFIN":{"name":"NXFIN","sections":["GRID"],"supported":false,"summary":"NXFIN defines the number of Local Grid Refinement (“LGR”) cells within a global or host cell in the x-direction via a vector, as opposed to defining the size for each cell for a Cartesian LGR Grid. The LGR keyword in the RUNSPEC section should be activated to indicate an LGR is being used, and the keyword NXFIN should be placed in between the CARFIN and ENDFIN keywords in the GRID section.","parameters":[{"index":1,"name":"NXFIN","description":"NXFIN is a vector of integer numbers describing the number of LGR cells within each defined global or host grid block in the x-direction in a Cartesian LGR grid. Repeat counts may be used, for example 2*2.0.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- CARFIN LGR GRID COMMANDS\n--\n-- LGR ----- HOST GRID ------ -- CARFIN GRID -- MAX HOST\n-- NAME I1 I2 J1 J2 K1 K2 NX NY NZ WELLS NAME\nCARFIN\nLGR-OP01 24 25 87 87 1 50 8 1 50 1 GLOBAL /\n--\n-- DEFINE LGR GRID BLOCKS IN THE X-DIRECTION\n--\nNXFIN\n4 4 /\nENDFIN\nThe above example splits the global cells (24-25,87, 1-50) into four and four LGR grid blocks in the x-direction, and since the HXFIN keyword has not been supplied, then the host cells will split into equal proportions.","size_kind":"array"},"NYFIN":{"name":"NYFIN","sections":["GRID"],"supported":false,"summary":"NYFIN defines the number of Local Grid Refinement (“LGR”) cells within a global or host cell in the x-direction via a vector, as opposed to defining the size for each cell for a Cartesian LGR Grid. The LGR keyword in the RUNSPEC section should be activated to indicate an LGR is being used, and the keyword NYFIN should be placed in between the CARFIN and ENDFIN keywords in the GRID section.","parameters":[{"index":1,"name":"NYFIN","description":"NYFIN is a vector of integer numbers describing the number of LGR cells within each defined global or host grid block in the y-direction in a Cartesian LGR grid. Repeat counts may be used, for example 2*2.0.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- CARFIN LGR GRID COMMANDS\n--\n-- LGR ----- HOST GRID ------ -- CARFIN GRID -- MAX HOST\n-- NAME I1 I2 J1 J2 K1 K2 NX NY NZ WELLS NAME\nCARFIN\nLGR-OP01 24 24 86 87 1 50 1 8 50 1 GLOBAL /\n--\n-- DEFINE LGR GRID BLOCKS IN THE Y-DIRECTION\n--\nNYFIN\n4 4 /\nENDFIN\nThe above example splits the global cells (24, 86-87,1-50) into four and four LGR grid blocks in the y-direction and since the HYFIN keyword has not been supplied, then the host cells will split into equal proportions.","size_kind":"array"},"NZFIN":{"name":"NZFIN","sections":["GRID"],"supported":false,"summary":"NZFIN defines the number of Local Grid Refinement (“LGR”) cells within a global or host cell in the z-direction via a vector, as opposed to defining the size for each cell for a Cartesian LGR Grid. The LGR keyword in the RUNSPEC section should be activated to indicate an LGR is being used, and the keyword NXFIN should be placed in between the CARFIN and ENDFIN keywords in the GRID section.","parameters":[{"index":1,"name":"NZFIN","description":"NZFIN is a vector of integer numbers describing the number of LGR cells within each defined global or host grid block in the x-direction in a Cartesian LGR grid. Repeat counts may be used, for example 2*2.0.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- CARFIN LGR GRID COMMANDS\n--\n-- LGR ----- HOST GRID ------ -- CARFIN GRID -- MAX HOST\n-- NAME I1 I2 J1 J2 K1 K2 NX NY NZ WELLS NAME\nCARFIN\nLGR-OP01 24 24 86 86 1 50 8 1 100 1 GLOBAL /\n--\n-- DEFINE LGR GRID BLOCKS IN THE Z-DIRECTION\n--\nNZFIN\n50*2 /\nENDFIN\nThe above example splits the global cells (24, 86, 1-50) into two LGR grid blocks per host cell in the z-direction, and since the HZFIN keyword has not been supplied, then the host cells will split into equal proportions.","size_kind":"array"},"OLDTRAN":{"name":"OLDTRAN","sections":["GRID"],"supported":null,"summary":"This keyword switches on Cartesian Regular Grids geometry transmissibility calculation (or block centered transmissibility calculations), which is the default option for this type of grid. Grids defined by the DX, DY, and DZ series of keywords will always invoke this option by default.","parameters":[],"example":"--\n-- ACTIVATE CARTESIAN REGULAR GRID TRANSMISSIBILITIES\n--\nOLDTRAN\nThe above example manually activates Cartesian Regular Grid transmissibility calculations.","size_kind":"none","size_count":0},"OLDTRANR":{"name":"OLDTRANR","sections":["GRID"],"supported":null,"summary":"This keyword switches on Radial Regular Grids geometry transmissibility calculation (or block centered transmissibility calculations), which is the default option for this type of grid. Grids defined by the DR, DTHETA, and DZ series of keywords will always invoke this option by default.","parameters":[],"example":"--\n-- ACTIVATE RADIAL REGULAR GRID TRANSMISSIBILITIES\n--\nOLDTRANR\nThe above example manually activates Radial Regular Grid transmissibility calculations.","size_kind":"none","size_count":0},"OPERATE":{"name":"OPERATE","sections":["GRID","EDIT","PROPS","REGIONS","SOLUTION"],"supported":false,"summary":"The OPERATE keyword performs a mathematical operation on a specified array or part of an array, optionally using another specified array as input to the operation. The keyword allows for various mathematical functions and their associated variables to be defined and applied to the specified array. Input constants can be integer or real valued depending on the array type; however, the arrays that can be operated on are dependent on which section the OPERATE keyword is being applied in.","parameters":[{"index":1,"name":"Y","description":"A character string of up to eight characters in length that defines the keyword identifying the array to be modified.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"I1","description":"A positive integer that defines the lower bound of the array in the I-direction to be modified must be greater than or equal to one and less than or equal to I2 and NX.","units":{},"default":"1","value_type":"INT"},{"index":3,"name":"I2","description":"A positive integer that defines the upper bound of the array in the I-direction to be modified must be greater than or equal to I1 and less than or equal to NX","units":{},"default":"NX","value_type":"INT"},{"index":4,"name":"J1","description":"A positive integer that defines the lower bound of the array in the J-direction to be modified must be greater than or equal to one and less than or equal to J2 and NY.","units":{},"default":"1","value_type":"INT"},{"index":5,"name":"J2","description":"A positive integer that defines the upper bound of the array in the J-direction to be modified must be greater than or equal to J1 and less than or equal to NY.","units":{},"default":"NY","value_type":"INT"},{"index":6,"name":"K1","description":"A positive integer that defines the lower bound of the array in the K-direction to be modified must be greater than or equal to one and less than or equal to K2 and NZ.","units":{},"default":"1","value_type":"INT"},{"index":7,"name":"K2","description":"A positive integer that defines the upper bound of the array in the K-direction to be modified must be greater than or equal to K1 and less than or equal to NZ.","units":{},"default":"NZ","value_type":"INT"},{"index":8,"name":"EQUATION","description":"A defined character string of up to eight characters that defines the mathematical function to be applied, using the X array and the ALPHA and BETA constants declared on this keyword. EQUATION should be set to one of the following character strings:","units":{},"default":"None","value_type":"STRING"},{"index":9,"name":"X","description":"A character string of up to eight characters in length that defines the keyword identifying the array to be used as an input parameter.","units":{},"default":"None","value_type":"STRING"},{"index":10,"name":"ALPHA","description":"An integer or real value that is the α variable in the EQUATION function.","units":{},"default":"None","value_type":"DOUBLE"},{"index":11,"name":"BETA","description":"An integer or real value that is the β variable in the EQUATION function.","units":{},"default":"None","value_type":"DOUBLE"}],"example":"The first example uses the MULTP function combined with the Net-to-Gross (NTG) array to re-scale the MULTX, MULTY and MULTZ arrays to reduce the transmissibility in three separate reservoirs based on the reservoir quality (NTG).\n--\n-- MATHEMATICAL OPERATIONS ON ARRAYS BY CELL\n--\n-- OUTPUT ---------- BOX --------- OPERATION INPUT ALPHA BETA\n-- ARRAY I1 I2 J1 J2 K1 K2 --------- ARRAY ----- ----\nOPERATE\nMULTX 1* 1* 1* 1* 1 32 ‘MULTP’ NTG 1.00 0.75 / RES1\nMULTY 1* 1* 1* 1* 1 32 ‘MULTP’ NTG 1.00 0.75 / RES1\nMULTZ 1* 1* 1* 1* 1 32 ‘MULTP’ NTG 1.00 0.75 / RES1\nMULTX 1* 1* 1* 1* 34 64 ‘MULTP’ NTG 1.00 0.85 / RES2\nMULTY 1* 1* 1* 1* 34 64 ‘MULTP’ NTG 1.00 0.85 / RES2\nMULTZ 1* 1* 1* 1* 34 64 ‘MULTP’ NTG 1.00 0.85 / RES2\nMULTX 1* 1* 1* 1* 67 96 ‘MULTP’ NTG 1.00 0.50 / RES3\nMULTY 1* 1* 1* 1* 67 96 ‘MULTP’ NTG 1.00 0.50 / RES3\nMULTZ 1* 1* 1* 1* 67 96 ‘MULTP’ NTG 1.00 0.50 / RES3\n/\nThe next example shows how to set the maximum gas saturation (SGU) based on the minimum (lowest) water saturation (SWL) when using the End-Point Scaling option.\n--\n-- MATHEMATICAL OPERATIONS ON ARRAYS\n--\n-- OUTPUT ---------- BOX --------- OPERATION INPUT ALPHA BETA\n-- ARRAY I1 I2 J1 J2 K1 K2 --------- ARRAY ----- ----\nOPERATE\nSGU 1* 1* 1* 1* 1* 1* 'MULTA' SWL -1.0 1.0 /\n/\nThe above example sets the maximum gas saturation to be one minus the minimum water saturation.\n| OPERATE Keyword and Variable Options by Section | | | | | | |\n|-------------------------------------------------|---------|-------|---------|----------|---------|----------|\n| GRID | EDIT | PROPS | REGIONS | SOLUTION | SUMMARY | SCHEDULE |\n| DX | DEPTH | SWL | ENDNUM | PRESSURE | | |\n| DY | PORV | SWCR | EQLNUM | SWAT | | |\n| DZ | TRANX | SWU | FIPNUM | SGAS | | |\n| PERMX | TRANY | SGL | IMBNUM | RV | | |\n| PERMY | TRANZ | SGCR | MISCNUM | RS | | |\n| PERMZ | DIFFX | SGU | PVTNUM | TBLK | | |\n| MULTX | DIFFY | KRW | ROCKNUM | GI | | |\n| MULTY | DIFFZ | KRO | SATNUM | OILAPI | | |\n| MULTZ | TRANR | KRG | WH2NUM | SALT | | |\n| DR | TRANTHT | PCG | | GASCONC | | |\n| DTHETA | DIFFR | PCW | | SOLVCONC | | |\n| PERMR | DIFFTHT | | | SOLVFRAC | | |\n| PERMTHT | | | | SFOAM | | |\n| DZNET | | | | SPOLY | | |\n| PORO | | | | | | |\n| NTG | | | | | | |\n| FLUXNUM | | | | | | |\n| MULTNUM | | | | | | |\n| MPFANUM | | | | | | |\n| DIFFX | | | | | | |\n| DIFFY | | | ","expected_columns":11,"size_kind":"list"},"OPERATER":{"name":"OPERATER","sections":["GRID","EDIT","PROPS","REGIONS","SOLUTION"],"supported":true,"summary":"The OPERATER keyword is similar to the OPERATE keyword, except it applies the mathematical operation on specific regions, whereas, OPERATE applies the operations on a cell by cell basis. Here the OPERATER keyword performs a mathematical operation on a specified property array, optionally using another property array as input to the function. The keyword allows for various mathematical functions and their associated variables to be defined and applied to the specified region data. Input constants can be integer or real valued depending on the array type; however, the arrays that can be operated on are dependent on which section the OPERATER keyword is being applied in.","parameters":[{"index":1,"name":"Y","description":"A character string of up to eight characters in length that defines the keyword identifying the array to be modified.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"REGION","description":"REGION is a positive integer representing the region for which the EQUATION should be applied. The default is to use the region number from the OPERNUM keyword; however this can be reset to another region array via the ARRAY item on this keyword, provided the array exists at the time the keyword is declared in the input deck. Note also the OPERNUM keyword must precede the use of the OPERATER keyword.","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"EQUATION","description":"A defined character string of up to eight characters that defines the mathematical function to be applied, using the X array and the ALPHA and BETA constants declared on this keyword. EQUATION should be set to one of the following character strings:","units":{},"default":"None","value_type":"STRING"},{"index":4,"name":"X","description":"A character string of up to eight characters in length that defines the keyword identifying the array to be used as an input parameter.","units":{},"default":"None","value_type":"STRING"},{"index":5,"name":"ALPHA","description":"An integer or real value that is the α variable in the EQUATION function.","units":{},"default":"None","value_type":"DOUBLE"},{"index":6,"name":"BETA","description":"An integer or real value that is the β variable in the EQUATION function.","units":{},"default":"None","value_type":"DOUBLE"},{"index":7,"name":"ARRAY","description":"The name of the array for which the REGION variable references. This can be any standard region array as declared in the REGION section (FIPNUM, PVTNUM, etc.), provided the array exists at the time the OPERATER keyword is invoked. In addition, the MULTNUM, FLUXNUM and OPERNUM may be used. Only the default value of OPERNUM is supported by OPM Flow.","units":{},"default":"OPERNUM","value_type":"STRING"}],"example":"The first example uses the MULTP function combined with the Net-to-Gross (NTG) array to re-scale the MULTX, MULTY and MULTZ arrays to reduce the transmissibility in three separate reservoirs based on the reservoir quality (NTG). This keyword sequence should be in the GRID section.\n--\n-- MATHEMATICAL OPERATIONS ON ARRAYS BY REGION\n--\n-- OUTPUT REGN OPERATION SOURCE ALPHA BETA REGN\n-- ARRAY NUM TYPE ARRAY CONST CONST ARRAY\nOPERATER\nMULTX 1 'MULTP' NTG 1.00 0.75 / RES1\nMULTY 1 'MULTP' NTG 1.00 0.75 / RES1\nMULTZ 1 'MULTP' NTG 1.00 0.75 / RES1\nMULTX 2 'MULTP' NTG 1.00 0.85 / RES2\nMULTY 2 'MULTP' NTG 1.00 0.85 / RES2\nMULTZ 2 'MULTP' NTG 1.00 0.85 / RES2\nMULTX 3 'MULTP' NTG 1.00 0.50 / RES3\nMULTY 3 'MULTP' NTG 1.00 0.50 / RES3\nMULTZ 3 'MULTP' NTG 1.00 0.50 / RES3\n/\nNotice that the ARRAY variable has been defaulted, resulting in OPERNUM being the regional array for the REGION variable.\nThe next example shows how to set the maximum gas saturation (SGU) based on the minimum (lowest) water saturation (SWL) when using the End-Point Scaling option, in the PROPS section.\n--\n-- MATHEMATICAL OPERATIONS ON ARRAYS\n--\n-- OUTPUT REGN OPERATION SOURCE ALPHA BETA REGN\n-- ARRAY NUM TYPE ARRAY CONST CONST ARRAY\nOPERATER\nSGU 1 'MULTA' SWL -1.0 1.0 /\nSGU 2 'MULTA' SWL -1.0 1.0 /\nSGU 3 'MULTA' SWL -1.0 1.0 /\n/\nThe above example sets the maximum gas saturation to be one minus the minimum water saturation for regions one to three.\nThe final example shows how to reset the FIPNUM array when the exported array from the earth model does not correspond to the simulator’s desired numbering scheme.\n--\n-- MATHEMATICAL OPERATIONS ON ARRAYS BY REGION\n--\n-- RESET FIPNUM BASED ON MULTNUM AND OPERNUM\n--\n-- DESTIN REGN OPERATION SOURCE ALPHA BETA INPUT SEGNUM EQUIL\n-- ARRAY NUM TYPE ARRAY CONST CONST ARRAY NUMBER NUMBER\nOPERATER\nFIPNUM 26 'MULTA' 'MULTNUM' 0.00 1 / 26 1\nFIPNUM 44 'MULTA' 'MULTNUM' 0.00 2 / 44 2\nFIPNUM 62 'MULTA' 'MULTNUM' 0.00 3 / 62 3\nFIPNUM 98 'MULTA' 'MULTNUM' 0.00 4 / 98 4\nFIPNUM 116 'MULTA' 'MULTNUM' 0.00 5 / 116 5\nFIPNUM 134 'MULTA' 'MULTNUM' 0.00 6 / 134 6\nFIPNUM 46 'MULTA' 'MULTNUM' 0.00 7 / 46 7\nFIPNUM 64 'MULTA' 'MULTNUM' 0.00 8 / 64 8\nFIPNUM 82 'MULTA' 'MULTNUM' 0.00 9 / 82 9\nFIPNUM 226 'MULTA' 'MULTNUM' 0.00 10 / 226 10\nFIPNUM 262 'MULTA' 'MULTNUM' 0.00 11 / 262 11\nFIPNUM 280 'MULTA' 'MULTNUM' 0.00 12 / 280 12\nFIPNUM 298 'MULTA' 'MULTNUM' 0.00 13 / 298 13\nFIPNUM 33 'MULTA' 'MULTNUM' 0.00 14 / 33 14\nFIPNUM 51 'MULTA' 'MULTNUM' 0.00 15 / 51 15\nFIPNUM 105 'MULTA' 'MULTNUM' 0.00 16 / 105 16\nFIPNUM 159 'MULTA' 'MULTNUM' 0.00 17 / 159 17\nFIPNUM 195 'MULTA' 'MULTNUM' 0.00 18 / 195 18\nFIPNUM 267 'MULTA' 'MULTNUM' 0.00 19 / 267 19\nFIPNUM 303 'MULTA' 'MULTNUM' 0.00 20 / 303 20\nFIPNUM 321 'MULTA' 'MULTNUM' 0.00 21 / 321 21\nFIPNUM 339 'MULTA' 'MULTNUM' 0.00 22 / 339 22\nFIPNUM 54 'MULTA' 'MULTNUM' 0.00 23 / 54 23\nFIPNUM 72 'MULTA' 'MULTNUM' 0.00 24 / 72 24\nFIPNUM 108 'MULTA' 'MULTNUM' 0.00 25 / 108 25\nFIPNUM 144 'MULTA' 'MULTNUM' 0.00 26 / 144 26\nFIPNUM 270 'MULTA' 'MULTNUM' 0.00 27 / 270 27\n/\nNote that operation can only be done in the REGION section as FIPNUM is only available for use in this section and that the ARRAY variable has been defaulted, resulting in OPERNUM being the regional array for the REGION variable.\n| OPERATER Keyword and Variable Options by Section | | | | | | |\n|--------------------------------------------------|---------|-------|---------|----------|---------|----------|\n| GRID | EDIT | PROPS | REGIONS | SOLUTION | SUMMARY | SCHEDULE |\n| DX | DEPTH | SWL | ENDNUM | PRESSURE | | |\n| DY | PORV | SWCR | EQLNUM | SWAT | | |\n| DZ | TRANX | SWU | FIPNUM | SGAS | | |\n| PERMX | TRANY | SGL |","expected_columns":7,"size_kind":"list"},"OPERNUM":{"name":"OPERNUM","sections":["GRID","REGIONS"],"supported":null,"summary":"This keyword defines the OPERATER region numbers for each grid block. The OPERNUM keyword defines the region numbers for each grid block, as such there must be one entry for each cell in the model. The array can also be used with the EQUALREG, ADDREG, COPYREG, MULTIREG, MULTREGP and MULTREGT keywords, as well as the OPERATER keyword in calculating various grid properties in the GRID and REGION section.","parameters":[{"index":1,"name":"OPERNUM","description":"OPERNUM defines an array of positive integers greater than or equal to one that assigns a grid cell to a particular OPERNUM region. The maximum number of OPERNUM regions is set by the NOPREG variable on the REGDIMS keyword in the RUNSPEC section. Note that the default value of zero implies that the calculations requested by the OPERATER keyword will not be performed.","units":{},"default":"0"}],"example":"The example below sets three OPERNUM regions for a 4 x 5 x 2 model.\n--\n-- DEFINE OPERNUM REGIONS FOR ALL CELLS\n--\nOPERNUM\n2 2 1 1 2 2 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n3 3 1 1 3 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n/\nAlternatively the EQUALS keyword could be employed to accomplish the same task, that is:\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nOPERNUM 1 1* 1* 1* 1* 1* 1* / SET REGION 1\nOPERNUM 2 1 2 1 2 1 1 / SET REGION 2\nOPERNUM 3 1 2 1 2 2 2 / SET REGION 3\n/\nOne can then increase PERMX by 25% in region three only.\n--\n-- MULTIPLY AN ARRAY BY A CONSTANT BASED ON A REGION NUMBER\n--\n-- ARRAY CONSTANT REGION REGION ARRAY\n-- VALUE NUMBER M / F / O\nMULTIREG\nPERMX 1.25 3 O /\n/","size_kind":"array"},"OUTRAD":{"name":"OUTRAD","sections":["GRID"],"supported":false,"summary":"OUTRAD defines the OUTER radius of the reservoir model for a radial or spider grid geometry. The RADIAL or SPIDER keyword in the RUNSPEC should be activated to indicate that radial or spider geometry is being used.","parameters":[{"index":1,"name":"OUTRAD","description":"A single real positive number greater than INRAD defining the outer radius of a radial grid.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":"Length"}],"example":"--\n-- INNER RADIUS OF FIRST GRID BLOCK IN THE RADIAL DIRECTION\n--\nINRAD\n0.25 /\n--\n-- OUTER RADIUS OF FIRST GRID BLOCK IN THE RADIAL DIRECTION\n--\nOUTRAD\n2050.0 /\nThe above example defines the inner radius to be 0.25 and the outer radius to be 2,050 feet. Note that the outer radius includes the inner radius.\n| [{R sub{i}} over {R sub{i-1}} ``=``left( OUTRAD over {R sub{i sub{j}-1}}right)` sup{1 over {left(NX`-`i sub{j}``+``1 right)}}] | (6.12) |\n|--------------------------------------------------------------------------------------------------------------------------------|--------|\n| [R sub{i}``=``left(R sub{i sub{j}-1} right) left( OUTRAD over {R sub{i sub{j}-1}} right)` sup{left(i`-`i sub{j}`+1` right) over {left(NX`-`i sub{j}``+``1 right)}}] | (6.13) |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|\n| [DR sub{ i}~=~R sub{i}``-``R sub{i`-`1}] | (6.14) |\n|------------------------------------------|--------|\n| OUTRAD Radial Grid Example | | | |\n|----------------------------|----------|----------|-------|\n| INRAD | 0.25 | | |\n| OUTRAD | 2050.0 | | |\n| NX | 10 | | |\n| NX | Ri | DR | Ratio |\n| 0 | 0.250 | 0.250 | |\n| 1 | 0.616 | 0.366 | 1.463 |\n| 2 | 1.516 | 0.900 | 2.463 |\n| 3 | 3.733 | 2.217 | 2.463 |\n| 4 | 9.193 | 5.460 | 2.463 |\n| 5 | 22.638 | 13.445 | 2.463 |\n| 6 | 55.748 | 33.109 | 2.463 |\n| 7 | 137.281 | 81.533 | 2.463 |\n| 8 | 338.058 | 200.777 | 2.463 |\n| 9 | 832.477 | 494.420 | 2.463 |\n| 10 | 2050.000 | 1217.523 | 2.463 |\n| Total | | 2050.000 | |","expected_columns":1,"size_kind":"fixed","size_count":1},"PARAOPTS":{"name":"PARAOPTS","sections":["GRID"],"supported":false,"summary":"The PARAOPTS keyword defines various options for parallel runs, for when the Parallel option has been invoked by the PARALLEL keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"METHOD","description":"","units":{},"default":"TREE","value_type":"STRING"},{"index":2,"name":"SET_PRINT","description":"","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"SIZE","description":"","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"NUM_BUFFERS","description":"","units":{},"default":"2","value_type":"INT"},{"index":5,"name":"VALUE_MEM","description":"","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"VALUE_COARSE","description":"","units":{},"default":"0","value_type":"INT"},{"index":7,"name":"VALUE_NNC","description":"","units":{},"default":"0","value_type":"INT"},{"index":8,"name":"VALUE_PRT_FILE","description":"","units":{},"default":"1","value_type":"INT"},{"index":9,"name":"RESERVED","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":9,"size_kind":"fixed","size_count":1},"PEBI":{"name":"PEBI","sections":["GRID"],"supported":false,"summary":"PEBI activates the unstructured Perpendicular Bisector (“PEBI”)121\n Heinemann, Z.E. and Brand, C.W. 1988. Gridding Techniques in Reservoir Simulation. Proc., First Intl. Forum on Reservoir Simulation, Alpbach, Austria, 339. and 122\n Heinemann, Z.E., Brand, C.W., Munka, M. et al. 1991. Modeling Reservoir Geometry With Irregular Grids. SPE Res Eng 6 (2): 225–232. SPE-18412-PA. http://dx.doi.org/10.2118/18412-PAloading of grid data generated by an external pre-processing program for generating simulation grids.","parameters":[{"index":1,"name":"OPTION1","description":"A defined character string that activates or deactivates the checking of negative transmissibility values. OPTION1 should be set to YES to check for negative values, or NO switches off this option.","units":{},"default":"NO","value_type":"STRING"},{"index":2,"name":"OPTION2","description":"A defined character string that activates or deactivates the calculation of pore volumes and transmissibilities. OPTION2 should be set to YES if the pore volumes and transmissibilities are provided, or NO for the values to calculated by the simulator.","units":{},"default":"NO","value_type":"STRING"}],"example":"–-\n-- OPTION1 OPTION2\n-- CHECK CALCULATE\nPEBI\nNO YES /\nThe above example switches off the negative transmissibility check and requests that the simulator calculates pore volumes and transmissibilities as they are not provided by the input data.","expected_columns":2,"size_kind":"fixed","size_count":1},"PERMAVE":{"name":"PERMAVE","sections":["GRID"],"supported":false,"summary":"The PERMAVE keyword defines the three directional exponent coefficients used to average the grid block permeabilities between two neighboring cells when calculating the transmissibility between the two blocks. The keyword can be used to change from the default weighted harmonic averaging (coefficient set equal to -1), to geometric (coefficient equal to zero), or to arithmetic averaging (coefficient equal to 1). The three coefficients represent the averaging in the x-, y- and z-directions.","parameters":[{"index":1,"name":"EXPO_0","description":"","units":{},"default":"-1","value_type":"INT"},{"index":2,"name":"EXPO_1","description":"","units":{},"default":"-1","value_type":"INT"},{"index":3,"name":"EXPO_2","description":"","units":{},"default":"-1","value_type":"INT"}],"example":"","expected_columns":3,"size_kind":"fixed","size_count":1},"PERMJFUN":{"name":"PERMJFUN","sections":["GRID"],"supported":false,"summary":"PERMJFUN defines the permeability to be used in de-normalizing the Leverett J-Functions123\n Leverett, M. C.; “Capillary Behaviour in Porous Solids”, Trans. AIME (1941) 142, 152-168. for when the PERM variable on the JFUNC or the JFUNCR keyword in the GRID section has been set to “U”, as oppose to using PERMX, PERMY, PERMZ arrays etc.","parameters":[{"index":1,"name":"PERMJFUN","description":"PERMJFUN is an array of real positive numbers assigning the permeability to be used in de-normalizing the Leverett J-Function to each cell in the model. Repeat counts may be used, for example 20*100.0.","units":{"field":"mD","metric":"mD","laboratory":"mD"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK PERMJFUN FOR ALL CELLS (BASED ON NX x NY x NZ = 300)\n--\nPERMJFUN\n100*500.0 100*50.0 100*200.0 /\nThe above example defines the PERMJFUN to be 500.0, 50.0, and 200.0 for the first, second and third layers in the model for all 300 cells, as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"PERMR":{"name":"PERMR","sections":["GRID"],"supported":null,"summary":"PERMR sets the permeability for each cell in the R direction in a radial geometry grid. The RADIAL or SPIDER keywords in the RUNSPEC should be activated to indicate that radial or spider geometry is being used.","parameters":[{"index":1,"name":"PERMR","description":"PERMR is an array of real positive numbers assigning the permeability in the R direction to each cell in the model. This equivalent to PERMX in a Cartesian grid. Repeat counts may be used, for example 20*100.0.","units":{"field":"mD","metric":"mD","laboratory":"mD"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK PERMR DATA FOR ALL CELLS (BASED ON NR x NY x NZ = 300)\n--\nPERMR\n100*500.0 100*50.0 100*200.0 /\nThe above example defines the PERMR to be 500.0, 50.0, and 200.0 for the first, second and third layers in the model for all 300 cells, as defined by the DIMENS keyword (10, 10, 3) in the RUNSPEC section.","size_kind":"array"},"PERMTHT":{"name":"PERMTHT","sections":["GRID"],"supported":null,"summary":"PERMTHT sets the permeability for each cell in the THETA direction in a radial geometry grid. The RADIAL or SPIDER keyword in the RUNSPEC should be activated to indicate that radial or spider geometry is being used.","parameters":[{"index":1,"name":"PERMTHT","description":"PERMTHT is an array of real positive numbers assigning the permeability in the THETA direction to each cell in the model. This equivalent to PERMY in a Cartesian grid. Repeat counts may be used, for example 20*100.0.","units":{"field":"mD","metric":"mD","laboratory":"mD"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK PERMTHT DATA FOR ALL CELLS (NX x NY x NZ = 300)\n--\nPERMTHT\n100*500.0 100*50.0 100*200.0 /\nThe above example defines the PERMTHT to be 500.0, 50.0, and 200.0 for the first, second and third layers in the model for all 300 cells, as defined by the DIMENS keyword (10, 10, 3) in the RUNSPEC section.","size_kind":"array"},"PERMX":{"name":"PERMX","sections":["GRID"],"supported":null,"summary":"PERMX defines the permeability in the X direction for all the cells in the model via an array. The keyword can be used for all grid types, except for the Radial Grid geometry.","parameters":[{"index":1,"name":"PERMX","description":"PERMX is an array of real positive numbers assigning the permeability in the X direction to each cell in the model. Repeat counts may be used, for example 20*100.0.","units":{"field":"mD","metric":"mD","laboratory":"mD"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK PERMX DATA FOR ALL CELLS (BASED ON NX x NY x NZ = 300)\n--\nPERMX\n100*500.0 100*50.0 100*200.0 /\nThe above example defines the PERMX to be 500.0, 50.0, and 200.0 for the first, second and third layers in the model for all 300 cells, as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"PERMY":{"name":"PERMY","sections":["GRID"],"supported":null,"summary":"PERMY defines the permeability in the Y direction for all the cells in the model via an array. The keyword can be used for all grid types, except for the Radial Grid geometry.","parameters":[{"index":1,"name":"PERMY","description":"PERMY is an array of real positive numbers assigning the permeability in the Y direction to each cell in the model. Repeat counts may be used, for example 20*100.0.","units":{"field":"mD","metric":"mD","laboratory":"mD"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK PERMY DATA FOR ALL CELLS (BASED ON NX x NY x NZ = 300)\n--\nPERMY\n100*500.0 100*50.0 100*200.0 /\nThe above example defines the PERMY to be 500.0, 50.0, and 200.0 for the first, second and third layers in the model for all 300 cells, as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"PERMZ":{"name":"PERMZ","sections":["GRID"],"supported":null,"summary":"PERMZ defines the permeability in the Z direction for all the cells in the model via an array. The keyword can be used for all grid types, except for the Radial Grid geometry.","parameters":[{"index":1,"name":"PERMZ","description":"PERMZ is an array of real positive numbers assigning the permeability in the Z direction to each cell in the model. Repeat counts may be used, for example 200*50.0.","units":{"field":"mD","metric":"mD","laboratory":"mD"},"default":"None"}],"example":"The example below defines the PERMZ to be 50.0, 5.0, and 20.0 for the first, second and third layers in the model for all 300 cells, as defined by the DIMENS keyword in the RUNSPEC section.\n--\n-- DEFINE GRID BLOCK PERMZ DATA FOR ALL CELLS (BASED ON NX x NY x NZ = 300)\n--\nPERMZ\n100*50.0 100*5.0 100*20.0 /\nThe next example sets PERMX to be 500.0, 50.0, and 200.0 for the first, second and third layers in the model for all 300 cells, as defined by the DIMENS keyword in the RUNSPEC section. It then copies the PERMX values to the PERMY and PERMZ arrays, and finally multiplies PERMZ by 0.1 times to get the final values for PERMZ.\n--\n-- DEFINE GRID BLOCK PERMX DATA FOR ALL CELLS\n--\nPERMX\n100*500.0 100*50.0 100*200.0 /\n--\n-- SOURCE DESTIN. ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nCOPY\nPERMX PERMY 1* 1* 1* 1* 1* 1* / CREATE PERMY\nPERMX PERMZ 1* 1* 1* 1* 1* 1* / CREATE PERMZ\n/\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nMULTIPLY\nPERMZ 0.10000 1* 1* 1* 1* 1* 1* / PERMZ * 0.1\n/\nThe above sequence of keywords is quite common in input decks, that is copying the PERMX data to the PERMY and PERMZ arrays and then adjusting the PERMY and PERMZ arrays as required using the MULTIPLY keyword.\n| Note Although PERMX and PERMY are commonly set to be equal, PERMZ is typically not equal to either PERMX or PERMY. Normally PERMZ is set as a fraction of PERMX with typical values ranging from 0.1 to 0.5 times PERMX. |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"array"},"PETGRID":{"name":"PETGRID","sections":["GRID"],"supported":false,"summary":"The PETGRID keyword instructs the simulator to load a Generic Simulation Grid (*.GSG) file that contains grid geometry data.","parameters":[{"index":1,"name":"FILE_NAME","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"PINCH":{"name":"PINCH","sections":["GRID"],"supported":null,"summary":"The PINCH keyword defines the parameters used to control the generation of Non-Neighbor Connections (“NNCs”) in the vertical (K) direction due to layers pinching out. This keyword is applied to all layers in the model as opposed to the PINCHREG keyword that offers more flexibility by applying the pinch-out controls to various regions in the model defined by the PINCHNUM keyword.","parameters":[{"index":1,"name":"PINCHTHK","description":"A real number defining the pinch-out threshold thickness for any cell. NNCs are generated across inactive cells having a vertical thickness less than PINCHTHK.","units":{"field":"ft. 0.001","metric":"m 0.001","laboratory":"cm 0.001"},"default":"Defined","value_type":"DOUBLE","dimension":"Length"},{"index":2,"name":"PINCHOPT","description":"A character string controlling the generation of pinch-outs when the MINPV keyword has been used to deactivate cells with small pore volumes. PINCHOPT can either be set to: GAP to allow the generation of NNCs across cells that have been made inactive with the MINPV keyword when the thickness is greater than PINCHTHK threshold. NOGAP to enforce the strict adherence to the PINCHTHK threshold whether or not cells have been made inactive due to the MINPV keyword.","units":{},"default":"GAP","value_type":"STRING"},{"index":3,"name":"PINCHGAP","description":"A real number defining the maximum “empty” thickness allowed between grid blocks in adjacent grid layers for a non-zero transmissibility to exist between them.","units":{"field":"ft. 1.0E20","metric":"m 1.0E20","laboratory":"cm 1.0E20"},"default":"Defined","value_type":"DOUBLE","dimension":"Length"},{"index":4,"name":"PINCHCAL","description":"A character string controlling the calculation of the pinch-out transmissibilities. PINCHCAL can either be set to: TOPBOT results in the pinch-out transmissibility being calculated from the half-cell Z-direction transmissibilities of the active cells on either side of the pinched-out layers. ALL results in the pinch-out transmissibility being calculated from the Z-direction transmissibilities harmonic average of all the cells between the active cells on either side of the pinched-out layers.","units":{},"default":"TOPBOT","value_type":"STRING"},{"index":5,"name":"PINCHMUL","description":"A character string controlling the calculation of the pinch-out transmissibilities when adjustments have been made by the MULTZ keyword. PINCHMUL can either be set to: TOP results in the pinch-out transmissibility being calculated from the active cell at the top of the pinch-out. ALL results in the pinch-out transmissibility being calculated from the minimum value of the MULTZ of the active cell at the top of the pinch-out and all the inactive cells in the pinch-out vertical column. Note if PINCHCAL has been set equal to ALL then PINCHMUL is reset to TOP, irrespective of the entered value for PINCHMUL.","units":{},"default":"TOP","value_type":"STRING"}],"example":"The first example below will create NNCs between the cells above and below any cell having vertical thickness less than 0.01 in either feet or metres.\n--\n-- SET PINCH-OUT PARAMETERS FOR CALCULATING PINCH-OUT PROPERTIES\n--\nPINCH\n-- THRESHOLD GAP EMPTY TRANS MULTZ\n-- THICKNESS NO GAP GAP CALC CALC\n0.01 1* 1* 1* 1* /\nFor the second example, the MINPV keyword is used to set the minimum pore volume to 500 m3 (metric units) and then the PINCH keyword is invoked with PINCHGAP set equal to GAP, as follows:\n--\n-- MINIMUM PORE VOLUME FOR ACTIVE CELLS\n--\nMINPV\n500.0 /\n--\n-- SET PINCH-OUT CRITERIA FOR THE MODEL\n--\nPINCH\n-- THRESHOLD GAP EMPTY TRANS MULTZ\n-- THICKNESS NO GAP GAP CALC CALC\n0.1 GAP 1* 1* 1* /\nIn the above example the MINPV keyword will deactivate all cells with pore volumes less than 500 m3. These deactivated cells are inactive in the model and therefore are not included in the flow calculations; however, by default they will result in no-flow barriers but may not be thin enough for PINCH to create NNCs across them. By setting PINCHGAP equal to GAP on the PINCH keyword (the default setting), then OPM Flow generates NNCs across the cells that have been deactivated by the MINPV keyword. However, in this case there may be grid blocks in the model with a pore volume greater than MINPV but a thickness less than the pinch-out threshold. These cells will not be deactivated by the PINCH keyword.","expected_columns":5,"size_kind":"fixed","size_count":1},"PINCHNUM":{"name":"PINCHNUM","sections":["GRID"],"supported":false,"summary":"The PINCHNUM keyword defines the pinch-out region numbers for each grid block, as such there must be one entry for each cell in the model. The array is used with the PINCHREG keyword to set the pinch-out options and threshold thickness for each region.","parameters":[{"index":1,"name":"PINCHNUM","description":"PINCHNUM defines an array of positive integers assigning a grid cell to a particular PINCHNUM region. The maximum number of PINCHNUM regions is set by the NRPINC variable on the GRIDOPTS keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"The example below sets defines three PINCHNUM regions for various layers in a model based on the model’s layering.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nMULTNUM 1 1* 1* 1* 1* 1* 1* / SET REGION 1\nMULTNUM 2 1 2 1 2 10 50 / SET REGION 2\nMULTNUM 3 1 2 1 2 51 100 / SET REGION 3\n/\nOne can then set the pinch-out criteria for each region.\n--\n-- SET PINCH-OUT CRITERA VIA THE PINCHNUM REGION\n--\nPINCHREG\n-- THRESHOLD GAP EMPTY TRANS\n-- THICKNESS NO GAP GAP CALC\n0.1 1* 1* 1* / PINCHNUM 01\n1.0 1* 10 1* / PINCHNUM 02\n1.0 NOGAP 20 1* / PINCHNUM 03\nThe above example sets the default pinch-out criteria for grid blocks defined as region one via the PINCHNUM array and different criteria for regions two and three.","size_kind":"array"},"PINCHOUT":{"name":"PINCHOUT","sections":["GRID"],"supported":false,"summary":"The PINCHOUT keyword activates the generation of Non-Neighbor Connections (“NNCs”) in the vertical (K) direction due to layers pinching out, using a constant threshold thickness of 0.001 for all unit systems. See also the PINCH keyword in the GRID section that allows for specifying the threshold thickness and other parameters on a layer basis, and the PINCHREG keyword that applies the pinch-out controls to various regions in the model defined by the PINCHNUM keyword.","parameters":[],"example":"The example will create NNCs between the cells above and below any cell having vertical thickness less than 0.001 in either feet or metres.\n--\n-- SET PINCH-OUT CRITERA WITH CONSTANT THRESHOLD THICKNESS OF 0.001\n--\nPINCHOUT","size_kind":"none","size_count":0},"PINCHREG":{"name":"PINCHREG","sections":["GRID"],"supported":null,"summary":"The PINCHREG keyword defines the parameters used to control the generation of Non-Neighbor Connections (“NNCs”) in the vertical (K) direction due to layers pinching out in combination with the PINCHNUM keyword. This allows different regions in the model to use different criteria in controlling the how pinch-outs are generated. The keyword should contain NRPINC records defining the criteria for each pinch-out region defined with the PINCHNUM keyword. NRPINC is the maximum number of PINCHNUM regions defined via the GRIDOPTS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"PINCHTHK","description":"A real number defining the pinch-out threshold thickness for any cell. NNCs are generated across inactive cells having a vertical thickness less than PINCHTHK.","units":{"field":"ft. 0.001","metric":"m 0.001","laboratory":"cm 0.001"},"default":"Defined","value_type":"DOUBLE","dimension":"Length"},{"index":2,"name":"PINCHOPT","description":"A character string controlling the generation of pinch-outs when the MINPV keyword has been used to deactivate cells with small pore volumes. PINCHOPT can either be set to: GAP to allow the generation of NNCs across cells that have been made inactive with the MINPV keyword when the thickness is greater than PINCHTHK threshold. NOGAP to enforce the strict adherence to the PINCHTHK threshold whether or not cells have been made inactive due to the MINPV keyword.","units":{},"default":"GAP","value_type":"STRING"},{"index":3,"name":"PINCHGAP","description":"A real number defining the maximum “empty” thickness allowed between grid blocks in adjacent grid layers for a non-zero transmissibility to exist between them.","units":{"field":"ft. 1.0E20","metric":"m 1.0E20","laboratory":"cm 1.0E20"},"default":"Defined","value_type":"DOUBLE","dimension":"Length"},{"index":4,"name":"PINCHCAL","description":"A character string controlling the calculation of the pinch-out transmissibilities. PINCHCAL can either be set to: TOPBOT results in the pinch-out transmissibility being calculated from the half-cell Z-direction transmissibilities of the active cells on either side of the pinched-out layers. ALL results in the pinch-out transmissibility being calculated from the Z-direction transmissibilities harmonic average of all the cells between the active cells on either side of the pinched-out layers.","units":{},"default":"TOPBOT","value_type":"STRING"},{"index":5,"name":"PINCHMUL","description":"A character string controlling the calculation of the pinch-out transmissibilities when adjustments have been made by the MULTZ keyword. PINCHMUL can either be set to: TOP results in the pinch-out transmissibility being calculated from the active cell at the top of the pinch-out. ALL results in the pinch-out transmissibility being calculated from the minimum value of the MULTZ of the active cell at the top of the pinch-out and all the inactive cells in the pinch-out vertical column. Note if PINCHCAL has been set equal to ALL then PINCHMUL is reset to TOP, irrespective of the entered value for PINCHMUL.","units":{},"default":"TOP","value_type":"STRING"}],"example":"--\n-- SET PINCH-OUT CRITERA VIA THE PINCHNUM REGION\n--\nPINCHREG\n-- THRESHOLD GAP EMPTY TRANS\n-- THICKNESS NO GAP GAP CALC\n0.1 1* 1* 1* / PINCHNUM 01\n1.0 1* 10 1* / PINCHNUM 02\n1.0 NOGAP 20 1* / PINCHNUM 03\nThe above example sets the default pinch-out criteria for grid blocks defined as region one via the PINCHNUM array and different values for regions two and three.","expected_columns":5,"size_kind":"list"},"PINCHXY":{"name":"PINCHXY","sections":["GRID"],"supported":false,"summary":"The PINCHXY keyword defines the x-direction and y-direction threshold thickness used to control the generation of Non-Neighbor Connections (“NNCs”) in the x- and y- directions for missing cells in the areal plane.","parameters":[{"index":1,"name":"PINCHTHX","description":"A real number defining the pinch-out threshold width for any cell in the x-direction. NNCs are generated across inactive cells having a width less than PINCHTHX in the x-direction.","units":{"field":"ft. 0.001","metric":"m 0.001","laboratory":"cm 0.001"},"default":"Defined","value_type":"DOUBLE","dimension":"Length"},{"index":2,"name":"PINCHTHY","description":"A real number defining the pinch-out threshold width for any cell in the y-direction. NNCs are generated across inactive cells having a width less than PINCHTHY in the y-direction.","units":{"field":"ft. 0.001","metric":"m 0.001","laboratory":"cm 0.001"},"default":"Defined","value_type":"DOUBLE","dimension":"Length"}],"example":"The example below will create NNCs between the cells in the areal plane having cell widths less than 0.01 in either feet or metres in both the x- and y-directions.\n--\n-- SET PINCH-OUT PARAMETERS FOR AREAL PLANE\n--\nPINCHXY\n-- X-DIRC Y-DIRC\n-- THRESHOLD THRESHOLD\n--\n0.01 0.01 /","expected_columns":2,"size_kind":"fixed","size_count":1},"PORO":{"name":"PORO","sections":["GRID"],"supported":null,"summary":"PORO defines the porosity for all the cells in the model via an array. The keyword can be used with all grid types.","parameters":[{"index":1,"name":"PORO","description":"PORO is an array of real positive numbers that are greater than or equal to zero and less than or equal to one that are the porosity values for each cell in the model. Repeat counts may be used, for example 3000*0.15","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK POROSITY DATA FOR ALL CELLS (BASED ON NX x NY x NZ = 300)\n--\nPORO\n300*0.300 /\nThe above example defines a constant porosity of 0.300 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"PYEND":{"name":"PYEND","sections":["GRID","EDIT","PROPS","REGIONS","SOLUTION","SUMMARY","SCHEDULE"],"supported":null,"summary":"The PYINPUT and PYEND keywords are a part of OPM Flow’s Python scripting facility that processes standard Python commands that can be used to manipulate and define the simulators input parameters during processing of the input deck. The main purpose of the facility is to script the construction of the various keywords.","parameters":[],"example":"The example shows how to construct the DX variable in the GRID section and to add the resulting DX array as part of the input deck.\n--\n-- START OF PYINPUT SECTION\n--\nPYINPUT\n#\n# Import Numpy Model\n#\nimport numpy as np\n#\n# Define DX and Get the Input Decks Unit Systems\n#\ndx = np.array([100.0, 100.0, 100.0, 100.0])\nactive_unit_system = context.deck.active_unit_system()\ndefault_unit_system = context.deck.default_unit_system()\n#\n# Set DX in the Input Deck\n#\nkw = context.DeckKeyword( context.parser['DX'], dx, active_unit_system,\ndefault_unit_system )\ncontext.deck.add(kw)\nPYEND\nThe active Parser objects are accessible as context.parser and the active Deck object is available as context.deck.\n| Note This is an OPM Flow specific keyword for the simulator’s scripting facility using the standard Python interpreter, as such it gives more flexibility than the commercial simulator’s data editing keywords (ADD, EQUAL, MULTIPLY, etc.), although OPM Flow also supports these keywords as well. The PYINPUT facility should be considered experimental as details of the OPM Flow - Python interface might change for future releases. In particular, the current implementation is quite minimal; however, future releases are expected to add more entry points in the simulator’s deck class which can be used to manipulate the input deck as the data is loaded. As a user you are encouraged to come with wishes in this regard. The PYINPUT facility is very powerful and allows for any piece of Python code to be included and run, including potentially malicious code. The important point is to scrutinize the Python code in between PYINPUT and PYEND in a deck you receive from other parties. |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|"},"PYINPUT":{"name":"PYINPUT","sections":["RUNSPEC","GRID","EDIT","PROPS","REGIONS","SOLUTION","SUMMARY","SCHEDULE"],"supported":null,"summary":"The PYINPUT and PYEND keywords are a part of OPM Flow’s Python scripting facility that processes standard Python commands that can be used to manipulate and define the simulators input parameters during processing of the input deck. The main purpose of the facility is to script the construction of the various keywords used by the simulator.","parameters":[{"index":"1-1","name":"PYTHON","description":"A series of standard Python commands with one line per command. The active Parser objects are accessible as context.parser and the active Deck object is available as context.deck.","units":{},"default":""}],"example":"The example shows how to construct the DX variable in the GRID section and to add the resulting DX array as part of the input deck.\n--\n-- START OF PYINPUT SECTION\n--\nPYINPUT\n#\n# Import Numpy Model\n#\nimport numpy as np\n#\n# Define DX and Get the Input Decks Unit Systems\n#\ndx = np.array([100.0, 100.0, 100.0, 100.0])\nactive_unit_system = context.deck.active_unit_system()\ndefault_unit_system = context.deck.default_unit_system()\n#\n# Set DX in the Input Deck\n#\nkw = context.DeckKeyword( context.parser['DX'], dx, active_unit_system,\ndefault_unit_system )\ncontext.deck.add(kw)\nPYEND\nThe active Parser objects is accessible as context.parser and the active Deck object is available as context.deck.\n| Note This is an OPM Flow specific keyword for the simulator’s scripting facility using the standard Python interpreter, as such it gives more flexibility than the commercial simulator’s data editing keywords (ADD, EQUALS, MULTIPLY, etc.), although OPM Flow also supports these keywords as well. The PYINPUT facility should be considered experimental as details of the OPM Flow - Python interface might change for future releases. In particular, the current implementation is quite minimal; however, future releases are expected to add more entry points in the simulator’s deck class which can be used to manipulate the input deck as the data is loaded. As a user you are encouraged to come with wishes in this regard. The PYINPUT facility is very powerful and allows for any piece of Python code to be included and run, including potentially malicious code. The important point is to scrutinize the Python code in between PYINPUT and PYEND in a deck you receive from other parties. |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"none","size_count":0},"QMOBIL":{"name":"QMOBIL","sections":["GRID"],"supported":false,"summary":"The QMOBIL keyword activates or deactivates the end-point mobility correction for Local Grid Refinements (“LGR”), for when LGRs have been activated for the input deck using the LGR keyword in the RUNSPEC section. QMOBIL should be placed in between the LGR definition keywords CARFIN, or RADIN (or RAFDIN4) and the ENDFIN keyword in the GRID section.","parameters":[{"index":1,"name":"MOBILE_END_POINT_CORRECTION","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"RADFIN":{"name":"RADFIN","sections":["GRID"],"supported":false,"summary":"This keyword defines a radial local grid refinement using one columns Local grid refinement is currently not supported by OPM Flow.","parameters":[{"index":1,"name":"NAME","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"I","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"J","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"K1","description":"","units":{},"default":"","value_type":"INT"},{"index":5,"name":"K2","description":"","units":{},"default":"","value_type":"INT"},{"index":6,"name":"NR","description":"","units":{},"default":"","value_type":"INT"},{"index":7,"name":"NTHETA","description":"","units":{},"default":"","value_type":"INT"},{"index":8,"name":"NZ","description":"","units":{},"default":"","value_type":"INT"},{"index":9,"name":"NWMAX","description":"","units":{},"default":"1","value_type":"INT"},{"index":10,"name":"INNER_RADIUS","description":"Default value is 0.5 ft (= 6 in)","units":{},"default":"0.1524","value_type":"DOUBLE","dimension":"Length"},{"index":11,"name":"OUTER_RADIUS","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":12,"name":"MINIMUM_RADIUS_REFINEMENT","description":"Default value is 5 ft","units":{},"default":"1.524","value_type":"DOUBLE","dimension":"Length"},{"index":13,"name":"PARENT_LGR","description":"","units":{},"default":"GLOBAL","value_type":"STRING"}],"example":"","expected_columns":13,"size_kind":"fixed","size_count":1},"RADFIN4":{"name":"RADFIN4","sections":["SPECIAL","GRID"],"supported":false,"summary":"This keyword defines a radial local grid refinement using four columns. Local grid refinement is currently not supported by OPM Flow.","parameters":[{"index":1,"name":"NAME","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"I1","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"I2","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"J1","description":"","units":{},"default":"","value_type":"INT"},{"index":5,"name":"J2","description":"","units":{},"default":"","value_type":"INT"},{"index":6,"name":"K1","description":"","units":{},"default":"","value_type":"INT"},{"index":7,"name":"K2","description":"","units":{},"default":"","value_type":"INT"},{"index":8,"name":"NR","description":"","units":{},"default":"","value_type":"INT"},{"index":9,"name":"NTHETA","description":"","units":{},"default":"","value_type":"INT"},{"index":10,"name":"NZ","description":"","units":{},"default":"","value_type":"INT"},{"index":11,"name":"NWMAX","description":"","units":{},"default":"1","value_type":"INT"}],"example":"","expected_columns":11,"size_kind":"fixed","size_count":1},"REFINE":{"name":"REFINE","sections":["GRID","EDIT","PROPS","REGIONS","SOLUTION","SCHEDULE"],"supported":false,"summary":"The REFINE keyword defines the start of a Cartesian or radial Local Grid Refinement (“LGR”) definition that sets the properties of the selected LGR. The keyword is then followed by the property keywords associated with the section where the keyword is being invoked. For example, if the REFINE keyword is used in the GRID section then most of the keywords in that section can be used to set the grid properties for the LGR.","parameters":[{"index":1,"name":"LGR","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"RESVNUM":{"name":"RESVNUM","sections":["GRID"],"supported":true,"summary":"The RESVNUM keyword is used to define the start of a reservoir coordinate data set and stipulates the reservoir number for the data set. The keyword is used in conjunction with the COORD keyword in the GRID section, that specifies a set of coordinate lines or pillars for a reservoir grid via an array. Note that the COORD keyword should immediately follow the RESVNUM keyword.","parameters":[{"index":1,"name":"RESVNUM","description":"A positive integer values that defines the reservoir coordinate data set, or the independent reservoir, for which the subsequent COORD data is to be associated with. RESVNUM should be less than or equal to NUMRES on the NUMRES keyword in the RUNSPEC section. OPM Flow currently only accepts a single data set, that is the default value of one.","units":{},"default":"1","value_type":"INT"}],"example":"--\n-- NUMRES\n-- NUMBER\nRESVNUM\n1 /\n--\n-- SPECIFY VERTICAL COORDINATE LINES FOR A REGULAR 3 x 2 GRID\n--(DX = 100 and DY = 200)\n--\n-- X1 Y1 Z1 X2 Y2 Z2\n-- --- --- ---- --- --- ----\nCOORD\n0 0 1000 0 0 5000\n100 0 1000 100 0 5000\n200 0 1000 200 0 5000\n300 0 1000 300 0 5000\n0 200 1000 0 200 5000\n100 200 1000 100 200 5000\n200 200 1000 200 200 5000\n300 200 1000 300 200 5000\n0 400 1000 0 400 5000\n100 400 1000 100 400 5000\n200 400 1000 200 400 5000\n300 400 1000 300 400 5000\n/\n--\n-- NUMRES\n-- NUMBER\nRESVNUM\n2 /\n--\n-- SPECIFY VERTICAL COORDINATE LINES FOR A REGULAR 3 x 2 GRID\n--(DX = 100 and DY = 200)\n--\n-- X1 Y1 Z1 X2 Y2 Z2\n-- --- --- ---- --- --- ----\nCOORD\n0 0 1000 0 0 5000\n100 0 1000 100 0 5000\n200 0 1000 200 0 5000\n300 0 1000 300 0 5000\n0 200 1000 0 200 5000\n100 200 1000 100 200 5000\n200 200 1000 200 200 5000\n300 200 1000 300 200 5000\n0 400 1000 0 400 5000\n100 400 1000 100 400 5000\n200 400 1000 200 400 5000\n300 400 1000 300 400 5000\n/","expected_columns":1,"size_kind":"fixed","size_count":1},"ROCKFRAC":{"name":"ROCKFRAC","sections":["GRID"],"supported":false,"summary":"ROCKFRAC defines the rock volume to bulk volume fraction for all the cells, The keyword can be used with all grid types. Rock volume of a grid block is calculated by multiply a cell’s bulk volume by it’s ROCKFRAC volume. A cell’s rock volume is used in the Coal option to calculate the adsorbed gas in the rock (coal), as well as the Thermal and Temp options to calculate the energy is stored in the rock.","parameters":[{"index":1,"name":"ROCKFRAC","description":"ROCKFRAC is an array of real numbers greater than or equal to zero and less than or equal to one, that are assigned the rock volume to bulk volume fraction values for each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 200*0.850.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- DEFINE GRID ROCKFRAC DATA FOR ALL CELLS (BASED ON NX x NY x NZ = 300)\n--\nROCKFRAC\n100*1.000 100*0.850 100*0.500 /\nThe above example defines a constant ROCKFRAC of 1.00 for the first 100 cells, then 0.85 for the second 100 hundred cells, and finally 0.500 for the last 100 cell, for the 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"RPTGRID":{"name":"RPTGRID","sections":["GRID"],"supported":false,"summary":"This keyword defines the data in the GRID section that is to be printed to the output print file in human readable format. The keyword has two distinct forms, the first of which consists of the keyword followed by a series of integers on the next line indicating the data to be printed (see the first example). This is the original formal in the commercial simulator and was subsequently superseded by the second format. The second format consists of the keyword followed by a series of character strings that indicate the data to be printed. In most cases the character string is the keyword used to load the data in the OPM Flow input deck, for example PORO for the porosity array. Its is anticipated that OPM Flow will eventually support the functionality of the second format only, the first format although recognized will be completely ignored.","parameters":[{"index":1,"name":"ALLNCC","description":"Print all the non-neighbor connections.","units":{},"default":"N/A","value_type":"STRING"},{"index":2,"name":"COORD","description":"Print the coordinate lines.","units":{},"default":"N/A"},{"index":3,"name":"COORDYS","description":"Print the coordinate systems.","units":{},"default":"N/A"},{"index":4,"name":"DEPTH","description":"Print grid cells center depths.","units":{},"default":"N/A"}],"example":"The first example shows the original format of this keyword; although the keyword and format are recognized by OPM Flow, the format is ignored and is unlikely to be implemented in in the simulator.\n--\n-- DEFINE GRID SECTION REPORT OPTION (ORIGINAL FORMAT)\n–\nRPTGRID\n1 2*0 1 3*1 /\nThe next example shows the second format of the keyword which may be supported in a future release of OPM Flow.\n-- DEFINE GRID SECTION REPORT OPTIONS\n--\nRPTGRID\nDX DY DZ DEPTH PORO PERMX /\n| Note This keyword has the potential to produce very large print files that some text editors may have difficulty loading, coupled with the fact that reviewing the data in this format is very cumbersome. A more efficient solution is to load the *.INIT file into OPM ResInsight to view the data graphically, this also has the benefit of being able to filter the grid based on I, J, K ranges and grid properties. |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"fixed","size_count":1,"variadic_record":true},"RPTGRIDL":{"name":"RPTGRIDL","sections":["GRID"],"supported":false,"summary":"This keyword defines the data in the GRID section that is to be printed to the output print file in human readable format for Local Grid Refinements (“LGRs”), for when LGRs have been activated for the input deck using the LGR keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"ALLNCC","description":"Print all the non-neighbor connections.","units":{},"default":"N/A","value_type":"STRING"},{"index":2,"name":"COORD","description":"Print the coordinate lines.","units":{},"default":"N/A"},{"index":3,"name":"COORDYS","description":"Print the coordinate systems.","units":{},"default":"N/A"},{"index":4,"name":"DEPTH","description":"Print grid cells center depths.","units":{},"default":"N/A"},{"index":24,"name":"ALLNNC","description":"ALLNNC is a defined positive integer that specifies the type of Non-Neighbor Connections (“NNC”) to be printed, and should be set to one of the follow: To print the NNCs within the LGRs, and the connections between the local and host cells to the print file (*.PRT). To print the NNCs within the LGRs, and the connections between the local and host cells to the print (*.PRT) and debug files (*.DBG). Same as (2) but the data in the debug file (*.DBG) is written out in an alternative format.","units":{},"default":"N/A"},{"index":57,"name":"EXTHOST","description":"EXTHOSTS outputs host cells for Perpendicular Bisector (“PEBI”)124\n Heinemann, Z.E. and Brand, C.W. 1988. Gridding Techniques in Reservoir Simulation. Proc., First Intl. Forum on Reservoir Simulation, Alpbach, Austria, 339. and 125\n Heinemann, Z.E., Brand, C.W., Munka, M. et al. 1991. Modeling Reservoir Geometry With Irregular Grids. SPE Res Eng 6 (2): 225–232. SPE-18412-PA. http://dx.doi.org/10.2118/18412-PALGRs. Heinemann, Z.E. and Brand, C.W. 1988. Gridding Techniques in Reservoir Simulation. Proc., First Intl. Forum on Reservoir Simulation, Alpbach, Austria, 339. Heinemann, Z.E., Brand, C.W., Munka, M. et al. 1991. Modeling Reservoir Geometry With Irregular Grids. SPE Res Eng 6 (2): 225–232. SPE-18412-PA. http://dx.doi.org/10.2118/18412-PA","units":{},"default":""}],"example":"The first example shows the original format of this keyword; although the keyword and format are recognized by OPM Flow, the format is ignored and is unlikely to be implemented in in the simulator.\n--\n-- DEFINE LGR GRID SECTION REPORT OPTION (ORIGINAL FORMAT)\n–\nRPTGRIDL\n1 2*0 1 3*1 /\nThe next example shows the second format of the keyword which may be supported in a future release of OPM Flow.\n-- DEFINE LGR GRID SECTION REPORT OPTIONS\n--\nRPTGRIDL\nDX DY DZ DEPTH PORO PERMX /\n| Note This keyword has the potential to produce very large print files that some text editors may have difficulty loading, coupled with the fact that reviewing the data in this format is very cumbersome. A more efficient solution is to load the *.INIT file into OPM ResInsight to view the data graphically, this also has the benefit of being able to filter the grid based on I, J, K ranges and grid properties. |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"fixed","size_count":1,"variadic_record":true},"RPTINIT":{"name":"RPTINIT","sections":["GRID"],"supported":false,"summary":"This keyword defines the data in the GRID and EDIT sections that is to be written out to the INIT file (*.INIT or *.FINIT). The format consists of the keyword followed by a series of character strings that indicate the data to be written. In most cases the character string is the keyword used to load the data into the OPM Flow input deck, for example PORO for the porosity array in the GRID section. In addition, values either read or calculated by the simulator in the EDIT section can also be written to the INIT file. Again the keyword or property name is used as the mnemonic for the character string, for example the PORV, TRANX keywords etc. If the RPTINIT keyword is not used in the input deck then a default set of data array are written to the file, in this case the actual data written is dependent on the model’s configuration and the options being used.","parameters":[{"index":1,"name":"MNEMONICS_LIST","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","size_kind":"fixed","size_count":1,"variadic_record":true},"RPTISOL":{"name":"RPTISOL","sections":["GRID"],"supported":false,"summary":"The RPTISOL keyword activates the isolated reservoir report that generates an array of isolated region numbers that is printed in the debug file (*.DBG). The main purpose of this facility is to use the generated array as input to the ISOLNUM keyword in the GRID section in conjunction with the Independent Reservoir Regions option. If the model can be divided into isolated reservoirs then the individual reservoirs may be solved independently, resulting in increased computational efficient, compared with solving the model as a whole.","parameters":[],"example":"--\n-- ACTIVATE ISOLATED RESERVOIR NUMBER REPORTING\n--\nRPTISOL\nThe above example activates the isolated reservoir report that generates an array of isolated region numbers to the debug file (*.DBG).","size_kind":"none","size_count":0},"SIGMA":{"name":"SIGMA","sections":["GRID"],"supported":false,"summary":"The SIGMA keyword defines the dual porosity matrix to fracture transmissibility multiplier, sigma, that is applied to all cells, for when the Dual Porosity model has been activated by either the DUALPORO or the DUALPERM keywords in the RUNSPEC section. Sigma (σ) takes into account the matrix-fracture interface area per unit volume and was defined by Kazemi et al126\n Kazemi, H., Merrill JR., L. S., Porterfield, K. L., and Zeman, P. R. “Numerical Simulation of Water-Oil Flow in Naturally Fractured Reservoirs,” paper SPE 5719, Society of Petroleum Engineers Journal (1976) 16, No. 6, 317-326. to be:","parameters":[{"index":1,"name":"COUPLING","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1/Length*Length"}],"example":"| [%sigma `=` 4left(1 over {l sub x} sup 2` + 1 over {l sub y} sup 2`+ 1 over {l sub z} sup 2` right)] | (6.15) |\n|------------------------------------------------------------------------------------------------------|--------|","expected_columns":1,"size_kind":"fixed","size_count":1},"SIGMAGD":{"name":"SIGMAGD","sections":["GRID"],"supported":false,"summary":"The SIGMAGD keyword defines the dual porosity matrix to fracture transmissibility multiplier, sigma, that is applied to all cells, for when the Dual Porosity model has been activated by either the DUALPORO or the DUALPERM keywords in the RUNSPEC section. In addition, the GRAVDR keyword in the RUNSPEC section should be used to enable the Gravity Drainage model for the run. Sigma (σ) takes into account the matrix-fracture interface area per unit volume and was defined by Kazemi et al127\n Kazemi, H., Merrill JR., L. S., Porterfield, K. L., and Zeman, P. R. “Numerical Simulation of Water-Oil Flow in Naturally Fractured Reservoirs,” paper SPE 5719, Society of Petroleum Engineers Journal (1976) 16, No. 6, 317-326. to be:","parameters":[{"index":1,"name":"COUPLING","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1/Length*Length"}],"example":"| [%sigma `=` 4left(1 over {l sub x} sup 2` + 1 over {l sub y} sup 2`+ 1 over {l sub z} sup 2` right)] | (6.16) |\n|------------------------------------------------------------------------------------------------------|--------|","expected_columns":1,"size_kind":"list"},"SIGMAGDV":{"name":"SIGMAGDV","sections":["GRID"],"supported":false,"summary":"The SIGMAGD keyword defines the dual porosity matrix to fracture transmissibility multiplier, sigma, that is applied to individual cells, for when the Dual Porosity model has been activated by either the DUALPORO or the DUALPERM keywords in the RUNSPEC section. In addition, the GRAVDR keyword in the RUNSPEC section should be used to enable the Gravity Drainage model for the run. Sigma (σ) takes into account the matrix-fracture interface area per unit volume and was defined by Kazemi et al128\n Kazemi, H., Merrill JR., L. S., Porterfield, K. L., and Zeman, P. R. “Numerical Simulation of Water-Oil Flow in Naturally Fractured Reservoirs,” paper SPE 5719, Society of Petroleum Engineers Journal (1976) 16, No. 6, 317-326. to be:","parameters":[],"example":"| [%sigma `=` 4left(1 over {l sub x} sup 2` + 1 over {l sub y} sup 2`+ 1 over {l sub z} sup 2` right)] | (6.17) |\n|------------------------------------------------------------------------------------------------------|--------|","size_kind":"array"},"SIGMAV":{"name":"SIGMAV","sections":["GRID"],"supported":false,"summary":"The SIGMAV keyword defines a dual porosity matrix to fracture multiplier, sigma, that is applied to individual cells, for when the Dual Porosity model has been invoked by either the DUALPORO or the DUALPERM keywords in the RUNSPEC section. Sigma (σ) takes into account the matrix-fracture interface area per unit volume and was defined by Kazemi et al129\n Kazemi, H., Merrill JR., L. S., Porterfield, K. L., and Zeman, P. R. “Numerical Simulation of Water-Oil Flow in Naturally Fractured Reservoirs,” paper SPE 5719, Society of Petroleum Engineers Journal (1976) 16, No. 6, 317-326. to be:","parameters":[],"example":"| [%sigma `=` 4left(1 over {l sub x} sup 2` + 1 over {l sub y} sup 2`+ 1 over {l sub z} sup 2` right)] | (6.18) |\n|------------------------------------------------------------------------------------------------------|--------|","size_kind":"array"},"SMULTX":{"name":"SMULTX","sections":["GRID"],"supported":false,"summary":"SMULTX multiples the transmissibility between two cell faces in the +X direction between cells in a host base grid and the connecting auto-refined grid cells, via an array, that is the keyword sets the transmissibility multiplier of block (Ihost, Jhost, Khost) in the host base grid, multiplies the transmissibility all the cells (Iauto, Jauto, Kauto) and (I+Iauto, Jauto, Kauto) in the auto-refinement grid. The Auto Refinement option must be enabled to use this keyword via the AUTOREF keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"SMULTX+","description":"SMULTX+ is an array of real positive numbers assigning the transmissibility multipliers in the +X direction to each cell face in the model. Repeat counts may be used, for example 20*100.0.","units":{},"default":"1.0"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n10 10 1 6 1 3 / DEFINE BOX AREA\n--\n-- SET SMULTX+ TRANSMISSIBILITY MULTIPLIERS\n--\nSMULTX\n18*0.300 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe above example defines a 0.3 scaling multiplier for the 18 cells defined by the preceding BOX statement. The ENDBOX keyword resets the input box to the full grid.","size_kind":"array"},"SMULTY":{"name":"SMULTY","sections":["GRID"],"supported":false,"summary":"SMULTY multiples the transmissibility between two cell faces in the +Y direction between cells in a host base grid and the connecting auto-refined grid cells, via an array, that is the keyword sets the transmissibility multiplier of block (Ihost, Jhost, Khost) in the host base grid, multiplies the transmissibility all the cells (Iauto, Jauto, Kauto) and (Iauto, J+1auto, Kauto) in the auto-refinement grid. The Auto Refinement option must be enabled to use this keyword via the AUTOREF keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"SMULTY+","description":"SMULTY+ is an array of real positive numbers assigning the transmissibility multipliers in the +X direction to each cell face in the model. Repeat counts may be used, for example 20*100.0.","units":{},"default":"1.0"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n10 10 1 6 1 3 / DEFINE BOX AREA\n--\n-- SET SMULTY+ TRANSMISSIBILITY MULTIPLIERS\n--\nSMULTY\n18*0.300 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe above example defines a 0.3 scaling multiplier for the 18 cells defined by the preceding BOX statement. The ENDBOX keyword resets the input box to the full grid.","size_kind":"array"},"SMULTZ":{"name":"SMULTZ","sections":["GRID"],"supported":false,"summary":"SMULTZ multiples the transmissibility between two cell faces in the +Z direction between cells in a host base grid and the connecting auto-refined grid cells, via an array, that is the keyword sets the transmissibility multiplier of block (Ihost, Jhost, Khost) in the host base grid, multiplies the transmissibility all the cells (Iauto, Jauto, Kauto) and (Iauto, Jauto, K+1auto) in the auto-refinement grid. The Auto Refinement option must be enabled to use this keyword via the AUTOREF keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"SMULTZ+","description":"SMULTZ+ is an array of real positive numbers assigning the transmissibility multipliers in the +X direction to each cell face in the model. Repeat counts may be used, for example 20*100.0.","units":{},"default":"1.0"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n10 10 1 6 1 3 / DEFINE BOX AREA\n--\n-- SET SMULTZ+ TRANSMISSIBILITY MULTIPLIERS\n--\nSMULTZ\n18*0.300 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe above example defines a 0.3 scaling multiplier for the 18 cells defined by the preceding BOX statement. The ENDBOX keyword resets the input box to the full grid.","size_kind":"array"},"SOLVDIRS":{"name":"SOLVDIRS","sections":["GRID"],"supported":false,"summary":"The SOLVDIRS keyword defines the linear solver principal directions, which should be set to XY, XZ, YX, YZ, ZX, or ZY. The default direction is based on the direction of the highest transmissibility and SOLVDIRS allows for over writing the default direction for when linear convergence of the equations are problematic.","parameters":[{"index":1,"name":"DIRECTION","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"SOLVNUM":{"name":"SOLVNUM","sections":["GRID"],"supported":false,"summary":"The SOLVNUM defines the unstructured Perpendicular Bisector (“PEBI”)130\n Heinemann, Z.E. and Brand, C.W. 1988. Gridding Techniques in Reservoir Simulation. Proc., First Intl. Forum on Reservoir Simulation, Alpbach, Austria, 339. and 131\n Heinemann, Z.E., Brand, C.W., Munka, M. et al. 1991. Modeling Reservoir Geometry With Irregular Grids. SPE Res Eng 6 (2): 225–232. SPE-18412-PA. http://dx.doi.org/10.2118/18412-PAgrid correspondence to the nested factorization solver order, for when the grid has been entered as a PEBI list. This keyword is generated by an external pre-processing program for generating simulation grids.","parameters":[],"example":"","size_kind":"array"},"SPECGRID":{"name":"SPECGRID","sections":["GRID"],"supported":true,"summary":"SPECGRID defines the dimensions of corner-point and radial grids in the x, y, and z directions as well as the number of reservoirs, where each reservoir has its own set of corner-point geometry data.","parameters":[{"index":1,"name":"NDIVIX","description":"A positive integer value that defines the number of cells in the X or R direction","units":{},"default":"1","value_type":"INT"},{"index":2,"name":"NDIVIY","description":"A positive integer value that defines the number of cells in the Y or THETA direction","units":{},"default":"1","value_type":"INT"},{"index":3,"name":"NDIVZ","description":"A positive integer value that defines the number of cells in the Z direction","units":{},"default":"1","value_type":"INT"},{"index":4,"name":"NUMRES","description":"A positive integer values that defines number of coordinate data sets, or independent reservoirs in the model. OPM Flow currently only accepts a single data set, that is the default value of one.","units":{},"default":"1","value_type":"INT"},{"index":5,"name":"TYPE","description":"A character string set to either T of F that defines the type of grid to be defined by subsequent keywords: T = Radial grid with radial coordinates F = Cartesian grid Only the default option F is supported by OPM Flow.","units":{},"default":"F","value_type":"STRING"}],"example":"--\n-- MAX MAX MAX MAX GRID\n-- NDIVIX NDIVIY NDIVIZ NUMRES TYPE\nSPECGRID\n46 112 22 1 F /\nThe above example defines a 46 x 112 x 22 grid with one set of irregular corner-point data.","expected_columns":5,"size_kind":"fixed","size_count":1},"THCGAS":{"name":"THCGAS","sections":["GRID"],"supported":false,"summary":"The THCGAS keyword defines the gas phase thermal conductivity for when the thermal calculation is activated by the THERMAL keyword in the RUNSPEC section, and should be used in conjunction with THCROCK keyword in the GRID section.","parameters":[{"index":1,"name":"THCGAS","description":"THCGAS is an array of real positive numbers that define the thermal conductivity of the gas phase in each grid block. Repeat counts may be used, for example 3000*20.0","units":{"field":"Btu/ft/day/°R","metric":"kJ/m/day/K","laboratory":"J/cm/hr/K"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK GAS PHASE THERMAL CONDUCTIVITY\n– FOR ALL CELLS (BASED ON NX x NY x NZ = 300)\n--\nTHCGAS\n300*20.0 /\nThe above example defines the gas phase thermal conductivity of 20.0 for each cell in the 300 grid block model as defined by the DIMENS keyword in the RUNSPEC section.\n| [\"Average Thermal Conductivity\"= {PORO times left( THCOIL + THCGAS+THCWATER+THCSOLID right )} over {\" NUMBER OF PHASES IN THE MODEL\"} times\nLEFT(1 - PORO RIGHT ) times THCROCK] | (6.19) |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|","size_kind":"array"},"THCOIL":{"name":"THCOIL","sections":["GRID"],"supported":false,"summary":"The THCOIL keyword defines the oil phase thermal conductivity for when the thermal calculation is activated by the THERMAL keyword in the RUNSPEC section, and should be used in conjunction with THCROCK keyword in the GRID section.","parameters":[{"index":1,"name":"THCOIL","description":"THCOIL is an array of real positive numbers that define the thermal conductivity of the oil phase in each grid block. Repeat counts may be used, for example 3000*20.0","units":{"field":"Btu/ft/day/°R","metric":"kJ/m/day/K","laboratory":"J/cm/hr/K"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK OIL PHASE THERMAL CONDUCTIVITY\n– FOR ALL CELLS (BASED ON NX x NY x NZ = 300)\n--\nTHCOIL\n300*20.0 /\nThe above example defines the oil phase thermal conductivity of 20.0 for each cell in the 300 grid block model, as defined by the DIMENS keyword in the RUNSPEC section.\n| [\"Average Thermal Conductivity\"= PORO times left( THCOIL + THCGAS+THCWATER+THCSOLID right ) over \" NUMBER OF PHASES IN THE MODEL\" times\nLEFT(1 -\" PORO\" RIGHT ) times \"THCROCK\"] | (6.20) |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|","size_kind":"array"},"THCONR":{"name":"THCONR","sections":["GRID"],"supported":null,"summary":"The THCONR keyword defines the reservoir rock plus fluid thermal conductivity for all cells for when the thermal calculation is activated by the THERMAL keywords in the RUNSPEC section.","parameters":[{"index":1,"name":"THCONR","description":"THCONR is an array of real positive numbers that define the combined rock and fluid conductivity of a grid block. Repeat counts may be used, for example 3000*25.0","units":{"field":"Btu/ft/day/°R","metric":"kJ/m/day/K","laboratory":"J/cm/hr/K"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK ROCK-FLUID THERMAL CONDUCTIVITY\n– FOR ALL CELLS (BASED ON NX x NY x NZ = 300)\n--\nTHCONR\n300*25.0 /\nThe above example defines the combined rock and fluid thermal conductivity of 25.0 for each cell in the 300 grid block model, as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"THCONSF":{"name":"THCONSF","sections":["GRID"],"supported":false,"summary":"The THCONSF keyword defines a gas saturation dependent scaling factor to the fluid and reservoir rock thermal conductivities entered via the THCONR keyword in the GRID section, for when the thermal calculation is activated by the THERMAL keyword in the RUNSPEC.","parameters":[{"index":1,"name":"THCONSF","description":"THCONSF is an array of real positive numbers, greater than zero and less than or equal to one, that define the gas saturation dependent scaling factor that is applied to the THCONR data, entered via the THCONR keyword, to adjust the thermal conductivity of the reservoir cells in each grid block. Repeat counts may be used, for example 3000*0.15","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- DEFINE GRID SGAS DEPENDENT SCALING FACTOR FOR THE THCONR ARRAY -- FOR ALL CELLS (BASED ON NX x NY x NZ = 300)\n-- (OPM FLOW THERMAL OPTION ONLY)\n--\nTHCONSF\n300*0.12 /\nThe above example defines the gas saturation thermal conductivity scaling factor to be applied to the THCONR to be 0.12 for all 300 cells in the model, as defined by the DIMENS keyword in the RUNSPEC section.\n| [%OMEGA sub{ i,j,k}`` =`` left(1 - \"THCONSF x Gas Saturation\" right ) sub{ i,j,k}] | (6.21) |\n|------------------------------------------------------------------------------------|--------|","size_kind":"array"},"THCROCK":{"name":"THCROCK","sections":["GRID"],"supported":false,"summary":"The THCROCK keyword defines the reservoir rock thermal conductivity for when the thermal calculation is activated by the THERMAL keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"THCROCK","description":"THCROCK is an array of real positive numbers that define the thermal conductivity of the reservoir rock in each grid block. Repeat counts may be used, for example 3000*20.0","units":{"field":"Btu/ft/day/°R","metric":"kJ/m/day/K","laboratory":"J/cm/hr/K"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK RESERVOIR ROCK THERMAL CONDUCTIVITY\n– FOR ALL CELLS (BASED ON NX x NY x NZ = 300)\n--\nTHCROCK\n300*20.0 /\nThe above example defines the reservoir rock thermal conductivity of 20.0 for each cell in the 300 grid block model, as defined by the DIMENS keyword in the RUNSPEC section.\n| [\"Average Thermal Conductivity\"= PORO times left( THCOIL + THCGAS+THCWATER+THCSOLID right ) over \" NUMBER OF PHASES IN THE MODEL\" times\nLEFT(1 - PORO RIGHT ) times THCROCK] | (6.22) |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|","size_kind":"array"},"THCWATER":{"name":"THCWATER","sections":["GRID"],"supported":false,"summary":"The THCWATER keyword defines the water phase thermal conductivity for when the thermal calculation is activated by the THERMAL keyword in the RUNSPEC section, and should be used in conjunction with THCROCK keyword in the GRID section.","parameters":[{"index":1,"name":"THCWATER","description":"THCWATER is an array of real positive numbers that define the thermal conductivity of the water phase in each grid block. Repeat counts may be used, for example 3000*20.0","units":{"field":"Btu/ft/day/°R","metric":"kJ/m/day/K","laboratory":"J/cm/hr/K"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK WATER PHASE THERMAL CONDUCTIVITY\n– FOR ALL CELLS (BASED ON NX x NY x NZ = 300)\n--\nTHCWATER\n300*2O.0 /\nThe above example defines the water phase thermal conductivity of 20.0 for each cell in the 300 grid block model, as defined by the DIMENS keyword in the RUNSPEC section.\n| [\"Average Thermal Conductivity\"= PORO times left( THCOIL + THCGAS+THCWATER+THCSOLID right ) over \" NUMBER OF PHASES IN THE MODEL\" times\nLEFT(1 - PORO RIGHT ) times THCROCK] | (6.23) |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|","size_kind":"array"},"THPRESFT":{"name":"THPRESFT","sections":["GRID"],"supported":null,"summary":"The THPRESFT keyword defines a fault threshold pressures that prevents fluid flow from occurring across the fault plane until the threshold pressure is exceeded, for when the threshold pressure option has been activated via the THRPRES variable on the EQLOPTS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"FLTNAME","description":"FLTNAME is a character string enclosed in quotes with a maximum length of eight characters, that defines the name of the fault. FLTNAME must have been previously defined using the FAULTS keyword in the GROD section, otherwise an error will occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"PRESS","description":"PRESS is a single positive real value that defines the threshold pressure for the fault (FLTNAME). If PRESS is defaulted then the simulator will set the threshold pressure to zero, that is the fault is open to flow along the fault plane.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"0","value_type":"DOUBLE","dimension":"Pressure"}],"example":"The example below defines two fault traces, ‘M_WEST’ and ‘BC’ fault having threshold pressures of 1000.0 and 2000 psis respectively.\n--\n-- DEFINE FAULTS IN THE GRID GEOMETRY\n--\n-- FAULT ------------ FAULT TRACE -------------\n-- NAME I1 I2 J1 J2 K1 K2 FACE\nFAULTS\n'M_WEST' 5 5 3 3 1 22 'X' /\n'M_WEST' 5 5 4 4 1 22 'X' /\n'M_WEST' 5 5 5 5 1 22 'X' /\n……………………………………………..\n'BC' 43 43 8 8 1 22 'Y' /\n'BC' 42 42 9 9 1 22 'X' /\n'BC' 44 44 8 8 1 22 'Y' /\n……………………………………………..\n/\n--\n-- DEFINE FAULT THRESHOLD PRESSURES\n--\n-- FAULT THRESHOLD\n-- NAME PRESSURE\nTHPRESFT\n'M_WEST' 1000.0 /\n'BC' 1200.0 /\n/","expected_columns":2,"size_kind":"list"},"TOPS":{"name":"TOPS","sections":["GRID"],"supported":null,"summary":"TOPS defines the depth of the top face of each cell in the model.","parameters":[{"index":1,"name":"TOPS","description":"TOPS is an array of real numbers defining the depth at the top face of each cell in the model. One can either just enter the TOPS for the first layer only based on NX x NY entries and OPM Flow will calculate the remaining TOPS based on either DZ or DZV. Alternatively NX x NY x NZ TOPS may be entered for each cell in the model. See the DIMENS keyword in the RUNSPEC section for the definition of NX, NY and NZ. Repeat counts may be used, for example 10*5201.0.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None"}],"example":"The example below defines the TOPS of the cells for each cell for NX = 5, NY = 5 and NZ = 3 model, as well as the X and Y direction cells sizes.\n--\n-- DEFINE GRID BLOCK TOPS FOR THE TOP LAYER (NX=5, NY=5, and NZ=3)\n--\nTOPS\n25*3100 25*3105 25*3110 / --\n-- DEFINE GRID BLOCK X DIRECTION CELL SIZE (BASED ON NX = 5)\n--\nDXV\n5*100 / --\n-- DEFINE GRID BLOCK X DIRECTION CELL SIZE (BASED ON NY = 5)\n--\nDYV\n5*100 /\nA second example is shown on the following page.\nThis example defines the same grid as before but with the TOPS keyword only defining the top layer and DZV keyword defining the cells thickness.\n--\n-- DEFINE GRID BLOCK TOPS FOR THE TOP LAYER (NX = 5, NY = 5, NZ = 3)\n--\nTOPS\n25*3100 /\n--\n-- DEFINE GRID BLOCK Z DIRECTION CELL SIZE (BASED ON NZ = 3)\n--\nDZV\n3*5.0 /\n--\n-- DEFINE GRID BLOCK X DIRECTION CELL SIZE (BASED ON NX = 5)\n--\nDXV\n5*100 / --\n-- DEFINE GRID BLOCK Y DIRECTION CELL SIZE (BASED ON NY = 5)\n--\nDYV\n5*100 /","size_kind":"array"},"TRANGL":{"name":"TRANGL","sections":["GRID"],"supported":false,"summary":"TRANGL enables Non-Neighbor Connections (“NNC”) between the global cells and the Local Grid Refinement (“LGR”) cells to be manually specified, as oppose to the simulator calculating the transmissibilities. The LGR keyword in the RUNSPEC section should be utilized to define the presence of LGRs in the model and to define various LGR dimension parameters.","parameters":[{"index":1,"name":"I1","description":"A positive integer that defines the LGR grid block in the I-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NX on the CARFIN keyword in the GRID section.","units":{},"default":"None","value_type":"INT"},{"index":2,"name":"J1","description":"A positive integer that defines the LGR grid block in the J-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NY on the CARFIN keyword in the GRID section.","units":{},"default":"None","value_type":"INT"},{"index":3,"name":"K1","description":"A positive integer that defines the LGR grid block in the K-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NZ on the CARFIN keyword in the GRID section.","units":{},"default":"None","value_type":"INT"},{"index":4,"name":"I2","description":"A positive integer that defines the GLOBAL grid block in the I-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NX on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":5,"name":"J2","description":"A positive integer that defines the GLOBAL grid block in the J-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NY on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":6,"name":"K2","description":"A positive integer that defines the GLOBAL grid block in the K-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NZ on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":7,"name":"TRANSNNC","description":"TRANSNNC is a positive real number greater than or equal to zero that defines the transmissibility between the GLOBAL grid block (I1, J1, K1) and the LGR grid block (I2, J2, K2). The default value of zero sets the transmissibility between the two cells to zero.","units":{"field":"cP.rb/day/psia","metric":"cP.rm3/day/bars","laboratory":"cP.rcc/hr/atm"},"default":"0.0","value_type":"DOUBLE","dimension":"Transmissibility"}],"example":"--\n-- MANUALLY DEFINE LGR-GLOBAL GRID NON-NEIGHBOR CONNECTIONS\n--\n-- ----LGR----- ---GLOBAL---- -- TRANSNCC --\n-- I1 J1 K1 I2 J2 K2\nTRANGL\n1 1 1 1 1 2 0.2500 /\n1 1 2 1 1 3 0.2500 /\n1 1 3 1 1 4 0.2500 /\n/\nThe above example defines the transmissibility between LGR cell (1, 1, 1) and global cell (1, 1, 2), LGR cell (1, 1, 2) and global cell (1, 1, 3) and finally between LGR cell (1, 1, 3) and global cell (1, 1, 4) to be 0.2500.","expected_columns":7,"size_kind":"list"},"USEFLUX":{"name":"USEFLUX","sections":["GRID"],"supported":false,"summary":"The USEFLUX keyword activates the Flux Boundary model and defines the name of the FLUX file. Only grid blocks that have been declared by the FLUXREG keyword in the GRID section to be in an active flux region, are active for the run.","parameters":[],"example":"","size_kind":"none","size_count":0},"USENOFLO":{"name":"USENOFLO","sections":["GRID"],"supported":false,"summary":"The USENOFLUX keyword activates the Flux Boundary model without a FLUX file. The USEFLUX keyword should still be in the input deck, but in this case the FLUX filename is ignored. The option is useful when the no-flow boundary condition is a reasonable assumption and avoids the pre-cursor run used to generate the FLUX file via the DUMPFLUX keyword in the GRID section. Only grid blocks that have been declared by the FLUXREG keyword in the GRID section to be in an active flux region, are active for the run.","parameters":[],"example":"--\n-- ACTIVATE FLUX BOUNDARY MODEL WITHOUT A FLUX FILE\n--\nUSEFLUX\n/\nUSENOFLO\nThe above example activates the Flux Boundary model without a FLUX file.","size_kind":"none","size_count":0},"VEDEBUG":{"name":"VEDEBUG","sections":["GRID"],"supported":false,"summary":"This keyword defines the debug Vertical Equilibrium (“VE”) data to be written to the debug file (*.DBG), for when the VE model has been activated by the VE keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"I1","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"I2","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"J1","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"J2","description":"","units":{},"default":"","value_type":"INT"},{"index":5,"name":"K1","description":"","units":{},"default":"","value_type":"INT"},{"index":6,"name":"K2","description":"","units":{},"default":"","value_type":"INT"},{"index":7,"name":"DEBUG_LEVEL","description":"","units":{},"default":"0","value_type":"INT"},{"index":8,"name":"LGR","description":"","units":{},"default":" ","value_type":"STRING"}],"example":"","expected_columns":8,"size_kind":"fixed","size_count":1},"VEFIN":{"name":"VEFIN","sections":["GRID"],"supported":false,"summary":"If the VE keyword in the RUNSPEC section has been used to activate the Vertical Equilibrium (“VE”) model for the global grid, then the VEFIN keyword may used to set various options for the Local Grid Refinements (“LGR”). The LGR keyword in the RUNSPEC section should be activated to indicate the presence of LGRs and the keyword VEFIN should be placed in between the CARFIN and ENDFIN keywords in the GRID section.","parameters":[{"index":1,"name":"VE","description":"","units":{},"default":"NO","value_type":"STRING"},{"index":2,"name":"NVEPT","description":"","units":{},"default":"0","value_type":"INT"}],"example":"","expected_columns":2,"size_kind":"fixed","size_count":1},"ZCORN":{"name":"ZCORN","sections":["GRID"],"supported":null,"summary":"ZCORN defines the depth of each corner point of a grid block on the pillars defining the reservoir grid. A total of 8 x NX x NY x NZ values are needed to fully define all the depths in the model. The depths specifying the top of the first layer are entered first with one point for each pillar for each grid block. The points are entered with the X axis cycling fastest. Next come the depths of the bottom of the first layer. The top of layer two follows etc.","parameters":[{"index":1,"name":"ZCORN","description":"An array of depths with 8 depths for each cell, for a total of 8 x Nx x NY x NZ entries","units":{"field":"feet","metric":"metres","laboratory":"cm"},"default":"None"}],"example":"--\n-- SPECIFY CORNER-POINT DEPTHS FOR A 3 x 2 x 2 GRID,\n-- WITH CONSTANT SLOPE IN THE X AND Y DIRECTIONS\n-- SUCH THAT ALL CORNER POINTS OF NEIGHBOURING BLOCKS ALIGN\nZCORN\n--\n-- top of layer 1\n--\n1450 1500 1500 1550 1550 1600\n1500 1550 1550 1600 1600 1650\n1500 1550 1550 1600 1600 1650\n1550 1600 1600 1650 1650 1700\n--\n-- bottom of layer 1\n--\n1460 1510 1510 1560 1560 1610\n1510 1560 1560 1610 1610 1660\n1510 1560 1560 1610 1610 1660\n1560 1610 1610 1660 1660 1710\n--\n-- top of layer 2\n--\n1460 1510 1510 1560 1560 1610\n1510 1560 1560 1610 1610 1660\n1510 1560 1560 1610 1610 1660\n1560 1610 1610 1660 1660 1710\n--\n-- bottom of layer 2\n--\n1470 1520 1520 1570 1570 1620\n1520 1570 1570 1620 1620 1670\n1520 1570 1570 1620 1620 1670\n1570 1620 1620 1670 1670 1720\n/\nThe above example defines depths of the vertical coordinate lines for a regular 3 by 2 by 2 grid with a constant slope in the x and y directions such that all the corner points of neighboring blocks are aligned.","size_kind":"array"},"DEPTH":{"name":"DEPTH","sections":["EDIT"],"supported":null,"summary":"The DEPTH keywords modifies the depth at the center of selected cells in the model. The cells DEPTH are calculated by OPM Flow at the end of the GRID section and this keyword allows the user to adjust the calculated depths in the EDIT section. The area to be modified can be defined via the various grid selection keywords, ADD, BOX, EQUALS, etc., and areas that are not selected remain unchanged.","parameters":[{"index":1,"name":"DEPTH","description":"DEPTH is an array of real numbers defining the depth at the center of each cell in the model. Only the values in the currently defined input BOX needed be entered. Repeat counts may be used, for example 30*5201.0.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None"}],"example":"The example below modifies the DEPTH of the cells for a selection of 10 cells from an NX = 10, NY = 11 and NZ = 20 model.\n--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1 10 11 11 20 20 / SET BOX AREA TO BE MODIFIED\n/\n--\n-- SET GRID BLOCK CENTER DEPTH FOR THE GRID BLOCKS\n--\nDEPTH 10*3500.0 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nAlternatively the EQUALS keyword can be used to perform the same edit.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nDEPTH 3500.0 1 10 11 11 20 20 / RESET DEPTH\n/","size_kind":"array"},"DIFFR":{"name":"DIFFR","sections":["EDIT"],"supported":false,"summary":"The DIFFR keyword defines the radial direction diffusivity values for cells in the current input box for when the Diffusivity option has been activated by the DIFFUSE keyword in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"DIFFTHT":{"name":"DIFFTHT","sections":["EDIT"],"supported":false,"summary":"The DIFFTHT keyword defines the theta direction diffusivity values for cells in the current input box for when the Diffusivity option has been activated by the DIFFUSE keyword in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"DIFFX":{"name":"DIFFX","sections":["EDIT"],"supported":false,"summary":"The DIFFX keyword defines the x-direction diffusivity values for cells in the current input box for when the Diffusivity option has been activated by the DIFFUSE keyword in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"DIFFY":{"name":"DIFFY","sections":["EDIT"],"supported":false,"summary":"The DIFFY keyword defines they y-direction diffusivity values for cells in the current input box for when the Diffusivity option has been activated by the DIFFUSE keyword in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"DIFFZ":{"name":"DIFFZ","sections":["EDIT"],"supported":false,"summary":"The DIFFZ keyword defines the z-direction diffusivity values for cells in the current input box for when the Diffusivity option has been activated by the DIFFUSE keyword in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"EDIT":{"name":"EDIT","sections":["EDIT"],"supported":null,"summary":"The EDIT activation keyword marks the end of the GRID section and the start of the EDIT section that enables modifications to the OPM Flow calculated properties derived from the data entered in the GRID section, for example grid block pore volumes via the PORV array and the transmissibilities via the TRANX, TRANY and TRANZ family of keywords.","parameters":[],"example":"-- ==============================================================================\n--\n-- EDIT SECTION\n--\n-- ==============================================================================\nEDIT\nThe above example marks the end of the GRID section and the start of the EDIT section in the OPM Flow data input file.","size_kind":"none","size_count":0},"EDITNNC":{"name":"EDITNNC","sections":["EDIT"],"supported":false,"summary":"EDITNNC enables Non-Neighbor Connections (“NNC”), entered via the NNC keyword or calculated by the simulator, to be multiplied (re-scaled) by a constant. For example, if the existing transmissibility between non-neighbor connections is Told and the multiplier is C, then the resulting transmissibility, Tnew, will be [T sub{new}~= C ``x ``T sub{old}]. . Only previously defined NNC’s entered via the NNC keyword or calculated by the simulator can be edited, otherwise a warning message will be printed.","parameters":[{"index":1,"name":"I1","description":"A positive integer that defines the first grid block in the I-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NX on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":2,"name":"J1","description":"A positive integer that defines the first grid block in the J-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NY on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":3,"name":"K1","description":"A positive integer that defines the first grid block in the K-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NZ on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":4,"name":"I2","description":"A positive integer that defines the second grid block in the I-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NX on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":5,"name":"J2","description":"A positive integer that defines the second grid block in the J-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NY on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":6,"name":"K2","description":"A positive integer that defines the second grid block in the K-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NZ on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":7,"name":"TRANSMUL","description":"TRANSMUL is a positive real number greater than or equal to zero that defines a constant that scales the transmissibility between the first grid block (I1, J1, K1) and the second grid block (I2, J2, K2). The default value of one means no scaling will be applied.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1","value_type":"DOUBLE"},{"index":8,"name":"ISATNUM1","description":"The default value of zero means the existing saturation table allocated to the upstream cell (I1,J1,K1).","units":{},"default":"0","value_type":"INT"},{"index":9,"name":"ISATNUM2","description":"ISATNUM2 is a positive integer defining which saturation table number (relative permeability table) to be used for flow from the second grid block to the first grid block. The default value of zero means the existing saturation table allocated to the downstream cell (I2,J2,K2).","units":{},"default":"0","value_type":"INT"},{"index":10,"name":"IPRSNUM1","description":"IPRSNUM1 is a positive integer defining which pressure table number (PVT table) to be used for flow from the first grid block to the second grid block. The default value of zero means the existing PVT table allocated to the upstream cell (I1,J1,K1).","units":{},"default":"0","value_type":"INT"},{"index":11,"name":"IPRSNUM2","description":"IPRSNUM2 is a positive integer defining which pressure table number (PVT table) to be used for flow from the second grid block to the first grid block. The default value of zero means the existing PVT table allocated to the downstream cell (I2,J2,K2).","units":{},"default":"0","value_type":"INT"},{"index":12,"name":"FACE1","description":"FACE1 is a character string that defines the face associated with flow from the first grid block to the second grid block, where FACE1 can have values of: X+, X-, Y+, Y-, Z+, or Z-. FACE1 is used with the commercial simulator’s Vertical Equilibrium option which is not supported by OPM Flow.","units":{},"default":"None","value_type":"STRING"},{"index":13,"name":"FACE2","description":"FACE2 is a character string that defines the face associated with flow from the second grid block to the first grid block, where FACE2 can have values of: X+, X-, Y+, Y-, Z+, or Z-. FACE2 is used with the commercial simulator’s Vertical Equilibrium option which is not supported by OPM Flow.","units":{},"default":"None","value_type":"STRING"},{"index":14,"name":"DIFFNNC","description":"DIFFNNC is a positive real number greater than or equal to zero that scales the diffusivity between the first grid block (I1, J1, K1) and the second grid block (I2, J2, K2).","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.0","value_type":"DOUBLE"}],"example":"--\n-- MANUALLY RESCALE NON-NEIGHBOR CONNECTIONS\n--\n-- ------------ BOX ----------- -- TRANSMUL --\n-- I1 J1 K1 I2 J2 K2\nEDITNCC\n1 1 1 1 1 2 0.2000 / SET NNC FOR FAULT\n1 1 2 1 1 3 0.2000 / SET NNC FOR FAULT\n1 1 3 1 1 4 0.2000 / SET NNC FOR FAULT\n/\nThe above example multiplies the transmissibility between cells (1, 1, 1) and (1, 1, 2), (1, 1, 2) and (1, 1, 3) and finally between (1, 1, 3) and (1, 1, 4) by 0.200.","expected_columns":14,"size_kind":"list"},"EDITNNCR":{"name":"EDITNNCR","sections":["EDIT"],"supported":null,"summary":"EDITNNCR enables Non-Neighbor Connections (“NNC”), entered via the NNC keyword or calculated by the simulator, to be reset to a user defined value. Only previously defined NNC’s entered via the NNC keyword or calculated by the simulator can be edited, otherwise a warning message will be printed. See also the EDITNNC keyword in the EDIT section that scales an existing NNC.","parameters":[{"index":1,"name":"I1","description":"A positive integer that defines the first grid block in the I-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NX on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":2,"name":"J1","description":"A positive integer that defines the first grid block in the J-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NY on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":3,"name":"K1","description":"A positive integer that defines the first grid block in the K-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NZ on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":4,"name":"I2","description":"A positive integer that defines the second grid block in the I-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NX on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":5,"name":"J2","description":"A positive integer that defines the second grid block in the J-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NY on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":6,"name":"K2","description":"A positive integer that defines the second grid block in the K-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NZ on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":7,"name":"TRANSNNC","description":"TRANSNNC is a positive real number greater than or equal to zero that defines the transmissibility between the first grid block (I1, J1, K1) and the second grid block (I2, J2, K2). This value cannot be defaulted and must be defined.","units":{"field":"cP.rb/day/psia","metric":"cP.rm3/day/bars","laboratory":"cP.rcc/hr/atm"},"default":"None","value_type":"DOUBLE","dimension":"Transmissibility"},{"index":8,"name":"ISATNUM1","description":"ISATNUM1 is a positive integer defining which saturation table number (relative permeability table) to be used for flow from the first grid block to the second grid block. The default value of zero means the existing saturation table allocated to the upstream cell (I1,J1,K1).","units":{},"default":"0","value_type":"INT"},{"index":9,"name":"ISATNUM2","description":"ISATNUM2 is a positive integer defining which saturation table number (relative permeability table) to be used for flow from the second grid block to the first grid block. The default value of zero means the existing saturation table allocated to the downstream cell (I2,J2,K2).","units":{},"default":"0","value_type":"INT"},{"index":10,"name":"IPRSNUM1","description":"IPRSNUM1 is a positive integer defining which pressure table number (PVT table) to be used for flow from the first grid block to the second grid block. The default value of zero means the existing PVT table allocated to the upstream cell (I1,J1,K1).","units":{},"default":"0","value_type":"INT"},{"index":11,"name":"IPRSNUM2","description":"IPRSNUM2 is a positive integer defining which pressure table number (PVT table) to be used for flow from the second grid block to the first grid block. The default value of zero means the existing PVT table allocated to the downstream cell (I2,J2,K2).","units":{},"default":"0","value_type":"INT"},{"index":12,"name":"FACE1","description":"FACE1 is a character string that defines the face associated with flow from the first grid block to the second grid block, where FACE1 can have vales of: X+, X-, Y+, Y-, Z+, or Z-.","units":{},"default":"None","value_type":"STRING"},{"index":13,"name":"FACE2","description":"FACE2 is a character string that defines the face associated with flow from the second grid block to the first grid block, where FACE2 can have vales of: X+, X-, Y+, Y-, Z+, or Z-.","units":{},"default":"None","value_type":"STRING"},{"index":14,"name":"DIFFNNC","description":"DIFFNNC is a positive real number greater than or equal to zero that scales the diffusivity between the first grid block (I1, J1, K1) and the second grid block (I2, J2, K2). The default value is the value calculated in the GRID section.","units":{"field":"feet","metric":"meters","laboratory":"cm"},"default":"1*","value_type":"DOUBLE","dimension":"Length"}],"example":"--\n-- MANUALLY RESET NON-NEIGHBOR CONNECTIONS\n--\n-- ------------ BOX ----------- -- TRANSNNC --\n-- I1 J1 K1 I2 J2 K2\nEDITNCCR\n1 1 1 1 1 2 0.2500 / RESET NNC TRANS FOR FAULT\n1 1 2 1 1 3 0.2500 / RESET NNC TRANS FAULT\n1 1 3 1 1 4 0.2500 / RESET NNC TRANS FAULT\n/\nThe above example res-sets the transmissibility between cells (1, 1, 1) and (1, 1, 2), (1, 1, 2) and (1, 1, 3) and (1, 1, 3) and (1, 1, 4) to be 0.2500.","expected_columns":14,"size_kind":"list"},"HMMULT":{"name":"HMMULT","sections":["EDIT"],"supported":false,"summary":"The HMMULT series of keywords defines the history match gradient cumulative permeability multipliers, for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section. The keyword consists of the first six characters of “HMMULT” followed by a one or two character string shown in Table 7.5, that determines the transmissibility direction, for example, HMMULTX.","parameters":[],"example":"| Mnemonic | Cartesian Grid | Radial Grid | | |\n|--------------|----------------|--------------|----------------|----------|\n| Grid Keyword | HMMULT Keyword | Grid Keyword | HMMULT Keyword | |\n| X/R | MULTX | HMMULTX | MULTR | HMMULTR |\n| XY | | HMMULTXY | | |\n| Y/HT | MULTY | hMMULTY | MULTTHT | HMMULTTH |\n| z | MULTZ | HMMULTZ | MULTZ | HMMULTZ |\n| PV | MULTPV | HMMULTPV | MULTPV | HMMULTPV |"},"PORV":{"name":"PORV","sections":["EDIT"],"supported":null,"summary":"PORV defines the pore volumes for all the cells in the model via an array. The keyword can be used for all grid types, except for the Radial Grid geometry. The keyword effectively overwrites previously entered and calculated data. The area to be modified can be defined via the various grid selection keywords, ADD, BOX, EQUALS, etc., and areas that are not selected remain unchanged.","parameters":[{"index":1,"name":"PORV","description":"PORV is an array of real positive numbers assigning a pore volume to each cell in the model. Only the values in the currently defined input BOX needed be entered. Repeat counts may be used, for example 20*100.0.","units":{"field":"rb","metric":"rm3","laboratory":"rcc"},"default":"None"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1* 100 1* 100 20 20 / DEFINE BOX AREA\n--\n-- SET PORV FOR THE GRID BLOCKS\n--\nPORV\n1000*0.00 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nHere the BOX statement is used to define the input grid for the PORV keyword, which overwrites the pore volume previously calculated with pore volume values of zero, resulting in a no-flow boundary in that part of the field between layers 19 and 21, since layer 20 is deactivated. The ENDBOX keyword resets the input box to the full grid.","size_kind":"array"},"TRANR":{"name":"TRANR","sections":["EDIT"],"supported":false,"summary":"TRANR defines the transmissibility in the +R direction for all the cells in the model via an array. The keyword can only be used with Radial Grid geometry grids. The keyword effectively overwrites previously entered and calculated data. The transmissibility overwritten is the +R face transmissibility of each grid block, that is for cell (I, J, K) the transmissibility between cells (I, J, K) and (I+1, J, K).","parameters":[{"index":1,"name":"TRANR","description":"TRANR is an array of real positive numbers assigning the transmissibility in the R direction to each cell in the model. Repeat counts may be used, for example 20*100.0.","units":{"field":"cP.rb/day/psia","metric":"cP.rm3/day/bars","laboratory":"cP.rcc/hr/atm"},"default":"None"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1 1 10 10 1 120 / DEFINE BOX AREA\n--\n-- SET TRANR+ TRANSMISSIBILITY\n--\nTRANR\n120*0.00 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nHere the BOX statement is used to define the input grid for the TRANR keyword, which overwrites the transmissibility previously calculated with transmissibility values of zero, resulting in a no-flow boundary in that part of the grid. The ENDBOX keyword resets the input box to the full grid.","size_kind":"array"},"TRANTHT":{"name":"TRANTHT","sections":["EDIT"],"supported":false,"summary":"TRANTHT defines the transmissibility in the +Theta direction for all the cells in the model via an array. The keyword can only be used with Radial Grid geometry grids. The keyword effectively overwrites previously entered and calculated data. The transmissibility overwritten is the +Theta face transmissibility of each grid block, that is for cell (I, J, K) the transmissibility between cells (I, J, K) and (I, J+1, K).","parameters":[{"index":1,"name":"TRANTHT","description":"TRANTHT is an array of real positive numbers assigning the transmissibility in the +Theta direction to each cell in the model. Repeat counts may be used, for example 20*100.0.","units":{"field":"cP.rb/day/psia","metric":"cP.rm3/day/bars","laboratory":"cP.rcc/hr/atm"},"default":"None"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n10 10 1 6 1 3 / DEFINE BOX AREA\n--\n-- SET TRANTHT TRANSMISSIBILITY\n--\nTRANTHT\n18*0.00 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nHere the BOX statement is used to define the input grid for the TRANTHT keyword, which overwrites the transmissibility previously calculated with transmissibility values of zero, resulting in a no-flow boundary in that part of the grid. The ENDBOX keyword resets the input box to the full grid.","size_kind":"array"},"TRANX":{"name":"TRANX","sections":["EDIT"],"supported":null,"summary":"TRANX defines the transmissibility in the X direction for all the cells in the model via an array. The keyword can be used for all grid types, except for the Radial Grid geometry. The keyword effectively overwrites previously entered and calculated data. The transmissibility overwritten is the +X face transmissibility of each grid block, that is for cell (I, J, K) the transmissibility between cells (I, J, K) and (I+1, J, K).","parameters":[{"index":1,"name":"TRANX","description":"TRANX is an array of real positive numbers assigning the transmissibility in the X direction to each cell in the model. Repeat counts may be used, for example 20*100.0.","units":{"field":"cP.rb/day/psia","metric":"cP.rm3/day/bars","laboratory":"cP.rcc/hr/atm"},"default":"None"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1 1 10 10 1 120 / DEFINE BOX AREA\n--\n-- SET TRANX+ TRANSMISSIBILITY\n--\nTRANX\n120*0.00 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nHere the BOX statement is used to define the input grid for the TRANX keyword, which overwrites the transmissibility previously calculated with transmissibility values of zero, resulting in a no-flow boundary in that part of the field. The ENDBOX keyword resets the input box to the full grid.","size_kind":"array"},"TRANY":{"name":"TRANY","sections":["EDIT"],"supported":null,"summary":"TRANY defines the transmissibility in the Y direction for all the cells in the model via an array. The keyword can be used for all grid types, except for the Radial Grid geometry. The keyword effectively overwrites previously entered and calculated data. The transmissibility overwritten is the +Y face transmissibility of each grid block, that is for cell (I, J, K) the transmissibility between cells (I, J, K) and (I, J+1, K).","parameters":[{"index":1,"name":"TRANY","description":"TRANY is an array of real positive numbers assigning the transmissibility in the Y direction to each cell in the model. Repeat counts may be used, for example 20*100.0.","units":{"field":"cP.rb/day/psia","metric":"cP.rm3/day/bars","laboratory":"cP.rcc/hr/atm"},"default":"None"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1 1 10 10 1 120 / DEFINE BOX AREA\n--\n-- SET TRANY+ TRANSMISSIBILITY\n--\nTRANY\n120*0.00 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nHere the BOX statement is used to define the input grid for the TRANY keyword, which overwrites the transmissibility previously calculated with transmissibility values of zero, resulting in a no-flow boundary in that part of the field. The ENDBOX keyword resets the input box to the full grid.","size_kind":"array"},"TRANZ":{"name":"TRANZ","sections":["EDIT"],"supported":null,"summary":"TRANX defines the transmissibility in the z direction for all the cells in the model via an array. The keyword can be used for all grid types, except for the Radial Grid geometry. The keyword effectively overwrites previously entered and calculated data. The transmissibility overwritten is the +Z face transmissibility of each grid block, that is for cell (I, J, K) the transmissibility between cells (I, J, K) and (I, J, K+1).","parameters":[{"index":1,"name":"TRANZ","description":"TRANZ is an array of real positive numbers assigning the transmissibility in the Z direction to each cell in the model. Repeat counts may be used, for example 20*100.0.","units":{"field":"cP.rb/day/psia","metric":"cP.rm3/day/bars","laboratory":"cP.rcc/hr/atm"},"default":"None"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1* 100 1* 100 20 20 / DEFINE BOX AREA\n--\n-- SET TRANZ+ TRANSMISSIBILITY\n--\nTRANZ\n1000*0.00 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nHere the BOX statement is used to define the input grid for the TRANZ keyword, which overwrites the transmissibility previously calculated with transmissibility values of zero, resulting in a no-flow boundary in that part of the field between layers 20 and 21. The ENDBOX keyword resets the input box to the full grid.","size_kind":"array"},"ACF":{"name":"ACF","sections":["PROPS"],"supported":false,"summary":"The ACF keyword defines the acentric factors for each of the compositional components active in the model and for each equation of state. The keyword should only be used if the compositional mode has been requested using the COMPS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"ACF","description":"A series of real numbers that define the acentric factors for each of the compositional components active in the model.","units":{},"default":"None","value_type":"DOUBLE","dimension":"1"}],"example":"The following example defines the acentric factors for each component in a single three-component equation of state model.\n--\n-- Acentric Factors\n--\nACF\n0.0108 0.2273 0.3434 /\nThe following example defines the acentric factors for each component in two three-component equation of state models.\n--\n-- Acentric Factors\n--\nACF\n0.0108 0.2273 0.3434 /\n0.0110 0.2281 0.3428 /","size_kind":"fixed","variadic_record":true},"ACTCO2S":{"name":"ACTCO2S","sections":["PROPS"],"supported":null,"summary":"The keyword ACTCO2S specifies the activity model for salting-out effects when calculating mutual solubility in the CO2 storage module which is activated by the CO2STORE keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"ACTMODEL","description":"A positive integer value selecting the activity model for the salting-out effect. The choices are: The Rumpf et al.1\n Rumpf, B.,Nicolaisen, H., Ocal, C., and Maurer, G., 1994. Solubility of carbon dioxide in aqueous solutions of sodium chloride: experimental results and correlation. J. Sol. Chem. 23, 431-448. model as detailed in the paper by Spycher and Pruess2\n Spycher, N., and Pruess, K., 2005. CO2-H2O mixtures in the geological sequestration of CO2. II. Partitioning in chloride brines at 12–100°C and up to 600 bar. Geochimica Et Cosmochimica Acta 69, 3309–3320.. The model was calibrated in the P-T range 5 to 96 bar and 40 to 160°C, and was shown in Spycher and Pruess2 to be accurate in the P-T range 1 to 600 bar and 12 to 100°C. Note that this model requires a (fixed-point) iteration procedure to compute solubility, but usually converges within few iterations. Rumpf, B.,Nicolaisen, H., Ocal, C., and Maurer, G., 1994. Solubility of carbon dioxide in aqueous solutions of sodium chloride: experimental results and correlation. J. Sol. Chem. 23, 431-448. Spycher, N., and Pruess, K., 2005. CO2-H2O mixtures in the geological sequestration of CO2. II. Partitioning in chloride brines at 12–100°C and up to 600 bar. Geochimica Et Cosmochimica Acta 69, 3309–3320. The Duan and Sun3\n Duan Z., and Sun R., 2003. An improved model calculating CO2 solubility in pure water and aqueous NaCl solutions from 257 to 533 K and from 0 to 2000 bar. Chem. Geol. 193, 257–271. model as detailed in the paper by Spycher and Pruess4\n Spycher, N., and Pruess, K., 2009. A Phase-Partitioning Model for CO2–Brine Mixtures at Elevated Temperatures and Pressures: Application to CO2-Enhanced Geothermal Systems. Transp Porous Med 82, 173–196.. The model was recalibrated to the P-T range 1 to 600 bar and 12 to 300°C, and was shown to be accurate within the same range. Note that above 99°C a (fixed-point) iteration procedure is required to compute solubility, while below 99°C the computations are done in a direct manner without needing iterations. Duan Z., and Sun R., 2003. An improved model calculating CO2 solubility in pure water and aqueous NaCl solutions from 257 to 533 K and from 0 to 2000 bar. Chem. Geol. 193, 257–271. Spycher, N., and Pruess, K., 2009. A Phase-Partitioning Model for CO2–Brine Mixtures at Elevated Temperatures and Pressures: Application to CO2-Enhanced Geothermal Systems. Transp Porous Med 82, 173–196. The Duan and Sun3 model as detailed in the paper by Spycher and Pruess2. The model was calibrated to the P-T range 0 to 2000 bar and 0 to 260°C, and was shown in Spycher and Pruess2 to be accurate in the P-T range 1 to 600 bar and 12 to 100°C. Note that no iterations are required to compute the solubility.","units":{},"default":"3","value_type":"INT"}],"example":"The following example activates activity model number 1.\n--\n-- ACTIVITY MODEL FOR SALTING-OUT EFFECTS IN CO2\n--\nACTCO2S\n1 /","expected_columns":1,"size_kind":"fixed","size_count":1},"ADSALNOD":{"name":"ADSALNOD","sections":["PROPS"],"supported":false,"summary":"ADSALNOD defines the salt concentration value based on a cells SATNUM number. The ADSALNOD property is used in the calculation of a polymer viscosity when the polymer and the salt options has been activated by the POLYMER and BRINE keywords in the RUNSPEC section. In the RUNSPEC section the number of SATNUM functions is declared by the NTSFUN variable on the TABDIMS keyword and allocated to individual cells by the SATNUM property array in the REGIONS section. NSSFUN on the TABDIMS keyword in the RUNSPEC section defines the maximum number of rows (or saturation values) in the relative permeability saturation tables and also sets the maximum number of entries for each ADSALNOD data set. The number of values for each data set must correspond to the number of polymer solution adsorption entries on the PLYADSS keyword. For example, if there are three sets of relative permeability tables and four values on the PLYADSS keyword, then three ADSALNOD data sets with four values of salt concentrat...","parameters":[{"index":1,"name":"SALTCON","description":"Field","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"Metric","value_type":"DOUBLE","dimension":"Density"}],"example":"Given three sets of relative permeability tables and four values on the PLYADSS keyword, then the data salt concentration should be entered as follows:\n--\n-- SETS SALT CONCENTRATION FOR POLYMER SOLUTION ADSORPTION\n-- VIA SATNUM ARRAY ALLOCATION\n--\n-- SALT\n--\nADSALNOD\n1.0\n5.0\n10.5\n25.0 / SATNUM TABLE NO. 01\n1.0\n3.0\n7.5\n15.0 / SATNUM TABLE NO. 02\n1.0\n7.5\n20.5\n35.0 / SATNUM TABLE NO. 03\nSee also the SALTNODE keyword.","size_kind":"fixed","variadic_record":true},"ADSORP":{"name":"ADSORP","sections":["PROPS"],"supported":false,"summary":"The ADSORP keyword defines the parameters for the generalized Langmuir Adsorption174\n Langmuir, Irving (June 1918). \"The Adsorption of Gases on Plane Surface of Glass, Mica and Platinum\". The Research Laboratory of the General Electric Company. 40 (9): 1361–1402. doi:10.1021/ja02242a004 function for when the polymer, surfact, alkaline, foam and tracers phases have been activated in the RUNSPEC section by the POLYMER, SURFACT, ALKALINE, FOAM and TRACER keywords.","parameters":[{"index":1,"name":"ADSORBING_COMP","description":"","units":{},"default":"","value_type":"STRING","record":1},{"index":1,"name":"ADORPTION_ISOTHERM","description":"","units":{},"default":"LANGMUIR","value_type":"STRING","record":2},{"index":2,"name":"A1","description":"","units":{},"default":"","value_type":"DOUBLE","record":2},{"index":3,"name":"A2","description":"","units":{},"default":"","value_type":"DOUBLE","record":2},{"index":4,"name":"B","description":"","units":{},"default":"","value_type":"DOUBLE","record":2},{"index":5,"name":"M","description":"","units":{},"default":"0.5","value_type":"DOUBLE","dimension":"1","record":2},{"index":6,"name":"N","description":"","units":{},"default":"0.5","value_type":"DOUBLE","dimension":"1","record":2},{"index":7,"name":"K_REF","description":"","units":{},"default":"","value_type":"DOUBLE","record":2}],"example":"","records_meta":[{"expected_columns":1},{"expected_columns":7}],"size_kind":"list"},"ALKADS":{"name":"ALKADS","sections":["PROPS"],"supported":false,"summary":"ALKADS defines the alkaline adsorption functions for when the alkaline model has been activated via the ALKALINE keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Density","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"ALKROCK":{"name":"ALKROCK","sections":["PROPS"],"supported":false,"summary":"The ALKROCK keyword defines the rock alkaline properties for when the alkaline model has been activated via the ALKALINE keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"ROCK_ADS_INDEX","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":1,"size_kind":"fixed"},"ALPOLADS":{"name":"ALPOLADS","sections":["PROPS"],"supported":false,"summary":"ALPOLDS defines the polymer adsorption versus alkaline concentration multipliers for when the alkaline model has been activated via the ALKALINE keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Density","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"ALSURFAD":{"name":"ALSURFAD","sections":["PROPS"],"supported":false,"summary":"ALSURAD defines the surfactant adsorption versus alkaline concentration multipliers for when the alkaline model has been activated via the ALKALINE keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Density","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"ALSURFST":{"name":"ALSURFST","sections":["PROPS"],"supported":false,"summary":"The ALSURFST keyword defines the water-oil surface tension versus alkaline concentration multipliers for when the alkaline model has been activated via the ALKALINE keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Density","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"APIGROUP":{"name":"APIGROUP","sections":["PROPS"],"supported":false,"summary":"The APIGROUP keyword defines the maximum number of groups of oil PVT tables when the API tracking option has been activated via the API keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"MAX_OIL_PVT_GROUP_COUNT","description":"","units":{},"default":"1","value_type":"INT"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"AQUTAB":{"name":"AQUTAB","sections":["PROPS"],"supported":null,"summary":"The AQUTAB keyword defines additional Carter-Tracy175\n Carter, R. D., and Tracy, G. W. “An Improved Method for Calculating Water Influx.” Transactions of AIME, Vol. 219 (1060), pp 415-417. aquifer functions to be used in the model. Carter-Tracy representation of the aquifer influx is via a qw term in the non-linear aquifer influence function Q(t). It allows the water influx from the aquifer to be represented in the simulator by assuming that there is a constant water influx rate over finite time periods. It is derived from the superposition methods of van Everdingen and Hurst176\n Van Everdingen, A. F., and Hurst, W. “The Application of the Laplace Transform to Flow Problems in Reservoirs.” Transactions of AIME, Vol. 186 (1949), pp. 305-324., whose superposition methods are not suitable for implementation in reservoir simulation software, although they are very useful in interpreting aquifer response. The storage requirements and calculation complexity of handling the resu...","parameters":[{"index":1,"name":"TD","description":"Dimensionless Time","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":["1","1"]},{"index":2,"name":"PD","description":"Dimensionless Pressure","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- CARTER-TRACY AQUIFER INFLUENCE TABLES\n-- (STARTS FROM TABLE NO. 2, AS DEFAULT IS TABLE NO. 1)\n--\nAQUTAB\n--\n-- TD PD\n-- ------- ---------\n0.06 0.251\n0.08 0.288\n0.10 0.322\n0.12 0.355\n0.14 0.387\n0.16 0.420\n0.18 0.452\n0.20 0.484\n0.22 0.516\n0.24 0.548\n0.26 0.580\n0.28 0.612\n0.30 0.644\n0.35 0.724\n0.40 0.804\n0.45 0.884\n0.50 0.964\n0.55 1.044\n0.60 1.124 / RD=1.5 TABLE NO. 02\n--\n-- TD PD\n-- ------- ---------\n0.22 0.443\n0.24 0.459\n0.26 0.476\n0.28 0.492\n0.30 0.507\n0.32 0.522\n0.34 0.536\n0.36 0.551\n0.38 0.565\n0.40 0.579\n0.42 0.593\n0.44 0.607\n0.46 0.621\n0.48 0.634\n0.50 0.648\n0.6 0.715\n0.7 0.782\n0.8 0.849\n0.9 0.915\n1.0 0.982\n2.0 1.649\n3.0 2.316\n5.0 3.649 / RD=2.0 TABLE NO. 03\nThe above example defines tables two and three Carter-Tracy aquifer influence tables.\n| Note OPM Flow includes the infinite acting Carter-Tracy aquifer influence table as a default for table number one; thus data entered on this keyword starts from table number two. |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Carter-Tracy Aquifer Influence Functions | | | | | | | | |\n|------------------------------------------|------------------------|------------------------|------------------------|------------------------|--------|--------|--------|--------|\n| No. | rD = 1.5 Dimensionless | rD = 2.0 Dimensionless | rD = 2.5 Dimensionless | rD = 3.0 Dimensionless | | | | |\n| tD | pD | tD | pD | tD | pD | tD | pD | |\n| 1 | 0.0600 | 0.2510 | 0.2200 | 0.4430 | 0.4000 | 0.5650 | 0.5200 | 0.6270 |\n| 2 | 0.0800 | 0.2880 | 0.2400 | 0.4590 | 0.4200 | 0.5760 | 0.5400 | 0.6360 |\n| 3 | 0.1000 | 0.3220 | 0.2600 | 0.4760 | 0.4400 | 0.5870 | 0.5600 | 0.6450 |\n| 4 | 0.1200 | 0.3550 | 0.2800 | 0.4920 | 0.4600 | 0.5980 | 0.6000 | 0.6620 |\n| 5 | 0.1400 | 0.3870 | 0.3000 | 0.5070 | 0.4800 | 0.6080 | 0.6500 | 0.6830 |\n| 6 | 0.1600 | 0.4200 | 0.3200 | 0.5220 | 0.5000 | 0.6180 | 0.7000 | 0.7030 |\n| 7 | 0.1800 | 0.4520 | 0.3400 | 0.5360 | 0.5200 | 0.6280 | 0.7500 | 0.7210 |\n| 8 | 0.2000 | 0.4840 | 0.3600 | 0.5510 | 0.5400 | 0.6380 | 0.8000 | 0.7400 |\n| 9 | 0.2200 | 0.5160 | 0.3800 | 0.5650 | 0.5600 | 0.6470 | 0.8500 | 0.7580 |\n| 10 | 0.2400 | 0.5480 | 0.4000 | 0.5790 | 0.5800 | 0.6570 | 0.9000 | 0.7760 |\n| 11 | 0.2600 | 0.5800 | 0.4200 | 0.5930 | 0.6000 | 0.6660 | 0.9500 | 0.7910 |\n| 12 | 0.2800 | 0.6120 | 0.4400 | 0.6070 | 0.6500 | 0.688","size_kind":"fixed","variadic_record":true},"BDENSITY":{"name":"BDENSITY","sections":["PROPS"],"supported":false,"summary":"BDENSITY defines the brine surface density for when the brine phase has been activated in the model by the BRINE keyword in the RUNSPEC section. The number of BDENSITY vector data sets is defined by the NTPVT parameter on the TABDIMS keyword in the RUNSPEC section. Each record consists of a maximum of NPPVT values, as declared on the TABDIMS keyword in the RUNSPEC section, with each value representing a brine surface density.","parameters":[{"index":1,"name":"WATDEN","description":"Field","units":{"field":"lb/ft3","metric":"kg/m","laboratory":"gm/cc"},"default":"Metric","value_type":"DOUBLE","dimension":"Density"}],"example":"The following shows the BDENSITY and PVTWSALT keywords for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set equal to two and NPPVT is set to greater than four on the TABDIMS keyword.\n--\n-- BRINE WATER DENSITY DATA FOR PVTWSALT KEYWORD\n--\n-- SALTCON SALTCON SALTCON SALTCON SALTCON -- DENSITY DENSITY DENSITY DENSITY DENSITY\n-- ------- ------- ------- ------- -------\nBDENSITY\n62.20 63.50 64.75 65.90 / FOR PVTWSALT TABLE 1\n64.00 65.50 67.00 / FOR PVTWSALT TABLE 2 --\n-- WATER SALT PVT TABLE\n--\nPVTWSALT\n-- REF PRES REF SALT\n-- PSIA LB/STB\n-- -------- --------\n4500.0 0.000 / TABLE NO. REF. DATA\n--\n-- SALTCONC BW CW VISC VISC\n-- LB/STB RB/STB 1/PSIA CPOISE GRAD\n-- -------- -------- ------- ------ ------\n0.0 1.020 2.7E-6 0.370 0.0\n2.0 1.010 2.7E-6 0.370 0.0\n4.0 1.000 2.7E-6 0.370 0.0\n10.0 0.950 2.7E-6 0.370 0.0 / TABLE NO. 01 SALT DATA\n--\n-- REF PRES REF SALT\n-- PSIA LB/STB\n-- -------- --------\n4000.0 0.000 / TABLE NO. 02 REF. DATA\n--\n-- SALTCONC BW CW VISC VISC\n-- LB/STB RB/STB 1/PSIA CPOISE GRAD\n-- -------- -------- ------- ------ ------\n0.0 1.005 2.5E-6 0.320 0.0\n6.0 0.985 2.5E-6 0.320 0.0\n12.0 0.930 2.5E-6 0.320 0.0 / TABLE NO. 02 SALT DATA\n| Note In OPM Flow the tracer equations are solved decoupled from the reservoir equations at the end of a time step. For each tracer an implicit system is solved, however, the tracer equations are linear, resulting in converge in two iterations. However, the Brine phase is solved fully implicitly and is fully coupled with the other flow equations. This is different to the commercial simulator, where the tracer equations are solved explicitly after the flow equations have converged at the end of a time step. This can lead to numerical instabilities if there are large variations in brine densities. |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"fixed","variadic_record":true},"BGGI":{"name":"BGGI","sections":["PROPS"],"supported":false,"summary":"The BGGI keyword defines Gi gas formation volume factor as a function of Gi and pressure for when the Gi option has been invoked via the GIMODEL keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"GAS_PRESSURE","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":2,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"}],"example":"","size_kind":"fixed","variadic_record":true},"BIC":{"name":"BIC","sections":["PROPS"],"supported":false,"summary":"The BIC keyword defines the binary interaction coefficients for each pair of compositional components active in the model and for each equation of state. The keyword should only be used if the compositional mode has been requested using the COMPS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"BIC","description":"A series of real numbers that define the binary interaction coefficients [k_ij]for each pair (i, j) of compositional components active in the model. The matrix [k_ij]is symmetrical with zeroes on the diagonal so only the portion of the matrix below the diagonal is required (i.e., i = {2, ... COMPS} and j < i), where COMPS is specified by the COMPS keyword in the RUNSPEC section. The values are ordered with j cycling fastest (i.e. [k_21], , [k_31], , [k_32], , [k_41], , [k_42], , [k_43], ...)., ...).","units":{},"default":"0","value_type":"DOUBLE","dimension":"1"}],"example":"The following example defines the binary interaction coefficients for each pair of compositional components in a single three-component equation of state model.\n--\n-- Binary Interaction Coefficients\n--\nBIC\n0.1209\n0.1310 0.0339 /\nThe following example defines the binary interaction coefficients for each component in two three-component equation of state models.\n--\n-- Binary Interaction Coefficients\n--\nBIC\n0.1209\n0.1310 0.0339 /\n0.1209\n0.1310 0.0339 /","size_kind":"fixed","variadic_record":true},"BIOFPARA":{"name":"BIOFPARA","sections":["PROPS"],"supported":null,"summary":"The BIOFPARA keyword defines parameters for models including biofilms. For the parameters, biomass means both suspended microbes in the water phase (labeled as microbial) and biofilm. Currently the two available models with biofilm effects are the BIOFILM and the MICP model. See Landa-Marbán et al198\n Landa-Marbán, D., Tveit, S., Kumar, K., Gasda, S.E., 2021. Practical approaches to study microbially induced calcite precipitation at the field scale. Int. J. Greenh. Gas Control 106, 103256. https://doi.org/10.1016/j.ijggc.2021.103256. and 199\n Landa-Marbán, D., Kumar, K., Tveit, S., Gasda, S.E., 2021. Numerical studies of CO2 leakage remediation by micp-based plugging technology. In: Røkke, N.A. and Knuutila, H.K. (Eds) Short Papers from the 11th International Trondheim CCS conference, ISBN: 978-82-536-1714-5, 284-290.for further information on the MICP model parameters, which are also used in the BIOFILM model.","parameters":[{"index":1,"name":"DENSBIOF","description":"A real positive value that defines the density of the biofilm.","units":{"field":"lb/rft3","metric":"kg/rm3","laboratory":"gm/rcc"},"default":"None","value_type":"DOUBLE","dimension":["Density","1/Time","1/Time","Concentration","1","1","1/Time","1/Time","1","1/Time","Concentration","Density","1"]},{"index":2,"name":"DEATRATE","description":"A real value that defines the biomass death rate.","units":{"field":"1/days","metric":"1/days","laboratory":"1/hours"},"default":"None"},{"index":3,"name":"GROWRATE","description":"A real positive value that defines the maximum specific biomass growth rate.","units":{"field":"1/days","metric":"1/days","laboratory":"1/hours"},"default":"None"},{"index":4,"name":"HALFGROW","description":"A real positive value that defines the half-velocity coefficient in the Monod equation for the biomass growth rate.","units":{"field":"lb/rft3","metric":"kg/rm3","laboratory":"gm/rcc"},"default":"None"},{"index":5,"name":"YIELGROW","description":"A real value that defines the yield biomass growth coefficient.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":6,"name":"OXYGSUBS","description":"A real value that defines the mass ratio of oxygen consumed to substrate used for biomass growth.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":7,"name":"ATTARATE","description":"A real positive value that defines the microbial attachment rate.","units":{"field":"1/days","metric":"1/days","laboratory":"1/hours"},"default":"None"},{"index":8,"name":"DETARATE","description":"A real positive value that defines the biofilm detachment rate.","units":{"field":"1/days","metric":"1/days","laboratory":"1/hours"},"default":"None"},{"index":9,"name":"DETAEXPO","description":"A real value that defines the exponent in the norm for the water velocity in the detachment term (this value was set to 0.58 in the MICP publication).","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":10,"name":"UREARATE","description":"A real positive value that defines the maximum rate of urea utilization.","units":{"field":"1/days","metric":"1/days","laboratory":"1/hours"},"default":"None"},{"index":11,"name":"HALFUREA","description":"A real positive value that defines the half-velocity coefficient in the Monod equation for the urea utilization rate.","units":{"field":"lb/rft3","metric":"kg/rm3","laboratory":"gm/rcc"},"default":"None"},{"index":12,"name":"DENSCALC","description":"A real positive value that defines the calcite density.","units":{"field":"lb/rft3","metric":"kg/rm3","laboratory":"gm/rcc"},"default":"None"},{"index":13,"name":"YIELURCA","description":"A real value that defines the yield coefficient in the calcite precipitation term (units of produced calcite over units of urea utilization).","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"The example below is based on metric units, with NTSFUN equal to two on the TABDIMS keyword.\n--\n-- DEFINE BIOMASS PARAMETERS FOR THE MICP MODEL\n--\n-- DENS DEAT GROW HALF YIEL OXYG\n-- BIOF RATE RATE GROW GROW SUBS\n-- ------ ------ ------ ------ ------ ------ ------\n-- ATTA DETA DETA UREA HALF DENS YIEL\n-- RATE RATE EXPO RATE UREA CALC URCA\n-- ------ ------ ------ ------ ------ ------ ------\nBIOFPARA\n35 0.0275 3.6 2E-05 0.5 0.5\n0.0735 2.6E-13 0.58 1391 21.3 2710 1.67 /\n10 0.0275 3.6 2E-05 0.5 0.5\n0.0735 1.1E-05 0.58 1391 21.3 2710 1.67 /\n| Note This is an OPM Flow specific keyword. |\n|--------------------------------------------|","size_kind":"fixed","variadic_record":true},"BOGI":{"name":"BOGI","sections":["PROPS"],"supported":false,"summary":"The BOGI keyword defines Gi oil formation volume factor as a function of Gi and pressure for when the Gi option has been invoked via the GIMODEL keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"OIL_PRESSURE","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":2,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"}],"example":"","size_kind":"fixed","variadic_record":true},"CNAMES":{"name":"CNAMES","sections":["PROPS"],"supported":true,"summary":"The CNAMES keyword defines the names for each of the compositional components active in the model. The keyword should only be used if the compositional mode has been requested using the COMPS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"CNAMES","description":"A series of character strings of up to eight characters in length that define the names for each of the compositional components active in the model.","units":{},"default":"None"}],"example":"The following example defines how to confirm a three component formulation, together with defining the names of the compositional components, to be used with the CO2STORE and GASWAT options.\n--\n-- CONFIRM NUMBER OF COMPOSITIONAL COMPONENTS (OPM FLOW KEYWORD)\n--\nNCOMPS\n3 /\n--\n-- DEFINE COMPOSITIONAL COMPONENTS NAMES (OPM FLOW KEYWORD)\n--\nCNAMES\n'H2O'\n'CO2'\n'NACL' /\n| Note This keyword is only supported by OPM Flow when the two phase gas-water CO2 storage model has been activated using the CO2STORE keyword and either the GASWAT or the GAS and WATER keywords in the RUNSPEC section. Only the component names \"H2O\", \"CO2\" and \"NACL\" (water, CO2 and salt respectively) are recognized when the CNAMES keyword is used with the CO2STORE keyword; any other component names are ignored. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"array"},"COALADS":{"name":"COALADS","sections":["PROPS"],"supported":false,"summary":"The COALADS keyword defines the gas and solvent relative adsorption tables for when the coal phase has been activated via the COAL keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["1","1","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"COALPP":{"name":"COALPP","sections":["PROPS"],"supported":false,"summary":"The COALPP keyword defines the gas and solvent partial pressure adsorption tables for when the coal phase has been activated via the COAL keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["1","1","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"DENAQA":{"name":"DENAQA","sections":["PROPS"],"supported":true,"summary":"The DENAQA keyword specifies the three Ezrokhi coefficients for each compositional component and for each equation of state that are used to calculate the aqueous phase density. The keyword should only be used if the compositional mode has been requested using the COMPS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"COEFFS","description":"A series of real numbers that define the three Ezrokhi coeffients for each of the compositional components active in the model.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":"1"}],"example":"The following example defines the Ezrokhi coefficients for each component in a single three-component equation of state model.\n--\n-- Ezrokhi Coefficients for Aqueous Density Calculation\n--\nDENAQA\n--COEFF0 COEFF1 COEFF2\n2.0E-6 -5.0E-7 2.0E-9\n2.0E-6 -5.0E-7 2.0E-9\n2.0E-6 -5.0E-7 2.0E-9 /\nThe following example defines the Ezrokhi coefficients for each component in two three-component equation of state models.\n--\n-- Ezrokhi Coefficients for Aqueous Density Calculation\n--\nDENAQA\n--COEFF0 COEFF1 COEFF2\n2.0E-6 -5.0E-7 2.0E-9\n2.0E-6 -5.0E-7 2.0E-9\n2.0E-6 -5.0E-7 2.0E-9 /\n--\n2.0E-6 -5.0E-7 2.0E-9\n2.0E-6 -5.0E-7 2.0E-9\n2.0E-6 -5.0E-7 2.0E-9 /","size_kind":"fixed","variadic_record":true},"DENSITY":{"name":"DENSITY","sections":["PROPS"],"supported":null,"summary":"DENSITY defines the oil, water and gas surface densities for the fluids for various regions in the model. The number of DENSITY vector data sets is defined by the NTPVT parameter on the TABDIMS keyword in the RUNSPEC section and the allocation of the DENSITY data sets to different grid blocks in the model is done via the PVTNUM keyword in the REGIONS section. One data set consists of one record or line which is terminated by a “/”. The surface density or gravity must be entered using either the DENSITY or GRAVITY keywords irrespective of which phases are active in the model.","parameters":[{"index":1,"name":"OILDEN","description":"OILDEN is a real number defining the density of the oil phase at surface conditions.","units":{"field":"lb/ft3 37.457","metric":"kg/m3 600","laboratory":"gm/cc 0.6"},"default":"Defined","value_type":"DOUBLE","dimension":"Density"},{"index":2,"name":"WATDEN","description":"WATDEN is a real number defining the density of the water phase at surface conditions.","units":{"field":"lb/ft3 62.366","metric":"kg/m3 999.014","laboratory":"gm/cc 0.999014"},"default":"Defined","value_type":"DOUBLE","dimension":"Density"},{"index":3,"name":"GASDEN","description":"GASDEN is a real number defining the density of the gas phase at surface conditions.","units":{"field":"lb/ft3 0.062428","metric":"kg/m3 1.000","laboratory":"gm/cc 0.001"},"default":"Defined","value_type":"DOUBLE","dimension":"Density"}],"example":"The following shows the DENSITY keyword for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set to one.\n--\n-- OIL WAT GAS\n-- DENSITY DENSITY DENSITY\n-- ------- ------- -------\nDENSITY\n39.0 62.37 0.04520 / PVT DATA REGION 1\nThe next example shows the DENSITY keyword for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set to three.\n--\n-- OIL WAT GAS\n-- DENSITY DENSITY DENSITY\n-- ------- ------- -------\nDENSITY\n38.0 62.30 0.04500 / PVT DATA REGION 1\n39.0 62.37 0.04520 / PVT DATA REGION 2\n40.0 62.40 0.04800 / PVT DATA REGION 3\nThe third, and final, example shows the DENSITY keyword for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set to four. Here table two defaults to table one, and table four defaults to table three.\n--\n-- OIL WAT GAS\n-- DENSITY DENSITY DENSITY\n-- ------- ------- -------\nDENSITY\n38.0 62.30 0.04500 / PVT DATA REGION 1\n/ PVT DATA REGION 2\n39.0 62.37 0.04520 / PVT DATA REGION 3\n/ PVT DATA REGION 3\nAgain, note that there is no terminating “/” for this keyword.","expected_columns":3,"size_kind":"fixed"},"DEPTHTAB":{"name":"DEPTHTAB","sections":["PROPS"],"supported":false,"summary":"This keyword, DEPTHTAB, defines the river time and depth tables, for when the River option has been activated via the RIVRDIMS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","size_kind":"fixed","variadic_record":true},"DIAGDISP":{"name":"DIAGDISP","sections":["PROPS"],"supported":false,"summary":"This keyword, DIAGDISP, activates the alternate form of tracer dispersion matrix for when the Tracer facility has been activated by the TRACERS keyword in the RUNSPEC section.","parameters":[],"example":"","size_kind":"none","size_count":0},"DIFFAGAS":{"name":"DIFFAGAS","sections":["PROPS"],"supported":null,"summary":"The DIFFAGAS keyword defines the gas diffusion coefficients assuming a mass fraction formulation for each compositional component in the model and for each PVT region, for when the Molecular Diffusion option has been activated by the DIFFUSE keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"CO2DIFF","description":"A real positive number that declares the CO2 or H2 in gas diffusion coefficient in the given PVT region.","units":{"field":"ft2/day","metric":"m2/day","laboratory":"cm2/hour"},"default":"None","value_type":"DOUBLE","dimension":"Length*Length/Time"},{"index":2,"name":"WATDIFF","description":"A real positive number that specifies the water in gas diffusion coefficient in the given PVT region.","units":{"field":"ft2/day","metric":"m2/day","laboratory":"cm2/hour"},"default":"None","value_type":"DOUBLE","dimension":"Length*Length/Time"}],"example":"The example below is based on field units, with NTPVT equal to three on the TABDIMS keyword.\n--\n-- PVT REGION GAS COMPONENT DIFFUSION COEFFICIENTS (OPM FLOW KEYWORD)\n--\nDIFFAGAS\n-- CO2 IN WAT IN\n-- GAS DF GAS DF\n-- ------- -------\n0.160 0.150 / PVT REGION NO. 01\n0.165 0.155 / PVT REGION NO. 02\n/ PVT REGION NO. 03\nHere the third PVT region has no values for the two component diffusion coefficients, and therefore the simulator will use correlations to define the diffusivity coefficients for this PVT region.\n| Note This is an OPM Flow keyword used with OPM Flow’s CO2STORE or H2STORE and GASWAT keywords in the RUNSPEC section, and should not be confused with the version of the DIFFAGAS keyword used in the commercial compositional simulator that defines activity corrected diffusion coefficients. |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Note The option has been tested in combination with the CO2STORE keyword, but not for the general case at this point. |\n|-----------------------------------------------------------------------------------------------------------------------|\n| Diffusivity Conversion Factors | | |\n|--------------------------------|-------------------|-----------------|\n| Laboratory Measured Units | Conversion Factor | Simulator Units |\n| 1 cm2/s | 92.9979 ft2/day | Field |\n| 8.64 m2/day | Metric | |\n| 3600 cm2/hour | Laboratory | |","expected_columns":2,"size_kind":"fixed"},"DIFFAWAT":{"name":"DIFFAWAT","sections":["PROPS"],"supported":null,"summary":"The DIFFAWAT keyword defines the water diffusion coefficients assuming a mass fraction formulation for each compositional component in the model and for each PVT region, for when the Molecular Diffusion option has been activated by the DIFFUSE keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"CO2DIFF","description":"A real positive number that declares the CO2 or H2 in water diffusion coefficient in the given PVT region.","units":{"field":"ft2/day","metric":"m2/day","laboratory":"cm2/hour"},"default":"None","value_type":"DOUBLE","dimension":"Length*Length/Time"},{"index":2,"name":"WATDIFF","description":"A real positive number that specifies the water in water diffusion coefficient in the given PVT region.","units":{"field":"ft2/day","metric":"m2/day","laboratory":"cm2/hour"},"default":"None","value_type":"DOUBLE","dimension":"Length*Length/Time"}],"example":"The example below is based on field units, with NTPVT equal to three on the TABDIMS keyword.\n--\n-- PVT REGION WATER COMPONENT DIFFUSION COEFFICIENTS (OPM FLOW KEYWORD)\n--\nDIFFAWAT\n-- CO2 IN WAT IN\n-- WAT DF WAT DF\n-- ------- -------\n0.160 0.150 / PVT REGION NO. 01\n0.165 0.155 / PVT REGION NO. 02\n/ PVT REGION NO. 03\nHere the third PVT region has no values for the two component diffusion coefficients, and therefore the simulator will use correlations to define the diffusivity coefficients for this PVT region.\n| Note This is an OPM Flow specific keyword used with OPM Flow’s CO2STORE or H2STORE and GASWAT keywords in the RUNSPEC section. |\n|--------------------------------------------------------------------------------------------------------------------------------|\n| Note The option has been tested in combination with the CO2STORE keyword, but not for the general case at this point. |\n|-----------------------------------------------------------------------------------------------------------------------|\n| Diffusivity Conversion Factors | | |\n|--------------------------------|-------------------|-----------------|\n| Laboratory Measured Units | Conversion Factor | Simulator Units |\n| 1 cm2/s | 92.9979 ft2/day | Field |\n| 8.64 m2/day | Metric | |\n| 3600 cm2/hour | Laboratory | |","expected_columns":2,"size_kind":"fixed"},"DIFFC":{"name":"DIFFC","sections":["PROPS"],"supported":null,"summary":"The DIFFC keyword defines the molecular weight of the fluids and diffusion coefficients between phases for each PVT region, for when the Molecular Diffusion option has been activated by the DIFFUSE keyword in the RUNSPEC section. This keyword is optional as OPM Flow will automatically calculate the coefficients, as described by Sandve et al.182\n Tor Harald Sandve1, Sarah E. Gasda, Atgeirr Rasmussen, and Alf Birger Rustad. Convective dissolution in field scale CO2 storage simulation using the OPM Flow simulator. Submitted to TCCS 11 – Trondheim Conference on CO2 Capture, Transport and Storage Trondheim, Norway – June 21-23, 2021., if the DIFFC keyword is absent from the input deck. The keyword thus allows one to overwrite the automatically calculated values.","parameters":[{"index":1,"name":"OILMW","description":"OILMW is a real positive number that specifies the molecular weight of the oil in the given PVT region.","units":{"field":"lb/lb-M","metric":"kg/kg-M","laboratory":"gm/gm-M"},"default":"None","value_type":"DOUBLE","dimension":"1"},{"index":2,"name":"GASMW","description":"GASMW is a real positive number that defines the molecular weight of the gas in the given PVT region.","units":{"field":"lb/lb-M","metric":"kg/kg-M","laboratory":"gm/gm-M"},"default":"None","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"GASGASDF","description":"A real positive number that defines the gas in gas diffusion coefficient in the given PVT region.","units":{"field":"ft2/day","metric":"m2/day","laboratory":"cm2/hour"},"default":"None","value_type":"DOUBLE","dimension":"Length*Length/Time"},{"index":4,"name":"OILGASDF","description":"A real positive number that declares the oil in gas diffusion coefficient in the given PVT region.","units":{"field":"ft2/day","metric":"m2/day","laboratory":"cm2/hour"},"default":"None","value_type":"DOUBLE","dimension":"Length*Length/Time"},{"index":5,"name":"GASOILDF","description":"A real positive number that specifies the gas in oil diffusion coefficient in the given PVT region.","units":{"field":"ft2/day","metric":"m2/day","laboratory":"cm2/hour"},"default":"None","value_type":"DOUBLE","dimension":"Length*Length/Time"},{"index":6,"name":"OILOILDF","description":"A real positive number that defines the oil in oil diffusion coefficient in the given PVT region.","units":{"field":"ft2/day","metric":"m2/day","laboratory":"cm2/hour"},"default":"None","value_type":"DOUBLE","dimension":"Length*Length/Time"},{"index":7,"name":"GASOILCD","description":"A real positive number that defines the gas in oil cross phase diffusion coefficient in the given PVT region. This parameter is ignored by OPM Flow and should be defaulted or set equal to zero.","units":{"field":"ft2/day","metric":"m2/day","laboratory":"cm2/hour"},"default":"0.0","value_type":"DOUBLE","dimension":"Length*Length/Time"},{"index":8,"name":"OILOILCD","description":"A real positive number that defines the oil in oil cross phase diffusion coefficient in the given PVT region. This parameter is ignored by OPM Flow and should be defaulted or set equal to zero.","units":{"field":"ft2/day","metric":"m2/day","laboratory":"cm2/hour"},"default":"0.0","value_type":"DOUBLE","dimension":"Length*Length/Time"}],"example":"The example below is based on field units, with NTPVT equal to three on the TABDIMS keyword.\n--\n-- PVT REGION MOLECULAR DIFFUSION TABLES\n--\nDIFFC\n-- OIL GAS GAS IN OIL IN GAS IN OIL IN GAS IN OIL IN\n-- MW MW GAS DF GAS DF OIL DF OIL DF OIL CD OIL CD\n-- ------ ----- ------- ------- ------- ------- ------- ------\n103.20 1.120 1.35E-6 1.05E-7 4.50E-7 1.05E-8 /TAB-1\n102.00 1.130 1.25E-6 1.25E-7 4.80E-7 1.05E-8 /TAB-2\n100.00 1.250 1.22E-6 /TAB-3\nHere the third PVT region has no values for the various oil related diffusion coefficients.\n| Note The option has been tested in combination with the CO2STORE keyword, but not for the general case at this point. |\n|-----------------------------------------------------------------------------------------------------------------------|","expected_columns":8,"size_kind":"fixed"},"DIFFCGAS":{"name":"DIFFCGAS","sections":["PROPS"],"supported":null,"summary":"The DIFFCGAS keyword defines the gas diffusion coefficients assuming the standard mole fraction formulation for each compositional component in the model and for each PVT region, for when the Molecular Diffusion option has been activated by the DIFFUSE keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"CO2DIFF","description":"A real positive number that declares the CO2 or H2 in gas diffusion coefficient in the given PVT region.","units":{"field":"ft2/day","metric":"m2/day","laboratory":"cm2/hour"},"default":"None","value_type":"DOUBLE","dimension":"Length*Length/Time"},{"index":2,"name":"WATDIFF","description":"A real positive number that specifies the water in gas diffusion coefficient in the given PVT region.","units":{"field":"ft2/day","metric":"m2/day","laboratory":"cm2/hour"},"default":"None","value_type":"DOUBLE","dimension":"Length*Length/Time"}],"example":"The example below is based on field units, with NTPVT equal to three on the TABDIMS keyword.\n--\n-- PVT REGION GAS COMPONENT DIFFUSION COEFFICIENTS (OPM FLOW KEYWORD)\n--\nDIFFCGAS\n-- CO2 IN WAT IN\n-- GAS DF GAS DF\n-- ------- -------\n0.160 0.150 / PVT REGION NO. 01\n0.165 0.155 / PVT REGION NO. 02\n/ PVT REGION NO. 03\nHere the third PVT region has no values for the two component diffusion coefficients, and therefore the simulator will use correlations to define the diffusivity coefficients for this PVT region.\n| Note This is an OPM Flow keyword used with OPM Flow’s CO2STORE or H2STORE and GASWAT keywords in the RUNSPEC section, and should not be confused with the more general version of the DIFFCGAS keyword used in the commercial compositional simulator. |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Note The option has been tested in combination with the CO2STORE keyword, but not for the general case at this point. |\n|-----------------------------------------------------------------------------------------------------------------------|\n| Diffusivity Conversion Factors | | |\n|--------------------------------|-------------------|-----------------|\n| Laboratory Measured Units | Conversion Factor | Simulator Units |\n| 1 cm2/s | 92.9979 ft2/day | Field |\n| 8.64 m2/day | Metric | |\n| 3600 cm2/hour | Laboratory | |","expected_columns":2,"size_kind":"fixed"},"DIFFCOAL":{"name":"DIFFCOAL","sections":["PROPS"],"supported":false,"summary":"The DIFF keyword defines the coal bed methane diffusion data for when the Coal Bed Methane option has been activated via the COAL keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"GAS_DIFF_COEFF","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length*Length/Time"},{"index":2,"name":"RE_ADSORB_FRACTION","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"SOL_DIFF_COEFF","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length*Length/Time"}],"example":"","expected_columns":3,"size_kind":"fixed"},"DIFFCWAT":{"name":"DIFFCWAT","sections":["PROPS"],"supported":null,"summary":"The DIFFCWAT keyword defines the water diffusion coefficients assuming the standard mole fraction formulation for each compositional component in the model and for each PVT region, for when the Molecular Diffusion option has been activated by the DIFFUSE keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"CO2DIFF","description":"A real positive number that declares the CO2 or H2 in water diffusion coefficient in the given PVT region.","units":{"field":"ft2/day","metric":"m2/day","laboratory":"cm2/hour"},"default":"None","value_type":"DOUBLE","dimension":"Length*Length/Time"},{"index":2,"name":"WATDIFF","description":"A real positive number that specifies the water in water diffusion coefficient in the given PVT region.","units":{"field":"ft2/day","metric":"m2/day","laboratory":"cm2/hour"},"default":"None","value_type":"DOUBLE","dimension":"Length*Length/Time"}],"example":"The example below is based on field units, with NTPVT equal to three on the TABDIMS keyword.\n--\n-- PVT REGION WATER COMPONENT DIFFUSION COEFFICIENTS (OPM FLOW KEYWORD)\n--\nDIFFCWAT\n-- CO2 IN WAT IN\n-- WAT DF WAT DF\n-- ------- -------\n0.160 0.150 / PVT REGION NO. 01\n0.165 0.155 / PVT REGION NO. 02\n/ PVT REGION NO. 03\nHere the third PVT region has no values for the two component diffusion coefficients, and therefore the simulator will use correlations to define the diffusivity coefficients for this PVT region.\n| Note This is an OPM Flow keyword used with OPM Flow’s CO2STORE or H2STORE and GASWAT keywords in the RUNSPEC section, and should not be confused with the more general version of the DIFFCWAT keyword used in the commercial compositional simulator. |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Note The option has been tested in combination with the CO2STORE keyword, but not for the general case at this point. |\n|-----------------------------------------------------------------------------------------------------------------------|\n| Diffusivity Conversion Factors | | |\n|--------------------------------|-------------------|-----------------|\n| Laboratory Measured Units | Conversion Factor | Simulator Units |\n| 1 cm2/s | 92.9979 ft2/day | Field |\n| 8.64 m2/day | Metric | |\n| 3600 cm2/hour | Laboratory | |","expected_columns":2,"size_kind":"fixed"},"DIFFDP":{"name":"DIFFDP","sections":["PROPS"],"supported":false,"summary":"This keyword, DIFFDP, activates the dual porosity molecular diffusion for matrix-fracture flow only option for when the Dual Porosity option has be activated by either the DUALPORO or DUALPERM keywords, and the Diffusivity option has been activated by the DIFFUSE keywords; three keywords are in the RUNSPEC section.","parameters":[],"example":"","size_kind":"none","size_count":0},"DIFFMICP":{"name":"DIFFMICP","sections":["PROPS"],"supported":null,"summary":"The DIFFMICP keyword defines the diffusion coefficients assuming the mass concentration formulation for each component dissolved in water and for each PVT region, for when the molecular diffusion option has been activated by the DIFFUSE keyword in the RUNSPEC section. The keyword should only be used if either the MICP or BIOFILM model has been activated in the RUNSPEC section.","parameters":[{"index":1,"name":"MICRDIFF","description":"A real positive number that declares the microbial concentration in water diffusion coefficient in the given PVT region.","units":{"field":"ft2/day","metric":"m2/day","laboratory":"cm2/hour"},"default":"None","value_type":"DOUBLE","dimension":["Length*Length/Time","Length*Length/Time","Length*Length/Time"]},{"index":2,"name":"OXYGDIFF","description":"A real positive number that declares the oxygen concentration in water diffusion coefficient in the given PVT region.","units":{"field":"ft2/day","metric":"m2/day","laboratory":"cm2/hour"},"default":"None"},{"index":3,"name":"UREADIFF","description":"A real positive number that declares the urea concentration in water diffusion coefficient in the given PVT region.","units":{"field":"ft2/day","metric":"m2/day","laboratory":"cm2/hour"},"default":"None"}],"example":"The example below is based on metric units, with NTPVT equal to one on the TABDIMS keyword.\n--\n-- PVT REGION MICP COMPONENT DIFFUSION COEFFICIENTS (OPM FLOW KEYWORD)\n--\nDIFFMICP\n-- MICR IN OXYG IN UREA IN\n-- WAT DF WAT DF WAT DF\n-- ------- ------- -------\n2E-04 2E-04 1E-04 / PVT REGION NO. 01\n| Note This is an OPM Flow specific keyword. |\n|--------------------------------------------|","size_kind":"fixed","variadic_record":true},"DIFFMMF":{"name":"DIFFMMF","sections":["GRID","SCHEDULE"],"supported":false,"summary":"This keyword, DIFFMMF, defines the diffusivity multipliers for matrix-fractures for when the Dual Porosity option has be activated by either the DUALPORO or DUALPERM keywords, or the Coal Bed Methane option is selected by the COAL keyword, and the Diffusivity option has been activated by the DIFFUSE keywords; all four keywords are in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"DISPERSE":{"name":"DISPERSE","sections":["PROPS"],"supported":false,"summary":"This keyword, DISPERSE, defines the dispersion tables for when the Dispersion option has been activated via declaring the dimensions of the DISPERSE tables using the DISPDIMS keyword and activating the Tracer option via the TRACERS keyword.","parameters":[{"index":1,"name":"VELOCITY","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length/Time"},{"index":2,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["1","Length*Length/Time"]}],"example":"","size_kind":"list","variadic_record":true},"DPKRMOD":{"name":"DPKRMOD","sections":["PROPS"],"supported":false,"summary":"The DPKRMOD keyword can be used to modify the matrix oil relative permeability data (oil-water, oil-gas) and the scaling of the fracture to matrix relative permeabilities, for dual porosity runs for when a Dual Porosity model has been activated by either the DUALPORO or DUALPERM keywords in the RUNSPEC section.","parameters":[{"index":1,"name":"MOD_OIL_WAT_PERM","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"1"},{"index":2,"name":"MOD_OIL_GAS_PERM","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"SCALE_PERM_FRACTURE","description":"","units":{},"default":"YES","value_type":"STRING"}],"example":"","expected_columns":3,"size_kind":"fixed"},"DSPDEINT":{"name":"DSPDEINT","sections":["PROPS"],"supported":false,"summary":"This keyword, DSPDEINT, activates the brine tracer dispersion interpolation by water density option for when the Brine phase is activated in the model by the BRINE keyword in the RUNSPEC section and the DISPERSE keyword in the PROPS section is in the input file. They keyword cause the lookup and interpolation of the DISPERSE tracer concentration to water density, that is the tracer concentration data on the DISPERSE keyword has been replaced by the water density data.","parameters":[],"example":"","size_kind":"none","size_count":0},"EHYSTR":{"name":"EHYSTR","sections":["PROPS"],"supported":false,"summary":"The EHYSTR keyword defines the hysteresis model and associated parameters when the hysteresis option has been activated by the HYSTER variable on the SATOPTS keyword in the RUNSPEC section. Both the Carlson185\n Carlson, F. M. “Simulation of Relative Permeability Hysteresis to the Non-Wetting Phase,” paper SPE 10157, presented at the SPE Annual Technical Conference & Exhibition, San Antonio, Texas, USA (October 5-7, 1981). and Killough186\n Killough, J. E. “Reservoir Simulation with History-dependent Saturation Functions,” paper SPE 5106, Society of Petroleum Engineers Journal (1976) 16, No. 1, 37-48. models are available.","parameters":[{"index":0,"name":"Carlson Hysteresis Model","description":"SATNUM","units":{},"default":""},{"index":1,"name":"HYSTRCP","description":"HYSTRCP is a positive real value that defines the Killough curvature parameter for capillary pressure hysteresis model. The value should range from 0.05 to 0.10. This item is not supported by OPM Flow and should be defaulted (1*).","units":{},"default":"0.1","value_type":"DOUBLE"},{"index":1,"name":"Carlson Hysteresis Model","description":"IMBNUM","units":{},"default":"","value_type":"DOUBLE"},{"index":2,"name":"HYSTMOD","description":"An integer value that determines the relative permeability hysteresis model to be used depending on the phase and the wettability of the system. HYSTMOD should be set to one of the following values:","units":{"field":"HYSTMOD","metric":"Non-Wetting Phases","laboratory":"Wetting Phase"},"default":"0","value_type":"INT"},{"index":2,"name":"Killough Hysteresis Model","description":"SATNUM","units":{},"default":"","value_type":"INT"},{"index":3,"name":"Killough Hysteresis Model","description":"IMBNUM","units":{},"default":"","value_type":"DOUBLE"},{"index":3,"name":"HYSTREL","description":"HYSTREL is a positive real number that defines the Killough’s wetting phase relative permeability curvature parameter. This parameter is only applicable if HYSMOD is set to either 4 or 7. This item is not supported by OPM Flow and should be defaulted (1*).","units":{},"default":"1.0","value_type":"DOUBLE"},{"index":4,"name":"Killough Hysteresis Model","description":"Killough Hysteresis Model","units":{},"default":"","value_type":"DOUBLE"},{"index":4,"name":"HYSTSGR","description":"HYSTSGR is a positive real number that sets a scaling parameter for the trapped non-wetting phase saturation in the Killough model. This item is not supported by OPM Flow and should be defaulted (1*).","units":{},"default":"0.1","value_type":"DOUBLE"},{"index":5,"name":"Carlson Non- Wetting Modeling for Gas and Water","description":"SATNUM","units":{},"default":"","value_type":"STRING"},{"index":5,"name":"HYSTOPT","description":"A defined character string that determines if the hysteresis model should be activated for relative permeability, capillary pressure, or both, and should be set to one of the following: BOTH:apply hysteresis modeling to both relative permeability, and capillary pressure curves. PC:apply hysteresis modeling to capillary pressure curves only. KR:apply hysteresis modeling to relative permeability curves only.","units":{},"default":"BOTH","value_type":"STRING"},{"index":6,"name":"Killough Non- Wetting Modeling for Gas and Water","description":"SATNUM","units":{},"default":"","value_type":"STRING"},{"index":6,"name":"HYSTSCAN","description":"A defined character string that determines the shape of Killough capillary pressure scanning curves when secondary reversal occurs, that is for a drainage, imbibition, drainage cycle. RETR: Secondary drainage curves re-traverses the same scanning curve. NEW: Secondary drainage curves follows a new scanning curve and further reversals also generate a new scanning curve. Only the RETR option is supported by OPM Flow.","units":{},"default":"RETR","value_type":"STRING"},{"index":7,"name":"Killough Non- Wetting Modeling for Gas and Water","description":"Killough Non- Wetting Modeling for the Wetting Oil Phase","units":{},"default":"","value_type":"STRING"},{"index":7,"name":"HYSTMOB","description":"A defined character string that determines how to apply the mobility control correction invoked by the MOBILE variable on the EQLOPTS keyword in the RUNSPEC section. HYSTMOB should be set to one of the following: DRAIN:Only the drainage curve end-points are modified. BOTH:Both the drainage and imbibition curve end-points are modified. The Mobility Control option is not supported in OPM Flow so this parameter has no effect and will be ignored. This item should be defaulted.","units":{},"default":"DRAIN","value_type":"STRING"},{"index":8,"name":"HYSTWET","description":"A defined character string that sets the wetting phase between oil and gas in three phase systems and should be set to one of the following: OIL: Oil is set as the wetting phase between oil and gas, and the oil relative permeability with respect to gas is determined by HYSTMOD for the wetting phase. GAS: Oil is set as the non-wetting phase between oil and gas, and the oil relative permeability with respect to gas is determined by HYSTMOD for the non-wetting phase. Note for all the above cases the gas relative permeability is always modelled as a non-wetting phase. Note oil is always the wetting phase to gas in two phase systems. This item is not supported by OPM Flow and should be defaulted (1*).","units":{},"default":"OIL","value_type":"STRING"},{"index":9,"name":"HYBAKOIL","description":"Baker model one or model two relative permeability oil phase hysteresis option used in the commercial compositional simulator. This item is not supported by OPM Flow and should be defaulted (1*).","units":{},"default":"NO","value_type":"STRING"},{"index":10,"name":"HYBAKGAS","description":"Baker model one or model two relative permeability gas phase hysteresis option used in the commercial compositional simulator. This item is not supported by OPM Flow and should be defaulted (1*).","units":{},"default":"NO","value_type":"STRING"},{"index":11,"name":"HYBAKWAT","description":"Baker model one or model two relative permeability water phase hysteresis option used in the commercial compositional simulator. This item is not supported by OPM Flow and should be defaulted (1*).","units":{},"default":"NO","value_type":"STRING"},{"index":12,"name":"HYTHRESH","description":"Killough’s hysteresis threshold saturation value used in the commercial compositional simulator. This item is not supported by OPM Flow and should be defaulted (1*).","units":{},"default":"0.0","value_type":"DOUBLE"},{"index":13,"name":"HYSWETRP","description":"Killough’s hysteresis wetting phase modification used in the commercial black-oil simulator. This item is not supported by OPM Flow and should be defaulted (1*).","units":{},"default":"0","value_type":"INT"},{"index":14,"name":"HYSPCSCL","description":"An integer value that determines if capillary pressure scaling should be enabled to correct the construction of the scanning capillary pressure curve. 0: Capillary pressure scaling is disabled. 1: Capillary pressure scaling is enabled. This option is currently disabled by default but this is likely to change as the correction is believed to be a bug fix. For more information see #6383. This is an OPM Flow specific item that is not supported by the commercial simulator.","units":{},"default":"0","value_type":"INT"}],"example":"--\n-- HYSTERESIS MODEL AND PARAMETERS\n--\n-- PC-CUR MODEL RELPERM TRAPPED OPTION SHAPE MOBILIT WET\n-- HYSTRCP HYSTMOD HYSTREL HYSTSGR HYSTOPT HYSTSCAN HYSTMOB HYSTWET\nEHYSTR\n0.1 0 0.1 1* KR 1* 1* 1* /\nThe above example defines the hysteresis model and parameters used in the Norne model. Here the default value is used for the Killough curvature parameter for capillary pressure hysteresis mode, the Carlson hysteresis model is used for the non-wetting phase and SATNUM for the wetting phase, 0.1 is used for Killough’s wetting phase relative permeability curvature parameter (this parameter is ignored because the Carlson model has been selected), the default values for the trapped non-wetting phase saturation in the Killough mode (again, this parameter is ignored because the Carlson model has been selected, and the hysteresis modeling is only applied to relative permeability curves).","expected_columns":14,"size_kind":"fixed","size_count":1},"EHYSTRR":{"name":"EHYSTRR","sections":["PROPS"],"supported":false,"summary":"The EHYSTRR keyword defines the hysteresis model and associated parameters via the drainage SATNUM allocation region array, for when the hysteresis option has been activated by the HYSTER variable on the SATOPTS keyword in the RUNSPEC section. Only the Killough187\n Killough, J. E. “Reservoir Simulation with History-dependent Saturation Functions,” paper SPE 5106, Society of Petroleum Engineers Journal (1976) 16, No. 1, 37-48. model is available for this keyword and the keyword is optional.","parameters":[{"index":1,"name":"HYSTRCP","description":"HYSTRCP is a positive real value that defines the Killough curvature parameter for capillary pressure hysteresis model. The value should range from 0.05 to 0.10.","units":{},"default":"0.1","value_type":"DOUBLE"},{"index":2,"name":"HYSTREL","description":"HYSTREL is a positive real number that defines the Killough’s wetting phase relative permeability curvature parameter. This parameter is ignored if HYSMOD on the EHYSTR keyword is not set to 4.","units":{},"default":"1.0","value_type":"DOUBLE"},{"index":3,"name":"HYSTSGR","description":"HYSTSGR is a positive real number that sets a scaling parameter for the trapped non-wetting phase saturation in the Killough model.","units":{},"default":"0.1","value_type":"DOUBLE"}],"example":"--\n-- HYSTERESIS MODEL AND PARAMETERS VIA SATNUM\n--\n-- PC-CUR RELPERM TRAPPED\n-- HYSTRCP HYSTREL HYSTSGR\nEHYSTRR\n0.04 1.0 1* / SATNUM REGION 1\n0.06 1.0 1* / SATNUM REGION 2\n0.08 1.0 1* / SATNUM REGION 3\n0.10 1.0 1* / SATNUM REGION 4\n0.10 1.0 1* / SATNUM REGION 5\nThe above example defines the hysteresis model and parameters for when NTSFUN equals five on the TABDIMS keyword in the RUNSPEC section, that is for five SATNUM regions.","expected_columns":3,"size_kind":"fixed"},"ENKRVD":{"name":"ENKRVD","sections":["PROPS"],"supported":false,"summary":"This keyword defines the maximum oil, gas, and water relative permeability values versus depth for the three phases and for when the end-point scaling option has been invoked by the ENDSCALE keyword in the RUNSPEC section. This functionality is not supported in OPM Flow.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"-1","value_type":"DOUBLE","dimension":["Length","1","1","1","1","1","1","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"ENPCVD":{"name":"ENPCVD","sections":["PROPS"],"supported":false,"summary":"This keyword defines the maximum gas-oil and water-oil capillary pressure values versus depth for when the end-point scaling option has been invoked by the ENDSCALE keyword in the RUNSPEC section","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"-1","value_type":"DOUBLE","dimension":["Length","Pressure","Pressure"]}],"example":"","size_kind":"fixed","variadic_record":true},"ENPTVD":{"name":"ENPTVD","sections":["PROPS"],"supported":false,"summary":"This keyword defines the variation of the relative permeability saturation end-points (SWL, SWCR, etc.) for all three phases versus depth for when the end-point scaling option has been invoked by the ENDSCALE keyword in the RUNSPEC section. This functionality is not supported in OPM Flow.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"-1","value_type":"DOUBLE","dimension":["Length","1","1","1","1","1","1","1","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"ENSPCVD":{"name":"ENSPCVD","sections":["PROPS"],"supported":false,"summary":"This keyword defines the variation of the capillary pressure saturation end-points, connate gas (SGL) and connate water (SWL), versus depth for when the end-point scaling option has been invoked by the ENDSCALE keyword in the RUNSPEC section. This functionality is not supported in OPM Flow.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"-1","value_type":"DOUBLE","dimension":["Length","1","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"EPSDBGS":{"name":"EPSDBGS","sections":["PROPS","SCHEDULE"],"supported":false,"summary":"This keyword, EPSDBGS, defines the end-point debug data for multiple grid blocks that should be written to the DEBUG file (*.DBG) for when the End-Point Scaling option has been activated by the ENDSCALE keyword in the RONSPEC section.","parameters":[{"index":1,"name":"TABLE_OUTPUT","description":"","units":{},"default":"0","value_type":"INT","record":1},{"index":2,"name":"CHECK_DRAIN_HYST","description":"","units":{},"default":"0","value_type":"INT","record":1},{"index":1,"name":"IX1","description":"","units":{},"default":"","value_type":"INT","record":2},{"index":2,"name":"IX2","description":"","units":{},"default":"","value_type":"INT","record":2},{"index":3,"name":"JY1","description":"","units":{},"default":"","value_type":"INT","record":2},{"index":4,"name":"JY2","description":"","units":{},"default":"","value_type":"INT","record":2},{"index":5,"name":"KZ1","description":"","units":{},"default":"","value_type":"INT","record":2},{"index":6,"name":"KZ2","description":"","units":{},"default":"","value_type":"INT","record":2},{"index":7,"name":"GRID_NAME","description":"","units":{},"default":"","value_type":"STRING","record":2}],"example":"","records_meta":[{"expected_columns":2},{"expected_columns":7}],"size_kind":"list"},"EPSDEBUG":{"name":"EPSDEBUG","sections":["PROPS","SCHEDULE"],"supported":false,"summary":"This keyword, EPSDEBUG, defines the end-point debug data for individual grid blocks that should be written to the Debug file (*.DBG) for when the End-Point Scaling option has been activated by the ENDSCALE keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"IX1","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"IX2","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"JY1","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"JY2","description":"","units":{},"default":"","value_type":"INT"},{"index":5,"name":"KZ1","description":"","units":{},"default":"","value_type":"INT"},{"index":6,"name":"KZ2","description":"","units":{},"default":"","value_type":"INT"},{"index":7,"name":"TABLE_OUTPUT","description":"","units":{},"default":"0","value_type":"INT"},{"index":8,"name":"GRID_NAME","description":"","units":{},"default":"","value_type":"STRING"},{"index":9,"name":"CHECK_DRAIN_HYST","description":"","units":{},"default":"0","value_type":"INT"}],"example":"","expected_columns":9,"size_kind":"fixed","size_count":1},"ESSNODE":{"name":"ESSNODE","sections":["PROPS"],"supported":false,"summary":"This keyword, ESSNODE, defines the salt concentration data that is used in calculating the water-oil surface tension for when the Brine option has been activated by the BRINE keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Density"]}],"example":"","size_kind":"fixed","variadic_record":true},"FHERCHBL":{"name":"FHERCHBL","sections":["PROPS"],"supported":false,"summary":"The FHERCHBL keyword defines Herschel-Bulkley rheological property data for Non-Newtonian fluids versus polymer concentration, for when the Polymer option has been invoked via the POLYMER keyword in the RUNSPEC section and Non-Newtonian Fluid phase has been declared active by the NNEWTF keyword, also in the RUNSPEC section.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Density","1","1","Pressure"]}],"example":"","size_kind":"fixed","variadic_record":true},"FILLEPS":{"name":"FILLEPS","sections":["PROPS"],"supported":null,"summary":"This keyword switches on the export of the saturation end-point data (SWL, SWCR, SOWCR array etc.) to the *.INIT file so that the data can be viewed in post-processing software like OPM ResInsight.","parameters":[],"example":"--\n-- ACTIVATE SATURATION END-POINT EXPORT TO THE INIT FILE\n--\nFILLEPS\nThe above example switches on the export of the end-point saturation data to the *.INIT file.","size_kind":"none","size_count":0},"FOAMADS":{"name":"FOAMADS","sections":["PROPS"],"supported":null,"summary":"The FOAMADS keyword defines the foam rock adsorption tables for when the Foam option has been activated by the FOAM keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"FOAMCON","description":"A columnar vector of real monotonically increasing down the column values that defines the foam concentration in the solution surrounding the rock. The first entry should be zero to define a no foam concentration data set. Units are dependent on the transport phase specified via the FOAMOPT1 variable on the FOAMOPTS keywod in the PROPS section.","units":{"field":"Gas: lb/Mscf Water: lb/stb","metric":"Gas: kg/sm3 Water: kg/sm3","laboratory":"Gas: gm/scc Water: gm/scc"},"default":"None","value_type":"DOUBLE","dimension":["FoamDensity","1"]},{"index":2,"name":"FOAMRATI","description":"A columnar vector of real increasing down the column values that defines the mass of adsorbed foam per unit mass of rock for a given FOAMCON. The first table data set entry should be zero to define a no foam concentration data set.","units":{"field":"lb/lb","metric":"kg/kg","laboratory":"gm/gm"},"default":"None"}],"example":"--\n-- FOAM ROCK ADSORPTION TABLE\n--\nFOAMADS\n-- FOAM FOAM\n-- FOAMCON FOAMRATI\n-- ------- --------\n0.0 0.00000\n2.0 0.00003\n4.0 0.00005\n6.0 0.00007\n8.0 0.00009\n10.0 0.00011\n12.0 0.00012\n14.0 0.00015 / TABLE NO. 01\n-- FOAM FOAM\n-- FOAMCON FOAMRATI\n-- ------- --------\n0.0 0.00000\n3.0 0.00004\n5.0 0.00006\n7.0 0.00008\n8.0 0.00009\n10.0 0.00011 / TABLE NO. 02\nThe above example defines two foam rock adsorption tables assuming NTSFUN equals two and NSSFUN is greater than or equal to eight on the TABDIMS keyword in the RUNSPEC section.","size_kind":"fixed","variadic_record":true},"FOAMDCYO":{"name":"FOAMDCYO","sections":["PROPS"],"supported":false,"summary":"The FOAMDCYO keyword defines the foam decay half-life versus oil saturation for when the Foam option has been activated by the FOAM keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["1","Time"]}],"example":"","size_kind":"fixed","variadic_record":true},"FOAMDCYW":{"name":"FOAMDCYW","sections":["PROPS"],"supported":false,"summary":"The FOAMDCYW keyword defines the foam decay half-life versus water saturation for when the Foam option has been activated by the FOAM keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["1","Time"]}],"example":"","size_kind":"fixed","variadic_record":true},"FOAMFCN":{"name":"FOAMFCN","sections":["PROPS"],"supported":false,"summary":"The FOAMFCN keyword defines the reduction in gas mobility versus capillary number, for when the Foam option has been activated by the FOAM keyword in the RUNSPEC section, and the FOAMOPT2 parameter on the FOAMOPTS keyword in the PROPS section has been set to the character string FUNC.","parameters":[{"index":1,"name":"CAPILLARY_NUMBER","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":2,"name":"EXP","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"}],"example":"","expected_columns":2,"size_kind":"fixed"},"FOAMFRM":{"name":"FOAMFRM","sections":["PROPS"],"supported":false,"summary":"The FOAMFRM keyword defines the reduction in gas mobility versus the reference mobility reduction factor, for when the Foam option has been activated by the FOAM keyword in the RUNSPEC section, and the FOAMOPT2 parameter on the FOAMOPTS keyword in the PROPS section has been set to the character string FUNC.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["1"]}],"example":"","size_kind":"fixed","variadic_record":true},"FOAMFSC":{"name":"FOAMFSC","sections":["PROPS"],"supported":null,"summary":"The FOAMFSC keyword defines the reduction in gas mobility as a function of the foam surfactant concentration within a grid block. The Foam option must be activated by the FOAM keyword in the RUNSPEC section in order to use this keyword. In addition, the FOAMOPT2 parameter on the FOAMOPTS keyword in the PROPS section must be set to the character string FUNC, in order to activate the functional form of the gas mobility reduction calculations.","parameters":[{"index":1,"name":"FOAMCON","description":"A real positive value that defines the foam surfactant concentration at which foam modeling becomes active in the model and a strong foam is formed. FOAMCON cannot be defaulted and must be specified for the first table. Subsequent tables can be defaulted and will in this case use the previous tables’ entries as the default value.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None","value_type":"DOUBLE","dimension":"Concentration"},{"index":2,"name":"FOAMEXP","description":"A real positive value that defines an exponent that determines the gradient in the change of the reduction in gas mobility due to foam (es in equation (8.51). Note if es is less than one then the slope of Fs in equation (8.51)will be infinite at Cs equal to zero. In this case, small surfactant concentrations have a significant effect on the mobility, especially if the reference concentration Csr is also small. If this is the case use MINSURF on this keyword to set a minimum surfactant concentration to avoid small-scale numerical errors from affecting the simulation.","units":{"field":"dimensionless 1.0","metric":"dimensionless 1.0","laboratory":"dimensionless 1.0"},"default":"Defined","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"MINSURF","description":"MINSURF is a real positive value that defines the minimum surfactant concentration for which the reduction in gas mobility will be calculated. The default value of 1 x 10-20 implies that there is no minimum","units":{"field":"lb/stb 1 x 10-20","metric":"kg/sm3 1 x 10-20","laboratory":"gm/scc 1 x 10-20"},"default":"Defined","value_type":"DOUBLE","dimension":"Concentration"},{"index":4,"name":"MINSWAT","description":"MINSWAT is a real positive value less than 1.0 that sets the minimum water saturation below which foam has no effect. The default value of 1 x 10-6 implies that there is no minimum. Note that this parameter is only used in the commercial simulator’s compositional simulator and is therefore not used by OPM Flow or the commercial simulators black-oil simulator.","units":{"field":"dimensionless 1 x 10-6","metric":"dimensionless 1 x 10-6","laboratory":"dimensionless 1 x 10-6"},"default":"Defined","value_type":"DOUBLE","dimension":"1"}],"example":"--\n-- FOAM GAS MOBILITY VERSUS SURFACTANT CONCENTRATION FUNCTIONS\n--\nFOAMFSC\n-- FOAM FOAM FOAM FOAM\n-- FOAMCON FOAMEXP MINSURF MINSWAT\n-- ------- ------- ------- -------\n0.001 1.010 / TABLE NO. 01\n0.002 1.000 / TABLE NO. 02\n/ TABLE NO. 03 (DEFAULTED)\n0.001 0.850 1.0E-10 / TABLE NO. 04\n0.002 1.030 / TABLE NO. 05\n0.002 1.000 / TABLE NO. 06\nHere, NTSFUN equals six on the TABDIMS keyword in the RUNSPEC section and therefore six entries are required for the FOAMFSC keyword. Table number three is completed defaulted and will therefore use all the properties from the previous table, that is table number two.\n| [F sub{s}`=`left({C sub{s}} over{C sup{r} sub{s} }right) sup{e sub{s}}] | (8.51) |\n|-------------------------------------------------------------------------|--------|\n| [M sub{ rf}`=` 1 over{ 1 ` +` left( M sub{r} `times` F sub{s} `times` F sub{w} `times` F sub{o} `times` F sub{c} right)}] | (8.52) |\n|---------------------------------------------------------------------------------------------------------------------------|--------|","expected_columns":4,"size_kind":"fixed"},"FOAMFSO":{"name":"FOAMFSO","sections":["PROPS"],"supported":false,"summary":"The FOAMFSO keyword defines the reduction in gas mobility versus oil saturation, for when the Foam option has been activated by the FOAM keyword in the RUNSPEC section, and the FOAMOPT2 parameter on the FOAMOPTS keyword in the PROPS section has been set to the character string FUNC.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["1","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"FOAMFST":{"name":"FOAMFST","sections":["PROPS"],"supported":false,"summary":"The FOAMFST keyword defines the gas-water surface tension versus the foam surfactant concentration, for when the Foam option has been activated by the FOAM keyword in the RUNSPEC section, and the FOAMOPT2 parameter on the FOAMOPTS keyword in the PROPS section has been set to the character string FUNC.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["FoamDensity","SurfaceTension"]}],"example":"","size_kind":"fixed","variadic_record":true},"FOAMFSW":{"name":"FOAMFSW","sections":["PROPS"],"supported":false,"summary":"The FOAMFRM keyword defines the reduction in gas mobility versus water saturation, for when the Foam option has been activated by the FOAM keyword in the RUNSPEC section, and the FOAMOPT2 parameter on the FOAMOPTS keyword in the PROPS section has been set to the character string FUNC.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["1","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"FOAMMOB":{"name":"FOAMMOB","sections":["PROPS"],"supported":null,"summary":"The FOAMMOB keyword defines the reduction in gas mobility as a function of the foam concentration within a grid block. The Foam option must be activated by the FOAM keyword in the RUNSPEC section in order to use this keyword. In addition, this keyword must be supplied if the foam model is activated.","parameters":[{"index":1,"name":"FOAMCON","description":"A columnar vector of real monotonically increasing down the column values that defines the foam concentration for the corresponding gas mobility reduction factor (FOAMRATI). The first entry should be zero to define a no foam concentration data set. Units are dependent on the transport phase specified via the FOAMOPT1 variable on the FOAMOPTS keyword in the PROPS section. FOAMOPT1 should be set to either GAS or WATER.","units":{"field":"Gas: lb/Mscf Water: lb/stb","metric":"Gas: kg/sm3 Water: kg/sm3","laboratory":"Gas: gm/scc Water: gm/scc"},"default":"None","value_type":"DOUBLE","dimension":["FoamDensity","1"]},{"index":2,"name":"FOAMRATI","description":"A columnar vector of real decreasing down the column values that defines the corresponding gas mobility reduction factor for a given FOAMCON. The first table data set entry should be one to define a no foam concentration data set. Each FOAMCON/FOAMRATI data set should be terminated by a “/”","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- FOAM GAS MOBILITY VERSUS FOAM CONCENTRATION TABLES\n--\nFOAMMOB\n-- FOAM FOAM\n-- FOAMCON FOAMRATI\n-- ------- --------\n0.000 1.00000\n0.005 0.50000\n0.010 0.20000\n0.015 0.10000\n0.020 0.07500\n0.025 0.07000\n0.030 0.06500\n0.035 0.06500 / TABLE NO. 01\n-- FOAM FOAM\n-- FOAMCON FOAMRATI\n-- ------- --------\n0.000 1.00000\n0.010 0.50000\n0.015 0.25000\n0.020 0.07500\n0.025 0.07000\n0.030 0.07000 / TABLE NO. 02\nGiven NTPVT equals two and NPPVT is greater and or equal to eight on the TABDIMS keyword in the RUNSPEC section, the example defines the foam gas mobility versus foam concentration tables for two tables.\nThere is no terminating “/” for this keyword.","size_kind":"fixed","variadic_record":true},"FOAMMOBP":{"name":"FOAMMOBP","sections":["PROPS"],"supported":false,"summary":"The FOAMMOBP keyword defines the reduction in foam mobility reduction versus oil pressure, for when the Foam option has been activated by the FOAM keyword in the RUNSPEC.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Pressure","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"FOAMMOBS":{"name":"FOAMMOBS","sections":["PROPS"],"supported":false,"summary":"The FOAMMOBS keyword defines the reduction in foam mobility reduction versus shear, for when the Foam option has been activated by the FOAM keyword in the RUNSPEC.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Length/Time","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"FOAMOPTS":{"name":"FOAMOPTS","sections":["PROPS"],"supported":true,"summary":"The FOAMOPTS keyword defines the transport phase for the foam (gas, water or solvent) and how gas mobility reduction should be calculated for when the Foam option has been activated by the FOAM keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"FOAMOPT1","description":"A defined character string that specifies the transport phase for the foam, and should be set to one of the following: GAS: for the foam to be transport in the gas phase., WATER: for the foam to be transported in the water phase, or SOLVENT: for the foam to be transported in the solvent phase.","units":{},"default":"GAS","value_type":"STRING","options":["GAS","WATER","SOLVENT"]},{"index":2,"name":"FOAMOPT2","description":"A defined character string that specifies the method to be used to calculate the reduction in gas mobility, and should be set to one of the following: TAB: Sets the reduction in gas mobility is to be calculated based on tables using the FOAMMOB keyword as a function of foam concentration, the FOAMMOBS keyword as a function of shear, or as a function of pressure using the FOAMMOBP keyword. All keywords are in the PROPS section. FUNC: Sets the reduction in gas mobility to be calculated based on a function defined via the FOAMFRM, FOAMFSC, FOAMFSW, FOAMFSO, FOAMFCN, or FOAMFST keywords in the PROPS section. Only the default value of TAB is currently supported by OPM Flow.","units":{},"default":"TAB","value_type":"STRING"}],"example":"--\n-- FOAMOPT1 FOAMOPT2\n-- PHASE MOBILITY\n-- -------- --------\nFOAMOPTS\nGAS TAB / FOAM MODEL OPTIONS\nThe above example defines the transport phase is to be gas and the gas mobility reduction is to use a table as defined by the FOAMMOB keyword as a function of foam concentration, the FOAMMOBS keyword as a function of shear, or as a function of pressure using the FOAMMOBP keyword.","expected_columns":2,"size_kind":"fixed","size_count":1},"FOAMROCK":{"name":"FOAMROCK","sections":["PROPS"],"supported":true,"summary":"The FOAMROCK keyword defines the foam rock properties for when the Foam option has been activated by the FOAM keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"ADINDX","description":"A positive integer of 1 or 2 that defines foam desorption option, as per: then foam desorption may occur by retracing the foam adsorption isotherm when the local foam concentration in the solution decreases. then no foam desorption may occur. Only the default value of 1 is supported by OPM Flow.","units":{"field":"dimensionless 1","metric":"dimensionless 1","laboratory":"dimensionless 1"},"default":"Defined","value_type":"INT"},{"index":2,"name":"DENSITY","description":"A real value that defines the rock in situ density, that is at reservoir conditions.","units":{"field":"lb/rb","metric":"kg/rm3","laboratory":"gm/rcc"},"default":"None","value_type":"DOUBLE","dimension":"Density"}],"example":"--\n-- FOAM-ROCK PROPERTIES\n--\nFOAMROCK\n-- DESORP INSITU\n-- OPTN DENSITY\n-- ------ -------\n1 1800.0 / TABLE NO. 01\n2 1980.0 / TABLE NO. 02\n1 2005.0 / TABLE NO. 03\nThe above example defines three foam-rock tables, based on the NTSFUN variable on the TABDIMS keyword in the RUNSPEC section being equal to three.\nThere is no terminating “/” for this keyword.\n| Note In the commercial simulator if the POLYMER and SURFACT phases have been activated in conjunction with the FOAM phase then the mass density of rock will be set by the PLYROCK, SURFROCK, or the FOAMROCK keywords depending on the order entered in the run deck. This is not the case for OPM Flow. OPM Flow’s FOAM phase is a standalone implementation and cannot be used in conjunction with the either the POLYMER or SURFACT phases. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":2,"size_kind":"fixed"},"GASDENT":{"name":"GASDENT","sections":["PROPS"],"supported":null,"summary":"GASDENT defines the gas density as a function of temperature coefficients for when OPM Flow’s thermal option has been activated by the THERMAL keyword in the RUNSPEC. Note this is an OPM Flow keyword used with OPM Flow’s black-oil thermal model that is not available in the commercial simulator’s black-oil thermal formulation.","parameters":[{"index":1,"name":"TEMP","description":"TEMP is a real positive value greater than zero that defines the absolute reference temperature used with TEXP1 and TEXP2 to estimate the change in gas density with respect to temperature.","units":{"field":"oR 527.67","metric":"oK 293.15","laboratory":"oK 293.15"},"default":"Defined","value_type":"DOUBLE","dimension":"AbsoluteTemperature"},{"index":2,"name":"TEXP1","description":"TEXP1 is a real positive value greater than zero that defines the gas thermal expansion coefficient of the first order.","units":{"field":"1/oR 1.67 x 10-4","metric":"1/oK 3.0 x 10-4","laboratory":"1/oK 3.0 x 10-4"},"default":"Defined","value_type":"DOUBLE","dimension":"1/AbsoluteTemperature"},{"index":3,"name":"TEXP2","description":"TEXP2 is a real positive value greater than zero that defines the gas thermal expansion coefficient of the second order.","units":{"field":"1/oR2 9.26 x 10-7","metric":"1/oK2 3.0 x 10-6","laboratory":"1/oK2 3.0 x 10-6"},"default":"Defined","value_type":"DOUBLE","dimension":"1/AbsoluteTemperature*AbsoluteTemperature"}],"example":"The following example shows the GASDENT keyword using the default values, for when the thermal option has been activated by the THERMAL keyword in the RUNSPEC section and for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set to two.\n--\n-- GAS DENSITY TEMPERATURE COEFFICIENTS (OPM FLOW THERMAL KEYWORD)\n--\n-- GAS DENSITY DENSITY\n-- TEMP COEFF1 COEFF2\n-- -------- ------- -------\nGASDENT\n1* 1* 1* / TABLE NO. 01\n1* 1* 1* / TABLE NO. 02\nThere is no terminating “/” for this keyword.\n| [%rho_g( p, T ) = %rho_g( p_s, T_s ) b_g( p, T )] | (8.3.73.1) |\n|---------------------------------------------------|------------|\n| [b_g( p, T ) = { b_g( p, T_ref ) } over { 1 + c_1 ( T - T_ref ) + c_2 ( T - T_ref )^2 }] | (8.3.73.2) |\n|------------------------------------------------------------------------------------------|------------|","expected_columns":3,"size_kind":"fixed"},"GASJT":{"name":"GASJT","sections":["PROPS"],"supported":null,"summary":"GASJT activates the gas Joule-Thomson188\n Natural Gas Engineering (McGraw-Hill chemical engineering series), Donald L. Katz, Robert l Lee, McGraw-Hill Education, 1990 (ISBN 0071007776, 9780071007771). effect in temperature calculations, and defines the gas Joule-Thomson Coefficient (“JTC”) at a given reference pressure, for when OPM Flow’s thermal option has been activated by the THERMAL keyword in the RUNSPEC.","parameters":[{"index":1,"name":"PRESS","description":"A real positive value that defines the reference pressure for the corresponding Joule-Thomson Coefficient, GASJTC.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":"Pressure"},{"index":2,"name":"GASJTC","description":"GASJTC is a real positive or negative value that defines the gas phase Joule-Thomson Coefficient. If the value is defaulted (1*) or set to 0, then GASJTC is internally calculated using the thermal gas density data on the GASDENT keyword in the PROPS section. If a non-zero value is specified, then the GASJTC is assumed to be constant and equal to that value.","units":{"field":"oF/psia","metric":"oC/barsa","laboratory":"oC/atma"},"default":"0","value_type":"DOUBLE","dimension":"AbsoluteTemperature/Pressure"}],"example":"The following example shows the GASJT keyword for when the thermal option has been activated by the THERMAL keyword in the RUNSPEC section, and for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set equal to two.\n--\n-- GAS JOULE-THOMSON COEFFICIENT (OPM FLOW EXTENSION KEYWORD)\n--\n-- REF GAS\n-- PRESS JTC\n-- -------- -------\nGASJT\n20.0 1* / TABLE NO. 01\n20.0 0.50 / TABLE NO. 02\nHere the first entry is defaulted, and the simulator will therefore calculate the gas JTC internally using the data on the GASDENT keyword in the PROPS section.\nThere is no terminating “/” for this keyword.\n| Note This is an OPM Flow keyword used with OPM Flow’s black-oil thermal model, that is not available in the commercial simulator’s black-oil thermal formulation. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| [%eta` `=`` left({ partial T} over {partial P} right)] | (8.53) |\n|--------------------------------------------------------|--------|\n| [%eta ``=`` RT^2 over Pc_p left({ partial Z} over {partial T} right) _P] | (8.54) |\n|--------------------------------------------------------------------------|--------|","expected_columns":2,"size_kind":"fixed"},"GASVISCT":{"name":"GASVISCT","sections":["PROPS"],"supported":null,"summary":"GASVISCT defines the gas viscosity as a function of temperature for when OPM Flow’s thermal option has been activated by the THERMAL keyword in the RUNSPEC. The reference pressure for this table is given by the VISCREF keyword in the PROPS section. Note this is an OPM Flow keyword used with OPM Flow’s black-oil thermal model that is not available in the commercial simulator’s black-oil thermal formulation. However, the keyword and similar functionality is available in the commercial compositional simulator.","parameters":[{"index":1,"name":"TEMP","description":"A columnar vector of real monotonically increasing down the column values that defines the temperature values.","units":{"field":"oF","metric":"oC","laboratory":"oC"},"default":"None","value_type":"DOUBLE","dimension":["Temperature","Viscosity"]},{"index":2,"name":"VIS","description":"A columnar vector of real increasing down the column values that defines the gas viscosity for the corresponding temperature values (TEMP). VIS should be given at the reference pressure defined by the PRESS variable on the VISCREF keyword.","units":{"field":"cP","metric":"cP","laboratory":"cP"},"default":"None"}],"example":"The following example shows the GASVISCT keyword for when the thermal option has been activated by the THERMAL keyword in the RUNSPEC section and for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set equal to one.\n--\n-- GAS VISCOSITY VERSUS TEMPERATURE TABLES (OPM FLOW EXTENSION KEYWORD)\n--\n-- GAS GAS\n-- TEMP VISC\n-- -------- -------\nGASVISCT\n100.0 0.0500\n110.0 0.0550\n120.0 0.0580\n150.0 0.0620\n165.0 0.0625 / TABLE NO. 01\nThere is no terminating “/” for this keyword.","size_kind":"fixed","variadic_record":true},"GIALL":{"name":"GIALL","sections":["PROPS"],"supported":false,"summary":"The GIALL keyword defines the GI values and the associated RVGI, RSGI, BGGI and BOGI values as a function of pressure, for when the GI Pseudo Compositional option has been activated in the model via the GIMODEL keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"PRESSURE","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":2,"name":"TABLE","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["1","1","1","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"GINODE":{"name":"GINODE","sections":["PROPS"],"supported":false,"summary":"The GINODE keyword defines the Gi node values used when the GIMODEL keyword in the RUNSPEC section has been used to activate the GI Pseudo Compositional option for the run. The keyword is used in conjunction with the RSGI, RVGI, BGGI and BOGI keywords in the PROPS section to describe the fluid properties for the GI Pseudo Compositional option.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["1"]}],"example":"","size_kind":"fixed","variadic_record":true},"GRAVCONS":{"name":"GRAVCONS","sections":["PROPS"],"supported":false,"summary":"The GRAVCONS keyword re-defines the gravity constant used in various calculations from the default value used by the simulator. Normally this keyword should not be used.","parameters":[{"index":1,"name":"GRAVCONS","description":"GRAVCONS is a positive real number number that defines the gravity constant used in various calculations.","units":{"field":"ft2psi/lb 0.00694","metric":"m2bars/kg 0.0000981","laboratory":"cm2atm/gm 0.000968"},"default":"Defined","value_type":"DOUBLE","dimension":"Length*Length*Pressure/Mass"}],"example":"--\n-- RE-DEFINE GRAVITY CONSTANT\n--\nGRAVITY\n0.0000980665 /\nThe above example re-defines the gravity constant to be 0.0000980665 ft2psi/lb from the default value of 0.00694 ft2psi/lb.","expected_columns":1,"size_kind":"list"},"GRAVITY":{"name":"GRAVITY","sections":["PROPS"],"supported":null,"summary":"GRAVITY defines the oil API gravity and water and gas surface specific gravities for the fluids for various regions in the model. The number of GRAVITY vector data sets is defined by the NTPVT parameter on the TABDIMS keyword in the RUNSPEC section and the allocation of the GRAVITY data sets to different grid blocks in the model is done via the PVTNUM keyword in the REGION section. One data set consists of one record or line which is terminated by a “/”.","parameters":[{"index":1,"name":"OILAPI","description":"OILAPI is a real number defining the API gravity of the oil phase at surface conditions. The American Petroleum Institute (“API”) classifies oils based on an API gravity (γAPI), or degrees API (oAPI), the relationship between relative density (γo) of oil and API gravity (γAPI) is given by: [%gamma SUB { API } ~ = ~ { 141.5 } OVER { %gamma SUB { o }}~-~ 131.5]","units":{"field":"oAPI","metric":"oAPI","laboratory":"oAPI"},"default":"None","value_type":"DOUBLE","dimension":"1"},{"index":2,"name":"WATGRAV","description":"WATGRAV is a real number defining the specific gravity of the water phase relative to pure water at surface conditions.","units":{"field":"(water =1.0) 0.7773","metric":"(water =1.0) 0.7773","laboratory":"(water =1.0) 0.7773"},"default":"Defined","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"GASGRAV","description":"GASGRAV is a real number defining the specific gravity of the gas phase relative to air at surface conditions.","units":{"field":"(air =1.0) 1.000","metric":"(air =1.0) 1.000","laboratory":"(air =1.0) 1.000"},"default":"Defined","value_type":"DOUBLE","dimension":"1"}],"example":"The following shows the GRAVITY keyword for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set to one.\n--\n-- OIL WAT GAS\n-- GRAVITY GRAVITY GRAVITY\n-- ------- ------- -------\nGRAVITY\n39.0 1.012 0.650 / GRAVITY PVT DATA REGION 1\nThe next example shows the GRAVITY keyword for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set to three.\n--\n-- OIL WAT GAS\n-- GRAVITY GRAVITY GRAVITY\n-- ------- ------- -------\nGRAVITY\n37.0 1.012 0.650 / GRAVITY PVT DATA REGION 1\n38.0 1.012 0.646 / GRAVITY PVT DATA REGION 2\n39.0 1.012 0.640 / GRAVITY PVT DATA REGION 3\nThe third and final example shows the GRAVITY keyword for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set to four. Here table two defaults to table one, and table four defaults to table three.\n--\n-- OIL WAT GAS\n-- GRAVITY GRAVITY GRAVITY\n-- ------- ------- -------\nGRAVITY\n37.0 1.012 0.650 / GRAVITY PVT DATA REGION 1\n/ GRAVITY PVT DATA REGION 2\n38.0 1.012 0.646 / GRAVITY PVT DATA REGION 3\n/ GRAVITY PVT DATA REGION 4\nAgain, note that there is no terminating “/” for this keyword.","expected_columns":3,"size_kind":"fixed"},"GSF":{"name":"GSF","sections":["PROPS"],"supported":null,"summary":"The GSF keyword defines the gas relative permeability and gas-water capillary pressure data versus gas saturation tables for when only gas and water are present in the input deck. This keyword should only be used if the gas and water phases are present in the run, and can therefore also be used with the CO2STORE and H2STORE models. In addition, the keyword must be used in conjunction with the WSF keyword in the PROPS section, that defines the water relative permeability versus water saturation for gas-water systems.","parameters":[{"index":1,"name":"SGAS","description":"A columnar vector of real values monotonically increasing down the column starting from zero and terminating at one minus the connate water saturation, that defines the gas saturation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":["1","1","Pressure"]},{"index":2,"name":"KRG","description":"A columnar vector of real values that are either equal or increasing down the column and that are greater than or equal to zero and less than or equal to one that defines the gas relative permeability. Note that the first entry in the column must be zero.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":3,"name":"PCWG","description":"A columnar vector of real values that are either equal or increasing down the column that defines the gas-water capillary pressure.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"None"}],"example":"--\n-- GAS RELATIVE PERMEABILITY TABLES (OPM FLOW KEYWORD)\n--\nGSF\n-- SGAS KRG PCGW\n-- FRAC PSIA\n-- -------- -------- -------\n0.00 0.0000 0.0\n0.05 0.0000 0.0\n0.10 0.0000 0.0\n0.15 0.0000 0.0\n0.20 0.0002 0.0\n0.25 0.0010 0.0\n0.30 0.0062 0.0\n0.35 0.0140 0.0\n0.40 0.0273 0.0\n0.45 0.0450 0.0\n0.50 0.0707 0.0\n0.55 0.1020 0.0\n0.60 0.1412 0.0\n0.65 0.1870 0.0\n0.70 0.2412 0.0\n0.77 0.3288 0.0\n0.82 0.4000 0.0\n0.85 0.4450 0.0 / TABLE NO. 01\n-- SGAS KRG PCGW\n-- FRAC PSIA\n-- -------- -------- -------\n0.00 0.0000 0.0\n0.05 0.0000 0.0\n0.10 0.0000 0.0\n0.15 0.0000 0.0\n0.20 0.0002 0.0\n0.25 0.0010 0.0\n0.30 0.0062 0.0\n0.35 0.0140 0.0\n0.40 0.0273 0.0\n0.45 0.0450 0.0\n0.50 0.0707 0.0\n0.55 0.1020 0.0\n0.60 0.1412 0.0\n0.65 0.1870 0.0\n0.70 0.2412 0.0\n0.77 0.3288 0.0\n0.82 0.4000 0.0\n0.85 0.4450 0.0 / TABLE NO. 02\nThe example defines two GSF tables for when gas and water are present in the input deck. In the tables the gas-water capillary pressure data has been set to zero.\n| Note GSF is a compositional keyword in the commercial compositional simulator, and will therefore cause an error in the commercial black-oil simulator. Currently, both the GSF and WSF keywords can only be used with the CO2STORE and H2STORE models. |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"fixed","variadic_record":true},"HA":{"name":"HA","sections":["PROPS","REGIONS"],"supported":false,"summary":"The HA series of keywords defines the history match end-point gradient parameters used to set the additive cumulative end point data, for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section. In addition, the End-Point Scaling option must also be activated by the ENDSCALE keyword which is also in the RUNSPEC section. The keyword consists of the first two characters of “HA” followed by the end-point keyword shown in Table 8.45, for example, HASWL.","parameters":[],"example":"| Type | End-Point Keyword | Oil-Water End-Point Definitions |\n|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|\n| Saturation | SWL | Connate water saturation, that is the smallest water saturation in a water saturation function table. |\n| SWCR | Critical water saturation, that is the largest water saturation for which the water relative permeability is zero. | |\n| SOWCR | Critical oil-in-water saturation, that is the largest oil saturation for which the oil relative permeability is zero in an oil-water system. | |\n| Relative Permeability | KRW | Relative permeability of water at the maximum water saturation (normally the maximum water saturation is one). |\n| KRO | Relative permeability of oil at the maximum oil saturation. | |\n| KRWR | Relative permeability of water at the residual oil saturation or the residual gas saturation in a gas-water run. | |\n| KRORW | Relative permeability of oil at the critical water saturation. | |\n| Capillary Pressure | SWLPC | Capillary pressure connate water saturation, that is the smallest water saturation in a water saturation function table. |\n| Type | End-Point Keyword | Gas-Oil End-Point Definitions |\n| Saturation | SGL | Connate gas saturation, that is the smallest gas saturation in a gas saturation function table. |\n| SGCR | Critical gas saturation, that is the largest gas saturation for which the gas relative permeability is zero. | |\n| SOGCR | Critical oil-in-gas saturation, that is the larg"},"HDISP":{"name":"HDISP","sections":["PROPS"],"supported":false,"summary":"The HDISP keyword is combined with three character tracer name, specified by the TRACER keyword in the PROPS section, to define the tracer’s mechanical dispersivity parameters.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Length","Length"]}],"example":"","size_kind":"fixed","variadic_record":true},"HM":{"name":"HM","sections":["PROPS","REGIONS"],"supported":false,"summary":"The HM series of keywords defines the history match end-point gradient parameters used to set the multiplicative cumulative end point data, for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section. In addition, the End-Point Scaling option must also be activated by the ENDSCALE keyword which is also in the RUNSPEC section. The keyword consists of the first two characters of “HM” followed by the end-point keyword shown in Table 8.46, for example, HMSWL.","parameters":[],"example":"| Type | End-Point Keyword | Oil-Water End-Point Definitions |\n|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|\n| Saturation | SWL | Connate water saturation, that is the smallest water saturation in a water saturation function table. |\n| SWCR | Critical water saturation, that is the largest water saturation for which the water relative permeability is zero. | |\n| SOWCR | Critical oil-in-water saturation, that is the largest oil saturation for which the oil relative permeability is zero in an oil-water system. | |\n| Relative Permeability | KRW | Relative permeability of water at the maximum water saturation (normally the maximum water saturation is one). |\n| KRO | Relative permeability of oil at the maximum oil saturation. | |\n| KRWR | Relative permeability of water at the residual oil saturation or the residual gas saturation in a gas-water run. | |\n| KRORW | Relative permeability of oil at the critical water saturation. | |\n| Capillary Pressure | SWLPC | Capillary pressure connate water saturation, that is the smallest water saturation in a water saturation function table. |\n| Type | End-Point Keyword | Gas-Oil End-Point Definitions |\n| Saturation | SGL | Connate gas saturation, that is the smallest gas saturation in a gas saturation function table. |\n| SGCR | Critical gas saturation, that is the largest gas saturation for which the gas relative permeability is zero. | |\n| SOGCR | Critical oil-in-gas saturation, that is the larg"},"HMMROCK":{"name":"HMMROCK","sections":["PROPS"],"supported":false,"summary":"HMMROCK defines the rock compressibility gradient cumulative multipliers to be applied to the rock compressibility as defined by the ROCK keyword in the PROPS section, for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section. The constant should be a real number.","parameters":[],"example":""},"HMMROCKT":{"name":"HMMROCKT","sections":["PROPS"],"supported":false,"summary":"HMMROCKT defines the rock compaction gradient cumulative multipliers to be applied to the compaction data entered by the ROCTAB or ROCKTABH keywords in the PRROPS section, for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section","parameters":[],"example":""},"HMPROPS":{"name":"HMPROPS","sections":["PROPS","REGIONS"],"supported":false,"summary":"HMPROPS defines the start of a history match end-points section, for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section. In addition, the End-Point Scaling option must also be activated by the ENDSCALE keyword which is also in the RUNSPEC section. The keyword allows for the BOX, EQUALS, COPY, MINVALUE, MAXVALUE and ADD keywords to be used with the HA and HM series of keywords that reference the end-point scaling arrays, that is: HMKRG, HMKRGR, HMKRO, HMKRORG, HMKRORW, HMKRW, HMKRWR, HMPCW, HMPCG, HMSGCR, HMSOWCR, HMSOGCR, HMSWCR, and HMSWL keywords.","parameters":[],"example":"","size_kind":"none","size_count":0},"HMROCK":{"name":"HMROCK","sections":["PROPS"],"supported":false,"summary":"The HMROCK keyword defines the history match rock compressibility gradient parameters for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section","parameters":[{"index":1,"name":"TABLE_NUMBER","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"CALCULATE_GRADIENTS","description":"","units":{},"default":"0","value_type":"INT"}],"example":"","expected_columns":2,"size_kind":"list"},"HMROCKT":{"name":"HMROCKT","sections":["PROPS"],"supported":false,"summary":"The HMROCKT keyword defines the history match rock compaction gradient parameters for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section, and the history match rock compaction data has been entered via the HMMROCKT, ROCKTAB and ROCKTABH keywords in the PROPS section.","parameters":[{"index":1,"name":"TABLE_NUMBER","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"CALCULATE_GRADIENTS_1","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"CALCULATE_GRADIENTS_2","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":3,"size_kind":"list"},"HMRREF":{"name":"HMRREF","sections":["PROPS"],"supported":false,"summary":"The HMRREF keyword defines the history match rock compaction reference pressure gradient values to be used in conjunction with HMMROCKT, ROCKTAB and ROCKTABH keywords in the PROPS section, for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section. The history match rock compaction data is entered via the HMMROCKT, ROCKTAB and ROCKTABH keywords in the PROPS section.","parameters":[{"index":1,"name":"P_REF","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":2,"name":"P_DIM","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"}],"example":"","expected_columns":2,"size_kind":"fixed"},"HWKRO":{"name":"HWKRO","sections":["PROPS"],"supported":false,"summary":"HWKRO defines the scaling parameter for the oil relative permeability value at the connate water saturation (SWL), for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The data is used to scale the oil relative permeability in the high salinity water wet oil relative permeability saturation tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"HWKRORG":{"name":"HWKRORG","sections":["PROPS"],"supported":false,"summary":"HWKRORG defines the scaling parameter for the relative permeability of oil at the critical gas saturation (SGCR), for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The data is used to scale the oil relative permeability in the high salinity water wet oil relative permeability saturation tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"HWKRORW":{"name":"HWKRORW","sections":["PROPS"],"supported":false,"summary":"HWKRORW defines the scaling parameter for the relative permeability of oil at the critical water saturation (SWCR), for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The data is used to scale the oil relative permeability in the high salinity water wet oil relative permeability saturation tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"HWKRW":{"name":"HWKRW","sections":["PROPS"],"supported":false,"summary":"HWKRW defines the scaling parameter at the maximum oil relative permeability value (SWU), that is for Sw = 1.0, for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The data is used to scale the water relative permeability in the high salinity water wet water relative permeability saturation tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"HWKRWR":{"name":"HWKRWR","sections":["PROPS"],"supported":false,"summary":"HWKRWR defines the scaling parameter at the maximum oil relative permeability value (SWU), that is for Sw = 1.0, for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The data is used to scale the water relative permeability in the high salinity water wet water relative permeability saturation tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"HWPCW":{"name":"HWPCW","sections":["PROPS"],"supported":false,"summary":"HWPCW defines the maximum water-oil pressure values for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section. The keyword re-scales the oil-water capillary pressure in the high salinity water wet capillary saturation tables from a cell’s assigned saturation function by the grid block’s HWPCW value.","parameters":[],"example":"| [P sub c ~=~P sub{ c sub{TABLE} } LEFT( HWPCW OVER {P SUB {c sub {TABLE-MAX }}} RIGHT)] | (8.55) |\n|------------------------------------------------------------------------------------------|--------|","size_kind":"array"},"HWSOGCR":{"name":"HWSOGCR","sections":["PROPS"],"supported":false,"summary":"HWSOGCR defines the critical oil saturation with respect to gas (“SOGCR”), for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The data is used to scale the oil saturation in the high salinity water wet oil-gas relative permeability saturation tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"HWSOWCR":{"name":"HWSOWCR","sections":["PROPS"],"supported":false,"summary":"HWSOWCR defines the critical oil saturation with respect to water (“SOWCR”), for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The data is used to scale the oil saturation in the high salinity water wet water-oil relative permeability saturation tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"HWSWCR":{"name":"HWSWCR","sections":["PROPS"],"supported":false,"summary":"HWSWCR defines the critical water saturation (“SWCR”), for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The data is used to scale the water saturation in the high salinity water wet water-oil relative permeability saturation tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"HWSWL":{"name":"HWSWL","sections":["PROPS"],"supported":false,"summary":"HWSWL defines the connate water saturation (“SWL”), for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The data is used to scale the water saturation in the high salinity water wet water-oil relative permeability saturation tables, as well as the associated capillary pressure tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"HWSWLPC":{"name":"HWSWLPC","sections":["PROPS"],"supported":false,"summary":"HWSWLPC defines the capillary pressure connate water saturation (“SWLPC”), for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The data is used to scale the water saturation in the high salinity water wet water-oil capillary pressure tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"HWSWU":{"name":"HWSWU","sections":["PROPS"],"supported":false,"summary":"HWSWU defines the maximum water saturation(“SWU”), for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The data is used to scale the water saturation in the high salinity water wet water-oil relative permeability saturation tables, as well as the associated capillary pressure tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"HYDRHEAD":{"name":"HYDRHEAD","sections":["PROPS"],"supported":false,"summary":"The HYDRHEAD keyword defines the hydraulic head reference data for when the hydraulic head information is requested to be written out via one on the SUMMARY keywords (BHD, BHDF, etc.) in the SUMMARY section, or to the RESTART file via the HYDH or HYDHFW variables on the RESTART keyword","parameters":[{"index":1,"name":"REF_DEPTH","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":2,"name":"FRESHWATER_DENSITY","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Density"},{"index":3,"name":"REMOVE_DEPTH_TERMS","description":"","units":{},"default":"NO","value_type":"STRING"}],"example":"","expected_columns":3,"size_kind":"fixed","size_count":1},"HYMOBGDR":{"name":"HYMOBGDR","sections":["PROPS"],"supported":false,"summary":"This keyword, HYMOBGDR, activates the Carlson and Killough alternative secondary drainage hysteresis option for when the hysteresis option has been activated by the HYSTER variable on the SATOPTS keyword in the RUNSPEC section, and either the Carlson192\n Carlson, F. M. “Simulation of Relative Permeability Hysteresis to the Non-Wetting Phase,” paper SPE 10157, presented at the SPE Annual Technical Conference & Exhibition, San Antonio, Texas, USA (October 5-7, 1981). or Killough193\n Killough, J. E. “Reservoir Simulation with History-dependent Saturation Functions,” paper SPE 5106, Society of Petroleum Engineers Journal (1976) 16, No. 1, 37-48. models have been selected via the EHYSTR keyword in the PROPS section. Due to numerical accuracy, the gas saturation may fall below the critical gas saturation (SGCR), that is the largest gas saturation for which the gas relative permeability is zero, and gas would therefore be immobile until the gas saturation increases above SGCR. T...","parameters":[],"example":"--\n-- ACTIVATE CARLSON AND KILLOUGH ALTERNATIVE DRAINAGE HYSTERESIS OPTION\n--\nHYMOBGDR","size_kind":"none","size_count":0},"HYSTCHCK":{"name":"HYSTCHCK","sections":["PROPS"],"supported":false,"summary":"The HYSTCHCK keyword activate the hysteresis imbibition and drainage end-point check to validate that the two sets of end-points are consistent, for when the Hysteresis option has been activated by the HYSTER variable on the SATOPTS keyword in the RUNSPEC section, and the ENDSCALE keyword in the RUNSPEC section has been activated to enable end-point scaling.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"IKRG":{"name":"IKRG","sections":["PROPS"],"supported":null,"summary":"IKRG defines the imbibition scaling parameter at the maximum gas relative permeability value (ISGU), normally ISGU is equal to 1.0 - Swc, for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the HYSTER option on the SATOPTS keyword in the RUNSPEC section has to be activated to invoke the Hysteresis option. The SCALCERS keyword in the PROPS section defines the options used in the re-scaling process, the options are two point scaling and three point scaling.","parameters":[{"index":1,"name":"IKRG","description":"IKRG is an array of positive real numbers which are greater than zero and less than or equal to 1.0, that are the assigned scaling IKRG imbibition values for each cell in the model. Repeat counts may be used, for example 50*0.400. dimensionless","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"The example below defines an input box for the whole grid and for layers one to three, for layer one IKRG is set equal to 0.550, for layer two IKRG equals 0.575, and for layer three IKRG equals 0.600.\n--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS (NX=100, NY=100)\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1* 1* 1* 1* 1 3 / DEFINE BOX AREA\n--\n-- SET IKRG VALUES FOR THREE LAYERS IN THE MODEL\n--\nIKRG\n1000*0.550 1000*0.575 1000*0.600 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\n| [k sub rg ~=~k sub{ rg sub{`TABLE} } LEFT(IKRG OVER {k SUB {rg sub {`TABLE-MAX }}} RIGHT)] | (8.56) |\n|--------------------------------------------------------------------------------------------|--------|\n| No | Phases Present | Critical Saturation |\n|----|----------------|----------------------------------|\n| 1 | Gas-Oil | S critical = 1.0 – ISOGCR - ISWL |\n| 2 | Gas-Oil-Water | S critical = 1.0 – ISOGCR - ISWL |\n| 3 | Gas-Water | S critical = 1.0 – ISWCR |"},"IKRGR":{"name":"IKRGR","sections":["PROPS"],"supported":null,"summary":"IKRGR defines the imbibition scaling parameter at the relative permeability of gas at residual oil saturation (1 – ISOGCR), or critical water saturation in a gas-water run (Swc), for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the HYSTER option on the SATOPTS keyword in the RUNSPEC section has to be activated to invoke the Hysteresis option. The SCALCERS keyword in the PROPS section defines the options used in the re-scaling process, the options are two point scaling and three point scaling.","parameters":[{"index":1,"name":"IKRGR","description":"IKRGR is an array of positive real numbers which are greater than zero and less than or equal to 1.0, that are the assigned imbibition scaling IKRGR values for each cell in the model. In addition, for a given grid block IKGRGT should be less than IKRG. Repeat counts may be used, for example 50*0.400.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"The first example defines an input box for the whole grid and for layers one to three, for layer one IKRRG is set equal to 0.500, for layer two IKRGR equals 0.570, and for layer three IKRGR equals 0.580.\n--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS (NX=100, NY=100)\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1* 1* 1* 1* 1 3 / DEFINE BOX AREA\n--\n-- SET IKRGR VALUES FOR THREE LAYERS IN THE MODEL\n--\nIKRGR\n10000*0.500 10000*0.570 10000*0.580 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe next example does exactly the same thing using the EQUALS keyword instead.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nIKRGR’ 0.5000 1* 1* 1* 1* 1 1 / IKRGR FOR LAYER 1\nIKRGR’ 0.5700 1* 1* 1* 1* 2 2 / IKRGR FOR LAYER 2\nIKRGR’ 0.5800 1* 1* 1* 1* 3 3 / IKRGR FOR LAYER 3\n/\n| No | Phases Present | Critical Saturation |\n|----|----------------|----------------------------------|\n| 1 | Gas-Oil | S critical = 1.0 – ISOGCR - ISWL |\n| 2 | Gas-Oil-Water | S critical = 1.0 – ISOGCR - ISWL |\n| 3 | Gas-Water | S critical = 1.0 – ISWCR |"},"IKRO":{"name":"IKRO","sections":["PROPS"],"supported":null,"summary":"IKRO defines the scaling parameter for the imbibition oil relative permeability value at the connate water saturation (ISWL), for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the HYSTER option on the SATOPTS keyword in the RUNSPEC section has to be activated to invoke the Hysteresis option. The SCALCERS keyword in the PROPS section defines the options used in the re-scaling process, the options are two point scaling and three point scaling.","parameters":[{"index":1,"name":"IKRO","description":"IKRO is an array of positive real numbers which are greater than zero and less than or equal to 1.0, that are the assigned imbibition scaling IKRO values for each cell in the model. Repeat counts may be used, for example 50*0.500.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"The example below defines an input box for the whole grid and for layers one to three, for layer one IKRO is set equal to 0.850, for layer two IKRO equals 0.875, and for layer three IKRO equals 0.900.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nIKRO 0.8500 1* 1* 1* 1* 1 1 / IKRO FOR LAYER 1\nIKRO 0.8750 1* 1* 1* 1* 2 2 / IKRO FOR LAYER 2\nIKRO 0.9000 1* 1* 1* 1* 3 3 / IKRO FOR LAYER 3\n/\n| [k sub ro ~=~k sub{ ro sub{`TABLE} } LEFT(IKRO OVER {k SUB {ro sub {`TABLE-MAX }}} RIGHT)] | (8.57) |\n|--------------------------------------------------------------------------------------------|--------|\n| No | Keywords Present | Critical Saturation |\n|----|------------------|-------------------------------|\n| 1 | KRORW | S critical = 1.0 – SWCR - SGL |\n| 2 | KRORG | S critical = 1.0 – SGCR - SWL |"},"IKRORG":{"name":"IKRORG","sections":["PROPS"],"supported":null,"summary":"IKRORG defines the scaling parameter for the imbibition relative permeability of oil at the critical gas saturation (ISGCR), for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the HYSTER option on the SATOPTS keyword in the RUNSPEC section has to be activated to invoke the Hysteresis option. The SCALCERS keyword in the PROPS section defines the options used in the re-scaling process, the options are two point scaling and three point scaling.","parameters":[{"index":1,"name":"IKRORG","description":"IKRORG is an array of positive real numbers which are greater than zero and less than or equal to 1.0, that are the assigned imbibition scaling IKRORG values for each cell in the model. Repeat counts may be used, for example 50*0.850.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"The first example defines an input box for the whole grid and for layers one to three, for layer one IKRORG is set equal to 0.755, for layer two IKRORG equals 0.775, and for layer three IKRORG equals 0.800.\n--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS (NX=100, NY=100)\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1* 1* 1* 1* 1 3 / DEFINE BOX AREA\n--\n-- SET IKRORG VALUES FOR THREE LAYERS IN THE MODEL\n--\nIKRORG\n10000*0.755 10000*0.775 10000*0.800 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe next example does exactly the same thing using the EQUALS keyword instead.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nIKRORG 0.7550 1* 1* 1* 1* 1 1 / IKRORG FOR LAYER 1\nIKRORG 0.7750 1* 1* 1* 1* 2 2 / IKRORG FOR LAYER 2\nIKRORG 0.8000 1* 1* 1* 1* 3 3 / IKRORG FOR LAYER 3\n/\n| No | Keywords Present | Critical Saturation |\n|----|------------------|---------------------------------|\n| 1 | IKRORW | S critical = 1.0 – ISWCR - ISGL |\n| 2 | IKRORG | S critical = 1.0 – ISGCR - SWL |"},"IKRORW":{"name":"IKRORW","sections":["PROPS"],"supported":null,"summary":"IKRORW defines the scaling parameter for the imbibition relative permeability of oil at the critical water saturation (ISWCR), for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the HYSTER option on the SATOPTS keyword in the RUNSPEC section has to be activated to invoke the Hysteresis option. The SCALECRS keyword in the PROPS section defines the options used in the re-scaling process, the options are two point scaling and three point scaling.","parameters":[{"index":1,"name":"IKRORW","description":"IKRORW is an array of positive real numbers which are greater than zero and less than or equal to 1.0, that are the assigned imbibition scaling IKRORW values for each cell in the model. Repeat counts may be used, for example 50*0.850","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"The first example defines an input box for the whole grid and for layers one to three, for layer one IKRORW is set equal to 0.755, for layer two IKRORW equals 0.775, and for layer three IKRORW equals 0.800.\n--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS (NX=100, NY=100)\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1* 1* 1* 1* 1 3 / DEFINE BOX AREA\n--\n-- SET IKRORW VALUES FOR THREE LAYERS IN THE MODEL\n--\nIKRORW\n10000*0.755 10000*0.775 10000*0.800 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe next example does exactly the same thing using the EQUALS keyword instead.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nIKRORW 0.7550 1* 1* 1* 1* 1 1 / IKRORW FOR LAYER 1\nIKRORW 0.7750 1* 1* 1* 1* 2 2 / IKRORW FOR LAYER 2\nIKRORW 0.8000 1* 1* 1* 1* 3 3 / IKRORW FOR LAYER 3\n/\n| No | Keywords Present | Critical Saturation |\n|----|------------------|---------------------------------|\n| 1 | IKRORW | S critical = 1.0 – ISWCR - ISGL |\n| 2 | IKRORG | S critical = 1.0 – ISGCR - ISWL |"},"IKRW":{"name":"IKRW","sections":["PROPS"],"supported":null,"summary":"IKRW defines the scaling parameter at the maximum imbibition water relative permeability value (ISWU), that is for Sw = 1.0, for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the HYSTER option on the SATOPTS keyword in the RUNSPEC section has to be activated to invoke the Hysteresis option. The SCALCERS keyword in the PROPS section defines the options used in the re-scaling process, the options are two point scaling and three point scaling.","parameters":[{"index":1,"name":"IKRW","description":"IKRW is an array of positive real numbers which are greater than zero and less than or equal to 1.0, that are the assigned imbibition scaling IKRW values for each cell in the model. Repeat counts may be used, for example 50*1.000.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"The example below defines an input box for the whole grid and for layers one to three, for layer one IKRW is set equal to 0.850, for layer two IKRW equals 0.875, and for layer three IKRW equals 0.900.\n--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS (NX=100, NY=100)\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1* 1* 1* 1* 1 3 / DEFINE BOX AREA\n--\n-- SET IKRW VALUES FOR THREE LAYERS IN THE MODEL\n--\nIKRW\n10000*0.850 10000*0.875 10000*0.900 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\n| [k sub rw ~=~k sub{ rw sub{`TABLE} } LEFT(IKRW OVER {k SUB {rw sub {`TABLE-MAX }}} RIGHT)] | (8.58) |\n|--------------------------------------------------------------------------------------------|--------|\n| No | Phases Present | Critical Saturation |\n|----|----------------|----------------------------------|\n| 1 | Gas-Oil | S critical = 1.0 – ISOWCR - ISGL |\n| 2 | Gas-Oil-Water | S critical = 1.0 – ISOWCR - ISGL |\n| 3 | Gas-Water | S critical = 1.0 – ISGCR |"},"IKRWR":{"name":"IKRWR","sections":["PROPS"],"supported":null,"summary":"IKRWR defines the scaling parameter at the imbibition critical oil to water saturation value (ISOWCR), for the imbibition water relative permeability curve, for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the HYSTER option on the SATOPTS keyword in the RUNSPEC section has to be activated to invoke the Hysteresis option. The SCALCERS keyword in the PROPS section defines the options used in the re-scaling process, the options are two point scaling and three point scaling.","parameters":[{"index":1,"name":"IKRWR","description":"IKRWR is an array of positive real numbers which are greater than zero and less than or equal to 1.0, that are the assigned imbibition scaling IKRWR values for each cell in the model. Repeat counts may be used, for example 50*1.000.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"The first example defines an input box for the whole grid and for layers one to three, for layer one IKRWR is set equal to 0.755, for layer two IKRWR equals 0.775, and for layer three IKRWR equals 0.800.\n--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS (NX=100, NY=100)\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1* 1* 1* 1* 1 3 / DEFINE BOX AREA\n--\n-- SET IKRWR VALUES FOR THREE LAYERS IN THE MODEL\n--\nIKRWR\n10000*0.755 10000*0.775 10000*0.800 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe next example does exactly the same thing using the EQUALS keyword instead.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nIKRWR 0.7550 1* 1* 1* 1* 1 1 / IKRWR FOR LAYER 1\nIKRWR 0.7750 1* 1* 1* 1* 2 2 / IKRWR FOR LAYER 2\nIKRWR 0.8000 1* 1* 1* 1* 3 3 / IKRWR FOR LAYER 3\n/\n| No | Phases Present | Critical Saturation |\n|----|----------------|----------------------------------|\n| 1 | Gas-Oil | S critical = 1.0 – ISOWCR - ISGL |\n| 2 | Gas-Oil-Water | S critical = 1.0 – ISOWCR - ISGL |\n| 3 | Gas-Water | S critical = 1.0 – ISGCR |"},"IMKRVD":{"name":"IMKRVD","sections":["PROPS"],"supported":false,"summary":"This keyword defines the maximum imbibition oil, gas, and water relative permeability versus depth for the three phases. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the HYSTER option on the SATOPTS keyword in the RUNSPEC section has to be activated to invoke the Hysteresis option.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Length","1","1","1","1","1","1","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"IMPCVD":{"name":"IMPCVD","sections":["PROPS"],"supported":false,"summary":"This keyword defines the maximum imbibition gas-oil and water-oil capillary pressure values versus depth for when the end-point scaling option has been invoked by the ENDSCALE keyword in the RUNSPEC section and the HYSTER option on the SATOPTS keyword in the RUNSPEC section has been activated to invoke the Hysteresis option.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Length","Pressure","Pressure"]}],"example":"","size_kind":"fixed","variadic_record":true},"IMPTVD":{"name":"IMPTVD","sections":["PROPS"],"supported":false,"summary":"This keyword defines the variation of the imbibition relative permeability saturation end-points (SWL, SWCR, etc.) for all three phases versus depth., for when the end-point scaling option has been invoked by the ENDSCALE keyword in the RUNSPEC section, and the HYSTER option on the SATOPTS keyword in the RUNSPEC section has been activated to invoke the Hysteresis option. This functionality is not supported in OPM Flow.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Length","1","1","1","1","1","1","1","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"IMSPCVD":{"name":"IMSPCVD","sections":["PROPS"],"supported":false,"summary":"This keyword defines the imbibition capillary pressure gas and water connate saturations values versus depth for when the end-point scaling option has been invoked by the ENDSCALE keyword in the RUNSPEC section, and the HYSTER option on the SATOPTS keyword in the RUNSPEC section has been activated to invoke the Hysteresis option. This functionality is not supported in OPM Flow.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Length","1","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"INTPC":{"name":"INTPC","sections":["PROPS"],"supported":false,"summary":"The INTPC keyword activates the integrated capillary pressure option for the oil, gas or both phases, for when a Dual Porosity model has been activated by either the DUALPORO or DUALPERM keywords in the RUNSPEC section. In addition, the keyword can only be used if the Gravity Drainage option has been specified by either the GRAVDR or GRAVDRM in the RUNSPEC section. Basically, activating this feature results in the simulator adjusting the capillary pressure curves by integrating the matrix capillary pressure curves over the matrix block height to calculate the average saturation.","parameters":[{"index":1,"name":"PHASE","description":"","units":{},"default":"BOTH","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"IONXROCK":{"name":"IONXROCK","sections":["PROPS"],"supported":false,"summary":"The IONXROCK keyword activates ion exchange and defines the ion exchange constant by saturation table regions, for when the brine phase has been activated by the BRINE keyword and the Multi-Component Brine model, that allows for the water phase to have multiple water salinities, has been activated by the ECLMC keyword. Both keywords are in the RUNSPEC section.","parameters":[{"index":1,"name":"VALUE","description":"","units":{},"default":"0","value_type":"DOUBLE"}],"example":"","expected_columns":1,"size_kind":"fixed"},"IONXSURF":{"name":"IONXSURF","sections":["PROPS"],"supported":false,"summary":"The IONXROCK keyword activates ion exchange on surfactant micellae194\n Particle of colloidal dimensions that exists in equilibrium with the molecules or ions in solution from which it is formed. A micella or micelle (plural micellae or micelles, respectively) is an aggregate (or supramolecular assembly) of surfactant molecules dispersed in a liquid colloid. A typical micella in aqueous solution forms an aggregate with the hydrophilic \"head\" regions in contact with surrounding solvent, sequestering the hydrophobic single-tail regions in the micella centre (https://en.wikipedia.org/wiki/Micelle). and defines the ion exchange constant by surfactant equivalent molecular weight for saturation table regions, for when the brine and surfactant phases has been activated by the BRINE and SURFACT keywords, and the Multi-Component Brine model, that allows for the water phase to have multiple water salinities, has been activated by the ECLMC keyword. All three keywords are in the RUNSPEC se...","parameters":[{"index":1,"name":"MOLECULAR_WEIGHT","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":2,"name":"ION_EXCH_CONST","description":"","units":{},"default":"0","value_type":"DOUBLE"}],"example":"","expected_columns":2,"size_kind":"fixed"},"IPCG":{"name":"IPCG","sections":["PROPS"],"supported":null,"summary":"IPCG defines the maximum imbibition gas-oil capillary pressure values for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the HYSTER option on the SATOPTS keyword in the RUNSPEC section has to be activated to invoke the hysteresis option. The keyword can be used with all grid types.","parameters":[{"index":1,"name":"IPCG","description":"IPCG is an array of positive real numbers assigning the maximum imbibition gas capillary pressure values for each cell in the model. Repeat counts may be used, for example 30*100.0.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK IPCG DATA FOR ALL CELLS (BASED ON NX x NY x NZ = 300)\n--\nIPCG\n100*50.0 100*75.0 100*125.0 /\nThe above example defines the IPCG for 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.\n| [P sub c ~=~P sub{ c sub{TABLE} } LEFT( IPCG OVER {P SUB {c sub {TABLE-MAX }}} RIGHT)] | (8.59) |\n|-----------------------------------------------------------------------------------------|--------|","size_kind":"array"},"IPCW":{"name":"IPCW","sections":["PROPS"],"supported":null,"summary":"IPCW defines the maximum imbibition water-oil or water-gas capillary pressure values for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the HYSTER option on the SATOPTS keyword in the RUNSPEC section has to be activated to invoke the hysteresis option. The keyword can be used with all grid types.","parameters":[{"index":1,"name":"IPCW","description":"IPCW is an array of positive real numbers assigning the maximum imbibition water capillary pressure values for each cell in the model. Repeat counts may be used, for example 30*100.0.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK IPCW DATA FOR ALL CELLS (BASED ON NX x NY x NZ = 300)\n--\nIPCW\n100*50.0 100*75.0 100*125.0 /\nThe above example defines the IPCW for 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.\n| [P sub c ~=~P sub{ c sub{TABLE} } LEFT( IPCW OVER {P SUB {c sub {TABLE-MAX }}} RIGHT)] | (8.60) |\n|-----------------------------------------------------------------------------------------|--------|","size_kind":"array"},"ISGCR":{"name":"ISGCR","sections":["PROPS"],"supported":null,"summary":"ISGCR defines the imbibition critical gas saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE keyword in the RUNSPEC section and the hysteresis model option has been activated on the SATOPTS keyword in the RUNSPEC section. The critical gas saturation is defined as the maximum gas saturation for which the gas relative permeability is zero in a two-phase relative permeability table.","parameters":[{"index":1,"name":"ISGCR","description":"ISGCR is an array of real numbers assigning the critical gas saturation values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.03","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT ISGCR DATA FOR CELLS (NX x NY x NZ = 300)\nISGCR\n300*0.050 /\nThe above example defines a constant critical gas saturation of 0.05 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"ISGL":{"name":"ISGL","sections":["PROPS"],"supported":null,"summary":"ISGL defines the imbibition connate gas saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE keyword in the RUNSPEC section and the hysteresis model option has been activated on the SATOPTS keyword in the RUNSPEC section. The connate gas saturation is defined as the minimum gas saturation in a two-phase gas relative permeability table.","parameters":[{"index":1,"name":"ISGL","description":"ISGL is an array of real numbers assigning the connate gas saturation values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.03 dimensionless","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT ISGL DATA FOR ALL CELLS (NX x NY x NZ = 300)\nISGL\n300*0.030 /\nThe above example defines a constant connate gas saturation of 0.03 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"ISGLPC":{"name":"ISGLPC","sections":["PROPS"],"supported":null,"summary":"ISGLPC defines the imbibition connate gas saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE keyword in the RUNSPEC section and the hysteresis model option has been activated on the SATOPTS keyword in the RUNSPEC section. The connate gas saturation is defined as the minimum gas saturation in a two-phase gas relative permeability table. The keyword only applies the scaling to the imbibition capillary pressures tables, unlike the ISGL keyword that applies the scaling to both the capillary pressure and relative permeability tables. The keyword can be used with all grid types.","parameters":[{"index":1,"name":"ISGLPC","description":"ISGLPC is an array of real numbers assigning the connate gas saturation values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. If ISGLPC is omitted from the input deck the values will be defaulted to those on the ISGL series of keywords. If the ISGL series of keywords are missing from the input deck then the values are taken from the cell allocated capillary pressure table. Repeat counts may be used, for example 30*0.03","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from SGL or from the cell allocated capillary pressure table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT ISGLPC DATA FOR ALL CELLS\n– (NX x NY x NZ = 300)\nISGLPC\n300*0.030 /\nThe above example defines a constant connate gas saturation of 0.03 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"ISGU":{"name":"ISGU","sections":["PROPS"],"supported":null,"summary":"ISGU defines the imbibition maximum gas saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE keyword in the RUNSPEC section and the hysteresis model option has been activated on the SATOPTS keyword in the RUNSPEC section. The maximum gas saturation is defined as the maximum gas saturation in a two-phase gas relative permeability table. The keyword can be used with all grid types.","parameters":[{"index":1,"name":"ISGU","description":"ISGU is an array of real numbers assigning the maximum gas saturation values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.70","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT ISGU DATA FOR ALL CELLS (NX x NY x NZ = 300)\nISGU\n300*0.700 /\nThe above example defines a constant connate gas saturation of 0.70 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"ISOGCR":{"name":"ISOGCR","sections":["PROPS"],"supported":null,"summary":"ISOGCR defines the imbibition critical oil saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE in the RUNSPEC section and the hysteresis model option has been activated on the SATOPTS keyword in the RUNSPEC section. The critical oil saturation with respect to gas is defined as the maximum oil saturation for which the oil relative permeability is zero in a two-phase gas-oil relative permeability table. The keyword can be used with all grid types.","parameters":[{"index":1,"name":"ISOGCR","description":"ISOGCR is an array of real numbers assigning the critical oil saturation with respect to gas values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.30","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT ISOGCR DATA FOR ALL CELLS\n-- (NX x NY x NZ = 300)\n--\nISOGCR\n300*0.200 /\nThe above example defines a constant critical gas saturation of 0.20 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"ISOWCR":{"name":"ISOWCR","sections":["PROPS"],"supported":null,"summary":"ISOWCR defines the imbibition critical oil saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE in the RUNSPEC section and the hysteresis model option has been activated on the SATOPTS keyword in the RUNSPEC section. The critical oil saturation with respect to water is defined as the maximum oil saturation for which the oil relative permeability is zero in a two-phase oil-water relative permeability table. The keyword can be used with all grid types.","parameters":[{"index":1,"name":"ISOWCR","description":"ISOWCR is an array of real numbers assigning the critical oil saturation with respect to water values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.30","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT ISOWCR DATA FOR ALL CELLS\n-- (NX x NY x NZ = 300)\n--\nISOWCR\n300*0.200 /\nThe above example defines a constant critical gas saturation of 0.20 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section","size_kind":"array"},"ISWCR":{"name":"ISWCR","sections":["PROPS"],"supported":null,"summary":"ISWCR defines the imbibition critical water saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE in the RUNSPEC section and the hysteresis model option has been activated on the SATOPTS keyword in the RUNSPEC section. The critical water saturation is defined as the maximum water saturation for which the water relative permeability is zero in a two-phase relative permeability table. The keyword can be used with all grid types.","parameters":[{"index":1,"name":"ISWCR","description":"ISWCR is an array of real numbers assigning the critical water saturation values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.20","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT ISWCR DATA FOR ALL CELLS\n-- (NX x NY x NZ = 300)\n--\nISWCR\n300*0.200 /\nThe above example defines a constant critical water saturation of 0.20 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"ISWL":{"name":"ISWL","sections":["PROPS"],"supported":null,"summary":"ISWL defines the imbibition connate water saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE in the RUNSPEC section and the hysteresis model option has been activated on the SATOPTS keyword in the RUNSPEC section. The connate water saturation is defined as the minimum water saturation in a two-phase water relative permeability table.","parameters":[{"index":1,"name":"ISWL","description":"ISWL is an array of real numbers assigning the connate water saturation values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.15","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT ISWL DATA FOR ALL CELLS (NX x NY x NZ = 300)\n--\nISWL\n300*0.150 /\nThe above example defines a constant connate water saturation of 0.15 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"ISWLPC":{"name":"ISWLPC","sections":["PROPS"],"supported":null,"summary":"ISWLPC defines the imbibition connate water saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE in the RUNSPEC section and the hysteresis model option has been activated on the SATOPTS keyword in the RUNSPEC section. The connate water saturation is defined as the minimum water saturation in a two-phase water relative permeability table. The keyword only applies the scaling to the imbibition capillary pressures tables, unlike the ISWL keyword that applies the scaling to both the capillary pressure and relative permeability tables. The keyword can be used with all grid types.","parameters":[{"index":1,"name":"ISWLPC","description":"ISWLPC is an array of real numbers assigning the connate water saturation values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. If ISWLPC is omitted from the input deck the values will be defaulted to those on the ISGL series of keywords. If the ISWL series of keywords are missing from the input deck then the values are taken from the cell allocated capillary pressure table. Repeat counts may be used, for example 30*0.15","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from SWL or from the cell allocated capillary pressure table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT ISWLPC DATA FOR ALL CELLS (\n-- NX x NY x NZ = 300)\n--\nISWLPC\n300*0.150 /\nThe above example defines a constant connate water saturation of 0.15 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"ISWU":{"name":"ISWU","sections":["PROPS"],"supported":null,"summary":"ISWU defines the imbibition maximum water saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE in the RUNSPEC section and the hysteresis model option has been activated on the SATOPTS keyword in the RUNSPEC section. The maximum water saturation is defined as the maximum water saturation in a two-phase water relative permeability table. The keyword can be used with all grid types.","parameters":[{"index":1,"name":"ISWU","description":"ISWU is an array of real numbers assigning the maximum water saturation values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.70","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT ISWU DATA FOR ALL CELLS (NX x NY x NZ = 300)\n--\nISWU\n300*0.700 /\nThe above example defines a constant connate gas saturation of 0.70 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"KRG":{"name":"KRG","sections":["PROPS"],"supported":null,"summary":"KRG defines the scaling parameter at the maximum drainage gas relative permeability value (SGU), normally SGU is equal to 1.0 - Swc, for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. The SCALCERS keyword in the PROPS section defines the options used in the re-scaling process, the options are two point scaling and three point scaling.","parameters":[{"index":1,"name":"KRG","description":"KRG is an array of positive real numbers which are greater than zero and less than or equal to 1.0, that are the assigned scaling KRG values for each cell in the model. Repeat counts may be used, for example 50*0.400. dimensionless","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"The first example defines an input box for the whole grid and for layers one to three, for layer one KRG is set equal to 0.555, for layer two KRG equals 0.575, and for layer three KRG equals 0.600.\n--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS (NX=100, NY=100)\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1* 1* 1* 1* 1 3 / DEFINE BOX AREA\n--\n-- SET KRG VALUES FOR THREE LAYERS IN THE MODEL\n--\nKRG\n10000*0.555 10000*0.575 10000*0.600 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe next example does exactly the same thing using the EQUALS keyword instead.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nKRG 0.5550 1* 1* 1* 1* 1 1 / KRG FOR LAYER 1\nKRG 0.5750 1* 1* 1* 1* 2 2 / KRG FOR LAYER 2\nKRG 0.6000 1* 1* 1* 1* 3 3 / KRG FOR LAYER 3\n/\n| [k sub rg ~=~k sub{ rg sub{`TABLE} } LEFT(KRG OVER {k SUB {rg sub {`TABLE-MAX }}} RIGHT)] | (8.61) |\n|-------------------------------------------------------------------------------------------|--------|\n| No | Phases Present | Critical Saturation |\n|----|----------------|--------------------------------|\n| 1 | Gas-Oil | S critical = 1.0 – SOGCR - SWL |\n| 2 | Gas-Oil-Water | S critical = 1.0 – SOGCR - SWL |\n| 3 | Gas-Water | S critical = 1.0 – SWCR |"},"KRGR":{"name":"KRGR","sections":["PROPS"],"supported":null,"summary":"KRGR defines the scaling parameter at the relative permeability of gas at residual oil saturation (1 – SOGCR), or critical water saturation in a gas-water run (Swc), for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. The SCALCERS keyword in the PROPS section defines the options used in the re-scaling process, the options are two point scaling and three point scaling.","parameters":[{"index":1,"name":"KRGR","description":"KRGR is an array of positive real numbers which are greater than zero and less than or equal to 1.0, that are the assigned scaling KRGR values for each cell in the model. In addition, for a given grid block KGRG should be less than KRG. Repeat counts may be used, for example 50*0.400.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"The first example defines an input box for the whole grid and for layers one to three, for layer one KRGR is set equal to 0.500, for layer two KRGR equals 0.570, and for layer three KRGR equals 0.580.\n--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS (NX=100, NY=100)\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1* 1* 1* 1* 1 3 / DEFINE BOX AREA\n--\n-- SET KRGR VALUES FOR THREE LAYERS IN THE MODEL\n--\nKRGR\n10000*0.500 10000*0.570 10000*0.580 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe next example does exactly the same thing using the EQUALS keyword instead.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nKRGR 0.5000 1* 1* 1* 1* 1 1 / KRGR FOR LAYER 1\nKRGR 0.5700 1* 1* 1* 1* 2 2 / KRGR FOR LAYER 2\nKRGR 0.5800 1* 1* 1* 1* 3 3 / KRGR FOR LAYER 3\n/\n| No | Phases Present | Critical Saturation |\n|----|----------------|--------------------------------|\n| 1 | Gas-Oil | S critical = 1.0 – SOGCR - SWL |\n| 2 | Gas-Oil-Water | S critical = 1.0 – SOGCR - SWL |\n| 3 | Gas-Water | S critical = 1.0 – SWCR |"},"KRO":{"name":"KRO","sections":["PROPS"],"supported":null,"summary":"KRO defines the scaling parameter for the drainage oil relative permeability value at the connate water saturation (SWL), for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. The SCALCERS keyword in the PROPS section defines the options used in the re-scaling process, the options are two point scaling and three point scaling.","parameters":[{"index":1,"name":"KRO","description":"KRO is an array of positive real numbers which are greater than zero and less than or equal to 1.0, that are the assigned scaling KRO values for each cell in the model. Repeat counts may be used, for example 50*0.500.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"The first example defines an input box for the whole grid and for layers one to three, for layer one KRO is set equal to 0.855, for layer two KRO equals 0.875, and for layer three KRO equals 0.900.\n--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS (NX=100, NY=100)\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1* 1* 1* 1* 1 3 / DEFINE BOX AREA\n--\n-- SET KRO VALUES FOR THREE LAYERS IN THE MODEL\n--\nKRO\n10000*0.855 10000*0.875 10000*0.900 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe next example does exactly the same thing using the EQUALS keyword instead.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nKRO 0.8550 1* 1* 1* 1* 1 1 / KRO FOR LAYER 1\nKOG 0.8750 1* 1* 1* 1* 2 2 / KRO FOR LAYER 2\nKRO 0.9000 1* 1* 1* 1* 3 3 / KRO FOR LAYER 3\n/\n| [k sub ro ~=~k sub{ ro sub{`TABLE} } LEFT(KRO OVER {k SUB {ro sub {`TABLE-MAX }}} RIGHT)] | (8.62) |\n|-------------------------------------------------------------------------------------------|--------|\n| No | Keywords Present | Critical Saturation |\n|----|------------------|-------------------------------|\n| 1 | KRORW | S critical = 1.0 – SWCR - SGL |\n| 2 | KRORG | S critical = 1.0 – SGCR - SWL |"},"KRORG":{"name":"KRORG","sections":["PROPS"],"supported":null,"summary":"KRORG defines the scaling parameter for the drainage relative permeability of oil at the critical gas saturation (SGCR), for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. The SCALCERS keyword in the PROPS section defines the options used in the re-scaling process, the options are two point scaling and three point scaling.","parameters":[{"index":1,"name":"KRORG","description":"KRORG is an array of positive real numbers which are greater than zero and less than or equal to 1.0, that are the assigned scaling KRORG values for each cell in the model. Repeat counts may be used, for example 50*0.850.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"The first example defines an input box for the whole grid and for layers one to three, for layer one KRORG is set equal to 0.755, for layer two KRORG equals 0.775, and for layer three KRORG equals 0.800.\n--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS (NX=100, NY=100)\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1* 1* 1* 1* 1 3 / DEFINE BOX AREA\n--\n-- SET KRORG VALUES FOR THREE LAYERS IN THE MODEL\n--\nKRORG\n10000*0.755 10000*0.775 10000*0.800 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe next example does exactly the same thing using the EQUALS keyword instead.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nKRORG 0.7550 1* 1* 1* 1* 1 1 / KRORG FOR LAYER 1\nKRORG 0.7750 1* 1* 1* 1* 2 2 / KRORG FOR LAYER 2\nKRORG 0.8000 1* 1* 1* 1* 3 3 / KRORG FOR LAYER 3\n/\n| No | Keywords Present | Critical Saturation |\n|----|------------------|-------------------------------|\n| 1 | KRORW | S critical = 1.0 – SWCR - SGL |\n| 2 | KRORG | S critical = 1.0 – SGCR - SWL |"},"KRORW":{"name":"KRORW","sections":["PROPS"],"supported":null,"summary":"KRORW defines the scaling parameter for the drainage relative permeability of oil at the critical water saturation (SWCR), for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. The SCALECRS keyword in the PROPS section defines the options used in the re-scaling process, the options are two point scaling and three point scaling.","parameters":[{"index":1,"name":"KRORW","description":"KRORW is an array of positive real numbers which are greater than zero and less than or equal to 1.0, that are the assigned scaling KRORW values for each cell in the model. Repeat counts may be used, for example 50*0.850","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"The first example defines an input box for the whole grid and for layers one to three, for layer one KRORW is set equal to 0.755, for layer two KRORW equals 0.775, and for layer three KRORW equals 0.800.\n--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS (NX=100, NY=100)\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1* 1* 1* 1* 1 3 / DEFINE BOX AREA\n--\n-- SET KRORW VALUES FOR THREE LAYERS IN THE MODEL\n--\nKRORW\n10000*0.755 10000*0.775 10000*0.800 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe next example does exactly the same thing using the EQUALS keyword instead.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nKRORW 0.7550 1* 1* 1* 1* 1 1 / KRORW FOR LAYER 1\nKRORW 0.7750 1* 1* 1* 1* 2 2 / KRORW FOR LAYER 2\nKRORW 0.8000 1* 1* 1* 1* 3 3 / KRORW FOR LAYER 3\n/\n| No | Keywords Present | Critical Saturation |\n|----|------------------|-------------------------------|\n| 1 | KRORW | S critical = 1.0 – SWCR - SGL |\n| 2 | KRORG | S critical = 1.0 – SGCR - SWL |"},"KRW":{"name":"KRW","sections":["PROPS"],"supported":null,"summary":"KRW defines the scaling parameter at the maximum drainage water relative permeability value (SWU), that is for Sw = 1.0, for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. The SCALCERS keyword in the PROPS section defines the options used in the re-scaling process, the options are two point scaling and three point scaling.","parameters":[{"index":1,"name":"KRW","description":"KRW is an array of positive real numbers which are greater than zero and less than or equal to 1.0, that are the assigned scaling KRW values for each cell in the model. Repeat counts may be used, for example 50*1.000.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"The first example defines an input box for the whole grid and for layers one to three, for layer one KRW is set equal to 0.855, for layer two KRW equals 0.875, and for layer three KRW equals 0.900.\n--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS (NX=100, NY=100)\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1* 1* 1* 1* 1 3 / DEFINE BOX AREA\n--\n-- SET KRW VALUES FOR THREE LAYERS IN THE MODEL\n--\nKRW\n10000*0.855 10000*0.875 10000*0.900 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe next example does exactly the same thing using the EQUALS keyword instead.\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nKRW 0.8550 1* 1* 1* 1* 1 1 / KRW FOR LAYER 1\nKRW 0.8750 1* 1* 1* 1* 2 2 / KRW FOR LAYER 2\nKRW 0.9000 1* 1* 1* 1* 3 3 / KRW FOR LAYER 3\n/\n| [k sub rw ~=~k sub{ rw sub{`TABLE} } LEFT(KRW OVER {k SUB {rw sub {`TABLE-MAX }}} RIGHT)] | (8.63) |\n|-------------------------------------------------------------------------------------------|--------|\n| No | Phases Present | Critical Saturation |\n|----|----------------|--------------------------------|\n| 1 | Gas-Oil | S critical = 1.0 – SOWCR - SGL |\n| 2 | Gas-Oil-Water | S critical = 1.0 – SOWCR - SGL |\n| 3 | Gas-Water | S critical = 1.0 – SGCR |"},"KRWR":{"name":"KRWR","sections":["PROPS"],"supported":null,"summary":"KRWR defines the scaling parameter at the drainage critical oil to water saturation value (SOWCR), for the drainage water relative permeability curve, for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. The SCALCERS keyword in the PROPS section defines the options used in the re-scaling process, the options are two point scaling and three point scaling.","parameters":[{"index":1,"name":"KRWR","description":"KRWR is an array of positive real numbers which are greater than zero and less than or equal to 1.0, that are the assigned scaling KRWR values for each cell in the model. Repeat counts may be used, for example 50*1.000.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"The first example defines an input box for the whole grid and for layers one to three, for layer one KRWR is set equal to 0.755, for layer two KRWR equals 0.775, and for layer three KRWR equals 0.800.\n--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS (NX=100, NY=100)\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1* 1* 1* 1* 1 3 / DEFINE BOX AREA\n--\n-- SET KRWR VALUES FOR THREE LAYERS IN THE MODEL\n--\nKRWR\n10000*0.755 10000*0.775 10000*0.800 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe next example does exactly the same thing using the EQUALS keyword instead.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nKRWR 0.7550 1* 1* 1* 1* 1 1 / KRWR FOR LAYER 1\nKRWR 0.7750 1* 1* 1* 1* 2 2 / KRWR FOR LAYER 2\nKRWR 0.8000 1* 1* 1* 1* 3 3 / KRWR FOR LAYER 3\n/\n| No | Phases Present | Critical Saturation |\n|----|----------------|--------------------------------|\n| 1 | Gas-Oil | S critical = 1.0 – SOWCR - SGL |\n| 2 | Gas-Oil-Water | S critical = 1.0 – SOWCR - SGL |\n| 3 | Gas-Water | S critical = 1.0 – SGCR |"},"LANGMPL":{"name":"LANGMPL","sections":["PROPS"],"supported":false,"summary":"This keyword, LANGMPL, defines the coal bed methane Langmuir Adsorption195\n Langmuir, Irving (June 1918). \"The Adsorption of Gases on Plane Surface of Glass, Mica and Platinum\". The Research Laboratory of the General Electric Company. 40 (9): 1361–1402. doi:10.1021/ja02242a004 pressure multiplier for each grid block, for when the Coal Bed Methane option has been activated via the COAL keyword in the RUNSPEC section. The keyword applies the multiplier to the pressure values in a cell’s allocated Langmuir table when calculating a cell’s adsorption capacity. See the LANGMUIR keyword in the PROPS section for specifying the Langmuir tables for the model.","parameters":[],"example":"","size_kind":"array"},"LANGMUIR":{"name":"LANGMUIR","sections":["PROPS"],"supported":false,"summary":"The LANGMUIR keyword defines the coal bed methane Langmuir Adsorption Isotherms196\n Langmuir, Irving (June 1918). \"The Adsorption of Gases on Plane Surface of Glass, Mica and Platinum\". The Research Laboratory of the General Electric Company. 40 (9): 1361–1402. doi:10.1021/ja02242a004 tables, for when the Coal Bed Methane option has been activated via the COAL keyword in the RUNSPEC section. See the COALNUM keyword in the GRID section for allocating the Langmuir tables to the grid blocks and also the LANGMPL keyword in the PROPS section for re-scaling the pressure values in the tables that are allocated to a cell.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Pressure","GasSurfaceVolume/Length*Length*Length","GasSurfaceVolume/Length*Length*Length"]}],"example":"","size_kind":"fixed","variadic_record":true},"LANGSOLV":{"name":"LANGSOLV","sections":["PROPS"],"supported":false,"summary":"The LANGMUIR keyword defines the coal bed methane Langmuir Adsorption Isotherms197\n Langmuir, Irving (June 1918). \"The Adsorption of Gases on Plane Surface of Glass, Mica and Platinum\". The Research Laboratory of the General Electric Company. 40 (9): 1361–1402. doi:10.1021/ja02242a004 Solvent tables, for when the Coal Bed Methane option has been activated via the COAL keyword and the Solvent phase has been declared by the SOLVENT keyword in the RUNSPEC section. See the COALNUM keyword in the GRID section for allocating the Langmuir solvent tables to the grid blocks, and also the LANGMUIR keyword in the PROPS section for defining the Langmuir Adsorption Isotherm tables. Keywords COALADS and COALPP, also in the PROPS section, are used to specify the relative adsorption data in runs containing the solvent phase.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Pressure","GasSurfaceVolume/Length*Length*Length"]}],"example":"","size_kind":"fixed","variadic_record":true},"LCUNIT":{"name":"LCUNIT","sections":["PROPS"],"supported":false,"summary":"The LCUNIT keyword defines the units for the Linear Combination facility which allows for a linear combination of oil, gas and water rates and volumes to be used as combination targets and constraints in controlling group and well production and injection data. See also the LINCOM in the SCHEDULE section that defines the actual linear combination equation.","parameters":[{"index":1,"name":"UNIT","description":"","units":{},"default":"UNIT","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"LKRO":{"name":"LKRO","sections":["PROPS"],"supported":false,"summary":"LKRO defines the scaling parameter for the oil relative permeability value at the connate water saturation (SWL), for all the cells in the model via an array, for when the Low Salt option and the End-point Scaling options has been activated by the LOWSALT and the ENDSCALE keywords in the RUNSPEC section. The data is used to scale the oil relative permeability in the low salinity oil wet oil relative permeability saturation tables.","parameters":[],"example":"","size_kind":"array"},"LKRORG":{"name":"LKRORG","sections":["PROPS"],"supported":false,"summary":"LKRORG defines the scaling parameter for the relative permeability of oil at the critical gas saturation (SGCR), for all the cells in the model via an array, for when the Low Salt option and the End-point Scaling options has been activated by the LOWSALT and the ENDSCALE keywords in the RUNSPEC section. The data is used to scale the oil relative permeability in the low salinity oil wet oil relative permeability saturation tables.","parameters":[],"example":"","size_kind":"array"},"LKRORW":{"name":"LKRORW","sections":["PROPS"],"supported":false,"summary":"LKRORW defines the scaling parameter for the relative permeability of oil at the critical water saturation (SWCR), for all the cells in the model via an array, for when the Low Salt option and the End-point Scaling options has been activated by the LOWSALT and the ENDSCALE keywords in the RUNSPEC section. The data is used to scale the oil relative permeability in the low salinity oil wet oil relative permeability saturation tables.","parameters":[],"example":"","size_kind":"array"},"LKRW":{"name":"LKRW","sections":["PROPS"],"supported":false,"summary":"LKRW defines the scaling parameter at the maximum oil relative permeability value (SWU), that is for Sw = 1.0, for all the cells in the model via an array, for when the Low Salt option and the End-point Scaling options has been activated by the LOWSALT and the ENDSCALE keywords in the RUNSPEC section. The data is used to scale the water relative permeability in the low salinity oil wet water relative permeability saturation tables.","parameters":[],"example":"","size_kind":"array"},"LKRWR":{"name":"LKRWR","sections":["PROPS"],"supported":false,"summary":"LKRWR defines the scaling parameter at the maximum oil relative permeability value (SWU), that is for Sw = 1.0, for all the cells in the model via an array, for when the Low Salt option and the End-point Scaling options has been activated by the LOWSALT and the ENDSCALE keywords in the RUNSPEC section. The data is used to scale the water relative permeability in the low salinity oil wet water relative permeability saturation tables.","parameters":[],"example":"","size_kind":"array"},"LPCW":{"name":"LPCW","sections":["PROPS"],"supported":false,"summary":"LPCW defines the maximum oil-water pressure values for all the cells in the model via an array, for when the Low Salt option and the End-point Scaling options has been activated by the LOWSALT and the ENDSCALE keywords in the RUNSPEC section. The keyword re-scales the oil-water capillary pressure in the low salinity oil wet capillary saturation tables from a cell’s assigned saturation function by the grid block’s LPCW value.","parameters":[],"example":"| [P sub c ~=~P sub{ c sub{TABLE} } LEFT( LPCW OVER {P SUB {c sub {TABLE-MAX }}} RIGHT)] | (8.64) |\n|-----------------------------------------------------------------------------------------|--------|","size_kind":"array"},"LSALTFNC":{"name":"LSALTFNC","sections":["PROPS"],"supported":false,"summary":"The LSALTFNC keyword defines the low salt weighting factors versus salt concentration functions for when the Low Salt option has been activated by the LOWSALT keyword in the RUNSPEC section. The tables are used to modify the oil and water relative permeability saturation end-points, as well as the water-oil capillary pressure end-points, for different salt concentrations within a grid cell.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Pressure","1","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"LSOGCR":{"name":"LSOGCR","sections":["PROPS"],"supported":false,"summary":"LSOGCR defines the critical oil saturation with respect to gas (“SOGCR”), for all the cells in the model via an array, for when the Low Salt option has been selected. The data is used to scale the oil saturation in the low salinity oil wet oil-gas relative permeability saturation tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"LSOWCR":{"name":"LSOWCR","sections":["PROPS"],"supported":false,"summary":"LSOWCR defines the critical oil saturation with respect to water (“SOWCR”), for all the cells in the model via an array, for when the Low Salt option has been selected. The data is used to scale the oil saturation in the low salinity oil wet water-oil relative permeability saturation tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"LSWCR":{"name":"LSWCR","sections":["PROPS"],"supported":false,"summary":"LSWCR defines the critical water saturation (“SWCR”), for all the cells in the model via an array, for when the Low Salt option has been selected. The data is used to scale the water saturation in the low salinity oil wet water-oil relative permeability saturation tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"LSWL":{"name":"LSWL","sections":["PROPS"],"supported":false,"summary":"LSWL defines the connate water saturation (“SWL”), for all the cells in the model via an array, for when the Low Salt option has been selected. The data is used to scale the water saturation in the low salinity oil wet water-oil relative permeability saturation tables, as well as the associated capillary pressure tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"LSWLPC":{"name":"LSWLPC","sections":["PROPS"],"supported":false,"summary":"LSWLPC defines the capillary pressure connate water saturation (“SWLPC”), for all the cells in the model via an array, for when the Low Salt option has been selected. The data is used to scale the water saturation in the low salinity oil wet water-oil capillary pressure tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"LSWU":{"name":"LSWU","sections":["PROPS"],"supported":false,"summary":"LSWU defines the maximum water saturation(“SWU”), for all the cells in the model via an array, for when the Low Salt option has been selected. The data is used to scale the water saturation in the low salinity oil wet water-oil relative permeability saturation tables, as well as the associated capillary pressure tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"LWKRO":{"name":"LWKRO","sections":["PROPS"],"supported":false,"summary":"LWKRO defines the scaling parameter for the oil relative permeability value at the connate water saturation (SWL), for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The data is used to scale the oil relative permeability in the low salinity water wet oil relative permeability saturation tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"LWKRORG":{"name":"LWKRORG","sections":["PROPS"],"supported":false,"summary":"LWKRORG defines the scaling parameter for the relative permeability of oil at the critical gas saturation (SGCR), for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The data is used to scale the oil relative permeability in the low salinity water wet oil relative permeability saturation tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"LWKRORW":{"name":"LWKRORW","sections":["PROPS"],"supported":false,"summary":"LWKRORW defines the scaling parameter for the relative permeability of oil at the critical water saturation (SWCR), for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The data is used to scale the oil relative permeability in the low salinity water wet oil relative permeability saturation tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"LWKRW":{"name":"LWKRW","sections":["PROPS"],"supported":false,"summary":"LWKRW defines the scaling parameter at the maximum water relative permeability value (SWU), that is for Sw = 1.0, for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The data is used to scale the water relative permeability in the low salinity water wet water relative permeability saturation tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"LWKRWR":{"name":"LWKRWR","sections":["PROPS"],"supported":false,"summary":"LWKRWR defines the scaling parameter at the critical oil to water saturation value (SOWCR), for the water relative permeability curve, for all the cells in the model via an array, and for when the Low Salt and Surfactant Wettability options have been selected. The data is used to scale the water relative permeability in the low salinity water wet water relative permeability saturation tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"LWPCW":{"name":"LWPCW","sections":["PROPS"],"supported":false,"summary":"LWPCW defines the maximum water-oil pressure values for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section. The keyword re-scales the oil-water capillary pressure in the low salinity water wet capillary saturation tables from the cell’s assigned saturation function by the grid block’s LWPCW value.","parameters":[],"example":"| [P sub c ~=~P sub{ c sub{TABLE} } LEFT( HWPCW OVER {P SUB {c sub {TABLE-MAX }}} RIGHT)] | (8.65) |\n|------------------------------------------------------------------------------------------|--------|","size_kind":"array"},"LWSOGCR":{"name":"LWSOGCR","sections":["PROPS"],"supported":false,"summary":"LWSOGCR defines the critical oil saturation with respect to gas (“SOGCR”), for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The data is used to scale the oil saturation in the low salinity water wet oil-gas relative permeability saturation tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"LWSOWCR":{"name":"LWSOWCR","sections":["PROPS"],"supported":false,"summary":"LWSOWCR defines the critical oil saturation with respect to water (“SOWCR”), for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The data is used to scale the oil saturation in the low salinity water wet water-oil relative permeability saturation tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"LWSWCR":{"name":"LWSWCR","sections":["PROPS"],"supported":false,"summary":"LWSWCR defines the critical water saturation (“SWCR”), for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The data is used to scale the water saturation in the low salinity water wet water-oil relative permeability saturation tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"LWSWL":{"name":"LWSWL","sections":["PROPS"],"supported":false,"summary":"LWSWL defines the connate water saturation (“SWL”), for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The data is used to scale the water saturation in the low salinity water wet water-oil relative permeability saturation tables, as well as the associated capillary pressure tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"LWSWLPC":{"name":"LWSWLPC","sections":["PROPS"],"supported":false,"summary":"LWSWLPC defines the capillary pressure connate water saturation (“SWLPC”), for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The data is used to scale the water saturation in the low salinity water wet water-oil capillary pressure tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"LWSWU":{"name":"LWSWU","sections":["PROPS"],"supported":false,"summary":"LWSWU defines the maximum water saturation(“SWU”), for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The data is used to scale the water saturation in the low salinity water wet water-oil relative permeability saturation tables, as well as the associated capillary pressure tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"MASSFLOW":{"name":"MASSFLOW","sections":["PROPS"],"supported":false,"summary":"The MASSFLOW keyword defines the upstream river mass flow versus time tables for rivers, for when the River option has been activated via the RIVRDIMS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"WORD","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","size_kind":"list","variadic_record":true},"MICPPARA":{"name":"MICPPARA","sections":["PROPS"],"supported":null,"summary":"The MICPPARA keyword used to define the model parameters for when the MICP model had been activated via the MICP keyword in the RUNSPEC section.","parameters":[],"example":""},"MISC":{"name":"MISC","sections":["PROPS"],"supported":null,"summary":"MISC defines the transformation between the miscible and immiscible relative permeability models, for when the MISCIBLE and SOLVENT keywords in the RUNSPEC section have been activated. The keyword can only be used with the MISCIBLE option and for when the oil, water, gas and solvent phases are active in the model.","parameters":[{"index":1,"name":"SSOL","description":"A columnar vector of real monotonically increasing down the column values starting from zero and terminating at one, that defines the solvent fraction with respect to the solvent and gas saturation, and is defined by: [S sub s over { left(S sub g ~+~ S sub s right) }] Where Sg is the gas saturation and Ss is the solvent saturation. Note that the first entry in the columnar vector should be zero and the last entry should be one to fully define the solvent fraction range.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":["1","1"]},{"index":2,"name":"MISC","description":"A columnar vector of real equal or increasing down the column values that are greater than or equal to zero and less then one, that define the corresponding miscibility for the corresponding solvent fraction SSOL. The first entry in the columnar vector should be zero and the last entry should be one to fully define the miscible-immiscible relationship.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- SOLVENT MISCIBILITY-IMMISCIBLITY TRANSFORM TABLE\n--\nMISC\n-- SSOL MISC\n-- FRAC FRAC\n-- ------- --------\n0.0000 0.0000\n0.2000 0.2500\n0.5000 0.7500\n1.0000 1.0000 / TABLE NO. 01\n-- SSOL MISC\n-- FRAC FRAC\n-- ------- --------\n0.0000 0.0000\n0.3000 0.2500\n0.6000 1.0000\n1.0000 1.0000 / TABLE NO. 02\nThe above example defines two solvent miscible-immiscible transform tables assuming NTMISC equals two and NSMISC is greater than or equal to four on the MISCIBLE keyword in the RUNSPEC section.","size_kind":"fixed","variadic_record":true},"MLANG":{"name":"MLANG","sections":["PROPS"],"supported":false,"summary":"This keyword, MLANG, defines the coal bed methane Langmuir Adsorption200\n Langmuir, Irving (June 1918). \"The Adsorption of Gases on Plane Surface of Glass, Mica and Platinum\". The Research Laboratory of the General Electric Company. 40 (9): 1361–1402. doi:10.1021/ja02242a004 maximum gas concentration for each grid cell used to scale the Langmuir isotherm table allocated to the cell, for when the Coal Bed Methane option has been activated via the COAL keyword in the RUNSPEC section. See the LANGMUIR keyword in the PROPS section for specifying the Langmuir tables for the model.","parameters":[],"example":"","size_kind":"array"},"MLANGSLV":{"name":"MLANGSLV","sections":["PROPS"],"supported":false,"summary":"This keyword, MLANGSLV, defines the coal bed methane Langmuir Adsorption201\n Langmuir, Irving (June 1918). \"The Adsorption of Gases on Plane Surface of Glass, Mica and Platinum\". The Research Laboratory of the General Electric Company. 40 (9): 1361–1402. doi:10.1021/ja02242a004 maximum solvent concentration for each grid cell used to scale the Langmuir isotherm solvent table allocated to the cell, for when the Coal Bed Methane option has been activated via the COAL keyword in the RUNSPEC section. In addition, the Solvent phase must have been declared by the SOLVENT keyword in the RUNSPEC section. See the COALNUM keyword in the GRID section for allocating the Langmuir solvent tables to the grid blocks, and also the LANGMUIR keyword in the PROPS section for defining the Langmuir Adsorption Isotherm tables. Keywords COALADS and COALPP, also in the PROPS section, are used to specify the relative adsorption data in runs containing the solvent phase.","parameters":[],"example":"","size_kind":"array"},"MSFN":{"name":"MSFN","sections":["PROPS"],"supported":null,"summary":"The MSFN keyword defines the miscible normalized relative permeability tables for when the MISCIBLE and or SOLVENT options have been activated in the RUNSPEC section using the respective keyword. The MISCIBLE keyword invokes a three component formulation (oil, water and solvent gas or an oil, water and solvent oil). Whereas the SOLVENT keyword results in a four component model (oil, water and gas plus a solvent). This keyword should only be used if the MISCIBLE and or SOLVENT options have been activated.","parameters":[{"index":1,"name":"SGAS","description":"A columnar vector of real monotonically increasing down the column values starting from zero and terminating at one, that defines the gas plus solvent saturation.","units":{},"default":"None","value_type":"DOUBLE","dimension":["1","1","1"]},{"index":2,"name":"KRSG","description":"A columnar vector of real values that are either equal or increasing down the column and that are greater than or equal to zero and less than or equal to one that defines the gas plus solvent relative permeability multiplier.","units":{},"default":"None"},{"index":3,"name":"KRO","description":"A columnar vector of real values that are either equal or increasing down the column and that are greater than or equal to zero and less than or equal to one that defines the oil relative permeability multiplier.","units":{},"default":"None"}],"example":"--\n-- MISCIBLE NORMALIZED RELATIVE PERMEABILITY TABLES\n--\nMSFN\n-- SGAS KRSG KRO\n-- FRAC\n-- -------- -------- --------\n0.0000 0.0000 1.0000\n1.0000 1.0000 0.0000 / TABLE NO. 01\n-- SGAS KRSG KRO\n-- FRAC\n-- -------- -------- --------\n0.0000 0.0000 1.0000\n0.2000 0.2000 0.8000\n0.4000 0.3000 0.7000\n0.6000 0.4000 0.6000\n0.8000 0.5000 0.4000\n1.0000 1.0000 0.0000 / TABLE NO. 02\nThe above example defines two MSN tables for use the MISCIBLE and SOLVENT options.","size_kind":"fixed","variadic_record":true},"MW":{"name":"MW","sections":["PROPS"],"supported":false,"summary":"The MW keyword defines the molecular weights for each of the compositional components active in the model and for each equation of state. The keyword should only be used if the compositional mode has been requested using the COMPS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"MW","description":"A series of real numbers that define the molecular weights for each of the compositional components active in the model.","units":{"field":"lb/lb-M","metric":"kg/kg-M","laboratory":"gm/gm-M"},"default":"None","value_type":"DOUBLE","dimension":"Mass/Moles"}],"example":"The following example defines the molecular weights for each component in a single three-component equation of state model.\n--\n-- Molecular Weights\n--\nMW\n16.0425 44.009 18.01528 /\nThe following example defines the molecular weights for each component in two three-component equation of state models.\n--\n-- Molecular Weights\n--\nMW\n16.0425 44.009 18.01528 /\n16.0425 44.009 18.01528 /","size_kind":"fixed","variadic_record":true},"NCOMPS":{"name":"NCOMPS","sections":["PROPS"],"supported":true,"summary":"This keyword confirms the maximum number of compositional components in the model, as such it should have the same number of components as that declared via the COMPS keyword in the RUNSPEC section. The keyword should only be used if the CO2STORE keyword and either the GASWAT or the GAS and WATER keywords in the RUNSPEC section, have also be activated for the gas-water two component model.","parameters":[{"index":1,"name":"NCOMPS","description":"A positive integer defining the maximum number of compositional components in the model. Secondly the number of components must be the same as that enter via the COMPS keyword in the RUNSPEC section. Only the default value of two is currently supported by OPM Flow.","units":{},"default":"2","value_type":"INT"}],"example":"The following example defines how to confirm a two component formulation to be used with the CO2STORE and GASWAT options.\n--\n-- CONFIRM NUMBER OF COMPOSITIONAL COMPONENTS (OPM FLOW KEYWORD)\n--\nNCOMPS\n2 /\n| Note This is an OPM Flow keyword used with OPM Flow’s CO2STORE and GASWAT keywords in the RUNSPEC section, and should not be confused with the more general version of the NCOMPS keyword used in the commercial compositional simulator. Secondly, although OPM Flow parses the keyword, the simulator currently ignores the data for this keyword. |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":1,"size_kind":"fixed","size_count":1},"NOWARNEP":{"name":"NOWARNEP","sections":["PROPS"],"supported":null,"summary":"The NOWARNEP keyword deactivates the writing out of warning messages associated with checking the consistency of saturation table end-points; however error messages are still reported by the simulator.","parameters":[],"example":"--\n-- DEACTIVATE END-POINT SCALING WARNING MESSAGES\n--\nNOWARNEP\nThe above example switches off the writing out of warning messages associated with checking the consistency of saturation table end-points;","size_kind":"none","size_count":0},"OILDENT":{"name":"OILDENT","sections":["PROPS"],"supported":null,"summary":"OILDENT defines the oil density as a function of temperature coefficients for when OPM Flow’s thermal option has been activated by the THERMAL keyword in the RUNSPEC. Note this is an OPM Flow keyword used with OPM Flow’s black-oil thermal model that is not available in the commercial simulator’s black-oil thermal formulation.","parameters":[{"index":1,"name":"TEMP","description":"TEMP is a real positive value greater than zero that defines the absolute reference temperature used with TEXP1 and TEXP2 to estimate the change in oil density with respect to temperature.","units":{"field":"oR 527.67","metric":"K 293.15","laboratory":"K 293.15"},"default":"Defined","value_type":"DOUBLE","dimension":"AbsoluteTemperature"},{"index":2,"name":"TEXP1","description":"TEXP1 is a real positive value greater than zero that defines the oil thermal expansion coefficient of the first order.","units":{"field":"1/oR 1.67 x 10-4","metric":"1/K 3.0 x 10-4","laboratory":"1/K 3.0 x 10-4"},"default":"Defined","value_type":"DOUBLE","dimension":"1/AbsoluteTemperature"},{"index":3,"name":"TEXP2","description":"TEXP2 is a real positive value greater than zero that defines the oil thermal expansion coefficient of the second order.","units":{"field":"1/oR2 9.26 x 10-7","metric":"1/K2 3.0 x 10-6","laboratory":"1/K2 3.0 x 10-6"},"default":"Defined","value_type":"DOUBLE","dimension":"1/AbsoluteTemperature*AbsoluteTemperature"}],"example":"The following example shows the OILDENT keyword using the default values, for when the thermal option has been activated by the THERMAL keyword in the RUNSPEC section and for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set to two.\n--\n-- OIL DENSITY TEMPERATURE COEFFICIENTS (OPM FLOW THERMAL KEYWORD)\n--\n-- OIL DENSITY DENSITY\n-- TEMP COEFF1 COEFF2\n-- -------- ------- -------\nOILDENT\n1* 1* 1* / TABLE NO. 01\n1* 1* 1* / TABLE NO. 02\nThere is no terminating “/” for this keyword.\n| [%rho_o( p, T ) = %rho_o( p_s, T_s ) b_o( p, T )] | (8.3.186.1) |\n|---------------------------------------------------|-------------|\n| [b_o( p, T ) = { b_o( p, T_ref ) } over { 1 + c_1 ( T - T_ref ) + c_2 ( T - T_ref )^2 }] | (8.3.186.2) |\n|------------------------------------------------------------------------------------------|-------------|","expected_columns":3,"size_kind":"fixed"},"OILJT":{"name":"OILJT","sections":["PROPS"],"supported":null,"summary":"OILJT activates the oil Joule-Thomson effect202\n The Joule–Thomson coefficient is defined as the change in temperature with respect to an increase in pressure at constant enthalpy. in temperature calculations, and defines the oil Joule-Thomson Coefficient (“JTC”) at a given reference pressure, for when OPM Flow’s thermal option has been activated by the THERMAL keyword in the RUNSPEC.","parameters":[{"index":1,"name":"PRESS","description":"A real positive value that defines the reference pressure for the corresponding Joule-Thomson Coefficient, OILJTC.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":"Pressure"},{"index":2,"name":"OILJTC","description":"OILJTC is a real positive or negative value that defines the oil phase Joule-Thomson Coefficient. If the value is defaulted (1*) or set to 0, then OILJTC is internally calculated using the thermal oil density data on the OILDENT keyword in the PROPS section. If a non-zero value is specified, then the OILJTC is assumed to be constant and equal to that value.","units":{"field":"oF/psia","metric":"oC/barsa","laboratory":"oC/atma"},"default":"0","value_type":"DOUBLE","dimension":"AbsoluteTemperature/Pressure"}],"example":"The following example shows the OILJT keyword for when the thermal option has been activated by the THERMAL keyword in the RUNSPEC section, and for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set equal to two.\n--\n-- OIL JOULE-THOMSON COEFFICIENT (OPM FLOW EXTENSION KEYWORD)\n--\n-- REF OIL\n-- PRESS JTC\n-- -------- -------\nOILJT\n20.0 1* / TABLE NO. 01\n20.0 -0.20 / TABLE NO. 02\nHere the first entry is defaulted, and the simulator will therefore calculate the oil JTC internally using the data on the OILDENT keyword in the PROPS section.\nThere is no terminating “/” for this keyword.\n| Note This is an OPM Flow keyword used with OPM Flow’s black-oil thermal model, that is not available in the commercial simulator’s black-oil thermal formulation. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| [%eta` `=`` left({ partial T} over {partial P} right)] | (8.66) |\n|--------------------------------------------------------|--------|\n| [%eta ``=`` left( T %alpha``-``1 right) 1 over( %rho C_p )``-`` left( g over C_p dp over dz right)^-1] | (8.67) |\n|--------------------------------------------------------------------------------------------------------|--------|\n| [%eta ``=`` left( T %alpha``-``1 right) 1 over( %rho C_b )] | (8.68) |\n|-------------------------------------------------------------|--------|","expected_columns":2,"size_kind":"fixed"},"OILVISCT":{"name":"OILVISCT","sections":["PROPS"],"supported":null,"summary":"OILVISCT defines the oil viscosity as a function of temperature for when OPM Flow’s thermal option has been activated by the THERMAL keyword in the RUNSPEC section. The reference pressure and solution gas-oil ratio of the oil for this table is given by the VISCREF keyword in the PROPS section. Note this is an OPM Flow keyword used with OPM Flow’s black-oil thermal model that is not available in the commercial simulator’s black-oil thermal formulation.","parameters":[{"index":1,"name":"TEMP","description":"A columnar vector of real monotonically increasing down the column values that defines the temperature values.","units":{"field":"oF","metric":"oC","laboratory":"oC"},"default":"None","value_type":"DOUBLE","dimension":["Temperature","Viscosity"]},{"index":2,"name":"VIS","description":"A columnar vector of real increasing down the column values that defines the oil viscosity for the corresponding temperature values (TEMP). VIS should be given at the reference pressure and solution gas-oil ratio as defined by PRESS and RS variables on the VISCREF keyword.","units":{"field":"cP","metric":"cP","laboratory":"cP"},"default":"None"}],"example":"The following example shows the OILVISCT keyword for when the thermal option has been activated by the THERMAL keyword in the RUNSPEC section and for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set equal to one.\n--\n-- OIL VISCOSITY VERSUS TEMPERATURE TABLES (OPM FLOW EXTENSION KEYWORD)\n--\n-- OIL OIL\n-- TEMP VISC\n-- -------- -------\nOILVISCT\n100.0 0.600\n110.0 0.650\n120.0 0.680\n150.0 0.720\n165.0 0.725 / TABLE NO. 01","size_kind":"fixed","variadic_record":true},"OVERBURD":{"name":"OVERBURD","sections":["PROPS"],"supported":null,"summary":"The OVERBURD keyword defines the overburden pressures versus depth relationship to be applied for when the rock compaction option has been invoked by the ROCKCOMP keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"DEPTH","description":"A columnar vector of real monotonically increasing down the column values that defines the depth for corresponding overburden pressure parameter PRESS.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":["Length","Pressure"]},{"index":2,"name":"PRESS","description":"A columnar vector of real monotonically increasing down the column values that defines the corresponding overburden pressure for the given DEPTH.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"None"}],"example":"The example below defines three overburden tables, assuming NTROCC is equal to three on the ROCKCOMP keyword and NPPVT is greater than or equal to four on the TABDIMS keyword.\n--\n-- OVERBURDEN PRESSURE VERSUS DEPTH TABLES\n--\nOVERBURD\n-- DEPTH OVERBURDEN\n-- FEET PRESSURE\n-- ------ ----------\n1000.0 300.000\n2000.0 600.000\n3000.0 900.000\n4000.0 1200.000 / TABLE N0. 01\n-- DEPTH OVERBURDEN\n-- FEET PRESSURE\n-- ------ ----------\n1000.0 200.000\n2000.0 400.000\n3000.0 800.000\n4000.0 1000.000 / TABLE N0. 02\n-- DEPTH OVERBURDEN\n-- FEET PRESSURE\n-- ------ ----------\n1000.0 400.000\n2000.0 800.000\n3000.0 1100.000\n4000.0 1500.000 / TABLE N0. 03\nNote that there must be exactly NTROCC tables entered for this keyword, otherwise an error will occur.\n--\n-- ROCK COMPACTION TABLES\n--\nROCKTAB\n-- PRESS PORV TX(YZ)\n-- MULT MULT\n-- ------ ------ ------\n1000.0 0.9600 0.9650\n1500.0 0.9800 0.9850\n3000.0 0.9900 0.9950\n4500.0 1.0000 1.0000\n4750.0 1.0100 1.0100 / TABLE NO. 01\n-- PRESS PORV TX(YZ)\n-- MULT MULT\n-- ------ ------ ------\n1000.0 0.9600 0.9650\n1500.0 0.9800 0.9850\n3000.0 0.9900 0.9950\n4500.0 1.0000 1.0000\n4750.0 1.0100 1.0100 / TABLE NO. 02\n-- PRESS PORV TX(YZ)\n-- MULT MULT\n-- ------ ------ ------\n1000.0 0.9600 0.9650\n2000.0 0.9800 0.9850\n3000.0 0.9900 0.9950\n4000.0 1.0100 1.0100 / TABLE NO. 03\nHere ROCKTAB tables one and two are identical.","size_kind":"fixed","variadic_record":true},"PCFACT":{"name":"PCFACT","sections":["PROPS"],"supported":null,"summary":"PCFACT defines the capillary pressure multiplication factor due to a change in porosity. Currently the keyword is used in conjunction with OPM Flow’s Salt Precipitation model, in which the pore space is reduced due to salt precipitating in the pore space, causing a reduction in porosity and an associated increase in capillary pressure.","parameters":[{"index":1,"name":"POROFAC","description":"A real monotonically increasing positive columnar vector that defines the porosity factor ([%phi over %phi sub 0]) for the corresponding PCFAC vector.) for the corresponding PCFAC vector. In the simulator’s Salt Precipitation model, the maximum value of [%phi]is [%phi sub 0], implying a maximum value of one for POROFAC., implying a maximum value of one for POROFAC.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":["1","1"]},{"index":2,"name":"PCFAC","description":"A real positive monotonically decreasing columnar vector that defines the capillary pressure ([p sub c]) multiplier associated with POROFAC and used to scale a grid block's capillary pressure due to the reduction in pore volume caused by salt precipitation. ) multiplier associated with POROFAC and used to scale a grid block's capillary pressure due to the reduction in pore volume caused by salt precipitation. Where: [PCFAC~=~ m left (%phi over %phi_0 right) newline\nwith `` p sub c~=~ m left (%phi over %phi_0 right) p sub c0]","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"The example below defines two PCFACT tables assuming NTSFUN equals two and NSSFUN is greater than or equal to five on the TABDIMS keyword in the RUNSPEC section.\n--\n-- CAPILLARY PRESSURE FACTOR INCREASE DUE TO SALT PRECIPITATION\n-- (OPM FLOW KEYWORD)\n--\nPCFACT\n-- PORO PC\n-- FACTOR FACTOR\n-- ------- --------\n0.00 2.0000\n0.25 2.0000\n0.50 1.4142\n0.75 1.1547\n1.00 1.0000 / TABLE NO. 01\n-- ------- --------\n0.00 2.0000\n0.25 2.0000\n0.50 1.4142\n0.75 1.1547\n1.00 1.0000 / TABLE NO. 02\nNote that the capillary pressure factor has been capped for POROFAC less than 0.25.\n| Note This is an OPM Flow specific keyword for the simulator’s Salt Precipitation model that is activated by the BRINE and PRECSALT keywords and declaring that vaporized water is present in the run via the VAPWAT keyword. All three keywords are in the RUNSPEC section. |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| [%phi ~=~ ( 1`-` s sub s) %phi sub 0] | (8.3.199.1) |\n|---------------------------------------|-------------|\n| [p sub c over p sub c0`=`left( {%phi over %phi sub 0} {k sub 0 over k} right) ^ {1 over 2}] | (8.3.199.2) |\n|----------------------------------------------------------------------------------------------|-------------|","size_kind":"fixed","variadic_record":true},"PCG":{"name":"PCG","sections":["PROPS"],"supported":false,"summary":"PCG defines the maximum drainage gas-oil capillary pressure values for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. The keyword can be used with all grid types.","parameters":[{"index":1,"name":"PCG","description":"PCG is an array of positive real numbers assigning the maximum drainage gas-oil capillary pressure values for each cell in the model. Repeat counts may be used, for example 30*100.0.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK PCG DATA FOR ALL CELLS (BASED ON NX x NY x NZ = 300)\n--\nPCG\n100*50.0 100*75.0 100*125.0 /\nThe above example defines the PCW for 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.\n| [P sub c ~=~P sub{ c sub{TABLE} } LEFT( PCG OVER {P SUB {c sub {TABLE-MAX }}} RIGHT)] | (8.69) |\n|----------------------------------------------------------------------------------------|--------|","size_kind":"array"},"PCG32D":{"name":"PCG32D","sections":["PROPS"],"supported":false,"summary":"This keyword, PCG32D, enables the gas-oil capillary pressure data to be entered as a function of both oil and water saturations. The keyword should be used in conjunction with the SGF32D keyword in the PROPS section. See also the PCW32D keyword in the PROPS section that provides similar functionality for the water-oil capillary pressure data.","parameters":[{"index":1,"name":"SOME_DATA","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","size_kind":"list","variadic_record":true},"PCRIT":{"name":"PCRIT","sections":["PROPS"],"supported":false,"summary":"The PCRIT keyword defines the critical pressures for each of the compositional components active in the model and for each equation of state. The keyword should only be used if the compositional mode has been requested using the COMPS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"PCRIT","description":"A series of real numbers that define the critical pressures for each of the compositional components active in the model.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":"Pressure"}],"example":"The following example defines the critical pressures for each component in a single three-component equation of state model.\n--\n-- Critical Pressures\n--\nPCRIT\n1070.132 667.0576 616.5844 /\nThe following example defines the critical pressures for each component in two three-component equation of state models.\n--\n-- Critical Pressures\n--\nPCRIT\n1070.132 667.0576 616.5844 /\n1070.132 667.0576 616.5844 /","size_kind":"fixed","variadic_record":true},"PCW":{"name":"PCW","sections":["PROPS"],"supported":false,"summary":"PCW defines the maximum drainage water-oil or water-gas capillary pressure values for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. The keyword can be used with all grid types.","parameters":[{"index":1,"name":"PCW","description":"PCW is an array of positive real numbers assigning the maximum drainage water capillary pressure values for each cell in the model. Repeat counts may be used, for example 30*100.0.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK PCW DATA FOR ALL CELLS (BASED ON NX x NY x NZ = 300)\n--\nPCW\n100*50.0 100*75.0 100*125.0 /\nThe above example defines the PCW for 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.\n| [P sub c ~=~P sub{ c sub{TABLE} } LEFT( PCW OVER {P SUB {c sub {TABLE-MAX }}} RIGHT)] | (8.70) |\n|----------------------------------------------------------------------------------------|--------|","size_kind":"array"},"PCW32D":{"name":"PCW32D","sections":["PROPS"],"supported":false,"summary":"This keyword, PCW32D, enables the water-oil capillary pressure data to be entered as a function of both oil and gas saturations. The keyword should be used in conjunction with the SWF32D keyword in the PROPS section. See also the PCG32D keyword in the PROPS section that provides similar functionality for the gas-oil capillary pressure data.","parameters":[{"index":1,"name":"SOME_DATA","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","size_kind":"list","variadic_record":true},"PECOEFS":{"name":"PECOEFS","sections":["PROPS"],"supported":false,"summary":"The PECOEFS keyword defines the Petro-Elastic model coefficients.","parameters":[{"index":1,"name":"WAT_SALINITY","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":2,"name":"TEMP","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Temperature"},{"index":3,"name":"MINERAL_DENSITY","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Density"},{"index":4,"name":"PHI_EFF_0","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":5,"name":"PHI_EFF_1","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":6,"name":"C_0","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":7,"name":"C_K","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":8,"name":"SHEAR_MOD","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":9,"name":"ALPHA","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"},{"index":10,"name":"E","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"},{"index":11,"name":"METHOD","description":"","units":{},"default":"0","value_type":"INT"}],"example":"","expected_columns":11,"size_kind":"list"},"PEGTAB":{"name":"PEGTAB","sections":["PROPS"],"supported":null,"summary":"The PEGTAB series of keywords define a series of coefficients of a polynomial function used in the calculation of the shear modulus in the petro-elastic model. The series of keywords consist of: PEGTAB0 PEGTAB1, PEGTAB2, PEGTAB3, PEGTAB4, PEGTAB5, PEGTAB6, and PEGTAB7.","parameters":[],"example":""},"PEKTAB":{"name":"PEKTAB","sections":["PROPS"],"supported":null,"summary":"The PEKTAB series of keywords define a series of coefficients of a polynomial function used in the calculation of the bulk modulus in the petro-elastic model. The series of keywords consist of: PEKTAB0 PEKTAB1, PEKTAB2, PEKTAB3, PEKTAB4, PEKTAB5, PEKTAB6, and PEKTAB7.","parameters":[],"example":""},"PERMFACT":{"name":"PERMFACT","sections":["PROPS"],"supported":null,"summary":"PERMFACT defines the permeability multiplication factor due to a change in porosity. The keyword is used in conjunction with OPM Flow’s Salt Precipitation model, in which the pore space is reduced due to salt precipitating in the pore space, causing a reduction in porosity and an associated reduction in permeability. This keyword is also used for the BIOFILM and MICP model, where the pore space is reduced due to biofilm formation, and for the MICP model, also due to calcite precipitation.","parameters":[{"index":1,"name":"POROFAC","description":"A real monotonically increasing positive columnar vector that defines the porosity ([%phi over %phi sub 0]) factor for the corresponding PERMFAC vector.) factor for the corresponding PERMFAC vector. In the simulator’s Salt Precipitation model, the maximum value of [%phi]is [%phi sub 0], implying a maximum value of one for POROFAC., implying a maximum value of one for POROFAC.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":["1","1"]},{"index":2,"name":"PERMFAC","description":"A real positive monotonically increasing columnar vector that defines the permeability (k) multiplier associated with POROFAC and used to scale a grid block's permeability due to the reduction in pore volume caused by salt precipitation. Where: [PERMFAC~=~ m left (%phi right) newline\nwith `` k~=~ m left (%phi right) k sub 0]","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"The example below defines two PERMFACT tables assuming NTSFUN equals two and NSSFUN is greater than or equal to five on the TABDIMS keyword in the RUNSPEC section.\n--\n-- PERMEABILITY FACTOR AS A FUNCTION OF POROSITY REDUCTION\n-- (OPM FLOW KEYWORD)\n--\nPERMFACT\n-- PORO PERM\n-- FACTOR FACTOR\n-- ------- --------\n0.00 0.0000\n0.25 0.0625\n0.50 0.2500\n0.75 0.5625\n1.00 1.0000 / TABLE NO. 01\n-- ------- --------\n0.00 0.0000\n0.25 0.0625\n0.50 0.2500\n0.75 0.5625\n1.00 1.0000 / TABLE NO. 02\nBoth tables use equation (8.72)with Φc equal to zero and ɣ equal to 2.0. Note that PERMFACT changes the permeability in all three dimensions, that is the PERMX, PERMY and PERMZ arrays are all modified.\n| Note This is an OPM Flow specific keyword. |\n|--------------------------------------------|\n| [%phi ~=~ ( 1`-` s sub s) %phi sub o] | (8.71) |\n|---------------------------------------|--------|\n| [k over k sub o`=`left( {%phi - %phi sub c} over {%phi sub o - %phi sub c} right) sup %gamma] | (8.72) |\n|------------------------------------------------------------------------------------------------|--------|","size_kind":"fixed","variadic_record":true},"PLMIXPAR":{"name":"PLMIXPAR","sections":["PROPS"],"supported":null,"summary":"The PLMIXPAR keyword defines the Todd-Longstaff210\n Todd, M. and Longstaff, W. “The Development, Testing and Application of a Numerical Simulator for Predicting Miscible Flood Performance,” paper SPE 3484, Journal of Canadian Petroleum Technology (1972) 24, No. 7, 874-882. mixing parameters for when the polymer option has been activated by the POLYMER keyword in the RUNSPEC section. This keyword must be present in the input deck if the POLYMER keyword has been activated.","parameters":[{"index":1,"name":"PLMVIS","description":"A real positive value that is greater than or equal to zero and less than or equal to one, that defines the viscosity Todd-Longstaff mixing parameter for each polymer region.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":"1"}],"example":"--\n-- POLYMER TODD-LONGSTAFF MIXING PARAMETERS\n--\nPLMIXPAR\n-- PLM\n-- VISCOS\n-- -------\n0.3500 / TABLE NO. 01\n0.2500 / TABLE NO. 02\n0.6500 / TABLE NO. 03\nThe above example defines three polymer Todd-Longstaff mixing parameter data sets, based on the NPLMIX variable on the REGDIMS keyword in the RUNSPEC section being equal to three.","size_kind":"fixed","variadic_record":true},"PLYADS":{"name":"PLYADS","sections":["SPECIAL","PROPS"],"supported":null,"summary":"The PLYADS keyword defines the rock polymer adsorption tables for when the polymer option has been activated by the POLYMER keyword in the RUNSPEC section. Alternatively, the functions can be entered via the PLYADSS keyword in the PROPS section for when salt sensitivity is to be considered.","parameters":[{"index":1,"name":"POLCON","description":"A columnar vector of real monotonically increasing down the column values that defines the polymer concentration in the solution surrounding the rock. The first entry should be zero to define a no polymer concentration.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None","value_type":"DOUBLE","dimension":["Concentration","1"]},{"index":2,"name":"POLRATIO","description":"A columnar vector of real increasing down the column values that defines the mass of adsorbed polymer per unit mass of rock. The first entry should be zero to define a zero ratio of polymer concentration.","units":{"field":"lb/lb","metric":"kg/kg","laboratory":"gm/gm"},"default":"None"}],"example":"--\n-- POLYMER ROCK ADSORPTION TABLE\n--\nPLYADS\n-- POLYMER POLYMER\n-- POLCON POLRATIO\n-- ------- --------\n0.0 0.00000\n2.0 0.00003\n4.0 0.00005\n6.0 0.00007\n8.0 0.00009\n10.0 0.00011\n12.0 0.00012\n14.0 0.00015 / TABLE NO. 01\n-- POLYMER POLYMER\n-- POLCON POLRATIO\n-- ------- --------\n0.0 0.00000\n3.0 0.00004\n5.0 0.00006\n7.0 0.00008\n8.0 0.00009\n10.0 0.00011 / TABLE NO. 02\nThe above example defines two polymer rock adsorption tables assuming NTSFUN equals two and NSSFUN is greater than or equal to eight on the TABDIMS keyword in the RUNSPEC section.\nThere is no terminating “/” for this keyword.","size_kind":"fixed","variadic_record":true},"PLYADSS":{"name":"PLYADSS","sections":["PROPS"],"supported":true,"summary":"The PLYADSS keyword defines the rock polymer adsorption tables for when the polymer and the salt options has been activated by the POLYMER and BRINE keywords in the RUNSPEC section.","parameters":[{"index":1,"name":"POLCON","description":"A columnar vector of real monotonically increasing down the column values that defines the polymer concentration in the solution surrounding the rock. The first entry should be zero to define a no polymer and no salt concentration data set. POLCON should only be given for the first entry of the POLCON/POLRATIO set and skipped until another POLCON/POLRATIO table is entered.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None","value_type":"DOUBLE","dimension":"Concentration"},{"index":2,"name":"POLRATIO","description":"A columnar vector of real increasing down the column values that defines the mass of adsorbed polymer per unit mass of rock of the saturated concentration of polymer adsorbed by the rock for a given POLCON and the salt concentration given by SALTCON on the ADSALNOD keyword in the PROPS section. The first table data set entry should be zero to define a no polymer and no salt concentration data set. Subsequent POLRATIO values define the POLCON/POLRATIO combinations for a given salt concentration as listed (and in the same order) by the SALTCON variable on the ADSALNOD keyword in the PROPS section. Each POLCON/POLRATIO/SALT data sets should be terminated by a “/”","units":{"field":"lb/lb","metric":"kg/kg","laboratory":"gm/gm"},"default":"None","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"--\n-- SETS SALT CONCENTRATION FOR POLYMER SOLUTION ADSORPTION\n-- VIA SATNUM ARRAY ALLOCATION\n--\n-- SALT\n--\nADSALNOD\n1.0\n5.0\n10.5\n25.0 / SATNUM TABLE NO. 01\n--\n-- POLYMER ROCK ADSORPTION WITH SALT DEPENDENCY TABLE\n--\nPLYADSS\n-- POLYMER POLYMER\n-- POLCON POLRATIO\n-- ------- --------\n0.0 0.00000\n0.00000\n0.00000\n0.00000 / TABLE NO. 01\n-- POLYMER POLYMER\n-- POLCON POLRATIO\n-- ------- --------\n1.0 0.00002\n0.00003\n0.00004\n0.00005 / TABLE NO. 02\n-- POLYMER POLYMER\n-- POLCON POLRATIO\n-- ------- --------\n2.0 0.00003\n0.00004\n0.00005\n0.00006 / TABLE NO. 03\n-- POLYMER POLYMER\n-- POLCON POLRATIO\n-- ------- --------\n3.0 0.00004\n0.00005\n0.00006\n0.00007 / TABLE NO. 04\nThe above example defines four polymer rock adsorption tables for four salt concentration on the ADSALNOD keyword, assuming NTSFUN equals one and NSSFUN is greater than or equal to four on the TABDIMS keyword in the RUNSPEC section.\nThere is no terminating “/” for this keyword.","size_kind":"list","variadic_record":true},"PLYATEMP":{"name":"PLYATEMP","sections":["PROPS"],"supported":false,"summary":"This keyword defines the polymer adsorption temperature for subsequent polymer adsorption tables entered via the PLYADS and PLYADSS keywords in the PROPS section. The Polymer option must have been activated by the POLYMER keyword in the RUNSPEC section and the Thermal option invoked by the THERMAL keyword, also in the RUNSPEC section.","parameters":[{"index":1,"name":"PLYATEMP","description":"Single real positive value that defines polymer adsorption temperature for subsequent polymer adsorption tables.","units":{"field":"oF","metric":"oC","laboratory":"oC"},"default":"None"}],"example":"The example shows how to enter the polymer adsorption data using the PLYADS keyword for two different temperatures.\n--\n-- RESERVOIR\n-- TEMPERATURE\n-- -----------\nPLYATEMP\n60.0 / TEMPERATURE\n--\n-- POLYMER ROCK ADSORPTION TABLE\n--\nPLYADS\n-- POLYMER POLYMER\n-- POLCON POLRATIO\n-- ------- --------\n0.0 0.00000\n2.0 0.00003\n4.0 0.00005\n6.0 0.00007\n8.0 0.00009\n10.0 0.00011\n12.0 0.00012\n14.0 0.00015 / TABLE NO. 01\n--\n-- POLYMER POLYMER\n-- POLCON POLRATIO\n-- ------- --------\n0.0 0.00000\n3.0 0.00004\n5.0 0.00006\n7.0 0.00008\n8.0 0.00009\n10.0 0.00011 / TABLE NO. 02\n--\n-- RESERVOIR\n-- TEMPERATURE\n-- -----------\nPLYATEMP\n120.0 / TEMPERATURE\n--\n-- POLYMER ROCK ADSORPTION TABLE\n--\nPLYADS\n-- POLYMER POLYMER\n-- POLCON POLRATIO\n-- ------- --------\n0.0 0.00000\n2.0 0.00003\n4.0 0.00005\n6.0 0.00007\n8.0 0.00009\n10.0 0.00011\n12.0 0.00012\n14.0 0.00015 / TABLE NO. 01\n--\n-- POLYMER POLYMER\n-- POLCON POLRATIO\n-- ------- --------\n0.0 0.00000\n3.0 0.00004\n5.0 0.00006\n7.0 0.00008\n8.0 0.00009\n10.0 0.00011 / TABLE NO. 02\nHere the first PLYATEMP keyword defines the temperature to be 60 oF for the subsequent two polymer rock adsorption tables, assuming NTSFUN equals four and NSSFUN is greater than or equal to eight on the TABDIMS keyword in the RUNSPEC section. The next PLYATEMP keyword defines the temperature to be 120 oF for the subsequent two polymer rock adsorption tables.","size_kind":"array"},"PLYCAMAX":{"name":"PLYCAMAX","sections":["PROPS"],"supported":false,"summary":"The PLYCAMAX keyword defines the maximum polymer-rock adsorption value used in the calculation of the resistance factor for the water phase by individual grid block, for when the Polymer option has been activated by the POLYMER keyword in the RUNSPEC section. See the POLMAX parameter on the PLYROCK keyword in the PROPS section for setting the property for the whole grid.","parameters":[],"example":"","size_kind":"array"},"PLYDHFLF":{"name":"PLYDHFLF","sections":["SPECIAL","PROPS","SCHEDULE"],"supported":false,"summary":"The PLYDHFLF keyword defines the polymer thermal degradation half-life with respect to temperature functions for when the polymer option has been activated by the POLYMER keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"TEMP","description":"A columnar vector of real monotonically increasing down the column values that defines the polymer thermal degradation temperature.","units":{"field":"oF","metric":"oC","laboratory":"oC"},"default":"None","value_type":"DOUBLE","dimension":["Temperature","Time"]},{"index":2,"name":"POLHFLF","description":"A columnar vector of real values that defines the corresponding polymer half-life.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"None"}],"example":"--\n-- POLYMER THERMAL DEGRADATION HALF-LIFE TABLE\n--\nPLYDHFLF\n-- POLYMER POLYMER\n-- TEMP HALF-LIFE\n-- ------- ---------\n0.0 365.000\n40.0 200.000\n80.0 150.000\n120.0 100.000 / TABLE NO. 01\n-- POLYMER POLYMER\n-- TEMP HALF-LIFE\n-- ------- --------\n0.0 365.000\n50.0 175.000\n75.0 140.000\n100.0 120.000\n125.0 90.000\n150.0 85.000 / TABLE NO. 02\nThe example defines two polymer thermal degradation half-life tables, based on the NTPVT variable on the TABDIMS keyword in the RUNSPEC section being equal to two and NPPVT variable on the same keyword being greater than or equal to six.","size_kind":"fixed","variadic_record":true},"PLYESAL":{"name":"PLYESAL","sections":["PROPS"],"supported":false,"summary":"This keyword, PLYESAL, defines the polymer effective salinity coefficient as well as enabling the effective salinity calculation for polymer adsorption. The keyword should only be used if the BRINE keyword has been declared to activate the brine phase, the ECLMC keyword to enable the Multi-Component Brine model, and the POLYMER keyword has been used to activate the polymer phase. All three keywords are in the RUNSPEC section.","parameters":[{"index":1,"name":"ALPHAP","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","expected_columns":1,"size_kind":"fixed"},"PLYKRRF":{"name":"PLYKRRF","sections":["PROPS"],"supported":false,"summary":"The PLYKRRF keyword defines the polymer rock permeability reduction factor to the water phase by individual cell, for when the Polymer option has been activated by the POLYMER keyword in the RUNSPEC section. PLYKRRF should consist of an array of real positive values that are greater than or equal to one. See the PERMFAC parameter on the PLYROCK keyword in the PROPS section for setting the property for the whole grid.","parameters":[],"example":"","size_kind":"array"},"PLYMAX":{"name":"PLYMAX","sections":["SPECIAL","PROPS"],"supported":null,"summary":"The PLYMAX keyword defines maximum polymer and salt concentrations that are to be used in the mixing parameter calculation of the fluid component viscosities, for when the Polymer option has been activated by the POLYMER keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"POLCON","description":"A real value that defines the polymer concentration in the solution which is used to calculate maximum polymer fluid component viscosity.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None","value_type":"DOUBLE","dimension":"Concentration"},{"index":2,"name":"SALTCON","description":"A real value that defines the salt concentration in the solution which is used to calculate maximum polymer fluid component viscosity. Note that If the BRINE option has not been activated by the BRINE keyword in the RUNSPEC section, then this variable is ignored; however, there should still be dummy entries in this case. This variable is ignored as the BRINE and POLYMER combination is not implemented in OPM Flow.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None","value_type":"DOUBLE","dimension":"Concentration"}],"example":"--\n-- POLYMER-SALT VISCOSITY MIXING CONCENTRATIONS\n--\nPLYMAX\n-- POLYMER SALT\n-- POLCON SALTCON\n-- ------- --------\n0.0100 0.0500 / TABLE NO. 01\n0.0075 0.0400 / TABLE NO. 02\n0.0050 0.0300 / TABLE NO. 03\nThe above example defines three polymer-salt viscosity mixing concentrations, based on the NPLMIX variable on the REGDIMS keyword in the RUNSPEC section being equal to three.\n| Note Currently, combining the BRINE and POLYMER models is not implemented in OPM Flow, and therefore SALTCON parameter on the PLYMAX keyword is ignored. |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":2,"size_kind":"fixed"},"PLYMWINJ":{"name":"PLYMWINJ","sections":["PROPS"],"supported":null,"summary":"This keyword, PLYMWINJ, describes the relationship of the injected polymer molecular weight as a function of polymer throughput and polymer velocity, for the simulator's Polymer Molecular Weight Transport option, that uses the polymer molecular weight in calculating the polymer viscosity. The table is a two dimensional table that relates the polymer throughput values and velocity values to derive the resulting molecular weight of the injected polymer, which is then used via the PLYVHM keyword in the PROPS section, to derive the polymer molecular weight scaled viscosity.","parameters":[{"index":1,"name":"PLYMWNUM","description":"A positive integer value greater than zero and less than or equal to the NTPMWINJ variable, as defined on the PINTDIMS keyword in the RUNSPEC section, that defines the PLYMWINJ Polymer Molecular Weight Model throughput and velocity table number.","units":{},"default":"None","record":1,"value_type":"INT"},{"index":1,"name":"THRUPUT","description":"A real positive monotonically increasing vector, that defines the polymer throughput values. The first entry should be zero to define a no throughput data set, and each vector record should be on a separate line terminated by a “/”.","units":{"field":"feet3/feet2","metric":"m3/m2","laboratory":"cm3/cm2"},"default":"None","record":2,"value_type":"DOUBLE","dimension":"Length"},{"index":1,"name":"VELOCITY","description":"A real positive monotonically increasing vector, that defines the polymer velocity values. The first entry should be zero to define a no velocity data set, and each vector record should be on a separate line terminated by a “/”.","units":{"field":"feet/day","metric":"m/day","laboratory":"cm/hour"},"default":"None","record":3,"value_type":"DOUBLE","dimension":"Length/Time"},{"index":1,"name":"POLYMW","description":"A series of real positive vectors representing the polymer molecular weights for all combinations of the polymer throughput values (THRUPUT) and velocity values (VELOCITY), organized as a series of vectors POLYMW(THRUPUT, VELOCITY). Thus, the first vector represents the molecular weights of the first THRUPUT value and each entry in the vector is the corresponding molecular weight of the associated VELOCITY vector. Each vector should be on a separate line and should be terminated by a “/”. Thus, if THRUPUT has three entries and VELOCITY has four, then there should be three vectors, with each vector containing four elements representing molecular weight values, as a function of THRUPUT and VELOCITY.","units":{"field":"lb/lb-M","metric":"kg/kg-M","laboratory":"gm/gm-M"},"default":"None","record":4,"value_type":"DOUBLE","dimension":"1"}],"example":"Given NTPMWINJ equals two on the PINTDIMS keyword in the RUNSPEC section, then two PLYWINJ tables are required to be entered:\n--\n-- POLYMER MOLECULAR WEIGHT MODEL THROUGHPUT AND VELOCITY TABLE\n-- (OPM FLOW PROPS KEYWORD)\n--\nPLYMWINJ\n1 / TABLE NUMBER\n--\n-- THROUGHPUT VALUES\n--\n0.0 200.0 400.0 /\n--\n-- VELOCITY VALUES\n--\n0.0 50.0 80.0 100.0 /\n--\n-- POLYMW VALUES\n--\n20.0 19.0 18.0 16.0 / POLYMW(OUTPUT=1, VELOCITY=1 TO N)\n20.0 16.0 14.0 12.0 / POLYMW(OUTPUT=2, VELOCITY=1 TO N)\n20.0 12.0 8.0 4.0 / POLYMW(OUTPUT=3, VELOCITY=1 TO N)\n/\nPLYMWINJ\n2 / TABLE NUMBER\n--\n-- THROUGHPUT VALUES\n--\n0.0 200.0 400.0 /\n--\n-- VELOCITY VALUES\n--\n0.0 50.0 70.0 100.0 /\n--\n-- POLYMW VALUES\n--\n20.0 19.0 18.0 16.0 / POLYMW(OUTPUT=1, VELOCITY=1 TO N)\n20.0 16.0 14.0 12.0 / POLYMW(OUTPUT=2, VELOCITY=1 TO N)\n20.0 12.0 8.0 4.0 / POLYMW(OUTPUT=3, VELOCITY=1 TO N)\n/\nAs mentioned previously, the PLYMWINJ keyword requires that the keyword itself must be repeated for each table, as is shown in the above example.\n| Note This is an OPM Flow specific keyword that employs an alternative polymer flood model based on a Polymer Molecular Weight Transport equation, that is not available in the commercial simulator. The model has been tested using metric units; however, using either field or laboratory units with the option should be considered experimental. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","records_meta":[{"expected_columns":1},{},{},{}],"size_kind":"list"},"PLYRMDEN":{"name":"PLYRMDEN","sections":["GRID"],"supported":null,"summary":"The PLYRMDEN keyword defines the in situ rock density at reservoir conditions by individual cell, for when the Polymer option has been activated by the POLYMER keyword in the RUNSPEC section. PLYRMDEN should consist of an array of real positive values. See the DENSITY parameter on the PLYROCK keyword in the PROPS section for setting the property for the whole grid.","parameters":[],"example":"","size_kind":"array"},"PLYROCK":{"name":"PLYROCK","sections":["PROPS"],"supported":null,"summary":"The PLYROCK keyword defines rock properties for when the Polymer option has been activated by the POLYMER keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"PSPACE","description":"A real positive value that is greater than or equal to zero and less the maximum water saturation and less than one, that defines available pore space for this rock type.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":"1"},{"index":2,"name":"PERMFAC","description":"A real positive value that is greater than or equal to one that defines decrease in the rock permeability to the water phase when the maximum amount of polymer has been adsorbed.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"DENSITY","description":"A real value that defines the rock in-situ density, that is at reservoir conditions.","units":{"field":"lb/rb","metric":"kg/rm3","laboratory":"gm/rcc"},"default":"None","value_type":"DOUBLE","dimension":"Density"},{"index":4,"name":"ADINDX","description":"A positive integer of 1 or 2 that defines the polymer desorption option. then polymer desorption may occur by retracing the polymer adsorption isotherm when the local polymer concentration in the solution decreases. then no polymer desorption may occur.","units":{"field":"dimensionless 1","metric":"dimensionless 1","laboratory":"dimensionless 1"},"default":"Defined","value_type":"DOUBLE","dimension":"1"},{"index":5,"name":"POLMAX","description":"A real positive non-zero value that defines the maximum polymer adsorption to be used in the calculation of the resistance factor for the water phase.","units":{"field":"lb/lb","metric":"kg/kg","laboratory":"gm/gm"},"default":"None","value_type":"DOUBLE","dimension":"1"}],"example":"--\n-- POLYMER-ROCK PROPERTIES\n--\nPLYROCK\n-- PORE PERM INSITU DESORP MAX\n-- SPACE FACTOR DENSITY OPTN POLY\n-- ------ -------- ------- ------ -------\n0.1200 1.7500 1800.0 1 0.00012 / TABLE NO. 01\n0.1300 1.8500 1980.0 2 0.00015 / TABLE NO. 02\n0.1500 1.9500 2005.0 1 0.00014 / TABLE NO. 03\nThe above example defines three polymer-rock tables, based on the NTSFUN variable on the TABDIMS keyword in the RUNSPEC section being equal to three.\nThere is no terminating “/” for this keyword.","expected_columns":5,"size_kind":"fixed"},"PLYSHEAR":{"name":"PLYSHEAR","sections":["SPECIAL","PROPS"],"supported":false,"summary":"The PLYSHEAR keyword activates and defines the polymer shear thinning-thickening option for when the polymer option has been activated by the POLYMER keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"VELOCITY","description":"A columnar vector of real monotonically increasing down the column values that defines the water-polymer flow velocity. The VELOCITY value for the first row in the table should be zero.","units":{"field":"feet/day","metric":"m/day","laboratory":"cm/hour"},"default":"None","value_type":"DOUBLE","dimension":["Length/Time","1"]},{"index":2,"name":"VISFAC","description":"A columnar vector of real values that defines a factor that scales the effective water and polymer viscosities for when shear thinning-thickening of the polymer occurs. Normally VISFAC value for the first row in the table should be one.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- ACTIVATE AND DEFINE POLYMER SHEARING PARAMETERS\n--\nPLYSHEAR\n-- WAT-POLY VISCOSITY\n-- VELOCITY FACTOR\n-- -------- ---------\n0.0 1.000\n1.0 0.900\n3.0 0.800\n6.0 0.700 / TABLE NO. 01\n-- WAT-POLY VISCOSITY\n-- VELOCITY FACTOR\n-- -------- ---------\n0.0 1.000\n1.0 0.900\n2.0 0.800\n4.0 0.750\n6.0 0.700\n8.0 0.650 / TABLE NO. 02\nThe above example activates the polymer shear thinning-thickening option and defines two polymer shear thinning-thickening tables, based on the NTPVT variable on the TABDIMS keyword in the RUNSPEC section being equal to two and NPPVT variable on the same keyword being greater than or equal to six.","size_kind":"fixed","variadic_record":true},"PLYSHLOG":{"name":"PLYSHLOG","sections":["SPECIAL","PROPS","SCHEDULE"],"supported":null,"summary":"This keyword activates and defines the parameters for the logarithm-based polymer shear thinning/thickening option.","parameters":[{"index":1,"name":"POLCON","description":"A real positive value that defines the reference polymer concentration for the VELOCITY and VISFAC data for this keyword.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None","record":1,"value_type":"DOUBLE","dimension":"Concentration"},{"index":2,"name":"SALTCON","description":"A real positive value that defines the reference salt concentration for the VELOCITY and VISFAC data for this keyword. Note that If the BRINE option has not been activated by the BRINE keyword in the RUNSPEC section, then this variable is ignored. This variable is ignored as the BRINE option is not implemented in OPM Flow.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None","record":1,"value_type":"DOUBLE","dimension":"Concentration"},{"index":3,"name":"TEMP","description":"A real positive value defines the reference polymer temperature for the VELOCITY and VISFAC data for this keyword. Note that If the TEMP option has not been activated by the TEMP keyword in the RUNSPEC section, then this variable is ignored. This variable is ignored as the TEMP and POLYMER options combination is not implemented in OPM Flow.","units":{"field":"oF","metric":"oC","laboratory":"oC"},"default":"None","record":1,"value_type":"DOUBLE","dimension":"Temperature"},{"index":1,"name":"VELOCITY","description":"A columnar vector of real monotonically increasing down the column values that defines the water-polymer flow velocity for the reference conditions of POLCON, SALTCON and TEMP. The VELOCITY value for the first row in the table should be a very small value that is greater than zero and less than 1 x 10-6.","units":{"field":"feet/day","metric":"m/day","laboratory":"cm/hour"},"default":"None","record":2,"value_type":"DOUBLE","dimension":["1","1"]},{"index":2,"name":"VISFAC","description":"A columnar vector of real positive values that define the dimensionless shear effect multiplier for the given VELOCITY entry for the reference conditions of POLCON, SALTCON and TEMP. Normally VISFAC value for the first row in the table should be one.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","record":2}],"example":"The following example show how to enter two PLYSHLOG tables given that the NTPVT variable on the TABDIMS keyword in the RUNSPEC section is set equal to two.\n--\n-- POLYMER SHEARING LOGARITHMIC PARAMETERS\n--\nPLYSHLOG\n-- REF REF REF\n-- POLCON SALTCON TEMP\n-- -------- ------- ----\n0.5\n/\n--\n-- VELOCITY VISFAC\n-- -------- -------\n0.0000001 1.00\n0.000001 1.10\n0.0001 1.30\n0.001 1.47\n0.01 1.67\n0.1 2.00\n1.0 2.20\n10.0 2.30\n100.0 2.40\n1000.0 2.40\n/ TABLE NO. 01\n-- REF REF REF\n-- POLCON SALTCON TEMP\n-- -------- ------- ----\n0.5\n/\n--\n-- VELOCITY VISFAC\n-- -------- -------\n0.0000001 1.00\n0.000001 1.10\n0.0001 1.35\n0.001 1.57\n0.01 1.87\n0.1 2.20\n1.0 2.40\n10.0 2.60\n100.0 2.65\n1000.0 2.65\n/ TABLE NO. 02\nThe example activates the polymer logarithmic shear thinning-thickening option and defines two polymer shear thinning-thickening tables, based on the NTPVT variable on the TABDIMS keyword in the RUNSPEC section being equal to two and NPPVT variable on the same keyword being greater than or equal to ten.","records_meta":[{"expected_columns":3},{}],"size_kind":"fixed","size_count":2},"PLYTRRF":{"name":"PLYTRRF","sections":["PROPS"],"supported":false,"summary":"The PLYTRRF keyword defines the polymer rock permeability reduction factor to the water phase as a function of temperature, for when the Polymer option has been activated by the POLYMER keyword in the RUNSPEC section. See the PLYTRRF keyword for the options on how this data is used in the polymer model and the PERMFAC parameter on the PLYROCK keyword for setting the property for the whole grid for a constant temperature. Both keywords are in the PROPS section.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Temperature","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"PLYTRRFA":{"name":"PLYTRRFA","sections":["PROPS"],"supported":false,"summary":"The PLYTRRFA keyword defines the how the polymer rock permeability reduction factor to the water phase as a function of temperature data, entered via the PLYTRRA keyword in the PROPS section, should be used. This keyword should only be used if the Polymer option has been activated by the POLYMER keyword in the RUNSPEC section. See the PERMFAC parameter on the PLYROCK keyword in the PROPS section for setting the property for the whole grid for a constant temperature.","parameters":[{"index":1,"name":"NBTRRF","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"PLYVISC":{"name":"PLYVISC","sections":["SPECIAL","PROPS","SCHEDULE"],"supported":null,"summary":"PLYSVISC defines the polymer viscosity scaling factors used to determine the relationship of pure water viscosity with respect to increasing polymer concentration within a grid block. The polymer option must be activated by the POLYMER keyword in the RUNSPEC section in order to use this keyword.","parameters":[{"index":1,"name":"POLCON","description":"A columnar vector of real monotonically increasing down the column values that defines the polymer concentration in the solution surrounding the rock. The first entry should be zero to define a no polymer concentration.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None","value_type":"DOUBLE","dimension":["Concentration","1"]},{"index":2,"name":"VISFAC","description":"A columnar vector of real increasing or equal values that defines a factor that scales the effective viscosity of the solution for the given POLCON entry. Normally VISFAC value for the first row in the table should be one.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- POLYMER VISCOSITY SCALING FACTOR TABLES\n--\nPLYVISC\n-- POLYMER VISCOSITY\n-- POLCON VISFAC\n-- -------- ---------\n0.0000 1.000\n0.0002 10.000\n0.0004 20.000\n0.0008 40.000 / TABLE NO. 01\n-- POLYMER VISCOSITY\n-- POLCON VISFAC\n-- -------- ---------\n0.0000 1.000\n0.0003 10.000\n0.0005 20.000\n0.0007 40.000\n0.0009 45.000\n0.0011 55.000 / TABLE NO. 02\nThe example defines two polymer viscosity scaling factor tables, based on the NTPVT variable on the TABDIMS keyword in the RUNSPEC section being equal to two and NPPVT variable on the same keyword being greater than or equal to six.","size_kind":"fixed","variadic_record":true},"PLYVISCS":{"name":"PLYVISCS","sections":["PROPS","SCHEDULE"],"supported":false,"summary":"PLYSVISCS defines the polymer-salt viscosity scaling factor tables applied to pure water that are used to determine the viscosity of a polymer-salt mixture with respect to increasing polymer concentration within a grid block. The polymer option must be activated by the POLYMER keyword, as well as the brine phase declared by the BRINE keyword in the RUNSPEC section in order to use this keyword. However the ECLM keyword in the RUNSPEC must not be used with this keyword.","parameters":[{"index":1,"name":"PC","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Mass/LiquidSurfaceVolume"},{"index":2,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","size_kind":"fixed","variadic_record":true},"PLYVISCT":{"name":"PLYVISCT","sections":["PROPS","SCHEDULE"],"supported":false,"summary":"PLYSVISCT defines the polymer-temperature viscosity scaling factor tables applied to pure water that are used to determine the viscosity of the polymer at a given temperature with respect to increasing polymer concentration within a grid block. Both the polymer option must be activated by the POLYMER keyword and the temperature option invoked by the TEMP keyword in the RUNSPEC section in order to use this keyword. However the BRINE keyword in the RUNSPEC must not be used with this keyword, that is the salt sensitivity options should be deactivated.","parameters":[{"index":1,"name":"PC","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Mass/LiquidSurfaceVolume"},{"index":2,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","size_kind":"fixed","variadic_record":true},"PLYVMH":{"name":"PLYVMH","sections":["PROPS"],"supported":null,"summary":"This keyword, PLYVMH, defines the constants used to calculate viscosity of the polymer solution as a function of the polymer molecular weight and the polymer concentration, for the simulator's Polymer Molecular Weight Transport option, that uses the polymer molecular weight in calculating the polymer viscosity. The keyword consists of a series of row vectors, which each vector having four elements, that define the constants used in calculating the polymer viscosity","parameters":[{"index":1,"name":"K_MH","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":2,"name":"MHA","description":"The Mark-Houwink exponent parameter a, in the Mark-Houwink equation, see equation (8.77).","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"GAMMA","description":"The ɣ intrinsic water-polymer viscosity constant in the Huggins equation, see equation (8.79).","units":{},"default":"None","value_type":"DOUBLE","dimension":"1"},{"index":4,"name":"KAPPA","description":"The κ intrinsic water-polymer viscosity constant in the Huggins equation, see equation (8.79).","units":{},"default":"None","value_type":"DOUBLE","dimension":"1"}],"example":"Given NPLYVMH equals two on the PINTDIMS keyword in the RUNSPEC section, then:\n--\n-- POLYMER MOLECULAR WEIGHT MODEL POLYMER VISCOSITY CONSTANTS\n-- (OPM FLOW PROPS KEYWORD)\n--\n-- MHK MHA VISC VISC\n-- CONST EXPON GAMMA KAPPA\nPLYVMH\n0.02 0.50 0.40 0.60 /\n0.03 0.51 0.42 0.63 /\n/\nTwo sets of data should be entered with the PLYVMH keyword, as shown above.\n| Note This is an OPM Flow specific keyword that employs an alternative polymer flood model based on a Polymer Molecular Weight Transport equation, that is not available in the commercial simulator. The model has been tested using metric units; however, using either field or laboratory units with the option should be considered experimental. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| [%eta_rel~=~ %eta over %eta_s] | (8.73) |\n|--------------------------------|--------|\n| [%eta_{\"sp\"} ~=~ left( %eta - %eta_s right) over %eta_s newline\n~~~`\" \" = ~ %eta over %eta_s ``-`` 1 newline\n~~~````\" \" = ~ %eta_rel ``-`` 1] | (8.74) |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|--------|\n| [%eta_{\"red\"} ~=~ %eta_\"sp\" over C_p newline\n~~~~~~~~~~````\" \" = ~left( %eta_rel ``-`` 1 right) over C_p] | (8.75) |\n|------------------------------------------------------------------------------------------------------------|--------|\n| [left [%eta right ] ~=~ lim from{ C_p toward 0 } {%eta_\"sp\" over C_p} newline\n~~~~~``\" \" = ~lim from{ C_p toward 0 } {{%eta - %eta_0} over {%eta_0 C_p}}] | (8.76) |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|\n| [left [%eta right ] ~=~ K` cdot `{M_w}^a] | (8.77) |\n|-------------------------------------------|--------|\n| [ln left( [%eta] right) ~=~ ln(K) ~+~ a `times `ln (M_w)] | (8.78) |\n|-----------------------------------------------------------|--------|\n| [~~~~~~~~~~~%eta_0 over %eta_s ~=~ 1``+`` %gamma left(X``+`` %kappa X^2 right) newline \n\"where\"~~~~~ \nX~=~ left[%eta right] C_p] | (8.79) |\n|----------------------------------------------------------------------------------------------------------------------------------|--------|\n| [left[ %eta right]~ = ~ K left(M_w ` cdot `1.0 times 10^-3 right)^a dot \" \" 1.0 times 10^-3] | (8.80) |\n|-----------------------------------------------------------------------------------------------|--------|\n| [~~~~~~~~~~~%eta_0 over %eta_s ~=~ 1``+`` %gamma left(X``+`` %kappa X^2 right) newline \n\"where\"~~~~~ \nX~=~ 1.0 times 10^-6left[%eta right] C_p] | (8.81) |\n|-------------------------------------------------------------------------------------------------------------------------------------------------|--------|","expected_columns":4,"size_kind":"fixed"},"PLYVSCST":{"name":"PLYVSCST","sections":["PROPS","SCHEDULE"],"supported":false,"summary":"PLYVSCST defines the polymer-salt-temperature viscosity scaling factor tables applied to pure water that are used to determine the viscosity of the polymer at a given salt concentration and for a given temperature, with respect to increasing polymer concentration within a grid block. Both the polymer option must be activated by the POLYMER keyword and the temperature option invoked by the TEMP keyword in the RUNSPEC section in order to use this keyword. In addition, the BRINE keyword in the RUNSPEC must also be invoked. The keyword is used in conjunction with the SALTNODE keyword to define the various salt concentrations and the TEMPNODE keyword to define the various reservoir temperatures. Both keywords are in the PROPS section.","parameters":[{"index":1,"name":"PC1","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Mass/LiquidSurfaceVolume"},{"index":2,"name":"MULT","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","size_kind":"list","variadic_record":true},"PMAX":{"name":"PMAX","sections":["PROPS"],"supported":false,"summary":"The PMAX keyword defines the maximum and minimum pressures expected to be encountered during the run. The data is used to perform the PVT total compressibility check that ensures that the total compressibility of a mixture of oil-gas, for when the gas-oil ratio is increasing for an oil, or the condensate gas ratio is increasing for a gas condensate, is positive respect to pressure. The total compressibility check is used to ensure that the entered oil and gas PVT data is consistent. If the check fails for given oil-gas mixture at a given pressure, resulting in a negative total compressibility, then this will result in numerical instabilities in the run causing this simulator difficulties in converging to a solution.","parameters":[{"index":1,"name":"MAX_PRESSURE","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":2,"name":"MAX_PRESSURE_CHECK","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Pressure"},{"index":3,"name":"MIN_PRESSURE_CHECK","description":"","units":{},"default":"1e+20","value_type":"DOUBLE","dimension":"Pressure"},{"index":4,"name":"NUM_NODES","description":"","units":{},"default":"30","value_type":"INT"}],"example":"","expected_columns":4,"size_kind":"fixed","size_count":1},"PMISC":{"name":"PMISC","sections":["PROPS"],"supported":null,"summary":"PMISC defines the transition between immiscible and miscible displacement as a function of oil pressure tables, for when the MISCIBLE keyword in the RUNSPEC section has be activated. If this keyword is absent from the input deck and MISCIBLE keyword in the RUNSPEC keyword has been activated, then miscibility is independent of the oil phase pressure.","parameters":[{"index":1,"name":"PRESS","description":"A columnar vector of real monotonically increasing down the column values that defines the oil phase pressure.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":["Pressure","1"]},{"index":2,"name":"MISC","description":"A columnar vector of real equal or increasing down the column values that defines the corresponding miscibility factor. MISC is a scaling that should lie be zero and one, where zero means no miscibility and one means full miscibility.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- MISCIBILITY VERSUS PRESSURE TABLES\n--\nPMISC\n-- OIL MISCIBILE\n-- PRESS FACTOR\n-- ------- ---------\n1000.0 0.000\n2000.0 0.250\n3000.0 1.000\n4000.0 1.000 / TABLE NO. 01\n-- OIL MISCIBILE\n-- PRESS FACTOR\n-- ------- ---------\n1500.0 0.000\n2000.0 0.000\n2500.0 0.250\n3000.0 0.350\n3500.0 1.000\n4000.0 1.000 / TABLE NO. 02\nThe above example defines two miscibility versus pressure tables assuming NTMISC equals two and NSMISC is greater than or equal to six on the MISCIBLE keyword in the RUNSPEC section.","size_kind":"fixed","variadic_record":true},"PPCWMAX":{"name":"PPCWMAX","sections":["PROPS"],"supported":null,"summary":"The PPCWMAX keyword defines the maximum capillary pressure allowed when scaling the capillary pressure tables to match the inputted SWATINIT array. This is primary used for when the SWATINIT array has values of water saturation above the connate water saturation significantly outside than capillary pressure transition zone, that is high on the structure. In this case OPM Flow may generate large values for the capillary pressure which may result in numerical converge problems. This keyword sets the maximum allowable calculated capillary pressure and how the water saturation should be treated when the limit is exceeded.","parameters":[{"index":1,"name":"PCWO","description":"A columnar vector of real values that defines the maximum allowable capillary pressure for each SATNUM region. The default value of infinity means there is no limit applied.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"Infinity","value_type":"DOUBLE","dimension":"Pressure"},{"index":2,"name":"OPTN","description":"A columnar vector of character strings that should be set to: NO: To ignore the SWATINIT value for the offending cell for when PCWO is exceeded. In this cases the capillary pressure for the block is set to the maximum (PCWO) and the water saturation is re-calculated based on PCWO. YES: To set the SWATINIT value to the connate water saturation for the offending cell for when PCWO is exceeded. In this case the capillary pressure is set to the maximum value of the appropriate SATNUM table and the initial water saturation is calculated to be consistent with the tables maximum capillary pressure. This results in the capillary pressures not being re-scale for the offending cell.","units":{},"default":"No","value_type":"STRING"}],"example":"--\n-- SET MAXIMUM PC FOR SWATINIT INITIALIZATION\n-- MAX MATCH\n-- PC SWATINIT\n-- -------- --------\nPPCWMAX\n100.0 YES / TABLE NO 01\n125.0 YES / TABLE NO 02\n135.0 YES / TABLE NO 03\nThe above example sets the maximum capillary pressure for three saturation regions to 100, 125 and 135 with SWATINIT reset to the connate water saturation for when the capillary pressure limit is exceeded.\n| Note Using this keyword to limit the re-scaled grid block capillary pressure values will effect the fluids in-place when the simulator has to re-calculate values due to the capillary pressure limit being exceeded. In addition, the high grid block capillary pressures may be indicative of an inconsistency between the tabular SATNUM capillary pressure values and the provided SWATINIT array water saturations. This inconsistency may be a result of the SWATINIT array being derived using a saturation height function, as is customary in static modeling software, and the numerical models tabulated capillary pressure. Rather than resetting the maximum calculated capillary pressure using the PPCWMAX keyword, it may be more appropriate to investigate the reason for the high capillary pressures values first, prior to applying the keyword. |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":2,"size_kind":"fixed"},"PROPS":{"name":"PROPS","sections":["PROPS"],"supported":null,"summary":"The PROPS activation keyword marks the end of the EDIT section and the start of the PROPS section that defines the key fluid and rock property data for the simulator","parameters":[],"example":"-- ==============================================================================\n--\n-- PROPS SECTION\n--\n-- ==============================================================================\nPROPS\nThe above example marks the end of the EDIT section and the start of the PROPS section in the OPM Flow data input file.","size_kind":"none","size_count":0},"PVCDO":{"name":"PVCDO","sections":["PROPS"],"supported":null,"summary":"PVCDO defines the oil PVT properties for dead oil1\n “Dead” oil is oil that it contains no dissolved gas or a relatively thick oil or residue that has lost its volatile components. with constant compressibility. If the oil has a constant and uniform dissolved gas concentration, Gas-Oil Ratio (“GOR”), and if the reservoir pressure never drops below the saturation pressure (bubble point pressure), then the model can be run more efficiently by omitting the GAS and DISGAS keywords from the RUNSPEC section, treating the oil as a dead oil, and defining a constant Rs (GOR) value with keyword RSCONST or RSCONSTT in the PROPS section. This results in the model being run as a dead oil problem with no active gas phase. However, OPM Flow takes into account the constant Rs in the calculations and reporting.","parameters":[{"index":1,"name":"PRESS","description":"PRESS is a real positive value defining the oil reference pressure for the other parameters for this data set.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":"Pressure"},{"index":2,"name":"OFVF","description":"OFVF is a real positive value defining the oil formation volume factor (Bo) at the reference pressure.","units":{"field":"rb/stb","metric":"rm3/sm3","laboratory":"rcc/scc"},"default":"None","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"OCOMP","description":"OCOMP is a real positive value defining the oil compressibility (Co) at the oil reference pressure and is defined as: [C sub{o}~=~ - 1 over {B sub{o}}left({dB sub{o}} over{dP} right)]","units":{"field":"1/psia","metric":"1/barsa","laboratory":"1/atma"},"default":"None","value_type":"DOUBLE","dimension":"1/Pressure"},{"index":4,"name":"OVISC","description":"OVISC is a real positive value defining the oil viscosity (µo) at the oil reference pressure.","units":{"field":"cP","metric":"cP","laboratory":"cP"},"default":"None","value_type":"DOUBLE","dimension":"Viscosity"},{"index":5,"name":"OVISCOMP","description":"OVISCOMP is a real positive value defining the oil viscosibility (µoc) at the oil reference pressure and is defined as: [%mu sub{oc}~=~ 1 over { %mu sub{o}}left({d%mu sub{o}} over{dP} right)]","units":{"field":"1/psia","metric":"1/barsa","laboratory":"1/atma"},"default":"None","value_type":"DOUBLE","dimension":"1/Pressure"}],"example":"--\n-- OIL PVT TABLE FOR DEAD WITH CONSTANT COMPRESSIBILITY\n--\nPVCDO\n-- REF PRES BO CO VISC VISC\n-- PSIA RB/STB 1/PSIA CPOISE GRAD\n-- -------- -------- ------- ------ ------\n3840.0 1.080 1.5E-6 1.750 0.0 / TABLE NO. 01\n3840.0 1.100 1.5E-6 1.050 0.0 / TABLE NO. 02\n3840.0 1.120 1.6E-6 0.950 0.0 / TABLE NO. 03\n3840.0 1.140 1.7E-6 0.850 0.0 / TABLE NO. 04\n3840.0 1.160 1.7E-6 0.800 0.0 / TABLE NO. 05\nThe above example defines five dead oil PVT tables with constant compressibility and viscosity, and assumes that NTPVT equals five on the TABDIMS keyword in the RUNSPEC section.\nThere is no terminating “/” for this keyword.","expected_columns":5,"size_kind":"fixed"},"PVCO":{"name":"PVCO","sections":["PROPS"],"supported":false,"summary":"PVCO defines the oil PVT properties for live216\n “Live” oil is oil that contains gas in solution, which is normally the case for most conventional oil reservoirs. However, for oil reservoirs classified as heavy oil reservoirs, the in situ dissolved gas may be negligible and oil would then be classified as gas-free oil which is commonly referred to as “dead” oil. and the keyword should only be used if the there is both oil and gas phases in the model. This keyword should be used when the DISGAS keyword has be declared in the RUNSPEC section indicating that dissolved gas (more commonly referred to as solution gas) is present in the oil. The keyword may be used for oil-water and oil-water-gas input decks. This is an alternative keyword to the PVTO keyword in the PROPS section that also enables entering live oil PVT data. Here, the PVCO keyword assumes that for the undersaturated oil with a given Gas-Oil Ratio (“GOR” or “Rs”), the oil compressibility is independent of the pressure....","parameters":[{"index":1,"name":"PRESS","description":"PRESS is a real columnar vector of real monotonically increasing down the column values that defines the oil phase saturation pressure (bubble-point pressure), that defines the RS, oil formation volume factor and the oil viscosity at PRESS.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":["Pressure","GasSurfaceVolume/LiquidSurfaceVolume","ReservoirVolume/LiquidSurfaceVolume","Viscosity","1/Pressure","1/Pressure"]},{"index":2,"name":"RS","description":"RS is a real monotonically increasing down the column values that defines the saturated gas-oil ratio (“GOR”) or Rs, for the given value of PRESS.","units":{"field":"Mscf/stb","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"1*"},{"index":3,"name":"OFVF","description":"OFVF is a real positive value defining the oil saturated formation volume factor (Bo) at the saturation pressure PRESS.","units":{"field":"rb/stb","metric":"rm3/sm3","laboratory":"rcc/scc"},"default":"None"},{"index":4,"name":"OVISC","description":"OVISC is a real positive value defining the oil viscosity (µo) at the oil saturated reference pressure, PRESS.","units":{"field":"cP","metric":"cP","laboratory":"cP"},"default":"1*"},{"index":5,"name":"OCOMP","description":"OCOMP is a real positive value defining the oil compressibility (Co) at the saturated oil reference pressure and is defined as: [C sub{o}~=~ - 1 over {B sub{o}}left({dB sub{o}} over{dP} right)]","units":{"field":"1/psia","metric":"1/barsa","laboratory":"1/atma"},"default":"1*"},{"index":6,"name":"OVISCOMP","description":"OVISCOMP is a real positive value defining the oil viiscosibility (µoc) at the saturated oil reference pressure with the given RS, where (µoc) is defined as: [%mu sub{oc}~=~ - 1 over { %mu sub{o}}left({d%mu sub{o}} over{dP} right)]","units":{"field":"1/psia","metric":"1/barsa","laboratory":"1/atma"},"default":"1*"}],"example":"--\n-- OIL PVT TABLE FOR LIVE OIL\n--\nPVCO\n-- PSAT RS BO VISC OIL OIL\n-- PSIA MSCF/STB RB/STB CPOISE COMPRES VISCOS\n-- -------- -------- ------- ------ ------- ------\n14.7 0.0010 1.05340 1.7230 3.0E-5 1*\n500.0 0.0890 1.08890 1.1670 1* 1*\n1000.0 0.2060 1.13850 0.8570 1* 1*\n1500.0 0.3360 1.19640 0.6840 1* 1*\n2000.0 0.4750 1.26110 0.5750 1* 1*\n2500.0 0.6220 1.33160 0.5000 1* 1*\n3000.0 0.7750 1.40740 0.4450 1* 1*\n3500.0 0.9330 1.48790 0.4020 1* 1*\n4000.0 1.0960 1.57280 0.3680 1* 1*\n4258.0 1.1800 1.61760 0.3530 1* 1*\n4500.0 1.2630 1.66190 0.3400 1* 1*\n5000.0 1.4340 1.75480 0.3170 1* 1*\n5500.0 1.6060 1.85020 0.2980 1* 1* / TABLE NO. 01\n--\n-- PSAT RS BO VISC OIL OIL\n-- PSIA MSCF/STB RB/STB CPOISE COMPRES VISCOS\n-- -------- -------- ------- ------ ------- ------\n14.7 0.0010 1.05340 1.7230 3.0E-5 1*\n500.0 0.0890 1.08890 1.1670 1* 1*\n1000.0 0.2060 1.13850 0.8570 1* 1*\n1500.0 0.3360 1.19640 0.6840 1* 1*\n2000.0 0.4750 1.26110 0.5750 1* 1*\n2500.0 0.6220 1.33160 0.5000 1* 1*\n3000.0 0.7750 1.40740 0.4450 1* 1*\n3500.0 0.9330 1.48790 0.4020 1* 1*\n4000.0 1.0960 1.57280 0.3680 1* 1*\n4258.0 1.1800 1.61760 0.3530 1* 1*\n4500.0 1.2630 1.66190 0.3400 1* 1*\n5000.0 1.4340 1.75480 0.3170 1* 1*\n5500.0 1.6060 1.85020 0.2980 1* 1* / TABLE NO. 02\nThe example defines two live oil PVT tables with constant compressibility above the saturation pressure, and assumes that NTPVT equals two on the TABDIMS keyword in the RUNSPEC section.","size_kind":"fixed","variadic_record":true},"PVDG":{"name":"PVDG","sections":["PROPS"],"supported":null,"summary":"PVDG defines the gas PVT properties for dry gas217\n Natural gas that occurs in the absence of condensate or liquid hydrocarbons, or gas that had condensable hydrocarbons removed, is called dry gas. It is primarily methane with some intermediates. The hydrocarbon mixture is solely gas in the reservoir and there is no liquid (condensate surface liquid) formed either in the reservoir or at surface. The term dry indicates that the gas does not contain heavier hydrocarbons to form liquids at the surface conditions. Dry gas typically has GOR's greater than 100,000 scf/stb or 18,000 Sm3/m3. . If the gas has a constant and uniform vaporized oil concentration, Condensate-Gas Ratio (“CGR”), and if the reservoir pressure never drops below the saturation pressure (dew point pressure), then the model can be run more efficiently by omitting the OIL and VAPOIL keywords from the RUNSPEC section, treating the gas as a dry gas, and defining a constant Rv (CGR) value with keyword RVCONST or RVCONS...","parameters":[{"index":1,"name":"PRESS","description":"A columnar vector of real monotonically increasing down the column values that defines the gas phase pressure.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":["Pressure","OilDissolutionFactor","Viscosity"]},{"index":2,"name":"GFVF","description":"A columnar vector of real decreasing down the column values that defines the corresponding gas phase formation volume factor.","units":{"field":"rb/Mscf","metric":"rm3/sm3","laboratory":"rcc/scc"},"default":"None"},{"index":3,"name":"GVISC","description":"A columnar vector of real increasing down the column values that defines the corresponding gas phase viscosity.","units":{"field":"cP","metric":"cP","laboratory":"cP"},"default":"None"}],"example":"The first example below defines two dry gas PVT tables assuming NTPVT equals two and NPPVT is greater than or equal to 22 on the TABDIMS keyword in the RUNSPEC section.\n--\n-- GAS PVT TABLE FOR DRY GAS\n--\nPVDG\n-- PRES BG VISC\n-- PSIA RB/MSCF CPOISE\n-- ------ -------- ------\n14.7 197.8092 0.0129\n50.0 65.9364 0.0130\n100.0 31.6495 0.0130\n230.0 13.8813 0.0131\n460.0 6.8210 0.0132\n690.0 4.4703 0.0135\n920.0 3.2968 0.0138\n1150.0 2.6113 0.0141\n1380.0 2.1560 0.0145\n1610.0 1.8316 0.0150\n1840.0 1.5952 0.0155\n2070.0 1.4129 0.0161\n2300.0 1.2700 0.0167\n2372.0 1.2305 0.0169\n2530.0 1.1551 0.0174\n2760.0 1.0621 0.0181\n2990.0 0.9841 0.0189\n3220.0 0.9190 0.0196\n3450.0 0.8638 0.0204\n4500.0 0.6910 0.0242\n6000.0 0.5616 0.0293 / TABLE N0. 01\n--\n-- PRES BG VISC\n-- PSIA RB/MSCF CPOISE\n-- ------ -------- ------\n14.7 265.0126 0.0133\n50.0 66.2531 0.0133\n100.0 33.1266 0.0133\n230.0 14.4552 0.0134\n460.0 7.0357 0.0136\n690.0 4.6493 0.0138\n920.0 3.4417 0.0140\n1150.0 2.7227 0.0144\n1380.0 2.2522 0.0147\n1610.0 1.9158 0.0151\n1840.0 1.6702 0.0156\n2070.0 1.4805 0.0162\n2300.0 1.3317 0.0167\n2372.0 1.2927 0.0169\n2530.0 1.2119 0.0173\n2760.0 1.1135 0.0180\n2990.0 1.0325 0.0187\n3220.0 0.9637 0.0194\n3450.0 0.9055 0.0201\n4500.0 0.7228 0.0236\n6000.0 0.5837 0.0285 / TABLE N0. 02\nThe second example defines four dry gas PVT tables assuming NTPVT equals four and NPPVT is greater than or equal to 22 on the TABDIMS keyword in the RUNSPEC section. Here table two defaults to table one, and table four defaults to table three.\n--\n-- GAS PVT TABLE FOR DRY GAS\n--\nPVDG\n-- PRES BG VISC\n-- PSIA RB/MSCF CPOISE\n-- ------ -------- ------\n14.7 197.8092 0.0129\n50.0 65.9364 0.0130\n100.0 31.6495 0.0130\n230.0 13.8813 0.0131\n460.0 6.8210 0.0132\n690.0 4.4703 0.0135\n920.0 3.2968 0.0138\n1150.0 2.6113 0.0141\n1380.0 2.1560 0.0145\n1610.0 1.8316 0.0150\n1840.0 1.5952 0.0155\n2070.0 1.4129 0.0161\n2300.0 1.2700 0.0167\n2372.0 1.2305 0.0169\n2530.0 1.1551 0.0174\n2760.0 1.0621 0.0181\n2990.0 0.9841 0.0189\n3220.0 0.9190 0.0196\n3450.0 0.8638 0.0204\n4500.0 0.6910 0.0242\n6000.0 0.5616 0.0293 / TABLE N0. 01\n/ TABLE N0. 02\n--\n-- PRES BG VISC\n-- PSIA RB/MSCF CPOISE\n-- ------ -------- ------\n14.7 265.0126 0.0133\n50.0 66.2531 0.0133\n100.0 33.1266 0.0133\n230.0 14.4552 0.0134\n460.0 7.0357 0.0136\n690.0 4.6493 0.0138\n920.0 3.4417 0.0140\n1150.0 2.7227 0.0144\n1380.0 2.2522 0.0147\n1610.0 1.9158 0.0151\n1840.0 1.6702 0.0156\n2070.0 1.4805 0.0162\n2300.0 1.3317 0.0167\n2372.0 1.2927 0.0169\n2530.0 1.2119 0.0173\n2760.0 1.1135 0.0180\n2990.0 1.0325 0.0187\n3220.0 0.9637 0.0194\n3450.0 0.9055 0.0201\n4500.0 0.7228 0.0236\n6000.0 0.5837 0.0285 / TABLE N0. 03\n/ TABLE N0. 04\nThere is no terminating “/” for this keyword.","size_kind":"fixed","variadic_record":true},"PVDO":{"name":"PVDO","sections":["PROPS"],"supported":null,"summary":"PVDO defines the oil PVT properties for dead oil218\n “Dead” oil is oil that it contains no dissolved gas or a relatively thick oil or residue that has lost its volatile components. . If the oil has a constant and uniform dissolved gas concentration, Gas-Oil Ratio (“GOR”), and if the reservoir pressure never drops below the saturation pressure (bubble point pressure), then the model can be run more efficiently by omitting the GAS and DISGAS keywords from the RUNSPEC section, treating the oil as a dead oil, and defining a constant Rs (GOR) value with keyword RSCONST or RSCONSTT in the PROPS section. This results in the model being run as a dead oil problem with no active gas phase. However, OPM Flow takes into account the constant Rs in the calculations and reporting.","parameters":[{"index":1,"name":"PRESS","description":"A columnar vector of real monotonically increasing down the column values that defines the oil phase pressure.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":["Pressure","1","Viscosity"]},{"index":2,"name":"OFVF","description":"A columnar vector of real decreasing down the column values that defines the corresponding oil phase formation volume factor.","units":{"field":"rb/stb","metric":"rm3/sm3","laboratory":"rcc/scc"},"default":"None"},{"index":3,"name":"OVISC","description":"A columnar vector of real increasing down the column values that defines the corresponding oil phase viscosity.","units":{"field":"cP","metric":"cP","laboratory":"cP"},"default":"None"}],"example":"The example below defines two dead oil PVT tables with variable viscosity and compressibility with respect to pressure, and assumes that NTPVT equals two and NPPVT is greater than or equal to eight on the TABDIMS keyword in the RUNSPEC section.\n--\n-- OIL PVT TABLE FOR DEAD OIL\n--\nPVDO\n-- PSAT BO VISC\n-- PSIA RB/STB CPOISE\n-- -------- ------- ------\n400 1.0102 1.16\n1200 1.0040 1.164\n2000 0.9960 1.167\n2800 0.9880 1.172\n3600 0.9802 1.177\n4400 0.9724 1.181\n5200 0.9646 1.185\n5600 0.9607 1.19 / TABLE NO. 01\n-- -------- ------- ------\n800 1.0255 1.14\n1600 1.0172 1.14\n2400 1.0091 1.14\n3200 1.0011 1.14\n4000 0.9931 1.14\n4800 0.9852 1.14\n5600 0.9774 1.14 / TABLE NO. 02\nThe second example defines four dead oil PVT tables with variable viscosity and compressibility with respect to pressure, and assumes that NTPVT equals four and NPPVT is greater than or equal to eight on the TABDIMS keyword in the RUNSPEC section. Here table two defaults to table one, and table four defaults to table three.\n--\n-- OIL PVT TABLE FOR DEAD OIL\n--\nPVDO\n-- PSAT BO VISC\n-- PSIA RB/STB CPOISE\n-- -------- ------- ------\n400 1.0102 1.16\n1200 1.0040 1.164\n2000 0.9960 1.167\n2800 0.9880 1.172\n3600 0.9802 1.177\n4400 0.9724 1.181\n5200 0.9646 1.185\n5600 0.9607 1.19 / TABLE NO. 01\n/ TABLE NO. 02\n800 1.0255 1.14\n1600 1.0172 1.14\n2400 1.0091 1.14\n3200 1.0011 1.14\n4000 0.9931 1.14\n4800 0.9852 1.14\n5600 0.9774 1.14 / TABLE NO. 03\n/ TABLE NO. 04\nThere is no terminating “/” for this keyword.","size_kind":"fixed","variadic_record":true},"PVDS":{"name":"PVDS","sections":["PROPS"],"supported":null,"summary":"PVDS defines the solvent PVT properties for use with SOLVENT option. The solvent is treated as an additional dry gas phase within the model. This keyword should only be used if the SOLVENT model has been invoked in the RUNSPEC section.","parameters":[{"index":1,"name":"PRESS","description":"A columnar vector of real monotonically increasing down the column values that defines the solvent phase pressure.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":["Pressure","OilDissolutionFactor","Viscosity"]},{"index":2,"name":"GFVF","description":"A columnar vector of real decreasing down the column values that defines the corresponding solvent phase formation volume factor.","units":{"field":"rb/Mscf","metric":"rm3/sm3","laboratory":"rcc/scc"},"default":"None"},{"index":3,"name":"GVISC","description":"A columnar vector of real increasing down the column values that defines the corresponding solvent phase viscosity.","units":{"field":"cP","metric":"cP","laboratory":"cP"},"default":"None"}],"example":"--\n-- GAS SOLVENT PVT TABLE\n--\nPVDS\n-- PRES BG VISC\n-- PSIA RB/MSCF CPOISE\n-- ------ -------- ------\n700.0 4.4703 0.0135\n920.0 3.2968 0.0138\n1150.0 2.6113 0.0141\n1380.0 2.1560 0.0145\n1610.0 1.8316 0.0150\n1840.0 1.5952 0.0155\n2070.0 1.4129 0.0161\n2300.0 1.2700 0.0167\n2372.0 1.2305 0.0169\n2530.0 1.1551 0.0174\n2760.0 1.0621 0.0181\n2990.0 0.9841 0.0189\n3220.0 0.9190 0.0196\n3450.0 0.8638 0.0204\n4500.0 0.6910 0.0242\n6000.0 0.5616 0.0293 / TABLE N0. 01\n--\n-- PRES BG VISC\n-- PSIA RB/MSCF CPOISE\n-- ------ -------- ------\n700.0 4.6493 0.0138\n920.0 3.4417 0.0140\n1150.0 2.7227 0.0144\n1380.0 2.2522 0.0147\n1610.0 1.9158 0.0151\n1840.0 1.6702 0.0156\n2070.0 1.4805 0.0162\n2300.0 1.3317 0.0167\n2372.0 1.2927 0.0169\n2530.0 1.2119 0.0173\n2760.0 1.1135 0.0180\n2990.0 1.0325 0.0187\n3220.0 0.9637 0.0194\n3450.0 0.9055 0.0201\n4500.0 0.7228 0.0236\n6000.0 0.5837 0.0285 / TABLE N0. 02\nThe above example defines two solvent PVT tables assuming NTPVT equals two and NPPVT is greater than or equal to 16 on the TABDIMS keyword in the RUNSPEC section.\nThere is no terminating “/” for this keyword.","size_kind":"fixed","variadic_record":true},"PVTG":{"name":"PVTG","sections":["PROPS"],"supported":null,"summary":"PVTG defines the gas PVT properties for wet gas219\n Natural gas that contains significant heavy hydrocarbons such as propane, butane and other liquid hydrocarbons is known as wet gas or rich gas. The general rule of thumb is if the gas contains less methane (typically less than 85% methane) and more ethane, and other more complex hydrocarbons, it is labeled as wet gas. Wet gas normally has GOR's less than 100,000 scf/stb or 18,000 Sm3/m3, with the condensate having a gravity greater than 50 oAPI.. This keyword should be used when the VAPOIL keyword has be declared in the RUNSPEC section indicating that that vaporized oil (more commonly referred to as condensate) is present in the wet gas phase. The keyword may be used for gas-water and oil-water-gas input decks that contain the oil and gas phases.","parameters":[{"index":1,"name":"PRESS","description":"A real monotonically increasing down the column vector that defines the gas phase pressure, associated with the saturated condensate-gas ratio (“CGR”) or Rv, the gas formation volume factor and the gas viscosity for the corresponding pressure for the stated saturated RVS. For a given PRESS the variability of the gas formation volume factor and the gas viscosity with respect to the under-saturated Rv is optionally included as a sub table under RVU, FVFU and VISU columns, that is it is not necessary to repeat PRESS for each sub table entry. However, each sub table must be terminated by a “/”. The under saturated Rv entries are optional, except for perhaps the last PRESS entry to define the PVT properties above the initial saturation pressure.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":"Pressure"},{"index":2,"name":"RVS / RVU","description":"A columnar vector of real positive number for both the saturated (RVS) and under saturated (RVU) Rv sub table entries. The RVS entry on the main table is the saturated CGR at the pressure indicated by PRESS and may be increasing or decreasing in value as PRESS varies. Subsequent under-saturated Rv for a sub table at the given PRESS, as defined by RVU, are monotonically decreasing for entries in a given sub table.","units":{"field":"stb/Mscf","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"None","value_type":"DOUBLE","dimension":["OilDissolutionFactor","OilDissolutionFactor","Viscosity"]},{"index":3,"name":"FVFS / FVFU","description":"A columnar vector of real decreasing down the column values that defines the corresponding gas phase formation volume factor for a given pressure (PRESS) and for a given Rv (either RVS or RVU).","units":{"field":"rb/Mscf","metric":"rm3/sm3","laboratory":"rcc/scc"},"default":"None"},{"index":4,"name":"VISS / VISU","description":"VISS a columnar vector of real increasing down the column values that defines the corresponding gas phase viscosity for a given pressure (PRESS) and for a given RVS. VISU a columnar vector of real decreasing from VISS down the column values that defines the corresponding gas phase viscosity for a given pressure (PRESS) and for a given RVU.","units":{"field":"cP","metric":"cP","laboratory":"cP"},"default":"None"}],"example":"The first example defines two wet gas PVT tables assuming NTPVT equals two, NPPVT is greater than or equal to eight, and NRPVT greater than or equal to two on the TABDIMS keyword in the RUNSPEC section.\n--\n-- GAS PVT TABLE FOR WET GAS WITH VAPORIZED OIL\n--\nPVTG\n-- PRES RV BG VISC\n-- BARSASM^3/SM^3 RM^3/SM^3 CPOISE\n-- ------ --------- ------- ------\n20 0.000132 0.042340 0.01344\n0 0.042310 0.01389 /\n40 0.000124 0.020460 0.01420\n0 0.020430 0.01450 /\n60 0.000126 0.013280 0.01526\n0 0.013250 0.01532 /\n80 0.000135 0.009770 0.01660\n0 0.009730 0.01634 /\n100 0.000149 0.007730 0.01818\n0 0.007690 0.01752 /\n120 0.000163 0.006426 0.01994\n0 0.006405 0.01883 /\n140 0.000191 0.005541 0.02181\n0 0.005553 0.02021 /\n160 0.000225 0.004919 0.02370\n0 0.004952 0.02163 /\n/ TABLE NO. 1\n-- PRES RV BG VISC\n-- BARSASM^3/SM^3 RM^3/SM^3 CPOISE\n-- ------ --------- ------- ------\n20 0.000132 0.042340 0.01344 /\n40 0.000124 0.020460 0.01420 /\n60 0.000126 0.013280 0.01526 /\n80 0.000135 0.009770 0.01660 /\n100 0.000149 0.007730 0.01818 /\n120 0.000163 0.006426 0.01994 /\n140 0.000191 0.005541 0.02181 /\n160 0.000225 0.004919 0.02370\n0 0.004952 0.02163 /\n/ TABLE NO. 2\nThe second example defines four wet gas PVT tables assuming NTPVT equals four, NPPVT is greater than or equal to eight, and NRPVT greater than or equal to two on the TABDIMS keyword in the RUNSPEC section. Here table two defaults to table one, and table four defaults to table three.\n--\n-- GAS PVT TABLE FOR WET GAS WITH VAPORIZED OIL\n--\nPVTG\n-- PRES RV BG VISC\n-- BARSASM^3/SM^3 RM^3/SM^3 CPOISE\n-- ------ --------- ------- ------\n20 0.000132 0.042340 0.01344\n0 0.042310 0.01389 /\n40 0.000124 0.020460 0.01420\n0 0.020430 0.01450 /\n60 0.000126 0.013280 0.01526\n0 0.013250 0.01532 /\n80 0.000135 0.009770 0.01660\n0 0.009730 0.01634 /\n100 0.000149 0.007730 0.01818\n0 0.007690 0.01752 /\n120 0.000163 0.006426 0.01994\n0 0.006405 0.01883 /\n140 0.000191 0.005541 0.02181\n0 0.005553 0.02021 /\n160 0.000225 0.004919 0.02370\n0 0.004952 0.02163 /\n/ TABLE NO. 1\n/ TABLE NO. 2\n-- PRES RV BG VISC\n-- BARSASM^3/SM^3 RM^3/SM^3 CPOISE\n-- ------ --------- ------- ------\n20 0.000132 0.042340 0.01344 /\n40 0.000124 0.020460 0.01420 /\n60 0.000126 0.013280 0.01526 /\n80 0.000135 0.009770 0.01660 /\n100 0.000149 0.007730 0.01818 /\n120 0.000163 0.006426 0.01994 /\n140 0.000191 0.005541 0.02181 /\n160 0.000225 0.004919 0.02370\n0 0.004952 0.02163 /\n/ TABLE NO. 3\n/ TABLE NO. 4\nNotice that in both examples there is no terminating “/” for this keyword only for a table and a sub table.\n| Note If the VAPWAT keyword in the RUNSPEC section is also present in the input deck, then the PVTG keyword in the PROPS section should be used to define the gas properties as function of pressure and RV, assuming water-saturated gas. Also, in this case, the PVTGW keyword, also in the PROPS section, should also be in the input deck. In this case, PVTGW defines the gas properties as function of pressure and RVW, assuming oil-saturated gas. |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"list","variadic_record":true},"PVTGW":{"name":"PVTGW","sections":["PROPS"],"supported":null,"summary":"PVTGW defines the gas PVT properties for dry gas1\n Natural gas that occurs in the absence of condensate or liquid hydrocarbons, or gas that had condensable hydrocarbons removed, is called dry gas. It is primarily methane with some intermediates. The hydrocarbon mixture is solely gas in the reservoir and there is no liquid (condensate surface liquid) formed either in the reservoir or at surface. The term dry indicates that the gas does not contain heavier hydrocarbons to form liquids at the surface conditions. Dry gas typically has GOR's greater than 100,000 scf/stb or 18,000 Sm3/m3. with vaporized water. This keyword should be used when the VAPWAT keyword has be declared in the RUNSPEC section indicating that that vaporized water is present in the dry gas phase. The keyword may be used for gas-water and oil-water-gas input decks that contain the dry gas and vaporized water phases.","parameters":[{"index":1,"name":"PRESS","description":"A real monotonically increasing down the column vector that defines the gas phase pressure, associated with the corresponding saturated water-gas ratio (“WGR”) or Rw, the gas formation volume factor, and the gas viscosity for the stated saturated RWS. For a given PRESS the variability of the gas formation volume factor and the gas viscosity with respect to the under-saturated Rw is optionally included as a sub table under RWU, FVFU and VISU columns, that is it is not necessary to repeat PRESS for each sub table entry. However, each sub table must be terminated by a “/”. The under saturated Rw entries are optional, except for perhaps the last PRESS entry to define the PVT properties above the initial saturation pressure.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":"Pressure"},{"index":2,"name":"RWS / RWU","description":"A columnar vector of real positive numbers for both the saturated (RWS) and under saturated (RWU) Rw sub table entries. The RWS entry on the main table is the saturated WGR at the pressure indicated by PRESS and may be increasing or decreasing in value as PRESS varies. Subsequent under-saturated Rw for a sub table at the given PRESS, as defined by RWU, are monotonically decreasing for entries in a given sub table.","units":{"field":"stb/Mscf","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"None","value_type":"DOUBLE","dimension":["OilDissolutionFactor","OilDissolutionFactor","Viscosity"]},{"index":3,"name":"FVFS / FVFU","description":"A columnar vector of real decreasing down the column values that defines the corresponding gas phase formation volume factor for a given pressure (PRESS) and for a given Rw (either RWS or RWU).","units":{"field":"rb/Mscf","metric":"rm3/sm3","laboratory":"rcc/scc"},"default":"None"},{"index":4,"name":"VISS / VISU","description":"VISS a columnar vector of real increasing down the column values that defines the corresponding gas phase viscosity for a given pressure (PRESS) and for a given RWS. VISU a columnar vector of real decreasing from VISS down the column values that defines the corresponding gas phase viscosity for a given pressure (PRESS) and for a given RWU.","units":{"field":"cP","metric":"cP","laboratory":"cP"},"default":"None"}],"example":"--\n-- GAS PVT TABLE FOR DRY GAS WITH VAPORIZED WATER (OPM FLOW KEYWORD)\n--\nPVTGW\n-- PRES RW BG VISC\n-- PSIA SM^3/SM^3 RM^3/SM^3 CPOISE\n-- ------ --------- ------- ------\n300 0.000479 0.042340 0.01344\n0 0.042310 0.01389 /\n600 0.000469 0.020460 0.01420\n0 0.020430 0.01450 /\n900 0.000403 0.013280 0.01526\n0 0.013250 0.01532 /\n1200 0.000354 0.009770 0.01660\n0 0.009730 0.01634 /\n1500 0.000272 0.007730 0.01818\n0 0.007690 0.01752 /\n1800 0.000225 0.006426 0.01994\n0 0.006405 0.01883 /\n2100 0.000191 0.005541 0.02181\n0 0.005553 0.02021 /\n2400 0.000163 0.004919 0.02370\n0 0.004952 0.02163 /\n/ TABLE NO. 1\n-- PRES RW BG VISC\n-- PSIA SM^3/SM^3 RM^3/SM^3 CPOISE\n-- ------ --------- ------- ------\n300 0.000479 0.042340 0.01344 /\n600 0.000469 0.020460 0.01420 /\n900 0.000403 0.013280 0.01526 /\n1200 0.000354 0.009770 0.01660 /\n1500 0.000272 0.007730 0.01818 /\n1800 0.000225 0.006426 0.01994 /\n2100 0.000191 0.005541 0.02181 /\n2400 0.000163 0.004919 0.02370 /\n/ TABLE NO. 2\nThe above example defines two dry gas PVT tables assuming NTPVT equals two and NPPVT is greater than or equal to eight on the TABDIMS keyword in the RUNSPEC section.\nNotice that there is no terminating “/” for this keyword only for a table and a sub table.\n| Note This is an OPM Flow specific keyword for the simulator’s Water Vaporization Model that is activated by declaring that vaporized water is present in the run. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Note If both the VAPWAT and VAPOIL keywords have been declared in the RUNSPEC section indicating that both vaporized water and vaporized oil are present in the wet gas, then the PVTGW keyword should be used along with the PVTG keyword in the PROPS section to fully define the wet gas PVT properties. The PVTGW keyword should be used to define the gas properties as a function of pressure and water-gas ratio (RVW), assuming oil-saturated gas. The PVTG keyword should be used to define the gas properties as a function of pressure and oil-gas ratio (RV), assuming water-saturated gas. Alternatively, the PVTGWO keyword in the PROPS section may be used instead of the PVTGW and PVTG keywords to fully define the wet gas PVT properties. |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"list","variadic_record":true},"PVTGWO":{"name":"PVTGWO","sections":["PROPS"],"supported":false,"summary":"PVTGWO defines the gas PVT properties for wet gas1\n Natural gas that contains significant heavy hydrocarbons such as propane, butane and other liquid hydrocarbons is known as wet gas or rich gas. The general rule of thumb is if the gas contains less methane (typically less than 85% methane) and more ethane, and other more complex hydrocarbons, it is labeled as wet gas. Wet gas normally has GOR's less than 100,000 scf/stb or 18,000 Sm3/m3, with the condensate having a gravity greater than 50 oAPI. with vaporized water and oil. This keyword should be used when the VAPOIL and VAPWAT keywords have been declared in the RUNSPEC section indicating that vaporized oil and water are present in the wet gas phase. The keyword may be used for oil-water-gas input decks that contain the wet gas with vaporized oil and water phases.","parameters":[{"index":1,"name":"PRESS","description":"A real monotonically increasing down the column vector that defines the gas phase pressure, associated with the saturated water-gas ratio (“WGR”) or Rw, the saturated condensate-gas ratio (“CGR”) or Rv, the gas formation volume factor, and the gas viscosity for the corresponding pressure for the stated saturated RWS. For a given PRESS the variability of the gas formation volume factor and the gas viscosity with respect to the under-saturated Rw and Rv is optionally included as a sub table under RWU, RVU, FVFU and VISU columns, that is it is not necessary to repeat PRESS for each sub table entry. However, each sub table must be terminated by a “/”. The under saturated Rw and Rv entries are optional, except for perhaps the last PRESS entry to define the PVT properties above the initial saturation pressure.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":"Pressure"},{"index":2,"name":"RWS / RWU","description":"A columnar vector of real positive numbers for both the saturated (RWS) and under saturated (RWU) Rw sub table entries. The RWS entry on the main table is the saturated WGR at the pressure indicated by PRESS and may be increasing or decreasing in value as PRESS varies. Subsequent under-saturated Rw for a sub table at the given PRESS, as defined by RWU, are monotonically decreasing for entries in a given sub table.","units":{"field":"stb/Mscf","metric":"sm3/sm3","laboratory":"rcc/scc"},"default":"None","value_type":"DOUBLE","dimension":["OilDissolutionFactor","OilDissolutionFactor","OilDissolutionFactor","Viscosity"]},{"index":3,"name":"RVS / RVU","description":"A columnar vector of real positive numbers for both the saturated (RVS) and under saturated (RVU) Rv sub table entries. The RVS entry on the main table is the saturated CGR at the pressure indicated by PRESS and may be increasing or decreasing in value as PRESS varies. Subsequent under-saturated Rv for a sub table at the given PRESS, as defined by RVU, are monotonically decreasing for entries in a given sub table.","units":{"field":"stb/Mscf","metric":"sm3/sm3","laboratory":"rcc/scc"},"default":"None"},{"index":4,"name":"FVFS / FVFU","description":"A columnar vector of real decreasing down the column values that defines the corresponding gas phase formation volume factor for a given pressure (PRESS) and for a given Rw (either RWS or RWU) and Rv (either RVS or RVU).","units":{"field":"rb/Mscf","metric":"rm3/sm3","laboratory":"rcc/scc"},"default":"None"},{"index":5,"name":"VISS / VISU","description":"VISS a columnar vector of real increasing down the column values that defines the corresponding gas phase viscosity for a given pressure (PRESS) and for a given RWS and RVS. VISU a columnar vector of real decreasing from VISS down the column values that defines the corresponding gas phase viscosity for a given pressure (PRESS) and for a given RWU and RVU.","units":{"field":"cP","metric":"cP","laboratory":"cP"},"default":"None"}],"example":"--\n-- GAS PVT TABLE FOR WET GAS WITH VAPORIZED WATER & OIL (OPM FLOW KEYWORD)\n--\nPVTGWO\n-- PRES RW RV BG VISC\n-- PSIA STB/MSCF STB/MSCF RB/MSCF CPOISE\n-- ------ -------- --------- ------- ------\n300 0.000479 0.000132 0.042340 0.01344\n0 0 0.042310 0.01389 /\n600 0.000469 0.000124 0.020460 0.01420\n0 0 0.020430 0.01450 /\n900 0.000403 0.000126 0.013280 0.01526\n0 0 0.013250 0.01532 /\n1200 0.000354 0.000135 0.009770 0.01660\n0 0 0.009730 0.01634 /\n1500 0.000272 0.000149 0.007730 0.01818\n0 0 0.007690 0.01752 /\n1800 0.000225 0.000163 0.006426 0.01994\n0 0 0.006405 0.01883 /\n2100 0.000191 0.000191 0.005541 0.02181\n0 0 0.005553 0.02021 /\n2400 0.000163 0.000225 0.004919 0.02370\n0 0 0.004952 0.02163 /\n/ TABLE NO. 1\n-- PRES RW RV BG VISC\n-- PSIA STB/MSCF STB/MSCF RB/MSCF CPOISE\n-- ------ -------- --------- ------- ------\n300 0.000479 0.000132 0.042340 0.01344 /\n600 0.000469 0.000124 0.020460 0.01420 /\n900 0.000403 0.000126 0.013280 0.01526 /\n1200 0.000354 0.000135 0.009770 0.01660 /\n1500 0.000272 0.000149 0.007730 0.01818 /\n1800 0.000225 0.000163 0.006426 0.01994 /\n2100 0.000191 0.000191 0.005541 0.02181 /\n2400 0.000163 0.000225 0.004919 0.02370 /\n/ TABLE NO. 2\nThe above example defines two wet PVT tables assuming NTPVT equals two and NPPVT is greater than or equal to eight on the TABDIMS keyword in the RUNSPEC section.\nNotice that there is no terminating “/” for this keyword only for a table and a sub table.\n| Note This is an OPM Flow specific keyword for the simulator’s Water Vaporization Model that is activated by declaring that vaporized water is present in the run. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"list","variadic_record":true},"PVTO":{"name":"PVTO","sections":["PROPS"],"supported":null,"summary":"PVTO defines the oil PVT properties for live oil222\n “Live” oil is oil that contains gas in solution, which is normally the case for most conventional oil reservoirs. However, for oil reservoirs classified as heavy oil reservoirs, the in situ dissolved gas may be negligible and oil would then be classified as gas-free oil which is commonly referred to as “dead” oil. and the keyword should only be used if the there is both oil and gas phases in the model. This keyword should be used when the DISGAS keyword has be declared in the RUNSPEC section indicating that dissolved gas (more commonly referred to as solution gas) is present in the oil. The keyword may be used for oil-water and oil-water-gas input decks.","parameters":[{"index":1,"name":"RS","description":"A real monotonically increasing down the column values that defines the saturated gas-oil ratio (“GOR”) or Rs, that defines the oil formation volume factor and the oil viscosity for the tabulated corresponding pressure for stated saturated RS. For a given RS the variability of the oil formation volume factor and the oil viscosity with respect to the saturated RS and pressure is optionally included as a sub table under PRSU, FVFU and VISU columns, that is it is not necessary to repeat RS for each sub table entry. However, each sub table must be terminated by a “/”. The under-saturated PRSU entries are optional, except for perhaps the last RS entry to define the PVT properties above the initial saturation pressure. If there are no following under-saturated PRSU entries then the RS entry row should be terminated by a “/”, if there are under-saturated PRSU entries then the last PRSU entry row should be terminated by a “/”.","units":{"field":"Mscf/stb","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"None","value_type":"DOUBLE","dimension":"GasDissolutionFactor"},{"index":2,"name":"PRSS / PRSU","description":"PRSS is a real columnar vector of real monotonically increasing down the column values that defines the oil phase saturation pressure (bubble-point pressure), that defines the oil formation volume factor and the oil viscosity for the corresponding PRSS pressure for a given saturated RS. PRSU is a real columnar vector of real monotonically increasing down the column values that defines the oil phase under-saturated pressure that defines the oil formation volume factor and the oil viscosity for the corresponding PRSU pressure for a given saturated RS. Note that PRSU should be greater than PRSS.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":["Pressure","1","Viscosity"]},{"index":3,"name":"FVFS / FVFU","description":"FVFS is a columnar vector of real increasing down the column values that defines the corresponding oil phase saturated formation volume factor for a given pressure (PRSS) and for a given RS. FVFU is a columnar vector of real decreasing down the column values that defines the corresponding oil phase under-saturated formation volume factor for a given pressure (PRSU) and for a given RS.","units":{"field":"rb/stb","metric":"rm3/sm3","laboratory":"rcc/scc"},"default":"None"},{"index":4,"name":"VISS / VISU","description":"VISS a columnar vector of real increasing down the column values that defines the corresponding oil phase saturated viscosity for a given pressure (PRSS) and for a given RS. If this is the only entry for a given RS and PRSS then the record should be terminate by a “/”. VISU a columnar vector of real decreasing from VISS down the column values that defines the corresponding oil phase under-saturated viscosity for a given pressure (PRSU) and for a given RS. If this is the only entry for a given RS and PRSU then the record should be terminate by a “/”.","units":{"field":"cP","metric":"cP","laboratory":"cP"},"default":"None"}],"example":"The first example defines live oil PVT tables assuming NTPVT equals two, NPPVT is greater than or equal to two, and NRPVT is greater than or equal to 18 on the TABDIMS keyword in the RUNSPEC section.\n--\n-- OIL PVT TABLE FOR LIVE OIL\n--\nPVTO\n-- RS PSAT BO VISC\n-- MSCF/STB PSIA RB/STB CPOISE\n-- -------- -------- ------- ------\n0.0010 14.7 1.05340 1.7230 /\n0.0890 500.0 1.08890 1.1670 /\n0.2060 1000.0 1.13850 0.8570 /\n0.3360 1500.0 1.19640 0.6840 /\n0.4750 2000.0 1.26110 0.5750 /\n0.5480 2250.0 1.29570 0.5340 /\n0.6220 2500.0 1.33160 0.5000 /\n0.6980 2750.0 1.36890 0.4700 /\n0.7750 3000.0 1.40740 0.4450 /\n0.8530 3250.0 1.44710 0.4220 /\n0.9330 3500.0 1.48790 0.4020 /\n1.0140 3750.0 1.52980 0.3840 /\n1.0960 4000.0 1.57280 0.3680 /\n1.1800 4258.0 1.61760 0.3530 /\n1.2630 4500.0 1.66190 0.3400 /\n1.3480 4750.0 1.70780 0.3280 /\n1.4340 5000.0 1.75480 0.3170 /\n1.6060 5500.0 1.85020 0.2980\n6242.0 1.83040 0.3186 /\n/ TABLE NO. 1\n--\n--\n-- RS PSAT BO VISC\n-- MSCF/STB PSIA RB/STB CPOISE\n-- -------- -------- ------- ------\n0.0010 14.7 1.05340 1.7230 /\n0.0390 250.0 1.06830 1.4220 /\n0.0890 500.0 1.08890 1.1670 /\n0.1460 750.0 1.11250 0.9850 /\n0.2060 1000.0 1.13850 0.8570 /\n0.2700 1250.0 1.16660 0.7590 /\n0.3360 1500.0 1.19640 0.6840 /\n0.4050 1750.0 1.22800 0.6240 /\n0.4750 2000.0 1.26110 0.5750 /\n0.5480 2250.0 1.29570 0.5340 /\n0.6220 2500.0 1.33160 0.5000 /\n0.6980 2750.0 1.36890 0.4700 /\n0.7750 3000.0 1.40740 0.4450 /\n0.8530 3250.0 1.44710 0.4220 /\n0.9330 3500.0 1.48790 0.4020 /\n1.0140 3750.0 1.52980 0.3840 /\n1.0960 4000.0 1.57280 0.3680 /\n1.1800 4258.0 1.61760 0.3530 /\n1.2630 4500.0 1.66190 0.3400 /\n1.3480 4750.0 1.70780 0.3280 /\n1.4340 5000.0 1.75480 0.3170 /\n1.6060 5500.0 1.85020 0.2980\n6242.0 1.83040 0.3186 /\n/ TABLE NO. 2\nNotice that there must be at least two entries for the last Rs value to enable the simulator to interpolate over the undersaturated pressure region.\nThe second example defines live oil PVT tables assuming NTPVT equals four, NPPVT is greater than or equal to two, and NRPVT is greater than or equal to 13 on the TABDIMS keyword in the RUNSPEC section. Here, tables two to four all default to table number one.\n--\n-- OIL PVT TABLE FOR LIVE OIL\n--\nPVTO\n-- RS PSAT BO VISC\n-- MSCF/STB PSIA RB/STB CPOISE\n-- -------- -------- ------- ------\n0.0010 14.7 1.05340 1.7230 /\n0.0890 500.0 1.08890 1.1670 /\n0.2060 1000.0 1.13850 0.8570 /\n0.3360 1500.0 1.19640 0.6840 /\n0.4750 2000.0 1.26110 0.5750 /\n0.5480 2250.0 1.29570 0.5340 /\n0.6220 2500.0 1.33160 0.5000 /\n0.7750 3000.0 1.40740 0.4450 /\n0.9330 3500.0 1.48790 0.4020 /\n1.0960 4000.0 1.57280 0.3680 /\n1.2630 4500.0 1.66190 0.3400 /\n1.4340 5000.0 1.75480 0.3170 /\n1.6060 5500.0 1.85020 0.2980\n6242.0 1.83040 0.3186 /\n/ TABLE NO. 1\n/ TABLE NO. 2\n/ TABLE NO. 3\n/ TABLE NO. 4\nAgain, note that there is no terminating “/” for this keyword only for a table and a sub table.","size_kind":"list","variadic_record":true},"PVTSOL":{"name":"PVTSOL","sections":["PROPS"],"supported":null,"summary":"PVTSOL defines the live oil PVT properties as a function of CO2 mass fraction. The keyword automatically invokes the simulator’s CO2 Dynamic EOR Model223\n T. H. Sandve, O. Sævareid and I. Aavatsmark: “Improved Extended Blackoil Formulation -- for CO2 EOR Simulations.” in ECMOR XVII – The 17th European Conference on the -- Mathematics of Oil Recovery, September 2020. , that uses a fourth component to model the injected CO2., for use in evaluating CO2 Enhanced Oil Recovery (“EOR”) projects. Normally CO2 EOR projects are evaluated via compositional simulators to account for the mass transfer of the various components and phases. Unfortunately, compositional models are computationally expensive compared to the black-oil approach, which for field studies is challenging, especially if an ensemble approach is being used to capture the uncertainties. Previous extended black-oil formulations often poorly represent the PVT properties of the oil-CO2 mixtures, resulting in poor agreement wi...","parameters":[{"index":1,"name":"CO2","description":"A real monotonically increasing down the column values that stipulates the CO2 mass fraction, that defines the oil and gas properties, formation volume factor, viscosity etc., for the tabulated corresponding pressure for the stated CO2 mass fraction. CO2 should be greater than or equal to zero and less than or equal to one. Note it is not necessary to repeat the value of CO2 for the pressure column. However, for a given CO2 mass fraction, the last pressure entry (PRESS) of the sub table should be terminated by a “/”.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":"1"},{"index":2,"name":"PRESS","description":"PRESS is a real columnar vector of real monotonically increasing down the column values that defines the oil phase saturation pressure (bubble-point pressure), that defines the oil formation volume factor and the oil viscosity for the corresponding PRESS pressure for a given saturated value of CO2.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":["Pressure","1","OilDissolutionFactor","GasDissolutionFactor","OilDissolutionFactor","1","1","Viscosity","Viscosity"]},{"index":3,"name":"OFVF","description":"OFVF is a columnar vector of real increasing down the column values that defines the corresponding oil phase saturated formation volume factor for a given pressure (PRESS) and for a given saturated value of CO2.","units":{"field":"rb/stb","metric":"rm3/sm3","laboratory":"rcc/scc"},"default":"None"},{"index":4,"name":"GFVF","description":"GFVF is a columnar vector of real decreasing down the column values that defines the corresponding gas phase saturated formation volume factor for a given pressure (PRESS) and for a given saturated value of CO2.","units":{"field":"rb/Mscf","metric":"rm3/sm3","laboratory":"rcc/scc"},"default":"None"},{"index":5,"name":"RS","description":"RS is a real monotonically increasing down the column values that defines the saturated gas-oil ratio (“GOR”) or Rs, for the given value of PRESS and for a given saturated value of CO2.","units":{"field":"Mscf/stb","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"None"},{"index":6,"name":"RV","description":"RV is a real monotonically increasing down the column values that defines the saturated condensate-gas ratio (“CGR”) or Rv, for the given value of PRESS and for a given saturated value of CO2.","units":{"field":"stb/Mscf","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"None"},{"index":7,"name":"XVOL","description":"XVOL is a real positive value greater than or equal to zero and less than or equal to one, that stipulates the volumetric fraction of CO2 in the oil phase, that is: [XVOL~=~{Volume_oil (CO_2)} over { Volume_oil (CO_2) `+` Volume_oil (Gas) `+` Volume_oil (Oil)}] where: Volume oil (CO2) is the surface volume of CO2 in the oil phase, Volume oil (Gas) is the surface volume of gas in the oil phase, and Volume oil (Oil) is the surface volume of oil in the oil phase.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":8,"name":"YVOL","description":"YVOL is a real positive value greater than or equal to zero and less than or equal to one, that defines the volumetric fraction of CO2 in the gas phase, that is: [YVOL~=~{Volume_gas (CO_2)} over { Volume_gas (CO_2)`+` Volume_gas (Gas)`+` Volume_gas (Oil) }] where: Volume gas (CO2) is the surface volume of CO2 in the gas phase, Volume gas (Gas) is the surface volume of gas in the gas phase, and Volume gas (Oil) is the surface volume of oil in the gas phase.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":9,"name":"OVISC","description":"OVISC is a columnar vector of real decreasing down the column values that defines the corresponding oil phase saturated viscosity for a given pressure (PRESS) and for a given saturated value of CO2.","units":{"field":"cP","metric":"cP","laboratory":"cP"},"default":"None"},{"index":10,"name":"GVISC","description":"GVISC is a columnar vector of real increasing down the column values that defines the corresponding gas phase saturated viscosity for a given pressure (PRESS) and for a given saturated value of CO2.","units":{"field":"cP","metric":"cP","laboratory":"cP"},"default":"None"}],"example":"--\n-- OIL PVT PROPERTIES FOR LIVE OIL VERSUS CO2 MASS FRACTION\n--\nPVTSOL\n-- CO2 PSAT BO BG RS RV XVOL YVOL OIL VISC GAS VISC\n-- MFRAC PSIA RB/STB RB/MSCF MSCF/STB STB/MSCF CPOISE CPOISE\n-- ----- ------- ------ ---------- -------- ---------- ------ ------ ---------- ----------\n0.000 14.50 1.0000 1.7810e+02 0.0000 0.0000e+00 0.0000 0.0000 2.0340e-01 1.3016e-02\n725.18 1.0655 6.0855e+00 0.1302 1.4432e-04 0.0000 0.0000 2.0340e-01 1.3016e-02\n870.22 1.0806 5.0340e+00 0.1591 1.9594e-04 0.0000 0.0000 1.9973e-01 1.3222e-02\n1015.26 1.0961 4.2814e+00 0.1886 2.8389e-04 0.0000 0.0000 1.9609e-01 1.3452e-02\n1160.30 1.1121 3.7174e+00 0.2189 4.1914e-04 0.0000 0.0000 1.9246e-01 1.3708e-02\n1305.33 1.1285 3.2799e+00 0.2499 6.0779e-04 0.0000 0.0000 1.8886e-01 1.3994e-02\n1450.37 1.1454 2.9314e+00 0.2819 8.5105e-04 0.0000 0.0000 1.8527e-01 1.4309e-02\n1595.41 1.1629 2.6479e+00 0.3148 1.1490e-03 0.0000 0.0000 1.8171e-01 1.4657e-02\n1740.45 1.1809 2.4133e+00 0.3487 1.5030e-03 0.0000 0.0000 1.7819e-01 1.5037e-02\n1885.49 1.1996 2.2163e+00 0.3838 1.9155e-03 0.0000 0.0000 1.7469e-01 1.5450e-02\n2030.52 1.2189 2.0490e+00 0.4200 2.3899e-03 0.0000 0.0000 1.7122e-01 1.5897e-02\n2175.56 1.2389 1.9055e+00 0.4574 2.9302e-03 0.0000 0.0000 1.6779e-01 1.6377e-02\n2320.60 1.2597 1.7812e+00 0.4962 3.5412e-03 0.0000 0.0000 1.6440e-01 1.6890e-02\n2465.64 1.2812 1.6728e+00 0.5364 4.2273e-03 0.0000 0.0000 1.6104e-01 1.7435e-02\n2610.67 1.3037 1.5775e+00 0.5782 4.9942e-03 0.0000 0.0000 1.5772e-01 1.8011e-02\n2755.71 1.3270 1.4933e+00 0.6216 5.8471e-03 0.0000 0.0000 1.5443e-01 1.8617e-02\n2900.75 1.3514 1.4185e+00 0.6668 6.7918e-03 0.0000 0.0000 1.5117e-01 1.9253e-02\n3045.79 1.3768 1.3517e+00 0.7139 7.8347e-03 0.0000 0.0000 1.4795e-01 1.9917e-02\n3137.32 1.3937 1.3132e+00 0.7450 8.5549e-03 0.0000 0.0000 1.4592e-01 2.0353e-02\n4061.05 1.3705 1.3132e+00 0.7450 8.5549e-03 0.0000 0.0000 1.5939e-01 2.0353e-02 /\n0.010 14.50 1.0000 1.7810e+02 0.0000 0.0000e+00 0.0464 0.0381 2.0301e-01 1.3203e-02\n725.18 1.0670 6.0041e+00 0.1341 1.4845e-04 0.0464 0.0381 2.0301e-01 1.3203e-02\n…………….………….….…….…….…….…….……….………….…….…….…….………….…….……….……………….……….…...…….…….….…….…………...\n3135.04 1.4082 1.2950e+00 0.7755 8.9113e-03 0.0298 0.0277 1.4422e-01 2.0743e-02\n4061.05 1.3840 1.2950e+00 0.7755 8.9113e-03 0.0298 0.0277 1.5772e-01 2.0743e-02 /\n0.100 14.50 1.0000 1.7810e+02 0.0000 0.0000e+00 0.3426 0.3023 1.9984e-01 1.4740e-02\n725.18 1.0795 5.3329e+00 0.1666 1.8243e-04 0.3426 0.3023 1.9984e-01 1.4740e-02\n…………….………….….…….…….…….…….……….………….…….…….…….………….…….……….……………….……….…...…….…….….…….…………...\n3116.25 1.5281 1.1444e+00 1.0268 1.1849e-02 0.2492 0.2431 1.3023e-01 2.3961e-02\n4061.05 1.4955 1.1444e+00 1.0268 1.1849e-02 0.2492 0.2431 1.4400e-01 2.3961e-02 /\n0.200 14.50 1.0000 1.7810e+02 0.0000 0.0000e+00 0.5303 0.4898 1.9699e-01 1.5838e-02\n725.18 1.0909 4.8402e+00 0.1964 2.1919e-04 0.5303 0.4898 1.9699e-01 1.5838e-02\n…………….………….….…….…….…….…….……….………….…….…….…….………….…….……….……………….……….…...…….…….….…….…………...\n4061.05 1.6501 1.0017e+00 1.3720 1.6728e-02 0.4220 0.4240 1.2963e-01 2.7757e-02 /\n0.300 14.50 1.0000 1.7810e+02 0.0000 0.0000e+00 0.6486 0.6159 1.9471e-01 1.6588e-02\n725.18 1.1003 4.4992e+00 0.2210 2.5440e-04 0.6486 0.6159 1.9471e-01 1.6588e-02\n…………….………….….…….…….…….…….……….………….…….…….…….………….…….……….……………….……….…...…….…….….…….…………...\n4061.05 1.8529 8.8189e-01 1.8200 2.4541e-02 0.5491 0.5597 1.1636e-01 3.2195e-02 /\n0.400 14.50 1.0000 1.7810e+02 0.0000 0.0000e+00 0.7303 0.7059 1.9292e-01 1.7131e-02\n725.18 1.1079 4.2506e+00 0.2413 2.8832e-04 0.7303 0.7059 1.9292e-01 1.7131e-02\n…………….………….….…….…….…….…….……….………….…….…….…….………….…….……….……………….……….…...…….…….….…….…………...\n4061.05 2.1298 7.8515e-01 2.4251 3.7664e-02 0.6468 0.6616 1.0441e-01 3.7755e-02 /\n0.500 14.50 1.0000 1.7810e+02 0.0000 0.0000e+00 0.7905 0.7733 1.9156e-01 1.7543e-02\n725.18 1.1140 4.0628e+00 0.2581 3.2217e-04 0.7905 0.7733 1.9156e-01 1.7543e-02\n…………….………….….…….…….…….…….……….………….…….…….…….………….…….……….……………….……….…...…….…….….…….…………...\n4061.05 2.5282 7.1557e-01 3.2879 6.07","size_kind":"list","variadic_record":true},"PVTW":{"name":"PVTW","sections":["PROPS"],"supported":null,"summary":"PVTW defines the water properties for various regions in the model. The number of PVTW vector data sets is defined by the NTPVT parameter on the TABDIMS keyword in the RUNSPEC section and the allocation of the PVTW tables to different grid blocks in the model is done via the PVTNUM keyword in the REGIONS section. One data set consists of one record or line which is terminated by a “/”. If the water phase is active in the model, which is normally the case, then this keyword must be defined in the OPM Flow input deck.","parameters":[{"index":1,"name":"PRES","description":"PRES is a real number defining the water reference pressure (P) for the other parameters for this data set.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":"Pressure"},{"index":2,"name":"WFVF","description":"WFVF is a real number defining the water formation volume factor (Bw) at the water reference pressure.","units":{"field":"rb/stb 1.0","metric":"rm3/sm3 1.0","laboratory":"rcc/scc 1.0"},"default":"Defined","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"WCOMP","description":"WCOMP is a real number defining the water compressibility (Cw) at the water reference pressure and is defined as: [C sub{w}~=~ - 1 over {B sub{w}}left({dB sub{w}} over{dP} right)]","units":{"field":"1/psia 0.00004","metric":"1/barsa 0.00004","laboratory":"1/atma 0.00004"},"default":"Defined","value_type":"DOUBLE","dimension":"1/Pressure"},{"index":4,"name":"WVISC","description":"WVISC is a real number defining the water viscosity (µw) at the water reference pressure.","units":{"field":"cP 0.50","metric":"cP 0.50","laboratory":"cP 0.50"},"default":"Defined","value_type":"DOUBLE","dimension":"Viscosity"},{"index":5,"name":"WVISCOMP","description":"WVISCOMP is a real number defining the water viscosibility (µwc) at the water reference pressure, µwc(Pref) and is defined as: [%mu sub{wc}~=~ - 1 over { %mu sub{w}}left({d%mu sub{w}} over{dP} right)]","units":{"field":"1/psia 0.0","metric":"1/barsa 0.0","laboratory":"1/atma 0.0"},"default":"Defined","value_type":"DOUBLE","dimension":"1/Pressure"}],"example":"The following shows the PVTW keyword for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set to one.\n--\n-- WATER PVT TABLE\n--\nPVTW\n-- REF PRES BW CW VISC VISC\n-- PSIA RB/STB 1/PSIA CPOISE GRAD\n-- -------- -------- ------- ------ ------\n4840.0 1.019 2.7E-6 0.370 1* / TABLE NO. 01\nThe next example shows the PVTW keyword for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set to three.\n--\n-- WATER PVT TABLE\n--\nPVTW\n-- REF PRES BW CW VISC VISC\n-- PSIA RB/STB 1/PSIA CPOISE GRAD\n-- -------- -------- ------- ------ ------\n4640.0 1.008 2.5E-6 0.350 1* / TABLE NO. 01\n4840.0 1.019 2.7E-6 0.370 1* / TABLE NO. 02\n4940.0 1.030 2.8E-6 0.390 1* / TABLE NO. 03\nThe above example defines three water PVT tables and assumes that NTPVT equals three on the TABDIMS keyword in the RUNSPEC section.\nThe third, and final example, shows the PVTW keyword for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set to four. Here table two defaults to table one, and table four defaults to table three\n--\n-- WATER PVT TABLE\n--\nPVTW\n-- REF PRES BW CW VISC VISC\n-- PSIA RB/STB 1/PSIA CPOISE GRAD\n-- -------- -------- ------- ------ ------\n4640.0 1.008 2.5E-6 0.350 1* / TABLE NO. 01\n/ TABLE NO. 02\n4940.0 1.030 2.8E-6 0.390 1* / TABLE NO. 03\n/ TABLE NO. 04\nNote that there is no terminating “/” for this keyword.","expected_columns":5,"size_kind":"fixed"},"PVTWSALT":{"name":"PVTWSALT","sections":["PROPS"],"supported":null,"summary":"PVTWSALT defines the brine water properties for various regions in the model, for when the brine phase has been activated by the BRINE keyword in the RUNSPEC section. In this case PVTWSALT is used instead of PVTW in the input file. However, if the ECLMC keyword has been entered in the RUNSPEC section to invoke the Multi-Component Brine model, the PVTW keyword should be used instead of PVTWSALT, as with this combination the salinity effect on the density is ignored.","parameters":[{"index":1,"name":"PRESS","description":"Single real positive value that defines the reference pressure for the data in the following records (Pref). PRESS should be approximately equal to the average reservoir pressures in the model. The simulator uses the previous time step values to forecast the current time step water properties by linear interpolation. If PRESS is not representative of the average reservoir pressures in the model then the linear interpolation might result in nonphysical values of the water saturation and water viscosity.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","record":1},{"index":1,"name":"","description":"","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"","record":1},{"index":1,"name":"SALTCON","description":"A columnar vector of real monotonically increasing values that defines the salt concentration in the solution (Cs).","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None","record":2},{"index":1,"name":"","description":"","units":{"field":"rb/stb","metric":"rm3/sm3","laboratory":"rcc/scc"},"default":"","record":2},{"index":3,"name":"WCOMP","description":"WCOMP is a real columnar vector defining the water compressibility (Cw) at the water reference pressure PRESS, for the corresponding salt concentration SALTCON. The water compressibility is defined as: [C sub{w}~=~ - 1 over {B sub{w}}left({dB sub{w}} over{dP} right)]","units":{"field":"1/psia","metric":"1/bars","laboratory":"1/atma"},"default":"None","record":2}],"example":"The following shows the PVTWSALT keyword for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set equal to two and NPPVT is set to greater than four on the TABDIMS keyword.\n--\n-- WATER SALT PVT TABLE\n--\nPVTWSALT\n-- REF PRES REF SALT\n-- PSIA LB/STB\n-- -------- --------\n4500.0 0.000 / TABLE NO. REF. DATA\n--\n-- SALTCONBW CW VISC VISC\n-- LB/STB RB/STB 1/PSIA CPOISE GRAD\n-- -------- -------- ------- ------ ------\n0.0 1.020 2.7E-6 0.370 0.0\n2.0 1.010 2.7E-6 0.370 0.0\n4.0 1.000 2.7E-6 0.370 0.0\n10.0 0.950 2.7E-6 0.370 0.0 / TABLE NO. 01 SALT DATA\n--\n-- REF PRES REF SALT\n-- PSIA LB/STB\n-- -------- --------\n4000.0 0.000 / TABLE NO. 02 REF. DATA\n--\n-- SALTCON BW CW VISC VISC\n-- LB/STB RB/STB 1/PSIA CPOISE GRAD\n-- -------- -------- ------- ------ ------\n0.0 1.005 2.5E-6 0.320 0.0\n3.0 1.000 2.5E-6 0.320 0.0\n6.0 0.985 2.5E-6 0.320 0.0\n12.0 0.930 2.5E-6 0.320 0.0 / TABLE NO. 02 SALT DATA\nNote that each table is terminated by a “/” and there is no “/” terminator for the keyword.\n| 1-1 |\n|-----|\n| 2-1 |\n|-----|\n| [{ B _ w ( { P , C _ s } ) `` = `` { { B _ w ( { P _ ref , C _ {s, ref} } ) } over { 1 ` + ` C _ w ( P - P _ ref ) ` + ` { left ( { C _ w ( P - P _ ref ) } right ) ^ 2 over 2 } } } }] | (8.82) |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|\n| [{ B _ w ( { P , C _ s } ) `` %mu _ w ( { P , C _ s } ) `` = `` { { B _ w ( { P _ ref , C _ {s, ref} } ) `` %mu _ w ( { P_ref , C _ {s, ref} } ) } over { 1 ` + ` ( { C _w - `` %mu _ wc } ) ( P - P _ ref ) ` + ` { left ( { ( C _ w - ``%mu _ wc ) ( P - P _ ref ) } right ) ^ 2 over 2 } } } }] | (8.83) |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|","size_kind":"fixed"},"PVZG":{"name":"PVZG","sections":["PROPS"],"supported":false,"summary":"PVZG defines the gas PVT properties for dry gas224\n Natural gas that occurs in the absence of condensate or liquid hydrocarbons, or gas that had condensable hydrocarbons removed, is called dry gas. It is primarily methane with some intermediates. The hydrocarbon mixture is solely gas in the reservoir and there is no liquid (condensate surface liquid) formed either in the reservoir or at surface. The term dry indicates that the gas does not contain heavier hydrocarbons to form liquids at the surface conditions. Dry gas typically has GOR's greater than 100,000 scf/stb or 18,000 Sm3/m3. via the gas compressibility factor (z-factor), instead of the gas formation volume factor. If the gas has a constant and uniform vaporized oil concentration, Condensate-Gas Ratio (“CGR”), and if the reservoir pressure never drops below the saturation pressure (dew point pressure), then the model can be run more efficiently by omitting the OIL and VAPOIL keywords from the RUNSPEC section, treating t...","parameters":[{"index":1,"name":"RTEMP","description":"Single real positive value that defines the reservoir temperature for the data in the following records.","units":{"field":"oF","metric":"oC","laboratory":"oC"},"default":"","record":1},{"index":1,"name":"PRESS","description":"A columnar vector of real monotonically increasing down the column values that defines the gas phase pressure.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","record":2},{"index":1,"name":"","description":"","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"","record":2},{"index":3,"name":"GVISC","description":"A columnar vector of real increasing down the column values that defines the corresponding gas phase viscosity.","units":{"field":"cP","metric":"cP","laboratory":"cP"},"default":"None","record":2}],"example":"---\n-- GAS PVT TABLE USING GAS Z-FACTOR\n--\nPVZG\n-- RESERVOIR TEMPERATURE FOR Z TO BG CONVERSION\n--\n180.0 /\n--\n-- PRES ZG VISC\n-- PSIA DIMLESS CPOISE\n-- ------ --------- -------\n14.7 0.998970 0.0130\n250.0 0.976260 0.0131\n500.0 0.954790 0.0134\n750.0 0.932050 0.0137\n1000.0 0.912990 0.0142\n1250.0 0.896320 0.0147\n1500.0 0.881610 0.0152\n1750.0 0.870830 0.0159\n2000.0 0.863130 0.0166\n2250.0 0.858920 0.0173\n2500.0 0.857800 0.0181\n2750.0 0.860430 0.0189\n3000.0 0.866440 0.0197\n3250.0 0.874980 0.0206\n3500.0 0.885470 0.0214\n3750.0 0.898350 0.0223\n4000.0 1.025120 0.0277 / TABLE NO 01 --\n-- GAS PVT TABLE USING GAS Z-FACTOR\n--\nPVZG\n-- RESERVOIR TEMPERATURE FOR Z TO BG CONVERSION\n--\n180.0 /\n--\n-- PRES ZG VISC\n-- PSIA DIMLESS CPOISE\n-- ------ --------- -------\n14.7 0.998970 0.0130\n250.0 0.976260 0.0131\n500.0 0.954790 0.0134\n750.0 0.932050 0.0137\n1000.0 0.912990 0.0142\n1250.0 0.896320 0.0147\n1500.0 0.881610 0.0152\n1750.0 0.870830 0.0159\n2000.0 0.863130 0.0166\n2250.0 0.858920 0.0173\n2500.0 0.857800 0.0181\n2750.0 0.860430 0.0189\n3000.0 0.866440 0.0197\n3250.0 0.874980 0.0206\n3500.0 0.885470 0.0214\n3750.0 0.898350 0.0223\n4000.0 1.025120 0.0277 / TABLE NO 01\nThe above example defines two dry PVZG tables assuming NTPVT equals two and NPPVT is greater than or equal to 17 on the TABDIMS keyword in the RUNSPEC section. There is no terminating “/” for this keyword.\n| 2-1 |\n|-----|\n| [PV~=~ZnRT] | (8.84) |\n|-------------|--------|\n| [V SUB{sc}~=~{Z SUB{sc}nRT SUB{sc}} OVER{ P SUB{sc}}] | (8.85) |\n|-------------------------------------------------------|--------|\n| [V SUB{i}~=~{Z SUB{i}n RT SUB{i}} OVER {P SUB{i}}] | (8.86) |\n|----------------------------------------------------|--------|\n| [E~=~{{V SUB{sc}} OVER { V SUB{i}}}] | (8.87) |\n|---------------------------------------|--------|\n| [E~=~ LEFT (P SUB { i } OVER P SUB {sc } RIGHT)\n ` ` LEFT(T SUB {sc } OVER T SUB { i } RIGHT )\n ` ` LEFT (1 OVER Z SUB { i } RIGHT )] | (8.88) |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------|\n| [E~=~ LEFT (P SUB { i } OVER {101.325} RIGHT)\n ` ` LEFT({273.15 ~+~15 } OVER T SUB { i } RIGHT )\n ` ` LEFT (1 OVER Z SUB { i } RIGHT )~=~\n 2.84` ` LEFT (P SUB { i } OVER { Z SUB {i } T SUB { i } } RIGHT )] | (8.89) |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|\n| [E~=~ LEFT (P SUB { i } OVER {14.7} RIGHT)\n ` ` LEFT({460 ~+~60 } OVER T SUB { i } RIGHT )\n ` ` LEFT (1 OVER Z SUB { i } RIGHT )~=~\n 35.37` ` LEFT (P SUB { i } OVER { Z SUB {i } T SUB { i } } RIGHT )] | (8.90) |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|","size_kind":"fixed"},"QHRATING":{"name":"QHRATING","sections":["PROPS"],"supported":false,"summary":"The QHRATING keyword defines a river’s mass flow rate versus depth tables, for when the River option has been activated via the RIVRDIMS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Length*Length*Length/Time","Length"]}],"example":"","size_kind":"fixed","variadic_record":true},"RIVRXSEC":{"name":"RIVRXSEC","sections":["PROPS"],"supported":false,"summary":"The RIVRXSEC keyword defines a river’s cross-sectional area and perimeter versus depth parameters. The River option must be activated via the RIVRDIMS keyword in the RUNSPEC section in order to use this keyword.","parameters":[{"index":1,"name":"DEPTH","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":2,"name":"WET_PERIMTER","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":3,"name":"AREA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length*Length"}],"example":"","expected_columns":3,"size_kind":"fixed"},"RKTRMDIR":{"name":"RKTRMDIR","sections":["PROPS"],"supported":false,"summary":"This keyword activates the directional transmissibility multipliers for the ROCKTAB keyword. This results in two additional columns being inputted on the ROCKTAB keyword. This feature is currently not supported in OPM Flow.","parameters":[],"example":"","size_kind":"none","size_count":0},"ROCK":{"name":"ROCK","sections":["PROPS"],"supported":null,"summary":"ROCK defines the rock compressibility for various regions in the model. The number of ROCK vector data sets is defined by the NTPVT parameter on the TABDIMS keyword in the RUNSPEC section and the allocation of the ROCK tables to different grid blocks in the model is done via the PVTNUM keyword in the REGIONS section. One data set consists of one record or line which is terminated by a “/”.","parameters":[{"index":1,"name":"PRESS","description":"PRESS is a real number defining the rock reference pressure for the other parameters for this data set.","units":{"field":"psia 14.7","metric":"barsa 1.0132","laboratory":"atma 1.0"},"default":"Default"},{"index":2,"name":"RCOMP","description":"RCOMP is a real number defining the rock compressibility (cf) at the rock reference pressure and is defined as: [c sub{f}~=~ - 1 over {V}left({dV} over{dP} right)]","units":{"field":"1/psia 0.0","metric":"1/barsa 0.0","laboratory":"1/atma 0.0"},"default":"Defined"}],"example":"The following shows the ROCK keyword for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set to one.\n--\n-- ROCK COMPRESSIBILITY\n--\n-- REFERENCE PRESSURE IS TAKEN FROM THE HCPV WEIGHTED RESERVOIR PRESSURE\n-- AS THE PORV IS ALREADY AT RESERVOIR CONDITIONS (OPM FLOW USES THE\n-- REFERENCE PRESSURE) TO CONVERT THE GIVEN PORV TO RESERVOIR CONDITIONS\n-- USING THE DATA ON THE ROCK KEYWORD)\n--\n-- REF PRES CF\n-- PSIA 1/PSIA\n-- -------- --------\nROCK\n3966.9 5.0E-06 / ROCK COMPRESSIBILITY\nThe next example shows the ROCK keyword for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set to three.\n--\n-- ROCK COMPRESSIBILITY\n--\n-- REFERENCE PRESSURE IS TAKEN FROM THE HCPV WEIGHTED RESERVOIR PRESSURE\n-- AS THE PORV IS ALREADY AT RESERVOIR CONDITIONS (OPM FLOW USES THE\n-- REFERENCE PRESSURE) TO CONVERT THE GIVEN PORV TO RESERVOIR CONDITIONS\n-- USING THE DATA ON THE ROCK KEYWORD)\n--\n-- REF PRES CF\n-- PSIA 1/PSIA\n-- -------- --------\nROCK\n3566.9 5.0E-06 / ROCK COMPRESSIBILITY REGION 1\n3966.9 5.5E-06 / ROCK COMPRESSIBILITY REGION 2\n4566.9 6.0E-06 / ROCK COMPRESSIBILITY REGION 3\nThe above example defines three ROCK tables and assumes that NTPVT equals three on the TABDIMS keyword in the RUNSPEC section.\nThere is no terminating “/” for this keyword, and thus the number entries must match the value entered via the TABDIMS(NTPVT), TABDIMS(NTROCC), or TABDIMS(NTSFUN) parameters, depending on the option selected via the ROCKOPTS keyword.\n| [V(P_i)``=``V(P_r) left( 1``+``c_f left( P_i`-`P_r right) ``+`` \n{ left( c_f ( P_i`-`P_r ) right) ^2} over 2 right)] | (8.91) |\n|------------------------------------------------------------------------------------------------------------------------|--------|\n| Note If the Rock Compaction option has been activated via the ROCKCOMP keyword in the RUNSPEC section, then the ROCKTAB keyword in the PROPS section should be used instead of ROCK keyword. |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|"},"ROCK2D":{"name":"ROCK2D","sections":["PROPS"],"supported":null,"summary":"The ROCK2D keyword defines rock compressibility pore volume multipliers as a function of pressure and water saturation (“Sw”) for when the rock compaction option has been invoked by the ROCKCOMP keyword in the RUNSPEC section. The pressure values are defined on this keyword and the water saturations are declared on the associated ROCKWNOD keyword in the PROPS section","parameters":[{"index":1,"name":"PRESS","description":"A columnar vector of real monotonically increasing down the column values that defines the corresponding overburden pressure for the subsequent MULT columnar vector.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"None","value_type":"DOUBLE","dimension":"Pressure"},{"index":2,"name":"MULT","description":"A columnar vector of real equal or decreasing down the column values that are less than or equal to one, that defines the rock compressibility pore volume multipliers corresponding to PRESS and for each water saturation entry in the ROCKWNOD keyword.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":"1"}],"example":"The following example defines two pore volume compaction tables, assuming NTROCC is equal to two on the ROCKCOMP keyword and NSSFUN is greater than or equal to four on the TABDIMS keyword.\n--\n-- ROCK COMPACTION VERSUS PRESSURE AND SW TABLES\n--\nROCK2D\n-- PRESS PORV FIRST ROCK2D TABLE DATA\n-- PSIA MULTIPLER\n-- ------ ----------\n0.0 0.850\n0.850\n0.850\n0.085 / P-SW SET TABLE NO. 01\n-- PRESS PORV\n-- PSIA MULTIPLER\n-- ------ ----------\n1000.0 0.900\n0.900\n0.900\n0.900 / P-SW SET TABLE NO. 01\n-- PRESS PORV\n-- PSIA MULTIPLER\n-- ------ ----------\n2500.0 0.950\n0.950\n0.950\n0.950 / P-SW SET TABLE NO. 01\n-- PRESS PORV\n-- PSIA MULTIPLER\n-- ------ ----------\n5000.0 1.000\n1.000\n1.000\n1.000 / P-SW SET TABLE NO. 01\n--\n-- PRESS PORV SECOND ROCK2D TABLE DATA\n-- PSIA MULTIPLER\n-- ------ ----------\n0.0 0.800\n0.800\n0.800\n0.800 / P-SW SET TABLE NO. 02\n-- PRESS PORV\n-- PSIA MULTIPLER\n-- ------ ----------\n1000.0 0.880\n0.880\n0.880\n0.880 / P-SW SET TABLE NO. 02\n-- PRESS PORV\n-- PSIA MULTIPLER\n-- ------ ----------\n2500.0 0.950\n0.950\n0.950\n0.950 / P-SW SET TABLE NO. 02\n-- PRESS PORV\n-- PSIA MULTIPLER\n-- ------ ----------\n5000.0 1.000\n1.000\n1.000\n1.000 / P-SW SET TABLE NO. 02\nNote that there must be exactly NTROCC tables entered for this keyword, otherwise an error will occur.","size_kind":"list","variadic_record":true},"ROCK2DTR":{"name":"ROCK2DTR","sections":["PROPS"],"supported":null,"summary":"The ROCK2DTR keyword defines rock compressibility transmissibility multipliers as a function of pressure and water saturation (“Sw”) for when the rock compaction option has been invoked by the ROCKCOMP keyword in the RUNSPEC section. The pressure values are defined on this keyword and the water saturations are declared on the associated ROCKWNOD keyword in the PROPS section","parameters":[{"index":1,"name":"PRESS","description":"A columnar vector of real monotonically increasing down the column values that defines the corresponding overburden pressure for the subsequent MULT columnar vector.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"None","value_type":"DOUBLE","dimension":"Pressure"},{"index":2,"name":"MULT","description":"A columnar vector of real equal or decreasing down the column values that are less than or equal to one, that defines the rock compressibility transmissibility multipliers corresponding to PRESS and for each water saturation entry in the ROCKWNOD keyword.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":"1"}],"example":"The following example defines two rock compressibility transmissibility compaction tables, assuming NTROCC is equal to two on the ROCKCOMP keyword and NSSFUN is greater than or equal to four on the TABDIMS keyword.\n--\n-- TRANSMISSIBILITY COMPACTION VERSUS PRESSURE AND SW TABLES\n--\nROCK2DTR\n-- PRESS TRAN FIRST ROCK2DTR TABLE DATA\n-- PSIA MULTIPLER\n-- ------ ----------\n0.0 0.850\n0.850\n0.850\n0.085 / P-SW SET TABLE NO. 01\n-- PRESS TRAN\n-- PSIA MULTIPLER\n-- ------ ----------\n1000.0 0.900\n0.900\n0.900\n0.900 / P-SW SET TABLE NO. 01\n-- PRESS TRAN\n-- PSIA MULTIPLER\n-- ------ ----------\n2500.0 0.950\n0.950\n0.950\n0.950 / P-SW SET TABLE NO. 01\n-- PRESS TRAN\n-- PSIA MULTIPLER\n-- ------ ----------\n5000.0 1.000\n1.000\n1.000\n1.000 / P-SW SET TABLE NO. 01\n--\n-- PRESS TRAN SECOND ROCK2DTR TABLE DATA\n-- PSIA MULTIPLER\n-- ------ ----------\n0.0 0.800\n0.800\n0.800\n0.800 / P-SW SET TABLE NO. 02\n-- PRESS TRAN\n-- PSIA MULTIPLER\n-- ------ ----------\n1000.0 0.880\n0.880\n0.880\n0.880 / P-SW SET TABLE NO. 02\n-- PRESS TRAN\n-- PSIA MULTIPLER\n-- ------ ----------\n2500.0 0.950\n0.950\n0.950\n0.950 / P-SW SET TABLE NO. 02\n-- PRESS TRAN\n-- PSIA MULTIPLER\n-- ------ ----------\n5000.0 1.000\n1.000\n1.000\n1.000 / P-SW SET TABLE NO. 02\nNote that there must be exactly NTROCC tables entered for this keyword, otherwise an error will occur.","size_kind":"list","variadic_record":true},"ROCKOPTS":{"name":"ROCKOPTS","sections":["PROPS"],"supported":true,"summary":"The ROCKOPTS keyword defines various options with respect to rock compaction and rock compressibility.","parameters":[{"index":1,"name":"ROCKOPT1","description":"A defined character string that specifies how the overburden pressures supplied by the OVERBURD keyword are applied to the tabulated pressures in the ROCKTAB keywords: STRESS: Use this option if the overburden pressures on the OVERBURD keyword are greater than the fluid pressure which results in the effective fluid pressure being negative. To avoid the rock compaction tables being entered with negative pressure values use this option. In this case the pore volume and transmissibility multipliers will be tabulated against the effective overburden pressure. PRESSURE: In this case the pore volume and transmissibility multipliers should be tabulated against the effective fluid pressure. This the default value. ROCKOPT1 should be set to PRESSURE if the OVERBURD is not used in the input deck. Only the default value of PRESSURE is supported.","units":{},"default":"PRESSURE","value_type":"STRING"},{"index":2,"name":"ROCKOPT2","description":"A defined character string that sets the reference pressure option: STORE: Copies the initial calculated grid block pressures into the overburden pressure array, resulting in the pore volumes being referenced at the initial pressures instead of the reference pressures as per the ROCKTAB keyword. NOSTORE: This option results in the pore volumes being referenced as per the ROCKTAB keyword. This is the default value. Note that STORE option should not be used with the OVERBURD keywords as the OVERBURD data will be overwritten.","units":{},"default":"NOSTORE","value_type":"STRING"},{"index":3,"name":"ROCKOPT3","description":"A defined character string that specifies which region array should be used to allocate the various ROCK and ROCKTAB property tables in the model: ROCKOPT3, should be set to ROCKNUM, SATNUM or PVTNUM. If the parameter is defaulted or the ROCKOPT keyword is not present in the deck, then the PVTNUM array is used. Secondly, if ROCKOPT3 is set to ROCKNUM but the NTROCC parameter on the TABDIMS keyword in the RUNSPEC section is defaulted, then again the PVTNUM array will be utilized. Only the PVTNUM and ROCKNUM options are currently supported.","units":{},"default":"PVTNUM","value_type":"STRING"},{"index":4,"name":"ROCKOPT4","description":"A defined character string that sets the initial conditions for the HYSTER and BOBERG options: DEFLATION: This option defines the reservoir rock to be fully compacted and the deflation curve is used to calculated the initial pore volume and transmissibility multipliers. This is the default value. ELASTIC: This option sets the pore volume and transmissibility multipliers to one, as the reservoir rock is set to lie on the elastic curve. This parameter is ignored by OPM Flow as the ROCKCOMP(ROCKOPT) options of HYSTER and BOBERG are not supported by the simulator.","units":{},"default":"DEFLATION","value_type":"STRING"}],"example":"--\n-- ROCKOPT1 ROCKOPT2 ROCKOPT3 ROCKOPT4\n-- PRS/STRE NO/STORE ARRAY\n-- -------- -------- -------- --------\nROCKOPTS\nPRESSURE NOSTORE PVTNUM / ROCK COMP OPTIONS\nThe above example defines the default values for the ROCKOPTS keyword.","expected_columns":4,"size_kind":"fixed","size_count":1},"ROCKPAMA":{"name":"ROCKPAMA","sections":["PROPS"],"supported":false,"summary":"ROCKPAMA defines the Palmer-Mansoori226\n Palmer, I. and Mansoori, J. “How Permeability Depends on Stress and Pore Pressure in Coalbeds: A New Model,” paper SPE 52607, SPE Reservoir Evaluation & Engineering (1998) 1, No. 6, 539-544. and 227\n Clarkson, C.R., Pan, Z., Palmer, I. and Harpalani, S. \"Predicting Sorption-Induced Strain and Permeability Increase With Depletion for Coalbed-Methane Reservoirs\", SPE 114778-PA, SPE Journal (2010) 15, No. 1, 152–159.parameters used for this rock model, for when the Coal Bed Methane option has been activated via the COAL keyword, and PALM-MAN has been declared for the ROCKOPT variable on the ROCKCOMP keyword; both keywords are in the RUNSPEC section. The Palmer-Mansoori rock model is used to calculate the impact on pore volume and permeability due to rock compaction.","parameters":[{"index":1,"name":"K","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":2,"name":"M","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":3,"name":"G","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":4,"name":"B","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":5,"name":"E1","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":6,"name":"f","description":"","units":{},"default":"0.5","value_type":"DOUBLE"},{"index":7,"name":"n","description":"","units":{},"default":"3","value_type":"DOUBLE"},{"index":8,"name":"g","description":"","units":{},"default":"1","value_type":"DOUBLE"},{"index":9,"name":"Bs","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":10,"name":"Es","description":"","units":{},"default":"0","value_type":"DOUBLE"}],"example":"","expected_columns":10,"size_kind":"fixed"},"ROCKTAB":{"name":"ROCKTAB","sections":["PROPS"],"supported":null,"summary":"The ROCKTAB keyword defines the rock compaction attributes to be applied when the rock compaction option has been invoked by the ROCKCOMP keyword in the RUNSPEC section. ROCKTAB defines pore volume and transmissibility multipliers versus pressure that are used in the compaction calculations. If the RKTRMDIR has been activated in the PROPS section, then the transmissibility multiplier is directional dependent and two additional columns are used to define the y and z direction transmissibility multipliers.","parameters":[{"index":1,"name":"PRESS","description":"If the ROCKOPT1 variable has been set to PRESSURE on the ROCKOPTS keyword in the PROPS section, then PRESS should be a columnar vector of real monotonically increasing down the column values, that define the reference pressure for which the other parameters correspond to. If ROCKOPT1 has been set to STRESS, then PRESS should be a columnar vector of real monotonically decreasing down the column values.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"None","value_type":"DOUBLE","dimension":["Pressure","1","1"]},{"index":2,"name":"PORV","description":"A columnar vector of real positive values that are either equal or increasing down the column that define the rock pore volume multiplier for a given PRESS.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":3,"name":"TRANS","description":"If the RKTRMDIR is absent from the input deck, then TRANS is a columnar vector of real positive values that are either equal or increasing down the column that define the x, y, and z directional transmissibility multipliers for the corresponding PRESS. If the RKTRMDIR is present in the input deck, then TRANS is a columnar vector of real positive values that are either equal or increasing down the column that define only the x directional transmissibility multipliers for the corresponding PRESS.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":4,"name":"TRANSY","description":"If the RKTRMDIR is absent from the input deck, then TRANSY is ignored. If the RKTRMDIR is present in the input deck, then TRANSY is a columnar vector of real positive values that are either equal or increasing down the column that define only the y directional transmissibility multipliers for the corresponding PRESS.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":5,"name":"TRANSZ","description":"If the RKTRMDIR is absent from the input deck, then TRANSZ is ignored. If the RKTRMDIR is present in the input deck, then TRANSZ is a columnar vector of real positive values that are either equal or increasing down the column that define only the z directional transmissibility multipliers for the corresponding PRESS.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"The example below defines two rock compaction tables, assuming NTROCC is equal to two on the ROCKCOMP keyword and NPPVT is greater than or equal to five on the TABDIMS keyword and that the RKTRMDIR keyword is present in the input deck.\n--\n-- ROCK COMPACTION TABLES\n--\nROCKTAB\n-- PRESS PORV TX(YZ) TY TZ\n-- MULT MULT MULT MULT\n-- ------ ------ ------ ------ ------\n1000.0 0.9600 0.9650 0.9650 0.9650\n1500.0 0.9800 0.9850 0.9850 0.9500\n3000.0 0.9900 0.9950 0.9950 0.9950\n4500.0 1.0000 1.0000 1.0000 1.0000\n4750.0 1.0100 1.0100 1.0100 1.0100 / TABLE NO. 01\n-- PRESS PORV TX(YZ) TY TZ\n-- MULT MULT MULT MULT\n-- ------ ------ ------ ------ ------\n1000.0 0.9600 0.9650 0.9650 0.9650\n1500.0 0.9800 0.9850 0.9850 0.9500\n3000.0 0.9900 0.9950 0.9950 0.9950\n4500.0 1.0000 1.0000 1.0000 1.0000\n4750.0 1.0100 1.0100 1.0100 1.0100 / TABLE NO. 02\nAs the x, y and z directional transmissibility multipliers are identical in the above example, we could eliminate the RKTRMDIR keyword from the input deck and enter the data in the three column format, as shown on the next page.\n--\n-- ROCK COMPACTION TABLES\n--\nROCKTAB\n-- PRESS PORV TX(YZ)\n-- MULT MULT\n-- ------ ------ ------\n1000.0 0.9600 0.9650\n1500.0 0.9800 0.9850\n3000.0 0.9900 0.9950\n4500.0 1.0000 1.0000\n4750.0 1.0100 1.0100 / TABLE NO. 01\n-- PRESS PORV TX(YZ)\n-- MULT MULT\n-- ------ ------ ------\n1000.0 0.9600 0.9650\n1500.0 0.9800 0.9850\n3000.0 0.9900 0.9950\n4500.0 1.0000 1.0000\n4750.0 1.0100 1.0100 / TABLE NO. 02\nThe net result of the two examples in this case is identical.","size_kind":"fixed","variadic_record":true},"ROCKTABH":{"name":"ROCKTABH","sections":["PROPS"],"supported":false,"summary":"The ROCKTABH keyword defines the rock compaction hysteresis attributes to be applied for when the rock compaction option has been invoked by the ROCKCOMP keyword in the RUNSPEC section. ROCKTABH defines pore volume and transmissibility multipliers versus pressure that are used in the compaction calculations. If the RKTRMDIR has been activated in the PROPS section, then the transmissibility multiplier is directional dependent and two additional columns are used to define the y and z direction transmissibility multipliers. The keyword should only be used if the Rock Compaction Hysteresis option has been activated by either setting the ROCKOPT parameter on the ROCKCOMP keyword to HYSTER or BOBERG.","parameters":[{"index":1,"name":"PRESS","description":"If the ROCKOPT1 variable has been set to PRESSURE on the ROCKOPTS keyword in the PROPS section, then PRESS should be a columnar vector of real monotonically increasing down the column values, that define the reference pressure for which the other parameters correspond to. If ROCKOPT1 has been set to STRESS, then PRESS should be a columnar vector of real monotonically decreasing down the column values.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"None","value_type":"DOUBLE"},{"index":2,"name":"PORV","description":"A columnar vector of real positive values that are either equal or increasing down the column that define the rock pore volume multiplier for a given PRESS.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":3,"name":"TRANS","description":"If the RKTRMDIR is absent from the input deck, then TRANS is a columnar vector of real positive values that are either equal or increasing down the column that define the x, y, and z directional transmissibility multipliers for the corresponding PRESS. If the RKTRMDIR is present in the input deck, then TRANS is a columnar vector of real positive values that are either equal or increasing down the column that define only the x directional transmissibility multipliers for the corresponding PRESS.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":4,"name":"TRANSY","description":"If the RKTRMDIR is absent from the input deck, then TRANSY is ignored. If the RKTRMDIR is present in the input deck, then TRANSY is a columnar vector of real positive values that are either equal or increasing down the column that define only the y directional transmissibility multipliers for the corresponding PRESS.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":5,"name":"TRANSZ","description":"If the RKTRMDIR is absent from the input deck, then TRANSZ is ignored. If the RKTRMDIR is present in the input deck, then TRANSZ is a columnar vector of real positive values that are either equal or increasing down the column that define only the z directional transmissibility multipliers for the corresponding PRESS.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"The example below defines two rock compaction tables, assuming NTROCC is equal to two on the ROCKCOMP keyword and NPPVT is greater than or equal to four on the TABDIMS keyword and that the RKTRMDIR keyword is not present in the input deck.\n--\n-- ROCK COMPACTION HYSTERESIS TABLES\n--\nROCKTABH\n-- PRESS PORV TX(YZ) TY TZ\n-- MULT MULT MULT MULT\n-- ------ ------ ------ ------ ------\n1500.0 0.9600 0.9800\n2500.0 0.9700 0.9850\n3500.0 0.9800 0.9900\n4500.0 0.9900 0.9950 / NPPVT = 1\n2500.0 0.9900 0.9900\n3500.0 0.9950 0.9950\n4750.0 0.9980 0.9980 / NPPVT = 2\n3500.0 1.0000 1.0000\n5500.0 1.0100 1.0100 / NPPVT = 3\n4500.0 1.0100 1.0100\n5750.0 1.0200 1.0200 / NPPVT = 4\n/ TABLE NO. 01 -- PRESS PORV TX(YZ) TY TZ\n-- MULT MULT MULT MULT\n-- ------ ------ ------ ------ ------\n1500.0 0.9400 0.9700\n2750.0 0.9400 0.9700 / NPPVT = 1\n2250.0 0.9800 0.9900\n3250.0 0.9800 0.9900 / NPPVT = 2\n3000.0 1.0000 1.0000\n4250.0 1.0000 1.0000 / NPPVT = 3\n4550.0 1.0200 1.0100\n5750.0 1.0200 1.0100 / NPPVT = 4\n/ TABLE NO. 02\nHere the deflation curve is define for table number one is:\n1500.0 0.9600 0.9800\n2500.0 0.9900 0.9900\n3500.0 1.0000 1.0000\n4500.0 1.0100 1.0100\nand for table number 2:\n1500.0 0.9400 0.9700\n2250.0 0.9800 0.9900\n3250.0 1.0000 1.0000\n4250.0 1.0200 1.0100\nAnd the dilation curve is define for table number one is:\n4500.0 0.9900 0.9950\n4750.0 0.9980 0.9980\n5500.0 1.0100 1.0100\n5750.0 1.0200 1.0200\nand for table number 2:\n2250.0 0.9400 0.9700\n3250.0 0.9800 0.9900\n4250.0 1.0000 1.0000\n5250.0 1.0200 1.0100","size_kind":"fixed","variadic_record":true},"ROCKTABW":{"name":"ROCKTABW","sections":["PROPS"],"supported":false,"summary":"The ROCKTABW keyword defines the rock compaction tables induced by increasing water saturation within a grid cell due to water invasion, for when the rock compaction option has been invoked by the ROCKCOMP keyword in the RUNSPEC section. ROCKTABW defines pore volume and transmissibility multipliers versus water saturation that are used in the compaction calculations. The keyword should be used together with the ROCK, ROCKTAB or ROCKTABH keywords that specify the pore volume and transmissibility multipliers as functions of pressure. Alternatively the ROCKWNOD, ROCK2D and ROCK2DTR keywords can be used to enter two dimensional tables of the data. All keywords are in the PROPS section.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","size_kind":"fixed","variadic_record":true},"ROCKTHSG":{"name":"ROCKTHSG","sections":["PROPS"],"supported":false,"summary":"The ROCKTHSG keyword defines the rock compaction hysteresis attributes to be applied for when the rock compaction option has been invoked by the ROCKCOMP keyword in the RUNSPEC section and the either the Dual Permeability or Dual Porosity models are activated by the DUALPERM and DUALPORO keywords in the RUNSPEC section. ROCKTHSG specifies sigma multipliers versus pressure that are used in the dual porosity rock compaction calculations. The keyword should only be used if the Rock Compaction Hysteresis option has been activated by either setting the ROCKOPT parameter on the ROCKCOMP keyword to one of the available options.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Pressure","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"ROCKTSIG":{"name":"ROCKTSIG","sections":["PROPS"],"supported":false,"summary":"The ROCKTSIG keyword defines the rock compaction attributes to be applied for when the rock compaction option has been invoked by the ROCKCOMP keyword in the RUNSPEC section, and the either the Dual Permeability or Dual Porosity models are activated by the DUALPERM and DUALPORO keywords in the RUNSPEC section. ROCKTSIG specifies sigma multipliers versus pressure that are used in the dual porosity rock compaction calculations. The keyword should only be used if the Rock Compaction Hysteresis option has been activated by either setting the ROCKOPT parameter on the ROCKCOMP keyword to one of the available options.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Pressure","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"ROCKWNOD":{"name":"ROCKWNOD","sections":["PROPS"],"supported":null,"summary":"The ROCK2D and the ROCK2DTR keywords in the PROPS section define rock compressibility pore volume and transmissibility multipliers as a function of pressure and water saturation (“Sw”), for when the rock compaction option has been invoked by the ROCKCOMP keyword in the RUNSPEC section. The pressure values are defined on ROCK2D and the ROCK2DTR keywords together with the multipliers. This keyword ROCKWNOD, defines the water saturations that are used in conjunction with the ROCK2D and the ROCK2DTR keywords.","parameters":[{"index":1,"name":"SWAT","description":"A columnar vector of real monotonically increasing down the column values that defines the water saturations to be associated with the data on the ROCK2D and the ROCKTR keywords.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":"1"}],"example":"The following example defines two ROCKWNOD tables for the pore volume and transmissibility compaction tables, assuming NTROCC is equal to two on the ROCKCOMP keyword and NSSFUN is greater than or equal to four on the TABDIMS keyword.\n--\n-- WATER SATURATION VALUES FOR COMPACTION PRESSURE-SW TABLES\n--\nROCKWNOD\n-- COMPACT\n-- SWAT\n-- ------\n0.000\n0.200\n0.400\n1.000 / P-SW SET TABLE NO. 01\n-- COMPACT\n-- SWAT\n-- ------\n0.000\n0.250\n0.750\n1.000 / P-SW SET TABLE NO. 02\nNote that there must be exactly NTROCC tables entered for this keyword, otherwise an error will occur.","size_kind":"fixed","variadic_record":true},"RPTPROPS":{"name":"RPTPROPS","sections":["PROPS"],"supported":false,"summary":"This keyword defines the data in the PROPS section that is to be printed to the output print file in human readable format. The keyword has two distinct forms, the first of which consists of the keyword followed by a series of integers on the next line indicating the data to be printed (see the first example). This is the original formal in the commercial simulator and was subsequently superseded by the second format. The second format consists of the keyword followed by a series of character strings that indicate the data to be printed. In most cases the character string is the keyword used to load the data in the OPM Flow input deck, for example PVDG for the dry gas PVT tables. Its is anticipated that OPM Flow will eventually support the functionality of the second format only, the first format although recognized will be completely ignored.","parameters":[{"index":1,"name":"PVDG","description":"Print dry gas PVT tables","units":{},"default":"N/A","value_type":"STRING"},{"index":2,"name":"PVTG","description":"Print wet gas PVT tables","units":{},"default":"N/A"},{"index":3,"name":"SGFN","description":"Print gas relative permeability saturation function tables.","units":{},"default":"N/A"},{"index":4,"name":"SGL","description":"Print connate gas saturation array.","units":{},"default":"N/A"}],"example":"The first example shows the original format of this keyword; although the keyword and format are recognized by OPM Flow, the format is ignored and is unlikely to be implemented in in the simulator.\n--\n-- DEFINE PROPS SECTION REPORT OPTION (ORIGINAL FORMAT)\n–\nRPTPROPS\n1 2*0 1 3*1 /\nThe next example shows the second format of the keyword which may be supported in a future release of OPM Flow.\n--\n-- DEFINE PROPS SECTION REPORT OPTIONS\n--\nRPTPROPS\nPVDO SOF2 SGFN SWFN /\n| Note Except for tabular like data, PVDG etc., this keyword has the potential to produce very large print files that some text editors may have difficulty loading. A more efficient solution for array type data is to load the *.INIT file into OPM ResInsight to view the data graphically, this also has the benefit of being able to filter the grid based on I, J, K ranges and grid properties. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"fixed","size_count":1,"variadic_record":true},"RSCONST":{"name":"RSCONST","sections":["PROPS"],"supported":false,"summary":"RSCONST defines a constant Gas-Oil Ratio (“GOR”), for all dead oil228\n “Dead” oil is oil that it contains no dissolved gas or a relatively thick oil or residue that has lost its volatile components. PVT fluids. If the oil has a constant and uniform dissolved gas concentration, GOR, and if the reservoir pressure never drops below the saturation pressure (bubble point pressure), then the model can be run more efficiently by omitting the GAS and DISGAS keywords from the RUNSPEC section, treating the oil as a dead oil, and defining a constant Rs (GOR) value with keywords RSCONST or RSCONSTT in the PROPS section. This results in the model being run as a dead oil problem with no active gas phase. However, OPM Flow takes into account the constant Rs in the calculations and reporting.","parameters":[{"index":1,"name":"RS","description":"A real positive value that defines the dead oil GOR for all oil PVT tables in the model","units":{"field":"Mscf/stb","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"None","value_type":"DOUBLE","dimension":"GasDissolutionFactor"},{"index":2,"name":"PRESS","description":"A real positive value that defines that saturation pressure (bubble point pressure) for all the oil PVT tables in the model.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":"Pressure"}],"example":"The example sets the dead oil GOR to 5 scf/stb and the bubble point pressure to 14.7 psia.\n--\n-- DEAD OIL PVT CONSTANT GOR AND SATURATION PRESSURE\n--\nRSCONST\n-- RS PSAT\n-- MSCF/STB PSIA\n-- -------- ------\n0.0050 14.7 /","expected_columns":2,"size_kind":"fixed","size_count":1},"RSCONSTT":{"name":"RSCONSTT","sections":["PROPS"],"supported":false,"summary":"RSCONSTT defines a constant Gas-Oil Ratio (“GOR”), for each dead oil229\n “Dead” oil is oil that it contains no dissolved gas or a relatively thick oil or residue that has lost its volatile components. PVT fluid in the model. If the oil has a constant and uniform dissolved gas concentration, GOR, and if the reservoir pressure never drops below the saturation pressure (bubble point pressure), then the model can be run more efficiently by omitting the GAS and DISGAS keywords from the RUNSPEC section, treating the oil as a dead oil, and defining a constant Rs (GOR) value with keywords RSCONST or RSCONSTT in the PROPS section. This results in the model being run as a dead oil problem with no active gas phase. However, OPM Flow takes into account the constant Rs in the calculations and reporting.","parameters":[{"index":1,"name":"RS","description":"A real positive columnar vector that defines the dead oil GOR for each oil PVT table in the model","units":{"field":"Mscf/stb","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"None","value_type":"DOUBLE","dimension":"GasDissolutionFactor"},{"index":2,"name":"PRESS","description":"A real positive columnar vector that defines the saturation pressure (bubble point pressure) for each the oil PVT table in the model.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":"Pressure"}],"example":"The example sets the dead oil GOR to 5, 6.5 and 8.0 scf/stb for PVT tables one, two and three, respectively and the bubble point pressure to 14.7 psia for all three tables.\n--\n-- DEAD OIL PVT CONSTANT GOR AND SATURATION PRESSURE\n--\nRSCONSTT\n-- RS PSAT\n-- MSCF/STB PSIA\n-- -------- ------\n0.0050 14.7 / TABLE NO. 01\n0.0065 14.7 / TABLE NO. 02\n0.0080 14.7 / TABLE NO. 03","expected_columns":2,"size_kind":"fixed"},"RSGI":{"name":"RSGI","sections":["PROPS"],"supported":false,"summary":"The RSGI keyword specifies the saturated oil Gas-Oil Ratio (“GOR”) factors used to specify the variation of the maximum possible GOR of oil with respect to pressure and Gi values, for when the GIMODEL keyword in the RUNSPEC section has been used to activate the GI Pseudo Compositional option for the run. See also the GINODE, RSGI, RVGI, BGGI and BOGI keywords in the PROPS section to describe the fluid properties for the GI Pseudo Compositional option.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Pressure","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"RTEMP":{"name":"RTEMP","sections":["PROPS","SOLUTION"],"supported":true,"summary":"This keyword defines the initial reservoir temperature for the model. Note that the RTEMP keyword is an alias for RTEMPA, and that both keywords are supported by OPM Flow, in both the PROPS and SOLUTION sections, but are treated as being mutually exclusive.","parameters":[{"index":1,"name":"RTEMP","description":"Single real positive value that defines the reservoir temperature for the model.","units":{"field":"oF","metric":"oC","laboratory":"oC"},"default":"None","value_type":"DOUBLE","dimension":"Temperature"}],"example":"--\n-- RESERVOIR\n-- TEMPERATURE\n-- -----------\nRTEMP\n190.0 / RESERVOIR TEMPERATURE\nThe above example defines the reservoir temperature to be 190 oF.","expected_columns":1,"size_kind":"fixed","size_count":1},"RTEMPA":{"name":"RTEMPA","sections":["PROPS","SOLUTION"],"supported":true,"summary":"This keyword defines the initial reservoir temperature for the model. Note that the RTEMPA keyword is an alias for RTEMP, and that both keywords are supported by OPM Flow, in both the PROPS and SOLUTION sections, but are treated as being mutually exclusive.","parameters":[{"index":1,"name":"RTEMPA","description":"Single real positive value that define the reservoir temperature for the model.","units":{"field":"oF","metric":"oC","laboratory":"oC"},"default":"None","value_type":"DOUBLE","dimension":"Temperature"}],"example":"--\n-- RESERVOIR\n-- TEMPERATURE\n-- -----------\nRTEMPA\n190.0 / RESERVOIR TEMPERATURE\nThe above example defines the reservoir temperature to be 190 oF.","expected_columns":1,"size_kind":"fixed","size_count":1},"RTEMPVD":{"name":"RTEMPVD","sections":["PROPS","SOLUTION"],"supported":true,"summary":"This keyword defines the initial reservoir temperature versus depth tables for each equilibration region. Note that the RTEMPVD keyword is an alias for TEMPVD, and that both keywords are supported by OPM Flow, in both the PROPS and SOLUTION sections, but are treated as being mutually exclusive.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Length","Temperature"]}],"example":"","size_kind":"fixed","variadic_record":true},"RVCONST":{"name":"RVCONST","sections":["PROPS"],"supported":false,"summary":"RVCONST defines a constant Condensate-Gas Ratio (“CGR” or Rv), for all dry gas230\n Natural gas that occurs in the absence of condensate or liquid hydrocarbons, or gas that had condensable hydrocarbons removed, is called dry gas. It is primarily methane with some intermediates. The hydrocarbon mixture is solely gas in the reservoir and there is no liquid (condensate surface liquid) formed either in the reservoir or at surface. The term dry indicates that the gas does not contain heavier hydrocarbons to form liquids at the surface conditions. Dry gas typically has GOR's greater than 100,000 scf/stb or 18,000 Sm3/m3. PVT fluids. If the gas has a constant and uniform dissolved condensate concentration, and if the reservoir pressure never drops below the saturation pressure (dew point pressure), then the model can be run more efficiently by omitting the OIL and VAPOIL keywords from the RUNSPEC section, treating the gas as a dry gas, and defining a constant Rv (CGR) value with keywor...","parameters":[{"index":1,"name":"RV","description":"A real positive value that defines the dry gas CGR for all dry gas PVT tables in the model","units":{"field":"stb/Mscf","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"None","value_type":"DOUBLE","dimension":"OilDissolutionFactor"},{"index":2,"name":"PRESS","description":"A real positive value that defines that saturation pressure (dew point pressure) for all the dry gas PVT tables in the model.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"0.0","value_type":"DOUBLE","dimension":"Pressure"}],"example":"The example sets the dry gas CGR to 5 stb/MMscf and the bubble point pressure to 14.7 psia.\n--\n-- DRY GAS PVT CONSTANT GCR AND SATURATION PRESSURE\n--\nRVCONST\n-- RV PSAT\n-- STB/MSCF PSIA\n-- -------- ------\n0.0050 14.7 /","expected_columns":2,"size_kind":"fixed","size_count":1},"RVCONSTT":{"name":"RVCONSTT","sections":["PROPS"],"supported":null,"summary":"RVCONSTT defines a constant Condensate-Gas Ratio (“CGR” or Rv), for each dry gas231\n Natural gas that occurs in the absence of condensate or liquid hydrocarbons, or gas that had condensable hydrocarbons removed, is called dry gas. It is primarily methane with some intermediates. The hydrocarbon mixture is solely gas in the reservoir and there is no liquid (condensate surface liquid) formed either in the reservoir or at surface. The term dry indicates that the gas does not contain heavier hydrocarbons to form liquids at the surface conditions. Dry gas typically has GOR's greater than 100,000 scf/stb or 18,000 Sm3/m3. PVT fluid. If the gas has a constant and uniform dissolved condensate concentration, and if the reservoir pressure never drops below the saturation pressure (dew point pressure), then the model can be run more efficiently by omitting the OIL and VAPGAS keywords from the RUNSPEC section, treating the gas as a dry gas, and defining a constant Rv (CGR) value with keywo...","parameters":[{"index":1,"name":"RS","description":"A real positive value that defines the dry gas CGR for each dry gas PVT table in the model","units":{"field":"stb/Mscf","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"None","value_type":"DOUBLE","dimension":["OilDissolutionFactor","Pressure"]},{"index":2,"name":"PRESS","description":"A real positive value that defines that saturation pressure (dew point pressure) for each dry gas PVT table in the model.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"0.0"}],"example":"The example sets the dry gas CGR to 5, 6.5 and 8.0 stb/MMscf for PVT tables one, two and three, respectively and the bubble point pressure to 14.7 psia for all three tables.\n--\n-- DRY GAS PVT CONSTANT GCR AND SATURATION PRESSURE\n--\nRVCONSTT\n-- RV PSAT\n-- STB/MSCF PSIA\n-- -------- ------\n0.0050 14.7 / TABLE NO. 01\n0.0065 14.7 / TABLE NO. 02\n0.0080 14.7 / TABLE NO. 03","size_kind":"fixed","variadic_record":true},"RVGI":{"name":"RVGI","sections":["PROPS"],"supported":false,"summary":"The RVGI keyword specifies the saturated gas Condensate-Gas Ratio (“CGR”) factors used to specify the variation of the maximum possible CGR of gas with respect to pressure and Gi values, for when the GIMODEL keyword in the RUNSPEC section has been used to activate the GI Pseudo Compositional option for the run. See also the GINODE, RSGI, RVGI, BGGI and BOGI keywords in the PROPS section to describe the fluid properties for the GI Pseudo Compositional option.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Pressure","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"RWGSALT":{"name":"RWGSALT","sections":["PROPS"],"supported":null,"summary":"RWGSALT defines the relationship of water vaporization versus pressure and salt concentration. This keyword should be used when the VAPWAT keyword has be declared in the RUNSPEC section indicating that vaporized water is present in the gas phase. In addition, if the Salt Precipitation model has been activated via the BRINE and PRECSALT keywords, also in the RUNSPEC section, then this keyword must be present. The keyword may be used for gas-water and oil-water-gas input decks that contain the either dry or wet gas and vaporized water phases.","parameters":[{"index":1,"name":"PRESS","description":"A real monotonically increasing down the column values that define the gas phase pressure, that together with salt concentration, defines the vaporized water in gas ratio (“VWGR”) or Rw","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":"Pressure"},{"index":2,"name":"SALTCON","description":"A real monotonically increasing positive columnar vector defining the salt concentration in water.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None","value_type":"DOUBLE","dimension":["Concentration","OilDissolutionFactor"]},{"index":3,"name":"RW","description":"A columnar vector of real positive number values defining the vaporized water in gas ratio (Rw) that for a given PRESS and SALTCON.","units":{"field":"stb/Mscf","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"None"}],"example":"The example defines two RWGSALT tables assuming NTPVT equals two and NPPVT is greater than or equal to eight on the TABDIMS keyword in the RUNSPEC section.\n--\n-- WATER VAPORIZATION TABLE FOR BRINE (OPM FLOW KEYWORD)\n--\nRWGSALT\n-- PRES SALTCONC RVW\n-- PSIA LB/STB STB/MSCF\n-- ------ ---------- ---------\n300 0 0.000132\n0.5 0.000132\n1 0.000132 /\n600 0 0.000132\n0.5 0.000132\n1 0.000132 /\n900 0 0.000132\n0.5 0.000132\n1 0.000132 /\n1200 0 0.000132\n0.5 0.000132\n1 0.000132 /\n1500 0 0.000132\n0.5 0.000132\n1 0.000132 /\n1800 0 0.000132\n0.5 0.000132\n1 0.000132 /\n2100 0 0.000132\n0.5 0.000132\n1 0.000132 /\n2400 0 0.000132\n0.5 0.000132\n1 0.000132 /\n/ Table NO. 1\n-- PRES SALTCONC RW\n-- PSIA LB/STB STB/MSCF\n-- ------ ---------- ---------\n300 0 0.000132\n0.5 0.000132\n1 0.000132 /\n600 0 0.000132\n0.5 0.000132\n1 0.000132 /\n900 0 0.000132\n0.5 0.000132\n1 0.000132 /\n1200 0 0.000132\n0.5 0.000132\n1 0.000132 /\n1500 0 0.000132\n0.5 0.000132\n1 0.000132 /\n1800 0 0.000132\n0.5 0.000132\n1 0.000132 /\n2100 0 0.000132\n0.5 0.000132\n1 0.000132 /\n2400 0 0.000132\n0.5 0.000132\n1 0.000132 /\n/ Table NO. 2\n| Note This is an OPM Flow specific keyword for the simulator’s Water Vaporization and Salt Precipitation Models, note that these are extensions to the simulator’s standard Brine model. |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"list","variadic_record":true},"SALINITY":{"name":"SALINITY","sections":["PROPS"],"supported":null,"summary":"The SALINITY keyword defines a uniform salinity for all cells in the model. The keyword should only be used with OPM Flow’s CO2-Brine model which is activated via the CO2STORE keyword in the RUNSPEC section. This keyword is a compositional keyword in the commercial simulator but has been implemented in OPM Flow’s black-oil CO2-Brine model.","parameters":[{"index":1,"name":"SALINITY","description":"A real positive value that defines the salinity for all grid blocks in the model for when the CO2-Brine model has been activated. Note that the units for salinity are molality, that is gm-M/Kg, and therefore the units are defined as given below with the 10-3 prefix.","units":{"field":"10-3 x lb-M/lb","metric":"10-3 x kg-M/kg","laboratory":"10-3 x gm-M/gm"},"default":"","value_type":"DOUBLE"}],"example":"The example sets the salt salinity for all cells in the model to 0.001 lb-M/Ib.\n--\n-- SET SALINITY FOR ALL CELLS (OPM FLOW KEYWORD)\n--\nSALINITY\n1.0 /\nNote that units for salinity are to the 10-3, that is a value of 0.001 lb-M/lb should be entered as 1.0 (10-3 x lb-M/lb), as per the example.","expected_columns":1,"size_kind":"fixed","size_count":1},"SALTMF":{"name":"SALTMF","sections":["PROPS"],"supported":null,"summary":"The SALTMF keyword defines a uniform salt liquid-phase mole fraction for all cells in the model. The keyword should only be used with OPM Flow’s CO2-Brine model which is activated via the CO2STORE keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"SALTMF","description":"A real positive value that defines the salt liquid-phase mole fraction for all grid blocks in the model for when the CO2-Brine model has been activated.","units":{"field":"mole fraction","metric":"mole fraction","laboratory":"mole fraction"},"default":"","value_type":"DOUBLE"}],"example":"The example sets the salt liquid-phase mole fraction for all cells in the model to 0.018.\n--\n-- SET SALT LIQUID-PHASE MOLE FRACTION FOR ALL CELLS (OPM FLOW KEYWORD)\n--\nSALTMF\n0.018 /","expected_columns":1,"size_kind":"fixed","size_count":1},"SALTNODE":{"name":"SALTNODE","sections":["PROPS"],"supported":false,"summary":"SALTNODE defines the salt concentration value based on a cells PVTNUM number. The SALTNODE property is used in the calculation of a polymer viscosity when the polymer and the salt options has been activated by the POLYMER and BRINE keywords in the RUNSPEC section. In the RUNSPEC section the number of PVTNUM functions is declared by NTPVT variable on the TABDIMS keyword and allocated to individual cells by the PVTNUM property array in the REGIONS section. NPPVT on the TABDIMS keyword in the RUNSPEC section defines the maximum number of rows (or pressure values) in the PVT tables and also sets the maximum number of entries for each SALNODE data set. The number of values for each data set must correspond to the number of polymer solution adsorption entries on the PLYADSS keyword. For example if there are three sets of PVT tables and four values on the PLYADSS keyword, then three SALTNODE data sets with four values of salt concentrations need to be entered.","parameters":[{"index":1,"name":"SALTNODE","description":"A real monotonically increasing positive columnar vector defining the salt concentration for a given PVTNUM table.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None","value_type":"DOUBLE","dimension":"Concentration"}],"example":"Given three sets of relative permeability tables and four values on the PLYADSS keyword and two SALNODE data sets with four values of salt concentrations then the data should be entered as follows:\n--\n-- SETS SALT CONCENTRATION FOR POLYMER SOLUTION ADSORPTION\n-- VIA PVTNUM ARRAY ALLOCATION\n--\n-- SALT\n--\nSALTNODE\n1.0\n5.0\n10.5\n25.0 / PVTNUM TABLE NO. 01\n1.0\n3.0\n7.5\n15.0 / PVTNUM TABLE NO. 02\nSee also the ADSALNOD keyword.","size_kind":"fixed","variadic_record":true},"SALTSOL":{"name":"SALTSOL","sections":["PROPS"],"supported":null,"summary":"SALTSOL defines a grid block's maximum salt solubility for each PVTNUM region. The keyword should only be used with OPM Flow’s Salt Precipitation model which is activated via the PRECSALT keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"SALTSOL","description":"A real positive value that defines the maximum salt solubility for all grid blocks in a PVTNUM region.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None","value_type":"DOUBLE","dimension":["Concentration","Density"]}],"example":"The first example sets the maximum salt solubility for all cells in the model to 134.6 lb/stb, assuming that there is only one PVT region, that is NTPVT is equal to one on the TABDIMS keyword in the RUNSPEC section.\n--\n-- SET SALT SOLUBILITY LIMIT FOR EACH REGION (OPM FLOW KEYWORD)\n--\nSALTSOL\n-- MAX SALT\n-- SALTSOL DENSITY\n134.6 1* /\nThe 134.6 lb/stb, (380 kg/sm3 or 0.384 gm/scc for metric and laboratory units, respectively) is based on the solubility of NACL at 212 oF (100 oC) and should be used with care.\nThe next example shows how to set the maximum salt solubility for when NTPVT is equal to three on the TABDIMS keyword in the RUNSPEC section.\n--\n-- SET SALT SOLUBILITY LIMIT FOR EACH REGION (OPM FLOW KEYWORD)\n--\nSALTSOL\n134.6 / PVT REGION NO. 1\n124.0 / PVT REGION NO. 2\n/ PVT REGION NO. 3\nHere the last entry, which is for region number three, is defaulted, and results in region’s three maximum salt solubility to take the previous value, in this case 124.0 lb/stb.\n| Note This is an OPM Flow specific keyword for the simulator’s Salt Precipitation model that is activated by the PRECSALT keyword and declaring that vaporized water is present in the run via the VAPWAT in the RUNSPEC section. |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"fixed","variadic_record":true},"SCALECRS":{"name":"SCALECRS","sections":["PROPS"],"supported":null,"summary":"The SCALECRS keyword sets the end-point scaling option to be either two-point or three-point scaling, for when the End-Point Scaling option has been invoked by the ENDSCALE keyword in the RUNSPEC section. This determines which end-points on the relative permeability curves are used for scaling based on the supplied end-point arrays (SGCR, SWCR, etc.).","parameters":[{"index":1,"name":"SCALEOPT","description":"SCALEOPT is a character string that sets the end-point scaling option and should be set to either NO or YES: NO: Activates two-point end-point scaling. YES: Activates three-point end-point","units":{},"default":"NO","value_type":"STRING"}],"example":"--\n-- TWO-POINT END-POINT SCALING IS NO THREE POINT IS YES\n--\n-- SCALEOPT\n-- ---------\nSCALECRS\nYES / SCALING OPTION\nThe above example activates three-point end-point scaling of the relative permeability curves.\n| Option | Phases | Relative Permeability End-Point | Minimum Saturation End-Point | Middle Saturation End-Point | Maximum Saturation End-Point |\n|---------------------------------|--------|---------------------------------|------------------------------|-----------------------------|------------------------------|\n| Two-Point | Water | KRW | SWCR | | SWU |\n| Gas | KRG | SGCR | | SGU | |\n| Oil-Water | KRORW | SOWCR | | (1.0 – SWL - SGL) | |\n| Oil-Gas | KRORG | SOGCR | | (1.0 – SWL - SGL) | |\n| Three-Point | Water | KRW | SWCR | (1.0 – SOWCR - SGL) | SWU |\n| Gas | KRG | SGCR | (1.0 - SOGCR-SWL) | SGU | |\n| Oil-Water | KRORW | SOWCR | (1.0 – SWCR - SGL) | (1.0 – SWL - SGL) | |\n| Oil-Gas | KRORG | SOGCR | (1.0 – SGCR - SGL) | (1.0 – SWL - SGL) | |\n| Two Phase Gas-Water Simulations | | | | | |\n| Water | KRW | SWCR | (1.0 - SGCR) | SWU | |\n| Gas | KRG | SGCR | (1.0 -SWCR) | SGU | |","expected_columns":1,"size_kind":"fixed","size_count":1},"SCALELIM":{"name":"SCALELIM","sections":["PROPS"],"supported":false,"summary":"This keyword defines the maximum water saturation allowed in a cell for when the end-point versus depth tables are used in the End-Point Scaling option to calculate the water saturation for a grid block. The End-Point Scaling option must be invoked by the ENDSCALE keyword in the RUNSPEC section to use this keyword, and the keyword may only be used in two phase runs containing water, or if the Miscible Flood option has been activated by the MISCIBLE keyword in the RUNSPEC section. This keyword functionality is not supported in OPM Flow.","parameters":[{"index":1,"name":"SAT_LIMIT","description":"","units":{},"default":"0","value_type":"DOUBLE"}],"example":"","expected_columns":1,"size_kind":"fixed"},"SDENSITY":{"name":"SDENSITY","sections":["PROPS"],"supported":null,"summary":"The SDENSITY keyword defines density at surface conditions of either the miscible injection gas for when the MISCIBLE option has been invoked in the RUNSPEC section, or the solvent for when the SOLVENT option has been invoked in the RUNSPEC section. This keyword must be invoked if either the MISCIBLE or SOLVENT options have been activated in the RUNSPEC section.","parameters":[{"index":1,"name":"SDENSITY","description":"SDENSITY is a real positive number defining the density at surface conditions of either: the miscible injection gas for when the MISCIBLE option has been invoked in the RUNSPEC section, or, the solvent for when the SOLVENT option has been invoked in the RUNSPEC section.","units":{"field":"lb/ft3","metric":"kg/m3","laboratory":"gm/cc"},"default":"None","value_type":"DOUBLE","dimension":"Density"}],"example":"The following shows the SDENSITY keyword for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set to one.\n--\n-- MIS-SOL\n-- DENSITY\n-- -------\nSDENSITY\n0.04520 / MIS-SOL DENSITY\nThe next example shows the SDENSITY keyword for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set to three.\n--\n-- MIS-SOL\n-- DENSITY\n-- -------\nSDENSITY\n0.04520 / MIS-SOL DENSITY 1\n0.05520 / MIS-SOL DENSITY 2\n0.06420 / MIS-SOL DENSITY 3\nThere is no terminating “/” for this keyword.","expected_columns":1,"size_kind":"fixed"},"SGCR":{"name":"SGCR","sections":["PROPS"],"supported":null,"summary":"SGCR defines the critical gas saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE keyword in the RUNSPEC section. The critical gas saturation is defined as the maximum gas saturation for which the gas relative permeability is zero in a two-phase relative permeability table.","parameters":[{"index":1,"name":"SGCR","description":"SGCR is an array of real numbers assigning the critical gas saturation values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.03","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT SGCR DATA FOR ALL CELLS\n-- (FOR NX x NY x NZ = 300)\n--\nSGCR\n300*0.050 /\nThe above example defines a constant critical gas saturation of 0.05 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"SGCWMIS":{"name":"SGCWMIS","sections":["PROPS"],"supported":null,"summary":"SGCWMIS defines the dependency between the miscible critical gas saturation and the water saturation, for when the MISCIBLE keyword in the RUNSPEC section has been activated. The keyword can only be used with the MISCIBLE option and for when the oil, water and gas phases are active in the model.","parameters":[{"index":1,"name":"SWAT","description":"A columnar vector of real monotonically increasing down the column values starting from zero and terminating atone, that defines the water saturation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":["1","1"]},{"index":2,"name":"SGCMIS","description":"A columnar vector of real equal or increasing down the column values that are greater than or equal to zero and less than one, that define the corresponding miscible gas critical gas saturation for the corresponding water saturation SWAT.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- MISCIBLE CRITICAL GAS VERSUS WATER SATURATION TABLE\n--\nSGCWMIS\n-- SWAT SGCRMIS\n-- FRAC FRAC\n-- ------- --------\n0.0000 0.0000\n0.2000 0.0300\n1.0000 0.0300 / TABLE NO. 01\n-- SWAT SGCRMIS\n-- FRAC FRAC\n-- ------- --------\n0.0000 0.0000\n0.3000 0.0500\n1.0000 0.0500 / TABLE NO. 02\nThe above example defines two miscible critical gas saturation versus water saturation tables assuming NTMISC equals two and NSMISC is greater than or equal to three on the MISCIBLE keyword in the RUNSPEC section.","size_kind":"fixed","variadic_record":true},"SGF32D":{"name":"SGF32D","sections":["PROPS"],"supported":false,"summary":"The SGF32D keyword defines the gas relative permeability as a function of both oil and water saturations. This keyword should only be used if the gas is present in the run.","parameters":[{"index":1,"name":"SOIL","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1","record":1},{"index":1,"name":"SWAT","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1","record":2},{"index":2,"name":"KRG","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1","record":2}],"example":"","records_meta":[{},{"expected_columns":2}],"size_kind":"list"},"SGFN":{"name":"SGFN","sections":["PROPS"],"supported":null,"summary":"The SGFN keyword defines the gas relative permeability and oil-gas capillary pressure data versus gas saturation tables for when gas is present in the input deck. This keyword should only be used if the gas is present in the run.","parameters":[{"index":1,"name":"SGAS","description":"A columnar vector of real monotonically increasing down the column values starting from zero and terminating at one, that defines the gas saturation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":["1","1","Pressure"]},{"index":2,"name":"KRG","description":"A columnar vector of real values that are either equal or increasing down the column and that are greater than or equal to zero and less than or equal to one that defines the gas relative permeability.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":3,"name":"PCOG","description":"A columnar vector of real values that are either equal or increasing down the column that defines the oil-gas capillary pressure.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"None"}],"example":"--\n-- GAS RELATIVE PERMEABILITY TABLES (SGFN)\n--\nSGFN\n-- SGAS KRG PCGO\n-- FRAC PSIA\n-- -------- -------- -------\n0.00 0.0000 0.0\n0.05 0.0000 0.0\n0.10 0.0000 0.0\n0.15 0.0000 0.0\n0.20 0.0002 0.0\n0.25 0.0010 0.0\n0.30 0.0062 0.0\n0.35 0.0140 0.0\n0.40 0.0273 0.0\n0.45 0.0450 0.0\n0.50 0.0707 0.0\n0.55 0.1020 0.0\n0.60 0.1412 0.0\n0.65 0.1870 0.0\n0.70 0.2412 0.0\n0.77 0.3288 0.0\n0.82 0.4000 0.0\n0.85 0.4450 0.0 / TABLE NO. 01\n-- SGAS KRG PCGO\n-- FRAC PSIA\n-- -------- -------- -------\n0.00 0.0000 0.0\n0.05 0.0000 0.0\n0.10 0.0000 0.0\n0.15 0.0000 0.0\n0.20 0.0002 0.0\n0.25 0.0010 0.0\n0.30 0.0062 0.0\n0.35 0.0140 0.0\n0.40 0.0273 0.0\n0.45 0.0450 0.0\n0.50 0.0707 0.0\n0.55 0.1020 0.0\n0.60 0.1412 0.0\n0.65 0.1870 0.0\n0.70 0.2412 0.0\n0.77 0.3288 0.0\n0.82 0.4000 0.0\n0.85 0.4450 0.0 / TABLE NO. 02\nThe example defines two SGFN tables for when gas is present in the input deck.","size_kind":"fixed","variadic_record":true},"SGL":{"name":"SGL","sections":["PROPS"],"supported":null,"summary":"SGL defines the connate gas saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE keyword in the RUNSPEC section. The connate gas saturation is defined as the minimum gas saturation in a two-phase gas relative permeability table.","parameters":[{"index":1,"name":"SGL","description":"SGL is an array of real numbers assigning the connate gas saturation values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.03","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT SGL DATA FOR ALL CELLS\n– (FOR NX x NY x NZ = 300)\n--\nSGL\n300*0.030 /\nThe above example defines a constant connate gas saturation of 0.03 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"SGLPC":{"name":"SGLPC","sections":["PROPS"],"supported":null,"summary":"SGLPC defines the connate gas saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE keyword in the RUNSPEC section. The connate gas saturation is defined as the minimum gas saturation in a two-phase gas relative permeability table. The keyword only applies the scaling to the drainage capillary pressure tables, unlike the SGL keyword that applies the scaling to both the capillary pressure and relative permeability tables. The keyword can be used with all grid types.","parameters":[{"index":1,"name":"SGLPC","description":"SGLPC is an array of real numbers assigning the connate gas saturation values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. If SGLPC is omitted from the input deck the values will be defaulted to those on the SGL series of keywords. If the SGL series of keywords are missing from the input deck then the values are taken from the cell allocated capillary pressure table. Repeat counts may be used, for example 30*0.03","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from SGL or from the cell allocated capillary pressure table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT SGLPC DATA FOR ALL CELLS\n–- (FOR NX x NY x NZ = 300)\n--\nSGLPC\n300*0.030 /\nThe above example defines a constant connate gas saturation of 0.03 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"SGOF":{"name":"SGOF","sections":["PROPS"],"supported":null,"summary":"The SGOF keyword defines the oil and gas relative permeability and oil-gas capillary versus gas saturation tables for when oil and gas are present in the input deck. This keyword should only be used if both oil and gas are present in the run.","parameters":[{"index":1,"name":"SGAS","description":"A columnar vector of real monotonically increasing down the column values starting from zero and terminating at one, that defines the gas saturation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":["1","1","1","Pressure"]},{"index":2,"name":"KRG","description":"A columnar vector of real values that are either equal or increasing down the column and that are greater than or equal to zero and less than or equal to one that defines the gas relative permeability.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":3,"name":"KRO","description":"A columnar vector of real values that are either equal or decreasing down the column and that are greater than or equal to zero and less than or equal to one that defines the oil relative permeability with respect to gas and connate water saturation. When water is active in the run, the first entry the column, that is at krog(Sg = 0), must be the same as the first entry in the corresponding SWOF table, that is at krow(So = 1 - Swco). The last value in the column should be zero.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":4,"name":"PCOG","description":"A columnar vector of real values that are either equal or increasing down the column that defines the oil-gas relative capillary pressure.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"None"}],"example":"The following example is based on NTSFUN equals two on the TABDIMS keyword in the RUNSPEC section.\n--\n-- GAS-OIL RELATIVE PERMEABILITY TABLES (SGOF)\nSGOF\n-- SG KRG KROG PCOG\n-- FRAC PSIA\n-- ------- -------- ------- -------\n0.00000 0.000000 0.90000 0.0000\n0.03000 0.000000 0.82500 0.0000\n0.80000 0.900000 0.00000 0.0000 / TABLE No. 01\n-- ------- -------- ------- -------\n0.00000 0.000000 0.90000 0.0000\n0.03000 0.000000 0.82500 0.0000\n0.04420 0.024200 0.80000 0.0000\n0.05850 0.048500 0.77500 0.0000\n0.07270 0.072700 0.75000 0.0000\n0.08700 0.097000 0.72500 0.0000\n0.10120 0.121200 0.70000 0.0000\n0.11550 0.145500 0.67500 0.0000\n0.12970 0.169700 0.65000 0.0000\n0.14390 0.193900 0.62500 0.0000\n0.15820 0.218200 0.60000 0.0000\n0.17240 0.242400 0.57500 0.0000\n0.18670 0.266700 0.55000 0.0000\n0.20090 0.290900 0.52500 0.0000\n0.21520 0.315200 0.50000 0.0000\n0.22940 0.339400 0.47500 0.0000\n0.24360 0.363600 0.45000 0.0000\n0.25790 0.387900 0.42500 0.0000\n0.27210 0.412100 0.40000 0.0000\n0.28640 0.436400 0.37500 0.0000\n0.30060 0.460600 0.35000 0.0000\n0.31480 0.484800 0.32500 0.0000\n0.32910 0.509100 0.30000 0.0000\n0.34330 0.533300 0.27500 0.0000\n0.35760 0.557600 0.25000 0.0000\n0.37180 0.581800 0.22500 0.0000\n0.38610 0.606100 0.20000 0.0000\n0.40030 0.630300 0.17500 0.0000\n0.41450 0.654500 0.15000 0.0000\n0.42880 0.678800 0.12500 0.0000\n0.44300 0.703000 0.10000 0.0000\n0.45730 0.727300 0.07500 0.0000\n0.47150 0.751500 0.05000 0.0000\n0.48580 0.775800 0.02500 0.0000\n0.50000 0.800000 0.00000 0.0000\n0.80000 0.900000 0.00000 0.0000 / TABLE No. 02\nThe example defines two SGOF tables for use when oil, gas and water are present in the run.","size_kind":"fixed","variadic_record":true},"SGOFLET":{"name":"SGOFLET","sections":["PROPS"],"supported":null,"summary":"SGOFLET defines the relative permeability and capillary pressure parameters for the gas-oil LET family of models. Both the gas and oil phases should be made active in the model via the GAS and OIL keywords in the RUNSPEC section. See section 8.2.6Saturation Table Generation - LET Functionsand Lomeland et al.232\n Lomeland F., Ebeltoft E. and Thomas W.H., 2005. A New Versatile Relative Permeability Correlation. Paper SCA2005-32 presented at the International Symposium of the Society of Core Analysts held in Toronto, Canada, 21-25 August, 2005.,233\n Lomeland F. and Ebeltoft E., 2008. A New Versatile Capillary Pressure Correlation. Paper SCA2008-08 presented at the International Symposium of the Society of Core Analysts held in Abu Dhabi, UAE, 29 Oct. – 2 Nov., 2008. 234\n Lomeland F., Hasanov B., Ebeltoft E. and Berge M., 2012. A Versatile Representation of Up-scaled Relative Permeability for Field Applications. Paper SPE 154487-MS presented at the EAGE Annual Conferen...","parameters":[{"index":1,"name":"SGL","description":"SGL is a real positive number less than one that defines the connate gas saturation, that is smallest gas saturation in the LET function.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0,0","value_type":"DOUBLE","dimension":"1"},{"index":2,"name":"SGCR","description":"SGCR is a real positive number greater than or equal to SGL and less than one, that defines the critical gas saturation, that is the largest gas saturation for which the gas relative permeability is zero.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0,0","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"LGAS","description":"LGAS is a real positive number that defines the LET Lower empirical parameter Lg for the gas phase with the associated oil phase in the LET relative permeability equation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0","value_type":"DOUBLE","dimension":"1"},{"index":4,"name":"EGAS","description":"EGAS is a real positive number that defines the LET Elevation empirical parameter Eg for the gas phase with the associated oil phase in the LET relative permeability equation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0","value_type":"DOUBLE","dimension":"1"},{"index":5,"name":"TGAS","description":"TGAS is a real positive number that defines the LET Top empirical parameter Tg for the gas phase with the associated oil phase in the LET relative permeability equation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0","value_type":"DOUBLE","dimension":"1"},{"index":6,"name":"KRTGAS","description":"KRTGAS is a real positive number less than one, that defines the relative permeability of gas at the maximum gas saturation Krgt in the LET relative permeability equation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0","value_type":"DOUBLE","dimension":"1"},{"index":7,"name":"SORG","description":"SORG is a real positive number less than one that defines the residual oil saturation in a gas-oil system in the LET equations.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0,0","value_type":"DOUBLE","dimension":"1"},{"index":8,"name":"SOGCR","description":"SOGCR is a real positive number less than one that defines critical oil-in-gas saturation, that is the largest oil saturation for which the oil relative permeability is zero in a gas-oil system.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0,0","value_type":"DOUBLE","dimension":"1"},{"index":9,"name":"LOIL","description":"LOIL is a real positive number that defines the LET Lower empirical parameter Lo for the oil phase with the associated gas phase in the LET relative permeability equation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0","value_type":"DOUBLE","dimension":"1"},{"index":10,"name":"EOIL","description":"EOIL is a real positive number that defines the LET Elevation empirical parameter Eo for the oil phase with the associated gas phase in the LET relative permeability equation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0","value_type":"DOUBLE","dimension":"1"},{"index":11,"name":"TOIL","description":"TOIL is a real positive number that defines the LET Top empirical parameter To for the oil phase with the associated gas phase in the LET relative permeability equation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0","value_type":"DOUBLE","dimension":"1"},{"index":12,"name":"KRTOIL","description":"KRTOIL is a real positive number less than or equal to one, that defines the relative permeability of oil at the residual oil saturation, Krot in the LET relative permeability equation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0","value_type":"DOUBLE","dimension":"1"},{"index":13,"name":"LPC","description":"LPC is a real positive number that defines the gas-oil LET Lower empirical parameter L in the LET capillary pressure equation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0","value_type":"DOUBLE","dimension":"1"},{"index":14,"name":"EPC","description":"EPC is a real positive number that defines the gas-oil LET Elevation empirical parameter E in the LET capillary pressure equation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0","value_type":"DOUBLE","dimension":"1"},{"index":15,"name":"TPC","description":"TPC is a real positive number that defines the gas-oil LET Top empirical parameter T in the LET capillary pressure equation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0","value_type":"DOUBLE","dimension":"1"},{"index":16,"name":"PCIR","description":"PCIR is a real positive number that defines the gas-oil capillary pressure at connate water saturation (SWL) in the LET capillary pressure equations.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"0,0","value_type":"DOUBLE","dimension":"Pressure"},{"index":17,"name":"PCIT","description":"PCIT is a real positive number that defines the gas-oil threshold capillary pressure at the maximum water saturation in the LET capillary pressure equations.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"0,0","value_type":"DOUBLE","dimension":"Pressure"}],"example":"The following example uses the SGOFLET keyword to define two relative gas-oil relative permeability tables, based on NTSFUN equals two on the TABDIMS keyword in the RUNSPEC section.\n--\n-- SGOFLET – GAS-OIL LET REL. PERMEABILITY FUNCTIONS (OPM FLOW KEYWORD)\n--\nSGOFLET\n-- SGL SGCR L-GAS E-GAS T-GAS KRT-GAS\n-- SOR SOGCR L-OIL E-OIL T-OIL KRT-OIL\n-- L-PC E-PC T-PC PCIR PCIT\n-- ------- ------ ------- ------- ------- -------\n0.00000 0.0000 1.00000 1.00000 1.00000 1.00000\n0.00000 0.0000 1.00000 1.00000 1.00000 1.00000\n1* 1* 1* 1* 1* / TABLE NO. 01\n0.00000 0.0000 1.00000 1.00000 1.00000 1.00000\n0.00000 0.0000 1.00000 1.00000 1.00000 1.00000\n1* 1* 1* 1* 1* / TABLE NO. 02\nHere the SGOFLET keyword parameters are all set to their default values.\n| Note This is an OPM Flow specific keyword and will therefore cause an error in the commercial simulator. |\n|----------------------------------------------------------------------------------------------------------|\n| Note All the LET parameters are dependent on the flooding event and flooding cycle, and thus are expected vary as such. To be clear, the values of SGCR, Lg, Lo etc. should be different for each flooding cycle. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":17,"size_kind":"fixed"},"SGU":{"name":"SGU","sections":["PROPS"],"supported":null,"summary":"SGU defines the maximum gas saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE keyword in the RUNSPEC section. The maximum gas saturation is defined as the maximum gas saturation in a two-phase gas relative permeability table.","parameters":[{"index":1,"name":"SGU","description":"SGU is an array of real numbers assigning the maximum gas saturation values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.70","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT SGU DATA FOR ALL CELLS\n-- (FOR NX x NY x NZ = 300)\n--\nSGU\n300*0.700 /\nThe above example defines a constant connate gas saturation of 0.70 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"SGWFLET":{"name":"SGWFLET","sections":["PROPS"],"supported":null,"summary":"SWGFLET defines the relative permeability and capillary pressure parameters for the water-gas LET family of models. Both the gas and water phases should be made active in the model via the GAS and WATER keywords in the RUNSPEC section. This keyword should only be used in two-phase models containing the gas and water phases only, that is the oil phase must be absent. See section 8.2.6Saturation Table Generation - LET Functionsand Lomeland et al.237\n Lomeland F., Ebeltoft E. and Thomas W.H., 2005. A New Versatile Relative Permeability Correlation. Paper SCA2005-32 presented at the International Symposium of the Society of Core Analysts held in Toronto, Canada, 21-25 August, 2005.,238\n Lomeland F. and Ebeltoft E., 2008. A New Versatile Capillary Pressure Correlation. Paper SCA2008-08 presented at the International Symposium of the Society of Core Analysts held in Abu Dhabi, UAE, 29 Oct. – 2 Nov., 2008. 239\n Lomeland F., Hasanov B., Ebeltoft E. and Berge M., 2012. A Ve...","parameters":[{"index":1,"name":"SGL","description":"SGL is a real positive number less than one that defines the connate gas saturation, that is smallest gas saturation in the LET function.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0,0"},{"index":2,"name":"SGCR","description":"SGCR is a real positive number greater than or equal to SGL and less than one, that defines the critical gas saturation, that is the largest gas saturation for which the gas relative permeability is zero.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0,0"},{"index":3,"name":"LGAS","description":"LGAS is a real positive number that defines the LET Lower empirical parameter Lg for the gas phase with the associated water phase in the LET relative permeability equations.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0"},{"index":4,"name":"EGAS","description":"EGAS is a real positive number that defines the LET Elevation empirical parameter Eg for the gas phase with the associated water phase in the LET relative permeability equations.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0"},{"index":5,"name":"TGAS","description":"TGAS is a real positive number that defines the LET Top empirical parameter Tg for the gas phase with the associated water phase in the LET relative permeability equations.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0"},{"index":6,"name":"KRTGAS","description":"KRTGAS is a real positive number less than one, that defines the relative permeability of gas at the maximum gas saturation Krgt in the LET relative permeability equations.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0"},{"index":7,"name":"SWL","description":"SWL is a real positive number less than one, that defines the connate water saturation, that is the smallest water saturation in the LET function.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0,0"},{"index":8,"name":"SWCR","description":"SWCR is a real positive number greater than or equal to SWL and less than one, that defines the critical water saturation, that is the largest water saturation for which the water relative permeability is zero, Swirr in equations.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0,0"},{"index":9,"name":"LWAT","description":"LWAT is a real positive number that defines the LET Lower empirical parameter Lw for the water phase with the associated gas phase in the LET relative permeability equations.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0"},{"index":10,"name":"EWAT","description":"EWAT is a real positive number that defines the LET Elevation empirical parameter Ew for the water phase with the associated gas phase in the LET relative permeability equations.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0"},{"index":11,"name":"TWAT","description":"TWAT is a real positive number that defines the LET Top empirical parameter Tw for the water phase with the associated gas phase in the LET relative permeability equations.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0"},{"index":12,"name":"KRTWAT","description":"KRTWAT is a real positive number less than one, that defines the relative permeability of water at the maximum water saturation (normally the maximum water saturation is one) Krwt in the LET relative permeability equations.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0"},{"index":13,"name":"LPC","description":"LPC is a real positive number that defines the gas-water LET Lower empirical parameter L in the LET capillary pressure equation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0"},{"index":14,"name":"EPC","description":"EPC is a real positive number that defines the gas-water LET Elevation empirical parameter E in the LET capillary pressure equation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0"},{"index":15,"name":"TPC","description":"TPC is a real positive number that defines the gas-water LET empirical parameter T in the LET capillary pressure equation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0"},{"index":16,"name":"PCIR","description":"PCIR is a real positive number that defines the gas-water capillary pressure at connate water saturation (SWL) in the LET capillary pressure equations.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"0,0"},{"index":17,"name":"PCIT","description":"PCIT is a real positive number that defines the gas-water threshold capillary pressure at the maximum water saturation in the LET capillary pressure equations.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"0,0"}],"example":"The following example uses the SWGFLET keyword to define two relative gas-water relative permeability tables, based on NTSFUN equals two on the TABDIMS keyword in the RUNSPEC section.\n--\n-- SGWFLET – GAS-WATER LET REL. PERMEABILITY FUNCTIONS (OPM FLOW KEYWORD)\n--\nSGWFLET\n-- SGL SGCR L-GAS E-GAS T-GAS KRT-GAS\n-- SWL SWCR L-WAT E-WAT T-WAT KRT-WAT\n-- L-PC E-PC T-PC PCIR PCIT\n-- ------- ------ ------- ------- ------- -------\n0.00000 0.0000 1.00000 1.00000 1.00000 1.00000\n0.00000 0.0000 1.00000 1.00000 1.00000 1.00000\n1* 1* 1* 1* 1* / TABLE NO. 01\n0.00000 0.0000 1.00000 1.00000 1.00000 1.00000\n0.00000 0.0000 1.00000 1.00000 1.00000 1.00000\n1* 1* 1* 1* 1* / TABLE NO. 02\nHere the SGWFLET keyword parameters are all set to their default values.\n| Note This is an OPM Flow specific keyword and will therefore cause an error in the commercial simulator. |\n|----------------------------------------------------------------------------------------------------------|\n| Note All the LET parameters are dependent on the flooding event and flooding cycle, and thus are expected vary as such. To be clear, the values of SWCR, Lg, Lw etc. should be different for each flooding cycle. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|"},"SGWFN":{"name":"SGWFN","sections":["PROPS"],"supported":null,"summary":"The SGWFN keyword defines the gas and water relative permeability and gas-water capillary pressure data versus gas saturation tables for when gas and water are present in the input deck. This keyword should only be used if gas and water are present in the run.","parameters":[{"index":1,"name":"SGAS","description":"A columnar vector of real monotonically increasing down the column values starting from zero and terminating at one, that defines the gas saturation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":["1","1","1","Pressure"]},{"index":2,"name":"KRG","description":"A columnar vector of real values that are either equal or increasing down the column and that are greater than or equal to zero and less than or equal to one that defines the gas relative permeability. Note that the first entry in the column must be zero.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":3,"name":"KRW","description":"A columnar vector of real values that are either equal or decreasing down the column and that are greater than or equal to zero and less than or equal to one that defines the water relative permeability with respect to gas saturation. The last value in the column should be zero.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":4,"name":"PCGW","description":"A columnar vector of real values that are either equal or increasing down the column that defines the gas-water relative capillary pressure.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"None"}],"example":"--\n-- GAS-WATER RELATIVE PERMEABILITY TABLES (SGWFN)\nSGWFN\n-- SG KRG KRW PCOW\n-- FRAC PSIA\n-- -------- -------- ------- -------\n0.000000 0.0000 0.9000 0.000000\n0.200000 0.0002 0.7664 0.000000\n0.699099 0.4973 0.0000 0.000000\n0.700000 1.0000 0.0000 0.000000 / TABLE NO. 01\n-- -------- -------- ------- -------\n0.000000 0.0000 0.9000 0.000000\n0.200000 0.0002 0.7664 0.000000\n0.245309 0.0004 0.7443 0.000000\n0.261989 0.0010 0.6907 0.000000\n0.303091 0.0044 0.5671 0.000000\n0.368269 0.0191 0.3962 0.000000\n0.435026 0.0519 0.2528 0.000000\n0.486387 0.0940 0.1643 0.000000\n0.522283 0.1339 0.1137 0.000000\n0.550683 0.1725 0.0803 0.000000\n0.575342 0.2115 0.0559 0.000000\n0.599076 0.2542 0.0367 0.000000\n0.621294 0.2991 0.0223 0.000000\n0.642171 0.3458 0.0120 0.000000\n0.658984 0.3868 0.0061 0.000000\n0.671123 0.4183 0.0030 0.000000\n0.679268 0.4403 0.0015 0.000000\n0.684963 0.4562 0.0008 0.000000\n0.688893 0.4674 0.0004 0.000000\n0.692025 0.4765 0.0002 0.000000\n0.694641 0.4841 0.0001 0.000000\n0.696976 0.4910 0.0000 0.000000\n0.699099 0.4973 0.0000 0.000000\n0.700000 1.0000 0.0000 0.000000 / TABLE NO. 02\nThe example defines two SGWFN tables for use when gas and water are present in the run.","size_kind":"fixed","variadic_record":true},"SHRATE":{"name":"SHRATE","sections":["PROPS"],"supported":null,"summary":"This keyword activates the logarithm-based polymer shear thinning/thickening option and defines the shear rate constant. This keyword can only be used in conjunction with the PLYSHLOG in the PROPS section","parameters":[{"index":1,"name":"SHRATE","description":"A positive real value that defines the shear rate constant.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"4.8","value_type":"DOUBLE","dimension":"1"}],"example":"The following example activates the logarithm-based polymer shear thinning/thickening option and defines the shear rate constants for a run with two PVT regions.\n--\n--ACTIVATE LOG-BASED POLYMER SHEAR THINNING-THICKENING OPTION\n--AND DEFINE THE SHEAR RATE CONSTANT\n--\nSHRATE\n--SHEAR RATE\n--CONSTANT\n4.8 /\n4.8 /","size_kind":"fixed","variadic_record":true},"SKPRPOLY":{"name":"SKPRPOLY","sections":["PROPS"],"supported":null,"summary":"This keyword, SKPRPOLY, describes the relationship of a water injection well's injected polymer skin pressure as a function of polymer throughput and water velocity, for the simulator's Polymer Molecular Weight Transport option. The table is a two dimensional table that relates the polymer throughput values and water velocity values to derive the resulting wellbore skin pressure of the injected polymer, which is then used to calculate the total wellbore skin pressure based on the polymer concentration.","parameters":[{"index":1,"name":"SKPRPNUM","description":"A positive integer value greater than zero and less than or equal to the NTSKPOLY variable, as defined on the PINTDIMS keyword in the RUNSPEC section, that defines the SKPRPOLY Polymer Molecular Weight Model polymer injection skin pressure table number.","units":{},"default":"None","record":1,"value_type":"INT"},{"index":2,"name":"POLCON","description":"A real positive value that the defines the reference polymer concentration for the table.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None","record":1,"value_type":"DOUBLE","dimension":"Concentration"},{"index":1,"name":"THRUPUT","description":"A real positive monotonically increasing vector, that defines the polymer throughput values. The first entry should be zero to define a no throughput data set, and each vector record should be on a separate line terminated by a “/”.","units":{"field":"feet3/feet2","metric":"m3/m2","laboratory":"cm3/cm2"},"default":"None","record":2,"value_type":"DOUBLE","dimension":"Length"},{"index":1,"name":"VELOCITY","description":"A real positive monotonically increasing vector, that defines the polymer velocity values. The first entry should be zero to define a no velocity data set, and each vector record should be on a separate line terminated by a “/”.","units":{"field":"feet/day","metric":"m/day","laboratory":"cm/hour"},"default":"None","record":3,"value_type":"DOUBLE","dimension":"Length/Time"},{"index":1,"name":"PRESS","description":"A series of real positive vectors representing the wellbore skin pressure, for the given reference polymer concentration (POLCON), for all combinations of the polymer throughput values (THRUPUT) and velocity values (VELOCITY), organized as a series of vectors PRESS(THRUPUT, VELOCITY). Thus, the first vector represents the wellbore skin pressure of the first THRUPUT value and each entry in the vector is the corresponding wellbore skin pressure of the associated VELOCITY vector. Each vector should be on a separate line and should be terminated by a “/”. Thus, if THRUPUT has three entries and VELOCITY has four, then there should be three vectors, with each vector containing four elements representing wellbore skin pressure values, as a function of THRUPUT and VELOCITY.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","record":4,"value_type":"DOUBLE","dimension":"Pressure"}],"example":"Given NTSKPOLY equals two on the PINTDIMS keyword in the RUNSPEC section, then two SKPRPOLY tables are required to be entered:\n--\n-- POLYMER MOLECULAR WEIGHT MODEL POLYMER INJECTION SKIN TABLE\n-- (OPM FLOW PROPS KEYWORD)\n--\nSKPRPOLY\n-- TABLE POLYMER REF\n-- NO. CONCENTRATION\n1 2.00 /\n--\n-- THROUGHPUT VALUES\n--\n0.0 200.0 400.0 /\n--\n-- VELOCITY VALUES\n--\n0.0 50.0 80.0 100.0 /\n--\n-- PRESS SKIN VALUES\n--\n0.0 10.0 20.0 40.0 / PRESS(THRUPUT=1, VELOCITY=1 TO N)\n0.0 50.0 100.0 200.0 / PRESS(THRUPUT=2, VELOCITY=1 TO N)\n0.0 100.0 200.0 400.0 / PRESS(THRUPUT=3, VELOCITY=1 TO N)\n/\nSKPRPOLY\n-- TABLE POLYMER REF\n-- NO. CONCENTRATION\n2 2.0 /\n--\n-- THROUGHPUT VALUES\n--\n0.0 200.0 400.0 /\n--\n-- VELOCITY VALUES\n--\n0.0 30.0 50.0 100.0 /\n--\n-- PRESS SKIN VALUES\n--\n0.0 10.0 20.0 40.0 / PRESS(THRUPUT=1, VELOCITY=1 TO N)\n0.0 50.0 100.0 200.0 / PRESS(THRUPUT=2, VELOCITY=1 TO N)\n0.0 100.0 200.0 400.0 / PRESS(THRUPUT=3, VELOCITY=1 TO N)\n/\nAs mentioned previously, the SKPRPOLY keyword requires that the keyword itself must be repeated for each table, as is shown in the above example.\n| Note This is an OPM Flow specific keyword that employs an alternative polymer flood model based on a Polymer Molecular Weight Transport equation, that is not available in the commercial simulator. The model has been tested using metric units; however, using either field or laboratory units with the option should be considered experimental. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","records_meta":[{"expected_columns":2},{},{},{}],"size_kind":"list"},"SKPRWAT":{"name":"SKPRWAT","sections":["PROPS"],"supported":null,"summary":"This keyword, SKPRWAT, describes the relationship of a water injection well's injected water skin pressure as a function of water throughput and water velocity, for the simulator's Polymer Molecular Weight Transport option. The table is a two dimensional table that relates the water throughput values and water velocity values to derive the resulting wellbore skin pressure of the injected water, which is then used to calculate the total wellbore skin pressure based on the polymer concentration.","parameters":[{"index":1,"name":"SKPRWNUM","description":"A positive integer value greater than zero and less than or equal to the NTSKWAT variable, as defined on the PINTDIMS keyword in the RUNSPEC section, that defines the SKPRWAT Polymer Molecular Weight Model water injection skin pressure table number.","units":{},"default":"None","record":1,"value_type":"INT"},{"index":1,"name":"THRUPUT","description":"A real positive monotonically increasing vector, that defines the water throughput values. The first entry should be zero to define a no throughput data set, and each vector record should be on a separate line terminated by a “/”.","units":{"field":"feet3/feet2","metric":"m3/m2","laboratory":"cm3/cm2"},"default":"None","record":2,"value_type":"DOUBLE","dimension":"Length"},{"index":1,"name":"VELOCITY","description":"A real positive monotonically increasing vector, that defines the water velocity values. The first entry should be zero to define a no velocity data set, and each vector record should be on a separate line terminated by a “/”.","units":{"field":"feet/day","metric":"m/day","laboratory":"cm/hour"},"default":"None","record":3,"value_type":"DOUBLE","dimension":"Length/Time"},{"index":1,"name":"PRESS","description":"A series of real positive vectors representing the wellbore skin pressure, for all combinations of the water throughput values (THRUPUT) and velocity values (VELOCITY), organized as a series of vectors PRESS(THRUPUT, VELOCITY). Thus, the first vector represents the wellbore skin pressure of the first THRUPUT value and each entry in the vector is the corresponding wellbore skin pressure of the associated VELOCITY vector. Each vector should be on a separate line and should be terminated by a “/”. Thus, if THRUPUT has three entries and VELOCITY has four, then there should be three vectors, with each vector containing four elements representing wellbore skin pressure values, as a function of THRUPUT and VELOCITY.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","record":4,"value_type":"DOUBLE","dimension":"Pressure"}],"example":"Given NTSKWAT equals two on the PINTDIMS keyword in the RUNSPEC section, then two SKPRWAT tables are required to be entered:\n--\n-- POLYMER MOLECULAR WEIGHT MODEL WATER INJECTION SKIN TABLE\n-- (OPM FLOW PROPS KEYWORD)\n--\nSKPRWAT\n1 / TABLE NUMBER\n--\n-- THROUGHPUT VALUES\n--\n0.0 200.0 400.0 /\n--\n-- VELOCITY VALUES\n--\n0.0 50.0 70.0 100.0 /\n--\n-- PRESS SKIN VALUES\n--\n0.0 2.0 4.0 8.0 / PRESS(THRUPUT=1, VELOCITY=1 TO N)\n0.0 20.0 40.0 80.0 / PRESS(THRUPUT=2, VELOCITY=1 TO N)\n0.0 50.0 100.0 200.0 / PRESS(THRUPUT=3, VELOCITY=1 TO N)\n/\nSKPRWAT\n2 / TABLE NUMBER\n--\n-- THROUGHPUT VALUES\n--\n0.0 200.0 400.0 /\n--\n-- VELOCITY VALUES\n--\n0.0 30.0 50.0 100.0 /\n--\n-- PRESS SKIN VALUES\n--\n0.0 2.0 4.0 8.0 / PRESS(THRUPUT=1, VELOCITY=1 TO N)\n0.0 20.0 40.0 80.0 / PRESS(THRUPUT=2, VELOCITY=1 TO N)\n0.0 50.0 100.0 200.0 / PRESS(THRUPUT=3, VELOCITY=1 TO N)\n/\nAs mentioned previously, the SKPRWAT keyword requires that the keyword itself must be repeated for each table, as is shown in the above example.\n| Note This is an OPM Flow specific keyword that employs an alternative polymer flood model based on a Polymer Molecular Weight Transport equation, that is not available in the commercial simulator. The model has been tested using metric units; however, using either field or laboratory units with the option should be considered experimental. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","records_meta":[{"expected_columns":1},{},{},{}],"size_kind":"list"},"SKRO":{"name":"SKRO","sections":["PROPS"],"supported":false,"summary":"SKRO defines the scaling parameter for the surfactant oil relative permeability value at the connate water saturation (SWL), for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the Surfactant option must be enabled by either the SURFST or SURFSTES keywords in the RUNSPEC section.","parameters":[{"index":1,"name":"SKRO","description":"SKRO is an array of positive real numbers which are greater than zero and less than or equal to 1.0, that are the assigned scaling SKRO values for each cell in the model. Repeat counts may be used, for example 50*0.500.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"The example defines an input box for the whole grid and for layers one to three, for layer one SKRO is set equal to 0.850, for layer two SKRO equals 0.875, and for layer three SKRO equals 0.900.\n--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS (NX=100, NY=100)\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1* 1* 1* 1* 1 3 / DEFINE BOX AREA\n--\n-- SET SKRO VALUES FOR THREE LAYERS IN THE MODEL\n--\nSKRO\n1000*0.855 1000*0.875 1000.0.900 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX","size_kind":"array"},"SKRORG":{"name":"SKRORG","sections":["PROPS"],"supported":false,"summary":"SKRORG defines the scaling parameter for the surfactant relative permeability of oil at the critical gas saturation (SGCR), for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the Surfactant option must be enabled by either the SURFST or SURFSTES keywords in the RUNSPEC section.","parameters":[{"index":1,"name":"SKRORG","description":"SKRORG is an array of positive real numbers which are greater than zero and less than or equal to 1.0, that are the assigned scaling SKRORG values for each cell in the model. Repeat counts may be used, for example 50*0.850.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"The example uses the EQUALS keyword to set layer one SKRORG equal to 0.750, layer two SKRORG equals 0.775, and layer three SKRORG equals 0.800.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nSKRORG 0.7550 1* 1* 1* 1* 1 1 / SKRORG FOR LAYER 1\nSKRORG 0.7750 1* 1* 1* 1* 2 2 / SKRORG FOR LAYER 2\nSKRORG 0.8000 1* 1* 1* 1* 3 3 / SKRORG FOR LAYER 3\n/","size_kind":"array"},"SKRORW":{"name":"SKRORW","sections":["PROPS"],"supported":false,"summary":"SKRORW defines the scaling parameter for the surfactant relative permeability of oil at the critical water saturation (SWCR), for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the Surfactant option must be enabled by either the SURFST or SURFSTES keywords in the RUNSPEC section.","parameters":[{"index":1,"name":"SKRORW","description":"SKRORW is an array of positive real numbers which are greater than zero and less than or equal to 1.0, that are the assigned scaling SKRORW values for each cell in the model. Repeat counts may be used, for example 50*0.850","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"The example defines an input box for the whole grid and for layers one to three, for layer one SKRORW is set equal to 0.750, for layer two SKRORW equals 0.775, and for layer three SKRORW equals 0.800.\n--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS (NX=100, NY=100)\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1* 1* 1* 1* 1 3 / DEFINE BOX AREA\n--\n-- SET SKRORW VALUES FOR THREE LAYERS IN THE MODEL\n--\nSKRORW\n1000*0.755 1000*0.775 1000.0.800 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX","size_kind":"array"},"SKRW":{"name":"SKRW","sections":["PROPS"],"supported":false,"summary":"SKRW defines the scaling parameter at the maximum surfactant water relative permeability value (SWU), that is for Sw = 1.0, for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the Surfactant option must be enabled by either the SURFST or SURFSTES keywords in the RUNSPEC section.","parameters":[{"index":1,"name":"SKRW","description":"SKRW is an array of positive real numbers which are greater than zero and less than or equal to 1.0, that are the assigned scaling SKRW values for each cell in the model. Repeat counts may be used, for example 50*1.000.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"The example uses the EQUALS keyword to set SKRW for layer one equal to 0.850, layer two SKRW to 0.875, and layer three KRW to 0.900.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nSKRW 0.8550 1* 1* 1* 1* 1 1 / SKRW FOR LAYER 1\nSKRW 0.8750 1* 1* 1* 1* 2 2 / SKRW FOR LAYER 2\nSKRW 0.9000 1* 1* 1* 1* 3 3 / SKRW FOR LAYER 3\n/","size_kind":"array"},"SKRWR":{"name":"SKRWR","sections":["PROPS"],"supported":false,"summary":"SKRWR defines the scaling parameter at the critical oil to water saturation value (SOWCR), for the surfactant water relative permeability curve, for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword.In addition, the Surfactant option must be enabled by either the SURFST or SURFSTES keywords in the RUNSPEC section.","parameters":[{"index":1,"name":"SKRWR","description":"SKRWR is an array of positive real numbers which are greater than zero and less than or equal to 1.0, that are the assigned scaling SKRWR values for each cell in the model. Repeat counts may be used, for example 50*1.000.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"The first example defines an input box for the whole grid and for layers one to three, for layer one SKRWR is set equal to 0.750, for layer two SKRWR equals 0.775, and for layer three SKRWR equals 0.800.\n--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS (NX=100, NY=100)\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1* 1* 1* 1* 1 3 / DEFINE BOX AREA\n--\n-- SET SKRWR VALUES FOR THREE LAYERS IN THE MODEL\n--\nSKRWR\n1000*0.755 1000*0.775 1000.0.800 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX","size_kind":"array"},"SLGOF":{"name":"SLGOF","sections":["PROPS"],"supported":null,"summary":"The SLGOF keyword defines the oil and gas relative permeability and oil-gas capillary pressure versus liquid saturation tables for when oil and gas are present in the input deck. This keyword should only be used if both oil and gas are present in the run.","parameters":[{"index":1,"name":"SLIQ","description":"A columnar vector of real monotonically increasing down the column values starting from zero and terminating at one, that defines the liquid saturation, that is the connate water saturation (SWL) plus the oil saturation. The first entry should correspond to residual liquid, that is Swc + Sorg and the last entry should be 1.0 to correspond to a gas saturation of zero.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":["1","1","1","Pressure"]},{"index":2,"name":"KRG","description":"A columnar vector of real values that are either equal or decreasing down the column and that are greater than or equal to zero and less than or equal to one that defines the gas relative permeability..","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":3,"name":"KRO","description":"A columnar vector of real values that are either equal or increasing down the column and that are greater than or equal to zero and less than or equal to one that defines the oil relative permeability with respect to gas and connate water saturation. When water is active in the run, the last entry the column, that is at krog(Sg = 0), must be the same as the first entry in the corresponding SWOF table, that is at krow(So = 1 - Swco). The first value in the column should be zero.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":4,"name":"PCOG","description":"A columnar vector of real values that are either equal or decreasing down the column that defines the oil-gas relative capillary pressure.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"None"}],"example":"--\n-- GAS-OIL RELATIVE PERMEABILITY TABLES (SLGOF)\nSLGOF\n-- SLIQ KRG KROG PCOG\n-- FRAC PSIA\n-- ------- -------- ------- -------\n0.30060 0.55000 0.0000 0.0000\n0.31480 0.42500 0.2848 0.0000\n0.32910 0.35000 0.3091 0.0000\n0.34330 0.27500 0.4333 0.0000\n0.35760 0.25000 0.5576 0.0000\n0.37180 0.22500 0.5818 0.0000\n0.38610 0.20000 0.6061 0.0000\n0.40030 0.17500 0.6303 0.0000\n0.41450 0.15000 0.6545 0.0000\n0.42880 0.12500 0.6788 0.0000\n0.44300 0.10000 0.7030 0.0000\n0.45730 0.07500 0.7273 0.0000\n0.47150 0.05000 0.7515 0.0000\n0.48580 0.02500 0.7758 0.0000\n0.50000 0.00000 0.8000 0.0000\n0.80000 0.00000 0.9000 0.0000 / TABLE No. 01\n-- ------- -------- ------- -------\n0.30060 0.55000 0.0000 0.0000\n0.31480 0.42500 0.2848 0.0000\n0.32910 0.35000 0.3091 0.0000\n0.34330 0.27500 0.4333 0.0000\n0.35760 0.25000 0.5576 0.0000\n0.37180 0.22500 0.5818 0.0000\n0.38610 0.20000 0.6061 0.0000\n0.40030 0.17500 0.6303 0.0000\n0.41450 0.15000 0.6545 0.0000\n0.42880 0.12500 0.6788 0.0000\n0.44300 0.10000 0.7030 0.0000\n0.45730 0.07500 0.7273 0.0000\n0.47150 0.05000 0.7515 0.0000\n0.48580 0.02500 0.7758 0.0000\n0.50000 0.00000 0.8000 0.0000\n0.80000 0.00000 0.9000 0.0000 / TABLE No. 02\nThe example defines two SLGOF tables for use when oil, gas and water are present in the run.","size_kind":"fixed","variadic_record":true},"SOCRS":{"name":"SOCRS","sections":["PROPS"],"supported":false,"summary":"SOCRS defines the miscible critical oil saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE keyword in the RUNSPEC section. The critical oil saturation with respect to water is defined as the maximum oil saturation for which the oil relative permeability is zero in a two-phase oil-water relative permeability table. The keyword is used with the Surfactant model to re-scale the surfactant relative permeability saturation tables allocated to a grid block by the by the SURFNUM keyword in the REGIONS section.","parameters":[{"index":1,"name":"SOCRS","description":"SOCRS is an array of real numbers assigning the critical oil saturation with respect to water values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.30","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT SOCRS DATA FOR ALL CELLS\n-- (FOR NX x NY x NZ = 300)\n--\nSOCRS\n300*0.200 /\nThe above example defines a constant critical oil saturation of 0.20 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"SOF2":{"name":"SOF2","sections":["PROPS"],"supported":null,"summary":"The SOF2 keyword defines the oil relative permeability versus oil saturation tables for when oil and gas or oil and water are present in the input deck. The keyword is also used to define the relative permeability of the miscible hydrocarbon phase in SOLVENT runs. This keyword should only be used if oil is present in the run.","parameters":[{"index":1,"name":"SOIL","description":"A columnar vector of real monotonically increasing down the column values starting from zero and terminating at one, that defines the oil or the hydrocarbon solvent saturation. For two phase runs the oil saturation should be entered and for when the SOLVENT option has been activated in the RUNSPEC section the total hydrocarbon phase (including the solvent) should be entered, that is SOIL = So + Sg + Ss.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":["1","1"]},{"index":3,"name":"KRO","description":"A columnar vector of real values that are either equal or increasing down the column and that are greater than or equal to zero and less than or equal to one that defines the oil relative permeability with respect to gas and connate water saturation. For two phase runs the oil relative permeability should be entered and for when the SOLVENT option has been activated in the RUNSPEC section the relative permeability of the miscible hydrocarbon phase with respect to water. The last value in the column should be zero.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- OIL RELATIVE PERMEABILITY TABLES (SOF2)\n--\nSOF2\n-- SOIL KRO\n-- FRAC FRAC\n-- -------- --------\n0.00 0.000000\n0.05 1.197e-5\n0.10 0.000191\n0.15 0.000969\n0.20 0.003065\n0.25 0.007483\n0.30 0.015517\n0.35 0.028747\n0.40 0.049041\n0.45 0.078555\n0.50 0.119730\n0.55 0.175297\n0.60 0.248272\n0.65 0.341961\n0.70 0.459956\n0.75 0.606134\n0.80 0.784664\n0.85 1.000000 / TABLE NO. 01\n-- -------- --------\n0.00 0.000000\n0.05 1.197e-5\n0.10 0.000191\n0.15 0.000969\n0.20 0.003065\n0.25 0.007483\n0.30 0.015517\n0.35 0.028747\n0.40 0.049041\n0.45 0.078555\n0.50 0.119730\n0.55 0.175297\n0.60 0.248272\n0.65 0.341961\n0.70 0.459956\n0.75 0.606134\n0.80 0.784664\n0.85 1.000000 / TABLE NO. 02\nThe example defines two SOF2 tables for when oil and gas or oil and water are present in the input deck.","size_kind":"fixed","variadic_record":true},"SOF3":{"name":"SOF3","sections":["PROPS"],"supported":null,"summary":"The SOF3 keyword defines the oil relative permeability versus oil saturation tables for when oil, gas and water are present in the input deck. The keyword should only be used if oil, gas and water are present in the input deck.","parameters":[{"index":1,"name":"SOIL","description":"A columnar vector of real monotonically increasing down the column values starting from zero and terminating at one, that defines the oil or the hydrocarbon solvent saturation. The final entry should be at the connate water saturation, that is 1- Swc.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":["1","1","1"]},{"index":3,"name":"KROW","description":"A columnar vector of real values that are either equal or increasing down the column and that are greater than or equal to zero and less than or equal to one that defines the oil relative permeability with respect to oil and water saturation. The first value in the column should be zero.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":4,"name":"KROG","description":"A columnar vector of real values that are either equal or increasing down the column and that are greater than or equal to zero and less than or equal to one that defines the oil relative permeability with respect to oil, gas and connate water saturation. The first value in the column should be zero.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- OIL RELATIVE PERMEABILITY TABLES (SOF3)\n--\nSOF3\n-- SOIL KRO KROG\n-- FRAC FRAC FRAC\n-- -------- -------- --------\n0.00 0.000000 0.00000\n0.05 1.197e-5 0.00000\n0.10 0.000191 0.00000\n0.15 0.000969 0.00000\n0.20 0.003065 0.00000\n0.25 0.007483 0.00000\n0.30 0.015517 0.05932\n0.35 0.028747 0.13158\n0.40 0.049041 0.21082\n0.45 0.078555 0.29960\n0.50 0.119730 0.40095\n0.55 0.175297 0.51818\n0.60 0.248272 0.65476\n0.65 0.341961 0.81420\n0.70 0.459956 1.00000\n0.75 0.606134 1.00000\n0.80 0.784664 1.00000\n0.85 1.000000 1.00000 / TABLE NO. 1\n-- -------- -------- --------\n0.00 0.000000 0.00000\n0.05 1.197e-5 0.00000\n0.10 0.000191 0.00000\n0.15 0.000969 0.00000\n0.20 0.003065 0.00000\n0.25 0.007483 0.00000\n0.30 0.015517 0.05932\n0.35 0.028747 0.13158\n0.40 0.049041 0.21082\n0.45 0.078555 0.29960\n0.50 0.119730 0.40095\n0.55 0.175297 0.51818\n0.60 0.248272 0.65476\n0.65 0.341961 0.81420\n0.70 0.459956 1.00000\n0.75 0.606134 1.00000\n0.80 0.784664 1.00000\n0.85 1.000000 1.00000 / TABLE NO. 2\nThe example defines two SOF3 tables for when oil, gas and water are present in the input deck.","size_kind":"fixed","variadic_record":true},"SOF32D":{"name":"SOF32D","sections":["PROPS"],"supported":false,"summary":"The SOF32D keyword defines the three phase oil relative permeability versus water and gas saturation tables for when oil, gas and water are present in the input deck. The keyword should only be used if oil, gas and water are present in the input deck. Normally the simulator calculates the three-phase oil relative permeabilities based on the entered two phase tables of water-oil and gas-oil, combined with the STONE1 and STONE2 keywords in the PROPS section that determine the method used to generate the thee phase oil relative permeability curves. SOF32D allows for the direct input of the three phase tables, as such the STONE1 and STONE2 keywords should not be entered if SOF32D is used in the input deck.","parameters":[{"index":1,"name":"SWAT","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1","record":1},{"index":1,"name":"SGAS","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1","record":2},{"index":2,"name":"KRO","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1","record":2}],"example":"","records_meta":[{},{"expected_columns":2}],"size_kind":"list"},"SOGCR":{"name":"SOGCR","sections":["PROPS"],"supported":null,"summary":"SOGCR defines the critical oil saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE keyword in the RUNSPEC section. The critical oil saturation with respect to gas is defined as the maximum oil saturation for which the oil relative permeability is zero in a two-phase gas-oil relative permeability table. The keyword can be used with all grid types.","parameters":[{"index":1,"name":"SOGCR","description":"SOGCR is an array of real numbers assigning the critical oil saturation with respect to gas values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.30 dimensionless","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT SOGCR DATA FOR ALL CELLS\n-- (FOR NX x NY x NZ = 300)\n--\nSOGCR\n300*0.200 /\nThe above example defines a constant critical gas saturation of 0.20 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"SOMGAS":{"name":"SOMGAS","sections":["PROPS"],"supported":false,"summary":"This keyword defines the minimum oil saturation as a function of gas saturation for Stone’s242\n Stone, H. L. “Probability Model for Estimating Three-Phase Relative Permeability,” paper SPE 2116, Journal of Canadian Petroleum Technology (1973) 22, No. 2, 214-218. first three phase oil relative permeability model as modified by Aziz and Settari243\n Aziz, K. and Settari, A. Petroleum Reservoir Simulation, London, UK, Applied Science Publishers (1979), page 398.. If the STONE1 and STONE2 keywords are not present in the input deck then the default three phase oil relative permeability model is employed. The SOMGAS and STONE1 keywords should only be used in three phase runs containing the oil, gas and water phases. The keyword is optional.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["1","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"SOMWAT":{"name":"SOMWAT","sections":["PROPS"],"supported":false,"summary":"This keyword defines the minimum oil saturation as a function of water saturation for Stone’s244\n Stone, H. L. “Probability Model for Estimating Three-Phase Relative Permeability,” paper SPE 2116, Journal of Canadian Petroleum Technology (1973) 22, No. 2, 214-218. first three phase oil relative permeability model as modified by Aziz and Settari245\n Aziz, K. and Settari, A. Petroleum Reservoir Simulation, London, UK, Applied Science Publishers (1979), page 398.. If the STONE1 and STONE2 keywords are not present in the input deck then the default three phase oil relative permeability model is employed. The SOMWAT and STONE1 keywords should only be used in three phase runs containing the oil, gas and water phases. The keyword is optional.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["1","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"SORWMIS":{"name":"SORWMIS","sections":["PROPS"],"supported":null,"summary":"SORWMIS defines the dependency between the miscible residual oil saturation and the water saturation, for when the MISCIBLE keyword in the RUNSPEC section has been activated. The keyword can only be used with the MISCIBLE option and for when the oil, water and gas phases are active in the model.","parameters":[{"index":1,"name":"SWAT","description":"A columnar vector of real monotonically increasing down the column values starting from zero and terminating at one, that defines the water saturation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":["1","1"]},{"index":2,"name":"SORMIS","description":"A columnar vector of real equal or increasing down the column values that are greater than or equal to zero and less than one, that define the corresponding miscible residual oil saturation for the corresponding water saturation SWAT.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- MISCIBLE RESIDUAL OIL VERSUS WATER SATURATION TABLE\n--\nSORWMIS\n-- SWAT SORWMIS\n-- FRAC FRAC\n-- ------- --------\n0.0000 0.0000\n0.2000 0.0000\n1.0000 0.0000 / TABLE NO. 01\n-- SWAT SORWMIS\n-- FRAC FRAC\n-- ------- --------\n0.0000 0.0000\n0.3000 0.1000\n0.7500 0.1500 / TABLE NO. 02\nThe above example defines two miscible residual oil versus water saturation tables assuming NTMISC equals two and NSMISC is greater than or equal to three on the MISCIBLE keyword in the RUNSPEC section.","size_kind":"fixed","variadic_record":true},"SOWCR":{"name":"SOWCR","sections":["PROPS"],"supported":null,"summary":"SOWCR defines the critical oil saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE keyword in the RUNSPEC section. The critical oil saturation with respect to water is defined as the maximum oil saturation for which the oil relative permeability is zero in a two-phase oil-water relative permeability table.","parameters":[{"index":1,"name":"SOWCR","description":"SOWCR is an array of real numbers assigning the critical oil saturation with respect to water values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.30","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT SOWCR DATA FOR ALL CELLS\n– (FOR NX x NY x NZ = 300)\n--\nSOWCR\n300*0.200 /\nThe above example defines a constant critical oil saturation of 0.20 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"SPECHEAT":{"name":"SPECHEAT","sections":["PROPS"],"supported":null,"summary":"SPECHEAT defines the specific heat of the oil, water and gas phases for various PVT regions in the model for when the THERMAL option has been activated in the RUNSPEC section. The number of SPECHEAT vector data sets is defined by the NTPVT parameter on the TABDIMS keyword in the RUNSPEC section and the allocation of the SPECHEAT data sets to different grid blocks in the model is done via the PVTNUM keyword in the REGIONS section.","parameters":[{"index":1,"name":"TEMP","description":"A columnar vector of real monotonically increasing down the column values that define the temperature for the corresponding oil, water and gas specific heat values.","units":{"field":"oF","metric":"oC","laboratory":"oC"},"default":"None","value_type":"DOUBLE","dimension":["Temperature","Energy/Mass*AbsoluteTemperature","Energy/Mass*AbsoluteTemperature","Energy/Mass*AbsoluteTemperature"]},{"index":2,"name":"OILSHEAT","description":"OILSHEAT is a columnar vector of positive real numbers defining the specific heat of oil at the corresponding temperature, TEMP.","units":{"field":"Btu/lb/oR","metric":"kJ/kg/K","laboratory":"J/gm/K"},"default":"None"},{"index":3,"name":"WATSHEAT","description":"WATSHEAT is a columnar vector of positive real numbers defining the specific heat of water at the corresponding temperature, TEMP.","units":{"field":"Btu/lb/oR","metric":"kJ/kg/K","laboratory":"J/gm/K"},"default":"None"},{"index":4,"name":"GASSHEAT","description":"GASHEAT is a columnar vector of positive real numbers defining the specific heat of gas at the corresponding temperature, TEMP.","units":{"field":"Btu/lb/oR","metric":"kJ/kg/K","laboratory":"J/gm/K"},"default":"None"}],"example":"The example below defines three fluid phases specific heat versus temperature tables assuming NTPVT equals three and NPPVT is greater than or equal to two on the TABDIMS keyword in the RUNSPEC section.\n--\n-- SPECIFIC HEAT OF OIL, WATER AND GAS TABLE\n--\nSPECHEAT\n-- TEMP SPECHEAT SPECHEAT SPECHEAT\n-- OIL WATER GAS\n-- ------- -------- -------- --------\n0.000 0.5000 1.5000 0.5000\n250.000 0.5000 1.5000 0.5000 / TABLE NO. 01\n-- TEMP SPECHEAT SPECHEAT SPECHEAT\n-- OIL WATER GAS\n-- ------- -------- -------- --------\n0.000 0.5500 1.5000 0.5000\n260.000 0.5500 1.5000 0.5000 / TABLE NO. 02\n-- TEMP SPECHEAT SPECHEAT SPECHEAT\n-- OIL WATER GAS\n-- ------- -------- -------- --------\n0.000 0.5500 1.5500 0.5000\n270.000 0.6000 1.5500 0.5000 / TABLE NO. 03\nThere is no terminating “/” for this keyword.","size_kind":"fixed","variadic_record":true},"SPECROCK":{"name":"SPECROCK","sections":["PROPS"],"supported":null,"summary":"SPECROCK defines the specific heat of the reservoir rock for various PVT regions in the model for when the THERMAL option has been activated in the RUNSPEC section. The number of SPECROCK vector data sets is defined by the NTSFUN parameter on the TABDIMS keyword in the RUNSPEC section and the allocation of the SPECROCK data sets to different grid blocks in the model is done via the SATNUM keyword in the REGIONS section.","parameters":[{"index":1,"name":"TEMP","description":"A columnar vector of real monotonically increasing down the column values that define the temperature for the corresponding rock specific heat values.","units":{"field":"oF","metric":"oC","laboratory":"oC"},"default":"None","value_type":"DOUBLE","dimension":["Temperature","Energy/Length*Length*Length*AbsoluteTemperature"]},{"index":2,"name":"ROCKHEAT","description":"ROCKHEAT is a columnar vector of positive real numbers defining the specific heat of the rock at the corresponding temperature, TEMP.","units":{"field":"Btu/ft3/oR","metric":"kJ/m3/K","laboratory":"J/cc/K"},"default":"None"}],"example":"The example below defines three rock specific heat versus temperature tables assuming NTSFUN equals three and NSSFUN is greater than or equal to two on the TABDIMS keyword in the RUNSPEC section.\n--\n-- SPECIFIC HEAT OF ROCK\n--\nSPECROCK\n-- TEMP SPECHEAT\n-- ROCK\n-- ------- --------\n0.000 20.000\n250.000 20.000 / TABLE NO. 01\n-- ------- --------\n0.000 21.000\n260.000 21.000 / TABLE NO. 02\n-- ------- --------\n0.000 23.000\n270.000 23.000 / TABLE NO. 03\nThere is no terminating “/” for this keyword.","size_kind":"fixed","variadic_record":true},"SSFN":{"name":"SSFN","sections":["PROPS"],"supported":null,"summary":"The SSFN keyword defines the miscible normalized relative permeability tables for when the SOLVENT option has been activated in the RUNSPEC section using the respective keyword. The SOLVENT keyword results in a four component model (oil, water and gas, plus a solvent). This keyword should only be used if the SOLVENT option has been activated.","parameters":[{"index":1,"name":"SGAS","description":"A columnar vector of real monotonically increasing down the column values starting from zero and terminating at one, that defines the gas plus solvent saturation ration which is defined as either: [S sub g over { left(S sub g ~+~ S sub s right) }]or or [S sub s over { left(S sub g ~+~ S sub s right) }] Where Sg is the gas saturation and Ss is the solvent saturation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":["1","1","1"]},{"index":2,"name":"KRGt","description":"A columnar vector of real values that are either equal or increasing down the column and that are greater than or equal to zero and less than or equal to one that defines the gas relative permeability. The resulting gas relative permeability is calculated from: [k sub rg ~=~ k sub rgt left( S sub g ~+~ S sub s Right) {k sub rg} sup t] where krgt is the data in this column and krgt is the gas relative permeability from the SGFN keyword.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":3,"name":"KRSt","description":"A columnar vector of real values that are either equal or increasing down the column and that are greater than or equal to zero and less than or equal to one that defines the solvent relative permeability. The resulting solvent relative permeability is calculated from: [k sub rs ~=~ k sub rgt left( S sub g ~+~ S sub s Right) {k sub rs} sup t] where krSt is the data in this column and krgt is the gas relative permeability from the SGFN keyword.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- SOLVENT RELATIVE PERMEABILITY TABLES\n--\nSSFN\n-- SGAS KRGT KRST\n-- FRAC\n-- -------- -------- --------\n0.0000 0.0000 0.0000\n1.0000 1.0000 1.0000 / TABLE NO. 01\n-- -------- -------- --------\n0.0000 0.0000 0.0000\n0.2000 0.2000 0.3000\n0.4000 0.3000 0.5000\n0.6000 0.4000 0.7000\n0.8000 0.5000 0.7500\n1.0000 1.0000 1.0000 / TABLE NO. 02\nThe above example defines two SSFN tables for use with the SOLVENT option.","size_kind":"fixed","variadic_record":true},"SSGCR":{"name":"SSGCR","sections":["PROPS"],"supported":false,"summary":"SSGCR defines the surfactant critical gas saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE keyword and the surfactant phase has been activated by the SURFACT keyword in the RUNSPEC section. The critical gas saturation is defined as the maximum gas saturation for which the gas relative permeability is zero in a two-phase relative permeability table. SSGCR is used to scale the surfactant oil relative permeability to gas data.","parameters":[{"index":1,"name":"SSGCR","description":"SSGCR is an array of real numbers assigning the surfactant critical gas saturation values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.03","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT SSGCR DATA FOR ALL CELLS\n-- (FOR NX x NY x NZ = 300)\n--\nSSGCR\n300*0.050 /\nThe above example defines a constant surfactant critical oil saturation with respect to gas of 0.05 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"SSGL":{"name":"SSGL","sections":["PROPS"],"supported":false,"summary":"SSGL defines the surfactant connate gas saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE keyword and the surfactant phase has been activated by the SURFACT keyword in the RUNSPEC section. The connate gas saturation is defined as the minimum gas saturation in a two-phase gas relative permeability table. SSGL is used to scale the surfactant oil and water relative permeability data.","parameters":[{"index":1,"name":"SSGL","description":"SSGL is an array of real numbers assigning the surfactant connate gas saturation values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.03","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT SSGL DATA FOR ALL CELLS\n-- (FOR NX x NY x NZ = 300)\n--\nSSGL\n300*0.030 /\nThe above example defines a constant surfactant connate gas saturation of 0.03 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"SSOGCR":{"name":"SSOGCR","sections":["PROPS"],"supported":false,"summary":"SSOGCR defines the surfactant critical oil saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE keyword and the surfactant phase has been activated by the SURFACT keyword in the RUNSPEC section. The critical oil saturation with respect to gas is defined as the maximum oil saturation for which the oil relative permeability is zero in a two-phase gas-oil relative permeability table. SSOGCR scales the surfactant oil relative permeability to gas data.","parameters":[{"index":1,"name":"SSOGCR","description":"SSOGCR is an array of real numbers assigning the surfactant critical oil saturation with respect to gas values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.30 dimensionless","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT SSOGCR DATA FOR ALL CELLS\n-- (FOR NX x NY x NZ = 300)\n--\nSSOGCR\n300*0.200 /\nThe above example defines a surfactant constant critical oil saturation with respect to gas of 0.20 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"SSOWCR":{"name":"SSOWCR","sections":["PROPS"],"supported":false,"summary":"SSOWCR defines the surfactant critical oil saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE keyword and the surfactant phase has been activated by the SURFACT keyword in the RUNSPEC section. The critical oil saturation with respect to water is defined as the maximum oil saturation for which the oil relative permeability is zero in a two-phase oil-water relative permeability table. SSOWCR scales the surfactant oil relative permeability to water data.","parameters":[{"index":1,"name":"SSOWCR","description":"SSOWCR is an array of real numbers assigning the surfactant critical oil saturation with respect to water values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.30","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT SSOWCR DATA FOR ALL CELLS\n-- (FOR NX x NY x NZ = 300)\n--\nSSOWCR\n300*0.200 /\nThe above example defines a constant critical oil saturation of 0.20 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"SSWCR":{"name":"SSWCR","sections":["PROPS"],"supported":false,"summary":"SSWCR defines the surfactant critical water saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE keyword and the surfactant phase has been activated by the SURFACT keyword in the RUNSPEC section. The critical water saturation is defined as the maximum water saturation for which the water relative permeability is zero in a two-phase relative permeability table. SSWCR scales the surfactant water relative permeability data.","parameters":[{"index":1,"name":"SSWCR","description":"SSWCR is an array of real numbers assigning the surfactant critical water saturation values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.20","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT SSWCR DATA FOR ALL CELLS\n-- (FOR NX x NY x NZ = 300)\n--\nSSWCR\n300*0.200 /\nThe above example defines a constant surfactant critical water saturation of 0.20 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"SSWL":{"name":"SSWL","sections":["PROPS"],"supported":false,"summary":"SSWL defines the surfactant connate water saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE keyword and the surfactant phase has been activated by the SURFACT keyword in the RUNSPEC section. The connate water saturation is defined as the minimum water saturation in a two-phase water relative permeability table. SSWL scales the surfactant oil relative permeability to water and gas data.","parameters":[{"index":1,"name":"SSWL","description":"SSWL is an array of real numbers assigning the connate water saturation values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.15","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT SSWL DATA FOR ALL CELLS\n-- (FOR NX x NY x NZ = 300)\n--\nSSWL\n300*0.150 /\nThe above example defines a constant surfactant connate water saturation of 0.15 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"SSWU":{"name":"SSWU","sections":["PROPS"],"supported":false,"summary":"SSWU defines the surfactant maximum water saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE keyword and the surfactant phase has been activated by the SURFACT keyword in the RUNSPEC section. The maximum water saturation is defined as the maximum water saturation in a two-phase water relative permeability table. SSWU scales the surfactant water relative permeability data.","parameters":[{"index":1,"name":"SSWU","description":"SSWU is an array of real numbers assigning the surfactant maximum water saturation values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.70","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT SSWU DATA FOR ALL CELLS\n-- (FOR NX x NY x NZ = 300)\n--\nSSWU\n300*0.700 /\nThe above example defines a constant surfactant connate gas saturation of 0.70 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"STOG":{"name":"STOG","sections":["PROPS"],"supported":false,"summary":"The STOG keyword defines capillary pressure oil-gas surface tension versus pressure tables used in adjusting the pressure independent capillary pressure vectors in the SGFN, SGOF or SLGOF saturation tables, entered by their respective keywords in the PROPS section. The SATOPTS keyword in the RUNSPEC section should state the SURFTENS character string to activate the Capillary Pressure Surface Tension Pressure Dependency option. If the STOG keyword is not supplied then no capillary pressure surface tension pressure scaling will occur and the capillary pressure values on the SGFN, SGOF or SLGOF saturation tables will be used directly.","parameters":[],"example":"","size_kind":"fixed"},"STONE":{"name":"STONE","sections":["PROPS"],"supported":null,"summary":"This keyword is an alias for STONE2 keyword that activates Stone’s246\n Stone, H. L. “Estimation of Three-Phase Relative Permeability and Residual Oil Data,” Journal of Canadian Petroleum Technology (1973) 12, No. 4, 53-61. second three phase oil relative permeability model as modified by Aziz and Settari247\n Aziz, K. and Settari, A. Petroleum Reservoir Simulation, London, UK, Applied Science Publishers (1979), page 398.. If the STONE, STONE1 and STONE2 keywords are not present in the input deck then the default three phase oil relative permeability model is employed. The STONE keyword should only be used in three phase runs containing the oil, gas and water phases.","parameters":[],"example":"--\n-- ACTIVATE STONE’S SECOND THREE PHASE RELATIVE PERMEABILITY MODEL\n--\nSTONE\nThe above example switches on the Modified Stone three phase relative permeability model.","size_kind":"none","size_count":0},"STONE1":{"name":"STONE1","sections":["PROPS"],"supported":null,"summary":"This keyword activates Stone’s248\n Stone, H. L. “Probability Model for Estimating Three-Phase Relative Permeability,” paper SPE 2116, Journal of Canadian Petroleum Technology (1973) 22, No. 2, 214-218. first three phase oil relative permeability model as modified by Aziz and Settari249\n Aziz, K. and Settari, A. Petroleum Reservoir Simulation, London, UK, Applied Science Publishers (1979), page 398.. If the STONE1 and STONE2 keywords are not present in the input deck then the default three phase oil relative permeability model is employed. The STONE1 keyword should only be used in three phase runs containing the oil, gas and water phases.","parameters":[],"example":"--\n-- ACTIVATE STONE’S FIRST THREE PHASE RELATIVE PERMEABILITY MODEL\n--\nSTONE1\nThe above example switches on the Modified Stone three phase relative permeability model.","size_kind":"none","size_count":0},"STONE1EX":{"name":"STONE1EX","sections":["PROPS"],"supported":null,"summary":"This keyword defines the exponent used in Stone’s250\n Stone, H. L. “Probability Model for Estimating Three-Phase Relative Permeability,” paper SPE 2116, Journal of Canadian Petroleum Technology (1973) 22, No. 2, 214-218. first three phase oil relative permeability model as modified by Aziz and Settari251\n Aziz, K. and Settari, A. Petroleum Reservoir Simulation, London, UK, Applied Science Publishers (1979), page 398.. The STONE1EX keyword should only be used in three phase runs containing the oil, gas and water phases and when the STONE1 keyword in the PROPS section has been used to activate Stone’s first three phase oil relative permeability model.","parameters":[{"index":1,"name":"STONEPAR1","description":"A real positive value that defines the exponent to be used in the Modified Stone first three phase oil relative permeability model.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":"1"}],"example":"Given NTSFUN equals five on the TABDIMS keyword in the RUNSPEC section, then:\n--\n-- DEFINE STONE'S FIRST THREE PHASE RELATIVE PERMEABILITY MODEL PARAMETER\n--\nSTONE1EX\n1.000 / SATURATION TABLE NO. 01\n1.000 / SATURATION TABLE NO. 02\n2.000 / SATURATION TABLE NO. 03\n1.000 / SATURATION TABLE NO. 04\n3.000 / SATURATION TABLE NO. 05\nDefines the exponents to be used in the Modified Stone first three phase oil relative permeability model, for each of the five saturation tables.","expected_columns":1,"size_kind":"fixed"},"STONE2":{"name":"STONE2","sections":["PROPS"],"supported":null,"summary":"This keyword activates Stone’s252\n Stone, H. L. “Estimation of Three-Phase Relative Permeability and Residual Oil Data,” Journal of Canadian Petroleum Technology (1973) 12, No. 4, 53-61. second three phase oil relative permeability model as modified by Aziz and Settari253\n Aziz, K. and Settari, A. Petroleum Reservoir Simulation, London, UK, Applied Science Publishers (1979), page 398.. If the STONE, STONE1 and STONE2 keywords are not present in the input deck then the default three phase oil relative permeability model is employed. The STONE2 keyword should only be used in three phase runs containing the oil, gas and water phases.","parameters":[],"example":"--\n-- ACTIVATE STONE’S SECOND THREE PHASE RELATIVE PERMEABILITY MODEL\n--\nSTONE2\nThe above example switches on the Modified Stone three phase relative permeability model.","size_kind":"none","size_count":0},"STOW":{"name":"STOW","sections":["PROPS"],"supported":false,"summary":"The STOW keyword defines capillary pressure oil-water surface tension versus pressure tables used in adjusting the pressure independent capillary pressure vectors in the SWFN or SWOF saturation tables, entered by their respective keywords in the PROPS section. The SATOPTS keyword in the RUNSPEC section should state the SURFTENS character string to activate the Capillary Pressure Surface Tension Pressure Dependency option. If the STOW keyword is not supplied then no capillary pressure surface tension pressure scaling will occur and the capillary pressure values on the SWFN or SWOF saturation tables will be used directly.","parameters":[],"example":"","size_kind":"fixed"},"STWG":{"name":"STWG","sections":["PROPS"],"supported":false,"summary":"The STWG keyword defines capillary pressure water-gas surface tension versus pressure tables for use with multi-segment wells. This facility has not been incorporated in OPM Flow’s multi-segment well implementation. Note that STWG is not required for Capillary Pressure Surface Tension Pressure Dependency option.","parameters":[],"example":"","size_kind":"fixed"},"SURFADDW":{"name":"SURFADDW","sections":["PROPS"],"supported":false,"summary":"SURFADDW defines tables of surfactant adsorbed concentration versus wettability fraction for when the SURFACTW keyword in the RUNSPEC section as been declared to activate the surfactant phase with changing wettability. The tables consists of columnar vectors of adsorbed surfactant concentration versus a wettability fraction that indicates the fraction of phase wettability. Here, a wettability fraction of zero indicates a 100% water wet rock resulting in the SURFWNUM allocated saturation tables being used, and a value of one meaning 100% oil wet rock, with the SATNUM allocated saturations tables being employed. Both the SURFWNUM and SATNUM keywords are in the REGIONS section.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["1","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"SURFADS":{"name":"SURFADS","sections":["PROPS"],"supported":false,"summary":"The SURFADS keyword defines the rock surfactant adsorption tables for when the surfactant option has been activated by the SURFACT keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"SURCON","description":"A columnar vector of real monotonically increasing down the column values that defines the surfactant concentration in the solution surrounding the rock. The first entry should be zero to define a no surfactant concentration.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None","value_type":"DOUBLE","dimension":["Concentration","1"]},{"index":2,"name":"SURRATIO","description":"A columnar vector of real increasing down the column values that defines the mass of adsorbed surfactant per unit mass of rock of the saturated concentration of surfactant adsorbed by the rock. The first entry should be zero to define a zero ratio of surfactant concentration.","units":{"field":"lb/lb","metric":"kg/kg","laboratory":"gm/gm"},"default":"None"}],"example":"--\n-- SURFACTANT ROCK ADSORPTION TABLE\n--\nSURFADS\n-- SURF SURF\n-- SURCON SURRATIO\n-- ------- --------\n0.0 0.00000\n2.0 0.00003\n4.0 0.00005\n6.0 0.00007\n8.0 0.00009\n10.0 0.00011\n12.0 0.00012\n14.0 0.00015 / TABLE NO. 01\n-- SURF SURF\n-- SURCON SURRATIO\n-- ------- --------\n0.0 0.00000\n3.0 0.00004\n5.0 0.00006\n7.0 0.00008\n8.0 0.00009\n10.0 0.00011 / TABLE NO. 02\nThe above example defines two surfactant rock adsorption tables assuming NTSFUN equals two and NSSFUN is greater than or equal to eight on the TABDIMS keyword in the RUNSPEC section.\nThere is no terminating “/” for this keyword.","size_kind":"fixed","variadic_record":true},"SURFCAPD":{"name":"SURFCAPD","sections":["PROPS"],"supported":false,"summary":"The SURFCAPD keyword defines the relationship between the log of the capillary number and the level of miscibility, for when the Surfactant option has been activated by the SURFACT keyword in the RUNSPEC section. A value of zero for the level of miscibility means fully immiscible conditions and consequently a value of one implies fully miscible conditions.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["1","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"SURFESAL":{"name":"SURFESAL","sections":["PROPS"],"supported":false,"summary":"This keyword, SURFESAL, defines the surfactant effective salinity coefficient as well as enabling the effective salinity calculation for surfactant adsorption. The keyword should only be used if the BRINE keyword has been declared to activate the brine phase, the ECLMC keyword to enable the Multi-Component Brine model, and the SURFACT keyword has been used to activate the surfact phase. All three keywords are in the RUNSPEC section.","parameters":[{"index":1,"name":"COEFF","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"}],"example":"","expected_columns":1,"size_kind":"fixed"},"SURFROCK":{"name":"SURFROCK","sections":["PROPS"],"supported":false,"summary":"The SURFROCK keyword defines rock properties for when the Surfactant option has been activated by the SURFACTANT keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"ADINDX","description":"A positive integer of 1 or 2 that defines the surfactant desorption option. then surfactant desorption may occur by retracing the surfactant adsorption isotherm when the local surfactant concentration in the solution decreases. then no surfactant desorption may occur.","units":{"field":"dimensionless 1","metric":"dimensionless 1","laboratory":"dimensionless 1"},"default":"Defined","value_type":"INT"},{"index":2,"name":"DENSITY","description":"A real value that defines the rock in-situ density, that is at reservoir conditions.","units":{"field":"lb/rtb","metric":"kg/rm3","laboratory":"gm/rcc"},"default":"None","value_type":"DOUBLE","dimension":"Mass/ReservoirVolume"}],"example":"--\n-- SURFACTANT-ROCK PROPERTIES\n--\nSURFROCK\n-- DESORP INSITU\n-- OPTN DENSITY\n-- ------ -------\n1 1800.0 / TABLE NO. 01\n2 1980.0 / TABLE NO. 02\n1 2005.0 / TABLE NO. 03\nThe above example defines three surfactant-rock tables, based on the NTSFUN variable on the TABDIMS keyword in the RUNSPEC section being equal to three.\nThere is no terminating “/” for this keyword.","expected_columns":2,"size_kind":"fixed"},"SURFST":{"name":"SURFST","sections":["PROPS"],"supported":false,"summary":"The SURFST keyword defines surfactant water-oil surface tension versus surfactant concentration in the water phase tables, used in adjusting the pressure independent capillary pressure vectors in the SWFN or SWOF saturation tables, entered by their respective keywords in the PROPS section. SURFST is also used to adjust the relative permeability curves on the aforementioned tables via the capillary number. The Surfactant option must have been activated by the SURFACTANT keyword in the RUNSPEC section to use this keyword and either this keyword or the SURFSTES keyword, also in the PROPS section, is obligatory in this case.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","size_kind":"fixed","variadic_record":true},"SURFSTES":{"name":"SURFSTES","sections":["PROPS"],"supported":false,"summary":"The SURFSTES keyword defines surfactant water-oil surface tension versus surfactant concentration in the water phase tables, used in adjusting the pressure independent capillary pressure vectors in the SWFN or SWOF saturation tables, entered by their respective keywords in the PROPS section. SURFSTES is also used to adjust the relative permeability curves on the aforementioned tables via the capillary number. The Surfactant option must have been activated by the SURFACTANT keyword in the RUNSPEC section to use this keyword and either this keyword or the SURFST keyword, also in the PROPS section, is obligatory in this case. In addition, the BRINE keyword in the RUNSPEC section must be activated and the ESSNODE keyword in the PROPS section must be used to define the salt concentration or the effective salinity.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","size_kind":"fixed","variadic_record":true},"SURFVISC":{"name":"SURFVISC","sections":["PROPS"],"supported":false,"summary":"SURFSVISC defines the surfactant viscosity relationship of solution water viscosity with respect to increasing surfactant concentration within a grid block. The surfactant option must be activated by the SURFACT keyword in the RUNSPEC section in order to use this keyword.","parameters":[{"index":1,"name":"SURFCON","description":"A columnar vector of real monotonically increasing down the column values that defines the surfactant concentration in the solution surrounding the rock. The first entry should be zero to define a no surfactant concentration.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None","value_type":"DOUBLE","dimension":["Concentration","Viscosity"]},{"index":2,"name":"SURFVISC","description":"A columnar vector of real positive values that defines the solution water viscosity of the solution for the given SURFCON entry at the reference pressure value, PRES, entered on the PVTW keyword in the PROPS section.","units":{"field":"cP","metric":"cP","laboratory":"cP"},"default":"None"}],"example":"--\n-- SURFACTANT SOLUTION WATER VISCOSITY TABLES\n--\nSURFVISC\n-- SURF VISCOSITY\n-- SURFCON SURFVISC\n-- -------- -----------\n0.0000 0.3500\n0.0100 0.3900\n0.0200 0.4200\n0.0300 0.4300 / TABLE NO. 01\n-- SURF VISCOSITY\n-- SURFCON VISFAC\n-- -------- ---------\n0.0000 1.000\n0.0003 10.000\n0.0005 20.000\n0.0007 40.000\n0.0009 45.000\n0.0011 55.000 / TABLE NO. 02\nThe example defines two surfactant viscosity scaling factor tables, based on the NTPVT variable on the TABDIMS keyword in the RUNSPEC section being equal to two and NPPVT variable on the same keyword being greater than or equal to six.","size_kind":"fixed","variadic_record":true},"SWATINIT":{"name":"SWATINIT","sections":["PROPS"],"supported":null,"summary":"SWATINIT defines the initial water saturation for all the cells in the model via an array. The keyword can be used with all grid types. SWATINIT is used to initialize the model by setting each grid block’s initial water saturation (“Sw”). If the array is present in the input deck, then OPM Flow will re-scale the water-oil capillary pressure curves entered via the SWFN saturation functions in the PROPS section, so that the resulting initialized Sw matches the values in the SWATINIT array.","parameters":[{"index":1,"name":"SWATINIT","description":"SWATINIT is an array of real positive numbers that are greater than or equal to zero and less than or equal to one, that define the initial water saturation values to each cell in the model. Repeat counts may be used, for example 3000*0.15","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK INITIAL SW DATA FOR ALL CELLS\n-- (BASED ON NX x NY x NZ = 300)\n--\nSWATINIT\n300*0.300 /\nThe above example defines a constant initial water saturation of 0.300 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"SWCR":{"name":"SWCR","sections":["PROPS"],"supported":null,"summary":"SWCR defines the critical water saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE keyword in the RUNSPEC section. The critical water saturation is defined as the maximum water saturation for which the water relative permeability is zero in a two-phase relative permeability table.","parameters":[{"index":1,"name":"SWCR","description":"SWCR is an array of real numbers assigning the critical water saturation values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.20","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT SWCR DATA FOR ALL CELLS\n-- (FOR NX x NY x NZ = 300)\n--\nSWCR\n300*0.200 /\nThe above example defines a constant critical water saturation of 0.20 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"SWF32D":{"name":"SWF32D","sections":["PROPS"],"supported":false,"summary":"The SWF32D keyword defines the three phase water relative permeability versus oil and gas saturation tables for when oil, gas and water are present in the input deck. The keyword should only be used if oil, gas and water are present in the input deck. Normally the simulator calculates the three-phase oil relative permeabilities based on the entered two phase tables of water-oil and gas-oil, combined with the STONE1 and STONE2 keywords in the PROPS section that determine the method used to generate the thee phase water relative permeability curves. SWF32D allows for the direct input of the three phase tables, as such the STONE1 and STONE2 keywords should not be entered if SWF32D is used in the input deck.","parameters":[{"index":1,"name":"SOIL","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1","record":1},{"index":1,"name":"SGAS","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1","record":2},{"index":2,"name":"KRW","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1","record":2}],"example":"","records_meta":[{},{"expected_columns":2}],"size_kind":"list"},"SWFN":{"name":"SWFN","sections":["PROPS"],"supported":null,"summary":"The SWFN keyword defines the water relative permeability and water-oil capillary pressure data versus water saturation tables for when water is present in the input deck. This keyword should only be used if water is present in the run.","parameters":[{"index":1,"name":"SWAT","description":"A columnar vector of real monotonically increasing down the column values starting from zero and terminating at one, that defines the water saturation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":["1","1","Pressure"]},{"index":2,"name":"KRW","description":"A columnar vector of real values that are either equal or increasing down the column and that are greater than or equal to zero and less than or equal to one that defines the water relative permeability with respect to gas saturation. The first value in the column should be zero.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":3,"name":"PCWO","description":"A columnar vector of real values that are either equal or increasing down the column that defines the water-oil relative capillary pressure. If the SWATINIT keyword has been used to initialize the model then columnar vector has to be strictly monotonically increasing.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"None"}],"example":"--\n-- WATER RELATIVE PERMEABILITY TABLES (SWFN)\n--\nSWFN\n-- SWAT KRW PCOW\n-- FRAC FRAC PSIA\n-- -------- -------- -------\n0.15 0.00000 0.0\n0.20 6.25e-6 0.0\n0.25 0.00010 0.0\n0.30 0.00050 0.0\n0.35 0.00160 0.0\n0.40 0.00390 0.0\n0.45 0.00810 0.0\n0.50 0.01500 0.0\n0.55 0.02560 0.0\n0.60 0.04100 0.0\n0.65 0.06250 0.0\n0.70 0.09150 0.0\n0.75 0.12960 0.0\n0.80 0.17850 0.0\n0.85 0.24010 0.0\n0.90 0.31640 0.0\n0.95 0.40960 0.0\n1.00 0.52200 0.0 / TABLE NO. 1\n-- -------- -------- -------\n0.15 0.00000 0.0\n0.20 6.25e-6 0.0\n0.25 0.00010 0.0\n0.30 0.00050 0.0\n0.35 0.00160 0.0\n0.40 0.00390 0.0\n0.45 0.00810 0.0\n0.50 0.01500 0.0\n0.55 0.02560 0.0\n0.60 0.04100 0.0\n0.65 0.06250 0.0\n0.70 0.09150 0.0\n0.75 0.12960 0.0\n0.80 0.17850 0.0\n0.85 0.24010 0.0\n0.90 0.31640 0.0\n0.95 0.40960 0.0\n1.00 0.52200 0.0 / TABLE NO. 2\nThe example defines two SWFN tables for use when water is present in the run.","size_kind":"fixed","variadic_record":true},"SWL":{"name":"SWL","sections":["PROPS"],"supported":null,"summary":"SWL defines the connate water saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE keyword in the RUNSPEC section. The connate water saturation is defined as the minimum water saturation in a two-phase water relative permeability table.","parameters":[{"index":1,"name":"SWL","description":"SWL is an array of real numbers assigning the connate water saturation values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.15","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT SWL DATA FOR ALL CELLS\n-- (FOR NX x NY x NZ = 300)\n--\nSWL\n300*0.150 /\nThe above example defines a constant connate water saturation of 0.15 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"SWLPC":{"name":"SWLPC","sections":["PROPS"],"supported":null,"summary":"SWLPC defines the connate water saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE keyword in the RUNSPEC section. The connate water saturation is defined as the minimum water saturation in a two-phase water relative permeability table. The keyword only applies the scaling to the drainage capillary pressures tables, unlike the SWL keyword that applies the scaling to both the capillary pressure and relative permeability tables. The keyword can be used with all grid types.","parameters":[{"index":1,"name":"SWLPC","description":"SWLPC is an array of real numbers assigning the connate water saturation values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. If SWLPC is omitted from the input deck the values will be defaulted to those on the SWL series of keywords. If the SWL series of keywords are missing from the input deck then the values are taken from the cell allocated capillary pressure table. Repeat counts may be used, for example 30*0.03","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from SGL or from the cell allocated capillary pressure table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT SWLPC DATA FOR ALL CELLS\n-- (FOR NX x NY x NZ = 300)\n--\nSWLPC\n300*0.150 /\nThe above example defines a constant connate water saturation of 0.15 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"SWOF":{"name":"SWOF","sections":["PROPS"],"supported":null,"summary":"The SWOF keyword defines the water and oil relative permeability and water-oil capillary pressure data versus water saturation tables for when water and oil are present in the input deck. This keyword should only be used if water and oil are present in the run.","parameters":[{"index":1,"name":"SWAT","description":"A columnar vector of real monotonically increasing down the column values starting from zero and terminating at one, that defines the water saturation. The first entry is the connate water saturation Swc and the last entry should be 1.0.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":["1","1","1","Pressure"]},{"index":2,"name":"KRW","description":"A columnar vector of real values that are either equal or increasing down the column and that are greater than or equal to zero and less than or equal to one that defines the water relative permeability with respect to gas saturation. The first value in the column should be zero.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":3,"name":"KRO","description":"A columnar vector of real values that are either equal or decreasing down the column and that are greater than or equal to zero and less than or equal to one that defines the oil relative permeability with respect to oil and water saturation. When gas is active in the run, the first entry the column, that is at krow(So = 1-Swc), must be the same as the first entry in the corresponding SGOF or SLGOF table, that is at krog(Sg = 0). The first value in the column should be one.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":4,"name":"PCWO","description":"A columnar vector of real values that are either equal or decreasing down the column that defines the water-oil relative capillary pressure. If the SWATINIT keyword has been used to initialize the model then columnar vector has to be strictly monotonically increasing.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"None"}],"example":"The following example is based on NTSFUN equals two on the TABDIMS keyword in the RUNSPEC section.\n--\n-- WATER-OIL RELATIVE PERMEABILITY TABLES (SWOF)\n--\nSWOF\n-- SWAT KRW KROW PCOW\n-- FRAC PSIA\n-- -------- -------- ------- -------\n0.200000 0.0000 0.9000 0.000000\n0.238616 0.0002 0.7664 0.000000\n0.245309 0.0004 0.7443 0.000000\n0.261989 0.0010 0.6907 0.000000\n0.303091 0.0044 0.5671 0.000000\n0.368269 0.0191 0.3962 0.000000\n0.435026 0.0519 0.2528 0.000000\n0.486387 0.0940 0.1643 0.000000\n0.550683 0.1725 0.0803 0.000000\n0.575342 0.2115 0.0559 0.000000\n0.599076 0.2542 0.0367 0.000000\n0.621294 0.2991 0.0223 0.000000\n0.642171 0.3458 0.0120 0.000000\n0.658984 0.3868 0.0061 0.000000\n0.671123 0.4183 0.0030 0.000000\n0.679268 0.4403 0.0015 0.000000\n0.684963 0.4562 0.0008 0.000000\n0.688893 0.4674 0.0004 0.000000\n0.692025 0.4765 0.0002 0.000000\n0.694641 0.4841 0.0001 0.000000\n0.696976 0.4910 0.0000 0.000000\n0.699099 0.4973 0.0000 0.000000\n0.700000 0.5000 0.0000 0.000000\n1.000000 0.9000 0.0000 0.000000 / TABLE NO. 01\n-- -------- -------- ------- -------\n0.200000 0.0000 0.9000 0.000000\n0.238616 0.0002 0.7664 0.000000\n0.245309 0.0004 0.7443 0.000000\n0.261989 0.0010 0.6907 0.000000\n0.303091 0.0044 0.5671 0.000000\n0.368269 0.0191 0.3962 0.000000\n0.435026 0.0519 0.2528 0.000000\n0.486387 0.0940 0.1643 0.000000\n0.550683 0.1725 0.0803 0.000000\n0.575342 0.2115 0.0559 0.000000\n0.599076 0.2542 0.0367 0.000000\n0.621294 0.2991 0.0223 0.000000\n0.642171 0.3458 0.0120 0.000000\n0.658984 0.3868 0.0061 0.000000\n0.671123 0.4183 0.0030 0.000000\n0.679268 0.4403 0.0015 0.000000\n0.684963 0.4562 0.0008 0.000000\n0.688893 0.4674 0.0004 0.000000\n0.692025 0.4765 0.0002 0.000000\n0.694641 0.4841 0.0001 0.000000\n0.696976 0.4910 0.0000 0.000000\n0.699099 0.4973 0.0000 0.000000\n0.700000 0.5000 0.0000 0.000000\n1.000000 0.9000 0.0000 0.000000 / TABLE NO. 01\nThe example defines two SWOF tables for use when water and oil are present in the run. In the tables the water-oil capillary pressure data has been set to zero.","size_kind":"fixed","variadic_record":true},"SWOFLET":{"name":"SWOFLET","sections":["PROPS"],"supported":null,"summary":"SWOFLET defines the relative permeability and capillary pressure parameters for the water-oil LET family of models. Both the oil and water phases should be made active in the model via the OIL and WATER keywords in the RUNSPEC section. See section 8.2.6Saturation Table Generation - LET Functionsand Lomeland et al.254\n Lomeland F., Ebeltoft E. and Thomas W.H., 2005. A New Versatile Relative Permeability Correlation. Paper SCA2005-32 presented at the International Symposium of the Society of Core Analysts held in Toronto, Canada, 21-25 August, 2005.,255\n Lomeland F. and Ebeltoft E., 2008. A New Versatile Capillary Pressure Correlation. Paper SCA2008-08 presented at the International Symposium of the Society of Core Analysts held in Abu Dhabi, UAE, 29 Oct. – 2 Nov., 2008. 256\n Lomeland F., Hasanov B., Ebeltoft E. and Berge M., 2012. A Versatile Representation of Up-scaled Relative Permeability for Field Applications. Paper SPE 154487-MS presented at the EAGE Annual Co...","parameters":[{"index":1,"name":"SWL","description":"SWL is a real positive number less than one, that defines the connate water saturation, that is the smallest water saturation in the LET function.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0,0","value_type":"DOUBLE","dimension":"1"},{"index":2,"name":"SWCR","description":"SWCR is a real positive number greater than or equal to SWL and less than one, that defines the critical water saturation, that is the largest water saturation for which the water relative permeability is zero, Swirr in equations.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0,0","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"LWAT","description":"LWAT is a real positive number that defines the LET Lower empirical parameter Lw for the water phase with the associated oil phase in the LET relative permeability equations.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0","value_type":"DOUBLE","dimension":"1"},{"index":4,"name":"EWAT","description":"EWAT is a real positive number that defines the LET Elevation empirical parameter Ew for the water phase with the associated oil phase in the LET relative permeability equations.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0","value_type":"DOUBLE","dimension":"1"},{"index":5,"name":"TWAT","description":"TWAT is a real positive number that defines the LET Top empirical parameter Tw for the water phase with the associated oil phase in the LET relative permeability equations.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0","value_type":"DOUBLE","dimension":"1"},{"index":6,"name":"KRTWAT","description":"KRTWAT is a real positive number less than one, that defines the relative permeability of water at the maximum water saturation (normally the maximum water saturation is one) Krwt in the LET relative permeability equations.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0","value_type":"DOUBLE","dimension":"1"},{"index":7,"name":"SORW","description":"SORW is a real positive number less than one that defines the residual oil saturation in an oil-water system in the LET equation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0,0","value_type":"DOUBLE","dimension":"1"},{"index":8,"name":"SOWCR","description":"SOWCR is a real positive number less than one that defines critical oil-in-water saturation, that is the largest oil saturation for which the oil relative permeability is zero in an oil-water system.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0,0","value_type":"DOUBLE","dimension":"1"},{"index":9,"name":"LOIL","description":"LOIL is a real positive number that defines the LET Lower empirical parameter Lo for the oil phase with the associated water phase in the LET relative permeability equationss","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0","value_type":"DOUBLE","dimension":"1"},{"index":10,"name":"EOIL","description":"EOIL is a real positive number that defines the LET Elevation empirical parameter Eo for the oil phase with the associated water phase in the LET relative permeability equations.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0","value_type":"DOUBLE","dimension":"1"},{"index":11,"name":"TOIL","description":"TOIL is a real positive number that defines the LET Top empirical parameter To for the oil phase with the associated water phase in the LET relative permeability equations.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0","value_type":"DOUBLE","dimension":"1"},{"index":12,"name":"KRTOIL","description":"KRTOIL is a real positive number less than or equal to one, that defines the relative permeability of oil at the residual oil saturation, Krot in the LET relative permeability equations.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0","value_type":"DOUBLE","dimension":"1"},{"index":13,"name":"LPC","description":"LPC is a real positive number that defines the water-oil LET Lower empirical parameter L in the LET capillary pressure equation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0","value_type":"DOUBLE","dimension":"1"},{"index":14,"name":"EPC","description":"EPC is a real positive number that defines the water-oil LET Elevation empirical parameter E in the LET capillary pressure equation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0","value_type":"DOUBLE","dimension":"1"},{"index":15,"name":"TPC","description":"TPC is a real positive number that defines the water-oil LET empirical parameter T in the LET capillary pressure equations.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0","value_type":"DOUBLE","dimension":"1"},{"index":16,"name":"PCIR","description":"PCIR is a real positive number that defines the water-oil capillary pressure at connate water saturation (SWL) in the LET capillary pressure equations.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"0,0","value_type":"DOUBLE","dimension":"Pressure"},{"index":17,"name":"PCIT","description":"PCIT is a real positive number that defines the water-oil threshold capillary pressure at the maximum water saturation in the LET capillary pressure equations.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"0,0","value_type":"DOUBLE","dimension":"Pressure"}],"example":"The following example uses the SWOFLET keyword to define two relative oi-water relative permeability tables, based on NTSFUN equals two on the TABDIMS keyword in the RUNSPEC section.\n--\n-- SWOFLET – WATER-OIL LET REL. PERMEABILITY FUNCTIONS (OPM FLOW KEYWORD)\n--\nSWOFLET\n-- SWL SWCR L-WAT E-WAT T-WAT KRT-WAT\n-- SOR SOWCR L-OIL E-OIL T-OIL KRT-OIL\n-- L-PC E-PC T-PC PCIR PCIT\n-- ------- ------ ------- ------- ------- -------\n0.00000 0.0000 1.00000 1.00000 1.00000 1.00000\n0.00000 0.0000 1.00000 1.00000 1.00000 1.00000\n1* 1* 1* 1* 1* / TABLE NO. 01\n0.00000 0.0000 1.00000 1.00000 1.00000 1.00000\n0.00000 0.0000 1.00000 1.00000 1.00000 1.00000\n1* 1* 1* 1* 1* / TABLE NO. 02\nHere the SWOFLET keyword parameters are all set to their default values.\n| Note This is an OPM Flow specific keyword and will therefore cause an error in the commercial simulator. |\n|----------------------------------------------------------------------------------------------------------|\n| Note All the LET parameters are dependent on the flooding event and flooding cycle, and thus are expected vary as such. To be clear, the values of SWCR, Lo, Lw etc. should be different for each flooding cycle. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":17,"size_kind":"fixed"},"SWU":{"name":"SWU","sections":["PROPS"],"supported":null,"summary":"SWU defines the maximum water saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE keyword in the RUNSPEC section. The maximum water saturation is defined as the maximum water saturation in a two-phase water relative permeability table.","parameters":[{"index":1,"name":"SWU","description":"SWU is an array of real numbers assigning the maximum water saturation values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.70","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT SWU DATA FOR ALL CELLS\n-- (FOR NX x NY x NZ = 300)\n--\nSWU\n300*0.700 /\nThe above example defines a constant connate gas saturation of 0.70 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"TCRIT":{"name":"TCRIT","sections":["PROPS"],"supported":false,"summary":"The TCRIT keyword defines the critical temperatures for each of the compositional components active in the model and for each equation of state. The keyword should only be used if the compositional mode has been requested using the COMPS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"TCRIT","description":"A series of real numbers that define the critical temperatures for each of the compositional components active in the model.","units":{"field":"°R","metric":"K","laboratory":"K"},"default":"None","value_type":"DOUBLE","dimension":"AbsoluteTemperature"}],"example":"The following example defines the critical temperatures for each component in a single three-component equation of state model.\n--\n-- Critical Temperatures\n--\nTCRIT\n547.4412 343.0152 665.802 /\nThe following example defines the critical temperatures for each component in two three-component equation of state models.\n--\n-- Critical Temperatures\n--\nTCRIT\n547.4412 343.0152 665.802 /\n547.4412 343.0152 665.802 /","size_kind":"fixed","variadic_record":true},"TEMPNODE":{"name":"TEMPNODE","sections":["PROPS"],"supported":false,"summary":"This keyword defines the reservoir temperature table used to calculate the polymer solution viscosity when the temperature option has been activated by the TEMP keyword in the RUNSPEC section in the commercial simulator. Naturally, the polymer option must also be activated by the POLYMER keyword in the RUNSPEC section in order to use this keyword.","parameters":[{"index":1,"name":"TABLE_DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Temperature"}],"example":"","expected_columns":1,"size_kind":"fixed"},"TEMPTVD":{"name":"TEMPTVD","sections":["PROPS"],"supported":false,"summary":"TEMPTVD activates the Temperature Flux Limited Transport option in the commercial simulator, to reduce numerical dispersion for when either the TEMP or THERMAL keywords in the RUNSPEC section have been declared.","parameters":[],"example":"","size_kind":"none","size_count":0},"TEMPVD":{"name":"TEMPVD","sections":["PROPS"],"supported":true,"summary":"This keyword defines the initial reservoir temperature versus depth tables for each equilibration region. Note that the TEMPVD keyword is an alias for RTEMPVD, and that both keywords are supported by OPM Flow, in both the PROPS and SOLUTION sections, but are treated as being mutually exclusive.","parameters":[{"index":1,"name":"DEPTH","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":2,"name":"TEMP","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Temperature"}],"example":"","expected_columns":2,"size_kind":"list"},"THCO2MIX":{"name":"THCO2MIX","sections":["PROPS"],"supported":null,"summary":"The THCO2MIX keyword specifies the thermal mixing models for salt in the water phase, CO2 in the liquid phase and vaporized water in gas phase.","parameters":[{"index":1,"name":"SALTMOD","description":"A defined character string that specifies the thermal mixing model for salt in the liquid phase, and should be set to one of the following: NONE: pure water enthalpy will be used, or MICHAELIDES: account for salt concentration according to Michaelides1\n Michaelides, E. E., “Thermodynamic Properties of Geothermal Fluids”, Geothermal Resources Council, Trans. Vol. 5 (361-364), October 1981., 1981. Michaelides, E. E., “Thermodynamic Properties of Geothermal Fluids”, Geothermal Resources Council, Trans. Vol. 5 (361-364), October 1981.","units":{},"default":"MICHAELIDES","value_type":"STRING"},{"index":2,"name":"LIQMOD","description":"A defined character string that specifies the thermal mixing model for CO2 in the liquid phase, and should be set to one of the following: NONE: do not account for CO2 in brine, IDEAL: account for CO2 assuming an ideal mixture (based on mass fractions), or DUANSUN: also add the heat of dissolution for CO2 according to Dun and Sun2\n Duan, Zhenhao, and Rui Sun. \"An improved model calculating CO2 solubility in pure water and aqueous NaCl solutions from 273 to 533 K and from 0 to 2000 bar.\" Chemical geology 193.3-4 (2003): 257-271., 2003 (Fig. 6). Duan, Zhenhao, and Rui Sun. \"An improved model calculating CO2 solubility in pure water and aqueous NaCl solutions from 273 to 533 K and from 0 to 2000 bar.\" Chemical geology 193.3-4 (2003): 257-271.","units":{},"default":"DUANSUN","value_type":"STRING","options":["NONE","IDEAL","DUANSUN"]},{"index":3,"name":"GASMOD","description":"A defined character string that specifies the thermal mixing model for vaporized water in the gas phase, and should be set to one of the following: NONE: pure CO2 enthalpy will be used, or IDEAL: account for vaporized water assuming an ideal mixture (based on mass fractions).","units":{},"default":"NONE","value_type":"STRING","options":["NONE","IDEAL"]}],"example":"The following example specifies the default thermal mixing models for salt in the liquid phase, CO2 in the liquid phase, and vaporized water in the gas phase.\n--\n-- SPECIFY THERMAL MIXING MODELS\n--\n-- SALT LIQUID GAS\n-- -------- -------- --------\nTHCO2MIX\nMICHAELIDES DUANSUN NONE /","expected_columns":3,"size_kind":"fixed","size_count":1},"TLMIXPAR":{"name":"TLMIXPAR","sections":["PROPS"],"supported":null,"summary":"The TLMIXPAR keyword defines the Todd-Longstaff259\n Todd, M. and Longstaff, W. “The Development, Testing and Application of a Numerical Simulator for Predicting Miscible Flood Performance,” paper SPE 3484, Journal of Canadian Petroleum Technology (1972) 24, No. 7, 874-882. mixing parameters, for when either the miscible or solvent options have been activated by the MISCIBLE or SOLVENT keywords in the RUNSPEC section. This keyword must be present in the input deck if the MISCIBLE or SOLVENT keywords have been activated.","parameters":[{"index":1,"name":"TLMVIS","description":"A real positive value that is greater than or equal to zero and less than or equal to one, that defines the viscosity Todd-Longstaff mixing parameter for each miscibility region.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":"1"},{"index":2,"name":"TLMDEN","description":"A real positive value that is greater than or equal to zero and less than or equal to one, that defines the density Todd-Longstaff mixing parameter for each miscibility region.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"The same value as entered for TLMVIS","value_type":"DOUBLE","dimension":"1"}],"example":"--\n-- TODD-LONGSTAFF MIXING PARAMETERS\n--\nTLMIXPAR\n-- TLM TLM\n-- VISCOS DENSITY\n-- ------- --------\n0.3500 0.3500 / TABLE NO. 01\n0.2500 1* / TABLE NO. 02\n0.6500 0.7500 / TABLE NO. 03\nThe above example defines three Todd-Longstaff mixing parameter data sets, based on the NTMISC variable on the MISCIBLE keyword in the RUNSPEC section being equal to three.","expected_columns":2,"size_kind":"fixed"},"TOLCRIT":{"name":"TOLCRIT","sections":["PROPS"],"supported":null,"summary":"Critical fluid saturations are determined from the relative permeability tables, that is the last saturation in a relative permeability table where the relative permeability of a phase is set equal to zero. Since floating-point numbers (as implemented in computers) are never exact, one cannot compare floating point numbers for exact equality. Thus, this keyword defines a value below which is considered equivalent to zero in determining the critical saturation for a phase.","parameters":[{"index":1,"name":"TOLCRIT","description":"TOLCRIT is a real positive number greater than zero and less than one that defines the critical saturation tolerance used to determine the critical saturation of a fluid in the relative permeability tables. The default value of 1 x 10-6 means that relative permeabilty values less than this value will be treated as being equal to zero.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1 x 10-6","value_type":"DOUBLE","dimension":"1"}],"example":"---\n-- SET THE CRITICAL SATURATION TOLERANCE\n--\nTOLCRIT\n1.0E-6 /\nThe above example defines the critical saturation tolerance to be the default value of 1 x 10-6.","expected_columns":1,"size_kind":"fixed","size_count":1},"TPAMEPS":{"name":"TPAMEPS","sections":["PROPS"],"supported":false,"summary":"TPAMEPS defines the volumetric strain versus coal gas concentration tables, for when the Coal Bed Methane option has been activated via the COAL keyword, and PALM-MAN has been declared for the ROCKOPT variable on the ROCKCOMP keyword; both keywords are in the RUNSPEC section. The Palmer-Mansoorii260\n Palmer, I. and Mansoori, J. “How Permeability Depends on Stress and Pore Pressure in Coalbeds: A New Model,” paper SPE 52607, SPE Reservoir Evaluation & Engineering (1998) 1, No. 6, 539-544. and 261\n Clarkson, C.R., Pan, Z., Palmer, I. and Harpalani, S. \"Predicting Sorption-Induced Strain and Permeability Increase With Depletion for Coalbed-Methane Reservoirs\", SPE 114778-PA, SPE Journal (2010) 15, No. 1, 152–159.rock model is used to calculate the impact on pore volume and permeability due to rock compaction.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","size_kind":"fixed","variadic_record":true},"TPAMEPSS":{"name":"TPAMEPSS","sections":["PROPS"],"supported":false,"summary":"TPAMEPSS defines the volumetric strain versus coal solvent concentration tables, for when the Coal Bed Methane option has been activated via the COAL keyword, and PALM-MAN has been declared for the ROCKOPT variable on the ROCKCOMP keyword; both keywords are in the RUNSPEC section. The Palmer-Mansoorii262\n Palmer, I. and Mansoori, J. “How Permeability Depends on Stress and Pore Pressure in Coalbeds: A New Model,” paper SPE 52607, SPE Reservoir Evaluation & Engineering (1998) 1, No. 6, 539-544. and 263\n Clarkson, C.R., Pan, Z., Palmer, I. and Harpalani, S. \"Predicting Sorption-Induced Strain and Permeability Increase With Depletion for Coalbed-Methane Reservoirs\", SPE 114778-PA, SPE Journal (2010) 15, No. 1, 152–159.rock model is used to calculate the impact on pore volume and permeability due to rock compaction.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","size_kind":"fixed","variadic_record":true},"TRACER":{"name":"TRACER","sections":["PROPS"],"supported":null,"summary":"The TRACER keyword defines a series of passive tracers that are associated with a phase (oil, water, or gas) in the model. The maximum number of tracers for each phase are declared on the TRACERS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"NAME","description":"A three letter character string defining the tracer’s name. NAME is used by the TNUM keyword in the REGIONS section, and unlike other keywords, the TNUM keyword itself must be concatenated with the phase and the name of the tracer defined by NAME. Similarly for the TVDP keyword in the SOLUTION section, where the TVDP keyword itself must be concatenated with the either letter F (for free) or S (for solution), followed by the name of the tracer defined by NAME. Note it is best to void names beginning with the letters F, S, and T as these names may create naming issues in post-processing software.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"PHASE","description":"A three letter character string that defines the tracer given by NAME to a particular fluid phase. The character should be set to OIL, WAT or GAS.","units":{},"default":"None","value_type":"STRING"},{"index":3,"name":"UNITS","description":"The units for the tracer. This can be any unit but should be consistent with values entered via the TBLK and TVDP keywords in the SOLUTION section. The default values are the same as the PHASE in the model.","units":{"field":"Liquid: stb Gas: Mscf","metric":"Liquid: sm3 Gas: sm3","laboratory":"Liquid: scc Gas: scc"},"default":"Same as the phases in the model","value_type":"STRING"},{"index":4,"name":"SOLPHASE","description":"A three or four letter character string defining the partitioned tracer’s solution phase. The character string should be set to OIL, WAT, GAS or MULT. Note that SOLPHASE only needs to be defined if the partitioned tracer option has been activate with the PARTTRAC keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"STRING"},{"index":5,"name":"KPNUM","description":"The table number to be used with the partitioned tracers defined by the PARTTRAC, TRACERKP and TRACERKM keywords. Note that KPNUM only needs to be defined if the partitioned tracer option has been activate with the PARTTRAC keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":6,"name":"ADSPHASE","description":"A three letter character string defining the phase used for the adsorption calculation for when the MULT option has been for SOLPHASE. The character string should be set to OIL, WAT, GAS or ALL. Note that ADSPHASE only needs to be defined if the partitioned tracer option has been activate with the PARTTRAC keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"STRING"}],"example":"--\n-- DEFINE TRACER NAMES\n--\n-- TRACER TRACER\n-- NAME PHASE\n-- ------ ------\nTRACER\n'IGS' 'GAS' / GAS INJECTOR\n'DGS' 'GAS' / DISOLVED GAS\n'IW1' 'WAT' / WAT INJECTOR 1\n'Iw2' 'WAT' / WAT INJECTOR 2\n/\nThe above example defines four passive tracers one for a gas injection well, one for tracking the dissolved gas, and two to track the injected water from two water injection wells.","expected_columns":6,"size_kind":"list"},"TRACERKM":{"name":"TRACERKM","sections":["PROPS"],"supported":false,"summary":"This keyword, TRACERKM, defines the Multi-Partitioned Tracer option K(P) tables, for when the Partitioned Tracer option has been activate with the PARTTRAC keyword in the RUNSPEC section, and the SOLPHASE parameter on the TRACER keyword in the PROPS section has been set to MULT to activate the Multi-Partitioned Tracer option. Multi-partitioned tracers can partition into any number of phases (oil, water, gas etc.) and have adsorption, decay and diffusion parameters specific to each phase; whereas the standard partitioned tracers only have a “free” and “solution” phases. For the TRACERKM keyword the K(P) tables relate the ratio of the reference phase to the other phases versus pressure. So for example, given a multi-partitioned tracer in oil, water and gas, with the water phase acting as the reference phase, then TRACERKM would consist of columnar vectors of:","parameters":[{"index":1,"name":"TRACER_NAME","description":"","units":{},"default":"","value_type":"STRING","record":1},{"index":2,"name":"PARTITION_FUNCTION_TYPE","description":"","units":{},"default":"STANDARD","value_type":"STRING","record":1},{"index":1,"name":"PHASES","description":"","units":{},"default":"","value_type":"STRING","record":2},{"index":1,"name":"TABLE","description":"","units":{},"default":"","value_type":"DOUBLE","record":3}],"example":"| [K sub { ow} left( P right)`=`{C sub{ oil }} over {C sub{ water } } \" and \" K sub { gw} left( P right)`=`{C sub{ gas }} over {C sub{ water } }] | (8.92) |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------|--------|","records_meta":[{"expected_columns":2},{},{}],"size_kind":"list"},"TRACERKP":{"name":"TRACERKP","sections":["PROPS"],"supported":false,"summary":"This keyword, TRACERKP, defines the Standard Partitioned Tracer option K(P) tables, for when the Partitioned Tracer option has been activate with the PARTTRAC keyword in the RUNSPEC section. Standard partitioned tracers only have a “free” and “solution” phases; whereas, Multi-partitioned tracers can partition into any number of phases (oil, water, gas etc.) and have adsorption, decay and diffusion parameters specific to each phase. For the TRACERKP keyword the K(P) tables relate the ratio of the reference phase (the “free” phase) to the solution phase versus pressure. So for example, given a standard partitioned tracer in oil and gas, with the oil phase acting as the reference phase, then TRACERKP would consist of columnar vectors of:","parameters":[{"index":1,"name":"TABLE","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Pressure","1"]}],"example":"| [K left( P right)`=`{C sub{ gas }} over {C sub{ oil } }] | (8.93) |\n|----------------------------------------------------------|--------|","size_kind":"fixed","variadic_record":true},"TRACITVD":{"name":"TRACITVD","sections":["PROPS"],"supported":false,"summary":"TRACITVD activates the Tracer Implicit Flux Limited Transport option and sets various parameters for this option. Basically the option is used to control numerical dispersion for tracers. Both the TRACERS keyword in the RUNSPEC section and the TRACER keyword in the PROPS section must be declared to activate tracers and to define the tracers.","parameters":[{"index":1,"name":"FLUX_LIMITER","description":"","units":{},"default":"1","value_type":"INT"},{"index":2,"name":"BOTH_TIMESTEP","description":"","units":{},"default":"YES","value_type":"STRING"}],"example":"","expected_columns":2,"size_kind":"fixed","size_count":1},"TRACTVD":{"name":"TRACTVD","sections":["PROPS"],"supported":false,"summary":"TRACTVD activates the Tracer Explicit Flux Limited Transport option. Basically the option is used to control numerical dispersion for tracers. Both the TRACERS keyword in the RUNSPEC section and the TRACER keyword in the PROPS section must be declared to activate tracers and to define the tracers.","parameters":[],"example":"","size_kind":"none","size_count":0},"TRADS":{"name":"TRADS","sections":["PROPS"],"supported":false,"summary":"This keyword, TRADS, specifies the environmental tracer adsorption tables that describe how a tracer is absorbed by the surrounding rock, for when the MXENVTR parameter has been set to greater than zero on the TRACERS keyword in the RUNSPEC section to activate environmental tracers. The keyword can only be used with environmental tracers.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","size_kind":"fixed","variadic_record":true},"TRDCY":{"name":"TRDCY","sections":["PROPS"],"supported":false,"summary":"This keyword, TRDCY, specifies the environmental tracer decay tables that specifies the tracer decay half-life, for when the MXENVTR parameter has been set to greater than zero on the TRACERS keyword in the RUNSPEC section to activate environmental tracers. The keyword can only be used with environmental tracers.","parameters":[{"index":1,"name":"HALF_TIME","description":"","units":{},"default":"1e+20","value_type":"DOUBLE","dimension":"Time"}],"example":"","expected_columns":1,"size_kind":"fixed"},"TRDIF":{"name":"TRDIF","sections":["PROPS"],"supported":false,"summary":"This keyword, TRDIF, specifies the tracer diffusion tables that specify the diffusion coefficient for a tracer. The keyword can be used with Environmental Tracers if the MXENVTR parameter has been set greater than zero on the TRACERS keyword in the RUNSPEC section. When used with a Standard Partitioned Tracer the diffusion coefficient applies to the solution phase, whereas as for a Multi-Partitioned Tracer the diffusion coefficient can be entered for each defined tracer phase. Unlike other keywords, the TRADS keyword must be concatenated with the three character name of the tracer declared by TRACER keyword in the PROPS section.","parameters":[{"index":1,"name":"HALF_TIME","description":"","units":{},"default":"1e+20","value_type":"DOUBLE","dimension":"Time"}],"example":"","expected_columns":1,"size_kind":"fixed"},"TRDIS":{"name":"TRDIS","sections":["PROPS"],"supported":false,"summary":"This keyword, TRDIS, specifies the tracer diffusion tables that should be allocated to a tracer, the actual dispersion tables are specified by the DISPERSE keyword in the PROPS section. The keyword can be used with Environmental Tracers if the MXENVTR parameter has been set greater than zero on the TRACERS keyword in the RUNSPEC section. The option does not work with two-phase Standard Partitioned Tracers and Multi-Partitioned Tracers. Unlike other keywords, the TRADS keyword must be concatenated with the three character name of the tracer declared by TRACER keyword in the PROPS section.","parameters":[{"index":1,"name":"D1TABLE","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"D2TABLE","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"D3TABLE","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"D4TABLE","description":"","units":{},"default":"","value_type":"INT"},{"index":5,"name":"D5TABLE","description":"","units":{},"default":"","value_type":"INT"},{"index":6,"name":"D6TABLE","description":"","units":{},"default":"","value_type":"INT"},{"index":7,"name":"D7TABLE","description":"","units":{},"default":"","value_type":"INT"},{"index":8,"name":"D8TABLE","description":"","units":{},"default":"","value_type":"INT"},{"index":9,"name":"D9TABLE","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":9,"size_kind":"fixed"},"TRNHD":{"name":"TRNHD","sections":["PROPS"],"supported":false,"summary":"The TRNHD keyword activates the Dispersion Non-Homogeneous Diffusion option for when tracer dispersion is independent of velocity or tracer concentration. Unlike other keywords, the TRNHD keyword must be concatenated with the name of the tracer declared by TRACER keyword in the PROPS section.","parameters":[],"example":"","size_kind":"none","size_count":0},"TRROCK":{"name":"TRROCK","sections":["PROPS"],"supported":false,"summary":"This keyword, TRROCK, specifies the environmental tracer rock data for the tracer adsorption model, for when the MXENVTR parameter has been set to greater than zero on the TRACERS keyword in the RUNSPEC section to activate environmental tracers. The keyword can only be used with environmental tracers.","parameters":[{"index":1,"name":"ADSORPTION_INDEX","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"MASS_DENSITY","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Mass/ReservoirVolume"},{"index":3,"name":"INIT_MODEL","description":"","units":{},"default":"1","value_type":"INT"}],"example":"","expected_columns":3,"size_kind":"fixed"},"TZONE":{"name":"TZONE","sections":["PROPS"],"supported":false,"summary":"The TZONE keyword sets the transition end-point scaling options for the oil, water and gas phases, for when the End-Point Scaling option has been activated by the ENDSCALE keyword in the RUNSPEC section. The keyword determines if the phase critical saturation should or should not be set to the initial immobile saturation in areas where the initial saturation is below the entered critical saturation.","parameters":[{"index":1,"name":"OILZONE","description":"OILZONE is a single character that sets the oil phase transition zone end-point scaling option and should be set to either T or F: T: for true, results in the SOWCR values being adjusted to the initial immobile saturation for oil-water or oil-water-miscible gas simulations. For oil-gas simulations the SOGCR values are modified to be the initial immobile saturation. The modifications only occur in cells where the initial saturation is below the entered critical saturation. F: for false, means the critical saturations are not modified.","units":{},"default":"F","value_type":"STRING"},{"index":2,"name":"WATZONE","description":"WATZONE is a single character that sets the water phase transition zone end-point scaling option and should be set to either T or F: T: for true, results in the SWCR values being adjusted to the initial immobile saturations. The modifications only occur in cells where the initial saturation is below the entered critical saturation values (SWCR). F: for false, means the critical saturations are not modified.","units":{},"default":"F","value_type":"STRING"},{"index":3,"name":"GASZONE","description":"GASZONE is a single character that sets the gas phase transition zone end-point scaling option and should be set to either T or F: T: for true, results in the SGCR values being adjusted to the initial immobile saturation for oil-gas or gas-water simulations. The modifications only occur in cells where the initial saturation is below the entered critical saturation (SGCR). F: for false, means the critical saturations are not modified.","units":{},"default":"F","value_type":"STRING"}],"example":"--\n-- END-POINT SCALING TRANSITION ZONE OPTIONS\n--\n-- OILZONE WATZONE GASZONE\n-- ------- ------- -------\nTZONE\nF T F / SCALING OPTION\nThe above example results in the SWCR values being adjusted to the initial immobile saturations.","expected_columns":3,"size_kind":"fixed","size_count":1},"VCRIT":{"name":"VCRIT","sections":["PROPS"],"supported":false,"summary":"The VCRIT keyword defines the critical volumes for each of the compositional components active in the model and for each equation of state. The keyword should only be used if the compositional mode has been requested using the COMPS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"VCRIT","description":"A series of real numbers that define the critical volumes for each of the compositional components active in the model.","units":{"field":"ft3/lb-M","metric":"m3/kg-M","laboratory":"m3/kg-M"},"default":"None","value_type":"DOUBLE","dimension":"GeometricVolume/Moles"}],"example":"The following example defines the critical volumes for each component in a single three-component equation of state model.\n--\n-- Critical Volumes\n--\nVCRIT\n1.505 1.585 3.250 /\nThe following example defines the critical volumes for each component in two three-component equation of state models.\n--\n-- Critical Volumes\n--\nVCRIT\n1.505 1.585 3.250 /\n1.505 1.585 3.250 /","size_kind":"fixed","variadic_record":true},"VDFLOW":{"name":"VDFLOW","sections":["PROPS"],"supported":false,"summary":"VDFLOW activates non-Darcy flow between grid blocks and defines a constant non-Darcy flow coefficient for the whole grid, the coefficient only applies to the gas phase. The coefficient is normally derived from well tests or calculated analytically based on the coefficient of inertial resistance, usually known as β, in Forchheimer’s flow equation,264\n Geertsma, J., 1974. Estimating the Coefficient of Inertial Resistance in Fluid Flow Through Porous Media. Soc.Pet.Eng.J., October: 445-450., 265\n Gewers, C.W.W. and Nichol, L.R., 1969. Gas Turbulence Factor in a Microvugular Carbonate. J.Can.Pet.Tech., April.and 266\n Wong, S.W., 1970. Effects of Liquid Saturation on Turbulence Factors for Gas Liquid Systems. J.Can.Pet.Tech., October. Dake267\n Dake, L.P. Fundamentals of Reservoir Engineering, Amsterdam, The Netherlands, Elsevier Science BV (1978) Chapter 8.6, pages 252-257., in chapter eight, reports a typical value of β to be 10.07 cm-1.","parameters":[{"index":1,"name":"BETA","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"VDFLOWR":{"name":"VDFLOWR","sections":["PROPS"],"supported":false,"summary":"VDFLOW activates non-Darcy flow between grid blocks and defines a constant non-Darcy flow coefficient for individual regions allocated by the SATNUM keyword in the REGIONS section. Note that the coefficient only applies to the gas phase. The coefficient is normally derived from well tests or calculated analytically based on the coefficient of inertial resistance, usually known as β, in Forchheimer’s flow equation,268\n Geertsma, J., 1974. Estimating the Coefficient of Inertial Resistance in Fluid Flow Through Porous Media. Soc.Pet.Eng.J., October: 445-450., 269\n Gewers, C.W.W. and Nichol, L.R., 1969. Gas Turbulence Factor in a Microvugular Carbonate. J.Can.Pet.Tech., April.and 270\n Wong, S.W., 1970. Effects of Liquid Saturation on Turbulence Factors for Gas Liquid Systems. J.Can.Pet.Tech., October. Dake271\n Dake, L.P. Fundamentals of Reservoir Engineering, Amsterdam, The Netherlands, Elsevier Science BV (1978) Chapter 8.6, pages 252-257., in chapter eight, re...","parameters":[{"index":1,"name":"BETA","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","expected_columns":1,"size_kind":"fixed"},"VEFRAC":{"name":"VEFRAC","sections":["PROPS"],"supported":false,"summary":"This keyword defines the Vertical Equilibrium (“VE”) relative permeability weighting factor (α) used to calculate the VE relative permeability curves to be used in the simulation, for when the VE option has been activated by the VE keyword in the RUNSPEC section. If α = 1.0, then the VE model calculated relative permeability curves will be used, and if α = 0.0, then the curves entered via the SWOF, SGOF, SLGOF series of keywords or the SWFN, SGFN, SGWFN, SOF2, SOF3, SOF32D series of keywords, will be used. A value of α between zero and one will result in weighted average relative permeability curves being employed, that is:","parameters":[{"index":1,"name":"FRAC","description":"","units":{},"default":"10","value_type":"DOUBLE"}],"example":"| [VE sub( average )~=~left( 1.0`-` %alpha right ) `times` left(SATNUM sub{curves}right)~+~ %alpha `times` left(VE Model sub{ curves } right)] | (8.94) |\n|----------------------------------------------------------------------------------------------------------------------------------------------|--------|","expected_columns":1,"size_kind":"fixed","size_count":1},"VEFRACP":{"name":"VEFRACP","sections":["PROPS"],"supported":false,"summary":"This keyword defines the Vertical Equilibrium (“VE”) capillary pressure weighting factor (α) used to calculate the VE capillary pressure curves to be used in the simulation, for when the VE option has been activated by the VE keyword in the RUNSPEC section. If α = 1.0, then the VE model calculated capillary pressure curves will be used, and if α = 0.0, then the curves entered via the SWOF, SGOF, SLGOF series of keywords or the SWFN, SGFN, SGWFN, SOF2, SOF3, SOF32D series of keywords, will be used. A value of α between zero and one will result in weighted average capillary pressure curves being employed, that is:","parameters":[{"index":1,"name":"FRAC","description":"","units":{},"default":"1","value_type":"DOUBLE"}],"example":"| [VE sub( average )~=~left( 1.0`-` %alpha right ) `times` left(SATNUM sub{curves}right)~+~ %alpha `times` left(VE Model sub{ curves } right)] | (8.95) |\n|----------------------------------------------------------------------------------------------------------------------------------------------|--------|","expected_columns":1,"size_kind":"fixed","size_count":1},"VEFRACPV":{"name":"VEFRACPV","sections":["PROPS"],"supported":false,"summary":"This keyword defines the Vertical Equilibrium (“VE”) capillary pressure weighting factor (α) used to calculate the VE capillary pressure curves to be used in the simulation, for when the VE option has been activated by the VE keyword in the RUNSPEC section. If α = 1.0, then the VE model calculated capillary pressure curves will be used, and if α = 0.0, then the curves entered via the SWOF, SGOF, SLGOF series of keywords or the SWFN, SGFN, SGWFN, SOF2, SOF3, SOF32D series of keywords, will be used. A value of α between zero and one will result in weighted average capillary pressure curves being employed, that is:","parameters":[],"example":"| [VE sub( average )~=~left( 1.0`-` %alpha right ) `times` left(SATNUM sub{curves}right)~+~ %alpha `times` left(VE Model sub{ curves } right)] | (8.96) |\n|----------------------------------------------------------------------------------------------------------------------------------------------|--------|","size_kind":"array"},"VEFRACV":{"name":"VEFRACV","sections":["PROPS"],"supported":false,"summary":"This keyword defines the Vertical Equilibrium (“VE”) relative permeability weighting factor (α) used to calculate the VE relative permeability curves to be used in the simulation, for when the VE option has been activated by the VE keyword in the RUNSPEC section. If α = 1.0, then the VE model calculated relative permeability curves will be used, and if α = 0.0, then the curves entered via the SWOF, SGOF, SLGOF series of keywords or the SWFN, SGFN, SGWFN, SOF2, SOF3, SOF32D series of keywords, will be used. A value of α between zero and one will result in weighted average relative permeability curves being employed, that is:","parameters":[],"example":"| [VE sub( average )~=~left( 1.0`-` %alpha right ) `times` left(SATNUM sub{curves}right)~+~ %alpha `times` left(VE Model sub{ curves } right)] | (8.97) |\n|----------------------------------------------------------------------------------------------------------------------------------------------|--------|","size_kind":"array"},"VISCAQA":{"name":"VISCAQA","sections":["PROPS"],"supported":true,"summary":"The VISCAQA keyword specifies the three Ezrokhi coefficients for each compositional component and for each equation of state that are used to calculate the aqueous phase viscosity. The keyword should only be used if the compositional mode has been requested using the COMPS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"COEFFS","description":"A series of real numbers that define the three Ezrokhi coeffients for each of the compositional components active in the model.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":"1"}],"example":"The following example defines the Ezrokhi coefficients for each component in a single three-component equation of state model.\n--\n-- Ezrokhi Coefficients for Aqueous Viscosity Calculation\n--\nVISCAQA\n--COEFF0 COEFF1 COEFF2\n2.0E-7 0.0 1.0E-9\n2.0E-7 0.0 1.0E-9\n2.0E-7 0.0 1.0E-9 /\nThe following example defines the Ezrokhi coefficients for each component in two three-component equation of state models.\n--\n-- Ezrokhi Coefficients for Aqueous Viscosity Calculation\n--\nVISCAQA\n--COEFF0 COEFF1 COEFF2\n2.0E-7 0.0 1.0E-9\n2.0E-7 0.0 1.0E-9\n2.0E-7 0.0 1.0E-9 /\n--\n2.0E-7 0.0 1.0E-9\n2.0E-7 0.0 1.0E-9\n2.0E-7 0.0 1.0E-9 /","size_kind":"fixed","variadic_record":true},"VISCREF":{"name":"VISCREF","sections":["PROPS"],"supported":null,"summary":"VISCREF defines the reference conditions for the viscosity-temperature tables, GASVISCT, OILVISCT and WATVISCT, for when the thermal option has been activated by THERMAL keyword in the RUNSPEC section. This keyword can only be used if the thermal option has been activated by the THERMAL keyword in the RUNSPEC section. Note this is different to the commercial simulator that uses the TEMP keyword in the RUNSPEC section to activate the black-oil thermal model.","parameters":[{"index":1,"name":"PRES","description":"PRES is a real positive number defining the reference pressure for the viscosity and temperature tables","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":"Pressure"},{"index":2,"name":"RS","description":"RS is a real positive number defining the reference gas-oil ratio for when the model contains gas dissolved as activated by the DISGAS keyword in the RUNSPEC section","units":{"field":"Mscf/stb","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"None","value_type":"DOUBLE","dimension":"GasDissolutionFactor"},{"index":3,"name":"API","description":"API is a real number defining the oil API for when the API tracking option has been invoked by the API keyword in the RUNSPEC section. Note that OPM Flow does not support API tracking, and therefore this variable is ignored.","units":{"field":"oAPI","metric":"oAPI","laboratory":"oAPI"},"default":"None","value_type":"DOUBLE","dimension":"1"}],"example":"The following example shows the VISCREF keyword for when the thermal option has been activated by the THERMAL keyword in the RUNSPEC section and for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set to five.\n--\n-- REF REF REF\n-- PRESSURE GOR API\n-- -------- ------- -------\nVISCREF\n3000.0 0.500 / TABLE NO. 01\n3200.0 0.550 / TABLE NO. 02\n3300.0 0.580 / TABLE NO. 03\n3400.0 0.620 / TABLE NO. 04\n3500.0 0.625 / TABLE NO. 05\nThere is no terminating “/” for this keyword.","expected_columns":3,"size_kind":"fixed"},"WAGHYSTR":{"name":"WAGHYSTR","sections":["PROPS"],"supported":true,"summary":"This keyword defines the parameters for the Water-Alternating-Gas (“WAG”) hysteresis option, for when the hysteresis option has been activated by the WAGHYSTR variable on the SATOPTS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"LANDS_PARAMETER","description":"A real value greater than zero that defines Land’s parameter, [C].. The Land’s parameter controls how the trapped gas saturation depends on the maximum gas saturation attained and the critical gas saturation; and the shape of the imbibition curve. [s_gtrap = s_gcr + ( s_gm - s_gcr ) over ( 1 + C(s_gm - s_gcr) )] where, [s_gtrap]is the trapped gas saturation, [s_gm]is the maximum gas saturation attained, and [s_gcr]is the critical gas saturation. Values of the Land’s parameter that are too small give a trapped gas saturation close to the maximum gas saturation attained. This results in an unphysical steep relative permeability curve giving potential convergence problems.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE"},{"index":2,"name":"SECONDARY_DRAINAGE_REDUCTION","description":"A real value greater than or equal to zero that defines the secondary drainage reduction factor, alpha. As alpha increases the reduction in gas mobility on secondary drainage increases.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.0","value_type":"DOUBLE"},{"index":3,"name":"GAS_MODEL","description":"A defined character string that defines whether the gas hysteresis model should be used, and should be set to one of the following character strings: YES: Use the WAG hysteresis model for the gas phase relative permeability. NO: Turn off the WAG hysteresis model and use the drainage curve. Only the YES option is currently supported by the simulator.","units":{},"default":"YES","value_type":"STRING"},{"index":4,"name":"RES_OIL","description":"A defined character string that defines whether the residual oil model should be used, and should be set to one of the following character strings: YES: Use the trapped gas to modify the residual oil saturation (SOM) in the STONE 1 three-phase oil relative permeability model. No action is taken unless the STONE1 keyword has been entered. NO: Do not modify the residual oil saturation. Only the NO option is currently supported by the simulator.","units":{},"default":"YES","value_type":"STRING"},{"index":5,"name":"WATER_MODEL","description":"A defined character string that defines whether the water hysteresis model should be used, and should be set to one of the following character strings: YES: Use the WAG hysteresis model for the water phase relative permeability NO: Turn off the WAG hysteresis model. Note that the hysteresis model specified in EHYSTR keyword applies. Only the NO option is currently supported by the simulator.","units":{},"default":"YES","value_type":"STRING"},{"index":6,"name":"IMB_LINEAR_FRACTION","description":"A real value greater than zero that defines the imbibtion curve linear fraction. This is the fraction of the curve between Sgm and Sgtrap that uses a linear transformation. A non-zero value for the linear fraction prevents the potential infinite gradient in the imbibition curve when using the Carlson analytic model.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.1","value_type":"DOUBLE"},{"index":7,"name":"THREEPHASE_SAT_LIMIT","description":"A real value between zero and one that defines the three-phase model threshold saturation. When the water saturation exceeds this threshold above the connate water saturation the gas (non-wetting) phase hysteresis switches from the two-phase model to the three-phase model. In the two-phase model a secondary drainage process follows the imbibition curve. However, if the water saturation exceeds the connate saturation by the given threshold, at the beginning of the secondary drainage process a three-phase secondary drainage curve is followed. This value also defines the minimum percentage change in gas saturation to allow switching from drainage to imbibition curve and vice-versa. This threshold allows better control of the numerical sensitivity of the system, preventing it from being too unstable.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.001","value_type":"DOUBLE"},{"index":8,"name":"RES_OIL_MOD_FRACTION","description":"A real value between zero and one that defines the residual oil modification fraction. This is the fraction of the trapped gas saturation subtracted from the residual oil (SOM) in the STONE 1 three-phase oil relative permeability model. This is not supported and will be ignored by the simulator.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0","value_type":"DOUBLE"}],"example":"The following example defines the WAG hysteresis model parameters using the WAGHYSTR keyword for a case with three saturation table regions\n--\n-- WAG HYSTERESIS PARAMETERS\n--\n-- LAND ALPHA GAS RES WATER LINEAR\n-- C FACTOR MODEL OIL MODEL FRAC\nWAGHYSTR\n2.0 1.0 YES YES YES 0.2 /\n2.0 1.0 YES NO /\n2.0 /\nHere, saturation table region one uses the gas WAG hysteresis, residual oil and water WAG hysteresis models, with a Land’s parameter of 2.0, an alpha factor of 1.0, and a imbibition curve linear factor of 0.2. The gas and water WAG hysteresis models are used in region two but the residual oil model is turned off, with a Land’s parameter of 2.0, an alpha factor of 1.0, and a default imbibition curve linear factor of 0.1. A Land’s parameter of 2.0 has been specified for region three with the remainder of the parameters defaulted.\nNote that the above example uses some options that are not currently supported by OPM Flow.","expected_columns":8,"size_kind":"fixed"},"WATDENT":{"name":"WATDENT","sections":["PROPS"],"supported":null,"summary":"WATDENT defines the water density as a function of temperature coefficients for when the thermal option has been activated by the THERMAL keyword in the RUNSPEC. Note this is an OPM Flow keyword used with OPM Flow’s black-oil thermal model that is not available in the commercial simulator’s black-oil thermal formulation.","parameters":[{"index":1,"name":"TEMP","description":"TEMP is a real positive value greater than zero that defines the absolute reference temperature used with TEXP1 and TEXP2 to estimate the change in water density with respect to temperature.","units":{"field":"oR 527.67","metric":"K 293.15","laboratory":"K 293.15"},"default":"Defined","value_type":"DOUBLE","dimension":"AbsoluteTemperature"},{"index":2,"name":"TEXP1","description":"TEXP1 is a real positive value greater than zero that defines the water thermal expansion coefficient of the first order.","units":{"field":"1/oR 1.67 x 10-4","metric":"1/K 3.0 x 10-4","laboratory":"1/K 3.0 x 10-4"},"default":"Defined","value_type":"DOUBLE","dimension":"1/AbsoluteTemperature"},{"index":3,"name":"TEXP2","description":"TEXP2 is a real positive value greater than zero that defines the water thermal expansion coefficient of the second order.","units":{"field":"1/oR2 9.26 x 10-7","metric":"1/K2 3.0 x 10-6","laboratory":"1/K2 3.0 x 10-6"},"default":"Defined","value_type":"DOUBLE","dimension":"1/AbsoluteTemperature*AbsoluteTemperature"}],"example":"The following example shows the WATDENT keyword using the default values, for when the thermal option has been activated by the THERMAL keyword in the RUNSPEC section and for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set to two.\n--\n-- WATER DENSITY TEMPERATURE COEFFICIENTS (OPM FLOW EXTENSION KEYWORD)\n--\n-- WATER DENSITY DENSITY\n-- TEMP COEFF1 COEFF2\n-- -------- ------- -------\nWATDENT\n1* 1* 1* / TABLE NO. 01\n1* 1* 1* / TABLE NO. 02\nThere is no terminating “/” for this keyword.\n| [%rho_w( p, T ) = %rho_w( p_s, T_s ) b_w( p, T )] | (8.3.366.1) |\n|---------------------------------------------------|-------------|\n| [b_w( p, T ) = { b_w( p, T_ref ) } over { 1 + c_1 ( T - T_ref ) + c_2 ( T - T_ref )^2 }] | (8.3.366.2) |\n|------------------------------------------------------------------------------------------|-------------|","expected_columns":3,"size_kind":"fixed"},"WATJT":{"name":"WATJT","sections":["PROPS"],"supported":null,"summary":"WATJT activates the water Joule-Thomson effect275\n The Joule–Thomson coefficient is defined as the change in temperature with respect to an increase in pressure at constant enthalpy. in temperature calculations, and defines the water Joule-Thomson Coefficient (“JTC”) at a given reference pressure, for when OPM Flow’s thermal option has been activated by the THERMAL keyword in the RUNSPEC.","parameters":[{"index":1,"name":"PRESS","description":"A real positive value that defines the reference pressure for the corresponding Joule-Thomson Coefficient, WATJTC.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":"Pressure"},{"index":2,"name":"WATJTC","description":"WATJTC is a real positive or negative value that defines the water phase Joule-Thomson Coefficient. If the value is defaulted (1*) or set to 0, then WATJTC is internally calculated using thermal water density data on the WATSDENT keyword in the PROPS section. If a non-zero value is specified, then the WATJTC is assumed to be constant and equal to that value.","units":{"field":"oF/psia","metric":"oC/barsa","laboratory":"oC/atma"},"default":"0","value_type":"DOUBLE","dimension":"AbsoluteTemperature/Pressure"}],"example":"The following example shows the WATJT keyword for when the thermal option has been activated by the THERMAL keyword in the RUNSPEC section, and for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set equal to two.\n--\n-- WATER JOULE-THOMSON COEFFICIENT (OPM FLOW EXTENSION KEYWORD)\n--\n-- REF OIL\n-- PRESS JTC\n-- -------- -------\nWATJT\n20.0 1* / TABLE NO. 01\n20.0 -0.20 / TABLE NO. 02\nHere the first entry is defaulted, and the simulator will therefore calculate the water JTC internally using the data on the WATDENT keyword in the PROPS section.\nThere is no terminating “/” for this keyword.\n| Note This is an OPM Flow keyword used with OPM Flow’s black-oil thermal model, that is not available in the commercial simulator’s black-oil thermal formulation. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| [%eta` `=`` left({ partial T} over {partial P} right)] | (8.98) |\n|--------------------------------------------------------|--------|\n| [%eta ``=`` left( T %alpha``-``1 right) 1 over( %rho C_p )``-`` left( g over C_p dp over dz right)^-1] | (8.99) |\n|--------------------------------------------------------------------------------------------------------|--------|\n| [%eta ``=`` left( T %alpha``-``1 right) 1 over( %rho C_b )] | (8.100) |\n|-------------------------------------------------------------|---------|","expected_columns":2,"size_kind":"fixed"},"WATVISCT":{"name":"WATVISCT","sections":["PROPS"],"supported":null,"summary":"WATVISCT defines the water viscosity as a function of temperature for when thermal option has been activated by the THERMAL keywords in the RUNSPEC. The reference pressure for this table is given by the VISCREF keyword in the PROPS section.","parameters":[{"index":1,"name":"TEMP","description":"A columnar vector of real monotonically increasing down the column values that defines the temperature values.","units":{"field":"oF","metric":"oC","laboratory":"oC"},"default":"None","value_type":"DOUBLE","dimension":["Temperature","Viscosity"]},{"index":2,"name":"VIS","description":"A columnar vector of real decreasing down the column values that defines the water viscosity for the corresponding temperature values (TEMP). VIS should be given at the reference pressure defined by the PRESS variable on the VISCREF keyword.","units":{"field":"cP","metric":"cP","laboratory":"cP"},"default":"None"}],"example":"The following example shows the WATVISCT keyword for when the thermal option has been activated by the THERMAL keyword in the RUNSPEC section and for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set equal to one.\n--\n-- WATER VISCOSITY VERSUS TEMPERATURE TABLES\n--\n-- WATER WATER\n-- TEMP VISC\n-- -------- -------\nWATVISCT\n100.0 0.625\n110.0 0.620\n120.0 0.580\n150.0 0.550\n165.0 0.500 / TABLE NO. 01\nThere is no terminating “/” for this keyword.","size_kind":"fixed","variadic_record":true},"WSF":{"name":"WSF","sections":["PROPS"],"supported":null,"summary":"The WSF keyword defines the water relative permeability data versus water saturation tables for when only gas and water are present in the input deck. This keyword should only be used if the gas and water phases are present in the run, and can therefore also be used with the CO2STORE and H2STORE models. In addition, the keyword must be used in conjunction with the GSF keyword in the PROPS section, that defines the gas relative permeability and gas-water capillary pressure data versus gas saturation for gas-water systems.","parameters":[{"index":1,"name":"SWAT","description":"A columnar vector of real values monotonically increasing down the column starting from the connate water saturation and terminating at one, that defines the water saturation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":["1","1"]},{"index":2,"name":"KRW","description":"A columnar vector of real values that are either equal or increasing down the column and that are greater than or equal to zero and less than or equal to one that defines the water relative permeability with respect to water saturation. Note that the first entry in the column must be zero.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- WATER RELATIVE PERMEABILITY TABLES (OPM FLOW KEYWORD)\n--\nWSF\n-- SWAT KRW\n-- FRAC\n-- -------- --------\n0.200000 0.0000\n0.238616 0.0002\n0.245309 0.0004\n0.261989 0.0010\n0.303091 0.0044\n0.368269 0.0191\n0.435026 0.0519\n0.486387 0.0940\n0.550683 0.1725\n0.575342 0.2115\n0.599076 0.2542\n0.621294 0.2991\n0.642171 0.3458\n0.658984 0.3868\n0.671123 0.4183\n0.679268 0.4403\n0.684963 0.4562\n0.688893 0.4674\n0.692025 0.4765\n0.694641 0.4841\n0.696976 0.4910\n0.699099 0.4973\n0.700000 0.5000\n1.000000 0.9000 / TABLE NO. 01\n-- -------- --------\n0.200000 0.0000\n0.238616 0.0002\n0.245309 0.0004\n0.261989 0.0010\n0.303091 0.0044\n0.368269 0.0191\n0.435026 0.0519\n0.486387 0.0940\n0.550683 0.1725\n0.575342 0.2115\n0.599076 0.2542\n0.621294 0.2991\n0.642171 0.3458\n0.658984 0.3868\n0.671123 0.4183\n0.679268 0.4403\n0.684963 0.4562\n0.688893 0.4674\n0.692025 0.4765\n0.694641 0.4841\n0.696976 0.4910\n0.699099 0.4973\n0.700000 0.5000\n1.000000 0.9000 / TABLE NO. 01\nThe example defines two WSF tables for use when only gas and water are present in the run.\n| Note WSF is a compositional keyword in the commercial compositional simulator, and will therefore cause an error in the commercial black-oil simulator. Currently, both the GSF and WSF keywords can only be used with the CO2STORE and H2STORE models. |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"fixed","variadic_record":true},"ZMFVD":{"name":"ZMFVD","sections":["PROPS"],"supported":true,"summary":"The ZMFVD keyword defines the compositional component mole fractions, for each component, as a function of depth, as such the keyword should have the same number of component columnar vectors as that declared via the COMPS keyword in the RUNSPEC section, and the NCOMPS keyword in the PROPS section. The keyword should only be used if the CO2STORE and GASWAT keywords in the RUNSPEC section have also be activated for the gas-water two component model.","parameters":[{"index":1,"name":"DEPTH","description":"A columnar vector of real monotonically increasing down the column values that defines the depth values for the corresponding compositional component mole fractions. The default number of DEPTH values is 20, as defined by the NDRXVD parameter on the EQLDIMS keyword in the RUNSPEC section, and which may be used to reset the number of DEPTH values.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":["Length","1","1"]},{"index":2,"name":"ZCOMP","description":"A series of columnar vectors, with each columnar vector representing a compositional component mole fraction as a function of DEPTH. In addition, the sum of the compositional component mole fractions must sum to one for a given DEPTH value, otherwise an error will occur. Secondly, if the composition is independent of depth, then only one single row may be entered. Note that the number of columnar vectors, should be the same as that entered via the NCOMPS keyword in the PROPS section, and the COMPS keyword in the RUNSPEC section. Finally, only the default value of two components are currently supported by OPM Flow.","units":{"field":"mole fraction","metric":"mole fraction","laboratory":"mole fraction"},"default":"None"}],"example":"The following example defines how to confirm a two component formulation, together with defining the names of the composition components, as well as the compositional gradient, to be used with the CO2STORE and GASWAT options.\n--\n-- CONFIRM NUMBER OF COMPOSITIONAL COMPONENTS (OPM FLOW KEYWORD)\n--\nNCOMPS\n2 /\n--\n-- DEFINE COMPOSITIONAL COMPONENTS NAMES (OPM FLOW KEYWORD)\n--\nCNAMES\n'CO2'\n'H2O' /\n--\n-- COMPOSITIONAL COMPONENT MOLE FRACTIONS VS DEPTH (OPM FLOW KEYWORD)\n--\n-- DEPTH CO2 H2O\nZMFVD\n2000 0.0 1.0\n2100 0.0 1.0\n/\n| Note This is an OPM Flow keyword used with OPM Flow’s CO2STORE and GASWAT keywords in the RUNSPEC section, and should not be confused with the more general version of the ZMFVD keyword used in the commercial compositional simulator. |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"fixed","variadic_record":true},"ENDNUM":{"name":"ENDNUM","sections":["REGIONS"],"supported":false,"summary":"The ENDNUM keyword defines the end-point scaling depth table region numbers for each grid block. The end-point scaling depth tables for various regions are defined by the ENPVTD280\n This keyword is not supported by OPM Flow but would change the results if supported so the simulation will be stopped. and the ENKRVD281\n This keyword is not supported by OPM Flow but would change the results if supported so the simulation will be stopped. keywords in the PROPS section. In the RUNSPEC section the NTENDP variable on the ENDSCALE keyword defines the maximum number of depth tables.","parameters":[{"index":1,"name":"ENDNUM","description":"ENDNUM defines an array of positive integers assigning a grid cell to a particular end-point scaling depth table region. The maximum number of ENDNUM regions is set by the NTENDP variable on the ENDSCALE keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"The example below sets three ENDNUM regions for a 4 x 5 x 2 model.\n--\n-- DEFINE ENDNUM REGIONS FOR ALL CELLS\n--\nENDNUM\n2 2 1 1 2 2 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n3 3 1 1 3 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n/\nAlternatively the EQUALS keyword could be employed to accomplish the same task, that is:\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nENDNUM 1 1* 1* 1* 1* 1* 1* / SET REGION 1\nENDNUM 2 1 2 1 2 1 1 / SET REGION 2\nENDNUM 3 1 2 1 2 2 2 / SET REGION 3\n/","size_kind":"array"},"EOSNUM":{"name":"EOSNUM","sections":["REGIONS"],"supported":false,"summary":"The EOSNUM keyword defines the Equation Of State (EOS) region number for all the cells in the model via an array. The region number specifies which Equation Of State is used in each grid block. The keyword should only be used if the compositional mode has been requested using the COMPS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"EOSNUM","description":"EOSNUM is an array of positive integers less than or equal to NMEOSR that define the EOS region number for each cell in the model. The NMEOSR variable on the TABDIMS keyword in the RUNSPEC section defines the number of EOS regions in the model.","units":{},"default":"1"}],"example":"The example below sets two EOSNUM regions for a 4 x 5 x 2 model.\n--\n-- DEFINE EOSNUM REGIONS FOR ALL CELLS\n--\nEOSNUM\n20*1\n20*2\n/","size_kind":"array"},"EQLNUM":{"name":"EQLNUM","sections":["REGIONS"],"supported":null,"summary":"The EQLNUM keyword defines the equilibration region numbers for each grid block. The equilibration data for various regions are defined in the SOLUTION section. For example, the EQUIL keyword in the SOLUTION section defines the initial pressures and fluid contacts for each equilibration region identified by the EQLNUM region array.","parameters":[{"index":1,"name":"EQLNUM","description":"EQLNUM defines an array of positive integers assigning a grid cell to a particular equilibration region. The maximum number of EQLNUM regions is set by the NTEQUL variable on the EQLDIMS keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"The example below sets three EQLNUM regions for a 4 x 5 x 2 model.\n--\n-- DEFINE EQLNUM REGIONS FOR ALL CELLS\n--\nEQLNUM\n2 2 1 1 2 2 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n3 3 1 1 3 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n/\nAlternatively the EQUALS keyword could be employed to accomplish the same task, that is:\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nEQLNUM’ 1 1* 1* 1* 1* 1* 1* / SET REGION 1\nEQLNUM’ 2 1 2 1 2 1 1 / SET REGION 2\nEQLNUM’ 3 1 2 1 2 2 2 / SET REGION 3\n/","size_kind":"array"},"FIP":{"name":"FIP","sections":["REGIONS"],"supported":null,"summary":"The FIP keyword defines the fluid in-place name and the associated region numbers for each grid block. The simulator can print out summaries of the fluid in-place in each region, the current flow rates between regions, and the cumulative flows between regions. This keyword is not in the standard keyword format due to the fluid in-place name being concatenated to the keyword FIP to fully define the keyword.","parameters":[{"index":1,"name":"FIPNAME","description":"A character string of up to eight characters, consisting of FIP as the first three characters followed by up to a five letter character string defining the fluid in-place’s name.","units":{},"default":"None"},{"index":2,"name":"FIPNUM","description":"FIPNUM defines an array of positive integers greater than or equal to one, that assigns a grid cell to a particular fluid in-place region named by FIPNAME. The maximum number of FIP and FIPNUM regions is set by the REGDIMS(NMFIPR) or the TABDIMS(NTFIP) keywords(variables) in the RUNSPEC section. If both REGDIMS(NMFIPR) and TABDIMS(NTFIP) have been defined then the maximum of the two is used.","units":{},"default":"1"}],"example":"The example below defines a region name of UNIT and sets three FIPUNIT regions for a 4 x 5 x 2 model.\n--\n-- DEFINE FIPUNIT FIP REGIONS FOR ALL CELLS\n--\nFIPUNIT\n2 2 1 1 2 2 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n3 3 1 1 3 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n/\nThe second example is based on the Norne model that defines two FIP regions based on geological layers and numerical layers using the EQUALS keyword.\n-- FIPGL BASED ON GEOLOGICAL LAYERS\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nFIPGL 1 1 46 1 112 1 3 / Garn\nFIPGL 2 1 46 1 112 4 4 / Not\nFIPGL 3 1 46 1 112 5 5 / Ile 2.2\nFIPGL 4 1 46 1 112 6 8 / Ile 2.1\nFIPGL 5 1 46 1 112 9 11 / Ile 1\nFIPGL 6 1 46 1 112 12 12 / Tofte 2.2\nFIPGL 7 1 46 1 112 13 15 / Tofte 2.1\nFIPGL 8 1 46 1 112 16 18 / Tofte 1\nFIPGL 9 1 46 1 112 19 22 / Tilje\n--\n-- FIPNL BASED ON NUMERICAL LAYERS\n--\nFIPNL 1 1 46 1 112 1 1 / Garn 3\nFIPNL 2 1 46 1 112 2 2 / Garn 2\nFIPNL 3 1 46 1 112 3 3 / Garn 1w\nFIPNL 4 1 46 1 112 4 4 / Not\nFIPNL 5 1 46 1 112 5 5 / Ile 2.2\nFIPNL 6 1 46 1 112 6 6 / Ile 2.1.3\nFIPNL 7 1 46 1 112 7 7 / Ile 2.1.2\nFIPNL 8 1 46 1 112 8 8 / Ile 2.1.1\nFIPNL 9 1 46 1 112 9 9 / Ile 1.3\nFIPNL 10 1 46 1 112 10 10 / Ile 1.2\nFIPNL 11 1 46 1 112 11 11 / Ile 1.1\nFIPNL 12 1 46 1 112 12 12 / Tofte 2.2\nFIPNL 13 1 46 1 112 13 13 / Tofte 2.1.3\nFIPNL 14 1 46 1 112 14 14 / Tofte 2.1.2\nFIPNL 15 1 46 1 112 15 15 / Tofte 2.1.1\nFIPNL 16 1 46 1 112 16 16 / Tofte 1.2.2\nFIPNL 17 1 46 1 112 17 17 / Tofte 1.2.1\nFIPNL 18 1 46 1 112 18 18 / Tofte 1.1\nFIPNL 19 1 46 1 112 19 19 / Tilje 4\nFIPNL 20 1 46 1 112 20 20 / Tilje 3\nFIPNL 21 1 46 1 112 21 21 / Tilje 2\nFIPNL 22 1 46 1 112 22 22 / Tilje 1\n/\nThen in order to get the reservoir pressure for the regions and the in-place oil volumes SUMMARY variables written to the SUMMARY file, one would use the following SUMMARY variable names in the SUMMARY section\n-- ==============================================================================\n--\n-- SUMMARY SECTION\n--\n-- ==============================================================================\nSUMMARY\n-- FIP REGION REPORTING\n--\nROIP_GL\n/\nROIP_NL\n/\nRPR__GL\n/\nRPR__NL\n/\nNotice how the “_” character has been used to extend the SUMMARY variable name to five characters.\n| Note The commercial simulator prints out a fluid in-place report if the FIP option on the RPTSCHED keyword is set equal to three, that is: FIP=3. This option is currently not available in OPM Flow. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|"},"FIPNUM":{"name":"FIPNUM","sections":["REGIONS"],"supported":null,"summary":"The FIPNUM keyword defines the fluid in-place region numbers for each grid block. The simulator can print out summaries of the fluid in-place in each region, the current flow rates between regions, and the cumulative flows between regions.","parameters":[{"index":1,"name":"FIPNUM","description":"FIPNUM defines an array of positive integers greater than or equal to one, that assigns a grid cell to a particular fluid in-place region. The maximum number of FIPNUM and FIP regions is set by the REGDIMS(NMFIPR) or the TABDIMS(NTFIP) keywords(variables) in the RUNSPEC section. If both REGDIMS(NMFIPR) and TABDIMS(NTFIP) have been defined then the maximum of the two is used.","units":{},"default":"1"}],"example":"The example below sets three FIPNUM regions for a 4 x 5 x 2 model.\n--\n-- DEFINE FIPNUM REGIONS FOR ALL CELLS\n--\nFIPNUM\n2 2 1 1 2 2 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n3 3 1 1 3 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n/\nAlternatively the EQUALS keyword could be employed to accomplish the same task, that is:\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nFIPNUM 1 1* 1* 1* 1* 1* 1* / SET REGION 1\nFIPNUM 2 1 2 1 2 1 1 / SET REGION 2\nFIPNUM 3 1 2 1 2 2 2 / SET REGION 3\n/\n| Note In most simulation models the FIPNUM array is used to define various regions in the model for fluid in-place reporting and to identify (or report) the flow between the different regions. When calibrating a model’s in-place volumes it would be useful to use the FIPNUM array combined with the MULTREGP keyword to accomplish this. However, the FIPNUM array cannot be used in the GRID section. A work around is to: Use the FIPNUM array but change the keyword to MULTNUM and incorporate this keyword or INCLUDE file in the GRID section. Use the MULTREGP to calibrate the fluid in-place volumes for the various regions. In the REGIONS section, use the COPY keyword to copy the MULTNUM array to the FIPNUM array. The above work flow will ensure that both arrays and the reporting of fluid in-place regions are consistent. |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"array"},"FIPOWG":{"name":"FIPOWG","sections":["REGIONS"],"supported":false,"summary":"The FIPOWG keyword activates automatic fluid in-place reporting based on the initial oil, gas and water zones defined by the initial equilibration. The fluid contacts on the EQUIL keyword in the SOLUTION section determine the reporting fluid category a grid cell belongs to. For example all grid cells with depths above the gas-oil contact on the EQUIL keyword will be assigned to the gas zone and reported accordingly. Similarly, grid cells with depths between the gas-oil contact and the water-oil contact will be assigned to the oil zone. And finally, grid cells with depths below the oil-water contact will be assigned to the water zone. The simulator can print out summaries of the fluid in-place in each region, the current flow rates between regions, and the cumulative flows between regions.","parameters":[],"example":"--\n-- ACTIVATE OIL, GAS, AND WATER FIP ZONE REPORTING\n--\nFIPOWG\nThe above example switches on automatic fluid in-place reporting based on the initial oil, gas and water zones defined by the initial equilibration.","size_kind":"none","size_count":0},"HBNUM":{"name":"HBNUM","sections":["REGIONS"],"supported":false,"summary":"The HBNUM keyword defines the Herschel-Bulkley rheological property table region numbers for each grid block, as such there must be one entry for each cell in the model. The region number specifies which table of Herschel-Bulkley rheological property data is assigned to a grid block, for when the Polymer option has been invoked via the POLYMER keyword in the RUNSPEC section and the Non-Newtonian Fluid phase has been declared active by the NNEWTF keyword, also in the RUNSPEC section. The FHERCHBL keyword in the PROPS section is used to specify the Herschel-Bulkley rheological property table data.","parameters":[],"example":"","size_kind":"array"},"HWSNUM":{"name":"HWSNUM","sections":["REGIONS"],"supported":false,"summary":"The HWSNUM keyword defines the saturation tables (relative permeability and capillary pressure tables) region numbers for each grid block, as such there must be one entry for each cell in the mode, for when the Surfactant Wettability option has been selected. The keyword may also be used with the Low Salt Brine option, in this case the water wet curves are calculated as a function of the low and high water wet salinity curves. The region number specifies which set of relative permeability tables are used to calculate the relative permeability and capillary pressure in a grid block. Note that the keyword is obligatory if the SURFACTW keyword in the RUNSPEC section has been used to invoke the Surfactant Wettability option.","parameters":[{"index":1,"name":"HWSNUM","description":"HWSNUM defines an array of positive integers assigning a grid cell to a particular saturation table region. The maximum number of HWSNUM regions is set by the NTSFUN variable on the TABDIMS keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"The example below sets three HWSNUM regions for a 4 x 5 x 2 model.\n--\n-- DEFINE HWSNUM REGIONS FOR ALL CELLS\n--\nHWSNUM\n2 2 1 1 2 2 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n3 3 1 1 3 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n/\nAlternatively the EQUALS keyword could be employed to accomplish the same task, that is:\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nHWSNUM 1 1* 1* 1* 1* 1* 1* / SET REGION 1\nHWSNUM 2 1 2 1 2 1 1 / SET REGION 2\nHWSNUM 3 1 2 1 2 2 2 / SET REGION 3\n/","size_kind":"array"},"IMBNUM":{"name":"IMBNUM","sections":["REGIONS"],"supported":false,"summary":"The IMBNUM keyword defines the imbibition saturation tables (relative permeability and capillary pressure tables) region numbers for each grid block, as such there must be one entry for each cell in the model. The region number specifies which set of relative permeability tables (SGFN, SWFN, SOF2, SOF3, SOF32D, SGOF, SLGOF and SWOF) are used to calculate the relative permeability and capillary pressure in a grid block.","parameters":[{"index":1,"name":"IMBNUM","description":"IMBNUM defines an array of positive integers assigning a grid cell to a particular saturation table region. The maximum number of IMBNUM regions is set by the NTSFUN variable on the TABDIMS keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"The example below sets three IMBNUM regions for a 4 x 5 x 2 model using the EQUALS keyword.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nIMBNUM 1 1* 1* 1* 1* 1* 1* / SET REGION 1\nIMBNUM 2 1 2 1 2 1 1 / SET REGION 2\nIMBNUM 3 1 2 1 2 2 2 / SET REGION 3\n/","size_kind":"array"},"IMBNUMMF":{"name":"IMBNUMMF","sections":["REGIONS"],"supported":false,"summary":"The IMBNUMMF keyword defines the imbibition saturation tables (relative permeability and capillary pressure tables) region numbers for flow between the matrix and fracture blocks, for when the HYSTER option on the SATOPTS keyword has been invoked to activate the Hysteresis option, and the Dual Porosity or Dual Permeability models have been activated via the DUALPORO or DUALPERM keywords. All keywords are in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"KRNUM":{"name":"KRNUM","sections":["REGIONS"],"supported":false,"summary":"The KRNUM keyword defines the direction dependent saturation tables (relative permeability and capillary pressure tables) region numbers for each grid block face, as such there must be one entry for each cell in the model. The region number specifies which set of relative permeability tables (SGFN, SWFN, SOF2, SOF3, SOF32D, SGOF, SLGOF and SWOF) are used to calculate the relative permeability and capillary pressure in a grid block. The keyword should only be used if Directional Dependent Saturation Function option has been activated by the DIRECT parameter on the SATOPTS keyword in the RUNSPEC section. Otherwise the standard none directional relative permeability curves should be assigned by the SATNUM keyword in the REGIONS section.","parameters":[{"index":1,"name":"KRNUM","description":"KRNUM defines an array of positive integers assigning a grid cell to a particular saturation table region. The maximum number of KRNUM regions is set by the NTSFUN variable on the TABDIMS keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"The example below sets the directional saturation tables in all three directions using the EQUALS keyword.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nKRNUMX 1 1* 1* 1* 1* 1* 1* / SET X-DIR TABLES\nKRNUMY 2 1* 1* 1* 1* 1* 1* / SET Y-DIR TABLES\nKRNUMZ 3 1* 1* 1* 1* 1* 1* / SET Z-DIR TABLES\n/","size_kind":"array"},"KRNUMMF":{"name":"KRNUMMF","sections":["REGIONS"],"supported":false,"summary":"The KRNUMMF keyword defines the drainage saturation tables (relative permeability and capillary pressure tables) region numbers for flow between the matrix and fracture blocks, for when the Dual Porosity or Dual Permeability models have been activated via the DUALPORO or DUALPERM keywords in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"LSLTWNUM":{"name":"LSLTWNUM","sections":["REGIONS"],"supported":false,"summary":"The LSLTWNUM keyword defines the saturation tables (relative permeability and capillary pressure tables) region numbers for each grid block, as such there must be one entry for each cell in the model. The region number specifies which set of relative permeability tables (SWFN, SOF3 and related keywords) are used to calculate the relative permeability and capillary pressure in a grid block. The keyword should only be used if the Low Salinity option for the Brine model and the Surfactant Wettability option have been activated by the LOWSALT and SURFACTW keywords, respectively, in the RUNSPEC section.","parameters":[{"index":1,"name":"LSLTWNUM","description":"LSLTWNUM defines an array of positive integers assigning a grid cell to a particular saturation table region. The maximum number of LSLTWNUM regions is set by the NTSFUN variable on the TABDIMS keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"The example below sets three LSLTWNUM regions for the model.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nLSLTWNUM 1 1* 1* 1* 1* 1* 1* / SET REGION 1\nLSLTWNUM 2 1 2 1 2 1 1 / SET REGION 2\nLSLTWNUM 3 1 2 1 2 2 2 / SET REGION 3\n/","size_kind":"array"},"LSNUM":{"name":"LSNUM","sections":["REGIONS"],"supported":false,"summary":"The LSNUM keyword defines the saturation tables (relative permeability and capillary pressure tables) region numbers for each grid block, as such there must be one entry for each cell in the model. The region number specifies which set of relative permeability tables (SWFN, SOF3 and related keywords) are used to calculate the relative permeability and capillary pressure in a grid block. The keyword should only be used if the Low Salinity option for the Brine model has been activated in the RUNSPEC section using the LOWSALT keyword.","parameters":[{"index":1,"name":"LSNUM","description":"LSNUM defines an array of positive integers assigning a grid cell to a particular saturation table region. The maximum number of LSNUM regions is set by the NTSFUN variable on the TABDIMS keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"The example below sets three LSNUM regions for the model.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nLSNUM 1 1* 1* 1* 1* 1* 1* / SET REGION 1\nLSNUM 2 1 2 1 2 1 1 / SET REGION 2\nLSNUM 3 1 2 1 2 2 2 / SET REGION 3\n/","size_kind":"array"},"LWSLTNUM":{"name":"LWSLTNUM","sections":["REGIONS"],"supported":false,"summary":"The LWSLTNUM keyword defines the saturation tables (relative permeability and capillary pressure tables) region numbers for each grid block, as such there must be one entry for each cell in the model. The region number specifies which set of relative permeability tables (SWFN, SOF3 and related keywords) are used to calculate the relative permeability and capillary pressure in a grid block. The keyword should only be used if the Low Salinity option for the Brine model has been activated by the LOWSALT kwyword in the RUNSPEC section.","parameters":[{"index":1,"name":"LWSLTNUM","description":"LWSLTNUM defines an array of positive integers assigning a grid cell to a particular saturation table region. The maximum number of LSLTWNUM regions is set by the NTSFUN variable on the TABDIMS keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"The example below sets three LWSLTNUM regions for the model.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nLWSLTNUM 1 1* 1* 1* 1* 1* 1* / SET REGION 1\nLWSLTNUM 2 1 2 1 2 1 1 / SET REGION 2\nLWSLTNUM 3 1 2 1 2 2 2 / SET REGION 3\n/","size_kind":"array"},"LWSNUM":{"name":"LWSNUM","sections":["REGIONS"],"supported":false,"summary":"The LWSNUM keyword defines the saturation tables (relative permeability and capillary pressure tables) region numbers for each grid block, as such there must be one entry for each cell in the model. The region number specifies which set of relative permeability tables (SWFN, SOF3 and related keywords) are used to calculate the relative permeability and capillary pressure in a grid block. The keyword should only be used if the Low Salinity option for the Brine model and the Surfactant Wettability option have been activated by the LOWSALT and SURFACTW keywords, respectively, in the RUNSPEC section.","parameters":[{"index":1,"name":"LWSNUM","description":"LWSNUM defines an array of positive integers assigning a grid cell to a particular saturation table region. The maximum number of LWSNUM regions is set by the NTSFUN variable on the TABDIMS keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"The example below sets three LWSNUM regions for the model.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nLWSNUM 1 1* 1* 1* 1* 1* 1* / SET REGION 1\nLWSNUM 2 1 2 1 2 1 1 / SET REGION 2\nLWSNUM 3 1 2 1 2 2 2 / SET REGION 3\n/","size_kind":"array"},"MISCNUM":{"name":"MISCNUM","sections":["REGIONS"],"supported":null,"summary":"The MISCNUM keyword defines the miscibility region number mixing tables as defined by the TLMIXPAR keyword in the PROPS section, for when the miscibility option has been activated by the MISCIBLE keyword in the RUNSPEC section. MISCNUM also allocates miscible residual oil saturation versus water saturation tables (SORWMIS keyword in the PROPS section) used to calculate the relative permeability and PVT properties for a grid cell.","parameters":[{"index":1,"name":"MISCNUM","description":"MISCNUM defines an array of positive integers greater than or equal to zero, that assign a grid cell to a particular table of mixing parameters as defined by the TLMIXPAR and SORWMIS keywords. A value of zero sets the fluids within a grid cell to be immiscible. The maximum number of MISCNUM regions is set by the NTMIS variable on the MISCIBLE keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"The example below sets three MISCNUM regions in the model on a layer by layer basis, using the EQUALS keyword.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nMISCNUM 1 1* 1* 1* 1* 1 12 / SET REGION 1\nMISCNUM 2 1* 1* 1* 1* 13 55 / SET REGION 2\nMISCNUM 3 1* 1* 1* 1* 56 120 / SET REGION 3\n/","size_kind":"array"},"PENUM":{"name":"PENUM","sections":["REGIONS"],"supported":false,"summary":"The PENNUM keyword defines the petro-elastic region number for each grid block that is used to assign the of petro-elastic coefficients, bulk modulus functions and shear modulus functions as defined by the PECOEFS, PEKTAB and PEGTAB series of keywords in the PROPS section.","parameters":[],"example":"","size_kind":"array"},"PLMIXNUM":{"name":"PLMIXNUM","sections":["REGIONS"],"supported":null,"summary":"The PLMIXNUM keyword defines the polymer region number for each grid block that is used to assign the mixing tables as well as the maximum polymer and salt concentrations, as defined by the PLMIXPAR and PLYMAX keywords in the PROPS section, for when the polymer option has been activated by the POLYMER keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"PLMIXNUM","description":"PLMIXNUM defines an array of positive integers greater than or equal to one, that assign a grid cell to a particular table of mixing parameters as defined by the PLMIXPAR and PLYMAX keywords. The maximum number of PLMIXNUM regions is set by the NPLMIX variable on the REGDIMS keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"The example below sets three PLMIXNUM regions in the model on a layer by layer basis, using the EQUALS keyword.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nPLMIXNUM 1 1* 1* 1* 1* 1 12 / SET REGION 1\nPLMIXNUM 2 1* 1* 1* 1* 13 55 / SET REGION 2\nPLMIXNUM 3 1* 1* 1* 1* 56 120 / SET REGION 3\n/","size_kind":"array"},"PVTNUM":{"name":"PVTNUM","sections":["REGIONS"],"supported":null,"summary":"The PVTNUM keyword defines the PVT region numbers for each grid block, as such there must be one entry for each cell in the model. The region number specifies which set of PVT tables (DENSITY, PVDG, PVDO, PVTG, PVTO, PVCO, PVTW and ROCK) are used to calculate the PVT properties in a grid block.","parameters":[{"index":1,"name":"PVTNUM","description":"PVTNUM defines an array of positive integers assigning a grid cell to a particular PVT region. The maximum number of PVTNUM regions is set by the NTPVT variable on the TABDIMS keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"The example below sets three PVTNUM regions for a 4 x 5 x 2 model.\n--\n-- DEFINE PVTNUM REGION FOR ALL CELLS\n--\nPVTNUM\n2 2 1 1 2 2 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n3 3 1 1 3 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n/\nAlternatively the EQUALS keyword could be employed to accomplish the same task, that is:\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nPVTNUM 1 1* 1* 1* 1* 1* 1* / SET REGION 1\nPVTNUM 2 1 2 1 2 1 1 / SET REGION 2\nPVTNUM 3 1 2 1 2 2 2 / SET REGION 3\n/\nThere third example shows how to ensure the various PVT regions are isolated. First of all define the MULTNUM array in the GRID section and ensure all the regions are isolated.\n-- ==============================================================================\n--\n-- GRID SECTION\n--\n-- ==============================================================================\nGRID\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nMULTNUM 1 1* 1* 1* 1* 1* 1* / SET REGION 1\nMULTNUM 2 1 2 1 2 1 1 / SET REGION 2\nMULTNUM 3 1 2 1 2 2 2 / SET REGION 3\n/\n--\n-- SET TRANSMISSIBILITES ACROSS DIFFERENT RESERVOIRS TO ZERO TO ISOLATE\n-- RESERVOIRS\n--\n-- REGION REGION TRANS DIREC NNC REGION ARRAY\n-- FROM TO MULT OPT OPTS M / F / O\nMULTREGT\n1* 1* 0.0 1* 'ALL' M / ALL REGIONS SEALED\n/\nThen in the REGIONS section copy the MULTNUM array to the PVTNUM array.\n-- ==============================================================================\n--\n-- REGIONS SECTION\n--\n-- ==============================================================================\nREGIONS\n--\n-- COPY AN ARRAY TO ANOTHER ARRAY BASED ON A REGION NUMBER\n--\n-- ARRAY ARRAY REGION REGION ARRAY\n-- FROM TO NUMBER M / F / O\nCOPYREG\nMULTNUM PVTNUM 1 M / COPY MULT TO PVT 1\nMULTNUM PVTNUM 2 M / COPY MULT TO PVT 2\nMULTNUM PVTNUM 3 M / COPY MULT TO PVT 3\n/\nAll the separate PVT regions are now isolated.\n| Note Care should be taken that cells in different PVTNUM regions are not in communication, since the fluid properties are associated with a cell. If for example, a rbbl or a rm3 of oil flows from PVTNUM region 1 to PVTNUM region 2, then the oil properties of that oil will change from the PVT 1 data set to the PVT data set 2. This will result in material balance errors, that may or may not cause numerical issues. To avoid this one should use the MULTNUM (or FLUXNUM, or OPERNUM) array with the MULTREGT array to ensure that the various PVTNUM regions are not in communication. |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"array"},"REGIONS":{"name":"REGIONS","sections":["REGIONS"],"supported":null,"summary":"The REGIONS activation keyword marks the end of the PROPS section and the start of the REGIONS section that defines how various fluid and rock property data defined in the PROPS section are allocated to the individual cells in the model.","parameters":[],"example":"-- ==============================================================================\n--\n-- REGIONS SECTION\n--\n-- ==============================================================================\nREGIONS\nThe above example marks the end of the PROPS section and the start of the REGIONS section in the OPM Flow data input file.","size_kind":"none","size_count":0},"RESIDNUM":{"name":"RESIDNUM","sections":["REGIONS"],"supported":false,"summary":"The RESIDNUM keyword defines the Vertical Equilibrium (“VE”) residual flow calculation saturation tables (relative permeability and capillary pressure tables) region numbers for each grid block, as such there must be one entry for each cell in the model. The region number specifies which set of relative permeability tables (SGFN, SWFN, SOF2, SOF3, SOF32D, SGOF, SLGOF and SWOF) are used to calculate the relative permeability and capillary pressure in a grid block. The keyword should only be used if the Vertical Equilibrium option has been invoked via the VE keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"RESIDNUM","description":"RESIDNUM defines an array of positive integers assigning a grid cell to a particular saturation table region. The maximum number of RESIDNUM regions is set by the NTSFUN variable on the TABDIMS keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"The example below sets three RESIDNUM regions for the model, by first setting all values to one, then setting layers 2 to 10 to two, and finally setting layers 30 to 50 to three.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nSATNUM 1 1* 1* 1* 1* 1* 1* / SET REGION 1\nSATNUM 2 1 2 1 2 2 10 / SET REGION 2\nSATNUM 3 1 2 1 2 30 50 / SET REGION 3\n/","size_kind":"array"},"ROCKNUM":{"name":"ROCKNUM","sections":["REGIONS"],"supported":null,"summary":"The ROCKNUM keyword defines the rock compaction table region numbers for each grid block, as such there must be one entry for each cell in the model. The region number specifies which set of rock compaction tables defined by the ROCKTAB keyword are used to calculate the rock compaction in a grid block.","parameters":[{"index":1,"name":"ROCKNUM","description":"ROCKNUM defines an array of positive integers assigning a grid cell to a particular rock compaction table region. The maximum number of ROCKNUM regions is set by the NTROCC variable on the ROCKCOMP keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"The example below sets three ROCKNUM regions for a 4 x 5 x 2 model.\n--\n-- DEFINE ROCKNUM REGION FOR ALL CELLS\n--\nROCKNUM\n2 2 1 1 2 2 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n3 3 1 1 3 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n/\nAlternatively the EQUALS keyword could be employed to accomplish the same task, that is:\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nROCKNUM 1 1* 1* 1* 1* 1* 1* / SET REGION 1\nROCKNUM 2 1 2 1 2 1 1 / SET REGION 2\nROCKNUM 3 1 2 1 2 2 2 / SET REGION 3\n/","size_kind":"array"},"RPTREGS":{"name":"RPTREGS","sections":["REGIONS"],"supported":false,"summary":"This keyword defines the data in the REGIONS section that is to be printed to the output print file in human readable format. The keyword has two distinct forms, the first of which consists of the keyword followed by a series of integers on the next line indicating the data to be printed (see the first example). This is the original formal in the commercial simulator and was subsequently superseded by the second format. The second format consists of the keyword followed by a series of character strings that indicate the data to be printed. In most cases the character string is the keyword used to load the data in the OPM Flow input deck, for example FIPNUM for the fluid in-place array. Its is anticipated that OPM Flow will eventually support the functionality of the second format only, the first format although recognized will be completely ignored.","parameters":[{"index":1,"name":"EQLNUM","description":"Print the equilibration region array.","units":{},"default":"N/A","value_type":"STRING"},{"index":2,"name":"FIPNUM","description":"Print the fluid in-place array.","units":{},"default":"N/A"},{"index":3,"name":"PVTNUM","description":"Print the PVT table assignment array.","units":{},"default":"N/A"},{"index":4,"name":"SATNUM","description":"Print the saturation function (relative permeability) assignment array.","units":{},"default":"N/A"}],"example":"The first example shows the original format of this keyword; although the keyword and format are recognized by OPM Flow, the format is ignored and is unlikely to be implemented in in the simulator.\n--\n-- DEFINE REGIONS SECTION REPORT OPTION (ORIGINAL FORMAT)\n–\nRPTREGS\n1 2*0 1 3*1 /\nThe next example shows the second format of the keyword which may be supported in a future release of OPM Flow.\n-- DEFINE REGIONS SECTION REPORT OPTIONS\n--\nRPTREGS\nFIPMUM EQLNUM PVTNUM SATNUM /\n| Note This keyword has the potential to produce very large print files that some text editors may have difficulty loading, coupled with the fact that reviewing the data in this format is very cumbersome. A more efficient solution is to load the *.INIT file into OPM ResInsight to view the data graphically, this also has the benefit of being able to filter the grid based on I, J, K ranges and grid properties. |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"fixed","size_count":1,"variadic_record":true},"SATNUM":{"name":"SATNUM","sections":["REGIONS"],"supported":null,"summary":"The SATNUM keyword defines the saturation tables (relative permeability and capillary pressure tables) region numbers for each grid block, as such there must be one entry for each cell in the model. The region number specifies which set of relative permeability tables (SGFN, SWFN, SOF2, SOF3, SOF32D, SGOF, SLGOF and SWOF) are used to calculate the relative permeability and capillary pressure in a grid block.","parameters":[{"index":1,"name":"SATNUM","description":"SATNUM defines an array of positive integers assigning a grid cell to a particular saturation table region. The maximum number of SATNUM regions is set by the NTSFUN variable on the TABDIMS keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"The example below sets three SATNUM regions for a 4 x 5 x 2 model.\n--\n-- DEFINE SATNUM REGIONS FOR ALL CELLS\n--\nSATNUM\n2 2 1 1 2 2 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n3 3 1 1 3 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n/\nAlternatively the EQUALS keyword could be employed to accomplish the same task, that is:\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nSATNUM 1 1* 1* 1* 1* 1* 1* / SET REGION 1\nSATNUM 2 1 2 1 2 1 1 / SET REGION 2\nSATNUM 3 1 2 1 2 2 2 / SET REGION 3\n/","size_kind":"array"},"SURFNUM":{"name":"SURFNUM","sections":["REGIONS"],"supported":false,"summary":"The SURFNUM keyword defines the saturation tables (relative permeability and capillary pressure tables) region numbers for each grid block, as such there must be one entry for each cell in the model. The region number specifies which set of oil-water relative permeability tables (SWFN, SOF2, SOF3, and SWOF) are used to calculate the relative permeability and capillary pressure in a grid block. In this case the SURFNUM allocated tables assume that oil and water are miscible, whereas the SATNUM allocated tables are used to allocate the immiscible saturation tables. To use this keyword the Surfactant option must have been activated by the SURFACT keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"SURFNUM","description":"SURFNUM defines an array of positive integers assigning a grid cell to a particular saturation table region. The maximum number of SURFNUM regions is set by the NTSFUN variable on the TABDIMS keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"The example below sets three SURFNUM for the model.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nSURFNUM 1 1* 1* 1* 1* 1* 1* / SET REGION 1\nSURFNUM 2 1* 1* 1* 1* 1 1 / SET REGION 2\nSURFNUM 3 1* 1* 1* 1* 2 2 / SET REGION 3\n/","size_kind":"array"},"SURFWNUM":{"name":"SURFWNUM","sections":["REGIONS"],"supported":false,"summary":"The SURFWNUM keyword defines the saturation tables (relative permeability and capillary pressure tables) region numbers for each grid block, as such there must be one entry for each cell in the mode, for when the Surfactant Wettability option has been selected. The keyword may also be used with the Low Salt Brine option, in this case the water wet curves are calculated as a function of the low and high water wet salinity curves. The region number specifies which set of relative permeability tables are used to calculate the relative permeability and capillary pressure in a grid block. Note that the keyword is obligatory if the SURFACTW keyword in the RUNSPEC section has been used to invoke the Surfactant Wettability option.","parameters":[{"index":1,"name":"SURFWNUM","description":"SURFWNUM defines an array of positive integers assigning a grid cell to a particular saturation table region. The maximum number of SURFWNUM regions is set by the NTSFUN variable on the TABDIMS keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"The example below sets three SURFWNUM regions for the model.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nSURFWNUM 1 1* 1* 1* 1* 1* 1* / SET REGION 1\nSURFWNUM 2 1 2 1 2 1 1 / SET REGION 2\nSURFWNUM 3 1 2 1 2 2 2 / SET REGION 3\n/","size_kind":"array"},"TNUM":{"name":"TNUM","sections":["REGIONS"],"supported":false,"summary":"The TNUM keyword defines the regions associated with the series of tracers associated with a phase (oil, water, or gas) in the model. The maximum number of tracers for each phase are declared on the TRACER keyword in the RUNSPEC section. Unlike other keywords, the TNUM keyword must be concatenated with the phase and the name of the tracer declared by TRACER keyword in the PROPS section. Table 9.24outlines the format of the TNUM keyword name.","parameters":[{"index":1,"name":"TNUMREG","description":"TUNREG defines an array of positive integers assigning a grid cell to a particular tracer table region. The maximum number of TNUMREG regions is set by the NTTRVD variable on the EQLDIMS keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"First define four passive tracers one for a free gas, one for dissolved gas, one for oil and one to track the water.\n--\n-- DEFINE TRACER NAMES\n--\n-- TRACER TRACER\n-- NAME PHASE\n-- ------ ------\nTRACER\n'GCG' 'GAS' / GAS CAP GAS\n'DGS' 'GAS' / DISOLVED GAS\n'OIL' 'OIL' / OIL\n'WAT' 'WAT' / WAT\n/\nGiven a 100 x 100 x 5 grid with DISGAS activated in the RUNSPEC section, then the following TNUM keywords define the various tracer regions given that NTTRVD equals four on the EQLDIMS keyword in the RUNSPEC section.\n--\n-- DEFINE PASSIVE TRACER CONCENTRATION REGIONS\n--\nTNUMFGCG\n1000*1\n1000*2\n1000*2\n1000*2\n1000*2\n/\nTNUMSDGS\n1000*1\n1000*1\n1000*1\n1000*1\n1000*1\n/\nTNUMFOIL\n1000*3\n1000*3\n1000*3\n1000*3\n1000*3\n/\nTNUMFWAT\n1000*4\n1000*4\n1000*4\n1000*4\n1000*4\n/\nThe keyword name is derived from the TNUM keyword, plus either F or S, plus the tracer name declared in the TRACER keyword. For example for the gas cap (free gas) this would be TNUM+F+GAS to give the TNUMFGAS keyword. And for the dissolved (solution) gas this would be TNUM+S+DGS resulting in the TNUMSDGS keyword.","size_kind":"array"},"TRKPF":{"name":"TRKPF","sections":["REGIONS"],"supported":false,"summary":"The TRKPF keyword defines the regions associated with the series of partition tracers and the partitioning tables allocated to grid blocks in the model, for when the Partitioned Tracer option has been enabled by the PARTTRAC keyword in the RUNSPEC section. The maximum number of tracers for each phase are declared on the TRACERS keyword in the RUNSPEC section. Unlike other keywords, the TRKPF keyword must be concatenated with the name of the tracer declared by TRACER keyword in the PROPS section. Table 9.26outlines the format of the TRKPF keyword name.","parameters":[{"index":1,"name":"TRKPFREG","description":"TRKPFREG defines an array of positive integers assigning a grid cell to a particular tracer table region. The maximum number of TRKPFREG regions is set by the NTTRVD variable on the EQLDIMS keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"First define one mult-partitioned tracer for the water phase.\n--\n-- DEFINE TRACER NAMES\n--\n-- TRACER TRACER TRACER PARTITION NUM ADSOR\n-- NAME PHASE VOLUME PHASE K(P) PHASE\n-- ------ ------ ------ --------- ---- -----\nTRACER\n'WAT' 'WAT' 1* MULT 2 ALL / WAT\n/\nThen for a given a 100 x 100 x 5 grid assign the partitioned tracer regions and K(P) tables, based on two regions.\n--\n-- DEFINE PARTITIONED TRACER REGIONS\n--\nTRKPFWAT\n1000*1\n1000*1\n1000*2\n1000*2\n1000*2\n/\nThe keyword name is derived from the TRKPF keyword, plus the tracer name declared in the TRACER keyword, in this case the keyword name is TRKPFWAT.","size_kind":"array"},"WH2NUM":{"name":"WH2NUM","sections":["REGIONS"],"supported":false,"summary":"The WH2NUM keyword defines the two phase Water-Alternating-Gas (“WAG”) hysteresis tables (relative permeability and capillary pressure tables) region numbers for each grid block, for when the hysteresis option has been activated by the WAGHYSTR variable on the SATOPTS keyword in the RUNSPEC section. The region number specifies which set of relative permeability tables (SGFN, SWFN, SOF2, SOF3, SOF32D, SGOF, SLGOF and SWOF) are used to calculate the relative permeability and capillary pressure in a grid block. Note that this keyword if the two phase water relative permeabilities WAG option.","parameters":[{"index":1,"name":"WH2NUM","description":"WH2NUM defines an array of positive integers assigning a grid cell to a particular saturation table region. The maximum number of WH2NUM regions is set by the NTSFUN variable on the TABDIMS keyword in the RUNSPEC section.","units":{},"default":"Taken from cell allocated SATNUM"}],"example":"The example below sets three WH2NUM regions for a model.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nWH2NUM 1 1* 1* 1* 1* 1* 1* / SET REGION 1\nWH2NUM 2 1 2 1 2 1 1 / SET REGION 2\nWH2NUM 3 1 2 1 2 2 2 / SET REGION 3\n/","size_kind":"array"},"WH3NUM":{"name":"WH3NUM","sections":["REGIONS"],"supported":false,"summary":"The WH3NUM keyword defines the three phase Water-Alternating-Gas (“WAG”) hysteresis tables (relative permeability and capillary pressure tables) region numbers for each grid block, for when the hysteresis option has been activated by the WAGHYSTR variable on the SATOPTS keyword in the RUNSPEC section. The region number specifies which set of relative permeability tables (SGFN, SWFN, SOF2, SOF3, SOF32D, SGOF, SLGOF and SWOF) are used to calculate the relative permeability and capillary pressure in a grid block. Note that this keyword if the three phase water relative permeabilities WAG option.","parameters":[{"index":1,"name":"WH3NUM","description":"WH3NUM defines an array of positive integers assigning a grid cell to a particular saturation table region. The maximum number of WH3NUM regions is set by the NTSFUN variable on the TABDIMS keyword in the RUNSPEC section.","units":{},"default":"Taken from cell allocated SATNUM"}],"example":"The example below sets three WH3NUM regions for a model.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nWH3NUM 1 1* 1* 1* 1* 1* 1* / SET REGION 1\nWH3NUM 2 1 2 1 2 1 1 / SET REGION 2\nWH3NUM 3 1 2 1 2 2 2 / SET REGION 3\n/","size_kind":"array"},"APIVD":{"name":"APIVD","sections":["SOLUTION"],"supported":false,"summary":"The APIVD keyword defines the oil API gravity versus depth tables for each equilibration region when API Tracking as been activated by the API keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"DEPTH","description":"A columnar vector of real monotonically increasing down the column values that defines the depth values for the corresponding API gravity values, API.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":["Length","1"]},{"index":2,"name":"API","description":"A columnar vector of real values that defines the API gravity at the corresponding DEPTH. The American Petroleum Institute (“API”) classifies oils based on an API gravity (γAPI), or degrees API (oAPI), the relationship between relative density (γo) of oil and API gravity (γAPI) is given by: [%gamma SUB { API } ~ = ~ { 141.5 } OVER { %gamma SUB { o }}~-~ 131.5]","units":{"field":"oAPI","metric":"oAPI","laboratory":"oAPI"},"default":"None"}],"example":"Given NTEQUL equals three and NDRXVD is greater than or equal to two on the EQLDIMS keyword in the RUNSPEC section, then the following example defines the bubble-point versus depth functions.\n--\n-- DEPTH API\n-- GRAVITY\n-- ------ --------\nAPIVD\n3000.0 41.10\n8000.0 41.10 / API VS DEPTH EQUIL REGN 01\n-- ------ --------\n3000.0 41.10\n8000.0 38.50 / API VS DEPTH EQUIL REGN 02\n-- ------ --------\n3000.0 41.10\n8000.0 38.50 / API VS DEPTH EQUIL REGN 03\nHere three tables are entered; the first table has a constant API gravity versus depth relationship for equilibration region number one and the other two equilibration regions have the API gravity varying with depth.","size_kind":"fixed","variadic_record":true},"AQANCONL":{"name":"AQANCONL","sections":["SOLUTION"],"supported":false,"summary":"The AQANCON keyword defines how analytical aquifers are connected to a Local Grid Refinement (\"LGR\") grid, this includes the Carter-Tracy, Fetkovich and Constant Flux analytical aquifers, all of which are implemented in OPM Flow. Carter-Tracy analytical aquifers are characterized by the AQUCT keyword in the GRID section and Fetkovich analytical aquifers are defined by either the AQUFET or AQUFETP keywords in the SOLUTION section. Finally, the Constant Flux aquifer is defined by the AQUFLUX keyword in SOLUTION section.","parameters":[{"index":1,"name":"AQUID","description":"AQUID is a positive integer greater than or equal to one and less than the maximum number of analytical aquifers as defined by the NANAQU variable on the AQUDIMS keyword in the RUNSPEC section, that defines the aquifer to be connected to the grid.","units":{},"default":"None","value_type":"INT"},{"index":2,"name":"LGRNAME","description":"A character string of up to eight characters in length that defines the name of the LGR that will connect to an analytical aquifer AQUID. The LGR must have been previously defined by the either the CARFIN (Cartesian LGR grid) keyword, or the RADIN/RADIN4 (radial LGR grid) keyword in the GRID section.","units":{},"default":"None","value_type":"STRING"},{"index":3,"name":"I1","description":"A positive integer that defines the LGR's lower bound of the cells in the I-direction to be connected to the aquifer, and must be greater than or equal to one and less than or equal to I2 and NX on the CARFIN keyword for Cartesian grids.","units":{},"default":"1","value_type":"INT"},{"index":4,"name":"I2","description":"A positive integer that defines the LGR's upper bound of the cells in the I-direction to be connected to the aquifer, and must be greater than or equal to I1 and less than or equal to NX on the CARFIN keyword for Cartesian grids.","units":{},"default":"NX","value_type":"INT"},{"index":5,"name":"J1","description":"A positive integer that defines the LGR's lower bound of the cells in the J-direction to be connected to the aquifer, and must be greater than or equal to one and less than or equal to J2 and NY on the CARFIN keyword for Cartesian grids.","units":{},"default":"1","value_type":"INT"},{"index":6,"name":"J2","description":"A positive integer that defines the LGR's upper bound of the cells in the J-direction to be connected to the aquifer, and must be greater than or equal to JI and less than or equal to NY on the CARFIN keyword for Cartesian grids.","units":{},"default":"NY","value_type":"INT"},{"index":7,"name":"K1","description":"A positive integer that defines the LGR's lower bound of the cells in the K-direction to be to be connected to the aquifer, and must be greater than or equal to one and less than or equal to K2 and NZ on the CARFIN keyword for Cartesian grids.","units":{},"default":"1","value_type":"INT"},{"index":8,"name":"K2","description":"A positive integer that defines the LGR's upper bound of the cells in the K-direction to be connected to the aquifer, and must be greater than or equal to KI and less than or equal to NZ on the CARFIN keyword for Cartesian grids.","units":{},"default":"NZ","value_type":"INT"},{"index":9,"name":"AQUFACE","description":"AQUFACE is a character string that sets the connection “face” of the cells declared by this record and should be set to one of the following: X+, Y+, or Z+ for the positive direction, or X-, Y- or Z- for the negative direction transmissibilities. I+, J+, or K+ for the positive direction, or I-, J- or K- for the negative direction transmissibilities.","units":{},"default":"None","value_type":"STRING"},{"index":10,"name":"AQUFLUX","description":"AQUFLUX is a positive real value that sets the fraction of the total influx between the aquifer and the defined cells declared on this keyword. If defaulted the cell face for each cell is applied and if a values is declared then this values is applied to all cells declared by this record.","units":{"field":"ft2","metric":"m2","laboratory":"cm2"},"default":"1*","value_type":"DOUBLE","dimension":"Length*Length"},{"index":11,"name":"AQUCOEF","description":"AQUCOEF is a real positive values that scales the calculated connection between the aquifer and the cells declared on this record.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0","value_type":"DOUBLE","dimension":"1"},{"index":12,"name":"AQUOPT","description":"AQUOPT is a character string that sets the cell face connection and should be set to one of the following: YES: Aquifer connections can adjoin to active cells allowing for connections inside the reservoir grid. It is not recommended to use this option without thoroughly checking the connections in the model. NO: Aquifer connections cannot adjoin to active cells preventing connections inside the reservoir grid. This is the recommended and the default value.","units":{},"default":"NO","value_type":"STRING"}],"example":"The following example defines aquifer number one connected to the J- face of various cells in the LGROP001 LGR, and a second basal aquifer connected to the K+ face.\n--\n-- LGR ANALYTIC AQUIFER CONNECTION\n--\n-- ID LGR ---------- BOX --------- CONNECT AQF AQF ADJOIN\n-- NUM NAME I1 I2 J1 J2 K1 K2 FACE INFLX MULTI CELLS\nAQANCONL\n1 LGROP001 1 10 1 15 1 10 J- 1* 1.0 'NO' /\n1 LGROP001 1 10 1 15 12 18 J- 1* 1.0 'NO' /\n2 LGROP001 1 10 1 15 20 20 K+ 1* 1.0 'NO' /\n/\nSee the AQUCT keyword in the GRID section for a complete example on defining and connecting a Carter-Tracy aquifer to a simulation grid.\n| Note If the AQANCONL keyword has been utilized in the run deck then OPM Flow will write the AQUIFERA array to the *.INIT file in order to visualize the aquifer connections in OPM ResInsight. This is accomplished by setting the AQUIFERA value to 2(AQUID-1) for cells connected to aquifer AQUID. If a cell is connected to multiple analytical aquifers then AQUIFERA is summed for all aquifers connected to a cell. Note that connecting cells to multiple aquifers is best avoided. |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":12,"size_kind":"list"},"AQANNC":{"name":"AQANNC","sections":["SOLUTION"],"supported":false,"summary":"AQANNC defines the analytic aquifer non-neighbor connections.","parameters":[{"index":1,"name":"AQUIFER_NUMBER","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"IX","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"IY","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"IZ","description":"","units":{},"default":"","value_type":"INT"},{"index":5,"name":"AREA","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Length*Length"}],"example":"","expected_columns":5,"size_kind":"list"},"AQANTRC":{"name":"AQANTRC","sections":["SOLUTION"],"supported":false,"summary":"The AQANTRC keyword defines the initial tracer concentrations for analytic aquifers that have previously been defined by the AQCT keyword in the GRID, PROPS, or SOLUTION sections for Carter-Tracy analytical aquifers, or the AQFET and AQFETP keywords in the SOLUTION section for Fetkovich analytical aquifers.","parameters":[{"index":1,"name":"AQUIFER_ID","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"TRACER","description":"","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"VALUE","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","expected_columns":3,"size_kind":"list"},"AQUALIST":{"name":"AQUALIST","sections":["SOLUTION"],"supported":false,"summary":"The AQUALIST keyword defines named lists of analytic aquifers identified by aquifer numbers for greater readability in the output.","parameters":[{"index":1,"name":"AQUIFER_LIST","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"LIST","description":"","units":{},"default":"","value_type":"INT"}],"example":"","size_kind":"list","variadic_record":true},"AQUCHGAS":{"name":"AQUCHGAS","sections":["SOLUTION","SCHEDULE"],"supported":false,"summary":"The AQUCHGAS keyword defines the properties of constant pressure gas analytical aquifers.","parameters":[{"index":1,"name":"AQUIFER_ID","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"DATUM_DEPTH","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":3,"name":"GAS_PRESSURE","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":4,"name":"AQUIFER_PROD_INDEX","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"GasSurfaceVolume/Time*Pressure"},{"index":5,"name":"TABLE_NUM","description":"","units":{},"default":"1","value_type":"INT"},{"index":6,"name":"TEMPERATURE","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Temperature"}],"example":"","expected_columns":6,"size_kind":"list"},"AQUCHWAT":{"name":"AQUCHWAT","sections":["SOLUTION","SCHEDULE"],"supported":false,"summary":"The AQUCHWAT keyword defines the properties of constant pressure water analytical aquifers.","parameters":[{"index":1,"name":"AQUIFER_ID","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"DATUM_DEPTH","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":3,"name":"INPUT_4","description":"","units":{},"default":"","value_type":"STRING"},{"index":4,"name":"ITEM4","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":5,"name":"AQUIFER_PROD_INDEX","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time*Pressure"},{"index":6,"name":"TABLE_NUM","description":"","units":{},"default":"1","value_type":"INT"},{"index":7,"name":"INIT_SALT_CONC","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"Mass/LiquidSurfaceVolume"},{"index":8,"name":"MINIMUM","description":"","units":{},"default":"-1e+200","value_type":"DOUBLE"},{"index":9,"name":"MAXIMUM","description":"","units":{},"default":"1e+200","value_type":"DOUBLE"},{"index":10,"name":"IGNORE_CAP_PRESSURE","description":"","units":{},"default":"NO","value_type":"STRING"},{"index":11,"name":"MIN_FLOW_PR_CONN","description":"","units":{},"default":"-1e+200","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time"},{"index":12,"name":"MAX_FLOW_PR_CONN","description":"","units":{},"default":"1e+200","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time"},{"index":13,"name":"REMOVE_DEPTH_TERM","description":"","units":{},"default":"NO","value_type":"STRING"},{"index":14,"name":"IMPORT_MAX_MIN_FLOW_RATE","description":"","units":{},"default":"0","value_type":"INT"},{"index":15,"name":"TEMPERATURE","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Temperature"}],"example":"","expected_columns":15,"size_kind":"list"},"AQUFET":{"name":"AQUFET","sections":["SOLUTION"],"supported":false,"summary":"The AQUFET keyword defines Fetkovich287\n Fetkovich, M. J. “A Simplified Approach to Water Influx Calculations - Finite Aquifer Systems,” Journal of Petroleum Technology, (1971) 23, No. 7, 814-828. analytical aquifers, the aquifer properties, together with the cell connections to the aquifer. Each row entry in the AQUFETP keyword defines one Fetkovich analytical aquifer and one cell face to be connected to the aquifer.","parameters":[{"index":1,"name":"DATUM","description":"DATUM is a single positive value that defines the Fetkovich reference datum depth for PRESS.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":"Length"},{"index":2,"name":"PRESS","description":"PRESS is a single positive value that defines the aquifer pressure at DATUM. If PRESS is defaulted then the simulator will set the aquifer’s initial reservoir pressure to be in equilibrium with the cells the aquifer is contacted to. Defaulting this parameter will avoid inconsistent equilibration pressures between the reservoir cells and the aquifer.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1*","value_type":"DOUBLE","dimension":"Pressure"},{"index":3,"name":"PORV","description":"A real positive value that defines the initial water volume of the aquifer.","units":{"field":"stb","metric":"sm3","laboratory":"scc"},"default":"None","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume"},{"index":4,"name":"COMP","description":"COMP is a real number defining the total compressibility (Ct) of the aquifer, that is the rock compressibility (Cf) plus the water compressibility (Cw) at the aquifer datum pressure (DATUM) and is defined as: [C sub{t}~=~ C sub{f}`+`C sub {w}]","units":{"field":"1/psia","metric":"1/barsa","laboratory":"1/atma"},"default":"None","value_type":"DOUBLE","dimension":"1/Pressure"},{"index":5,"name":"PI","description":"A real positive number that defines the aquifer productivity index based on the aquifer influx rate per unit pressure drop.","units":{"field":"stb/d/psia","metric":"sm3/barsa","laboratory":"scc/hr/atma"},"default":"None","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Pressure*Time"},{"index":6,"name":"PVTW","description":"A positive integer that defines the aquifer’s PVTW water property table.","units":{},"default":"1","value_type":"INT"},{"index":7,"name":"I1","description":"A positive integer that defines the lower bound of the cells in the I-direction to be connected to the aquifer and must be greater than or equal to one and less than or equal to I2 and NX.","units":{},"default":"1","value_type":"INT"},{"index":8,"name":"I2","description":"A positive integer that defines the upper bound of the cells in the I-direction to be connected to the aquifer and must be greater than or equal to I1 and less than or equal to NX","units":{},"default":"NX","value_type":"INT"},{"index":9,"name":"J1","description":"A positive integer that defines the lower bound of the cells in the J-direction to be connected to the aquifer and must be greater than or equal to one and less than or equal to J2 and NY.","units":{},"default":"1","value_type":"INT"},{"index":10,"name":"J2","description":"A positive integer that defines the upper bound of the cells in the J-direction to be connected to the aquifer and must be greater than or equal to JI and less than or equal to NY.","units":{},"default":"NY","value_type":"INT"},{"index":11,"name":"K1","description":"A positive integer that defines the lower bound of the cells in the K-direction to be to be connected to the aquifer and must be greater than or equal to one and less than or equal to K2 and NZ.","units":{},"default":"1","value_type":"INT"},{"index":12,"name":"K2","description":"A positive integer that defines the upper bound of the cells in the K-direction to be connected to the aquifer and must be greater than or equal to KI and less than or equal to NZ.","units":{},"default":"NZ","value_type":"INT"},{"index":13,"name":"AQUFACE","description":"AQUFACE is a character string that sets the connection “face” of the cells declared by this record and should be set to one of the following: X+, Y+, or Z+ for the positive direction, or X-, Y- or Z- for the negative direction transmissibilities. I+, J+, or K+ for the positive direction, or I-, J- or K- for the negative direction transmissibilities.","units":{},"default":"None","value_type":"STRING"},{"index":14,"name":"SALTCON","description":"SALTCON is a real positive number that defines the initial salt concentration in the aquifer. This variable is ignored by OPM Flow.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"0.0","value_type":"DOUBLE","dimension":"Concentration"}],"example":"Given the following grid and aquifer dimensions in the RUNSPEC section:\n-- ==============================================================================\n--\n-- RUNSPEC SECTION\n--\n-- ==============================================================================\nRUNSPEC --\n-- MAX MAX MAX\n-- NDIVIX NDIVIY NDIVIZ\nDIMENS\n20 1 5 /\n-- AQF AQF AQF AQF AQF AQF AQF AQF\n-- MXAQN MXNAQC NIFTBL NRIFTB NANAQU NCAMAX MXNALI MXAAQL\nAQUDIMS\n1* 1* 5 100 1 1* 1* 1* /\nThe Fetkovich Analytical aquifer is defined in the SOLUTION sections as:\n-- ==============================================================================\n--\n-- SOLUTION SECTION\n--\n-- ==============================================================================\nSOLUTION --\n-- FETKOVICH AQUIFER DESCRIPTION AND CONNECTIONS\n--\n-- DATUM AQF AQF AQF AQF AQF -------- BOX ------- CONNECT SALT\n-- DEPTH PRESS VOLM COMP PI PVT I1 I2 J1 J2 K1 K2 FACE CONC\n--\nAQUFET\n1130. 1* 1.0E+12 3.0E-5 500E3 1 1 1 1 1 1 1 'J-' /\nHere one Fetkovich Analytical aquifer is connected to a single cell (1, 1, 1) at the J- face (or X- face) of the grid.\n| Note If the model is unstable then this may be due to an aquifer not being in equilibrium with the connecting reservoir blocks, for example the aquifer is connected to only hydrocarbon reservoir cells. Try commenting out the aquifer and see if this resolves the instabilities. |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":14,"size_kind":"list"},"AQUFETP":{"name":"AQUFETP","sections":["SOLUTION","SCHEDULE"],"supported":null,"summary":"The AQUFETP keyword defines Fetkovich288\n Fetkovich, M. J. “A Simplified Approach to Water Influx Calculations - Finite Aquifer Systems,” Journal of Petroleum Technology, (1971) 23, No. 7, 814-828. analytical aquifers and the aquifer properties. Each row entry in the AQUFETP keyword defines one Fetkovich analytical aquifer. In order to fully define this type of aquifer, the aquifer must be connected to the reservoir using the AQUANCON keyword in the GRID or SOLUTION sections.","parameters":[{"index":1,"name":"AQUID","description":"A positive integer greater than or equal to one and less than or equal to NANAQ on the AQUDIMS keyword in the RUNSPEC section, that defines the Fetkovich aquifer number.","units":{},"default":"1","value_type":"INT"},{"index":2,"name":"DATUM","description":"DATUM is a single positive value that defines the Fetkovich reference datum depth for PRESS.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":"Length"},{"index":3,"name":"PRESS","description":"PRESS is a single positive value that defines the aquifer pressure at DATUM. If PRESS is defaulted then the simulator will set the aquifer’s initial reservoir pressure to be in equilibrium with the cells the aquifer is contacted to. Defaulting this parameter will avoid inconsistent equilibration pressures between the reservoir cells and the aquifer.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1*","value_type":"DOUBLE","dimension":"Pressure"},{"index":4,"name":"PORV","description":"A real positive value that defines the initial water volume of the aquifer.","units":{"field":"stb","metric":"sm3","laboratory":"scc"},"default":"None","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume"},{"index":5,"name":"COMP","description":"COMP is a real number defining the total compressibility (Ct) of the aquifer, that is the rock compressibility (Cf) plus the water compressibility (Cw) at the aquifer datum pressure (DATUM) and is defined as: [C sub{t}~=~ C sub{f}`+`C sub {w}]","units":{"field":"1/psia","metric":"1/barsa","laboratory":"1/atma"},"default":"None","value_type":"DOUBLE","dimension":"1/Pressure"},{"index":6,"name":"PI","description":"A real positive number that defines the aquifer productivity index based on the aquifer influx rate per unit pressure drop.","units":{"field":"stb/d/psia","metric":"sm3/d/barsa","laboratory":"scc/hr/atma"},"default":"None","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Pressure*Time"},{"index":7,"name":"PVTW","description":"A positive integer that defines the aquifer’s PVTW water property table.","units":{},"default":"1","value_type":"INT"},{"index":8,"name":"SALTCON","description":"SALTCON is a real positive number that defines the initial salt concentration in the aquifer, for when the simulator's Brine Model has been activated via the BRINE keyword in the RUNSPEC section. This variable is ignored by OPM Flow.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"0.0","value_type":"DOUBLE","dimension":"Concentration"},{"index":9,"name":"TEMP","description":"TEMP is a real positive number that defines the initial temperature of the aquifer at DATUM for use with OPM Flow's thermal option. The THERMAL keyword in the RUNSPEC section must be activated to use this option.","units":{"field":"oF","metric":"oC","laboratory":"oC"},"default":"1*","value_type":"DOUBLE","dimension":"Temperature"}],"example":"Given the following grid and aquifer dimensions in the RUNSPEC section:\n-- ==============================================================================\n--\n-- RUNSPEC SECTION\n--\n-- ==============================================================================\nRUNSPEC\n--\n-- MAX MAX MAX\n-- NDIVIX NDIVIY NDIVIZ\nDIMENS\n20 1 5 /\n-- AQF AQF AQF AQF AQF AQF AQF AQF\n-- MXAQN MXNAQC NIFTBL NRIFTB NANAQU NCAMAX MXNALI MXAAQL\nAQUDIMS\n1* 1* 5 100 1 1* 1* 1* /\nThe Fetkovich analytical aquifer is defined in the SOLUTION sections as:\n-- ==============================================================================\n--\n-- SOLUTION SECTION\n--\n-- ==============================================================================\nSOLUTION --\n-- FETKOVICH AQUIFER DESCRIPTION\n--\n-- ID DATUM AQF AQF AQF AQF AQF SALT\n-- NUM DEPTH PRESS VOLM COMP PI PVT CONC\n--\nAQUFETP\n1 1130. 1* 1.0E+12 3.0E-5 500E3 1 0.0 /\n/\nAnd the connection of the aquifer is set in the GRID or the SOLUTION sections as:\n--\n-- ANALYTIC AQUIFER CONNECTION\n--\n-- ID ---------- BOX --------- CONNECT AQF AQF ADJOIN\n-- NUMBER I1 I2 J1 J2 K1 K2 FACE INFLX MULTI CELLS\nAQUANCON\n1 1 1 1 1 1 1 J- 1.0 1.0 'NO' /\n/\nHere one Fetkovich analytical aquifer is connected to a single cell (1, 1, 1) at the J- face (or Y- face) of the cell.\n| Note If the model is unstable then this may be due to an aquifer not being in equilibrium with the connecting reservoir blocks, for example if the aquifer is connected to some hydrocarbon reservoir cells. Try commenting out the aquifer and see if this resolves the instabilities, and if so amend the aquifer connections accordingly. |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":9,"size_kind":"list"},"AQUFLUX":{"name":"AQUFLUX","sections":["SOLUTION","SCHEDULE"],"supported":null,"summary":"The AQUFLUX keyword defines the properties of Constant Flux Analytical Aquifers, that allows for a constant water influx to the connected grid blocks. This type of aquifer is connected to the model using either the AQUANCON keyword for global cells, or the AQUANCONL keyword for cells belonging to a Local Grid Refinement (\"LGR\"), both the aforementioned keywords are in the GRID and SOLUTION sections. The keyword itself may be utilized in both the SOLUTION and SCHEDULE sections, with subsequent entries overwriting the previous entry.","parameters":[{"index":1,"name":"AQUID","description":"A positive integer greater than or equal to one and less than or equal to NANAQ on the AQUDIMS keyword in the RUNSPEC section, that defines the AQUFLUX aquifer number.","units":{"field":"stb/day/ft2","metric":"sm3/day/m2","laboratory":"scc/hour/cm2"},"default":"1","value_type":"INT"},{"index":2,"name":"FLUX","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time*Length*Length"},{"index":3,"name":"SALTCON","description":"SALTCON is a real positive number that defines the initial salt concentration in the aquifer, for when with simulator's Brine Model has been activated via the BRINE keyword in the RUNSPEC section. This variable is ignored by OPM Flow.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"0.0","value_type":"DOUBLE","dimension":"Density"},{"index":4,"name":"TEMP","description":"TEMP is a real positive number that defines the initial temperature of the aquifer for use with OPM Flow's thermal option. The THERMAL keyword in the RUNSPEC section must be activated to use this option. If the THERMAL keyword is absent from the input deck, then the parameter is ignored.","units":{"field":"oF","metric":"oC","laboratory":"oC"},"default":"1*","value_type":"DOUBLE","dimension":"Temperature"},{"index":5,"name":"PRESS","description":"PRESS is a single positive value that defines the aquifer pressure for use with OPM Flow's thermal option. The THERMAL keyword in the RUNSPEC section must be activated to use this option. If the THERMAL keyword is absent from the input deck, then the parameter is ignored.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1*","value_type":"DOUBLE","dimension":"Pressure"}],"example":"Given a total of five analytical aquifers as declared by the NANAQ parameter on the AQUDIMS keyword being set to five, of which three are Constant Flux Aquifers and two Carter-Tracy Aquifers, then:\n--\n-- CONSTANT FLUX AQUIFER DESCRIPTION\n--\n-- ID WATER SALT AQF AQU\n-- NUM INFLUX CONC TEMP PRES\n--\nAQUFLUX\n1 0.0004 1* 1* 1* /\n2 0.0005 1* 1* 1* /\n3 0.0003 1* 1* 1* /\n/\n--\n-- CARTER-TRACY AQUIFER DESCRIPTION\n--\n-- ID DATUM AQF AQF AQF AQF AQF AQF INFL PVT AQU\n-- NUM DEPTH PRESS PERM PORO RCOMP RE DZ ANGLE NUM TAB\n--\nAQUCT\n4 2000.0 269 100.0 0.30 3.0e-5 330 10.0 360.0 1 2 /\n5 2000.0 269 100.0 0.30 3.0e-5 330 10.0 360.0 1 2 /\n/\nDefines three Constant Flux Aquifers and three Carter-Tracy Aquifers, and the connection of the aquifers are set in the GRID or SOLUTION sections via:\n--\n-- ANALYTIC AQUIFER CONNECTION\n--\n-- ID ---------- BOX --------- CONNECT AQF AQF ADJOIN\n-- NUMBER I1 I2 J1 J2 K1 K2 FACE INFLX MULTI CELLS\nAQUANCON\n1 1 198 1 14 1 10 J- 1* 1.0 'NO' /\n2 1 198 1 14 12 22 J- 1* 1.0 'NO' /\n3 1 198 1 14 23 54 J- 1* 1.0 'NO' /\n4 1 198 1 14 61 70 J- 1* 1.0 'NO' /\n5 1 198 15 172 71 71 K+ 1* 1.0 'NO' /\n/\n| [q_w`=`AQUFLUX(AQFLUX) ` times ` A_( i, j, k) ` times ` AQUANCON(AQUCOEF)] | (10.14) |\n|----------------------------------------------------------------------------|---------|","expected_columns":5,"size_kind":"list"},"BC":{"name":"BC","sections":["SOLUTION"],"supported":false,"summary":"The BC keyword defines the boundary conditions for the model, and can be used to set boundary conditions for when external influx or efflux volumes are influencing the reservoir pressure and production history. For example, when the average reservoir pressure remains constant throughout the production period due to water influx, or gas migration from an external source.","parameters":[{"index":1,"name":"I1","description":"A positive integer that defines the lower bound of the grid in the I-direction for which the boundary conditions are to be applied, must be greater than or equal 1 and less than or equal to I2 and NX.","units":{},"default":"1","value_type":"INT"},{"index":2,"name":"I2","description":"A positive integer that defines the upper bound of the grid in the I-direction for which the boundary conditions are to be applied, must be greater than or equal to II and less than or equal to NX","units":{},"default":"NX","value_type":"INT"},{"index":3,"name":"J1","description":"A positive integer that defines the lower bound of the grid in the J-direction for which the boundary conditions are to be applied, must be greater than or equal 1 and less than or equal to J2 and NY.","units":{},"default":"1","value_type":"INT"},{"index":4,"name":"J2","description":"A positive integer that defines the upper bound of the grid in the J-direction for which the boundary conditions are to be applied, must be greater than or equal to JI and less than or equal to NY.","units":{},"default":"NY","value_type":"INT"},{"index":5,"name":"K1","description":"A positive integer that defines the lower bound of the grid in the K-direction for which the boundary conditions are to be applied, must be greater than or equal to one and less than or equal to K2 and NZ.","units":{},"default":"1","value_type":"INT"},{"index":6,"name":"K2","description":"A positive integer that defines the upper bound of the grid in the K-direction for which the boundary conditions are to be applied, must be greater than or equal to KI and less than or equal to NZ.","units":{},"default":"NZ","value_type":"INT"},{"index":7,"name":"DIRECT","description":"A character string that defines the direction to apply the boundary conditions, and should be set to one of the following X, Y, or Z for the positive direction, or X-, Y- or Z- for the negative direction.","units":{},"default":"None","value_type":"STRING"},{"index":8,"name":"TYPE","description":"A defined character string that defines the type of boundary condition to be applied, and should be set to one of the following character strings: DIRICHLET: for a user defined boundary conditions. In this case, items (1) through (7) must be set, together with PHASE for the fluid type, and PRESS and TEMP for the constant pressure and temperature boundary conditions. This option is currently not supported but will be available in the next release. FREE: for the initial state of the boundary to be kept throughout the simulation, that is a constant boundary condition. For this option only items (1) through (7) need to be defined. RATE: for the boundary to have a constant influx or efflux rate. Again items (1) through (7) are required, plus PHASE for the fluid type, and RATE to set the PHASE rate. Only the FREE and RATE options are currently supported; however the next release will support the DIRICHLET option.","units":{},"default":"None","value_type":"STRING","options":["DIRICHLET","FREE","RATE"]},{"index":9,"name":"PHASE","description":"A defined character string that sets fluid type used in the boundary calculations, and should be set to one of the following character strings: GAS: the gas phase will be used to control the boundary conditions for when the TYPE has been set to DIRICHLET or RATE. OIL: the oil phase will be used to control the boundary conditions for when the TYPE has been set to DIRICHLET or RATE. WATER or WAT: the water phase will be used to control the boundary conditions for when the TYPE has been set to DIRICHLET or RATE. PHASE must be declared if TYPE has been set to either DIRICHLET or RATE.","units":{},"default":"None","value_type":"STRING","options":["GAS","OIL","WAT"]},{"index":10,"name":"RATE","description":"A real value that defines the constant surface oil, gas or water rate to be injected or withdrawn at the boundary, for when TYPE has been set to RATE. Note a negative value implies an injection rate, whereas, a positive value indicates a withdrawal rate.","units":{"field":"Liquid: stb/day Gas: Mscf/day","metric":"Liquid: sm3/day Gas: sm3/day","laboratory":"Liquid: scc/hr Gas: scc/hr"},"default":"0,0","value_type":"DOUBLE","dimension":"Mass/Time*Length*Length"},{"index":11,"name":"PRESS","description":"PRESS is a real positive value that defines the constant pressure boundary condition. PRESS should only be entered if TYPE has been set to DIRICHLET. If the pressure at the boundary is less than PRESS, then the fluid type declared via PHASE will flow across the boundary. The default value of 1* will use the simulator's calculated value based on data entered via the EQUIL keyword in the SOLUTION section.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1*","value_type":"DOUBLE","dimension":"Pressure"},{"index":12,"name":"TEMP","description":"TEMP is a real positive number that defines the constant temperature boundary condition. TEMP should only be entered if TYPE has been set to DIRICHLET. The default value of 1* will use the simulator's calculated value based on data entered via one of the following reservoir temperature keywords: RTEMP, RTEMPA, RTEMPVD, TEMPI, or TEMPVD, in the SOLUTION section. Note that all of the aforementioned reservoir temperature keywords, except for TEMPI, may also be used in the PROPS section as well.","units":{"field":"oF","metric":"oC","laboratory":"oC"},"default":"1*","value_type":"DOUBLE","dimension":"Temperature"}],"example":"The first example shows how to set a constant pressure boundary using TYPE equal to FREE:\n--\n-- DEFINE MODEL BOUNDARY CONDITIONS (OPM FLOW SOLUTION GRID KEYWORD)\n--\n-- ---------- BOX --------- BC BC BC BC BC BC\n-- I1 I2 J1 J2 K1 K2 DIRC TYPE PHASE RATE PRESS TEMP\nBC\n1 1 1 1* 1 1* X- FREE 1* 1* 1* 1* /\n1 1* 1 1 1 1* Y FREE /\n/\nWith this option it is only necessary to define the boundary cells and all the other parameters (PHASE, RATE, PRESS, and TEMP) can be defaulted, as they are ignored for when TYPE equals FREE.\nThe next example is based on NX, NY and NZ equal to 20, 1, 10 respectively, on the DIMENS keyword in the RUNSPEC section, and shows how different boundary types can be assigned to different parts of the model.\n--\n-- DEFINE MODEL BOUNDARY CONDITIONS (OPM FLOW SOLUTION GRID KEYWORD)\n--\n-- ---------- BOX --------- BC BC BC BC BC BC\n-- I1 I2 J1 J2 K1 K2 DIRC TYPE PHASE RATE PRESS TEMP\nBC\n1 1 1 1 1 10 X- RATE GAS 1* 256.0 100.0 /\n20 20 1 1 1 10 X FREE 4* /\n/\nThe last example shows how the DIRICHLET boundary condition option may be used:\n--\n-- DEFINE MODEL BOUNDARY CONDITIONS (OPM FLOW SOLUTION GRID KEYWORD)\n--\n-- ---------- BOX --------- BC BC BC BC BC BC\n-- I1 I2 J1 J2 K1 K2 DIRC TYPE PHASE RATE PRESS TEMP\nBC\n1 1 1 1* 1 1* X- DIRICHLET WAT 1* 256.0 100.0 /\n1 1* 1 1 1 1* Y DIRICHLET WAT 1* 1* 100.0 /\n/\nHere, the first line sets both the pressure and temperature at the boundary, and the second line defaults the pressure entry, so that the simulator calculated initial boundary pressure will be used.\n| Note This is an OPM Flow specific keyword and will therefore cause an error in the commercial simulator. |\n|----------------------------------------------------------------------------------------------------------|","expected_columns":12,"size_kind":"list"},"DATUM":{"name":"DATUM","sections":["SOLUTION"],"supported":null,"summary":"The DATUM keyword defines the datum depth for the model. This allows for all grid block potentials (depth corrected pressures) to be calculated at a common depth.","parameters":[{"index":1,"name":"DATUM","description":"DATUM is a single positive value that defines the datum depth for the model.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":"Length"}],"example":"-- DATUM\n-- DEPTH\n-- ------\nDATUM\n5000.0 / DATUM DEPTH FOR REPORTING\nThe above example defines the datum for the model to be 5000.0","expected_columns":1,"size_kind":"fixed","size_count":1},"DATUMR":{"name":"DATUMR","sections":["SOLUTION"],"supported":null,"summary":"The DATUMR keyword defines the datum depth for each fluid in-place region (FIPNUM) declared in the model. This allows for all grid block potentials (depth corrected pressures) to be calculated at a common depth within a FIPNUM region.","parameters":[{"index":1,"name":"DATUMR","description":"DATUMR is a vector of positive values that defines the datum depth for each fluid in-place region.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None"}],"example":"--\n-- DATUM\n-- DEPTH\n-- ------\nDATUMR\n4800.0\n4900.0\n5000.0 / DATUM DEPTH FOR REPORTING\nThe above example defines the datum depth for three FIPNUM regions, for when NTFIP has been set equal to three on the REGDIMS keyword in the RUNSPEC section.","size_kind":"fixed","size_count":1},"DATUMRX":{"name":"DATUMRX","sections":["SOLUTION"],"supported":null,"summary":"The DATUMRX keyword defines the datum depth for each fluid in-place family region defined by the FIP keyword. This allows for all grid block potentials (depth corrected pressures) to be calculated at a common depth within a given FIP region. The FIP keyword in the REGIONS section allows one to define additional sets of fluid in-place regions to the standard FIPNUM keyword. For example, one could use FIPNUM to define the reservoir layers as fluid in-place regions and the FIP keyword to define the fluid in-place region for fault blocks.","parameters":[{"index":1,"name":"FIPNAME","description":"A character string of up to five characters in length that defines the FIP family name for which the datum depth data is being defined. The default value of 1* will set DATUMR to the standard FIPNUM region numbers.","units":{},"default":"1*","value_type":"STRING"},{"index":2,"name":"DATUMR","description":"DATUMR is a vector of positive values that defines the datum depth for each fluid in-place family region. There must be one entry for each region in the FIP family name. A maximum of NTFIP values, as declared by the REGDIMS keyword in the RUNSPEC section, may be entered for each FIPNAME entry.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":"Length"}],"example":"--\n-- FIP DATUM\n-- NAME DEPTH\nDATUMRX\n'FLTBL' 5000.0 5000.0 5000.0 5000.0 / DATUM DEPTH FOR REPORTING\n'LICBL' 5000.0 5050.0 / DATUM DEPTH FOR REPORTING\n/\nThe above example defines the datum depth for two FIP families, FLTBL and LICBL, with the datum set to a constant 5000.0 psia for FLTBL family and different values for each of the regions in the LICBL family of regions.","size_kind":"list","variadic_record":true},"DYNAMICR":{"name":"DYNAMICR","sections":["SOLUTION","SCHEDULE"],"supported":false,"summary":"The DYNAMICR keyword marks the start of a Dynamic Region section and defines the parameters used for Dynamic Regions that allows for property and reporting regions to vary as the run progresses, based on the parameters and logic defined by this keyword and section. A Dynamic Region section is terminated by the ENDDYN keyword in the SOLUTION or SCHEDULE sections.","parameters":[],"example":"","size_kind":"none","size_count":0},"ENDDYN":{"name":"ENDDYN","sections":["SOLUTION","SCHEDULE"],"supported":false,"summary":"The ENDDYN keyword marks the end of a Dynamic Region section that was started with the DYNAMICR keyword in the SOLUTION or SCHEDULE sections. Dynamic Regions allow for property and reporting regions to vary as the run progresses, based on the parameters and logic defined within the section.","parameters":[],"example":"","size_kind":"none","size_count":0},"EQUIL":{"name":"EQUIL","sections":["SOLUTION"],"supported":null,"summary":"This keyword defines the parameters used to initialize the model for when equilibration is calculated by OPM Flow. This is the standard methodology to initialize a model, the non-standard formulation of entering the pressures and saturations for each grid cell is seldom employed in the industry. The keyword can be used with all grid types.","parameters":[{"index":1,"name":"DATUM","description":"DATUM is a single positive value that defines the reference datum depth for PRESS.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"0.0","value_type":"DOUBLE","dimension":"Length"},{"index":2,"name":"PRESS","description":"PRESS is a single positive value that defines the pressure at DATUM. If the DATUM depth lies above the GOC then PRESS is the pressure with respect to the gas phase. If the DATUM depth is below OWC then PRESS refers to the water phase pressure. Otherwise, PRESS refers to the oil phase pressure.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"0.0","value_type":"DOUBLE","dimension":"Pressure"},{"index":3,"name":"WATCONT","description":"For three phase runs containing oil, gas and water WATCONT is the depth of the oil-water contact (OWC). For two phase runs containing oil and water WATCONT is the depth of the oil-water contact (OWC). For two phase runs containing gas and water WATCONT is the depth of the gas-water contact (GWC).","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"0.0","value_type":"DOUBLE","dimension":"Length"},{"index":4,"name":"WATCAP","description":"For three phase runs containing oil, gas and water WATCAP is the oil-water capillary pressure at the OWC. For two phase runs containing oil and water WATCAP is the oil-water capillary pressure at the OWC. For two phase runs containing gas and water WATCAP is the gas-water capillary pressure at the GWC","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"0.0","value_type":"DOUBLE","dimension":"Pressure"},{"index":5,"name":"GASCONT","description":"For three phase runs containing oil, gas and water GASCONT is the depth of the gas-oil contact (GOC). Note in cases where there is no gas cap (or free gas) then GASCONT should be set to a value shallower than the top of the reservoir. In cases where there is initially no oil zone, as for a gas condensate field for example, the GASCONT should be set to the same depth as WATCONT. For two phase runs containing oil and water, or gas and water, GASCONT is ignored.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"0.0","value_type":"DOUBLE","dimension":"Length"},{"index":6,"name":"GASCAP","description":"For three phase runs containing oil, gas and water GASCAP is the gas-oil capillary pressure at the GWC. For two phase runs containing oil and water, or gas and water, GASCAP is ignored.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"0.0","value_type":"DOUBLE","dimension":"Pressure"},{"index":7,"name":"EQLOPT1","description":"EQLOPT1 is an integer value that sets the initialization option for when dissolved gas is present in the run, as activated by the DISGAS keyword in the RUNSPEC section. A positive value of EQLOPT1 results in the gas-oil ratio being calculated from data entered on the PBVD (saturation pressure or bubble-point pressure versus depth table) or the RSVD keyword (gas-oil ratio versus depth table). If this option is selected, then either the PBVD or RSVD keywords must be present in the input deck. Note that the allocation of multiple PBVD and RSVD tables to each grid cell is through the EQLNUM keyword and not the PVTNUM keyword. A zero value of EQLOPT1 results in the gas-oil ratio being set to the saturated gas-oil ratio at the GOC. In this case DATUM must be equal GASCONT and the PBVD and RSVD keywords may be omitted. A negative value of EQLOPT1 results in the same option for when EQLOPT1 is zero. EQLOPT1 is ignored if there is no dissolved gas in the run.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0","value_type":"INT"},{"index":8,"name":"EQLOPT2","description":"EQLOPT2 is an integer value that sets the initialization option for when vaporized oil (condensate) is present in the run, as activated by the VAPOIL keyword in the RUNSPEC section. A positive value of EQLOPT2 results in the condensate-gas ratio being calculated from data entered on the PDVD (saturation pressure or dew point pressure versus depth table) or the RVVD keyword (condensate-gas ratio versus depth table). If this option is selected, then either the PDVD or RVVD keywords must be present in the input deck Note that the allocation of multiple PDVD and RVVD tables to each grid cell is through the EQLNUM keyword and not the PVTNUM keyword. A zero value of EQLOPT2 results in the condensate-gas ratio being set to the saturated condensate-gas ratio at the GOC. In this case DATUM must be equal GASCONT and the PDVD and RVVD keywords may be omitted. A negative value of EQLOPT2 results in the same option for when EQLOPT2 is zero. EQLOPT2 is ignored if there is no vaporized oil in the run.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0","value_type":"INT"},{"index":9,"name":"EQLOPT3","description":"EQLOPT3 is an integer value that sets the initialization accuracy options for the equilibration calculation. A zero value of EQLOPT3 results in OPM Flow using the fluid saturations at the center of the grid block in the equilibration calculation. This results in a stable initialization at the expense of a potentially less accurate fluid in-place calculation, especially for large thick grid blocks with a fluid contact in the block. A negative value of EQLOPT3 results in the simulator dividing each grid cell into[2` abs{N}~+~1]horizontal sub-blocks for the equilibration calculation. This results in an accurate fluid in-place calculation at the expense of initialization stability, that is there may be some movement of fluids when there is no production at the start of the run. horizontal sub-blocks for the equilibration calculation. This results in an accurate fluid in-place calculation at the expense of initialization stability, that is there may be some movement of fluids when there is no production at the start of the run. Increasing the value of N increases the accuracy of the calculation, with the maximum value of N being set to 20 by OPM Flow. A positive value of EQLOPT3 results in the same option for when EQLOPT3 is negative, except that tilted fault blocks are used in the calculation. Again, increasing the value of N increases the accuracy of the calculation, with the maximum value of N being set to 20 by OPM Flow. Note this option should be used with Irregular Corner-Point Grids. EQLOPT3 is ignored for Radial Grids.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0","value_type":"INT"},{"index":10,"name":"EQLOPT4","description":"A positive integer value greater than or equal one and less than or equal to three, that sets the initialization option in the commercial compositional simulator. EQLOPT4 should be defaulted with 1*, as it is not used by OPM Flow.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"INT"},{"index":11,"name":"EQLOPT5","description":"A positive integer value that if set to one forces PRESS to be used for the datum pressure in the commercial compositional simulator. EQLOPT5 should be defaulted with either 1*, as it is not used by OPM Flow.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"INT"},{"index":12,"name":"EQLOPT6","description":"EQLOPT6 is an integer value that sets the initialization option for when vaporized water is present in the run, as activated by the VAPWAT keyword in the RUNSPEC section. Note this is an OPM Flow specific parameter for use with simulator's Vaporized Water Model. A positive value of EQLOPT6 results in the vaporized water-gas ratio being calculated from data entered on the RVWVD keyword (vaporized water-gas ratio versus depth table). If this option is selected, then the RVWVD keyword must be present in the input deck Note that the allocation of multiple RVWVD tables to each grid cell is through the EQLNUM keyword and not the PVTNUM keyword. A zero value of EQLOPT2 results in the vaporized water-gas ratio being set to the saturated vaporized water-gas ratio at the GOC. In this case DATUM must be equal GASCONT and the RVWVD keyword may be omitted. A negative value of EQLOPT6 results in the same option for when EQLOPT6 is zero. EQLOPT6 is ignored if there is no vaporized water in the run.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0","value_type":"INT"}],"example":"--\n-- DATUM DATUM OWC PCOW GOC PCGO RS RV N E300 RVW\n-- DEPTH PRESS DEPTH ---- DEPTH ---- OPT OPT OPT OPTS OPT\nEQUIL\n3650.0 1560.0 3712.0 0.00 1000.0 0.00 1 0 -5 2* 1* /\n3650.0 1560.0 3741.0 0.00 1000.0 0.00 1 0 -5 2* 1* /\n3650.0 1560.0 3741.0 0.00 1000.0 0.00 1 0 -5 2* 1* /\nThe above example defines three equilibration records for when NTEQUL equals three on the EQLDIMS keyword in the RUNSPEC section. Here there is no gas cap and the GOC has been set to a value above the reservoirs (1000.0), and the value of EQLOPT3 (-5) has been explicitly stated.\n| Note A common method to initialize a model is by using the SWATINIT property array to set the initial water saturation for each cell in the model. This property is normally exported from a static model, where Saturation Height Functions (“SHF”) have been used to describe the water saturation profile with depth. In the dynamic model capillary pressure functions are used to described the water profile versus depth. Note that if the SWATINIT array has been used to initialize the model then the fine grid block initialization via the EQLOPT3 variable, should not normally be used, and should be defaulted or set equal to zero; otherwise, the resulting water saturation will not strictly honor the SWATINIT array. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":12,"size_kind":"fixed"},"GASCONC":{"name":"GASCONC","sections":["SOLUTION"],"supported":false,"summary":"The GASCONC keyword defines the initial equilibration coal gas concentration values for all matrix grid cells in the model and should be used in conjunction with the GCVD keyword in the SOLUTION section, to fully describe the initial state of the model. The keyword should only be used if the coal phase has been activated in the model via the COAL keyword in the RUNSPEC section. Note both GASCONC and GCVD are optional as the simulator will calculate the coal gas concentration based on the equilibrium concentration and the block pressure.","parameters":[{"index":1,"name":"GASCONC","description":"GASCONC is an array of real positive numbers that define the initial equilibration coal gas concentration values to each matrix cell in the model. Repeat counts may be used, for example 20*75.0.","units":{"field":"Mscf/ft3","metric":"sm3/m3","laboratory":"scc/cc"},"default":"None"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION COAL GAS CONCENTRATION FOR ALL CELLS\n-- BASED ON NX = 100, NY = 100 AND NZ = 6\n--\nGASCONC\n1000*75.500 1000*65.500 1000*60.000 /\nThe above example defines the initial equilibration coal gas concentration values to be 75.500 for all the matrix cells in the first layer, 65.500 for all the cells in the second layer, and finally 60.000 for all the cells in the third layer.","size_kind":"array"},"GASSATC":{"name":"GASSATC","sections":["SOLUTION"],"supported":false,"summary":"The GASSATC keyword defines the initial equilibration saturated coal gas concentration values for all grid cells in the model. The keyword should only be used if the coal phase has been activated in the model via the COAL keyword in the RUNSPEC section. The keyword is used to re-scale the Langmuir isotherms entered via the LANGMUIR keyword in the PROPS section, in conjunction with a matrix grid blocks initial reservoir pressure. The keyword is optional, and if absent from the input file, the matrix grid block Langmuir isotherm is left unscaled.","parameters":[{"index":1,"name":"GASSATC","description":"GASSATC is an array of real positive numbers that define the initial equilibration saturated coal gas concentration values to each cell in the model. Repeat counts may be used, for example 20*75.0.","units":{"field":"Mscf/ft3","metric":"sm3/m3","laboratory":"scc/cc"},"default":"None"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION SAT COAL GAS CONCENTRATION ALL CELLS MODEL\n-- BASED ON NX = 100, NY = 100 AND NZ = 6\n--\nGASSATC\n1000*75.500 1000*65.500 1000*60.000 /\nThe above example defines the initial equilibration saturated coal gas concentration values to be 75.500 for all the matrix cells in the first layer, 65.500 for all the cells in the second layer, and finally 60.000 for all the cells in the third layer.","size_kind":"array"},"GCVD":{"name":"GCVD","sections":["SOLUTION"],"supported":false,"summary":"The GCVD keyword defines the initial coal gas concentration versus depth tables for each equilibration region for when the coal phase has been activated in the run via the COAL keyword in the RUNSPEC section. The keyword may be used in conjunction with the GASCONC keyword in the SOLUTION section, to fully describe the initial state of the model. Note both GASCONC and GCVD are optional as the simulator will calculate the coal gas concentration based on the equilibrium concentration and the block pressure.","parameters":[{"index":1,"name":"DEPTH","description":"A columnar vector of real monotonically increasing down the column values that defines the depth values for the corresponding coal gas concentration, GCVALS.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":["Length","GasSurfaceVolume/Length*Length*Length"]},{"index":2,"name":"GCVALS","description":"A columnar vector of real values that defines the coal gas concentration values at the corresponding DEPTH.","units":{"field":"Mscf/ft3","metric":"sm3/m3","laboratory":"scc/cc"},"default":"None"}],"example":"Given NTEQUL equals three and NDRXVD is greater than or equal to two on the EQLDIMS keyword in the RUNSPEC section, then the following example defines the coal gas concentration versus depth functions.\n--\n-- DEPTH GC\n-- MSCF/FT\n-- ------ --------\nGCVD\n100.0 75.5000\n1000.0 75.5000 / GC VS DEPTH EQUIL REGN 01\n-- ------ --------\n100.0 65.5000\n1000.0 65.5000 / GC VS DEPTH EQUIL REGN 02\n-- ------ --------\n100.0 60.0000\n1000.0 60.0000 / GC VS DEPTH EQUIL REGN 03\nHere three tables are entered with a constant coal gas concentration versus depth relationship for each equilibration region.","size_kind":"fixed","variadic_record":true},"GETGLOB":{"name":"GETGLOB","sections":["SOLUTION"],"supported":false,"summary":"This keyword, GETGLOB, switches on the global grid read option for when the run is restarting from a RESTART file. Only the global grid will be loaded in the subsequent RESTART keyword and any Local Grid Refinements (“LGR”) on the RESTART file will be ignored.","parameters":[],"example":"--\n-- ACTIVATE LOADING OF GLOBAL GRID RESTART DATA OPTION\n--\nGETGLOB\nThe above example switches on the option to only load the global grid from the RESTART file.","size_kind":"none","size_count":0},"GI":{"name":"GI","sections":["SOLUTION"],"supported":false,"summary":"The GI keyword defines the initial equilibration GI values for all grid cells in the model and should be used in conjunction with the other enumeration equilibration keywords; PBUB, PDEW, PRESSURE, RS, RV, SOIL and SWAT keywords etc., to fully describe the initial state of the model. The keyword should only be used if the GI Pseudo Compositional option has been activated in the model via the GIMODEL keyword in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"HMAQUCT":{"name":"HMAQUCT","sections":["SOLUTION"],"supported":false,"summary":"The HMAQUCT keyword defines the history match analytical Carter-Tracy aquifer gradient parameters for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section, and analytical Carter-Tracy aquifers have been specified in the model via the AQUCT and connected to the grid using the AQUANCON or AQANCONL keywords. All keywords are in the SOLUTION section.","parameters":[{"index":1,"name":"AQUIFER_ID","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"DERIVATIES_RESP_PERM_MULT","description":"","units":{},"default":"NO","value_type":"STRING"},{"index":3,"name":"DERIVATIES_RESP_OPEN_ANGLE_MULT","description":"","units":{},"default":"NO","value_type":"STRING"},{"index":4,"name":"DERIVATIES_RESP_AQUIFER_DEPTH","description":"","units":{},"default":"NO","value_type":"STRING"}],"example":"","expected_columns":4,"size_kind":"list"},"HMAQUFET":{"name":"HMAQUFET","sections":["SOLUTION"],"supported":false,"summary":"The HMAQUFET keyword defines the history match analytical Fetkovich aquifer gradient parameters for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section, and analytical Fetkovich aquifers have been specified in the model via the AQUFET and/or the AQUFETP keywords and connected to the grid using AQUANCON or AQANCONL keywords. All keywords are in the SOLUTION section.","parameters":[{"index":1,"name":"AQUIFER_ID","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"DERIVATIES_RESP_WAT_VOL_MULT","description":"","units":{},"default":"NO","value_type":"STRING"},{"index":3,"name":"DERIVATIES_RESP_AQUIFER_PROD_INDEX_MULT","description":"","units":{},"default":"NO","value_type":"STRING"},{"index":4,"name":"DERIVATIES_RESP_AQUIFER_DEPTH","description":"","units":{},"default":"NO","value_type":"STRING"}],"example":"","expected_columns":4,"size_kind":"list"},"HMMLCTAQ":{"name":"HMMLCTAQ","sections":["SOLUTION"],"supported":false,"summary":"The HMMLCTAQ keyword defines the history match analytical Carter-Tracy aquifer gradient multipliers for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section, and analytical Carter-Tracy aquifers have been specified in the model via the AQUCT and connected to the grid using the AQUANCON or AQANCONL keywords. All keywords are in the SOLUTION section.","parameters":[{"index":1,"name":"AQUIFER_ID","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"AQUIFER_PERM_MULT","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"AQUIFER_ANGLE_MULT","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"},{"index":4,"name":"AQUIFER_DEPTH_MULT","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"}],"example":"","expected_columns":4,"size_kind":"list"},"HMMLFTAQ":{"name":"HMMLFTAQ","sections":["SOLUTION"],"supported":false,"summary":"The HMAQUFET keyword defines the history match analytical Fetkovich aquifer gradient multipliers for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section, and analytical Fetkovich aquifers have been specified in the model via the AQUFET and/or the AQUFETP keywords and connected to the grid using AQUANCON or AQANCONL keywords. All keywords are in the SOLUTION section.","parameters":[{"index":1,"name":"AQUIFER_ID","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"AQUIFER_WAT_VOL_MULT","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"AQUIFER_PROD_INDEX_MULT","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"},{"index":4,"name":"AQUIFER_DEPTH_MULT","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"}],"example":"","expected_columns":4,"size_kind":"list"},"HMMLTWCN":{"name":"HMMLTWCN","sections":["SOLUTION"],"supported":false,"summary":"This keyword, HMMLTWCN, defines the history match gradient multipliers for well connection factors and connection skins, for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section. Wells must be specified using the WELPSECS keyword in the SCHEDULE section and their connections defined by the COMPDAT and/or COMPDATL keywords, also in the SCHEDULE section","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"GRID","description":"","units":{},"default":"FIELD","value_type":"STRING"},{"index":3,"name":"I","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"J","description":"","units":{},"default":"","value_type":"INT"},{"index":5,"name":"K","description":"","units":{},"default":"","value_type":"INT"},{"index":6,"name":"CTF","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"},{"index":7,"name":"SKIN","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"}],"example":"","expected_columns":7,"size_kind":"list"},"HMWELCON":{"name":"HMWELCON","sections":["SOLUTION"],"supported":false,"summary":"This keyword, HMWELCON, defines the history match gradient parameters for well connection factors and connection skins, for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section. Wells must be specified using the WELPSECS keyword in the SCHEDULE section and their connections defined by the COMPDAT and/or COMPDATL keywords, also in the SCHEDULE section","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"GRID","description":"","units":{},"default":"FIELD","value_type":"STRING"},{"index":3,"name":"I","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"J","description":"","units":{},"default":"","value_type":"INT"},{"index":5,"name":"K","description":"","units":{},"default":"","value_type":"INT"},{"index":6,"name":"REQ_TRANS_FACTOR_GRAD","description":"","units":{},"default":"NO","value_type":"STRING"},{"index":7,"name":"REQ_SKIN_FACTOR_GRAD","description":"","units":{},"default":"NO","value_type":"STRING"}],"example":"","expected_columns":7,"size_kind":"list"},"NOHMD":{"name":"NOHMD","sections":["SOLUTION","SCHEDULE"],"supported":false,"summary":"The NOHMD deactivates various history match gradient derivative calculations for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section. The keyword consists of a series of character strings that define which derivative should be switch off based on the keyword that requested the derivatives to be calculated, for example HMFAULTS keyword in the GRID section. If an empty list is entered then all the gradient derivative calculations previously requested are switch off. The keyword is useful for changing from history matching runs to predication cases, as the prediction cases will be more computationally efficient without the burden of the gradient derivative calculations.","parameters":[{"index":1,"name":"GRAD_PARAMS","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","size_kind":"fixed","size_count":1,"variadic_record":true},"NOHMO":{"name":"NOHMO","sections":["SOLUTION","SCHEDULE"],"supported":false,"summary":"The NOHMO deactivates various history match gradient derivative calculations for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section. The keyword consists of a series of character strings that define which derivative should be switch off based on the keyword that requested the derivatives to be calculated, for example HMFAULTS keyword in the GRID section. If an empty list is entered then all the gradient derivative calculations previously requested are switch off. The keyword is useful for changing from history matching runs to predication cases, as the prediction cases will be more computationally efficient without the burden of the gradient derivative calculations.","parameters":[{"index":1,"name":"GRAD_PARAMS","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","size_kind":"fixed","size_count":1,"variadic_record":true},"OILAPI":{"name":"OILAPI","sections":["SOLUTION"],"supported":null,"summary":"The OILAPI keyword defines the initial equilibration oil API gravity pressures for all grid cells in the model, for when the Oil API Tracking option as been invoked by the API keyword in the RUNSPEC section. The keyword should be used in conjunction with the PBUB, PDEW, PRESSURE, RS, RV, SGAS, SOIL and SWAT keywords etc., to fully describe the initial state of the model.","parameters":[{"index":1,"name":"OILAPI","description":"OILAPI is an array of real positive numbers assigning the initial equilibration oil API gravity to each cell in the model. The American Petroleum Institute (“API”) classifies oils based on an API gravity (γAPI), or degrees API (oAPI), the relationship between relative density (γo) of oil and API gravity (γAPI) is given by: [%gamma SUB { API } ~ = ~ { 141.5 } OVER { %gamma SUB { o }}~-~ 131.5] Repeat counts may be used, for example 20*38.5","units":{"field":"oAPI","metric":"oAPI","laboratory":"oAPI"},"default":"None"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION OIL API FOR ALL CELLS IN THE MODEL\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nOILAPI\n1000*40.2 1000*39.5 1000*38.2 /\nThe above example defines the initial equilibration oil API gravity to be 40.2 for all the cells in the first layer, 39.5 for all the cells in the second layer, and finally 38.2 for all the cells in the third layer.","size_kind":"array"},"OUTSOL":{"name":"OUTSOL","sections":["SOLUTION","SCHEDULE"],"supported":false,"summary":"This keyword defines the data and frequency of the data to be written to the RESTART file at each requested restart point. The keyword has been replaced by the RPTRST keyword in the SOLUTION and SCHEDULE sections and is therefore considered retired.","parameters":[],"example":"","size_kind":"none","size_count":0},"PBUB":{"name":"PBUB","sections":["SOLUTION"],"supported":false,"summary":"The PBUB keyword defines the initial equilibration buble-point saturation pressures values for all grid cells in the model and should be used in conjunction with the PDEW, PRESSURE, RS, RV, SGAS, SOIL and SWAT keywords etc., to fully describe the initial state of the model. The keyword should only be used if dissolved gas has been activated in the model via the DISGAS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"PBUB","description":"PBUB is an array of real positive numbers assigning the initial equilibration bubble-point saturation pressure values to each cell in the model. Repeat counts may be used, for example 20*3500.0","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION PSAT VALUES FOR ALL CELLS IN THE MODEL\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nPBUB\n1000*3500.0 1000*3525.0 1000*0.3535.0 /\nThe above example defines the initial equilibration bubble-point saturation pressure values to be 3500.0 for all the cells in the first layer, 3525.0 for all the cells in the second layer, and finally 3535.0 for all the cells in the third layer.","size_kind":"array"},"PBVD":{"name":"PBVD","sections":["SOLUTION"],"supported":null,"summary":"The PBVD keyword defines the bubble-point pressure versus depth tables for each equilibration region that should be used when there is dissolved gas in the model (DISGAS has been activated in the RUNSPEC section) and the EQLOPT1 variable has been set to a positive integer on the EQUIL keyword in the SOLUTION section.","parameters":[{"index":1,"name":"DEPTH","description":"A columnar vector of real monotonically increasing down the column values that defines the depth values for the corresponding bubble-point values, PBVALS.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":["Length","Pressure"]},{"index":2,"name":"PBVALS","description":"A columnar vector of real values that defines the oil bubble-point values at the corresponding DEPTH.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None"}],"example":"Given NTEQUL equals three and NDRXVD is greater than or equal to two on the EQLDIMS keyword in the RUNSPEC section, then the following example defines the bubble-point versus depth functions.\n--\n-- DEPTH PSAT\n-- PRESS\n-- ------ ------\nPBVD\n3000.0 3000.0\n8000.0 3025.0 / PSAT VS DEPTH EQUIL REGN 01\n-- ------ ------\n3000.0 3100.0\n8000.0 3125.0 / PSAT VS DEPTH EQUIL REGN 02\n-- ------ ------\n3000.0 3200.0\n8000.0 3225.0 / PSAT VS DEPTH EQUIL REGN 03\nHere three tables are entered and each table is terminated by a “/” and there is no keyword terminating “/”.","size_kind":"fixed","variadic_record":true},"PDEW":{"name":"PDEW","sections":["SOLUTION"],"supported":false,"summary":"The PDEW keyword defines the initial equilibration dew-point pressure values for all grid cells in the model and should be used in conjunction with the PBUB, PRESSURE, RS, RV, SGAS, SOIL and SWAT keywords etc., to fully describe the initial state of the model. The keyword should only be used if vaporized oil been activated in the model via the VAPOIL keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"PDEW","description":"PDEW is an array of real positive numbers assigning the initial equilibration dew-point pressure values to each cell in the model. Repeat counts may be used, for example 20*3525.0","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION PSAT VALUES FOR ALL CELLS IN THE MODEL\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nPDEW\n1000*3500.0 1000*3525.0 1000*0.3535.0 /\nThe above example defines the initial equilibration dew-point saturation pressure values to be 3500.0 for all the cells in the first layer, 3525.0 for all the cells in the second layer, and finally 3535.0 for all the cells in the third layer.","size_kind":"array"},"PDVD":{"name":"PDVD","sections":["SOLUTION"],"supported":null,"summary":"The PDVD keyword defines the dew-point pressure versus depth tables for each equilibration region that should be used when there is vaporized oil in the model (VAPOIL has been activated in the RUNSPEC section) and the EQLOPT2 variable has been set to a positive integer on the EQUIL keyword in the SOLUTION section.","parameters":[{"index":1,"name":"DEPTH","description":"A columnar vector of real monotonically increasing down the column values that defines the depth values for the corresponding dew-point values, PDVALS.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":["Length","Pressure"]},{"index":2,"name":"PDVALS","description":"A columnar vector of real values that defines the gas dew-point values at the corresponding DEPTH.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None"}],"example":"Given NTEQUL equals three and NDRXVD is greater than or equal to two on the EQLDIMS keyword in the RUNSPEC section, then the following example defines the bubble-point versus depth functions.\n--\n-- DEPTH PSAT\n-- PRESS\n-- ------ ------\nPDVD\n3000.0 2000.0\n8000.0 2025.0 / PSAT VS DEPTH EQUIL REGN 01\n-- ------ ------\n3000.0 2100.0\n8000.0 2125.0 / PSAT VS DEPTH EQUIL REGN 02\n-- ------ ------\n3000.0 2200.0\n8000.0 2225.0 / PSAT VS DEPTH EQUIL REGN 03\nHere three tables are entered and each table is terminated by a “/” and there is no keyword terminating “/”.","size_kind":"fixed","variadic_record":true},"PRESSURE":{"name":"PRESSURE","sections":["SOLUTION"],"supported":null,"summary":"The PRESSURE keyword defines the initial equilibration pressures for all grid cells in the model and should be used in conjunction with the PBUB, PDEW, RS, RV, SGAS, SOIL and SWAT keywords etc., to fully describe the initial state of the model.","parameters":[{"index":1,"name":"PRESSURE","description":"PRESSURE is an array of real positive numbers assigning the initial equilibration pressures to each cell in the model. Repeat counts may be used, for example 20*4200.0.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION PRESSURES FOR ALL CELLS IN THE MODEL\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nPRESSURE\n1000*4500.0 1000*4510.0 1000*4520.0 /\nThe above example defines the initial equilibration pressures to be 4500.0 for all the cells in the first layer, 4510.0 for all the cells in the second layer, and finally 4520.0 for all the cells in the third layer.","size_kind":"array"},"PRVD":{"name":"PRVD","sections":["SOLUTION"],"supported":false,"summary":"The PRVD keyword defines the initial reservoir pressure versus depth and should be used in conjunction with the PBUB, PDEW, RS, RV, SGAS, SOIL and SWAT keywords etc., to fully describe the initial state of the model. PRVD is an alternative to the PRESSURE keyword in the SOLUTION section, that defines the initial equilibration pressures for all grid cells in the model","parameters":[{"index":1,"name":"DEPTH","description":"A columnar vector of real monotonically increasing down the column values that defines the depth values for the corresponding reservoir oil pressures values, PRESSURE.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":["Length","Pressure"]},{"index":2,"name":"PRESSURE","description":"A columnar vector of real values that defines the initial equilibration oil pressure values at the corresponding DEPTH.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None"}],"example":"Given NTEQUL equals three and NDRXVD is greater than or equal to five on the EQLDIMS keyword in the RUNSPEC section, then the following example defines the initial oil reservoir pressure versus depth\n--\n-- DEPTH INIT\n-- PRESS\n-- ------ ------\nPRVD\n3000.0 3000.0\n4000.0 3345.0\n5000.0 3690.0\n7000.0 4700.0\n7200.0 4769.0 / POIL VS DEPTH EQUIL REGN 01\n-- ------ ------\n3000.0 3100.0\n4000.0 3445.0\n5000.0 3790.0\n7000.0 4700.0\n7200.0 4769.0 / POIL VS DEPTH EQUIL REGN 02\n-- ------ ------\n3000.0 3150.0\n4000.0 3495.0\n5000.0 3840.0\n7000.0 4700.0\n7200.0 4769.0 / POIL VS DEPTH EQUIL REGN 03\nHere three tables are entered and each table is terminated by a “/” and there is no keyword terminating “/”.","size_kind":"fixed","variadic_record":true},"RAINFALL":{"name":"RAINFALL","sections":["SOLUTION","SCHEDULE"],"supported":false,"summary":"This RAINFALL keyword defines the month by month rainfall flux for constant flux aquifers.","parameters":[{"index":1,"name":"AQUIFER_ID","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"JAN_FLUX","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time*Length*Length"},{"index":3,"name":"FEB_FLUX","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time*Length*Length"},{"index":4,"name":"MAR_FLUX","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time*Length*Length"},{"index":5,"name":"APR_FLUX","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time*Length*Length"},{"index":6,"name":"MAI_FLUX","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time*Length*Length"},{"index":7,"name":"JUN_FLUX","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time*Length*Length"},{"index":8,"name":"JUL_FLUX","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time*Length*Length"},{"index":9,"name":"AUG_FLUX","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time*Length*Length"},{"index":10,"name":"SEP_FLUX","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time*Length*Length"},{"index":11,"name":"OCT_FLUX","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time*Length*Length"},{"index":12,"name":"NOV_FLUX","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time*Length*Length"},{"index":13,"name":"DES_FLUX","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time*Length*Length"}],"example":"","expected_columns":13,"size_kind":"fixed","size_count":1},"RBEDCONT":{"name":"RBEDCONT","sections":["PROPS"],"supported":false,"summary":"The RBEDCONT keyword defines the river grid block contact area versus depth tables, for when the River option has been activated via the RIVRDIMS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Length","Length*Length"]}],"example":"","size_kind":"fixed","variadic_record":true},"RESTART":{"name":"RESTART","sections":["SOLUTION"],"supported":false,"summary":"The RESTART keyword defines the parameters to restart the simulation from a previous run that has written a RESTART file out to disk. Only restarting from RESTART files is permitted by OPM Flow; restarting from SAVE files is not implemented.","parameters":[{"index":1,"name":"RSNAME","description":"The RSNAME variable is a character string that defines the root name of the RESTART file to be read into the current input deck.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"RSNUM","description":"A positive integer that defines the restart point on the RESTART file to be read and to be used to initialize the model. When OPM Flow writes a restart point a message is printed to the *.PRT file indicating the time step the restart was written out.","units":{},"default":"None","value_type":"INT"},{"index":3,"name":"RSTYPE","description":"A defined character sting set to SAVE to read the restart data from the SAVE file, otherwise defaulted to 1* to read the data from the RESTART file. The SAVE file option is not supported by OPM Flow and should be defaulted with 1*.","units":{},"default":"1*","value_type":"STRING"},{"index":4,"name":"RSFORMAT","description":"A defined character string that defines the format of the SAVE file to be read if RSTYPE has been set to SAVE, and should be set to one of the following: FORMATTED: If the file is formatted as ASCII i.e. a text file, as oppose to a binary file. The option can be abbreviated to just the letter F. UNFORMATTED: If the file is in binary format, note this option can be abbreviated to just the letter U. This type of file is operating system dependent If the variable RSFORMAT omitted then the default is for binary file input. This option is not supported by OPM Flow and should be defaulted with 1*.","units":{},"default":"U","value_type":"STRING"}],"example":"The example below defines a restart from the previously run NOR-OPM-A01 case at time step number 40.\n-- ==============================================================================\n--\n-- SOLUTION SECTION\n--\n-- ==============================================================================\nSOLUTION\n--\n-- FLEXIBLE RESTART FROM PREVIOUS SIMULATION RUN\n--\n-- FILE RESTART RESTART FILE\n-- NAME NUMBER TYPE FORMAT\nRESTART\n'NOR-OPM-A01' 40 1* 1* /\nIn addition in the SCHEDULE section the SKIPREST keyword should be used to correctly read in the schedule data up to the RESTART point.\n-- ==============================================================================\n--\n-- SCHEDULE SECTION\n--\n-- ==============================================================================\nSCHEDULE\n--\n-- ACTIVATE SKIPREST OPTION TO AVOID MODIFYING SCHEDULE SECTION\n--\nSKIPREST\nNote is advisable to place the SKIPREST keyword at the very beginning of the SCHEDULE section.","expected_columns":4,"size_kind":"fixed","size_count":1},"RIVERSYS":{"name":"RIVERSYS","sections":["SOLUTION","SCHEDULE"],"supported":false,"summary":"RIVERSYS defines a river system by specifying the branch structure of the river together with the branch's associated boundary conditions, for when the River option has been activated via the RIVRDIMS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"RIVER","description":"","units":{},"default":"","value_type":"STRING","record":1},{"index":2,"name":"EQUATION","description":"","units":{},"default":"","value_type":"STRING","record":1},{"index":1,"name":"BRANCH_NR","description":"","units":{},"default":"","value_type":"INT","record":2},{"index":2,"name":"BRANCH_NAME","description":"","units":{},"default":"","value_type":"STRING","record":2},{"index":3,"name":"DOWNSTREAM_BC","description":"","units":{},"default":"","value_type":"STRING","record":2}],"example":"","records_meta":[{"expected_columns":2},{}],"size_kind":"list"},"RPTRST":{"name":"RPTRST","sections":["SOLUTION","SCHEDULE"],"supported":false,"summary":"This keyword defines the data to be written to the RESTART file and the frequency at which restart points will be created. In addition to the solution data arrays required to restart a run, the user may request extra data to be written to the restart file for visualization in OPM ResInsight.","parameters":[{"index":1,"name":"XMFCO2","description":"CO2 liquid-phase mole fractions written when the CO2STORE option has been activated in the RUNSPEC section.","units":{},"default":"XMFCO2","value_type":"STRING"},{"index":2,"name":"XMFH2","description":"H2 liquid-phase mole fractions written when the H2STORE option has been activated in the RUNSPEC section.","units":{},"default":"XMFH2"},{"index":3,"name":"YMFWAT","description":"Water gas-phase mole fractions written when either the CO2STORE or H2STORE option has been activated in the RUNSPEC section.","units":{},"default":"YMFWAT"}],"example":"The first example request that the standard restart data be written out every month.\n--\n-- RESTART CONTROL BASIC = 4 (YEARLY) 5 (MONTHLY)\n--\nRPTRST\nBASIC=5 /\nThe next example requests that the standard restart data be written at every report time step until this switch is reset and all the restarts are kept. In addition to the standard the data the gas, oil and water relative permeability data will also be written out at each report time step.\n--\n-- RESTART CONTROL BASIC = 4 (YEARLY) 5 (MONTHLY)\n--\nRPTRST\nBASIC=2 KRG KRO KRW /\n| Note Currently, OPM Flow distinguishes between those arrays which are required for restarting a run and those which are \"merely\" for visualization and analysis. However, this classification is imperfect and leads to potentially exporting arrays that are incompatible with the commercial simulator, such as the TEMP array in non-thermal simulation runs. If one is willing to forego the ability to restart an OPM Flow simulation run, using the commercial simulator, e.g., simulating the historic period using OPM Flow and the prediction period using the commercial simulator, then additional arrays are available, including the PBUB and PDEW vectors generated by the PBPD option, by using the following command line option: --enable-opm-rst-file=true |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"fixed","size_count":1,"variadic_record":true},"RPTSOL":{"name":"RPTSOL","sections":["SOLUTION"],"supported":true,"summary":"This keyword defines the data in the SOLUTION section that is to be printed to the output print file in human readable format. The keyword has two distinct forms, the first of which consists of the keyword followed by a series of integers on the next line indicating the data to be printed (see the first example). This is the original formal in the commercial simulator and was subsequently superseded by the second format. The second format consists of the keyword followed by a series of character strings that indicate the data to be printed. In most cases the character string is the keyword used to load the data in the OPM Flow input deck, for example PVDG for the dry gas PVT tables. Its is anticipated that OPM Flow will eventually support the functionality of the second format only, the first format although recognized will be completely ignored.","parameters":[{"index":1,"name":"DENO","description":"Print the oil reservoir density array","units":{},"default":"N/A","value_type":"STRING"},{"index":2,"name":"EQUIL","description":"Print the equilibration report.","units":{},"default":"N/A"},{"index":3,"name":"FIP","description":"Print the fluid in-place report. The parameter is assigned a value, OPTION, using the form FIP=OPTION, where OPTION is an integer variable set to: OPTION = 1 then the report is for the field only. OPTION = 2 then in addition to the field report, a report is produced for each FIPNUM region, as defined by the FIPNUM keyword in the REGIONS section. Note the commercial simulator also prints the flows to other regions as well as the flows from the wells. This additional reporting option has not been implemented in OPM Flow. OPTION = 3 then in addition to the above, a balance report is also produced for fluid in-place regions defined by the FIP keyword in the REGIONS section.","units":{},"default":"FIP=2"},{"index":4,"name":"FIPRESV","description":"Print the reservoir volumes in-place report.","units":{},"default":"N/A"},{"index":5,"name":"WELSPECS","description":"WELSPECS switches on reporting of the well connections, wells and groups at each report time step. There are numerous reports associated with this option. Unlike the other reporting parameters that produce a report for each reporting time step, the WELSPECS report option only produces a report if an associated keyword has been activated at the current reporting time step. For example, if the reporting time steps are January, February, and March 2020, and the RPTSCHED WELSPECS option is activated in January, with wells OP01 and OP02 being declared via the WELSPECS and COMPDAT keywords, then a report will be printed for January for these two wells. If there are no further well activations until March, with well OP03 being declared, then there will be no report for February, and only well OP03 will reported at the March reporting time step.","units":{},"default":"N/A"}],"example":"The first example shows the original format of this keyword; although the keyword and format are recognized by OPM Flow, the format is ignored and is unlikely to be implemented in in the simulator.\n--\n-- DEFINE SOLUTION SECTION REPORT OPTION (ORIGINAL FORMAT)\n–\nRPTSOL\n1 2*0 1 3*1 /\nThe next example shows the second format of the keyword which may be supported in a future release of OPM Flow.\n--\n-- DEFINE SOLUTION SECTION REPORT OPTIONS\n--\nRPTSOL\nFIP=2 FIPRESV RESTART=3 /\n| Note Except for non-array like data, FIP etc., this keyword has the potential to produce very large print files that some text editors may have difficulty loading. A more efficient solution for array type data is to load the *.INIT and *.RESTART files into OPM ResInsight to view the data graphically, this also has the benefit of being able to filter the grid based on I, J, K ranges and grid properties. |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"fixed","size_count":1,"variadic_record":true},"RS":{"name":"RS","sections":["SOLUTION"],"supported":null,"summary":"The RS keyword defines the initial equilibration gas-oil ratio values for all grid cells in the model and should be used in conjunction with the PBUB, PDEW, PRESSURE, RV, SGAS, SOIL and SWAT keywords etc., to fully describe the initial state of the model. The keyword should only be used if dissolved gas has been activated in the model via the DISGAS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"RS","description":"RS is an array of real positive numbers assigning the initial equilibration gas-oil ratio values to each cell in the model. Repeat counts may be used, for example 20*1.30.","units":{"field":"Mscf/stb","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"None"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION GOR VALUES FOR ALL CELLS IN THE MODEL\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nRS\n1000*1.3500 1000*1.3010 1000*1.3000 /\nThe above example defines the initial equilibration GOR values to be 1.3500 for all the cells in the first layer, 1.3010 for all the cells in the second layer, and finally 1.3000 for all the cells in the third layer.","size_kind":"array"},"RSVD":{"name":"RSVD","sections":["SOLUTION"],"supported":null,"summary":"The RSVD keyword defines the dissolved gas-oil ratio (Rs) versus depth tables for each equilibration region that should be used when there is dissolved gas in the model (DISGAS has been activated in the RUNSPEC section) and the EQLOPT1 variable has been set to a positive integer on the EQUIL keyword in the SOLUTION section.","parameters":[{"index":1,"name":"DEPTH","description":"A columnar vector of real monotonically increasing down the column values that defines the depth values for the corresponding dissolve gas-oil ratio values, RS.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":["Length","GasDissolutionFactor"]},{"index":2,"name":"RS","description":"A columnar vector of real values that defines the dissolved gas-oil ratio values at the corresponding DEPTH.","units":{"field":"Mscf/stb","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"None"}],"example":"Given NTEQUL equals three and NDRXVD is greater than or equal to two on the EQLDIMS keyword in the RUNSPEC section, then the following example defines the bubble-point versus depth functions.\n--\n-- DEPTH RS\n-- MSCF/STB\n-- ------ --------\nRSVD\n3000.0 1.400\n8000.0 1.400 / RS VS DEPTH EQUIL REGN 01\n-- ------ --------\n3000.0 1.400\n8000.0 1.400 / RS VS DEPTH EQUIL REGN 02\n-- ------ --------\n3000.0 1.400\n8000.0 1.400 / RS VS DEPTH EQUIL REGN 03\nHere three tables are entered with a constant GOR versus depth relationship.","size_kind":"fixed","variadic_record":true},"RSW":{"name":"RSW","sections":["SOLUTION"],"supported":null,"summary":"The RSW keyword defines the initial equilibration solution gas in water ratio values for all grid cells in the model and should be used in conjunction with the PBUB, PDEW, PRESSURE, RS, SGAS, SOIL and SWAT keywords etc., to fully describe the initial state of the model. The keyword should only be used if both gas and water phases have been activated in the model via the GAS and WATER keywords, and the DISGASW keyword is also present activating OPM Flow’s Dissolved Gas in Water Model. All the aforementioned keywords are in the RUNSPEC section.","parameters":[{"index":1,"name":"RSW","description":"RSW is an array of positive real numbers assigning the initial equilibration solution gas-water ratio values to each cell in the model. Repeat counts may be used, for example 20*1.30.","units":{"field":"Mscf/stb","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"None"}],"example":"--\n-- INITIAL EQUILIBRATION SOLUTION GAS IN WATER RATIO VALUES FOR ALL CELLS\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nRSW\n1000*0.0000 1000* 0.0000 1000*1.3000 /\nThe above example defines the initial equilibration solution gas-water values to be 0.000 for all the cells in the first and second layers and 1.3000 for all the cells in the third layer.\n| Note This is an OPM Flow specific keyword for the simulator’s Dissolved Gas in Water Model that is activated by declaring that dissolved gas in water is present in the run using the DISGASW keyword in the RUNSPEC section. Use the command line option --enable-opm-rst-file=true to output the RSW data to the RESTART file. |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"array"},"RV":{"name":"RV","sections":["SOLUTION"],"supported":null,"summary":"The RV keyword defines the initial equilibration vaporized oil-gas ratio values for all grid cells in the model and should be used in conjunction with the PBUB, PDEW, PRESSURE, RS, SGAS, SOIL and SWAT keywords etc., to fully describe the initial state of the model. The keyword should only be used if vaporized oil been activated in the model via the VAPOIL keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"RV","description":"RV is an array of real positive numbers assigning the initial equilibration vaporized oil-gas ratio values to each cell in the model. Repeat counts may be used, for example 20*0.00720","units":{"field":"stb/Mscf","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"None"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION CGR VALUES FOR ALL CELLS IN THE MODEL\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nRV\n1000*0.00720 1000*0.00725 1000*0.00730 /\nThe above example defines the initial equilibration GOR values to be 0.00720 for all the cells in the first layer, 0.00725 for all the cells in the second layer, and finally 0.00730 for all the cells in the third layer.","size_kind":"array"},"RVVD":{"name":"RVVD","sections":["SOLUTION"],"supported":null,"summary":"The RVVD keyword defines the vaporized oil-gas ratio (Rv) versus depth tables for each equilibration region that should be used when there is vaporized oil in the model (VAPOIL has been activated in the RUNSPEC section) and the EQLOPT2 variable has been set to a positive integer on the EQUIL keyword in the SOLUTION section.","parameters":[{"index":1,"name":"DEPTH","description":"A columnar vector of real monotonically increasing down the column values that defines the depth values for the corresponding vaporized oil-gas ratio values, RV.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":["Length","OilDissolutionFactor"]},{"index":2,"name":"RV","description":"A columnar vector of real values that defines the vaporized oil-gas ratio values at the corresponding DEPTH.","units":{"field":"stb/Mscf","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"None"}],"example":"Given NTEQUL equals three and NDRXVD is greater than or equal to two on the EQLDIMS keyword in the RUNSPEC section, then the following example defines the dew-point versus depth functions.\n--\n-- DEPTH RV\n-- STB/MSCF\n-- ------ --------\nRVVD\n3000.0 0.00725\n8000.0 0.00725 / RV VS DEPTH EQUIL REGN 01\n-- ------ --------\n3000.0 0.00730\n8000.0 0.00730 / RV VS DEPTH EQUIL REGN 02\n-- ------ --------\n3000.0 0.00750\n8000.0 0.00750 / RV VS DEPTH EQUIL REGN 03\nHere three tables are entered with a constant CGR versus depth relationship for each equilibration region.","size_kind":"fixed","variadic_record":true},"RVW":{"name":"RVW","sections":["SOLUTION"],"supported":null,"summary":"The RVW keyword defines the initial equilibration vaporized water in gas ratio values for all grid cells in the model and should be used in conjunction with the PBUB, PDEW, PRESSURE, RV, SGAS, SOIL and SWAT keywords etc., to fully describe the initial state of the model. The keyword should only be used if both gas and water phases have been activated in the model via the GAS and WATER keywords, and the VAPWAT is also present activating OPM Flow’s Vaporized Water Model. All the aforementioned keywords are in the RUNSPEC section.","parameters":[{"index":1,"name":"RVW","description":"RVW is an array of real positive numbers assigning the initial equilibration gas-vaporized water ratio values to each cell in the model. Repeat counts may be used, for example 20*1.30.","units":{"field":"stb/Mscf","metric":"sm3/sm3","laboratory":"rcc/scc"},"default":"None"}],"example":"--\n-- INITIAL EQUILIBRATION WATER VAPOR IN GAS RATIO VALUES FOR ALL CELLS\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nRVW\n1000*0.0000 1000* 0.0000 1000*1.3000 /\nThe above example defines the initial equilibration gas-vaporized water values to be 0.000 for all the cells in the first and second layers and 1.3000 for all the cells in the third layer.\n| Note This is an OPM Flow specific keyword for the simulator’s Water Vaporization Model that is activated by declaring that vaporized water is present in the run using the VAPWAT keyword in the RUNSPEC section. Use the command line option --enable-opm-rst-file=true to output the RVW data to the RESTART file. |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"array"},"RVWVD":{"name":"RVWVD","sections":["SOLUTION"],"supported":null,"summary":"The RVWVD keyword defines the vaporized water-gas ratio (Rvw) versus depth tables for each equilibration region that should be used when there is vaporized water in the model and the EQLOPT6 variable has been set to a positive integer on the EQUIL keyword in the SOLUTION section.","parameters":[{"index":1,"name":"DEPTH","description":"A columnar vector of real monotonically increasing down the column values that defines the depth values for the corresponding vaporized oil-gas ratio values, RVW","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":["Length","OilDissolutionFactor"]},{"index":2,"name":"RVW","description":"A columnar vector of real values that defines the vaporized water-gas ratio values, values at the corresponding DEPTH.","units":{"field":"stb/Mscf","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"None"}],"example":"Given NTEQUL equals three and NDRXVD is greater than or equal to two on the EQLDIMS keyword in the RUNSPEC section, then the following example defines the vaporized water-gas ratio versus depth functions.\n--\n-- DEPTH RVW\n-- STB/MSCF\n-- ------ --------\nRVWVD\n3000.0 0.00000\n8000.0 0.00000 / RVW VS DEPTH EQUIL REGN 01\n-- ------ --------\n3000.0 0.00000\n8000.0 0.00000 / RVW VS DEPTH EQUIL REGN 02\n-- ------ --------\n3000.0 0.00100\n8000.0 0.00100 / RVW VS DEPTH EQUIL REGN 03\nThe example shows three tables for three regions with constant RVW versus depth relationships for each equilibration region, with the first two tables having a zero vaporized water-gas ratio and the last region having a constant 0.001 stb/Mscf versus depth relationship.\n| Note This is an OPM Flow specific keyword for the simulator’s Water Vaporization Model that is activated by declaring that vaporized water is present in the run using the VAPWAT keyword in the RUNSPEC section. Use the command line option --enable-opm-rst-file=true to output the RVW data to the RESTART file. |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"fixed","variadic_record":true},"SALT":{"name":"SALT","sections":["SOLUTION"],"supported":null,"summary":"The SALT keyword defines the initial equilibration salt concentration values for all grid cells in the model and should be used in conjunction with the PBUB, PDEW, PRESSURE, RS, RV, SGAS, SGAS and SWAT keywords etc., to fully describe the initial state of the model. The keyword should only be used if the salt (brine) phase has been activated in the model via the BRINE keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"SALT","description":"SALT is an array of real positive numbers that are greater than or equal to zero assigning the initial equilibration salt concentration values to each cell in the model. Repeat counts may be used, for example 20*15.0.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None","value_type":"DOUBLE","dimension":"Concentration"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION SALT CONCENTRATION FOR ALL CELLS\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nSALT\n10000*0.0000 10000*0.0000 10000*15.000 /\nThe above example defines the initial equilibration salt concentration values to be 0.0000 for all the cells in the first and second layers and finally 15.000 for all the cells in the third layer.","size_kind":"fixed","size_count":1,"variadic_record":true},"SALTP":{"name":"SALTP","sections":["SOLUTION"],"supported":null,"summary":"The SALTP keyword defines the initial equilibration precipitated salt volume fraction values for all grid cells in the model and should be used in conjunction with the PBUB, PDEW, PRESSURE, RS, RV, SGAS, SOIL and SWAT keywords etc., to fully describe the initial state of the model. The keyword should only be used if the salt (brine) phase has been activated in the model via the BRINE keyword, and the PRECSALT keyword to activate OPM Flow’s Salt Precipitation Model. Both keywords are in the RUNSPEC section.","parameters":[{"index":1,"name":"SALTP","description":"SALTP is an array of real positive numbers that are greater than or equal to zero and less than or equal to one, that define the initial equilibration salt volume fraction values to each cell in the model. Repeat counts may be used, for example 20*0.15.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":"1"}],"example":"The example activates the standard Brine Tracking model using the BRINE keyword, OPM Flow’s Salt Precipitation model using the PRECSALT keyword, and OPM Flow’s vaporized water phase with the VAPWAT keyword; all three keywords are in the RUNSPEC section.\n-- ==============================================================================\n--\n-- RUNSPEC SECTION\n--\n-- ==============================================================================\nRUNSPEC\n--\n-- MAX MAX RSVD TVDP TVDP\n-- EQLNUM DEPTH NODES TABLE NODES\nEQLDIMS\n3 1* 20 1* 1* /\n--\n-- ACTIVATE STANDARD BRINE MODEL\n--\nBRINE\n--\n-- ACTIVATE THE OPM FLOW SALT PRECIPITATION MODEL (OPM FLOW KEYWORD)\n--\nPRECSALT\n--\n-- VAPORIZED WATER IN WET GAS IS PRESENT IN THE RUN (OPM FLOW KEYWORD)\n--\nVAPWAT\nThen in the SOLUTION section the SALTP keyword would be of the form:\n-- ==============================================================================\n--\n-- SOLUTION SECTION\n--\n-- ==============================================================================\nSOLUTION\n--\n-- DEFINE INITIAL PRECIPITATED SALT VOLUME FRACTION FOR ALL CELLS\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nSALTP\n1000*0.0000 1000*0.0000 1000*0.100 /\nHere the initial equilibration precipitated salt volume fraction values are set to 0.0000 for all the cells in the first and second layers and finally 0.1000 for all the cells in the third layer.\n| Note This is an OPM Flow specific keyword for the simulator’s Salt Precipitation Model that is activated by the PRECSALT keyword and declaring that vaporized water is present in the run via the VAPWAT in the RUNSPEC section. This keyword defines the initial precipitated salt volume fraction contained within the pore space. See SALT in the SOLUTION section that defines the initial salt concentration within the water phase. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"fixed","size_count":1,"variadic_record":true},"SALTPVD":{"name":"SALTPVD","sections":["SOLUTION"],"supported":true,"summary":"The SALTPVD keyword defines the initial precipitated salt volume fraction versus depth tables for each equilibration region for when OPM Flow’s Salt Precipitation Model has been activated in the input deck via the PRECSALT keyword in the RUNSPEC section. The keyword defines the initial deposited salt as a volume fraction (Ss), that is solid salt saturation.","parameters":[{"index":1,"name":"DEPTH","description":"A columnar vector of real monotonically increasing down the column values that defines the depth for corresponding salt volume fraction SALTPSAT.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":["Length","1"]},{"index":2,"name":"SALTPSAT","description":"A columnar vector of real values that defines the corresponding volume fraction of precipitated salt for the given depth. Note only the standard Brine Model is supported and therefore there should be only one columnar vector of SALTPSAT.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"The example activates the standard Brine Tracking model using the BRINE keyword, OPM Flow’s Salt Precipitation model using the PRECSALT keyword, and OPM Flow’s vaporized water phase with the VAPWAT keyword; all three keywords are in the RUNSPEC section. The example also sets the number of equilibrium regions to three (NTEQUL set to three on the EQLDIMS keyword also in the RUNSPEC), that is:\n-- ==============================================================================\n--\n-- RUNSPEC SECTION\n--\n-- ==============================================================================\nRUNSPEC\n--\n-- MAX MAX RSVD TVDP TVDP\n-- EQLNUM DEPTH NODES TABLE NODES\nEQLDIMS\n3 1* 20 1* 1* /\n--\n-- ACTIVATE STANDARD BRINE MODEL\n--\nBRINE\n--\n-- ACTIVATE THE OPM FLOW SALT PRECIPITATION MODEL (OPM FLOW KEYWORD)\n--\nPRECSALT\n--\n-- VAPORIZED WATER IN WET GAS IS PRESENT IN THE RUN (OPM FLOW KEYWORD)\n--\nVAPWAT\nThen in the SOLUTION section the SALTPVD keyword would be of the form:\n-- ==============================================================================\n--\n-- SOLUTION SECTION\n--\n-- ==============================================================================\nSOLUTION\n--\n-- PRECIPITATED SALT VOLUME FRACTION VERSUS DEPTH (OPM FLOW KEYWORD)\n--\n-- DEPTH SALTPSAT\n-- ------ --------\nSALTPVD\n3000.0 0.000\n8000.0 0.000 / EQUIL REGN 01\n-- ------ --------\n3000.0 0.000\n8000.0 0.000 / EQUIL REGN 02\n-- ------ --------\n3000.0 0.000\n8000.0 0.000 / EQUIL REGN 03\nHere the initial precipitated salt volume fraction has been set to zero for all three equilibration regions.\n| Note This is an OPM Flow specific keyword for the simulator’s Salt Precipitation Model that is activated by the PRECSALT keyword and declaring that vaporized water is present in the run via the VAPWAT in the RUNSPEC section. This is the initial precipitated salt volume fraction contained within the pore space, see SALTVD in the SOLUTION section that defines the initial salt concentration within the water phase. |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"fixed","variadic_record":true},"SALTREST":{"name":"SALTREST","sections":["SOLUTION"],"supported":false,"summary":"The SALTREST keyword defines restart salt concentration values for all grid cells in the model and should be used in runs that are using the RESTART facility, where the initial run has not used the Low Salt or Brine options. This allows for initial runs that have used the standard water PVT properties via the PVTW keyword in the PROPS section, to be restarted with salt dependent water properties. The keyword should only be used if the salt (brine) phase has been activated in the current restart run (not the initial run) via the BRINE keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"SALTREST","description":"SALTREST is an array of real positive numbers that are greater than or equal to zero assigning the restart salt concentration values to each cell in the model. Repeat counts may be used, for example 20*15.0.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None","value_type":"DOUBLE","dimension":"Concentration"}],"example":"--\n-- DEFINE RESTART SALTREST VALUES FOR ALL CELLS IN THE MODEL\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nSALTREST\n1000*0.0000 1000*0.0000 1000*15.000 /\nThe above example defines the restart salt concentration values to be 0.0000 for all the cells in the first and second layers and finally 15.000 for all the cells in the third layer.","size_kind":"fixed","size_count":1,"variadic_record":true},"SALTVD":{"name":"SALTVD","sections":["SOLUTION"],"supported":null,"summary":"The SALTVD keyword defines the initial salt concentration versus depth tables for each equilibration region for when the salt (brine) phase has been activated in the model via the BRINE keyword in the RUNSPEC section, and the EQLOPT1 variable has been set to a positive integer on the EQUIL keyword in the SOLUTION section. Secondly, the keyword should also be used to set the initial salt concentration versus depth if OPM Flow’s PRECSALT keyword in the RUNSPEC section has been used to activate the simulators Salt Precipitation model.","parameters":[{"index":1,"name":"DEPTH","description":"A columnar vector of real monotonically increasing down the column values that defines the depth for corresponding salt concentrations SALTCON.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":["Length","Concentration"]},{"index":2,"name":"SALTCON","description":"A columnar vector of real monotonically increasing down the column values that defines the corresponding salt concentration within the water phase for the given depth. There should be one columnar vector for each type of salt. For the standard Brine Model there is only one salt type and therefore there should be only one columnar vector of SALTCON. However, if the BRINE keyword has been invoked with the ECLMC keyword in the RUNSPEC section, then there should one columnar SALTCON vector for each declared salt type. It is recommended to provide initial salt concentrations less then or equal to values provided by SALTSOL keyword in the PROPS section.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None"}],"example":"The first example activates the standard Brine Tracking model using the BRINE keyword in the RUNSPEC section and sets the number of equilibrium regions to three (NTEQUIL set to 3 on the EQLDIMS keyword also in the RUNSPEC), that is:\n-- ==============================================================================\n--\n-- RUNSPEC SECTION\n--\n-- ==============================================================================\nRUNSPEC\n--\n-- MAX MAX RSVD TVDP TVDP\n-- EQLNUM DEPTH NODES TABLE NODES\nEQLDIMS\n3 1* 20 1* 1* /\n--\n-- ACTIVATE STANDARD BRINE MODEL\n--\nBRINE\nThen in the SOLUTION section the SALTVD keyword would be of the form:\n-- ==============================================================================\n--\n-- SOLUTION SECTION\n--\n-- ==============================================================================\nSOLUTION\n--\n-- DEPTH SALT-1 SALT-2 SALT-3 SALT-4\n-- SALTCON SALTCON SALTCON SALTCON\n-- ------ ------- ------- ------- ------- SALTVD\n3000.0 1.200\n8000.0 1.200 / EQUIL REGN 01\n-- ------ --------\n3000.0 1.300\n8000.0 1.300 / EQUIL REGN 02\n-- ------ --------\n3000.0 1.400\n8000.0 1.400 / EQUIL REGN 03\nThe next example shows how the SALTVD keyword is entered when both the ECLMC and BRINE keywords have activated the Multi-Component Brine model in the RUNSPEC section, that is:\n-- ==============================================================================\n--\n-- RUNSPEC SECTION\n--\n-- ==============================================================================\nRUNSPEC\n--\n-- MAX MAX RSVD TVDP TVDP\n-- EQLNUM DEPTH NODES TABLE NODES\nEQLDIMS\n3 1* 20 1* 1* /\n--\n--\n-- ACTIVATE MULTI-COMPONENT BRINE MODEL\n--\nECLMC\n--\n-- DEFINE WATER PHASE MULTI-COMPONENT BRINE COMPONENTS\n--\n-- SALT1 SALT2 SALT3 SALT4 SALT5\nBRINE\nNACL CACL MGC03 /\nThe above example activates the Multi-Component Brine model with three different water salinities for three equilibrium regions. In this case the resulting SALTVD keyword would be of the form:\n-- ==============================================================================\n--\n-- SOLUTION SECTION\n--\n-- ==============================================================================\nSOLUTION\n--\n-- DEPTH SALT-01 SALT-02 SALT-03 SALT-04\n-- CONCENTR CONCENTR CONCENTR CONCENTR\n-- ------ -------- -------- -------- -------- SALTVD\n3000.0 1.200 0.540 0.020\n7000.0 1.200 0.640 0.040 / EQUIL REGN 01\n-- ------ -------- -------- --------\n3000.0 1.300 0.440 0.020\n8000.0 1.300 0.540 0.040 / EQUIL REGN 02\n-- ------ -------- -------- --------\n5000.0 1.400 0.640 0.002\n8000.0 1.400 0.640 0.002 / EQUIL REGN 03\nIn this case there are three data sets, on one for each equilibrium region and three SALTCON columnar vectors, one for each salt type (NACL, CACL and MGC03) declared via the BRINE keyword in the RUNSPEC section.\nNote that the Multi-Component Brine model is not available in OPM Flow.\n| Note This is the initial salt concentration contained within the water phase, see the SALTPVD keyword in the SOLUTION section that defines the initial salt volume fraction that has been precipitated into the pore space. |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"fixed","variadic_record":true},"SBIOF":{"name":"SBIOF","sections":["SOLUTION"],"supported":null,"summary":"The SBIOF keyword defines the initial equilibration biofilm volume fraction for all grid cells in the model. The keyword should only be used if either the BIOFILM or MICP model has been activated in the RUNSPEC section.","parameters":[{"index":1,"name":"SBIOF","description":"SBIOF is an array of real numbers that are greater than or equal to zero and less than or equal to one assigning the initial equilibration biofilm volume fraction values to each cell in the model. Repeat counts may be used, for example 20*0.0010.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION BIOFILM VOLUME FRACTION FOR ALL CELLS\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nSBIOF\n10000*0.0000 10000*0.0000 10000*0.0010 /\nThe above example defines the initial equilibration biofilm volume fraction values to be 0.0000 for all the cells in the first and second layers and finally 0.0010 for all the cells in the third layer.\n| Note This is an OPM Flow specific keyword. |\n|--------------------------------------------|","size_kind":"array"},"SCALC":{"name":"SCALC","sections":["SOLUTION"],"supported":null,"summary":"The SCALC keyword defines the initial equilibration calcite volume fraction for all grid cells in the model. The keyword should only be used if the MICP model has been activated in the RUNSPEC section.","parameters":[{"index":1,"name":"SCALC","description":"SCALC is an array of real numbers that are greater than or equal to zero and less than or equal to one assigning the initial equilibration calcite volume fraction values to each cell in the model. Repeat counts may be used, for example 20*0.0010.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION CALCITE VOLUME FRACTION FOR ALL CELLS\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nSCALC\n1000*0.0000 1000*0.0000 1000*0.0010 /\nThe above example defines the initial equilibration calcite volume fraction values to be 0.0000 for all the cells in the first and second layers and finally 0.0010 for all the cells in the third layer.\n| Note This is an OPM Flow specific keyword. |\n|--------------------------------------------|","size_kind":"array"},"SCVD":{"name":"SCVD","sections":["SOLUTION"],"supported":false,"summary":"The SCVD keyword defines the initial coal solvent concentration versus depth tables for each equilibration region for when the coal phase has been activated in the run via the COAL keyword in the RUNSPEC section. The keyword may be used in conjunction with the SOLVCONC keyword in the SOLUTION section, to fully describe the initial state of the model. Note both SOLVCONC and SCVD are optional as the simulator will calculate the coal gas concentration based on the equilibrium concentration and the block pressure.","parameters":[{"index":1,"name":"DEPTH","description":"A columnar vector of real monotonically increasing down the column values that defines the depth values for the corresponding coal solvent concentration, SCVALS.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":["Length","1"]},{"index":2,"name":"SCVALS","description":"A columnar vector of real values that defines the coal solvent concentration values at the corresponding DEPTH.","units":{"field":"Mscf/ft3","metric":"sm3/m3","laboratory":"scc/cc"},"default":"None"}],"example":"Given NTEQUL equals three and NDRXVD is greater than or equal to two on the EQLDIMS keyword in the RUNSPEC section, then the following example defines the coal solvent concentration versus depth functions.\n--\n-- DEPTH SOLVC\n-- MSCF/FT\n-- ------ --------\nSCVD\n100.0 75.5000\n1000.0 75.5000 / SC VS DEPTH EQUIL REGN 01\n-- ------ --------\n100.0 65.5000\n1000.0 65.5000 / SC VS DEPTH EQUIL REGN 02\n-- ------ --------\n100.0 60.0000\n1000.0 60.0000 / SC VS DEPTH EQUIL REGN 03\nHere three tables are entered with a constant coal solvent concentration versus depth relationship for each equilibration region","size_kind":"fixed","variadic_record":true},"SFOAM":{"name":"SFOAM","sections":["SOLUTION"],"supported":false,"summary":"The SFOAM keyword defines the initial equilibration foam concentration values for all grid cells in the model and should be used in conjunction with the PBUB, PDEW, PRESSURE, RS, RV, SGAS, SGAS and SWAT keywords etc., to fully describe the initial state of the model. The keyword should only be used if the foam phase has been activated in the model via the FOAM keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"SFOAM","description":"SFOAM is an array of real positive numbers that are greater than or equal to zero assigning the initial equilibration foam concentration values to each cell in the model. Units are dependent on the transport phase specified via the FOAMOPT1 variable on the FOAMOPTS keyword in the PROPS section. FOAMOPT1 should be set to either GAS or WATER. Repeat counts may be used, for example 20*0.5","units":{"field":"Gas: lb/Mscf Water: lb/stb","metric":"Gas: kg/sm3 Water: kg/sm3","laboratory":"Gas: gm/scc Water: gm/scc"},"default":"None"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION FOAM VALUES FOR ALL CELLS IN THE MODEL\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nSFOAM\n1000*0.0000 1000*0.0000 1000*0.500 /\nThe above example defines the initial equilibration foam concentration values to be 0.0000 for all the cells in the first and second layers and finally 0.500 for all the cells in the third layer.","size_kind":"array"},"SGAS":{"name":"SGAS","sections":["SOLUTION"],"supported":null,"summary":"The SGAS keyword defines the initial equilibration gas saturation values for all grid cells in the model and should be used in conjunction with the PBUB, PDEW, PRESSURE, RS, RV, SOIL and SWAT keywords etc., to fully describe the initial state of the model. The keyword should only be used if the gas phase has been activated in the model via the GAS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"SGAS","description":"SGAS is an array of real positive numbers that are greater than or equal to zero and less than or equal to one assigning the initial equilibration gas saturation values to each cell in the model. Repeat counts may be used, for example 20*0.600.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION GAS SAT VALUES FOR ALL CELLS IN THE MODEL\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nSGAS\n1000*0.7000 1000*0.6500 1000*0.6000 /\nThe above example defines the initial equilibration gas saturation values to be 0.7000 for all the cells in the first layer, 0.6500 for all the cells in the second layer, and finally 0.6000 for all the cells in the third layer.","size_kind":"array"},"SMICR":{"name":"SMICR","sections":["SOLUTION"],"supported":null,"summary":"The SMICR keyword defines the initial equilibration microbial concentration values for all grid cells in the model. The keyword should only be used if either the BIOFILM or MICP model has been activated in the RUNSPEC section.","parameters":[{"index":1,"name":"SMICR","description":"SMICR is an array of real numbers that are greater than or equal to zero assigning the initial equilibration microbial concentration values to each cell in the model. Repeat counts may be used, for example 20*0.1500.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION MICROBIAL CONCENTRATION FOR ALL CELLS\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nSMICR\n1000*0.0000 1000*0.0000 1000*0.1500 /\nThe above example defines the initial equilibration microbial concentration values to be 0.0000 for all the cells in the first and second layers and finally 0.1500 for all the cells in the third layer.\n| Note This is an OPM Flow specific keyword. |\n|--------------------------------------------|","size_kind":"array"},"SOIL":{"name":"SOIL","sections":["SOLUTION"],"supported":null,"summary":"The SOIL keyword defines the initial equilibration oil saturation values for all grid cells in the model and should be used in conjunction with the PBUB, PDEW, PRESSURE, RS, RV, SGAS and SWAT keywords etc., to fully describe the initial state of the model. The keyword should only be used if the oil phase has been activated in the model via the OIL keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"SOIL","description":"SOIL is an array of real positive numbers that are greater than or equal to zero and less than or equal to one assigning the initial equilibration oil saturation values to each cell in the model. Repeat counts may be used, for example 20*0.600.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION OIL SAT VALUES FOR ALL CELLS IN THE MODEL\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nSOIL\n1000*0.7000 1000*0.6500 1000*0.6000 /\nThe above example defines the initial equilibration oil saturation values to be 0.7000 for all the cells in the first layer, 0.6500 for all the cells in the second layer, and finally 0.6000 for all the cells in the third layer.","size_kind":"array"},"SOLUTION":{"name":"SOLUTION","sections":["SOLUTION"],"supported":null,"summary":"The SOLUTION activation keyword marks the end of the REGIONS section and the start of the SOLUTION section that defines the parameters used to initialize the model, by:","parameters":[],"example":"-- ==============================================================================\n--\n-- SOLUTION SECTION\n--\n-- ==============================================================================\nSOLUTION\nThe above example marks the end of the REGIONS section and the start of the SOLUTION section in the OPM Flow data input file.","size_kind":"none","size_count":0},"SOLVCONC":{"name":"SOLVCONC","sections":["GRID"],"supported":false,"summary":"The SOLVCONC keyword defines the initial coal solvent concentration values for all matrix grid cells in the model and should be used in conjunction with the SCVD keyword in the SOLUTION section, to fully describe the initial state of the model. The keyword should only be used if the coal phase has been activated in the model via the COAL keyword in the RUNSPEC section. Note both SOLVCONC and SCVD are optional as the simulator will calculate the coal solvent concentration based on the equilibrium concentration and the block pressure.","parameters":[{"index":1,"name":"SOLVCONC","description":"SOLVCONC is an array of real positive numbers that define the initial equilibration coal solvent concentration values to each matrix cell in the model. Repeat counts may be used, for example 20*75.0.","units":{"field":"Mscf/ft3","metric":"sm3/m3","laboratory":"scc/cc"},"default":"None"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION COAL SOLVENT CONCENTRATION FOR ALL CELLS\n-- BASED ON NX = 100, NY = 100 AND NZ = 6\n--\nSOLVCONC\n1000*75.500 1000*65.500 1000*60.000 /\nThe above example defines the initial coal solvent concentration values to be 75.500 for all the matrix cells in the first layer, 65.500 for all the cells in the second layer, and finally 60.000 for all the cells in the third layer.","size_kind":"array"},"SOLVFRAC":{"name":"SOLVFRAC","sections":["SOLUTION"],"supported":false,"summary":"The SOLVFRAC keyword defines the initial solvent faction within the gas phase values for all matrix grid cells in the model. The keyword should only be used if the coal phase has been activated in the model via the COAL keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"SOLVFRAC","description":"SOLVFRAC is an array of real positive numbers that define the initial solvent fraction within the gas phase values for each matrix cell in the model. Repeat counts may be used, for example 20*0.075.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION GAS SOLVENT FRACTION FOR ALL CELLS\n-- BASED ON NX = 100, NY = 100 AND NZ = 6\n--\nSOLVFRAC\n1000*0.0250 1000*0.0350 1000*0.0500 /\nThe above example defines the initial gas solvent fraction values to be 0.250 for all the matrix cells in the first layer, 0.0350 for all the cells in the second layer, and finally 0.0500 for all the cells in the third layer.","size_kind":"array"},"SOXYG":{"name":"SOXYG","sections":["SOLUTION"],"supported":null,"summary":"The SOXYG keyword defines the initial equilibration oxygen concentration values for all grid cells in the model. The keyword should only be used if the MICP model has been activated in the RUNSPEC section.","parameters":[{"index":1,"name":"SOXYG","description":"SOXYG is an array of real numbers that are greater than or equal to zero assigning the initial equilibration oxygen concentration values to each cell in the model. Repeat counts may be used, for example 20*0.1500","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION OXYGEN CONCENTRATION FOR ALL CELLS\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nSOXYG\n1000*0.0000 1000*0.0000 1000*0.1500 /\nThe above example defines the initial equilibration oxygen concentration values to be 0.0000 for all the cells in the first and second layers and finally 0.1500 for all the cells in the third layer.\n| Note This is an OPM Flow specific keyword. |\n|--------------------------------------------|","size_kind":"array"},"SPOLY":{"name":"SPOLY","sections":["SOLUTION","SPECIAL"],"supported":null,"summary":"The SPOLY keyword defines the initial equilibration polymer concentration values for all grid cells in the model and should be used in conjunction with the PBUB, PDEW, PRESSURE, RS, RV, SGAS, SGAS and SWAT keywords etc., to fully describe the initial state of the model. The keyword should only be used if the polymer phase has been activated in the model via the POLYMER keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"SPOLY","description":"SPOLY is an array of real positive numbers that are greater than or equal to zero assigning the initial equilibration polymer concentration values to each cell in the model. Repeat counts may be used, for example 20*25.0.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION POLYMER VALUES FOR ALL CELLS IN THE MODEL\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nSPOLY\n1000*0.0000 1000*0.0000 1000*15.000 /\nThe above example defines the initial equilibration polymer concentration values to be 0.0000 for all the cells in the first and second layers and finally 15.000 for all the cells in the third layer.","size_kind":"array"},"SPOLYMW":{"name":"SPOLYMW","sections":["SOLUTION"],"supported":null,"summary":"The SPOLYMW keyword defines the initial equilibration polymer molecular weights for all grid cells in the model and should only be be used with OPM Flow's Polymer Molecular Weight Transport option, together with the other standard equilibration keywords, in order to fully describe the initial state of the model.","parameters":[{"index":1,"name":"SPOLYMW","description":"SPOLYMW is an array of real positive numbers that are greater than or equal to zero assigning the initial equilibration polymer molecular weights to each cell in the model. Repeat counts may be used, for example 20*5.0","units":{"field":"lb/lb-M","metric":"kg/kg-M","laboratory":"gm/gm-M"},"default":"0,0"}],"example":"--\n-- INITIAL EQUILIBRATION POLYMER MOLECULAR WEIGHTS FOR ALL CELLS\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nSPOLYMW 0.0000 1* 1* 1* 1* 1 5 / LAYERS 1 TO 5\nSPOLYMW 5.0000 1* 1* 1* 1* 6 7 / LAYERS 6 TO 7\nSPOLYMW 0.0000 1* 1* 1* 1* 8 20 / LAYERS 8 TO 20\n/\nThe above example defines the initial equilibration polymer molecular weights to be 0.0000 for all the cells, except for layers six to seven, where the polymer molecular weight is set to five for these cells.\n| Note This is an OPM Flow specific keyword that employs an alternative polymer flood model based on a Polymer Molecular Weight Transport equation, that is not available in the commercial simulator. The model has been tested using metric units; however, using either field or laboratory units with the option should be considered experimental. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"array"},"SSOL":{"name":"SSOL","sections":["SOLUTION"],"supported":null,"summary":"The SSOL keyword defines the initial equilibration solvent saturation values for all grid cells in the model and should be used in conjunction with the PBUB, PDEW, PRESSURE, RS, RV, SGAS, SOIL and SWAT keywords etc., to fully describe the initial state of the model. The keyword should only be used if the solvent phase has been activated in the model via the SOLVENT keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"SSOL","description":"SSOL is an array of real positive numbers that are greater than or equal to zero and less than or equal to one assigning the initial equilibration solvent saturation values to each cell in the model. Repeat counts may be used, for example 20*0.000.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION GAS SAT VALUES FOR ALL CELLS IN THE MODEL\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nSSOL\n1000*0.0000 1000*0.0000 1000*0.0000 /\nThe above example defines the initial equilibration solvent saturation values to be 0.0 for all the cells in the in the model.","size_kind":"array"},"SUREA":{"name":"SUREA","sections":["SOLUTION"],"supported":null,"summary":"The SUREA keyword defines the initial equilibration urea concentration values for all grid cells in the model. The keyword should only be used if the MICP model has been activated in the RUNSPEC section.","parameters":[{"index":1,"name":"SUREA","description":"SUREA is an array of real numbers that are greater than or equal to zero assigning the initial equilibration urea concentration values to each cell in the model. Repeat counts may be used, for example 20*30.0.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION UREA CONCENTRATION FOR ALL CELLS\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nSUREA\n1000*0.0000 1000*0.0000 1000*20.0 /\nThe above example defines the initial equilibration urea concentration values to be 0.0000 for all the cells in the first and second layers and finally 20.0 for all the cells in the third layer.\n| Note This is an OPM Flow specific keyword. |\n|--------------------------------------------|","size_kind":"array"},"SURF":{"name":"SURF","sections":["SOLUTION"],"supported":false,"summary":"The SURF keyword defines the initial equilibration surfactant concentration values for all grid cells in the model and should be used in conjunction with the PBUB, PDEW, PRESSURE, RS, RV, SGAS, SGAS and SWAT keywords etc., to fully describe the initial state of the model. The keyword should only be used if the surfactant phase has been activated in the model via the SURFACT keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"SURF","description":"SURF is an array of real positive numbers that are greater than or equal to zero assigning the initial equilibration surfactant concentration values to each cell in the model. Repeat counts may be used, for example 20*25.0.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION SURFACTANT VALUES FOR ALL CELLS\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nSURF\n1000*0.0000 1000*0.0000 1000*0.2500 /\nThe above example defines the initial equilibration surfactant concentration values to be 0.0000 for all the cells in the first and second layers and finally 0.2500 for all the cells in the third layer.","size_kind":"array"},"SWAT":{"name":"SWAT","sections":["SOLUTION"],"supported":null,"summary":"The SWAT keyword defines the initial equilibration water saturation values for all grid cells in the model and should be used in conjunction with the PBUB, PDEW, PRESSURE, RS, RV, SGAS and SOIL keywords etc., to fully describe the initial state of the model. The keyword should only be used if the water phase has been activated in the model via the WATER keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"SWAT","description":"SWAT is an array of real positive numbers that are greater than or equal to zero and less than or equal to one assigning the initial equilibration water saturation values to each cell in the model. Repeat counts may be used, for example 20*0.300.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION WAT SAT VALUES FOR ALL CELLS IN THE MODEL\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nSWAT\n1000*0.2000 1000*0.2500 1000*0.4500 /\nThe above example defines the initial equilibration water saturation values to be 0.2000 for all the cells in the first layer, 0.2500 for all the cells in the second layer, and finally 0.4500 for all the cells in the third layer.","size_kind":"array"},"TBLK":{"name":"TBLK","sections":["SOLUTION"],"supported":null,"summary":"TBLK keyword defines the initial tracer concentration for all or selected cells in the model, for when the TRACERS keyword in the RUNSPEC section has declared the maximum number of tracers for each phase, and the TRACER keyword in the PROPS section has defined the tracer. This keyword is not in the standard keyword format due to the tracer name being concatenated to the keyword TBLK to fully define the tracer being initialized.","parameters":[{"index":1,"name":"NAME","description":"A character string of up to eight characters, consisting of TBLK as the first four characters followed by a four letter character string defining the tracer’s name. The fifth character should either be the letter F or the letter S, that indicates the state of the tracer either to be free (F) or in solution (S). For example, TBLKFIGS (free) or TBLKSIGS (solution). The last three characters of NAME (the effective tracer name) must also match an entry on the TRACER keyword’s NAME parameter, in the PROPS section. Note it is best to void names beginning with the letters F, S, and T as these names may create naming issues in post-processing software.","units":{},"default":"None"},{"index":2,"name":"TBLK","description":"TBLK is an array of real numbers greater than or equal to zero, that are assigned the tracer concentration values for each cell in the model or the current input BOX. Repeat counts may be used, for example 200*0.0. The units for the tracer, if required, are set on the TRACER keyword in the PROPS section. This should be the same as the PHASE in the model.","units":{"field":"Liquid: TBLK/stb Gas: TBLK/Mscf","metric":"Liquid: TBLK/sm3 Gas: TBLK/sm3","laboratory":"Liquid: TBLK/scc Gas: TBLK/scc"},"default":"None"}],"example":"The following TRACERS keyword in the RUNSPEC section declares the number of tracers in the model.\n--\n-- NUMBER AND TYPE OF TRACERS\n-- NO OIL NO WAT NO GAS NO ENV DIFF MAX MIN TRACER\n-- TRACERS TRACERS TRACERS TRACERS CONTL NONLIN NONLIN NONLIN\nTRACERS\n0 0 1 0 'NODIFF' 1* 1* 1* /\nAnd the TRACER keyword in the PROPS section declares the tracer name and the phase for the tracer.\n--\n-- DEFINE TRACER NAMES\n--\n-- TRACER TRACER\n-- NAME PHASE\n-- ------ ------\nTRACER\n'IGS' 'GAS' / INJECTED GAS\n/\nFinally, the TBLK keyword in the SOLUTION section sets the initial tracer grid block concentrations in both the free and solution states.\n--\n-- INITIAL TRACER CONCENTRATIONS\n--\nTBLKFIGS\n1000*0.0 / TRACER FIGS CONCENTRATIONS\nTBLKSIGS\n1000*0.0 / TRACER SIGS CONCENTRATIONS\nHere the initial concentrations are set to zero.\nThen in the SCHEDULE section one can us the WTRACER keyword to define the well injecting the tracer and the tracer concentration being injected,.\n--\n-- DEFINE CONCENTRATION OF TRACERS IN THE INJECTION STREAMS,\n-- INJECTION TRACER CONCENTRATIONS NOT DEFINED USING THE WTRACER\n-- KEYWORD ARE ASSUMED TO BE ZERO.\n--\n-- WELL NAME TRACER TRACER TRACER\n-- NAME TRACER VALUE CUM GROUP\nWTRACER\n'GI01' 'IGS' 1.0 /\n/\nIn this case, well GI01 is a gas injection well injecting gas with a tracer concentration of 1.0. The example shows how to track dry gas injection in a gas condensate reservoir, although, the example can be used for any type of gas injection.\n| Note Currently, one cannot initialize tracers using the EQUALS keyword. Instead use the array format, that is the keyword followed by the required number of values, or the TVDP keyword in the SOLUTION section to set the initial tracer concentrations as a function of depth. |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"array"},"TEMPI":{"name":"TEMPI","sections":["SOLUTION"],"supported":null,"summary":"This keyword defines the initial reservoir temperature for each cell in the model. The keyword is used to explicitly define the initial reservoir temperature via the Enumeration Initialization method rather than defining a uniform initial temperature or defining temperature versus depth tables.","parameters":[{"index":1,"name":"TEMPI","description":"TEMPI is an array of real positive numbers assigning the initial temperature to each cell in the model. Repeat counts may be used, for example 20*100.0.","units":{"field":"oF","metric":"oC","laboratory":"oC"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK TEMPERATURE FOR ALL CELLS\n– (BASED ON NX x NY x NZ = 300)\n--\nTEMPI\n100*212.0 100*215.0 100*220.0 /\nThe above example defines the initial temperature to be 212.0, 215.0, and 220.0 oF for the first, second and third layers in the model for all 300 cells, as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"THPRES":{"name":"THPRES","sections":["SOLUTION"],"supported":false,"summary":"The THPRES defines the threshold pressure between various equilibration regions that have been defined by the EQLNUM keyword in the REGIONS section. The threshold pressure defines the potential difference between two regions which must be exceeded before flow can occur between the two regions. Once flow occurs the potential between the two regions is reduced by the threshold pressure.","parameters":[{"index":1,"name":"EQLNUM1","description":"EQLNUM1 is an a positive integer that is greater or equal to one and less than or equal to NTEQUL on the EQLDIMS keyword in the RUNSPEC section, that defines the “from” equilibration region number.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"INT"},{"index":2,"name":"EQLNUM2","description":"EQLNUM1 is an a positive integer that is greater or equal to one and less than or equal to NTEQUL on the EQLDIMS keyword in the RUNSPEC section, that defines the “to” equilibration region number.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"INT"},{"index":3,"name":"THPRES","description":"THPRES defines the threshold pressure from EQLNUM1 to EQLNUM2 and from EQLNUM2 to EQLNUM1. The default value of 1* sets the threshold pressure to a value that initially prevents flow between the two equilibration regions. Any subsequent production or injection in either of the two equilibration regions will therefore result in flow between the two regions. Thus, this default initially isolates the two equilibration regions. If a equilibration region number pair has not been explicitly defined by this keyword the THPRES is set to zero, for no threshold pressure.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1*","value_type":"DOUBLE","dimension":"Pressure"}],"example":"Given NTEQUL is equal to six on the EQLDIMS keyword in the RUNSPEC section,\n--\n-- EQLNUM EQLNUM THPRES\n-- FROM TO VALUE\nTHPRES\n1 2 0.588031 / REGN 1 TO REGN 2\n2 1 0.588031 / REGN 2 TO REGN 1\n1 3 0.787619 / REGN 1 TO REGN 3\n3 1 0.787619 / REGN 3 TO REGN 1\n1 4 7.000830 / REGN 1 TO REGN 4\n4 1 7.000830 / REGN 4 TO REGN 1\n/\nThe above example defines the threshold pressures between equilibration regions one and two, one and three and one and four. As the threshold pressures between regions one and five and one and six (as well as other combinations), have not been explicitly set in the example, the threshold pressures for these combinations are set to zero.\nHowever, as the irreversible option, as defined by IRREVER variable on EQLOPTS keyword in the RUNSPEC section, is not supported, then example can be simplified to:\n--\n-- EQLNUM EQLNUM THPRES\n-- FROM TO VALUE\nTHPRES\n1 2 0.588031 / REGN 1 AND REGN 2\n1 3 0.787619 / REGN 1 AND REGN 3\n1 4 7.000830 / REGN 1 AND REGN 4\n/\nAgain, as the threshold pressures between regions one and five and one and six (as well as other combinations), have not been explicitly set in the example, the threshold pressures for these combinations are set to zero.\n| Note Care should be taken that cells in different EQLNUM regions are not in communication, as this will result in an unstable initial equilibration. |\n|------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":3,"size_kind":"list"},"TVDP":{"name":"TVDP","sections":["SOLUTION"],"supported":null,"summary":"This keyword defines the initial equilibration tracer concentration versus depth functions for each grid cell in the model, for when the Tracer option has been enabled by the TRACERS keyword in the RUNSPEC section. The maximum number of tracers for each phase are declared on the TRACERS keyword in the RUNSPEC section. Unlike other keywords, the TVDP keyword must be concatenated with the name of the tracer declared by the TRACER keyword in the PROPS section as outlined in Table 10.61.","parameters":[{"index":1,"name":"DEPTH","description":"A columnar vector of real monotonically increasing down the column values that defines the depth values for the corresponding initial tracer saturations, TVDP","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":["Length","1"]},{"index":2,"name":"TVDPVAL","description":"A columnar vector of real values, greater than or equal to zero, that defines the initial tracer concentration values at the corresponding DEPTH. If tracer units have been defined by the UNITS parameter on the TRACER keyword in the PROPS section, then the units of TVDPVAL are the ratio of UNITS divided by the TVDPVAL units given below. For example, if UNITS was defined as kg, then for metric units TVDPVAL units would be kg/sm3.","units":{"field":"Liquid: stb Gas: Mscf","metric":"Liquid: sm3 Gas: sm3","laboratory":"Liquid: scc Gas: scc"},"default":"None"}],"example":"This example is taken from Norne model, in which there are seven tracers related to the water phase.\n-- ==============================================================================\n--\n-- RUNSPEC SECTION\n--\n-- ==============================================================================\nRUNSPEC\n--\n-- MAX MAX RSVD TVDP TVDP\n-- EQLNUM DEPTH NODES TABLE NODES\nEQLDIMS\n9 1* 20 7 1* /\n-- ==============================================================================\n--\n-- PROPS SECTION\n--\n-- ==============================================================================\nPROPS\n--\n-- DEFINE TRACER NAMES\n--\n-- TRACER TRACER\n-- NAME PHASE\n-- ------ ------\nTRACER\nSEA WAT /\nHTO WAT /\nS36 WAT /\n2FB WAT /\n4FB WAT /\nDFB WAT /\nTFB WAT /\n/\n-- ==============================================================================\n--\n-- SOLUTION SECTION\n--\n-- ==============================================================================\nSOLUTION\n--\n-- INITIAL EQUILIBRATION TRACER SATURATION VERSUS DEPTH\n--\n-- DEPTH TRACER\n-- CONCENT\n-- ------ --------\nTVDPFSEA\n1000.0 0.0\n5000.0 0.0 / TRACER FSEA CONCENTRATION VS DEPTH\nTVDPFHTO\n1000.0 0.0\n5000.0 0.0 / TRACER FHTO CONCENTRATION VS DEPTH\nTVDPFS36\n1000.0 0.0\n5000.0 0.0 / TRACER FS36 CONCENTRATION VS DEPTH\nTVDPF2FB\n1000.0 0.0\n5000.0 0.0 / TRACER F2FB CONCENTRATION VS DEPTH\nTVDPF4FB\n1000.0 0.0\n5000.0 0.0 / TRACER F4FB CONCENTRATION VS DEPTH\nTVDPFDFB\n1000.0 0.0\n5000.0 0.0 / TRACER FDFB CONCENTRATION VS DEPTH\nTVDPFTFB\n1000.0 0.0\n5000.0 0.0 / TRACER FTFB CONCENTRATION VS DEPTH\nHere we first define the number of tracers in the model via the EQLDIMS keyword in the RUNSPEC section, then the actual tracers themselves in the PROPS section using the TRACER keyword, and finally the initial tracer concentrations are all set to zero via the TVDP keyword in the PROPS section.","size_kind":"fixed","templated":true,"variadic_record":true},"VAPPARS":{"name":"VAPPARS","sections":["SOLUTION","SCHEDULE"],"supported":null,"summary":"VAPPARS defines the rate of oil vaporization in the presence of undersaturated gas and the rate at which the remaining oil gets “heavier” via the reduction in the solution gas-oil ratio (“Rs”). This keyword should only be used if the OIL, GAS, DISGAS and VAPOIL keywords in the RUNSPEC section have been invoked to allow oil, gas, dissolved gas and vaporized oil to be present in the model.","parameters":[{"index":1,"name":"VAPPAR1","description":"VAPPAR1 is a real positive dimensionless number that defines the rate at which oil vaporizes into the available undersaturated gas in a grid block. The default value of zero invokes the standard black-oil formulation in which all oil vaporizes into the available undersaturated phase in a grid cell. Increasing this parameter decreases the rate of vaporization. Typical values for VAPPAR1 range from zero to five.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0","value_type":"DOUBLE"},{"index":2,"name":"VAPPAR2","description":"VAPPAR2 is a real positive dimensionless number that defines the rate at which the Rs of the remaining oil in a grid cell decreases The default value of zero invokes the standard black-oil formulation in which the remaining oil’s Rs does not change as the oil vaporizes into the available undersaturated gas in a grid cell. Increasing this parameter increases the difference between the remaining oil and the vaporized oil Rs values. Typical values for VAPPAR2 are less than one.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0","value_type":"DOUBLE"}],"example":"The first example sets the black-oil default parameters\n--\n-- OIL VAPORIZATION PARAMETERS\n--\n-- OIL-VAP RS-INCS\n-- VAPPAR1 VAPPAR2\nVAPPARS\n0 0 /\nAnd the second example decreases the rate at which the oil vaporizes into the available undersaturated gas and increases the difference between the grid block oil saturation Rs and the vaporized oil Rs within a grid cell.\n--\n-- OIL VAPORIZATION PARAMETERS\n--\n-- OIL-VAP RS-INCS\n-- VAPPAR1 VAPPAR2\nVAPPARS\n1.5 0.150 /\nAgain, the keyword is normally used in history matching field performance to control the availability of the vaporized oil phase.","expected_columns":2,"size_kind":"fixed","size_count":1},"VISDATES":{"name":"VISDATES","sections":["SCHEDULE"],"supported":false,"summary":"The VISDATES keyword defines External Reservoir Geo-Mechanics VISAGE option stress dates. The keyword should not be used in input decks as the associated data is generated by an external program.","parameters":[{"index":1,"name":"DAY","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"MONTH","description":"","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"YEAR","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"TIMESTAMP","description":"","units":{},"default":"00:00:00","value_type":"STRING"}],"example":"","expected_columns":4,"size_kind":"list"},"VISOPTS":{"name":"VISOPTS","sections":["SOLUTION"],"supported":false,"summary":"The VISDATES keyword defines External Reservoir Geo-Mechanics VISAGE option modeling options. The keyword should not be used in input decks as the associated data is generated by an external program.","parameters":[{"index":1,"name":"INIT_RUN","description":"","units":{},"default":"NO","value_type":"STRING"},{"index":2,"name":"EXIT","description":"","units":{},"default":"NO","value_type":"STRING"},{"index":3,"name":"ACTIVE","description":"","units":{},"default":"NO","value_type":"STRING"},{"index":4,"name":"REL_TOL","description":"","units":{},"default":"0.05","value_type":"DOUBLE"},{"index":5,"name":"UNUSED","description":"","units":{},"default":"","value_type":"STRING"},{"index":6,"name":"RETAIN_RESTART_FREQUENCY","description":"","units":{},"default":"NO","value_type":"STRING"},{"index":7,"name":"RETAIN_RESTART_CONTENT","description":"","units":{},"default":"NO","value_type":"STRING"},{"index":8,"name":"ERROR","description":"","units":{},"default":"ERROR","value_type":"STRING"}],"example":"","expected_columns":8,"size_kind":"list"},"ALL":{"name":"ALL","sections":["SUMMARY"],"supported":null,"summary":"This keyword activates the writing out of a standard set of summary production and injection data vectors for the field, group and well objects to the SUMMARY (*.SMSPEC and *.UNSMRY) and RSM (*.RSM) files. Table 11.26lists the production, injection, pressure and volume summary variables written out by the ALL keyword, and Table 11.27list the aquifer variables.","parameters":[],"example":"-- ==============================================================================\n--\n-- SUMMARY SECTION\n--\n-- ==============================================================================\nSUMMARY\n--\n-- EXPORT STANDARD SUMMARY VARIABLE VECTORS TO FILE\n--\nALL\n--\n-- ACTIVATE COLUMNAR SUMMARY DATA REPORTING OPTION\n--\nRUNSUM\n--\n-- ACTIVATE SUMMARY DATA RSM FILE OUTPUT OPTION\n--\nSEPARATE\nNote the SEPARATE keyword is not required for OPM Flow as this is the default behavior; however, it is probably good practice to include it if the same input decks are being run with commercial simulator.\n| Standard Production, Injection, and Pressures Summary Variables | | | | | |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-------|-------|------|-----------------------------------------------------------|\n| Variable | Root | Field | Group | Well | Comment |\n| Gas Injection Rate | GIR | FGIR | GGIR | WGIR | |\n| Gas Injection Total | GIT | FGIT | GGIT | WGIT | |\n| Gas Production Rate | GPR | FGPR | GGPR | WGPR | Produced reservoir gas only, gas lift gas is excluded. |\n| Gas Production Total | GPT | FGPT | GGPT | WGPT | |\n| Oil Injection Rate | OIR | FOIR | GOIR | WOIR | |\n| Oil Injection Total | OIT | FOIT | GOIT | WOIT | |\n| Oil Production Rate ","size_kind":"none","size_count":0},"DATE":{"name":"DATE","sections":["SUMMARY"],"supported":null,"summary":"This keyword activates the writing out of the date of each time step to the SUMMARY file. Normally only the time in days and decimal years are written out to the SUMMARY file, activating the DATE option also results in the DATE being written out to the SUMMARY file as well. This option is normally used when the RUNSUM keyword in the SUMMARY section has been activated to produce a RSM file.","parameters":[],"example":"The following example shows an example RSM file output when the DATE option has not been activated.\n-------------------------------------------------------------------------------\nSUMMARY OF RUN NO-DATE-KEYWORD\n-------------------------------------------------------------------------------\nTIME YEARS FPR FOEW FOPR FOPT\nDAYS YEARS PSIA STB/DAY STB\n-------------------------------------------------------------------------------\n0 0 4467.125 0 0 0\n1.000000 0.002738 4466.943 0.000239 3235.662 3235.662\n31.00000 0.084873 4464.476 0.007407 3230.117 100256.4\n60.00000 0.164271 4462.717 0.014291 3193.902 193421.5\n91.00000 0.249144 4460.813 0.021523 3127.557 291306.3\n121.0000 0.331280 4458.909 0.028362 3055.878 383879.7\n152.0000 0.416153 4456.914 0.035262 2982.212 477271.4\n……………………………………………….\nAnd activating the SUMMARY file DATE option with:\n--\n-- ACTIVATE DATE SUMMARY FILE OPTION\n--\nDATE\nResults in the following example RSM file output.\n-------------------------------------------------------------------------------\nSUMMARY OF RUN WITH-DATE-KEYWORD\n-------------------------------------------------------------------------------\nDATE YEARS DAY MONTH YEAR FPR FOEW FOPR\nYEARS PSIA STB/DAY\n-------------------------------------------------------------------------------\n1-JAN-98 0 19 10 1992 4467.125 0 0\n2-JAN-98 0.002738 20 10 1992 4466.943 0.000239 3235.662\n31-JAN-98 0.084873 21 10 1992 4464.476 0.007407 3230.117\n28-FEB-98 0.164271 24 10 1992 4462.717 0.014291 3193.902\n31-MAR-98 0.249144 28 10 1992 4460.813 0.021523 3127.557\n30-APR-98 0.331280 3 11 1992 4458.909 0.028362 3055.878\n31-MAY-98 0.416153 14 11 1992 4456.914 0.035262 2982.212\n……………………………………………….","size_kind":"none","size_count":0},"EXCEL":{"name":"EXCEL","sections":["SUMMARY"],"supported":false,"summary":"This keyword activates the writing out of the RSM file data in a format that can easily be loaded into Microsoft's EXCEL spreadsheet program or LibreOffice’s CALC spreadsheet program. The RSM file output is activated by the RUNSUM keyword in the SUMMARY section.","parameters":[],"example":"-- ==============================================================================\n--\n-- SUMMARY SECTION\n--\n-- ==============================================================================\nSUMMARY\n--\n-- ACTIVATE COLUMNAR SUMMARY DATA REPORTING OPTION\n--\nRUNSUM\n--\n-- ACTIVATE EXCEL SUMMARY FILE OPTION\n--\nEXCEL\nThe above example activates the SUMMARY file EXCEL option for directly loading the RSM file into either Microsoft's EXCEL or LibreOffice’s CALC spreadsheet programs.","size_kind":"none","size_count":0},"FMWSET":{"name":"FMWSET","sections":["SUMMARY"],"supported":false,"summary":"This keyword is similar to the ALL keyword in the SUMMARY section, in that it results in a group of summary variables to be written out to the SUMMARY file. In this case the keyword activates the writing out of a set of data vectors that give the production and injections status of all the wells in the model, as well as the number of wells in the drilling queue and the number of workover events occurring within a time step. Both instantaneous and cumulative well counts and events are written out as listed in Table 11.28.","parameters":[],"example":"-- ==============================================================================\n--\n-- SUMMARY SECTION\n--\n-- ==============================================================================\nSUMMARY\n--\n-- EXPORT WELL STATUS VECTORS FOR THE FIELD TO FILE\n--\nFMWSET\n--\n-- ACTIVATE COLUMNAR SUMMARY DATA REPORTING OPTION\n--\nRUNSUM\n--\n-- ACTIVATE SUMMARY DATA RSM FILE OUTPUT OPTION\n--\nSEPARATE\nThe above example exports the field standard well status variables to the SUMMARY file.\n| Field and Group Well Status Summary Variables | | | | |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-------|-------|---------|\n| Variable | Root | Field | Group | Comment |\n| Number of abandoned injection wells | MWIA | FMWIA | GMWIA | |\n| Number of abandoned production wells | MWPA | FMWPA | GMWPA | |\n| Number of drilling events in total | MWDT | FMWDT | GMWDT | |\n| Number of drilling events this time step | MWDR | FMWDR | GMWDR | |\n| Number of injection wells currently flowing | MWIN | FMWIN | GMWIN | |\n| Number of injectors on group control | MWIG | FMWIG | GMWIG | |\n| Number of injectors on own reservoir volume rate limit control ","size_kind":"none","size_count":0},"GMWSET":{"name":"GMWSET","sections":["SUMMARY"],"supported":false,"summary":"This keyword is similar to the ALL keyword in the SUMMARY section, in that it results in a group of summary variables to be written out to the SUMMARY file. In this case the keyword activates the writing out of a set of data vectors that give the production and injections status of all the wells in the named groups, as well as the number of wells in the drilling queue and the number of workover events occurring within a time step for the requested groups. Both instantaneous and cumulative well counts and events for the groups are written out as tabulated in Table 11.29.","parameters":[],"example":"The first example below exports all the group standard well status variables to the SUMMARY file.\n-- ==============================================================================\n--\n-- SUMMARY SECTION\n--\n-- ==============================================================================\nSUMMARY\n--\n-- EXPORT WELL STATUS VECTORS FOR NAMED GROUPS TO FILE\n--\nGMWSET\n/\n--\n-- ACTIVATE COLUMNAR SUMMARY DATA REPORTING OPTION\n--\nRUNSUM\n--\n-- ACTIVATE SUMMARY DATA RSM FILE OUTPUT OPTION\n--\nSEPARATE\nThe second example exports all the group standard well status variables for just the PLAT1 and PLT2 groups only to the SUMMARY file.\n--\n-- EXPORT WELL STATUS VECTORS FOR NAMED GROUPS TO FILE\n--\nGMWSET\n‘PLAT1’ ‘PLAT2’\n/\n--\n-- ACTIVATE COLUMNAR SUMMARY DATA REPORTING OPTION\n--\nRUNSUM\n--\n-- ACTIVATE SUMMARY DATA RSM FILE OUTPUT OPTION\n--\nSEPARATE\n| Field and Group Well Status Summary Variables | | | | |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-------|-------|---------|\n| Variable | Root | Field | Group | Comment |\n| Number of abandoned injection wells | MWIA | FMWIA | GMWIA | |\n| Number of abandoned production wells | MWPA | FMWPA | GMWPA | |\n| Number of drilling events in total | MWDT | FMWDT | GMWDT | |\n| Number of drilling events this timestep | MWDR | FMWDR | GMWDR | |\n| Number of injection wells currently flowing | MWIN | FMWIN | GMWIN | |\n| Number of injectors on group control ","size_kind":"none","size_count":0},"NARROW":{"name":"NARROW","sections":["SUMMARY"],"supported":false,"summary":"The NARROW keyword activates the Run Summary Narrow Column Output option, for when printed SUMMARY data has been requested by the RUNSUM keyword in the SUMMARY section. The option increases the number of columns “printed on the page”.","parameters":[],"example":"","size_kind":"none","size_count":0},"NEWTON":{"name":"NEWTON","sections":["SUMMARY"],"supported":null,"summary":"This keyword activates the writing out of the Newton iteration vector (the number of non-linear iterations per time step) to the SUMMARY file, and the RSM file if the RSM file option has been requested by the RUNSUM keyword in the SUMMARY section,","parameters":[],"example":"-- ==============================================================================\n--\n-- SUMMARY SECTION\n--\n-- ==============================================================================\nSUMMARY\n--\n-- ACTIVATE COLUMNAR SUMMARY DATA REPORTING OPTION\n--\nRUNSUM\n--\n-- ACTIVATE SUMMARY DATA RSM FILE OUTPUT OPTION\n--\nSEPARATE --\n-- ACTIVATE NEWTON ITERATION SUMMARY OUTPUT\n--\nNEWTON\nThe above example actives the writing out of the Newton iteration vector to the SUMMARY file."},"NMESSAGE":{"name":"NMESSAGE","sections":["SUMMARY"],"supported":true,"summary":"This keyword activates the writing out of a standard set of summary OPM Flow simulation performance summary variables to the SUMMARY (*.SMSPEC and *.UNSMRY) and RSM (*.RSM) files, namely the number of messages written per message class. Table 11.30lists the summary variables written out by the NMESSAGE keyword.","parameters":[],"example":"-- ==============================================================================\n--\n-- SUMMARY SECTION\n--\n-- ==============================================================================\nSUMMARY\n--\n-- EXPORT PERFORMANCE CUMULATIVE MESSAGE VARIABLE VECTORS TO FILE\n--\nNMESSAGE\n--\n-- ACTIVATE COLUMNAR SUMMARY DATA REPORTING OPTION\n--\nRUNSUM\n--\n-- ACTIVATE SUMMARY DATA RSM FILE OUTPUT OPTION\n--\nSEPARATE\nNote the SEPARATE keyword is not required for OPM Flow as this is the default behavior; however, it is probably good practice to include it if the same input decks are being run with the commercial simulator.\n| OPM Flow Simulator Performance Summary Variables Cumulative Message Variables | | |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|--------------|\n| Variable Description | Variable | Comment |\n| Messages - Cumulative number of BUG messages. | MSUMBUG | Unsupported. |\n| Messages - Cumulative number of COMMENT messages. | MSUMCOMM | Unsupported. |\n| Messages - Cumulative number of ERROR messages. | MSUMERR | Unsupported. |\n| Messages - Cumulative number of MESSAGES messages. ","size_kind":"none","size_count":0},"OFM":{"name":"OFM","sections":["SUMMARY"],"supported":false,"summary":"This keyword activates the writing out of the SUMMARY file data in the Oil Field Manager (“OFM”) file format to enable the simulated data to be directly loaded into Oil Field Manager.","parameters":[],"example":"","size_kind":"none","size_count":0},"PERFORMA":{"name":"PERFORMA","sections":["SUMMARY"],"supported":null,"summary":"The PERFORMA keyword activates the writing out of a standard set of OPM Flow simulation numerical performance summary variables to the SUMMARY (*.SMSPEC and .*UNSMRY) and RSM (*.RSM) files. Table 11.31lists the summary variables written out by the keyword.","parameters":[],"example":"-- ==============================================================================\n--\n-- SUMMARY SECTION\n--\n-- ==============================================================================\nSUMMARY\n--\n-- EXPORT NUMERICAL PERFORMANCE SUMMARY VARIABLES TO FILE\n--\nPERFORMA\n--\n-- ACTIVATE COLUMNAR SUMMARY DATA REPORTING OPTION\n--\nRUNSUM\n--\n-- ACTIVATE SUMMARY DATA RSM FILE OUTPUT OPTION\n--\nSEPARATE\nNote the SEPARATE keyword is not required for OPM Flow as this is the default behavior; however, it is probably good practice to include it if the same input decks are being run with commercial simulator.\n| OPM Flow Simulator Performance Summary Variables Numerical Performance Variables | | |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Variable Description | Variable | Comment |\n| Elapsed - Elapsed time in seconds. | ELAPSED | No data written to file. |\n| Iterations - Number linear iterations for each time step. | MLINEARS | |\n| Iterat"},"RPTONLY":{"name":"RPTONLY","sections":["SUMMARY","SCHEDULE"],"supported":null,"summary":"This keyword activates the writing out of the SUMMARY file and the RSM file data, if the RSM file option has been requested by the RUNSUM keyword in the SUMMARY section, at report time steps only. The default is for the data to be written out for all time steps to the SUMMARY files. This keyword reduces the file size at the expense of lower resolution in the time domain.","parameters":[],"example":"-- ==============================================================================\n--\n-- SUMMARY SECTION\n--\n-- ==============================================================================\nSUMMARY\n--\n-- EXPORT STANDARD SUMMARY VARIABLE VECTORS TO FILE\n--\nALL\n--\n-- ACTIVATE COLUMNAR SUMMARY DATA REPORTING OPTION\n--\nRUNSUM\n--\n-- ACTIVATE SUMMARY DATA RSM FILE OUTPUT OPTION\n--\nSEPARATE\n--\n-- ACTIVATE REPORT TIME STEPS ONLY SUMMARY FILE OPTION\n--\nRPTONLY\nThe above example activates the writing out of the SUMMARY file at report time steps only.","size_kind":"none","size_count":0},"RPTONLYO":{"name":"RPTONLYO","sections":["SUMMARY","SCHEDULE"],"supported":null,"summary":"This keyword deactivates the writing out of the SUMMARY file and the RSM file data, if the RSM file option has been requested by the RUNSUM keyword in the SUMMARY section, at report time steps only, and switches on writing out all the time steps to the files. This option is the default behavior for when RPTONLY has not been activated.","parameters":[],"example":"-- ==============================================================================\n--\n-- SUMMARY SECTION\n--\n-- ==============================================================================\nSUMMARY\n--\n-- EXPORT STANDARD SUMMARY VARIABLE VECTORS TO FILE\n--\nALL\n--\n-- ACTIVATE COLUMNAR SUMMARY DATA REPORTING OPTION\n--\nRUNSUM\n--\n-- ACTIVATE SUMMARY DATA RSM FILE OUTPUT OPTION\n--\nSEPARATE\n--\n-- DEACTIVATE REPORT TIME STEPS ONLY SUMMARY FILE OPTION\n--\nRPTONLYO\nThe above example deactivates the writing out of the SUMMARY file at report time steps only, and switches on writing out all the time steps to the file.","size_kind":"none","size_count":0},"RPTSMRY":{"name":"RPTSMRY","sections":["SUMMARY"],"supported":false,"summary":"This keyword activates or deactivates a listing of all the summary variables that are going to be written to the SUMMARY file and the RSM file, if the RSM file option has been requested by the RUNSUM keyword in the SUMMARY section.","parameters":[{"index":1,"name":"RPTSMRY","description":"An integer value set to zero for no report, or one to produce the report.","units":{},"default":"0","value_type":"INT"}],"example":"-- ==============================================================================\n--\n-- SUMMARY SECTION\n--\n-- ==============================================================================\nSUMMARY\n--\n-- EXPORT STANDARD SUMMARY VARIABLE VECTORS TO FILE\n--\nALL\n--\n-- ACTIVATE COLUMNAR SUMMARY DATA REPORTING OPTION\n--\nRUNSUM\n--\n-- ACTIVATE SUMMARY DATA RSM FILE OUTPUT OPTION\n--\nSEPARATE\n--\n-- ACTIVATE OR DEACTIVATE SUMMARY LIST REPORT\n--\nRPTSMRY\n1 /\nThe example switches on the summary list report.","expected_columns":1,"size_kind":"fixed","size_count":1},"RUNSUM":{"name":"RUNSUM","sections":["SUMMARY"],"supported":null,"summary":"This keyword activates the writing out of the SUMMARY file data in a columnar format to the PRT file. Normally the SEPARATE keyword in the SUMMARY section is invoked in the same run to direct the data stream to a separate RSM file for easy loading into other programs, for example, Microsoft's EXCEL or LibreOffice’s CALC spreadsheet programs.","parameters":[],"example":"-- ==============================================================================\n--\n-- SUMMARY SECTION\n--\n-- ==============================================================================\nSUMMARY\n--\n-- ACTIVATE COLUMNAR SUMMARY DATA REPORTING OPTION\n--\nRUNSUM\n--\n-- ACTIVATE SUMMARY DATA RSM FILE OUTPUT OPTION\n--\nSEPARATE\nNote unlike the commercial simulator, OPM Flow always writes out the data to a separate file.","size_kind":"none","size_count":0},"SEPARATE":{"name":"SEPARATE","sections":["SUMMARY"],"supported":null,"summary":"This keyword activates the writing out of the SUMMARY file date in a columnar format to the RSM file, if the RUNSUM keyword has also been activated in the SUMMARY section. Both the SEPARATE and the RUNSUM keywords need to be invoked. If the SEPARATE option is not activated then the RSM output is directed to the end of the PRT file. Normally the both the SEPARATE and RUNSUM keywords are invoked in the same run to enable easy loading of the data into Microsoft's EXCEL or LibreOffice’s CALC spreadsheet programs.","parameters":[],"example":"-- ==============================================================================\n--\n-- SUMMARY SECTION\n--\n-- ==============================================================================\nSUMMARY\n--\n-- ACTIVATE COLUMNAR SUMMARY DATA REPORTING OPTION\n--\nRUNSUM\n--\n-- ACTIVATE SUMMARY DATA RSM FILE OUTPUT OPTION\n--\nSEPARATE\nNote unlike the commercial simulator, OPM Flow always writes out the data to a separate file; however, it is probably good practice to include it if the same input decks are being run with commercial simulator.","size_kind":"none","size_count":0},"SUMMARY":{"name":"SUMMARY","sections":["SUMMARY"],"supported":null,"summary":"The SUMMARY activation keyword marks the end of the SOLUTION section and the start of the SUMMARY section that defines the variables to be written out to the SUMMARY file for reporting and plotting of grid block data, production data, etc.","parameters":[],"example":"-- ==============================================================================\n--\n-- SUMMARY SECTION\n--\n-- ==============================================================================\nSUMMARY\nThe above example marks the end of the SOLUTION section and the start of the SUMMARY section in the OPM Flow data input file.","size_kind":"none","size_count":0},"SUMTHIN":{"name":"SUMTHIN","sections":["SUMMARY","SCHEDULE"],"supported":null,"summary":"This keyword defines a time interval for writing out the SUMMARY data to the SUMMARY file and the RSM file, if the RUNSUM keyword has also been activated in the SUMMARY section. Only the data for the first time step in the time interval is written out and the other time steps are skipped until the next time interval, except for report time steps. Note that report time steps data are always written out regardless of the setting on this keyword. This enables the size of the SUMMARY files to be reduced depending on the size of the time interval. However, the keyword will produce irregular time steps reports of the SUMMARY data.","parameters":[{"index":1,"name":"SUMSTEP","description":"SUMSTEP is a real positive number that defines the time interval for which the first time step of data will be written to the SUMMARY file (and the RSM file if RSM output has been activated). For example, if SUMSTEP is set to 30 days, and if the simulator takes time steps of 0, 5, 10, 16, 24, 30, 40, 45, 60, 90 days. Then the SUMMARY data will be written out at time steps 0, 30, 40 and 60 days.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"None","value_type":"DOUBLE","dimension":"Time"}],"example":"--\n-- DEFINE SUMMARY DATA REPORTING TIME STEP INTERVAL\n--\n-- SUMSTEP\nSUMTHIN\n30.0 / /\nThe above example defines the SUMMARY file time step interval to be 30 days for both field and metric units.","expected_columns":1,"size_kind":"fixed","size_count":1},"ACTION":{"name":"ACTION","sections":["SCHEDULE"],"supported":false,"summary":"The ACTION keyword defines a series of conditions that invoke run time processing of ACTION functions and is similar to executing a run time script for conditions and variables at the field level.","parameters":[{"index":1,"name":"ACTION_NAME","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"QUANTITY","description":"","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"OPERATOR","description":"","units":{},"default":"","value_type":"STRING"},{"index":4,"name":"TRIGGER_VALUE","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","expected_columns":4,"size_kind":"fixed","size_count":1},"ACTIONG":{"name":"ACTIONG","sections":["SCHEDULE"],"supported":false,"summary":"The ACTIONG keyword defines a series of conditions that invoke run time processing of ACTION functions and is similar to executing a run time script for conditions and variables at the group level","parameters":[{"index":1,"name":"ACTION","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"GROUP_NAME","description":"","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"QUANTITY","description":"","units":{},"default":"","value_type":"STRING"},{"index":4,"name":"OPERATOR","description":"","units":{},"default":"","value_type":"STRING"},{"index":5,"name":"TRIGGER_VALUE","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":6,"name":"REPETITIONS","description":"","units":{},"default":"1","value_type":"INT"},{"index":7,"name":"INCREMENT","description":"","units":{},"default":"0","value_type":"DOUBLE"}],"example":"","expected_columns":7,"size_kind":"fixed","size_count":1},"ACTIONR":{"name":"ACTIONR","sections":["SCHEDULE"],"supported":false,"summary":"The ACTIONR keyword defines a series of conditions that invoke run time processing of ACTION functions and is similar to executing a run time script for conditions and variables at the region level.","parameters":[{"index":1,"name":"ACTION","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"FLUID_IN_PLACE_NR","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"FLUID_IN_PLACE_REG_FAM","description":"","units":{},"default":"","value_type":"STRING"},{"index":4,"name":"QUANTITY","description":"","units":{},"default":"","value_type":"STRING"},{"index":5,"name":"OPERATOR","description":"","units":{},"default":"","value_type":"STRING"},{"index":6,"name":"TRIGGER_VALUE","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":7,"name":"REPETITIONS","description":"","units":{},"default":"1","value_type":"INT"},{"index":8,"name":"INCREMENT","description":"","units":{},"default":"0","value_type":"DOUBLE"}],"example":"","expected_columns":8,"size_kind":"fixed","size_count":1},"ACTIONS":{"name":"ACTIONS","sections":["SCHEDULE"],"supported":false,"summary":"The ACTIONS keyword defines a series of conditions that invoke run time processing of ACTION functions and is similar to executing a run time script for conditions and variables associated with well segments.","parameters":[{"index":1,"name":"ACTION","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"WELL_SEGMENT","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"QUANTITY","description":"","units":{},"default":"","value_type":"STRING"},{"index":5,"name":"OPERATOR","description":"","units":{},"default":"","value_type":"STRING"},{"index":6,"name":"TRIGGER_VALUE","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":7,"name":"REPETITIONS","description":"","units":{},"default":"1","value_type":"INT"},{"index":8,"name":"INCREMENT","description":"","units":{},"default":"0","value_type":"DOUBLE"}],"example":"","expected_columns":8,"size_kind":"fixed","size_count":1},"ACTIONW":{"name":"ACTIONW","sections":["SCHEDULE"],"supported":false,"summary":"This keyword starts the definition of an ACTIONW section that stipulates the Boolean conditions to test the nominated well parameters, and the resulting SCHEDULE keywords to be executed, if the Boolean condition evaluates to true. An ACTIONW Definition Section is terminated by an ENDACTIO keyword on a separate line. Here, the keyword defines a series of conditions applied to wells only, that invoke run time processing of ACTION functions, and is similar to executing a run time script for conditions and variables at the well level. The ACTION series of keywords (ACTION, ACTIONG, ACTIONR, ACTIONS and ACTIONW) can apply Boolean conditional tests to variables at the field, group, region, well segment and well levels.","parameters":[{"index":1,"name":"Bottom-Hole Pressure","description":"WBHP","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"Gas Injection Rate","description":"WGIR","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"Gas Injection Total","description":"WGIT","units":{},"default":"","value_type":"STRING"},{"index":4,"name":"Gas-Liquid Ratio","description":"WGLR","units":{},"default":"","value_type":"STRING"},{"index":5,"name":"Gas-Liquid Ratio (Bottom Hole)","description":"WBGLR","units":{},"default":"","value_type":"DOUBLE"},{"index":6,"name":"Gas-Oil Ratio","description":"WGOR","units":{},"default":"","value_type":"INT"},{"index":7,"name":"Gas Production Rate","description":"WGPR","units":{},"default":"","value_type":"DOUBLE"},{"index":8,"name":"Gas Production Total","description":"WGPT","units":{},"default":""},{"index":9,"name":"Liquid Production Rate","description":"WLPR","units":{},"default":""},{"index":10,"name":"Liquid Production Rate","description":"WLPT","units":{},"default":""},{"index":11,"name":"Oil Injection Rate","description":"WOIR","units":{},"default":""},{"index":12,"name":"Oil Injection Total","description":"WOIT","units":{},"default":""},{"index":13,"name":"Oil Production Rate","description":"WOPR","units":{},"default":""},{"index":14,"name":"Oil Production Total","description":"WOPT","units":{},"default":""},{"index":15,"name":"Polymer Production Concentration","description":"WCPC","units":{},"default":""},{"index":16,"name":"Polymer Production Rate","description":"WCPR","units":{},"default":""},{"index":17,"name":"Salt Production Concentration","description":"WSPC","units":{},"default":""},{"index":18,"name":"Salt Production Rate","description":"WSPR","units":{},"default":""},{"index":19,"name":"Tracer Production Concentration (Tracer name should be added to WTPC)","description":"WTPC","units":{},"default":""},{"index":20,"name":"Tracer Production Rate (Tracer name should be added to WTPC)","description":"WTPR","units":{},"default":""},{"index":21,"name":"Tubing Head Pressure","description":"WTHP","units":{},"default":""},{"index":22,"name":"Voidage Injection Rate","description":"WVIR","units":{},"default":""},{"index":23,"name":"Voidage Injection Total","description":"WVIT","units":{},"default":""},{"index":24,"name":"Voidage Production Rate","description":"WVPR","units":{},"default":""},{"index":25,"name":"Voidage Production Total","description":"WVPT","units":{},"default":""},{"index":26,"name":"Water Cut","description":"WWCT","units":{},"default":""},{"index":27,"name":"Water Injection Rate","description":"WWIR","units":{},"default":""},{"index":28,"name":"Water Injection Total","description":"WWIT","units":{},"default":""},{"index":29,"name":"Water Production Rate","description":"WWPR","units":{},"default":""},{"index":30,"name":"Water Production Total","description":"WWPT","units":{},"default":""},{"index":31,"name":"Water-Gas Ratio","description":"WWGR","units":{},"default":""},{"index":32,"name":"User Defined Quantity","description":"WUXXXXXX","units":{},"default":""}],"example":"The first example uses the ACTIONW keyword to re-complete a gas injection well, GI01, when the well’s bottom-hole pressure exceeds the fracture pressure of the formation, and to open up a structurally higher zone in the well. The keyword NEXTSTEP is used to set the next step to 0.1 days to avoid convergence issues due to a well event.\n--\n-- ACTIONW WELL COMMANDS\n--\nACTIONW\n-- ACTION WELL ACTION ACTION ACTION MAX INCREMENT\n-- NAME NAME LHS TEST RHS ACTIONS RHS\nACTW-1 GI01 WBHP > 6800.0 /\n--\n-- ACTION COMMANDS TO BE EXECUTED\n--\n-- NEXT ALL\n-- STEP TIME\nNEXTSTEP\n0.1 'NO' /\n--\n-- WELL PRODUCTION STATUS\n--\n-- WELL WELL --LOCATION-- COMPLETION\n-- NAME STAT I J K FIRST LAST\nWELOPEN\nGI01 SHUT /\nGI01 SHUT 0 0 0 2 2 /\nGI01 OPEN /\nGI01 OPEN 0 0 0 1 1 /\n/\nENDACTIO\nThe second example shows how to reduce a producing well's deliverability due to water production. Here, well OP01’s productivity index is reduced by 2% when the well’s liquid production total is greater than 100,000 stb. The reduction is repeated 300 times and each time the action is executed the ACTRHS constant is increased by 10,000 stb.\n--\n-- ACTIONW WELL COMMANDS\n--\nACTIONW\n-- ACTION WELL ACTION ACTION ACTION MAX ICREMENT\n-- NAME NAME LHS TEST RHS ACTIONS RHS\nACTW-01 OP01 WLPT > 100E3 300 10E3 /\n--\n-- DEFINE WELL CONNECTION MULTIPLIERS\n--\n-- WELL PI --LOCATION-- COMPLETION\n-- NAME MULT I J K FIRST LAST\nWPIMULT\nOP01 0.980 1* 1* 1* 1* 1* /\n/\nENDACTIO\nThe final example is similar to the previous example, and shows how to nest ACTIONW blocks and how to apply ACTIONW to all the oil producers when the Boolean condition are satisfied.\n--\n-- ACTIONW WELL COMMANDS\n--\nACTIONW\n-- ACTION WELL ACTION ACTION ACTION MAX ICREMENT\n-- NAME NAME LHS TEST RHS ACTIONS RHS\nACTW-01A 'OP*' WLPT > 100E3 300 10E3 /\n--\n-- ACTIONW WELL COMMANDS\n--\nACTIONW\n-- ACTION WELL ACTION ACTION ACTION MAX ICREMENT\n-- NAME NAME LHS TEST RHS ACTIONS RHS\nACTW-01B 'OP*' WPI > 5.0 1 0.0 /\n--\n-- DEFINE WELL CONNECTION MULTIPLIERS\n--\n-- WELL PI --LOCATION-- COMPLETION\n-- NAME MULT I J K FIRST LAST\nWPIMULT\n'?' 0.980 1* 1* 1* 1* 1* /\n/\nENDACTIO\nENDACTIO\nIn this case the outer ACTIONW checks if the liquid production for each OP* well is great than the calculated ACTRHS constant, if it is, then inner ACTIONW reduces all the selected wells’ productivity indices by 2%, provided the well’s productivity index is greater than five.\n| Note Within an ACTIONW Definition Section any UDQ variables utilizing well variables, must have their associated wells previously fully defined in the commercial simulator, otherwise an error will occur. For example, if a well’s GOR is being used as part of a UDQ definition, then the well must be fully characterized prior to declaring the UDQ definition. This restriction does not apply to OPM Flow; however, it should be considered if the same deck is to be run with both simulators. |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":7,"size_kind":"fixed","size_count":1},"ACTIONX":{"name":"ACTIONX","sections":["SCHEDULE"],"supported":true,"summary":"The ACTIONX keyword defines a series of conditions that invoke run time processing of ACTION functions and is similar to executing a run time script. This is the general purpose version of the ACTION series of keywords that can apply Boolean conditional tests to variables at the field, group, region, well segment and well levels. The ACTION, ACTIONG, ACTIONR, ACTIONS and ACTIONW keywords are not implemented in OPM Flow and are unlikely to be so, as the ACTIONX keyword implements their functionality with greater flexibility.","parameters":[{"index":1,"name":"ACTNAME","description":"ACTNAME is a character sting of up to eight characters in length, that defines the name of this action definition. If ACTNAME has previously been used by any ACTION series keyword, then the previous ACTION series definition will be replaced by the definition declared by this ACTIONX Definition Section.","units":{},"default":"","record":1,"value_type":"STRING"},{"index":2,"name":"ACTNSTEP","description":"ACTNSTEP is a positive integer that defines the number times that the ACTNAME definition is executed. ACTIONX definitions are activated at the end of a time step and this parameter is used to set how many time steps the ACTNAME definition will be invoked. The default value of one means that the definition will be executed only once. Use a large value, for example 10,000 for the definition to be executed at every time step. Note that the counter only affects successful evaluations; i.e. if ACTNSTEP is set equal to one (the default), then the simulator will test the action at the end of every time step until it evaluates to true.","units":{},"default":"1","record":1,"value_type":"INT"},{"index":3,"name":"ACTDELTA","description":"ACTDELTA is a real positive value that defines the minimum duration of time after the conditions defined on the second record have been satisfied before the ACTIONX actions are executed. For example, if ACTDELTA is defaulted the actions will be executed at the end of the time step for which the conditions are met. If set to say 30, then a minimum of 30 days will pass before the actions are executed (assuming field or metric units).","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"0.0","record":1,"value_type":"DOUBLE","dimension":"Time"},{"index":1,"name":"ACTLHS","description":"ACTLHS is a series of character strings, each up to eight characters in length, that defines a constant, UDQ defined value, or a SUMMARY variable on the left hand side of a Boolean conditional test. The format for ACTLHS is dependent on the SUMMARY variable type: Aquifer, Block, Field, Group, Region, Time, Well, Well Connection, Well Local Grid Refinement Connection, or a Well Segment. In addition to SUMMARY variables, an UDQ defined value or a Constant variable can be used. The format for the various data types is given in Table 12.7.","units":{},"default":"Not Applicable","record":2,"value_type":"RAW_STRING"},{"index":2,"name":"ACTTEST","description":"ACTTEST is a defined character string that states the Boolean operator and must be set to one of the following Boolean conditionals: >: Greater than. <: Less than. >=: Greater than or equal to. <=: Less than or equal to. =: Equal to. !=: Not equal to. For example to test if the field’s gas production rate is less than 600 MMscf/d then one would use: ACTIONX PHASE2 1 / GGPR 'FIELD' < 600E3 / / ... ENDACTIO","units":{},"default":"Not Applicable","record":2},{"index":3,"name":"ACTRHS","description":"ACTRHS is a numeric value or a series of character strings, each up to eight characters in length, that defines a constant, an UDQ defined value, or a SUMMARY variable on the right hand side of a Boolean conditional test, as outlined in Table 12.7(see also ACTLHS). In the case of well quantities the set of matching wells is captured and can be used as a general \"well list\" with the symbol '?' in subsequent well keywords. For example, to shut-in all oil producing wells (‘OP*’) with a water cut greater than 90% for every time the field water production rate exceeds 60,000 stb/d one would use: ACTIONX MXWATER 10000 / GWPR 'FIELD' > 60E3 AND / WWCT 'OP*' > 0.90 / / -- WELL PRODUCTION STATUS -- -- WELL WELL --LOCATION-- COMPLETION -- NAME STAT I J K FIRST LAST WELOPEN '?' SHUT / / ENDACTIO","units":{},"default":"Not Applicable","record":2},{"index":4,"name":"ANDOR","description":"An optional defined character string that specifies a Boolean operator that must be set to either AND or OR if included on this record, that links this record with additional records of this type. For example, to test if the field’s gas production rate is less than 600 MMscf/d after 2020 then one would use: ACTIONX PHASE2 1 / GGPR 'FIELD' < 600E3 AND / YEAR > 2020 / / ... ENDACTIO This item should be left blank if not required.","units":{},"default":"Not Applicable","record":2}],"example":"The first example uses the UDQ keyword to sort the oil wells from high water cut to low, via the WU_WLIST variable, and then use the ACTIONX keyword to shut-in the worst offending well when the field’s water production is greater than 30,000 stb/d.\n--\n-- DEFINE START OF USER DEFINED QUANTITY SECTION\n--\nUDQ\n--\n-- OPERATOR VARIABLE EXPRESSION\n--\nDEFINE WU_WCUT WWCT 'OP*' / WELL WWCT LIST\nDEFINE WU_LIST SORTD(WU_WCUT) / WELL WWCT LIST SORTED\n/ END OF UDQ SECTION\n--\n-- DEFINE START OF ACTIONX SECTION\n--\nACTIONX\nWSHUTIN 10 /\nGWPR 'FIELD' > 30E3 AND /\nWU_LIST 'OP*' = 1 /\n/\n--\n-- DEFINE WELL AND WELL CONNECTIONS FLOWING STATUS\n--\n-- WELL WELL --LOCATION-- COMPLETION\n-- NAME STAT I J K FIRST LAST\nWELOPEN\n'?' SHUT /\n'?' SHUT 0 0 0 0 0 /\n/\nENDACTIO\nApart from checking that the field’s water production rate is greater than 30,000 stb/d the Boolean conditional also checks that there is at least one well in the sorted well list. Notice also the use of ‘?’ symbol as a substitution of the well name and that the ACTIONX WSHUTIN series of commands will be executed a total of ten times.\nThe second example checks to see if the field’s gas rate is below 600 MMscf/d and if the simulation time is greater that July 1, 2030. If it is, then compression is installed by re-setting all the gas producing well’s THP and BHP pressures to 450 psia and 300 psia respectively. In addition all gas wells currently shut-in are tested to see if they can be opened up under the new THP and BHP constraints.\n--\n-- START ACTIONX FIELD PHASE-3 AUTOMATIC COMPRESSION\n--\nACTIONX\nPHASE-3 1 /\nGGPR 'FIELD' < 600E3 AND /\nDAY >= 1 AND /\nMNTH >= JUL AND /\nYEAR >= 2030 /\n/\n--\n-- INSTALL COMPRESSION AND RESET WELL THP AND BHPS\n--\n-- WELL WELL TARGET\n-- NAME TARG VALUE\nWELTARG\n'GP*' THP 450 /\n'GP*' BHP 300 /\n/\n--\n-- TEST AND OPEN ALL WELLS UNDER COMPRESSION CONSTRAINTS\n--\n-- WELL TEST CLOSE NO. START\n-- NAME INTV CHECK CHECK TIME\nWTEST\n'GP*' 1.0 PE 1 3 /\n/\n--\n-- END OF ACTIONX FIELD PHASE-3 AUTOMATIC COMPRESSION DEFINITION\n--\nENDACTIO\n| Variable Type | Description |\n|---------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------","records_meta":[{"expected_columns":3},{}],"size_kind":"list"},"APILIM":{"name":"APILIM","sections":["SCHEDULE"],"supported":false,"summary":"The APILIM keyword defines API Tracking grid block limits for when API Tracking has been activated via the API keyword in the RUNSPEC section. The keyword enables the simulator to monitor the grid blocks outside the limits defined on the keyword, as well as to optionally contrain the values within a given range.","parameters":[{"index":1,"name":"LIMITER","description":"","units":{},"default":"NONE","value_type":"STRING"},{"index":2,"name":"SCOPE","description":"","units":{},"default":"BOTH","value_type":"STRING"},{"index":3,"name":"LOWER_API_LIMIT","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":4,"name":"UPPER_API_LIMIT","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":5,"name":"NUM_ROWS","description":"","units":{},"default":"10","value_type":"INT"}],"example":"","expected_columns":5,"size_kind":"fixed","size_count":1},"AQUCWFAC":{"name":"AQUCWFAC","sections":["SCHEDULE"],"supported":false,"summary":"The AQUCWFAC keyword modifies the datum depth and pressure for all aquifers specified by the AQUCHWAT keyword in the SOLUTION or SCHEDULE sections.","parameters":[{"index":1,"name":"ADD_TO_DEPTH","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Length"},{"index":2,"name":"MULTIPLY","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"}],"example":"","expected_columns":2,"size_kind":"list"},"BCPROP":{"name":"BCPROP","sections":["SCHEDULE"],"supported":true,"summary":"The BCPROP keyword defines the type and properties of the boundary conditions.","parameters":[{"index":1,"name":"INDEX","description":"A positive integer that identifies the boundary condition.","units":{},"default":"None","value_type":"INT"},{"index":2,"name":"TYPE","description":"A defined character string that defines the type of boundary condition to be applied, and should be set to one of the following character strings: DIRICHLET: for user defined boundary conditions. In this case, COMPONENT for the fluid type, and PRESS and TEMP for the constant pressure and temperature boundary conditions must be specified. FREE: for the initial state of the boundary to be kept throughout the simulation, that is a constant boundary condition. The remaining items should be defaulted. RATE: for the boundary to have a constant influx or efflux rate. In this case, COMPONENT for the fluid type, and RATE to set the mass rate per unit area must be specified. THERMAL: Constant temperature boundary condition (no-flow of mass). NONE: No flow boundary condition.","units":{},"default":"None","value_type":"STRING","options":["DIRICHLET","FREE","RATE"]},{"index":3,"name":"COMPONENT","description":"A defined character string that sets fluid type used in the boundary calculations, and should be set to one of the following character strings: GAS: the gas phase will be used to control the boundary conditions for when the TYPE has been set to DIRICHLET or RATE. OIL: the oil phase will be used to control the boundary conditions for when the TYPE has been set to DIRICHLET or RATE . WATER or WAT: the water phase will be used to control the boundary conditions for when the TYPE has been set to DIRICHLET or RATE. SOLVENT: the solvent component will be used to control the boundary conditions for when the TYPE has been set to RATE. POLYMER: the polymer component will be used to control the boundary conditions for when the TYPE has been set to RATE. MICR: the microbial component will be used to control the boundary conditions for when the TYPE has been set to RATE. OXYG: the oxygen component will be used to control the boundary conditions for when the TYPE has been set to RATE. UREA: the urea component will be used to control the boundary conditions for when the TYPE has been set to RATE. NONE: the fluid type is undefined. COMPONENT must be declared and not equal to NONE if TYPE has been set to either DIRICHLET or RATE. MICR requires the BIOFILM or MICP keyword, and OXYG or UREA requires the MICP keyword.","units":{},"default":"NONE","value_type":"STRING","options":["GAS","OIL","WAT","SOLVENT","POLYMER","MICR","OXYG","UREA","NONE"]},{"index":4,"name":"RATE","description":"A real value that defines the constant mass rate per unit area of the specified COMPONENT to be injected or withdrawn at the boundary, when TYPE has been set to RATE. Note a negative value implies an influx rate, whereas, a positive value indicates an efflux.","units":{"field":"lb/day/ft2","metric":"kg/day/m2","laboratory":"gm/hour/cm2"},"default":"0.0","value_type":"DOUBLE","dimension":"Mass/Time*Length*Length"},{"index":5,"name":"PRESS","description":"PRESS is a real positive value that defines the constant pressure boundary condition. PRESS should only be entered if TYPE has been set to DIRICHLET. If the pressure at the boundary is less than PRESS, then the fluid type declared via COMPONENT will flow across the boundary. The default value of 1* will use the simulator's calculated value based on data entered via the EQUIL keyword in the SOLUTION section.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1*","value_type":"DOUBLE","dimension":"Pressure"},{"index":6,"name":"TEMP","description":"TEMP is a real positive number that defines the constant temperature boundary condition. TEMP should only be entered if TYPE has been set to DIRICHLET or THERMAL. The default value of 1* will use the simulator's calculated value based on data entered via one of the following reservoir temperature keywords: RTEMP, RTEMPA, RTEMPVD, TEMPI, or TEMPVD, in the SOLUTION section. Note that all of the aforementioned reservoir temperature keywords, except for TEMPI, may also be used in the PROPS section as well.","units":{"field":"oF","metric":"oC","laboratory":"oC"},"default":"1*","value_type":"DOUBLE","dimension":"Temperature"},{"index":7,"name":"MECHTYPE","description":"A defined character string that defines the type of geo-mechanical boundary condition to be applied, and should be set to one of the following character strings: FREE: Surface is free to move with no external stress. FIXED: Surface is fixed in the x/y/z-directions if FIXEDX / FIXEDY / FIXEDZ > 0. The displacement in each direction defined by DISPX / DISPY / DISPZ. The external stess is defined by STRESSXX / STRESSYY / STRESSZZ. NONE: No geo-mechanical boundary condition.","units":{},"default":"NONE","value_type":"STRING"},{"index":8,"name":"FIXEDX","description":"A positive integer that identifies the whether the boundary is free or fixed in the x-direction. A value of 0 implies the boundary is free to move in the x-direction. A value > 0 implies the boundary is fixed in the x-direction with displacement defined by DISPX,","units":{},"default":"1","value_type":"INT"},{"index":9,"name":"FIXEDY","description":"A positive integer that identifies the whether the boundary is free or fixed in the y-direction. A value of 0 implies the boundary is free to move in the y-direction. A value > 0 implies the boundary is fixed in the y-direction with displacement defined by DISPY,","units":{},"default":"1","value_type":"INT"},{"index":10,"name":"FIXEDZ","description":"A positive integer that identifies the whether the boundary is free or fixed in the z-direction. A value of 0 implies the boundary is free to move in the z-direction. A value > 0 implies the boundary is fixed in the z-direction with displacement defined by DISPZ,","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1","value_type":"INT"},{"index":11,"name":"STRESSXX","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Pressure"},{"index":12,"name":"STRESSYY","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Pressure"},{"index":13,"name":"STRESSZZ","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Pressure"},{"index":14,"name":"DISPX","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Length"},{"index":15,"name":"DISPY","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Length"},{"index":16,"name":"DISPZ","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Length"}],"example":"The first example shows how to set a constant pressure boundary using TYPE equal to FREE:\n--\n-- DEFINE BOUNDARY CONDITIONS CONNECTION (OPM FLOW GRID KEYWORD)\n--\n--INDEX ---------- BOX --------- BC\n-- I1 I2 J1 J2 K1 K2 DIRC\nBCCON\n1 1 1 1 1* 1 1* X- /\n2 1 1* 1 1 1 1* Y /\n/\n--\n-- DEFINE BOUNDARY CONDITIONS PROPERTIES (OPM FLOW SCHEDULE KEYWORD)\n--\n--INDEX BC BC BC BC BC\n-- TYPE COMPT RATE PRESS TEMP\nBCPROP\n1 FREE 1* 1* 1* 1* /\n2 FREE /\n/\nWith this option it is only necessary to define the boundary cells and all the other parameters (COMPONENT, RATE, PRESS, and TEMP) can be defaulted, as they are ignored when TYPE equals FREE.\nThe next example is based on NX, NY and NZ equal to 20, 1, 10 respectively, on the DIMENS keyword in the RUNSPEC section, and shows how different boundary types can be assigned to different parts of the model.\n--\n-- DEFINE BOUNDARY CONDITIONS CONNECTION (OPM FLOW GRID KEYWORD)\n--\n--INDEX ---------- BOX --------- BC\n-- I1 I2 J1 J2 K1 K2 DIRC\nBCCON\n1 1 1 1 1 1 10 X- /\n2 20 20 1 1 1 10 X /\n/\n--\n-- DEFINE BOUNDARY CONDITIONS PROPERTIES (OPM FLOW SCHEDULE KEYWORD)\n--\n--INDEX BC BC BC BC BC\n-- TYPE COMPT RATE PRESS TEMP\nBCPROP\n1 DIRICHLET GAS 1* 256.0 100.0 /\n2 FREE 4* /\n/\nThe last example shows how the DIRICHLET boundary condition option may be used:\n--\n-- DEFINE BOUNDARY CONDITIONS CONNECTION (OPM FLOW GRID KEYWORD)\n--\n--INDEX ---------- BOX --------- BC\n-- I1 I2 J1 J2 K1 K2 DIRC\nBCCON\n1 1 1 1 1* 1 1* X- /\n2 1 1* 1 1 1 1* Y /\n/\n--\n-- DEFINE BOUNDARY CONDITIONS PROPERTIES (OPM FLOW SCHEDULE KEYWORD)\n--\n--INDEX BC BC BC BC BC\n-- TYPE COMPT RATE PRESS TEMP\nBCPROP\n1 DIRICHLET WAT 1* 256.0 100.0 /\n2 DIRICHLET WAT 1* 1* 100.0 /\n/\nHere, the first line sets both the pressure and temperature at the boundary, and the second line defaults the pressure entry, so that the simulator calculated initial boundary pressure will be used.\n| Note This is an OPM Flow specific keyword and will therefore cause an error in the commercial simulator. |\n|----------------------------------------------------------------------------------------------------------|","expected_columns":16,"size_kind":"list"},"BRANPROP":{"name":"BRANPROP","sections":["SCHEDULE"],"supported":null,"summary":"BRANPROP defines network branch properties for the extended network option for when the Extended Network Model has been activated by the NETWORK keyword in the RUNSPEC section. There are two types of network facilities in the simulator, the Standard Network model, which is defined with the GRUPNET keyword in the SCHEDULE section and the Extended Network Model defined by the BRANPROP and NODEPROP keywords, again in the SCHEDULE section.","parameters":[{"index":1,"name":"DOWNNODE","description":"A character string of up to eight characters in length that defines the down stream node name for this branch, that is the node closest to the wells. Thus for a production network, this will be an inlet node as the wells are importing fluid into the branch node. Whereas for an injection node, this is an outlet node as injection fluid is being exported to the wells.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"UPNODE","description":"A character string of up to eight characters in length that defines the up stream node name for this branch, that is the node furthermost from the wells. Thus for a production network, this will be an outlet node as the wells are exporting fluid from the branch node. Whereas for an injection node, this is an inlet node as the wells are importing the injection fluid.","units":{},"default":"None","value_type":"STRING"},{"index":3,"name":"VFPTAB","description":"A positive integer greater than or equal to zero that defines the vertical lift performance table to be used for calculating the pressure behavior between the inlet (for production) or outlet (for injection) node (DOWNNODE) and the outlet (for production) or inlet (for injection) node (UPNODE). For a production network this must reference a table associated with the VFPPROD keyword, and for an injection network a table declared via the VFPINJ keyword. Both keywords are in the SCHEDULE section. If the pressure behavior between the two nodes is zero (no pressure loss in the network branch), then a value of 9999 should be entered for this variable. A value of zero for VFPTAB removes the branch from the extended network and the resulting flows are ignored in the network flow stream.","units":{},"default":"None","value_type":"INT"},{"index":4,"name":"ALQ-NODE","description":"A real positive value that defines the artificial lift quantity to be used in conjunction with the VFPPROD assigned to the branch via the VPFTAB variable. VFPTAB vertical lift performance table and the artificial lift quantity ALQ-NODE are used with the branch fluid rates to calculate the pressure behavior through the branch. For a network this can be considered to be either a pump to pump fluid through the network or a compressor to compress gas to a higher export pressure. Basically, ALQ-NODE is used to reduce the pressure loss through the branch. Note that the units for ALQ-NODE are dependent on the associated variable on the VFPPROD keyword. Should be set to zero if ALQ-DEN is set to either DENO or DENG, or if the branch is associated with an automatic compressor.","units":{},"default":"0.0","value_type":"DOUBLE"},{"index":5,"name":"ALQ-DEN","description":"A defined character string that defines that ALQ-NODE variable represents either as a surface density or as an artificial lift quantity for a pump or a compressor, and should be set to one of the following: DENO: ALQ-NODE represents the average surface oil density flowing through the branch. DENG: ALQ-NODE represents the average surface gas density flowing through the branch. NONE: ALQ-NODE is the artificial lift quantity as defined on the VFPPROD keyword to model a pump or a compressor. The VFPPROD keyword should be consistent with this variable, that is, if ALQ-DEN is set to to DENO then the surface oil should be used as the ALQ variable on the VFPPROD keyword.","units":{},"default":"NONE","value_type":"STRING"}],"example":"Given the following Extended Network model in Figure 12.3.\n[formula]\n[formula]\nFigure 12.3: Extend Network Example\nFirst the Extended Network model should be used invoked in the RUNSPEC section, and then the BRANPROP keyword should be used to define the branch network, and finally the NODEPROP keyword is used to describe the node properties.\n-- ==============================================================================\n--\n-- RUNSPEC SECTION\n--\n-- ==============================================================================\nRUNSPEC\n--\n-- ACTIVATE THE EXTENDED NETWORK OPTION AND DEFINE PARAMETERS\n--\n-- MAX. MAX NOT\n-- NODE LINK USED\nNETWORK\n3 2 1* /\n…..…………..\n..……..…..\n-- ==============================================================================\n--\n-- SCHEDULE SECTION\n--\n-- ==============================================================================\nSCHEDULE\n--\n-- EXTENDED NETWORK BRANCH PROPERTIES\n--\n-- DOWN UP VFP VFP\n-- NODE NODE TABLE ALFQ\nBRANPROP\nB1 PLAT-A 5 1* /\nC1 PLAT-A 4 1* /\n/\n--\n-- EXTENDED NETWORK NODE PROPERTIES\n--\n-- NODE NODE CHOKE GAS CHOKE SOURCE NETWORK\n-- NAME PRESS OPTN LIFT GROUP SINK TYPE\nNODEPROP\nPLAT-A 21.0 NO NO /\nB1 1* NO NO /\nC1 1* NO NO /\n/\nHere the main platform for the field, PLAT-A, has a fixed 21 barsa pressure applied as an operating constraint.","expected_columns":5,"size_kind":"list"},"CALTRAC":{"name":"CALTRAC","sections":["SCHEDULE"],"supported":false,"summary":"The CALTRAC keyword is used to assign a gas calorfic value to a tracer, for when the Tracer option has been invoked by the TRACER keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"IX1","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"CECON":{"name":"CECON","sections":["SCHEDULE"],"supported":false,"summary":"CECON sets the economic cut-off criteria for a well’s connection to the simulation grid.","parameters":[{"index":1,"name":"WELLNAME","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"I","description":"","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"J","description":"","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"K1","description":"","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"K2","description":"","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"MAX_WCUT","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":7,"name":"MAX_GOR","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":8,"name":"MAX_WGR","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":9,"name":"WORKOVER_PROCEDURE","description":"","units":{},"default":"CON","value_type":"STRING"},{"index":10,"name":"CHECK_STOPPED","description":"","units":{},"default":"NO","value_type":"STRING"},{"index":11,"name":"MIN_OIL","description":"","units":{},"default":"-1e+20","value_type":"DOUBLE"},{"index":12,"name":"MIN_GAS","description":"","units":{},"default":"-1e+20","value_type":"DOUBLE"},{"index":13,"name":"FOLLOW_ON_WELL","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":13,"size_kind":"list"},"CECONT":{"name":"CECONT","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, CECONT, sets the tracer economic cut-off criteria for a well’s connection to the simulation grid.","parameters":[],"example":"","size_kind":"none","size_count":0},"COMPDAT":{"name":"COMPDAT","sections":["SCHEDULE"],"supported":false,"summary":"The COMPDAT keyword defines how a well is connected to the reservoir by defining or modifying existing well connections. Ideally the connections should be declared in the correct sequence, starting with the connection nearest the well head and then working along the wellbore towards the bottom or toe of the well, however this may not be possible or convenient, for example when connections are added or removed from a well during the simulation (see COMPORD in the SCHEDULE section for options regarding connection ordering).","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well connection data are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"I","description":"A positive integer greater than or equal to zero and less than or equal to NX that defines the connection location in the I-direction. If set to zero or defaulted with 1* the location is taken from the wellhead location I-direction value on the WELSPECS keyword in the SCHEDULE section.","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"J","description":"A positive integer greater than or equal to zero and less than or equal to NY that defines the connection location in the J-direction. If set to zero or defaulted with 1* the location is taken from the wellhead location J-direction value on the WELSPECS keyword in the SCHEDULE section.","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"K1","description":"A positive integer greater than or equal to one and less than or equal to NZ that defines the UPPER connection location in the K-direction.","units":{},"default":"None","value_type":"INT"},{"index":5,"name":"K2","description":"A positive integer greater than or equal to K1 and less than or equal to NZ that defines the LOWER connection location in the K-direction.","units":{},"default":"None","value_type":"INT"},{"index":6,"name":"STATUS","description":"A defined character string of length four that defines the connections’ operational status, STATUS should be set to one of the following character strings: OPEN: the connections are open to flow. SHUT: the connections are closed to flow (shut-in). AUTO: the connection are initially closed, but may be opened automatically if an economic limit is violated. Currently this option is not supported by OPM Flow.","units":{},"default":"OPEN","value_type":"STRING","options":["OPEN","SHUT","AUTO"]},{"index":7,"name":"SATNUM","description":"An integer greater than or equal to zero and less than NTSFUN as declared on the TABDIMS keyword in the RUNSPEC section, that defines the saturation table number to be used for flow between the reservoir grid block and the well connections. If SATNUM is set to zero or defaulted with 1* then: The saturation table allocated to the grid block that the connections are located within are used. If the hysteresis option has been activated via the HYSTER variable on the SATOPTS keyword in the RUNSPEC section, then both the imbibition and drainage saturation tables allocated to the grid block that the connections are located within are used. The imbibition table allocation can be changed by the COMPIMB keyword in the RUNSPEC section, provided it is entered after the COMPDAT keyword.","units":{},"default":"0","value_type":"INT"},{"index":8,"name":"CONFACT","description":"A real value greater than or equal to zero that defines the transmissibility connection factor between the well bore and the reservoir grid block. If set to zero or defaulted with 1* then items (9) through (13) are used to calculate CONFACT.","units":{"field":"cP.rb/day/psia 0","metric":"cP.rm3/day/bars 0","laboratory":"cP.rcc/hr/atm 0"},"default":"Defined","value_type":"DOUBLE","dimension":"Viscosity*ReservoirVolume/Time*Pressure"},{"index":9,"name":"DW","description":"A real positive value that defines the well bore diameter of the connections for the well. DW is used in calculating a well’s productivity or injectivity index; however the value will be ignored in calculating the connections CONFACT value if CONFACT has been directly entered.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":"Length"},{"index":10,"name":"KH","description":"A real value that defines the effective KH (permeability x length) for the connections. If less than or equal to zero, or defaulted by 1*, then KH is calculated from the connected grid blocks. KH is ignored if CONFAC has been directly entered.","units":{"field":"mD.ft","metric":"mD.m","laboratory":"mD.cm"},"default":"Calculated from connected grid blocks","value_type":"DOUBLE","dimension":"Permeability*Length"},{"index":11,"name":"SKIN","description":"A real value that defines the connections dimensionless skin factor. SKIN is used in calculating a well’s productivity or injectivity index; however, the value will be ignored in calculating the connections CONFACT value if CONFAC has been directly entered.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.0","value_type":"DOUBLE","dimension":"1"},{"index":12,"name":"DFACT","description":"A real value that defines the non-Darcy D factor coefficient for gas wells. It is recommended that the value should be defaulted with 1* and the non-Darcy D factor coefficient for gas wells defined via the WDFAC keyword in the SCHEDULE section. If the value is greater than or equal to zero then the value is used to define the well D factor and the simulator evaluates the connection D factors internally. If the value is less than zero then its sign is reversed and then used directly to define the connection D factors. In this case any D factor values previously defined using the WDFAC keyword for other connections will retained, whereas, any connection D factors previously defined for the entire well using the WDFACCOR keyword will be discarded.","units":{"field":"day/Mscf","metric":"day/m3","laboratory":"hour/sc"},"default":"0.0","value_type":"DOUBLE","dimension":"Time/GasSurfaceVolume"},{"index":13,"name":"DIRECT","description":"A defined character string of length one that defines the orientation of the connections and should be set to either X, Y, or Z. The direction of connections also determines the length of the connection used to calculate the connection factor if CONFACT has not been entered directly. The default value is for a vertical connection, that is DIRECT is defaulted to Z.","units":{},"default":"Z","value_type":"STRING"},{"index":14,"name":"PR","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"}],"example":"The following example defines two vertical oil wells using the WELSPECS keyword and their associated connection data.\n--\n-- WELL SPECIFICATION DATA\n--\n-- WELL GROUP LOCATION BHP PHASE DRAIN INFLOW OPEN CROSS PRESS\n-- NAME NAME I J DEPTH FLUID AREA EQUANS SHUT FLOW TABLE WELSPECS\nOP01 PLATFORM 14 13 1* OIL 1* STD SHUT NO 1* /\nOP02 PLATFORM 35 96 1* OIL 1* STD SHUT NO 1* /\n/\n--\n-- WELL CONNECTION DATA\n--\n-- WELL --- LOCATION --- OPEN SAT CONN WELL KH SKIN D DIR\n-- NAME II JJ K1 K2 SHUT TAB FACT DIA FACT FACT FACT PEN\nCOMPDAT\nOP01 1* 1* 20 56 OPEN 1* 1* 0.708 1* 0.0 1* 'Z' /\nOP01 1* 1* 75 100 SHUT 1* 1* 0.708 1* 0.0 1* 'Z' /\nOP02 35 96 75 100 OPEN 1* 1* 0.708 1* 0.0 1* 'Z' /\nWell OP01 has two sets of connections; the first one connects grid cells (14, 13, 20) to (14, 13, 56) to the well and is open to flow and the second connecting grid cells (14, 13, 75) to (14, 13, 100) is shut. Well OP02 has only one open set of connections from cells (35, 96, 75) to cells (35, 96, 100).\n| Note The term well connection is used to describe individual connections from the wellbore to the reservoir grid, as opposed to well completions. A well completion is used to describe a set of connections, for example, a well may consist of several completions with each completion consisting of multiple connections. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":14,"size_kind":"list"},"COMPDATL":{"name":"COMPDATL","sections":["SCHEDULE"],"supported":false,"summary":"The COMPDATL keyword defines how a well in a Local Grid Refinement (“LGR”) is connected to the reservoir by declaring the LGR and defining or modifying existing well connections. Ideally the connections should be declared in the correct sequence, starting with the connection nearest the well head and then working along the wellbore towards the bottom or toe of the well, however this may not be possible or convenient, for example when connections are added or removed from a well during the simulation (see the COMPORD keyword in the SCHEDULE section for options regarding connection ordering).","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well connection data are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None"},{"index":2,"name":"LGRNAME","description":"A character string of up to eight characters in length that defines the LGR name for which the well LGR connection data are being defined. Note that the well name (LGRNAME) must have been declared previously using the WELSPECL keyword in the SCHEDULE section, otherwise an error may occur. If defaulted with 1* the LGR on the WELSPECL keyword will be utilized.","units":{},"default":"Defined"},{"index":3,"name":"I","description":"A positive integer greater than or equal to zero and less than or equal to NX that defines the connection location in the I-direction. If set to zero or defaulted with 1* the location is taken from the wellhead location I-direction value on the WELSPECS keyword in the SCHEDULE section.","units":{},"default":"0"},{"index":4,"name":"J","description":"A positive integer greater than or equal to zero and less than or equal to NY that defines the connection location in the J-direction. If set to zero or defaulted with 1* the location is taken from the wellhead location J-direction value on the WELSPECS keyword in the SCHEDULE section.","units":{},"default":"0"},{"index":5,"name":"K1","description":"A positive integer greater than or equal to one and less than or equal to NZ that defines the UPPER connection location in the K-direction.","units":{},"default":"None"},{"index":6,"name":"K2","description":"A positive integer greater than or equal to K1 and less than or equal to NZ that defines the LOWER connection location in the K-direction.","units":{},"default":"None"},{"index":7,"name":"STATUS","description":"A character string of length four that defines the connections’ operational status, STATUS should be set to one of the following character strings: OPEN: the connections are open to flow. SHUT: the connections are closed to flow (shut-in). AUTO: the connection are initially closed, but may be opened automatically if an economic limit is violated. Currently this option is not supported by OPM Flow","units":{},"default":"OPEN"},{"index":8,"name":"SATNUM","description":"An integer greater than or equal to zero and less than NTSFUN as declared on the TABDIMS keyword in the RUNSPEC, that defines the saturation table number to be used for flow between the reservoir grid block and the well connections. If SATNUM is set to zero or defaulted with 1* then: The saturation table allocated to the grid block that the connections are located within are used. If the hysteresis option has been activated via the HYSTER variable on the SATOPTS keyword in the RUNSPEC section, then both the imbibition and drainage saturation tables allocated to the grid block that the connections are located within are used. The imbibition table allocation can be changed by the COMPIMB keyword in the RUNSPEC section, provided it is entered after the COMPDAT keyword.","units":{},"default":"0"},{"index":9,"name":"CONFACT","description":"A real value greater than or equal to zero that defines the transmissibility connection factor between the well bore and the reservoir grid block. If set to zero or defaulted with 1* then items (9) through (13) are used to calculate CONFACT.","units":{"field":"cP.rb/day/psia 0","metric":"cP.rm3/day/bars 0","laboratory":"cP.rcc/hr/atm 0"},"default":"Defined"},{"index":10,"name":"DW","description":"A real positive value that defines the well bore diameter of the connections for the well. DW is used in calculating a well’s productivity or injectivity index; however the value will be ignored in calculating the connections CONFACT value if CONFAC has been directly entered.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None"},{"index":11,"name":"KH","description":"A real value that defines the effective KH (permeability x length) for the connections. If less than or equal to zero or defaulted by 1* then KH is calculated from the connected grid blocks. KH is ignored if CONFAC has been directly entered.","units":{"field":"mD.ft","metric":"mD.m","laboratory":"mD.cm"},"default":"Calculated from connected grid blocks"},{"index":12,"name":"SKIN","description":"A real value that defines the connections dimensionless skin factor. SKIN is used in calculating a well’s productivity or injectivity index; however, the value will be ignored in calculating the connections CONFACT value if CONFAC has been directly entered.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.0"},{"index":13,"name":"DFACT","description":"A real value that defines the non-Darcy D factor coefficient for gas wells. This value should be defaulted with 1* and the non-Darcy D factor coefficient for gas wells defined via the WDFAC keyword in the SCHEDULE section. Currently this option is not supported by OPM Flow.","units":{"field":"day/Mscf","metric":"day/m3","laboratory":"hour/sc"},"default":"1*"},{"index":14,"name":"DIRECT","description":"A one letter character string that defines the orientation of the connections and should be set to either X, Y, or Z. The direction of connections also determines the length of the connection used to calculate the connection factor if CONFAC has not been entered directly. The default value is for a vertical connection, that is DIRECT is defaulted to Z.","units":{},"default":"Z"}],"example":"The following example defines two vertical oil wells using the WELSPECS keyword and their associated connection data.\n--\n-- WELL LGR SPECIFICATION DATA\n--\n-- WELL GROUP LGR -LOCATION- BHP PHASE DRAIN INFLOW SHUT CROSS PVT\n-- NAME NAME NAME I J DEPTH FLUID AREA EQUA. IN FLOW TABLE\nWELSPECL\nOP01 PLAT OP01LGR 14 13 1* OIL 1* STD SHUT NO 1* /\nOP02 PLAT OP02LGR 28 96 1* OIL 1* STD SHUT NO 1* /\n/\n--\n-- WELL LGR CONNECTION DATA\n--\n-- WELL LGR ---LOCATION--- OPEN SAT CONN WELL KH SKIN D DIR\n-- NAME NAME II JJ K1 K2 SHUT TAB FACT DIA FACT FACT FACT PEN\nCOMPDATL\nOP01 OP01LGR 1* 1* 20 56 OPEN 1* 1* 0.708 1* 1* 1* Z /\nOP01 OP01LGR 1* 1* 75 100 SHUT 1* 1* 0.708 1* 1* 1* Z / OP02 OP02LGR 35 96 75 100 OPEN 1* 1* 0.708 1* 1* 1* Z /\n/\nWell OP01 has two sets of connections; the first one connects grid cells (14, 13, 20) to (14, 13, 56) to the well and is open to flow and the second connecting grid cells (14, 13, 75) to (14, 13, 100) is shut. Well OP02 has only one open connection from cells (35, 96, 75) to cells (35, 96, 100).\n| Note The term well connection is used to describe individual connections from the wellbore to the reservoir grid, as opposed to well completions. A well completion is used to describe a set of connections, for example, a well may consist of several completions with each completion consisting of multiple connections. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|"},"COMPDATM":{"name":"COMPDATM","sections":["SCHEDULE"],"supported":false,"summary":"The COMPDATM keyword is an alias for the COMPDATL keyword. COMPDATM defines how a well in an amalgamated Local Grid Refinement (“LGR”) is connected to the reservoir by declaring the LGR and defining or modifying existing well connections. Ideally the connections should be declared in the correct sequence, starting with the connection nearest the well head and then working along the wellbore towards the bottom or toe of the well, however this may not be possible or convenient, for example when connections are added or removed from a well during the simulation (see the COMPORD keyword in the SCHEDULE section for options regarding connection ordering).","parameters":[],"example":""},"COMPFLSH":{"name":"COMPFLSH","sections":["SCHEDULE"],"supported":false,"summary":"COMPFLSH is used to assign saturated PVT differential-flash liberation ratios to individual well completions for both the oil formation volume factor and the gas-oil ratio. Only the saturated oil properties are changed by this keyword, that is only data entered via the PVCO or PVTO keywords in the PROPS section will be used in the calculation. The other fluid PVT property keywords: PVTW, PVTG, DENSITY, etc., are not used.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"I","description":"","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"J","description":"","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"UPPER_K","description":"","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"LOWER_K","description":"","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"F1","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"},{"index":7,"name":"F2","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"},{"index":8,"name":"FLASH_PVTNUM","description":"","units":{},"default":"0","value_type":"INT"}],"example":"","expected_columns":8,"size_kind":"list"},"COMPIMB":{"name":"COMPIMB","sections":["SCHEDULE"],"supported":false,"summary":"The COMPIMB keyword assigns imbibition saturation tables to well connections. The COMPDAT keyword in the SCHEDULE section also assigns imbibition saturation tables to connections, but in this case the table number is the same as for the drainage curve. If this is not the required assignment then the COMPIMB keyword can be used to reset the imbibition saturation table number. For this to be effective the COMPIMB keyword must precede the COMPDAT keyword, otherwise it will have no effect.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well connection data is being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"I","description":"A positive integer greater than or equal to zero and less than or equal to NX that defines the connection location in the I-direction. If set to zero or defaulted with 1* then all connections in the I-direction that also satisfy J, K1 and K2 criteria are assigned the IMBNUM imbibition table number.","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"J","description":"A positive integer greater than or equal to zero and less than or equal to NY that defines the connection location in the J-direction. If set to zero or defaulted with 1* then all connections in the J-direction that also satisfy I, K1 and K2 criteria are assigned the IMBNUM imbibition table number.","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"K1","description":"A positive integer greater than or equal to one and less than or equal to NZ that defines the UPPER connection location in the K-direction. If set to zero or defaulted with 1* then the upper most connection in the well is used.","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"K2","description":"A positive integer greater than or equal to K1 and less than or equal to NZ that defines the LOWER connection location in the K-direction. If set to zero or defaulted with 1* then the lowest most connection in the well is used.","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"IMBNUM","description":"An integer greater than or equal to zero and less than NTSFUN as declared on the TABDIMS keyword in the RUNSPEC, that defines the imbibition saturation table number to be used for flow between the reservoir grid block and the well connections. If IMBNUM is set to zero or defaulted with 1* then the inhibition saturation table allocated to the grid block that the connections are located within is used. If I, J, K1, K2 are all set to zero or defaulted to 1*, then IMBNUM is allocated to all connections in the well.","units":{},"default":"0","value_type":"INT"}],"example":"The following example defines the connections for two vertical oil wells using the COMPDAT keyword and then re-sets the imbibition saturation functions using the COMPIMP keyword.\n--\n-- WELL CONNECTION DATA\n--\n-- WELL --- LOCATION --- OPEN SAT CONN WELL KH SKIN D DIR\n-- NAME II JJ K1 K2 SHUT TAB FACT DIA FACT FACT FACT PEN\nCOMPDAT\nOP01 1* 1* 20 56 OPEN 1 1* 0.708 1* 0.0 1* 'Z' /\nOP01 1* 1* 75 100 SHUT 2 1* 0.708 1* 0.0 1* 'Z' /\nOP02 35 96 75 100 OPEN 1 1* 0.708 1* 0.0 1* 'Z' /\n--\n-- ASSIGN IMBIBITION SATURATION TABLES TO CONNECTIONS\n--\n-- WELL ---LOCATION--- SAT\n-- NAME II JJ K1 K2 TAB\nCOMPIMB\nOP01 1* 1* 20 56 11 /\nOP01 1* 1* 75 100 12 /\nOP02 1* 1* 1* 1* 11 /\n/\nWell OP01 has two sets of COMPIMB records to overwrite the imbibition saturation tables, one for connections (14, 13, 20) to (14, 13, 56) resetting the imbibition saturation table number from one to 11 and one for connections (14, 13, 75) to (14, 13, 100) that resets the imbibition table number from 2 to 12. Well OP02 has only one connection from cells (35, 96, 75) to cells (35, 96, 100), so all the default values for I, J, K1, and K2 can be used to set the imbibition table numbers from 2 to 11. Note in all cases the drainage saturation table retains the value as specified by the COMPDAT keyword, that is one, two and one.","expected_columns":6,"size_kind":"list"},"COMPINJK":{"name":"COMPINJK","sections":["SCHEDULE"],"supported":false,"summary":"The COMPINJK keyword assigns injection well relative permeability values to well connections.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"I","description":"","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"J","description":"","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"K_UPPER","description":"","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"K_LOWER","description":"","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"REL_PERM","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"1"}],"example":"","expected_columns":6,"size_kind":"list"},"COMPLMPL":{"name":"COMPLMPL","sections":["SCHEDULE"],"supported":false,"summary":"The COMPLMPL keyword assigns well connections in a LGR, as defined by the COMPDATL keyword in the SCHEDULE section, to completion intervals. This “lumping” of the connections to various completion intervals allows automatic workovers and economic criteria to be applied to the completions (that is a set of connections) as opposed to the connections. This allows for a more realistic approach for workovers operations.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well connection data are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"LGRNAME","description":"A character string of up to eight characters in length that defines the LGR name for which the well LGR connection data are being defined. Note that the well name (LGRNAME) must have been declared previously using the WELSPECL keyword in the SCHEDULE section, otherwise an error may occur. If defaulted with 1* the LGR on the WELSPECL keyword will be utilized.","units":{},"default":"Defined","value_type":"STRING"},{"index":3,"name":"I","description":"A positive integer greater than or equal to zero and less than or equal to NX that defines the connection location in the I-direction. If set to zero or defaulted with 1* then all connections in the I-direction that also satisfy J, K1 and K2 criteria are assigned the ICOMP completion number.","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"J","description":"A positive integer greater than or equal to zero and less than or equal to NY that defines the connection location in the J-direction. If set to zero or defaulted with 1* then all connections in the J-direction that also satisfy I, K1 and K2 criteria are assigned the ICOMP completion number.","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"K1","description":"A positive integer greater than or equal to one and less than or equal to NZ that defines the UPPER connection location in the K-direction. If set to zero or defaulted with 1* then the upper most connection in the well is used.","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"K2","description":"A positive integer greater than or equal to K1 and less than or equal to NZ that defines the LOWER connection location in the K-direction. If set to zero or defaulted with 1* then the low most connection in the well is used.","units":{},"default":"0","value_type":"INT"},{"index":7,"name":"ICOMP","description":"An integer greater than or equal to one and less than or equal to MXCONS as defined on the WELLDIMS keyword in the RUNSPEC section, that defines the completion number of the currently defined set of connections. If I, J, K1, K2 are all set to zero or defaulted to 1*, then all connections in the well have the same completion number of ICOMP.","units":{},"default":"None","value_type":"INT"}],"example":"The following example defines the connections for two vertical oil wells using the COMPDATL keyword and the re-allocation of the connections to completions intervals using the COMPLMPL keyword.\n--\n-- WELL CONNECTION DATA FOR LGR WELLS\n--\n-- WELL LGR --- LOCATION --- OPEN SAT CONN WELL D DIR\n-- NAME NAME II JJ K1 K2 SHUT TAB FACT DIA FACT PEN\nCOMPDATL\nOP01 OP01LGR 14 13 20 56 OPEN 1* 1* 0.708 3* Z /\nOP01 OP01LGR 14 13 75 100 SHUT 1* 1* 0.708 3* Z /\nOP02 OP02LGR 35 96 75 100 OPEN 1* 1* 0.708 3* Z /\n/\n--\n-- ASSIGN WELL CONNECTIONS TO COMPLETIONS\n--\n-- WELL LGR --- LOCATION --- COMPL\n-- NAME NAME II JJ K1 K2 NO. COMPLMPL OP01 OP01LGR 1* 1* 20 56 1 / COMPLETION NO. 01\nOP01 OP01LGR 1* 1* 75 100 2 / COMPLETION NO. 02\nOP02 OP02LGR 1* 1* 75 85 1 / COMPLETION NO. 01\nOP02 OP21LGR 1* 1* 86 100 2 / COMPLETION NO. 02\n/\nHere the well OP01 connections (14, 13, 20) to (14, 13, 56) are assigned to completion number one and connections (14, 13, 75) to (14, 13, 100) are assigned to completion number two. Well OP02 has only one set of connection data from cells (35, 96, 75) to cells (35, 96, 100), but they have split into two separate completion intervals, with connections (35. 96, 75) to (35. 96, 85) assigned to completion interval number one and (35, 96, 86) to (35, 96, 100) to completion number two.","expected_columns":7,"size_kind":"list"},"COMPLUMP":{"name":"COMPLUMP","sections":["SCHEDULE"],"supported":null,"summary":"The COMPLUMP keyword assigns connections, as defined by the COMPDAT keyword in the SCHEDULE section, to completion intervals. This “lumping” of the connections to various completion intervals allows automatic workovers and economic criteria to be applied to the completions (that is a set of connections) as opposed to the connections. This allows for a more realistic approach for workovers operations.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well connection data are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"I","description":"A positive integer greater than or equal to zero and less than or equal to NX that defines the connection location in the I-direction. If set to zero or defaulted with 1* then all connections in the I-direction that also satisfy J, K1 and K2 criteria are assigned the ICOMP completion number.","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"J","description":"A positive integer greater than or equal to zero and less than or equal to NY that defines the connection location in the J-direction. If set to zero or defaulted with 1* then all connections in the J-direction that also satisfy I, K1 and K2 criteria are assigned the ICOMP completion number.","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"K1","description":"A positive integer greater than or equal to one and less than or equal to NZ that defines the UPPER connection location in the K-direction. If set to zero or defaulted with 1* then the uppermost connection in the well is used.","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"K2","description":"A positive integer greater than or equal to K1 and less than or equal to NZ that defines the LOWER connection location in the K-direction. If set to zero or defaulted with 1* then the lowermost connection in the well is used.","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"ICOMP","description":"An integer greater than or equal to one and less than or equal to MXCONS as defined on the WELLDIMS keyword in the RUNSPEC section, that defines the completion number of the currently defined set of connections. If I, J, K1, K2 are all set to zero or defaulted to 1*, then all connections in the well have the same completion number of ICOMP.","units":{},"default":"None","value_type":"INT"}],"example":"The following example defines the connections for two vertical oil wells using the COMPDAT keyword and the re-allocation of the connections to completions intervals using the COMPLUMP keyword.\n--\n-- WELL CONNECTION DATA\n--\n-- WELL --- LOCATION --- OPEN SAT CONN WELL KH SKIN D DIR\n-- NAME II JJ K1 K2 SHUT TAB FACT DIA FACT FACT FACT PEN\nCOMPDAT\nOP01 14 13 20 56 OPEN 1* 1* 0.708 1* 0.0 1* 'Z' /\nOP01 14 13 75 100 SHUT 1* 1* 0.708 1* 0.0 1* 'Z' /\nOP02 35 96 75 100 OPEN 1* 1* 0.708 1* 0.0 1* 'Z' /\n/\n--\n-- ASSIGN WELL CONNECTIONS TO COMPLETIONS\n--\n-- WELL --- LOCATION --- COMPL\n-- NAME II JJ K1 K2 NO. COMPLUMP OP01 1* 1* 20 56 1 / COMPLETION NO. 01\nOP01 1* 1* 75 100 2 / COMPLETION NO. 02\nOP02 1* 1* 75 85 1 / COMPLETION NO. 01\nOP02 1* 1* 86 100 2 / COMPLETION NO. 02\n/\nHere the well OP01 connections (14, 13, 20) to (14, 13, 56) are assigned to completion number one and connections (14, 13, 75) to (14, 13, 100) are assigned to completion number two. Well OP02 has only one set of connection data from cells (35, 96, 75) to cells (35, 96, 100), but they have been split into two separate completion intervals, with connections (35, 96, 75) to (35. 96, 85) assigned to completion interval number one and (35, 96, 86) to (35, 96, 100) assigned to completion number two.","expected_columns":6,"size_kind":"list"},"COMPOFF":{"name":"COMPOFF","sections":["SCHEDULE"],"supported":false,"summary":"The COMPOFF keyword deactivates network automatic compressors defined via the GASFCOMP keyword in the SCHEDULE section.","parameters":[],"example":"","size_kind":"none","size_count":0},"COMPORD":{"name":"COMPORD","sections":["SCHEDULE"],"supported":true,"summary":"The COMPORD keyword defines how the well connection data entered on the COMPDAT keyword in the SCHEDULE section are to be ordered for a well.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well connection data are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"COMPORD","description":"A character string that defines the method for ordering the well connections given on the COMPDAT keyword, and should be set to DEPTH, INPUT, or TRACK. DEPTH: The connections are ordered by a connection’s true vertical depth from the shallowest to the deepest. If multiple connections are at the same depth then these connections are sub ordered by the sequence they were entered on the COMPDAT keyword. INPUT: This option results in the connections being ordered in the same sequence as entered via the COMPDAT keyword. In this case the connections should be declared in the correct sequence, starting with the connection nearest the well head and then working along the wellbore towards the bottom or toe of the well. Atgeirr Rasmussen\n 2017-09-20T11:54:43\n AFR\n This option is somewhat involved to explain precisely, should we insert an explanation of the algorithm used here? If not here, where?\n TRACK\n David Baxendale\n 2017-10-02T17:52:03.846000000\n DBx\n Reply to Atgeirr Rasmussen (09/20/2017, 11:54): \"...\"\n Yes, we need to document this but I think this can wait until we get the first release out, otherwise we will never finish. I’ll keep the comments so we can trackt it.\n : This option enables OPM Flow to trace the well connections through the grid to obtain the correct order for the connections. If the supplied COMPDAT indicates the well is vertical (via the DIRECT variable being equal to Z on the COMPDAT keyword) then the DEPTH option will be applied instead. This option is somewhat involved to explain precisely, should we insert an explanation of the algorithm used here? If not here, where? Reply to Atgeirr Rasmussen (09/20/2017, 11:54): \"...\" Yes, we need to document this but I think this can wait until we get the first release out, otherwise we will never finish. I’ll keep the comments so we can trackt it. All options are now supported by OPM Flow.","units":{},"default":"TRACK","value_type":"STRING"}],"example":"The following example defines the connections for two vertical oil wells using the COMPDAT keyword and the COMPORD to defined the connection ordering for the wells.\n--\n-- WELL CONNECTION DATA\n--\n-- WELL --- LOCATION --- OPEN SAT CONN WELL KH SKIN D DIR\n-- NAME II JJ K1 K2 SHUT TAB FACT DIA FACT FACT FACT PEN\nCOMPDAT\nOP01 1* 1* 20 56 OPEN 1* 1* 0.708 1* 0.0 1* 'Z' /\nOP01 1* 1* 75 100 SHUT 1* 1* 0.708 1* 0.0 1* 'Z' /\nOP02 35 96 75 100 OPEN 1* 1* 0.708 1* 0.0 1* 'Z' /\n--\n-- DEFINE WELL CONNECTION ORDERING\n--\n-- WELL COMPL\n-- NAME ORDER\nCOMPORD\nOP01 DEPTH /\nOP02 DEPTH /\n/\nThe DEPTH option has been chosen because both wells are vertical. Also one could use the following format instead for the COMPORD:\n--\n-- DEFINE WELL CONNECTION ORDERING\n--\n-- WELL COMPL\n-- NAME ORDER\nCOMPORD\n* DEPTH /\n/\nas both wells should utilize the DEPTH option. This version would set all wells in the model to DEPTH connection ordering.\n| Note If visual inspection of the well trajectories in the model indicate problematic or unrealistic well connections, the options on this keyword may be useful in correcting the issue. |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":2,"size_kind":"list"},"COMPRIV":{"name":"COMPRIV","sections":["SCHEDULE"],"supported":false,"summary":"The COMPRIV keyword defines grid cell connections to a river, for when the River option has been activated via the RIVRDIMS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"RIVER","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"I","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"J","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"K","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":4,"size_kind":"list"},"COMPRP":{"name":"COMPRP","sections":["SCHEDULE"],"supported":false,"summary":"The COPMPRP keyword re-scales the fluid saturations of a well’s connection to the grid block.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"I","description":"","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"J","description":"","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"K_UPPER","description":"","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"K_LOWER","description":"","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"SAT_TABLE_NUM","description":"","units":{},"default":"","value_type":"INT"},{"index":7,"name":"SWMIN","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":8,"name":"SWMAX","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":9,"name":"SGMIN","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":10,"name":"SGMAX","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"}],"example":"","expected_columns":10,"size_kind":"list"},"COMPRPL":{"name":"COMPRPL","sections":["SCHEDULE"],"supported":false,"summary":"The COPMPRPL keyword re-scales the fluid saturations of a well’s connection to an LGR grid block, for when the Local Grid Refinement (“LGR”) option has been activated by the LGR keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"LOCAL_GRID","description":"","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"I","description":"","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"J","description":"","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"K_UPPER","description":"","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"K_LOWER","description":"","units":{},"default":"0","value_type":"INT"},{"index":7,"name":"SAT_TABLE_NUM","description":"","units":{},"default":"","value_type":"INT"},{"index":8,"name":"SWMIN","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":9,"name":"SWMAX","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":10,"name":"SGMIN","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":11,"name":"SGMAX","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"}],"example":"","expected_columns":11,"size_kind":"list"},"COMPSEGL":{"name":"COMPSEGL","sections":["SCHEDULE"],"supported":false,"summary":"The COMSEGSL keyword defines how a multi-segment well is connected to the reservoir by defining or modifying existing well connections in an LGR. Note that well must have been previously define by the WELSPECL keyword in the SCHEDULE section and the well connections must have been previously defined via the COMPDATL keyword in the SCHEDULE section. The COMPSEGL keyword should be repeated for each multi-segment well in the model.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which a multi-segment well is being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECL keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","record":1,"value_type":"STRING"},{"index":1,"name":"LGRNAME","description":"A character string of up to eight characters in length that defines the name of the local grid refinement for which the well is assigned to.","units":{},"default":"None","record":2,"value_type":"STRING"},{"index":2,"name":"I","description":"A positive integer greater than or equal to one and less than or equal to NX that defines the connection location in the I-direction.","units":{},"default":"None","record":2,"value_type":"INT"},{"index":3,"name":"J","description":"A positive integer greater than or equal to zero and less than or equal to NY that defines the connection location in the J-direction.","units":{},"default":"None","record":2,"value_type":"INT"},{"index":4,"name":"K","description":"A positive integer greater than or equal to zero and less than or equal to NZ that defines the connection location in the K-direction.","units":{},"default":"None","record":2,"value_type":"INT"},{"index":5,"name":"IBRANCH","description":"A positive integer greater than or equal to one and less than or equal to MXBRAN on WSEGDIMS keyword in the RUNSPEC section that defines the branch number of the defined I, J and K connection.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","record":2,"value_type":"INT"},{"index":6,"name":"DISTANCE_START","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length","record":2},{"index":7,"name":"DEPTH2","description":"DEPTH2 is a real positive value that defines the length of the tubing from the tubing head or wellhead at the surface to the end of the connection in the I, J, K cell.","units":{},"default":"","record":2,"value_type":"DOUBLE","dimension":"Length"},{"index":8,"name":"DIRECT","description":"A one letter character string that defines the orientation of the connections and should be set to either X, Y, or Z. The direction of connections also determines the length of the connection The default value is for a vertical connection, that is DIRECT is defaulted to Z.","units":{},"default":"Z","record":2,"value_type":"STRING"},{"index":9,"name":"IEND","description":"IEND is positive or negative integer, that is not equal to zero that is set to one of the following: a value between -NX and +NX that is not equal to zero that defines the last connection location in the I-direction, a value between -NY and +NY that is not equal to zero that defines the last connection location in the J-direction, or a value between -NZ and +NZ that is not equal to zero that defines the last connection location in the K-direction, that defines the end of the range of the connections depending on the value of DIRECT. For example, if DIRECT is equal to Y or J then the IEND will be associated with the J-direction. The value may be positive or negative but must be calculated to remain within the grid. For example for NY is set 100 on the DIMENS keyword in the RUNSPEC section and J on this record set to 50, then IEND most range between -49 to +50. Currently this option is not supported by OPM Flow.","units":{},"default":"None","record":2,"value_type":"INT"},{"index":10,"name":"DEPTH3","description":"DEPTH3 is a real positive value that defines the datum depth for this set of connection, normally taken as the mid-point of the perforations associated with this set of connections. Currently this option is not supported by OPM Flow.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","record":2,"value_type":"DOUBLE","dimension":"Length"},{"index":11,"name":"LENGTH","description":"LENGTH is a real positive value that defines the length of the well for this set of completions that is used in thermal calculations.. Currently this option is not supported by OPM Flow.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","record":2,"value_type":"DOUBLE","dimension":"Length"},{"index":12,"name":"ISEG","description":"A real positive values equal to or greater than zero that defines the coordinate in the x-direction of the nodal point of this segment that is used for display purposes only. Currently this option is not supported by OPM Flow.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","record":2,"value_type":"INT"}],"example":"The following example defines the completions for two oil producing segment oil wells (OP01 and OP02) using the COMPSEGS keywords.\n-- COMPLETION SEGMENT SPECIFICATION DATA\n--\n-- WELL\n-- NAME\nCOMPSEGS\nOP01 /\n-- LGR --LOCATION-- BRAN TUBING NODAL DIR LOC MID COMP ISEG\n-- NAME II JJ K1 NO LENGTH DEPTH PEN I,J,K PERFS LENGTH\nLGR01 10 10 1 1 2512.5 2525.0 /\nLGR01 10 10 2 1 2525.0 2550.0 /\nLGR01 10 10 3 1 2550.0 2575.0 /\nLGR01 10 10 4 1 2575.0 2600.0 /\nLGR01 10 10 5 1 2600.0 2625.0 /\nLGR01 10 10 6 1 2625.0 2650.0 /\nLGR01 9 10 2 2 2637.5 2837.5 /\nLGR01 8 10 2 2 2837.5 3037.5 /\nLGR01 7 10 2 2 3037.5 3237.5 /\nLGR01 6 10 2 2 3237.5 3437.5 /\nLGR01 5 10 2 2 3437.5 3637.5 /\n/\nNote that the COMPDATL keyword in the SCHEDULE section must also be defines for this well.","records_meta":[{"expected_columns":1},{"expected_columns":12}],"size_kind":"list"},"COMPSEGS":{"name":"COMPSEGS","sections":["SCHEDULE"],"supported":false,"summary":"This keyword defines how a multi-segment well is connected to the reservoir by allocating each well connection to a well segement. Note that the well must have previously been defined as a multi-segment well using the WELSEGS keyword in the SCHEDULE section and the well connections must have previously been defined via the COMPDAT keyword in the SCHEDULE section.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which a multi-segment well is being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","record":1,"value_type":"STRING"},{"index":1,"name":"I","description":"A positive integer greater than or equal to one and less than or equal to NX that defines the connection location in the I-direction.","units":{},"default":"None","record":2,"value_type":"INT"},{"index":2,"name":"J","description":"A positive integer greater than or equal to one and less than or equal to NY that defines the connection location in the J-direction.","units":{},"default":"None","record":2,"value_type":"INT"},{"index":3,"name":"K","description":"A positive integer greater than or equal to one and less than or equal to NZ that defines the connection location in the K-direction.","units":{},"default":"None","record":2,"value_type":"INT"},{"index":4,"name":"IBRANCH","description":"A positive integer greater than or equal to one and less than or equal to MXBRAN on WSEGDIMS keyword in the RUNSPEC section that defines the branch number of the defined I, J and K connection.","units":{},"default":"None","record":2,"value_type":"INT"},{"index":5,"name":"LENGTH1","description":"A real positive value that defines the length of the tubing from the tubing reference point (for example Measure Depth Relative to Kelly Bushing, MDRKB) to the start of the connection in the I, J, K cell.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","record":2,"value_type":"DOUBLE","dimension":"Length"},{"index":6,"name":"LENGTH2","description":"A real positive value that defines the length of the tubing from the tubing reference point to the end of the connection in the I, J, K cell.","units":{},"default":"","record":2,"value_type":"DOUBLE","dimension":"Length"},{"index":7,"name":"DIRECT","description":"A one letter character string that defines the orientation of the connections and should be set to either X, Y or Z, or either I, J or K. The direction of connections may also determine the length of the connection. Currently this option is not supported by OPM Flow.","units":{},"default":"None","record":2,"value_type":"STRING"},{"index":8,"name":"IJKEND","description":"A positive integer that is set to one of the following depending on the orientation of the connections (DIRECT): X or I: A value between 1 and NX that defines the last connection location in the I-direction, Y or J: A value between 1 and NY that defines the last connection location in the J-direction, or Z or K: A value between 1 and NZ that defines the last connection location in the K-direction. For example, if DIRECT is equal to Y or J then the IJKEND will be associated with the J-direction. The value may be less than or greater than Y or J but must be between 1 and NY. Currently this option is not supported by OPM Flow.","units":{},"default":"None","record":2,"value_type":"INT"},{"index":9,"name":"DEPTH","description":"A real positive value that defines the datum depth for this set of connections, normally taken as the mid-point of the perforations associated with this set of connections. Currently this option is not supported by OPM Flow.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","record":2,"value_type":"DOUBLE","dimension":"Length"},{"index":10,"name":"THLEN","description":"A real positive value that defines the length of the well in the connection cells for this set of completions that is used in thermal calculations. If this value is defaulted then the thickness of the cell in the direction of the well orientation (DIRECT) is used. Currently this option is not supported by OPM Flow.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","record":2,"value_type":"DOUBLE","dimension":"Length"},{"index":11,"name":"ISEG","description":"A real positive value that defines the segment number to assign to this range of connections. If this value is defaulted then each connection is assigned to the segment with the nodal point nearest to the centre of the connection. Currently this option is not supported by OPM Flow.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","record":2,"value_type":"INT"}],"example":"The following example defines the completions for two multi-segment oil production wells (OP01 and OP02) using the COMPSEGS keyword.\n-- COMPLETION SEGMENT SPECIFICATION DATA\n--\n-- WELL\n-- NAME\nCOMPSEGS\nOP01 /\n-- --LOCATION-- BRAN START END DIR LOC MID COMP ISEG\n-- II JJ K1 NO LENGTH LENGTH PEN I,J,K PERFS LENGTH\n10 10 1 1 2512.5 2525.0 /\n10 10 2 1 2525.0 2550.0 /\n10 10 3 1 2550.0 2575.0 /\n10 10 4 1 2575.0 2600.0 /\n10 10 5 1 2600.0 2625.0 /\n10 10 6 1 2625.0 2650.0 /\n9 10 2 2 2637.5 2837.5 /\n8 10 2 2 2837.5 3037.5 /\n7 10 2 2 3037.5 3237.5 /\n6 10 2 2 3237.5 3437.5 /\n5 10 2 2 3437.5 3637.5 /\n/\n-- COMPLETION SEGMENT SPECIFICATION DATA\n--\n-- WELL\n-- NAME\nCOMPSEGS\nOP02 /\n-- --LOCATION-- BRAN START END DIR LOC MID COMP ISEG\n-- II JJ K1 NO LENGTH LENGTH PEN I,J,K PERFS LENGTH\n1 9 3 1 2662.5 2862.5 /\n1 8 3 1 2862.5 3062.5 /\n1 7 3 1 3062.5 3262.5 /\n1 6 3 1 3262.5 3462.5 /\n1 5 3 1 3462.5 3662.5 /\n2 10 5 2 2712.5 2912.5 /\n2 10 5 2 2912.5 3112.5 /\n4 10 5 2 3112.5 3312.5 /\n5 10 5 2 3312.5 3512.5 /\n6 10 5 2 3512.5 3712.5 /\n1 9 6 3 2737.5 2937.5 /\n1 8 6 3 2937.5 3137.5 /\n1 7 6 3 3137.5 3337.5 /\n1 6 6 3 3337.5 3537.5 /\n1 5 6 3 3537.5 3737.5 /\n/\nNote that the COMPDAT keyword in the SCHEDULE section must also be defined for these two wells.","records_meta":[{"expected_columns":1},{"expected_columns":11}],"size_kind":"list"},"COMPTRAJ":{"name":"COMPTRAJ","sections":["SCHEDULE"],"supported":true,"summary":"The COMPTRAJ keyword defines how a well that has been declared as a trajectory well, using the WELTRAJ keyword in the SCHEDULE section, is connected to the reservoir model by defining or modifying existing well perforation depths. The keyword can only be used for wells defined by the WELTRAJ keyword, and WELTRAJ defined wells must use the COMPTRAJ keyword to define the connections to the grid, that is one cannot use COMPDAT for these type of wells.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well connection data are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"IBRANCH","description":"A positive integer greater than or equal to one and less than or equal to MXBRAN on WSEGDIMS keyword in the RUNSPEC section that defines the branch number of a segment. All segments on the main stem must have IBRANCH set to one and lateral branches should have values between two and MXSEGS on the WSEGDIMS keyword in the RUNSPEC section. Only the default value of one is currently supported, that is only the main branch of a multi-segment well is supported, or a single trajectory for a conventional well.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"1","value_type":"INT"},{"index":3,"name":"PERF_TOP","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":4,"name":"PERF_BOT","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":5,"name":"REF","description":"REF is a defined character string that defines the reference depth type for TOP and BOT, and should be set to either: MD for the depths referencing Measured Depth, or TVD for depths referencing True Vertical Depth. Only measured depth is currently supported, that is MD.","units":{},"default":"MD","value_type":"STRING"},{"index":6,"name":"ICOMP","description":"An integer greater than or equal to one and less than or equal to MXCONS as defined on the WELLDIMS keyword in the RUNSPEC section, that defines the completion number of the currently defined perforation interval (connection interval). If defaulted with 1*, then ICOMP is set equal to one.","units":{},"default":"1","value_type":"INT"},{"index":7,"name":"STATUS","description":"A defined character string of length four that defines the connections’ operational status within the perforation interval, STATUS should be set to one of the following character strings: OPEN: the connections are open to flow. SHUT: the connections are closed to flow (shut-in). AUTO: the connection are initially closed, but may be opened automatically if an economic limit is violated. Currently this option is not supported by OPM Flow.","units":{},"default":"OPEN","value_type":"STRING","options":["OPEN","SHUT","AUTO"]},{"index":8,"name":"SATNUM","description":"An integer greater than or equal to zero and less than NTSFUN as declared on the TABDIMS keyword in the RUNSPEC, that defines the saturation table number to be used for flow between the reservoir grid block and the well connections. If SATNUM is set to zero or defaulted with 1* then: The saturation table allocated to the grid block that the connections are located within are used. If the hysteresis option has been activated via the HYSTER variable on the SATOPTS keyword in the RUNSPEC section, then both the imbibition and drainage saturation tables allocated to the grid block that the connections are located within are used. The imbibition table allocation can be changed by the COMPIMB keyword in the RUNSPEC section, provided it is entered after the COMPTRAJ keyword.","units":{},"default":"0","value_type":"INT"},{"index":9,"name":"CONFACT","description":"A real value greater than or equal to zero that defines the transmissibility connection factor between the well bore and the reservoir grid block. If set to zero or defaulted with 1* then items (10) through (13) are used to calculate CONFACT.","units":{"field":"cP.rb/day/psia 0","metric":"cP.rm3/day/bars 0","laboratory":"cP.rcc/hr/atm 0"},"default":"Defined","value_type":"DOUBLE","dimension":"Viscosity*ReservoirVolume/Time*Pressure"},{"index":10,"name":"DW","description":"A real positive value that defines the well bore diameter of the connections for the well. DW is used in calculating a well’s productivity or injectivity index; however the value will be ignored in calculating the connections CONFACT value if CONFAC has been directly entered.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":"Length"},{"index":11,"name":"KH","description":"A real value that defines the effective KH (permeability x length) for the connections within the perforation interval. If less than or equal to zero, or defaulted by 1*, then KH is calculated from the connected grid blocks. KH is ignored if CONFACT has been directly entered.","units":{"field":"mD.ft","metric":"mD.m","laboratory":"mD.cm"},"default":"Calculated from connected grid blocks","value_type":"DOUBLE","dimension":"Permeability*Length"},{"index":12,"name":"SKIN","description":"A real value that defines the connections dimensionless skin factor. SKIN is used in calculating a well’s productivity or injectivity index; however, the value will be ignored in calculating the connections CONFACT value if CONFACT has been directly entered.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.0","value_type":"DOUBLE","dimension":"1"},{"index":13,"name":"DFACT","description":"A real value that defines the non-Darcy D factor coefficient for gas wells. This value should be defaulted with 1* and the non-Darcy D factor coefficient for gas wells defined via the WDFAC keyword in the SCHEDULE section. Currently this option is not supported by OPM Flow.","units":{"field":"day/Mscf","metric":"day/m3","laboratory":"hour/sc"},"default":"1*","value_type":"DOUBLE","dimension":"1"}],"example":"The following example defines two trajectory wells oil wells, OP01 and OP02, using the WELTRAJ keyword, together with their perforations using the COMPTRAJ keyword.\n--\n-- WELL SPECIFICATION DATA\n--\n-- WELL GROUP LOCATION BHP PHASE DRAIN INFLOW OPEN CROSS PVT\n-- NAME NAME I J DEPTH FLUID AREA EQUANS SHUT FLOW TABLE\nWELSPECS\nOP01 PLATFORM 1* 1* 1* OIL 1* STD SHUT NO 1* /\nOP02 PLATFORM 1* 1* 1* OIL 1* STD SHUT NO 1* /\n/\n--\n-- WELL TRAJECTORY DATA\n--\n-- WELL BRAN XCORD YCORD TVDSS MD\n-- NAME NO DEPTH DEPTH\n-- ----- ---- ------------ ------------ ------------ ------------\nWELTRAJ\nOP01 1* 2.805445e+06 3.602948e+06 -100.000000 0.0 /\nOP01 1* 2.805445e+06 3.602948e+06 877.0000000 977.0 /\nOP01 1* 2.805445e+06 3.602948e+06 957.9950240 1058.0 /\nOP01 1* 2.805444e+06 3.602946e+06 1051.976081 1152.0 /\n…………………... /\nOP02 1* 2.810828e+06 3.604507e+06 9371.792711 11418.0 /\nOP02 1* 2.810885e+06 3.604525e+06 9443.657000 11511.0 /\nOP02 1* 2.810952e+06 3.604546e+06 9531.966162 11624.0 /\nOP02 1* 2.810973e+06 3.604553e+06 9560.411742 11660.0 /\n/\n--\n--\n-- WELL TRAJECTORY CONNECTION DATA\n--\n-- WELL BRAN -- PERFORATION -- COMPL OPEN SAT CONN WELL KH SKIN D\n-- NAME NO. TOP BOT REF NO. SHUT TAB FACT DIA FACT FACT FACT\nCOMPTRAJ\nOP01 1* 8230 8244 MD 1 SHUT 1* 1* 0.708 1* 0.0 1* /\nOP01 1* 8352 8380 MD 1 SHUT 1* 1* 0.708 1* 0.0 1* /\nOP01 1* 9070 9100 MD 1 SHUT 1* 1* 0.708 1* 0.0 1* /\nOP01 1* 9220 9250 MD 2 SHUT 1* 1* 0.708 1* 0.0 1* /\nOP01 1* 9266 9280 MD 2 SHUT 1* 1* 0.708 1* 0.0 1* /\nOP01 1* 9693 9703 MD 3 SHUT 1* 1* 0.708 1* 0.0 1* /\nOP01 1* 9940 9974 MD 3 SHUT 1* 1* 0.708 1* 0.0 1* /\nOP02 1* 9979 9985 TVD 1* SHUT 1* 1* 0.708 1* 0.0 1* /\nOP02 1* 10173 10183 TVD 1* SHUT 1* 1* 0.708 1* 0.0 1* /\nOP02 1* 10190 10204 TVD 1* SHUT 1* 1* 0.708 1* 0.0 1* /\nOP02 1* 10327 10333 TVD 1* SHUT 1* 1* 0.708 1* 0.0 1* /\nOP02 1* 10339 10345 TVD 1* SHUT 1* 1* 0.708 1* 0.0 1* /\nOP02 1* 11528 11538 TVD 1* SHUT 1* 1* 0.708 1* 0.0 1* /\n/\nWell OP01 has eight perforation intervals, with the intervals one to three grouped into one completion, perforation intervals four to five grouped into completion number two, and finally the bottom three perforations are grouped into completion number three. In contrast, OP02 has six perforated intervals with their completion interval defaulted to one.\n| Note This is an OPM Flow specific keyword and will therefore cause an error in the commercial simulator. |\n|----------------------------------------------------------------------------------------------------------|\n| Note The term well connection is used to describe individual connections from the wellbore to the reservoir grid, as opposed to well completions. A well completion is used to describe a set of connections, for example, a well may consist of several completions with each completion consisting of multiple connections. For wells defined using the WELTRAJ and COMPTRAJ keywords, the WELTRAJ keyword defines the trajectory of the well within the model, and the COMPTRAJ defines the perforation intervals in the well. A perforation interval will automatically generate various well connections to the grid, and in addition multiple perforation intervals may be grouped into a completion. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":13,"size_kind":"list"},"COMPVE":{"name":"COMPVE","sections":["SCHEDULE"],"supported":false,"summary":"The COMPVE keyword is used to re-define the well connection depths in the global grid.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"I","description":"","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"J","description":"","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"K_UPPER","description":"","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"K_LOWER","description":"","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"SAT_TABLE_NUM","description":"","units":{},"default":"","value_type":"INT"},{"index":7,"name":"CVEFRAC","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":8,"name":"DTOP","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":9,"name":"DBOT","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":10,"name":"FLAG","description":"","units":{},"default":"NO","value_type":"STRING"},{"index":11,"name":"S_D","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":12,"name":"GTOP","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":13,"name":"GBOT","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"}],"example":"","expected_columns":13,"size_kind":"list"},"COMPVEL":{"name":"COMPVEL","sections":["SCHEDULE"],"supported":false,"summary":"The COMPVEL keyword is used to re-define the well connection depths in a Local Grid Refinement (“LGR”) grid.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"LOCAL","description":"","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"I","description":"","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"J","description":"","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"K_UPPER","description":"","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"K_LOWER","description":"","units":{},"default":"0","value_type":"INT"},{"index":7,"name":"SAT_TABLE_NUM","description":"","units":{},"default":"","value_type":"INT"},{"index":8,"name":"CVEFRAC","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":9,"name":"DTOP","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":10,"name":"DBOT","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":11,"name":"FLAG","description":"","units":{},"default":"NO","value_type":"STRING"},{"index":12,"name":"S_D","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":13,"name":"GTOP","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":14,"name":"GBOT","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"}],"example":"","expected_columns":14,"size_kind":"list"},"CPIFACT":{"name":"CPIFACT","sections":["SCHEDULE"],"supported":false,"summary":"The CPIFACT keyword is used to define well connection transmissibility multipliers for well connections to the global grid.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"MULT","description":"","units":{},"default":"","value_type":"UDA"},{"index":3,"name":"I","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"J","description":"","units":{},"default":"","value_type":"INT"},{"index":5,"name":"K","description":"","units":{},"default":"","value_type":"INT"},{"index":6,"name":"C1","description":"","units":{},"default":"","value_type":"INT"},{"index":7,"name":"C2","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":7,"size_kind":"list"},"CPIFACTL":{"name":"CPIFACTL","sections":["SCHEDULE"],"supported":false,"summary":"The CPIFACT keyword is used to define well Local Grid Refinement (“LGR”) connection transmissibility multipliers for well connections to a LGR, for when the LGR option has been invoked by the LGR keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"MULT","description":"","units":{},"default":"","value_type":"UDA"},{"index":3,"name":"LGR","description":"","units":{},"default":"","value_type":"STRING"},{"index":4,"name":"I","description":"","units":{},"default":"","value_type":"INT"},{"index":5,"name":"J","description":"","units":{},"default":"","value_type":"INT"},{"index":6,"name":"K","description":"","units":{},"default":"","value_type":"INT"},{"index":7,"name":"C1","description":"","units":{},"default":"","value_type":"INT"},{"index":8,"name":"C2","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":8,"size_kind":"list"},"CSKIN":{"name":"CSKIN","sections":["SCHEDULE"],"supported":null,"summary":"This keyword, CSKIN, is used to re-define a well’s connection skin factors and as such will result in the well’s connection transmissibility factors being updated accordingly. The well connections must already be defined using the COMPDAT keyword in the SCHEDULE section before this keyword can be used.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well connection skin is being re-defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"I","description":"A positive integer greater than or equal to one and less than or equal to NX that defines the connection location in the I-direction. If set to zero or defaulted with 1* then connections in any I-direction location will be modified.","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"J","description":"A positive integer greater than or equal to one and less than or equal to NY that defines the connection location in the J-direction. If set to zero or defaulted with 1* then connections in any J-direction location will be modified.","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"K1","description":"A positive integer greater than or equal to one and less than or equal to K2 and NZ that defines the UPPER connection location in the K-direction. If set to zero or defaulted with 1* then this will be taken from the top connection of the well.","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"K2","description":"A positive integer greater than or equal to K1 and less than or equal to NZ that defines the LOWER connection location in the K-direction. If set to zero or defaulted with 1* then this will be taken from the bottom connection of the well.","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"SKIN","description":"A real value that defines the connections’ dimensionless skin factors.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.0","value_type":"DOUBLE","dimension":"1"}],"example":"The following example re-defines the skin factor for all well OP01 connections in layers 4 to 6.\n--\n-- CONNECTION SKIN DATA\n--\n-- WELL --- LOCATION --- SKIN\n-- NAME II JJ K1 K2 FACT\nCSKIN\nOP01 1* 1* 4 6 2.0 /\n/","expected_columns":6,"size_kind":"list"},"DATES":{"name":"DATES","sections":["SCHEDULE"],"supported":null,"summary":"This keyword advances the simulation to a given report date after which additional keywords may be entered to instruct OPM Flow to perform additional functions via the SCHEDULE section keywords, or further DATES data sets or keywords may be entered to advance the simulator to the next report date.","parameters":[{"index":1,"name":"DAY","description":"A positive integer that defines the day of the month for the data set, the value should be greater than or equal to one and less than or equal to 31.","units":{},"default":"None","value_type":"INT"},{"index":2,"name":"MONTH","description":"Character string for the month for the data set and should be one of the following 'JAN', 'FEB', 'MAR', 'APR', 'MAY', 'JUN', 'JUL' (or 'JLY'), 'AUG', 'SEP', 'OCT', 'NOV', or 'DEC'","units":{},"default":"None","value_type":"STRING"},{"index":3,"name":"YEAR","description":"A positive four digit integer value representing the year for the data set, which must be specified fully by four digits, that is 1986.","units":{},"default":"None","value_type":"INT"},{"index":4,"name":"TIME","description":"A numeric character string that defines the time for the data set in the form of: HH:MM:SS.SSSS The default value means in most cases this parameter can be defaulted. TIME is normally used when detailed DST matching is performed to enable the pressures and rates to be stated at specific dates and times.","units":{},"default":"00:00:00","value_type":"STRING"}],"example":"Given a start date of January 1, 2020 set via the START keyword in the RUNSPEC section, the following example advances the simulator from the start date of January 1, 2020 to January 1, 2021, using quarterly reporting time steps.\n-- ==============================================================================\n--\n-- SCHEDULE SECTION\n--\n-- ==============================================================================\nSCHEDULE\n-- ------------------------------------------------------------------------------\n-- SCHEDULE SECTION - 2020-01-01\n-- ------------------------------------------------------------------------------\nRPTSCHED\n'WELLS=2' 'WELSPECS' 'CPU=2' FIP=2' /\nDATES\n2 JAN 2020 /\n/\nRPTSCHED\n'NOTHING' /\nDATES\n1 APR 2020 /\n1 JLY 2020 /\n1 OCT 2020 /\n/\n-- ------------------------------------------------------------------------------\n-- SCHEDULE SECTION - 2021-01-01\n-- ------------------------------------------------------------------------------\nRPTSCHED\n'WELLS=2' 'WELSPECS' 'CPU=2' FIP=2' /\nDATES\n1 JAN 2021 /\n/\nRPTSCHED\n'NOTHING' /\nDATES\n1 APR 2021 /\n1 JLY 2021 /\n1 OCT 2021 /\n/\nThe above example writes out a series of report at the start of the run and then advances the simulation one day to January 2, 2020 and switches off the reporting. The simulation then advances to April 1, July 1 and October 1, 2020 with no further changes to the run. After October 1, 2020 reporting is switched on again to enable a report on January 1, 2021, which is then subsequently switched off after the January 1, 2021 report time step has been completed.\nNote if one wishes to terminate the run at the end of year (as opposes to the beginning of the year and get a final report for the year, then the next example demonstrates the keyword sequence to enable this.\n-- ------------------------------------------------------------------------------\n-- SCHEDULE SECTION - 2021-01-01\n-- ------------------------------------------------------------------------------\nRPTSCHED\n'WELLS=2' 'WELSPECS' 'CPU=2' FIP=2' /\nDATES\n2 JAN 2021 /\n/\nRPTSCHED\n'NOTHING' /\nDATES\n1 FEB 2021 /\n1 MAR 2021 /\n1 APR 2021 /\n1 MAY 2021 /\n1 JUN 2021 /\n1 JLY 2021 /\n1 AUG 2021 /\n1 SEP 2021 /\n1 OCT 2021 /\n1 NOV 2021 /\n1 DEC 2021 /\n/\n--\n-- FINAL REPORT AND RESTART AT YEAR END\n--\nRPTSCHED\n'WELLS=2' 'WELSPECS' 'CPU=2' FIP=2' /\nRPTRST\n'BASIC=2' /\nDATES\n31 DEC 2021 /\n/\nIn the above example monthly reporting time steps have been used instead of quarterly and report is requested after the December 1, 2021 time step and is therefore written out on December 31, 2021.","expected_columns":4,"size_kind":"list"},"DCQDEFN":{"name":"DCQDEFN","sections":["SCHEDULE"],"supported":false,"summary":"The DCQDEFN keyword defines the DCQ units to be rate or energy (calorific value) when using the Gas Field Operation model and the Gas Calorific Value control option. The gas DCQ rates are controlled by the GASYEAR, GASPERIO, GDCQ, GASFTARG or GASFDECR keywords in the SCHEDULE section.","parameters":[{"index":1,"name":"QUANTITY","description":"","units":{},"default":"GAS","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"DELAYACT":{"name":"DELAYACT","sections":["SCHEDULE"],"supported":false,"summary":"The DELAYACT keyword defines a series of keywords that should be executed after an ACTION keyword has been triggered by the ACTION, ACTIONG, ACTIONR, ACTIONW, ACTIONS, or ACTIONX keywords.","parameters":[{"index":1,"name":"ACTION_NAME","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"ACTION_TRIGGER","description":"","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"DELAY","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Time"},{"index":4,"name":"NUM_TIMES","description":"","units":{},"default":"1","value_type":"INT"},{"index":5,"name":"INCREMENT","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Time"}],"example":"","expected_columns":5,"size_kind":"fixed","size_count":1},"DIMPES":{"name":"DIMPES","sections":["SCHEDULE"],"supported":null,"summary":"This keyword, DIMPES, defines the Implicit in Pressure Explicit Saturation (“IMPES”) dynamic solution parameters and results in the simulator switching from the current solution formulation to the IMPES formulation. OPM Flow uses a different numerical scheme which makes this keyword redundant; hence, OPM Flow ignores this keyword. It is documented here for completeness.","parameters":[{"index":1,"name":"DSTARG","description":"","units":{},"default":"0.05","value_type":"DOUBLE","dimension":"1"},{"index":2,"name":"DSMAX","description":"","units":{},"default":"0.1","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"DPMAX","description":"","units":{},"default":"13.79","value_type":"DOUBLE","dimension":"Pressure"}],"example":"--\n-- ACTIVATE THE IMPES SOLUTION OPTION\n--\nDIMPES\nThe above example switches on the IMPES solution option; however, this has no effect in OPM Flow input decks.","expected_columns":3,"size_kind":"fixed","size_count":1},"DIMPLICT":{"name":"DIMPLICT","sections":["SCHEDULE"],"supported":null,"summary":"This keyword, DIMPLICT, activates the Fully Implicit Formulation and results in the simulator switching from the current solution formulation to the fully implicit formulation. OPM Flow uses a different numerical scheme which makes this keyword redundant; hence, OPM Flow ignores this keyword. It is documented here for completeness.","parameters":[],"example":"--\n-- ACTIVATES THE FULLY IMPLICIT SOLUTION OPTION\n--\nDIMPLICT\nThe above example switches on the fully implicit solution option; however, this has no effect in OPM Flow input decks.","size_kind":"none","size_count":0},"DRILPRI":{"name":"DRILPRI","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, DRILPRI, defines the prioritized drilling queue priority parameters used in the priority formulae for this type of drilling queue.","parameters":[{"index":1,"name":"INTERVAL","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Time"},{"index":2,"name":"A","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":3,"name":"B","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":4,"name":"C","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":5,"name":"D","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":6,"name":"E","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":7,"name":"F","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":8,"name":"G","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":9,"name":"H","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":10,"name":"LOOK_AHEAD","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Time"},{"index":11,"name":"CALCULATION","description":"","units":{},"default":"SINGLE","value_type":"STRING"}],"example":"","expected_columns":11,"size_kind":"fixed","size_count":1},"DRSDT":{"name":"DRSDT","sections":["SCHEDULE"],"supported":null,"summary":"DRSDT defines the maximum rate at which the solution gas-oil ratio (Rs) can be increased in a grid cell. The keyword is similar in functionality to the DRSDTR keyword, that defines the maximum rate at which Rs can be increased in a grid cell by region. Both keywords should only be used if the OIL, GAS, and DISGAS keywords in the RUNSPEC section have been invoked to allow oil, gas and dissolved gas to be present in the model. The keyword only affects the behavior of an increasing Rs, for example when gas is being injected into an oil reservoir, and is subject to the availability of free gas and the ability of the undersaturated oil to adsorb this gas.","parameters":[{"index":1,"name":"DRSDT1","description":"DRSDT1 is a real positive number that defines the maximum rate at which the solution gas-oil ratio is allowed to increase in a grid cell, that is the maximum rate the gas can dissolve into the available undersaturated oil. A value of zero means that Rs cannot increase and free gas cannot dissolve into the unsaturated oil in a grid cell. Alternatively a very large value of DRSDT1 allows Rs to increase rapidly until there is no free gas or the oil within the grid block is fully saturated. Note if the keyword is not present in the input deck then DRSDT1 is assumed to be a very large number resulting in complete re-solution of the gas into the available undersaturated oil.","units":{"field":"Mscf/stb/d","metric":"sm3/sm3/day","laboratory":"scc/scc/day"},"default":"None","value_type":"DOUBLE","dimension":"GasDissolutionFactor/Time"},{"index":2,"name":"DRSDT2","description":"DRSDT2 is a defined character string that defines whether the DRSDT1 is applied to either all grid blocks or just those grid blocks containing free gas: ALL: means the DRSDT1 maximum rate at which Rs is allowed to increase in a grid cell is applied to all grid blocks. FREE: means the DRSDT1 maximum rate at which Rs is allowed to increase in a grid cell is applied to grid blocks only containing free gas. Note if the keyword is not present in the input deck then DRSDT2 is set to the default value of ALL.","units":{},"default":"ALL","value_type":"STRING","options":["ALL","FREE"]}],"example":"The first example prevents the solution gas-oil ratio from increasing and applies this to all grid cells.\n--\n-- SOLUTION GAS (RS) MAXIMUM RATE OF INCREASE FOR MODEL --\nDRSDT\n-- MAX RS ALL/FREE\n-- DRSDT1 DRSDT2\n-- ------- --------\n0.000 ALL /\nAnd the second example below applies 0.0005 Mscf/stb/d as the maximum rate at which the solution gas-oil ratio is allowed to increase in a grid cell, and applies this to only cells containing free gas.\n--\n-- SOLUTION GAS (RS) MAXIMUM RATE OF INCREASE FOR MODEL --\nDRSDT\n-- MAX RS ALL/FREE\n-- DRSDT1 DRSDT2\n-- ------- --------\n0.0005 FREE /\nAgain, the keyword parameters when applied are subject to the availability of free gas and the ability of the undersaturated oil to adsorb this gas.","expected_columns":2,"size_kind":"fixed","size_count":1},"DRSDTCON":{"name":"DRSDTCON","sections":["SCHEDULE"],"supported":null,"summary":"The DRSDTCON keyword defines the parameters that control the convective dissolution of carbon dioxide (CO2) into the in-situ brine within a grid cell, as described by Mykkeltvedt et al.1\n Mykkeltvedt, T.S., Sandve, T.H. & Gasda, S.E. New Sub-grid Model for Convective Mixing in Field-Scale CO2 Storage Simulation. Transp Porous Med 152, 9 (2025). https://doi.org/10.1007/s11242-024-02141-5, based on an assumption of vertical equilibrium. The keyword internally causes the simulator to calculate the solution gas-oil ratio (Rs), normally controlled by the DRSDT1 parameter on the DRSDT keyword in the SCHEDULE section, making the DRSDT keyword redundant.","parameters":[{"index":1,"name":"CHI","description":"A real positive value () that defines the proportionality constant related to the maximum rate of increase of CO2 solution gas-oil ratio (Rs) in the Linear regime. A value of zero means that convective dissolution of CO2 into in-situ brine does not occur and free CO2 cannot dissolve into the brine. Alternatively, a non-zero value of CHI allows convective dissolution of CO2. Note if the CO2STORE keyword is present but the DRSDTCON keyword is absent from the input deck, then this results in instantaneous dissolution of CO2 into the available undersaturated in-situ brine.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.04","value_type":"DOUBLE","dimension":"1"},{"index":1,"name":"PSI","description":"A real positive value () that defines the normalised CO2 solution gas-oil ratio ([tilde X]) at the transition between the Linear and the Steady-State regimes.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.34","value_type":"DOUBLE","dimension":"1"},{"index":1,"name":"OMEGA","description":"A real positive value () that defines the maximum rate of increase in CO2 solution gas-oil ratio (Rs) in the Steady-State regime.","units":{"field":"1/s","metric":"1/s","laboratory":"1/s"},"default":"3.0e-9","value_type":"DOUBLE","dimension":"1"},{"index":1,"name":"OPTION","description":"A defined character string that specifies in which cells the convective dissolution rate limit is applied, and should be set to one of the following character strings: ALL: the limit is applied to all cells. FREE: the limit is only applied to cells with free gas.","units":{},"default":"ALL","value_type":"DOUBLE","dimension":"1"},{"index":2,"name":"PSI","description":"","units":{},"default":"0.34","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"OMEGA","description":"","units":{},"default":"3e-09","value_type":"DOUBLE","dimension":"1"},{"index":4,"name":"OPTION","description":"","units":{},"default":"ALL","value_type":"STRING"}],"example":"The example below is similar to that shown under the CO2STORE keyword in the RUNSPEC section. In the RUNSPEC section one declares that the carbon dioxide storage model is active for the run to account for both carbon dioxide and water phase solubility using OPM Flow’s CO2-Brine PVT model.\n-- ==============================================================================\n--\n-- RUNSPEC SECTION\n--\n-- ==============================================================================\nRUNSPEC\n-- ------------------------------------------------------------------------------\n-- FLUID TYPES AND TRACER OPTIONS\n-- ------------------------------------------------------------------------------\n--\n-- ACTIVATE CO2 STORAGE IN THE MODEL (OPM FLOW CO2 STORAGE KEYWORD)\n--\nCO2STORE\n--\n-- ACTIVATE GAS-WATER THE MODEL (OPM FLOW KEYWORD)\n--\nGASWAT\n--\n-- DISSOLVED GAS IN WATER IS PRESENT IN THE RUN (OPM FLOW KEYWORD)\n--\nDISGASW\n--\n-- VAPORIZED WATER IN DRY/WET GAS IS PRESENT IN THE RUN (OPM FLOW KEYWORD)\n--\nVAPWAT\nThe second part of the example sets the maximum dissolution rate for convective CO2 mixing via the DRSDTCON keyword in the SCHEDULE section using the base case parameters calculated by Mykkeltvedt et al from fine-scale simulations.\n-- ==============================================================================\n--\n-- SCHEDULE SECTION\n--\n-- ==============================================================================\nSCHEDULE\n--\n-- CO2 CONVECTIVE DISSOLUTION PARAMETERS\n--\nDRSDTCON\n-- CHI PSI OMEGA OPTION\n0.04 0.34 3.0E-09 ALL /\nSee also the CO2STORE keyword in the RUNSPEC section for further information on OPM Flow’s CO2 storage facility.\n| [R_s``>``R_{s,sat} S_o] | (12.3.53.1) |\n|-------------------------|-------------|\n| [F_lin\n``=`` %chi left({ R_{s,sat} K_z %DELTA %rho_c g } over {%mu_o S_o`D_z%phi}right )] | (12.3.53.2) |\n|--------------------------------------------------------------------------------------------|-------------|\n| [tilde X ``=`` {R_s - R_{s,sat} S_g} over {R_{s,sat} (1-S_g)}] | (12.3.53.3) |\n|----------------------------------------------------------------|-------------|\n| Note In the commercial simulator a constant or regional value for DRSDT can be given as an input parameter. This can be used to include the effect of convective mixing as shown by Thibeau and Dutin5\n Thibeau, S., & Dutin, A. (2011). Large scale CO2 storage in unstructured aquifers: Modeling study of the ultimate CO2 migration distance. Energy Procedia, 4, 4230-4237.. Thibeau, S., & Dutin, A. (2011). Large scale CO2 storage in unstructured aquifers: Modeling study of the ultimate CO2 migration distance. Energy Procedia, 4, 4230-4237. OPM Flow’s approach differs from this in that the DRSDT value is computed internally and is dependent on both the static and dynamic cell properties. |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":4,"size_kind":"fixed"},"DRSDTR":{"name":"DRSDTR","sections":["SCHEDULE"],"supported":false,"summary":"DRSDTR defines the maximum rate at which the solution gas-oil ratio (Rs) can be increased in a grid cell for various regions in the model. The keyword is similar in functionality to the DRSDT keyword, that defines the maximum rate at which Rs can be increased in a grid cell for all cells in the model. The number of DRSDTR vector data sets is defined by the NTPVT parameter on the TABDIMS keyword in the RUNSPEC section and the allocation of the DRSDTR records to different grid blocks in the model is done via the PVTNUM keyword in the REGION section. One data set consists of one record or line which is terminated by a “/”.","parameters":[{"index":1,"name":"DRSDT1","description":"DRSDT1 is a real positive number that defines the maximum rate at which the solution gas-oil ratio is allowed to increase in a grid cell, that is the maximum rate the gas can dissolve into the available undersaturated oil. A value of zero means that Rs cannot increase and free gas cannot dissolve into the unsaturated oil in a grid cell. Alternatively a very large value of DRSDT1 allows Rs to increase rapidly until there is no free gas or the oil within the grid block is fully saturated. Note if the keyword is not present in the input deck then DRSDT1 is assumed to be a very large number resulting in complete re-solution of the gas into the available undersaturated oil.","units":{"field":"Mscf/stb/d","metric":"sm3/sm3/day","laboratory":"scc/scc/day"},"default":"None","value_type":"DOUBLE","dimension":"GasDissolutionFactor/Time"},{"index":2,"name":"DRSDT2","description":"DRSDT2 is a defined character string that defines whether the DRSDT1 is applied to either all grid blocks or just those grid blocks containing free gas: ALL: means the DRSDT1 maximum rate at which Rs is allowed to increase in a grid cell is applied to all grid blocks. FREE: means the DRSDT1 maximum rate at which Rs is allowed to increase in a grid cell is applied to grid blocks only containing free gas. Note if the keyword is not present in the input deck then DRSDT2 is set to the default value of ALL.","units":{},"default":"ALL","value_type":"STRING","options":["ALL","FREE"]}],"example":"The first example prevents the solution gas-oil ratio from increasing and applies this to all regions for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set to three.\n--\n-- SOLUTION GAS (RS) MAXIMUM RATE OF INCREASE BY REGION --\nDRSDTR\n-- MAX RS ALL/FREE\n-- DRSDT1 DRSDT2\n-- ------- --------\n0.0000 ALL /\n0.0000 ALL /\n0.0000 ALL /\nThe second example below prevents the solution gas-oil ratio from increasing and applies this to all grid cells in PVTNUM region one. For PVTNUM regions one and two the keyword applies 0.0005 Mscf/stb/d as the maximum rate at which the solution gas-oil ratio is allowed to increase in a grid cell, and applies this to only cells containing free gas.\n--\n-- SOLUTION GAS (RS) MAXIMUM RATE OF INCREASE BY REGION --\nDRSDTR\n-- MAX RS ALL/FREE\n-- DRSDT1 DRSDT2\n-- ------- --------\n0.0000 ALL /\n0.0005 FREE /\n0.0005 FREE /\nAgain, the keyword parameters when applied are subject to the availability of free gas and the ability of the undersaturated oil to adsorb this gas.","expected_columns":2,"size_kind":"fixed"},"DRVDT":{"name":"DRVDT","sections":["SCHEDULE"],"supported":null,"summary":"DRVDT defines the maximum rate at which the vaporized oil-gas ratio or condensate-gas ratio (Rv) can be increased in a grid cell. The keyword is similar in functionality to the DRVDTR keyword, that defines the maximum rate at which Rv can be increased in a grid cell by region. Both keywords should only be used if the OIL, GAS, and VAPOIL (condensate) keywords in the RUNSPEC section have been invoked to allow oil, gas and condensate to be present in the model. The keyword only affects the behavior of an increasing Rv, for example when gas is being injected into a gas condensate reservoir as part of as gas re-cycling scheme, and is subject to the availability of free oil (condensate) and the ability of the undersaturated gas to adsorb this condensate.","parameters":[{"index":1,"name":"DRVDT1","description":"DRVDT1 is a real positive number that defines the maximum rate at which the vaporized oil-gas ratio is allowed to increase in a grid cell, that is the maximum rate at which the oil can dissolve into the available undersaturated gas. A value of zero means that Rv cannot increase and free oil cannot vaporize into the unsaturated gas in a grid cell. Alternatively a very large value of DRVDT1 allows Rv to increase rapidly until there is no free oil or the gas within the grid block is fully saturated. Note if the keyword is not present in the input deck then DRVDT1 is assumed to be a very large number resulting in complete re-vaporization of the oil into the available undersaturated gas.","units":{"field":"stb/Mscf/d","metric":"sm3/sm3/day","laboratory":"scc/scc/day"},"default":"None","value_type":"DOUBLE","dimension":"OilDissolutionFactor/Time"}],"example":"The example prevents the solution oil-gas ratio from increasing.\n--\n-- VAPORIZED OIL (RV) MAXIMUM RATE OF INCREASE FOR MODEL --\nDRVDT\n-- MAX RV\n-- DRVDT1\n-- -------\n0.000 /\nAgain, the keyword parameters when applied are subject to the availability of free oil and the ability of the undersaturated gas to adsorb this oil.","expected_columns":1,"size_kind":"fixed","size_count":1},"DRVDTR":{"name":"DRVDTR","sections":["SCHEDULE"],"supported":null,"summary":"DRVDTR defines the maximum rate at which the vaporized oil-gas ratio or condensate-gas ratio (Rv) can be increased in a grid cell for various regions in the model. The keyword is similar in functionality to the DRVDT keyword, that defines the maximum rate at which Rv can be increased in a grid cell for all cells in the model. The number of DRVDTR vector data sets is defined by the NTPVT parameter on the TABDIMS keyword in the RUNSPEC section and the allocation of the DRVDTR records to different grid blocks in the model is done via the PVTNUM keyword in the REGION section. One data set consists of one record or line which is terminated by a “/”.","parameters":[{"index":1,"name":"DRVDT1","description":"DRVDT1 is a real positive number that defines the maximum rate at which the vaporized oil-gas ratio is allowed to increase in a grid cell, that is the maximum rate at which the oil can vaporize into the available undersaturated gas. A value of zero means that Rv cannot increase and free oil cannot vaporize into the unsaturated gas in a grid cell. Alternatively a very large value of DRVDT1 allows Rv to increase rapidly until there is no free oil or the gas within the grid block is fully saturated. Note if the keyword is not present in the input deck then DRVDT1 is assumed to be a very large number resulting in complete re-vaporization of the oil into the available undersaturated gas.","units":{"field":"stb/Mscf/d","metric":"sm3/sm3/day","laboratory":"scc/scc/day"},"default":"None","value_type":"DOUBLE","dimension":"OilDissolutionFactor/Time"}],"example":"The first example prevents the vaporized oil-gas ratio from increasing and applies this to all regions for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set to three.\n--\n-- VAPORIZED OIL (RV) MAXIMUM RATE OF INCREASE PARAMETERS BY REGION\n--\nDRVDTR\n-- MAX RV\n-- DRVDT1\n-- ------- -\n0.000 /\n0.000 /\n0.000 /\nThe second example below prevents the vaporized oil-gas ratio from increasing and applies this to all grid cells in PVTNUM region one. For PVTNUM regions one and two the keyword applies 0.005 stb//Mscf/d as the maximum rate at which the vaporized oil-gas ratio is allowed to increase in a grid cell,\n--\n-- VAPORIZED OIL (RV) MAXIMUM RATE OF INCREASE PARAMETERS BY REGION\n--\nDRVDTR\n-- MAX RV\n-- DRVDT1\n-- -------\n0.0000 /\n0.0005 /\n0.0005 /\nAgain, the keyword parameters when applied are subject to the availability of free oil and the ability of the undersaturated gas to adsorb this oil.","expected_columns":1,"size_kind":"fixed"},"DUMPCUPL":{"name":"DUMPCUPL","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, DUMPCUPL, activates output to the Reservoir Coupling file from the reservoir coupling file in the master run for when reservoir coupling is invoked by the GRUPMAST and SLAVES keywords in the SCHEDULE section.","parameters":[{"index":1,"name":"VALUE","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"ENDACTIO":{"name":"ENDACTIO","sections":["SCHEDULE"],"supported":null,"summary":"The ENDACTIO keyword defines the end of a series of conditions that invoke run time processing of the ACTION series of keywords, namely: ACTION, ACTIONG, ACTIONR, ACTIONS, ACTIONW and ACTIONX. Only the ACTIONX keyword is implemented in OPM Flow as this keyword implements the ACTION, ACTIONG, ACTIONR, ACTIONS, ACTIONW functionality with greater flexibility. See the ACTIONX keyword in the SCHEDULE section for a full description of the ACTION facility.","parameters":[],"example":"The example shows the use of the ACTIONX and ENDACTIO keywords to test if the field’s gas production rate is less than 600 MMscf/d after 2020 and to open up additional wells if this occurs.\n--\n-- START OF ACTIONX FIELD PHASE-2 DEVELOPMENT DEFINITION\n--\nACTIONX\nPHASE2 1 /\nGGPR 'FIELD' < 600E3 AND /\nYEAR > 2020 /\n/\n-- WELL PRODUCTION STATUS\n--\n-- WELL WELL --LOCATION-- COMPLETION\n-- NAME STAT I J K FIRST LAST\nWELOPEN\nGP10 OPEN /\nGP11 OPEN /\n/\n--\n-- END OF ACTIONX FIELD PHASE-2 DEVELOPMENT DEFINITION\n--\nENDACTIO","size_kind":"none","size_count":0},"EXCAVATE":{"name":"EXCAVATE","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, EXCAVATE, sets the status of global and LGR grid blocks to active or excavate. Excavated grid blocks have all the transmissibilities set to zero thus disabling flow between the surrounding grid blocks.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"INT"}],"example":"","size_kind":"fixed","size_count":1,"variadic_record":true},"EXIT":{"name":"EXIT","sections":["SCHEDULE"],"supported":null,"summary":"The EXIT keyword is part of OPM Flow’s ACTION facility that allows for terminating the simulation for when a condition within an ACTIONX definition is satisfied. Invoking the keyword within an ACTIONX definition will result in the simulation terminating with an exit status code. The ACTION facility allows the user to enter computational logic to the simulation run based on the how the simulation run is proceeding – see the ACTIONX keyword in the SCHEDULE section.","parameters":[{"index":1,"name":"EXITCODE","description":"An optional integer that sets the exit code printed to the *.PRT file, if not not defined the default value of zero will be used.","units":{},"default":"0","value_type":"INT"}],"example":"The first example uses the ACTIONX keyword to define a condition for when the Field Oil Production Rate (“FOPR) falls below 1,000 stb/d (or 1,000 m3) using the default value for the EXITCODE.\n--\n-- DEFINE START OF ACTIONX SECTION\n--\nACTIONX\n'CHECK_FOPR' 100000 /\nFOPR < 1000 /\n/\n--\n-- TERMINATE AND EXIT SIMULATION\n--\nEXIT\n/\nENDACTIO\nThe next example terminates the simulation with EXITCODE one when the Field Pressure (“FPR”) falls below 200 psia (or 200 barsa).\n--\n-- DEFINE START OF ACTIONX SECTION\n--\nACTIONX\n'CHECK_FPR' 100000 /\nFPR < 200 /\n/\n--\n-- TERMINATE AND EXIT SIMULATION\n--\nEXIT\n1 /\nENDACTIO\nNote is is probably good practice to always set the EXITCODE to be able to identify the reason for the simulation stopping.\n| Note This is an OPM Flow specific keyword for the simulator’s ACTION facility and will therefore cause an error if used in the commercial simulator. |\n|------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":1,"size_kind":"fixed","size_count":1},"FBHPDEF":{"name":"FBHPDEF","sections":["SCHEDULE"],"supported":null,"summary":"This keyword, FBHPDEF, defines the default well BHP target for production wells and the default BHP constraint for injection wells.","parameters":[{"index":1,"name":"TARGET_BHP","description":"A real positive value that defines the default well BHP target for production wells.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1.01325 barsa","value_type":"DOUBLE","dimension":"Pressure"},{"index":2,"name":"LIMIT_BHP","description":"A real positive value that defines the default well BHP limit for injection wells.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"6895 barsa","value_type":"DOUBLE","dimension":"Pressure"}],"example":"The following examples sets the default BHP target for production wells to 1.01325, and the default BHP limit for injection wells to 6895:\n--\n-- DEFAULT BHP TARGET AND CONSTRAINTS\n--\nFBHPDEF\n1.01325 6895. /","expected_columns":2,"size_kind":"fixed","size_count":1},"GASBEGIN":{"name":"GASBEGIN","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, GASBEGIN, defines the start of an Annual Scheduling section set of keywords used when the Gas Field Operations option has been activated by the GASFIELD keyword in the RUNSPEC section. An Annual Scheduling section starts with the GASBEGIN keyword and is terminated by the GASEND keyword, with keywords in between used to control and write reports at selected times between the start and end of a contract period. Only one Annual Scheduling section is activate at a time, that is, a subsequent Annual Scheduling section overwrites the previous set of entries. To clear the current Annual Schedule section enter the GASBEGIN keyword followed by the GASEND keyword word with no other keywords in between.","parameters":[],"example":"","size_kind":"none","size_count":0},"GASEND":{"name":"GASEND","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, GASEND, defines the end of an Annual Scheduling section set of keywords used when the Gas Field Operations option has been activated by the GASFIELD keyword in the RUNSPEC section. An Annual Scheduling section starts with the GASBEGIN keyword and is terminated by the GASEND keyword, with keywords in between used to control and write reports at selected times between the start and end of a contract period. Only one Annual Scheduling section is activate at a time, that is, a subsequent Annual Scheduling section overwrites the previous set of entries. To clear the current Annual Schedule section enter the GASBEGIN keyword followed by the GASEND keyword word with no other keywords in between.","parameters":[],"example":"","size_kind":"none","size_count":0},"GASFCOMP":{"name":"GASFCOMP","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, GASFCOMP, defines automatic gas compressors for when the Gas Field Operations option has been activated by the GASFIELD keyword in the RUNSPEC section and the Standard Network option has been specified by the GRUPTREE, GRUPNET and GNETINJE series of keywords in the SCHEDULE section. Automatic gas compressors are automatically switch on for a group if a group’s gas production target cannot be satisfied. In addition, if a group’s gas target is reduced then the automatic compressors are initially switch off to test that the reduced gas rate target can be met without compression, if not, compression is switched back on. Note that all automatic compressors are “switch on” when calculating a field’s gas deliverability.","parameters":[{"index":1,"name":"GROUP","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"VFP_TABLE_NUM","description":"","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"ARTFICIAL_LIFT_QNTY","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":4,"name":"GAS_CONSUMPTION_RATE","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"GasSurfaceVolume/Time"},{"index":5,"name":"COMPRESSION_LVL","description":"","units":{},"default":"1","value_type":"INT"},{"index":6,"name":"ACTION_SEQ_NUM","description":"","units":{},"default":"1","value_type":"INT"}],"example":"","expected_columns":6,"size_kind":"list"},"GASFDECR":{"name":"GASFDECR","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, GASFDECR, defines the field’s monthly reduction in the gas sales contract quantity for when the Gas Field Operations option has been activated by the GASFIELD keyword in the RUNSPEC section. Gas contracts are commonly based on a Daily Contract Quantity (“DCQ”) that determines the gas rate that the field should be produced at, which is normally expressed as a multiple of the DCQ, for example 1.33, and is often referred to as the “swing factor”. Some gas contracts also define a maximum DCQ (“Max DCQ”) and/or a minimum take or pay DCQ (“Min DCQ”), as well as seasonal demand characteristics. For example, gas rates may be set higher in the winter months in order to meet heating demand compared with summer months in colder climates, and the opposite in warmer climates where air conditioning demand is high.","parameters":[{"index":1,"name":"JAN","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":2,"name":"FEB","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":3,"name":"MAR","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":4,"name":"APR","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":5,"name":"MAY","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":6,"name":"JUN","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":7,"name":"JUL","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":8,"name":"AUG","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":9,"name":"SEP","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":10,"name":"OCT","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":11,"name":"NOV","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":12,"name":"DEC","description":"","units":{},"default":"0","value_type":"DOUBLE"}],"example":"| [Q sub{month}`=` DCQ times SWINGFAC sub{ month }] | (12.19) |\n|---------------------------------------------------|---------|\n| [Q sub{month}`=`left( DCQ times SWINGFAC sub{ month } right) `-`GASFDECR sub{ month}] | (12.20) |\n|---------------------------------------------------------------------------------------|---------|","expected_columns":12,"size_kind":"fixed","size_count":1},"GASFDELC":{"name":"GASFDELC","sections":["SCHEDULE"],"supported":false,"summary":"The GASFDELC keyword defines how the field’s gas deliverability calculation should be performed for when the Gas Field Operations option has been activated by the GASFIELD keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"VALUE","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"GASFTARG":{"name":"GASFTARG","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, GASFTARG, defines the field’s monthly gas sales contract quantity for when the Gas Field Operations option has been activated by the GASFIELD keyword in the RUNSPEC section. Gas contracts are commonly based on a Daily Contract Quantity (“DCQ”) that determines the gas rate that the field should be produced at, which is normally expressed as a multiple of the DCQ, for example 1.33, and is often referred to as the “swing factor”. Some gas contracts also define a maximum DCQ (“Max DCQ”) and/or a minimum take or pay DCQ (“Min DCQ”), as well as seasonal demand characteristics. For example, gas rates may be set higher in the winter months in order to meet heating demand compared with summer months in colder climates, and the opposite in warmer climates where air conditioning demand is high.","parameters":[{"index":1,"name":"JAN","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length*Length*Length/Time"},{"index":2,"name":"FEB","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length*Length*Length/Time"},{"index":3,"name":"MAR","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length*Length*Length/Time"},{"index":4,"name":"APR","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length*Length*Length/Time"},{"index":5,"name":"MAY","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length*Length*Length/Time"},{"index":6,"name":"JUN","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length*Length*Length/Time"},{"index":7,"name":"JUL","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length*Length*Length/Time"},{"index":8,"name":"AUG","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length*Length*Length/Time"},{"index":9,"name":"SEP","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length*Length*Length/Time"},{"index":10,"name":"OCT","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length*Length*Length/Time"},{"index":11,"name":"NOV","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length*Length*Length/Time"},{"index":12,"name":"DEC","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length*Length*Length/Time"}],"example":"| [Q sub{month}`=` DCQ times SWINGFAC sub{ month }] | (12.21) |\n|---------------------------------------------------|---------|\n| [Q sub{month}`=` Minimum `left( left(DCQ times SWINGFAC sub{ month } right) ,`GASFTARG sub{ month} right)] | (12.22) |\n|------------------------------------------------------------------------------------------------------------|---------|","expected_columns":12,"size_kind":"fixed","size_count":1},"GASMONTH":{"name":"GASMONTH","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, GASMONTH, states the month for which subsequent scheduling events take place within an Annual Schedule section for when the Gas Field Operations option has been activated by the GASFIELD keyword in the RUNSPEC section. The keyword must lie in between the GASBEGIN, that defines the start of an Annual Scheduling section and the GASEND keyword that ends the section. Optionally, the keyword can be used to write a report to the print file (*.PRT) at the requested month.","parameters":[{"index":1,"name":"MONTH","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"WRITE_REPORT","description":"","units":{},"default":"NO","value_type":"STRING"}],"example":"","expected_columns":2,"size_kind":"fixed","size_count":1},"GASPERIO":{"name":"GASPERIO","sections":["SCHEDULE"],"supported":false,"summary":"This keyword advances the simulation over one or more gas contract periods for when the Gas Field Operations option has been activated by the GASFIELD keyword in the RUNSPEC section. A contract period in this case is the period over which the Daily Contract Quantity is fixed, this can a be year or one or more months. If the contract period is a year then the GASYEAR keyword in the SCHEDULE section can be used instead of GASPERIOD.","parameters":[{"index":1,"name":"NUM_PERIODS","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"NUM_MONTHS","description":"","units":{},"default":"12","value_type":"INT"},{"index":3,"name":"INITIAL_DCQ","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":4,"name":"SWING_REQ","description":"","units":{},"default":"PER","value_type":"STRING"},{"index":5,"name":"LIMIT_TIMESTEPS","description":"","units":{},"default":"YES","value_type":"STRING"},{"index":6,"name":"LIMIT_DCQ_RED_FACTOR","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"1"},{"index":7,"name":"ANTICIPATED_DCQ_RED_FACTOR","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"},{"index":8,"name":"MAX_ITERATIONS","description":"","units":{},"default":"3","value_type":"INT"},{"index":9,"name":"DCQ_CONV_TOLERANCE","description":"","units":{},"default":"0.1","value_type":"DOUBLE","dimension":"1"}],"example":"","expected_columns":9,"size_kind":"fixed","size_count":1},"GASYEAR":{"name":"GASYEAR","sections":["SCHEDULE"],"supported":false,"summary":"This keyword advances the simulation over one or more gas contract years for when the Gas Field Operations option has been activated by the GASFIELD keyword in the RUNSPEC section. A contract year in this case is the period over which the Daily Contract Quantity is fixed, this can a be year, this keyword or the GASPERIO keyword in the SCHEDULE section, or one or more months. If the contract period is over one or more months then the GASPERIO keyword in the SCHEDULE section can be used instead of GASYEAR.","parameters":[{"index":1,"name":"NUM_YEARS","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"INITIAL_DCQ","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":3,"name":"SWING_REQ","description":"","units":{},"default":"YEAR","value_type":"STRING"},{"index":4,"name":"LIMIT_TIMESTEPS","description":"","units":{},"default":"YES","value_type":"STRING"},{"index":5,"name":"LIMIT_DCQ_RED_FACTOR","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"1"},{"index":6,"name":"ANTICIPATED_DCQ_RED_FACTOR","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"},{"index":7,"name":"MAX_ITERATIONS","description":"","units":{},"default":"3","value_type":"INT"},{"index":8,"name":"DCQ_CONV_TOLERANCE","description":"","units":{},"default":"0.1","value_type":"DOUBLE","dimension":"1"}],"example":"","expected_columns":8,"size_kind":"fixed","size_count":1},"GCALECON":{"name":"GCALECON","sections":["SCHEDULE"],"supported":false,"summary":"The GCALECON keyword defines economic criteria for production groups, including the field level group FIELD, that have previously been defined by the GCONPROD keyword in the SCHEDULE section and have had their rate targets and constraints set by calorific value via the GCONVAL keyword in the SCHEDULE section.","parameters":[{"index":1,"name":"GRPNAME","description":"A character string of up to eight characters in length that defines the group name for which the group target and constraints are being defined. The group named FIELD is the top most group and should be used to set targets and constraints for the field. Note that the group hierarchy should be defined by the GRUPTREE keyword when there is more than one level of groups, otherwise all the groups will sit directly under the FIELD group in the group tree hierarchy.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"ENEVAL","description":"A real positive value that defines the minimum economic surface energy production rate, below which an economic action of shutting in or stopping all the wells in the group, as requested by item (9) of the WELSPECS keyword. A value less than or equal to zero switches of this criteria.","units":{"field":"BTU/day","metric":"kJ/day","laboratory":"J/hour"},"default":"0.0","value_type":"DOUBLE","dimension":"Energy/Time"},{"index":3,"name":"CALVAL","description":"A real positive value that defines the minimum economic surface calorific value, below which an economic action of shutting in or stopping all the wells in the group, as requested by item (9) of the WELSPECS keyword. A value less than or equal to zero switches of this criteria,","units":{"field":"Btu/Mscf","metric":"kJ/sm3","laboratory":"J/scc"},"default":"0.0","value_type":"DOUBLE","dimension":"Energy/GasSurfaceVolume"},{"index":4,"name":"FLAG_END_RUN","description":"","units":{},"default":"NO","value_type":"STRING"},{"index":8,"name":"END","description":"A defined character string that defines if the simulation should terminate if all the producing wells in the group, including the FIELD group, are shut or stopped. END should be set to one of the following character strings: NO: no action is taken and the run continues. YES: terminate the run at the next report time step.","units":{},"default":"NO"}],"example":"The following example defines the economic criteria for the field with a minimum economic surface energy production rate of 5 x 109 BTU/day and a minimum economic surface calorific value of900 Btu/Mscf\n--\n-- GROUP ECONOMIC CRITERIA FOR PRODUCTION GROUPS UNDER CALORIFIC CONTROL\n--\n-- GRUP ENERGY CALORIFIC END\n-- NAME RATE VALUE RUN\nGCALECON\nFIELD 5E9 900.0 'YES' /\n/\nIf the economic limits are violated then the run will stop at the next report time step.","expected_columns":4,"size_kind":"list"},"GCONCAL":{"name":"GCONCAL","sections":["SCHEDULE"],"supported":false,"summary":"The GCONCAL keyword defines calorific production targets and constraints for groups, including the top most group in the group hierarchy known as the FIELD group. Wells are allocated to groups when the wells are specified by the WELSPECS keyword in the SCHEDULE section. Wells defined to be under group control will have their production rates controlled by the group to which they belong, in addition to any well constraints defined for the wells.","parameters":[{"index":1,"name":"GRPNAME","description":"A character string of up to eight characters in length that defines the group name for which the group’s target calorific value is being defined. The group named FIELD is the top most group and should be used to set targets and constraints for the field. Note that the group hierarchy should be defined by the GRUPTREE keyword when there is more than one level of groups, otherwise all the groups will sit directly under the FIELD group in the group tree hierarchy.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"CALVAL","description":"A real positive value that defines the target surface calorific value of the produced gas. The default value of 1 x 1020 switches off calorific control for the group.","units":{"field":"Btu/Mscf","metric":"kJ/sm3","laboratory":"J/hour"},"default":"1.0 x 1020","value_type":"DOUBLE","dimension":"Energy/GasSurfaceVolume"},{"index":3,"name":"ACTION","description":"A defined character string that defines the action to be taken if the CALVAL is violated. ACTION should be set to one of the following character strings: NONE: no action is taken and the group’s produced calorific value will therefore no longer meet CALVAL. RATE: scale back the gas rate of various wells under the group by the value of FACTOR until the calorific target (CALVAL) is satisfied. The corrective action takes places at the end of the time step in which the constraint is violated.","units":{},"default":"None","value_type":"STRING","options":["NONE","RATE"]},{"index":4,"name":"FACTOR","description":"A real positive value that is less than or equal to one that defines the amount wells can be scaled back in order to satisfy CALVAL. Note this assumes that there are wells within the group that are producing with higher and lower calorific values, and the simulator is thus able to fine a combination of wells that satisfy the group’s CALVAL target.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":"1"}],"example":"The following example defines the calorific production target for the field.\n---\n-- GROUP CALORIFIC PRODUCTION CONTROLS\n--\n-- GRUP CALORIFIC ACTION CUT\n-- NAME VALUE BACK\nGCONCAL\nFIELD 1010E3 RATE 0.95 /\n/\nHere the calorific production target has been set to 1,010 x 103 Btu/Mscf for the field and if the target cannot be met then the well rates are reduced by 0.95 at each iteration until the target is satisfied.","expected_columns":4,"size_kind":"list"},"GCONENG":{"name":"GCONENG","sections":["SCHEDULE"],"supported":false,"summary":"The GCONCAL keyword defines energy production targets and constraints for groups, including the top most group in the group hierarchy known as the FIELD group. Wells are allocated to groups when the wells are specified by the WELSPECS keyword in the SCHEDULE section. Wells defined to be under group control will have their production rates controlled by the group to which they belong, in addition to any well constraints defined for the wells.","parameters":[{"index":1,"name":"GRPNAME","description":"A character string of up to eight characters in length that defines the group name for which the group’s target calorific value is being defined. The group named FIELD is the top most group and should be used to set targets and constraints for the field. Note that the group hierarchy should be defined by the GRUPTREE keyword when there is more than one level of groups, otherwise all the groups will sit directly under the FIELD group in the group tree hierarchy.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"ENGVAL","description":"A real positive value that defines the surface energy target for the group. The default value of 1 x 1020 switches off the energy target for the group.","units":{"field":"BTU/day","metric":"kJ/day","laboratory":"J/hour"},"default":"1.0 x 1020","value_type":"DOUBLE","dimension":"Energy/Time"}],"example":"The following example defines the energy production target for the field.\n--\n-- GROUP ENERGY PRODUCTION CONTROLS\n--\n-- GRUP ENERGY\n-- NAME VALUE\nGCONENG\nFIELD 1010E9 /\n/\nHere the energy production target has been set to 1,010 x 109 Btu/day for the field.","expected_columns":2,"size_kind":"list"},"GCONINJE":{"name":"GCONINJE","sections":["SCHEDULE"],"supported":null,"summary":"The GCONINJE keyword defines injection targets and constraints for groups, including the top most group in the group hierarchy known as the FIELD group. Wells are allocated to groups when the wells are specified by the WELSPECS keyword in the SCHEDULE section. Wells defined to be under group control will have their injection rates controlled by the group to which they belong, in addition to any well constraints defined for the wells.","parameters":[{"index":1,"name":"GRPNAME","description":"A character string of up to eight characters in length that defines the group name for which the group target and constraints are being defined. The group named FIELD is the top most group and should be used to set targets and constraints for the whole field. Note that the group hierarchy should be defined by the GRUPTREE keyword in the SCHEDULE, when there is more than one level of groups, otherwise all the groups will sit directly under the FIELD group in the group tree hierarchy.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"TYPE","description":"A defined character string that defines the type of injection fluid. TYPE should be set to one of the following character strings: GAS: for a gas injection well. OIL: for a water injection well. WAT: for a water injection well.","units":{},"default":"None","value_type":"STRING","options":["GAS","OIL","WAT"]},{"index":3,"name":"TARGET","description":"A defined character string that sets the target injection control for the group, all the other phases will therefore act as constraints. The simulator will attempt to meet the TARGET based on the phase rate stated in items (4) to (7) on this keyword. TARGET should be set to one of the following character strings: NONE: the group has no target phase, but if entered, constraints are still defined and active. FLD: this group is controlled from a higher level group, including the FIELD group. RATE: the injection phase will be control by the surface fluid rate for the phase defined by the TYPE variable. For example, if TYPE has been set to WAT then this would mean the water injection rate as defined by item (4). RESV: the target is set to the in situ reservoir volume rate as defined by item (5). REIN: the target is set to the group's production of the phase defined by TYPE multiplied by the value on item (6). For example, if TYPE has been set to WAT then this would mean the group's water production multiplied by item (6). VREP: the target is set to the group's voidage replacement ratio as defined by item (7).","units":{},"default":"None","value_type":"STRING","options":["NONE","FLD","RATE","RESV","REIN","VREP"]},{"index":4,"name":"RATE","description":"A real positive value that defines the maximum surface injection rate target or constraint for the phase declared by the TYPE variable. This value may be specified using a User Defined Argument (UDA).","units":{"field":"Liquid stb/d Gas Mscf/d","metric":"Liquid sm3/day Gas sm3/day","laboratory":"Liquid scc/hour Gas scc/hour"},"default":"None","value_type":"UDA"},{"index":5,"name":"RESV","description":"A real positive value that defines the maximum reservoir volume injection rate target or constraint. This value may be specified using a User Defined Argument (UDA). Note setting a value here other than the default means that TYPE, item (2) will be the supplement or “make up” phase.","units":{"field":"rtb/d","metric":"rm3/day","laboratory":"rcc/hour"},"default":"None","value_type":"UDA","dimension":"ReservoirVolume/Time"},{"index":6,"name":"REIN","description":"A real positive value that defines the target or constraint re-injection fraction for the produced phase defined by the TYPE variable. This value may be specified using a User Defined Argument (UDA). For example, if TYPE is equal to GAS and REIN is equal to 0.85, then 85% of the produced gas will be re-injected.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"UDA","dimension":"1"},{"index":7,"name":"VREP","description":"A real positive value that defines the target or constraint of the voidage replacement ratio based on all the produced fluids. This value may be specified using a User Defined Argument (UDA). For example, if TYPE is equal to WAT and VREP is equal to 1.00, then 100% of the produced reservoir volume will be re-inject as an equivalent water volume. Note setting a value here other than the default means that TYPE, item (2) will be the supplement phase.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"UDA","dimension":"1"},{"index":8,"name":"GRPCNTL","description":"A defined character string that determines if this group is subject to higher level group control. YES: then this group is subject to a higher level group’s control and the flow rates for this group will be adjusted accordingly. NO: then this group is NOT subject to a higher level group’s control and the flow rates for this group will only be controlled by the parameters for this group. This variable is ignored if GRPNAME is equal to FIELD.","units":{},"default":"YES","value_type":"STRING","options":["YES","NO"]},{"index":9,"name":"GRPGUIDE","description":"A real positive value that defines a group's injection guide rate expressed as a dimensionless number. A group requires a value for GRPGUIDE only if it is required to produce a specified proportion of a higher level group’s rate. Defaulting GRPGUIDE results in the subordinate groups and wells under guide control having their rates dictated by any higher level groups under guide rate control. In other words the GRPNAME is masked out. Setting GRPGUIDE to a real positive value and GUIPHASE to either RATE or RESV will result in a constant injection guide rate.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":"1"},{"index":10,"name":"GUIPHASE","description":"A defined character string that sets the guide phase to which the guide rate in item (9) applies. GUIPHASE should be set to one of the following character strings: NETV: the guide phase is set to production rate minus any injected reservoir rate from the other phases. The net volume is calculated at the beginning of a time step and the option should only be used for groups under voidage replacement control. Note that using this option means that TYPE, item (2) will be the supplement or “make up” phase and the value entered for the group's guide rate (GRPGUIDE) will be ignored with this option. RATE: the guide phase is set to the surface injection rate. Setting GUIPHASE to RATE and GRPGUIDE to a real positive value will result in a constant injection guide rate. RESV: the guide phase is set to the in situ reservoir volume rate. Setting GUIPHASE to RESV and GRPGUIDE to a real positive value will result in a constant injection guide rate. VOID: the guide rate is calculated at the beginning of each time step based on the group’s net voidage rate. OPM Flow now supports all guide rate options. The default value of 1* means that the group has no injection guide rate for this phase.","units":{},"default":"None","value_type":"STRING","options":["NETV","RATE","RESV","VOID"]},{"index":11,"name":"GRPREIN","description":"A character string of up to eight characters in length that defines the group name whose production rate should be used for applying the REIN quantity to be injected into GRPNAME. This variable is used to re-inject the REIN production faction from another group (GRPREIN) via this group (GRPNAME). If GRPREIN is defaulted then the re-injection quantity for GRPNAME will be based on the production from GRPNAME itself.","units":{},"default":"GRPNAME","value_type":"STRING"},{"index":12,"name":"GRPVREP","description":"A character string of up to eight characters in length that defines the group name whose production rate should be used for applying the VREP quantity to be injected into GRPNAME. This variable is used to re-inject the VREP production faction from another group (GRPVREP) via this group (GRPNAME). If GRPVREP is defaulted then the voidage quantity for GRPNAME will be based on the production from GRPNAME itself.","units":{},"default":"GRPNAME","value_type":"STRING"},{"index":13,"name":"WGASRATE","description":"Wet gas injection rate used in the commercial compositional simulator. Not used and should be defaulted with 1*.","units":{},"default":"1*","value_type":"DOUBLE","dimension":"GasSurfaceVolume/Time"}],"example":"The following example defines the injection targets and constraints for the field and two groups that are one level below the field group, since the GRUPTREE keyword has not been entered to define the group hierarchy.\n--\n-- GROUP INJECTION TARGETS AND CONSTRAINTS\n--\n-- GRUP FLUID CNTL SURF RESV REINJ VOID GRUP GUIDE GUIDE GRUP GRUP\n-- NAME TYPE MODE RATE RATE FRAC FRAC CNTL RATE DEF REINJ RESV\nGCONINJE\nFIELD WAT VREP 35E3 1* 1* 1* NO 1* 1* 1* 1* /\nGRP01 WAT VREP 1* 1* 1* 1.0 YES 1* 1* 1* 1* /\nGRPO2 WAT VREP 1* 1* 1* 1.0 YES 1* 1* 1* 1* /\n/\nIn this example, group GRP01 and GRP02 are injecting water via voidage replacement with a voidage replacement of one and are under the control on the field group, that imposes a 35,000 m3/day total water injection limit.","expected_columns":13,"size_kind":"list"},"GCONPRI":{"name":"GCONPRI","sections":["SCHEDULE"],"supported":false,"summary":"The GCONPRI keyword defines production targets and constraints for groups, including the top most group in the group hierarchy known as the FIELD group, for when groups and their associated wells are operating under priority control as oppose to guide rate control. Priority control is activated by the PRIORITY keyword in the SCHEDULE section. Wells are allocated to groups when the wells are specified by the WELSPECS keyword in the SCHEDULE section. Wells defined to be under group control will have their production rates controlled by the group to which they belong, in addition to any well constraints defined for the wells.","parameters":[{"index":1,"name":"GRPNAME","description":"A character string of up to eight characters in length that defines the group name for which the group target and constraints are being defined. The group named FIELD is the top most group and should be used to set targets and constraints for the field. Note that the group hierarchy should be defined by the GRUPTREE keyword when there is more than one level of groups, otherwise all the groups will sit directly under the FIELD group in the group tree hierarchy.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"ORAT","description":"A real positive value that defines the maximum surface oil production rate constraint. This value may be specified using a User Defined Argument (UDA).","units":{"field":"stb/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"None","value_type":"UDA","dimension":"LiquidSurfaceVolume/Time"},{"index":3,"name":"OILACT","description":"A defined character string that defines the action to be taken if ORAT is exceeded. OILACT should be set to one of the following character strings: NONE: no action is taken. CON: close the worst offending connection in the worst offending well. If connections have been grouped as completions then the worst offending completion in the worst offending well will be closed. +CON: close the worst offending connection and all below it in the worst offending well. If connections have been grouped as completions then the worst offending completion and all below it in the worst offending well will be closed. WELL: close the worst offending well. PLUG: plug back the worst offending well based on the plug back length and options defined on the WPLUG keyword in the SCHEDULE. PRI: control the group production rate using the first priority formulae defined by the PRIORITY keyword in the SCHEDULE section. PR2: control the group production rate using the second priority formulae defined by the PRIORITY keyword in the SCHEDULE section.","units":{},"default":"“NONE”","value_type":"STRING","options":["NONE","CON","WELL","PLUG","PRI","PR2"]},{"index":4,"name":"WRAT","description":"A real positive value that defines the maximum surface water production rate constraint. This value may be specified using a User Defined Argument (UDA).","units":{"field":"stb/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"None","value_type":"UDA","dimension":"LiquidSurfaceVolume/Time"},{"index":5,"name":"WATACT","description":"A defined character string that defines the action to be taken if WRAT is exceeded. WATACT should be set to a character string described by the OILACT parameter on this record.","units":{},"default":"None","value_type":"STRING"},{"index":6,"name":"GRAT","description":"A real positive value that defines the maximum surface gas production rate constraint This value may be specified using a User Defined Argument (UDA).","units":{"field":"Mscf/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"None","value_type":"UDA","dimension":"GasSurfaceVolume/Time"},{"index":7,"name":"GASACT","description":"A defined character string that defines the action to be taken if GRAT is exceeded. GASACT should be set to a character string described by the OILACT parameter on this record.","units":{},"default":"None","value_type":"STRING"},{"index":8,"name":"LRAT","description":"A real positive value that defines the maximum surface liquid (oil plus water) production rate constraint. This value may be specified using a User Defined Argument (UDA).","units":{"field":"stb/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"None","value_type":"UDA","dimension":"LiquidSurfaceVolume/Time"},{"index":9,"name":"LIQACT","description":"A defined character string that defines the action to be taken if LRAT is exceeded. LIQACT should be set to a character string described by the OILACT parameter on this record.","units":{},"default":"None","value_type":"STRING"},{"index":10,"name":"RESV","description":"A real positive value that defines the maximum reservoir volume production rate constraint. This value may be specified using a User Defined Argument (UDA).","units":{"field":"rb/d","metric":"rm3/day","laboratory":"rcc/hour"},"default":"None","value_type":"UDA","dimension":"ReservoirVolume/Time"},{"index":11,"name":"RESVFRAC","description":"A real positive value that defines a group's maximum production balancing fraction constraint. This value may be specified using a User Defined Argument (UDA).","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"UDA","dimension":"1"},{"index":12,"name":"","description":"Not used should be defaulted with 1*.","units":{},"default":"1*","value_type":"UDA","dimension":"GasSurfaceVolume/Time"},{"index":13,"name":"","description":"Not used should be defaulted with 1*.","units":{},"default":"1*","value_type":"STRING"},{"index":14,"name":"","description":"Not used should be defaulted with 1*.","units":{},"default":"1*","value_type":"UDA","dimension":"1"},{"index":15,"name":"","description":"Not used should be defaulted with 1*.","units":{},"default":"1*","value_type":"UDA","dimension":"1"},{"index":16,"name":"LINCOMB","description":"A real positive value that defines the linearly combined maximum surface target rate or constraint, as per the LINCOM keyword in the SCHEDULE section.","units":{},"default":"1*","value_type":"UDA"},{"index":17,"name":"LINACT","description":"A defined character string that defines the action to be taken if LINCOMB is exceeded. LINACT should be set to a character string described by the OILACT parameter on this record.","units":{},"default":"None","value_type":"STRING"}],"example":"The following example defines the production targets and constraints for the field and two groups that are one level below the field group, since the GRUPTREE keyword has not been entered to define the group hierarchy.\n--\n-- GROUP PRIORITY PRODUCTION CONTROLS\n--\n-- GRUP ORAT ORAT WRAT WRAT GRAT GRAT LRAT LRAT RVOL RVOL\n-- NAME LIMT ACTN LIMT ACTN LIMT ACTN LIMT ACTN LIMT ACTN\nGCONPRI\nFIELD 40E3 PRI 30E3 +CON 125E3 PRI 1* 1* 1* 1* /\nGRP01 25E3 PRI 1* 1* 1* 1* 1* 1* 1* 1* /\nGRP02 25E3 PRI 1* 1* 1* 1* 1* 1* 1* 1* /\n/\nAll groups are controlled by oil constraints, but only the field level has water and gas constraints to reflect the actual production facility constraints. The oil production constraint of 40,000, 25,000 and 25,000 stb/d are defined for the field, GRP01 and GRP02 groups, respectively. If the oil rate constraint is exceeded then the wells will be controlled using the priority formulae one, as defined on the PRIORITY keyword in the SCHEDULE section. Similarly for the field, for when the gas constraint is exceeded. Finally, if the field water constraint is surpassed then the worst offending connection and below in the worst offending well are shut.","expected_columns":17,"size_kind":"list"},"GCONPROD":{"name":"GCONPROD","sections":["SCHEDULE"],"supported":true,"summary":"The GCONPROD keyword defines production targets and constraints for groups, including the top most group in the group hierarchy known as the FIELD group. Wells are allocated to groups when the wells are specified by the WELSPECS keyword in the SCHEDULE section. Wells defined to be under group control will have their production rates controlled by the group to which they belong, in addition to any well constraints defined for the wells.","parameters":[{"index":1,"name":"GRPNAME","description":"A character string of up to eight characters in length that defines the group name for which the group target and constraints are being defined. The group named FIELD is the top most group and should be used to set targets and constraints for the field. Note that the group hierarchy should be defined by the GRUPTREE keyword in the SCHEDULE section, when there is more than one level of groups, otherwise all the groups will sit directly under the FIELD group in the group tree hierarchy.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"TARGET","description":"A defined character string that specifies the production rate control mode for the group. The simulator will attempt to meet the TARGET rate as defined by remaining items on this keyword. TARGET should be set to one of the following character strings: NONE: the group has no target rate, but if entered, constraints are still defined and active. FLD: this group is controlled by a higher level group (including the FIELD group) subject to its guide rate as defined by items (9) and (10). ORAT: the target is set to the surface oil production rate as defined by item (3). WRAT: the target is set to the surface water production rate as defined by item (4). GRAT: the target is set to the surface gas production rate as defined by item (5). LRAT: the target is set to the surface liquid (oil plus water) production rate as defined by item (6). RESV: the target is set to the in situ reservoir volume rate as defined by item (14). Note that the commercial simulator includes additional options (not listed above) that are not currently supported by OPM Flow.","units":{},"default":"None","value_type":"STRING","options":["NONE","FLD","ORAT","WRAT","GRAT","LRAT","RESV"]},{"index":3,"name":"ORAT","description":"A real positive value that defines the maximum surface oil production rate target or constraint. This value may be specified using a User Defined Argument (UDA).","units":{"field":"stb/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"None","value_type":"UDA","dimension":"LiquidSurfaceVolume/Time"},{"index":4,"name":"WRAT","description":"A real positive value that defines the maximum surface water production rate target or constraint. This value may be specified using a User Defined Argument (UDA).","units":{"field":"stb/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"None","value_type":"UDA","dimension":"LiquidSurfaceVolume/Time"},{"index":5,"name":"GRAT","description":"A real positive value that defines the maximum surface gas production rate target or constraint. This value may be specified using a User Defined Argument (UDA).","units":{"field":"Mscf/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"None","value_type":"UDA","dimension":"GasSurfaceVolume/Time"},{"index":6,"name":"LRAT","description":"A real positive value that defines the maximum surface liquid (oil plus water) production rate target or constraint. This value may be specified using a User Defined Argument (UDA).","units":{"field":"stb/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"None","value_type":"UDA","dimension":"LiquidSurfaceVolume/Time"},{"index":7,"name":"ACTION","description":"A defined character string that specifies the action to be taken if the constraints in (3) to (6) are violated. ACTION should be set to one of the following character strings: NONE: no action is taken. CON: close the worst offending connection in the worst offending well. If connections have been grouped as completions then the worst offending completion in the worst offending well will be closed. +CON: close the worst offending connection and all below it in the worst offending well. If connections have been grouped as completions then the worst offending completion and all below it in the worst offending well will be closed. WELL: close the worst offending well. PLUG: plug back the worst offending well. RATE: control the group production rate to equal the upper limit. This effectively changes the TARGET to be the violated phase constraint. The corrective action takes places at the end of the time step in which the constraint is violated. Note that only the NONE, WELL and RATE options are currently supported by OPM Flow.","units":{},"default":"None","value_type":"STRING","options":["NONE","CON","WELL","PLUG","RATE"]},{"index":8,"name":"GRPCNTL","description":"A defined character string that determines if this group is subject to higher level group control. YES: then this group is subject to a higher level group’s control and the flow rates for this group will be adjusted accordingly. NO: then this group is NOT subject to a higher level group’s control and the flow rates for this group will only be controlled by the parameters for this group. GRPCNTL will be ignored for the FIELD group.","units":{},"default":"None","value_type":"STRING","options":["YES","NO"]},{"index":9,"name":"GRPGUIDE","description":"A real positive value that defines a group's production guide rate expressed as a dimensionless number. A group requires a value for GRPGUIDE only if it is required to produce a specified proportion of a higher level group’s rate","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE"},{"index":10,"name":"GUIPHASE","description":"A defined character string that sets the guide phase to which the guide rate in item (9) applies. GUIPHASE should be set to one of the following character strings: OIL: the guide phase is set to oil. WAT: the guide phase is set to water. GAS: the guide phase is set to gas. LIQ: the guide phase is set to liquid (oil plus water). COMB: the guide phase is set to a linear combination of phases with the coefficients specified by the LINCOM keyword in the SCHEDULE section. INJV: the guide rate is set to the group’s reservoir volume injection rate at the start of each timestep. POTN: the guide rate is set to the group’s production potential at the start of each timestep. FORM: the guide rate will be based on the formulae defined via the GUIDERAT keyword in the SCHEDULE section. The formulae enables subordinate groups and wells to decrease their contribution from wells producing too much gas or too much water. ' ' or 1* : the group is not under guide rate control, and therefore superordinate group production targets will be pro-rated directly down to its subordinate groups and wells. Note that only the OIL, WAT, GAS, LIQ and default options are currently supported by OPM Flow.","units":{},"default":"1*","value_type":"STRING","options":["OIL","WAT","GAS","LIQ","COMB","INJV","POTN","FORM"]},{"index":11,"name":"ACTWAT","description":"A defined character string that defines the action to be taken if the WRAT constraint, item (4), is violated. ACTWAT should be set to one of the following character strings: NONE: no action is taken. CON: close the worst offending connection in the worst offending well. If connections have been grouped as completions then the worst offending completion in the worst offending well will be closed. +CON: close the worst offending connection and all below it in the worst offending well. If connections have been grouped as completions then the worst offending completion and all below it in the worst offending well will be closed. WELL: close the worst offending well. PLUG: plug back the worst offending well. This option is not implemented in OPM Flow. RATE: control the group production rate to equal the upper limit. This effectively changes the TARGET to be the violated phase constraint. If defaulted then procedure defined by ACTION, item (7), is applied. The corrective action takes places at the end of the time step in which the constraint is violated. Note that only the NONE and RATE options are currently supported by OPM Flow.","units":{},"default":"1*","value_type":"STRING","options":["NONE","CON","WELL","PLUG","RATE"]},{"index":12,"name":"ACTGAS","description":"A defined character string that defines the action to be taken if the GRAT constraint, item (5), is violated. ACTGAS should be set to one of the following character strings: NONE: no action is taken. CON: close the worst offending connection in the worst offending well. If connections have been grouped as completions then the worst offending completion in the worst offending well will be closed. +CON: close the worst offending connection and all below it in the worst offending well. If connections have been grouped as completions then the worst offending completion and all below it in the worst offending well will be closed. WELL: close the worst offending well. PLUG: plug back the worst offending well. RATE: control the group production rate to equal the upper limit. This effectively changes the TARGET to be the violated phase constraint. If defaulted then procedure defined by ACTION, item (7), is applied. The corrective action takes places at the end of the time step in which the constraint is violated Note that only the NONE and RATE options are currently supported by OPM Flow.","units":{},"default":"1*","value_type":"STRING","options":["NONE","CON","WELL","PLUG","RATE"]},{"index":13,"name":"ACTLIQ","description":"A defined character string that defines the action to be taken if the LRAT constraint, item (6), is violated. ACLIQT should be set to one of the following character strings: NONE: no action is taken. CON: close the worst offending connection in the worst offending well. If connections have been grouped as completions then the worst offending completion in the worst offending well will be closed. +CON: close the worst offending connection and all below it in the worst offending well. If connections have been grouped as completions then the worst offending completion and all below it in the worst offending well will be closed. WELL: close the worst offending well. PLUG: plug back the worst offending well. This option is not implemented in OPM Flow. RATE: control the group production rate to equal the upper limit. This effectively changes the TARGET to be the violated phase constraint. If defaulted then procedure defined by ACTION, item (7), is applied. The corrective action takes places at the end of the time step in which the constraint is violated. Note that only the NONE and RATE options are currently supported by OPM Flow.","units":{},"default":"1*","value_type":"STRING","options":["NONE","CON","WELL","PLUG","RATE"]},{"index":14,"name":"RESV","description":"A real positive value that defines the maximum reservoir volume production rate target or constraint. This value may be specified using a User Defined Argument (UDA).","units":{"field":"rb/d","metric":"rm3/day","laboratory":"rcc/hour"},"default":"None","value_type":"UDA","dimension":"ReservoirVolume/Time"},{"index":15,"name":"RESVFRAC","description":"A real positive value that defines the maximum reservoir volume production balancing fraction. Not used and should be defaulted with 1*.","units":{},"default":"1*","value_type":"DOUBLE","dimension":"1"},{"index":16,"name":"WGASRATE","description":"Wet gas production rate used in the commercial compositional simulator. Not used and should be defaulted with 1*.","units":{},"default":"1*","value_type":"DOUBLE","dimension":"1"},{"index":17,"name":"CALRATE","description":"Calorific production rate used in the commercial compositional simulator. Not used and should be defaulted with 1*.","units":{},"default":"1*","value_type":"DOUBLE"},{"index":18,"name":"GASFRAC","description":"Surface gas production fraction used in the commercial compositional simulator Not used and should be defaulted with 1*.","units":{},"default":"1*","value_type":"DOUBLE"},{"index":19,"name":"WATFRAC","description":"Surface water production fraction used in the commercial compositional simulator. Not used and should be defaulted with 1*.","units":{},"default":"1*","value_type":"DOUBLE"},{"index":20,"name":"COMBRATE","description":"Linearly combined production rate used in the commercial compositional simulator. Not used and should be defaulted with 1*.","units":{},"default":"1*","value_type":"DOUBLE"},{"index":21,"name":"COMBPROC","description":"Linearly combined procure for when exceeding COMBRATE, used in the commercial black-oil simulator. Not used and should be defaulted with 1*.","units":{},"default":"1*","value_type":"STRING"}],"example":"The following example defines the production targets and constraints for the field and two groups that are one level below the field group, since the GRUPTREE keyword has not been entered to define the group hierarchy.\n--\n-- GROUP PRODUCTION CONTROLS\n--\n-- GRUP CNTL OIL WAT GAS LIQ CNTL GRUP GUIDE GUIDE CNTL\n-- NAME MODE RATE RATE RATE RATE OPT CNTL RATE DEF WAT\nGCONPROD\nFIELD ORAT 40E3 60E3 300E3 60E3 1* 1* 1* 1* 1* /\nGRP01 FLD 25E3 1* 1* 1* 1* 1* 1* 1* 1* /\nGRP02 FLD 25E3 1* 1* 1* 1* 1* 1* 1* 1* /\n/\nAll groups are controlled by oil rate targets or constraints, but only the field level has water, gas and liquid constraints to reflect the actual production facility constraints. The wells under group control will be produced based on oil potential of each of the wells under group control, such that the field oil production target of 40,000 stb/d is honored and subject to the other phase fluid constraints. In addition, GRP01 and GRP02 oil rate values of 25,000 stb/d are constraints as these two groups are subject to the FIELD level targets and constraints.","expected_columns":21,"size_kind":"list"},"GCONSALE":{"name":"GCONSALE","sections":["SCHEDULE"],"supported":null,"summary":"GCONSALE defines group sales gas production targets and constraints for when the gas production from an oil field group is exported under a Gas Sales Agreement (“GSA”) and the oil field group also has oil production targets and constraints.","parameters":[{"index":1,"name":"GRPNAME","description":"A character string of up to eight characters in length that defines the group name for which the group gas sales target and constraints are being defined. The group named FIELD is the top most group and should be used to set the gas sales targets and constraints for the field. Note that the group hierarchy should be defined by the GRUPTREE keyword when there is more than one level of groups, otherwise all the groups will sit directly under the FIELD group in the group tree hierarchy.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"GSALE","description":"GSALE should either be set to: A real positive value that defines the gas sales rate for the group, or, A real negative value that switches off both gas sales and gas re-injection for the group. This value may be specified using a User Defined Argument (UDA). Note that if GSALE has been set to switch off both gas sales and gas re-injection, then the GCONINJE keyword in the SCHEDULE section may be used to re-enable gas re-injection again.","units":{"field":"Mscf/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"None","value_type":"UDA","dimension":"GasSurfaceVolume/Time"},{"index":3,"name":"GSALEMAX","description":"A real positive value that must be greater than GSALE that defines the maximum allowed gas sales rate. If GSALE exceeds GSALEMAX then the action defined by the ACTION variable on this keyword is implemented at the end of the current time step. This value may be specified using a User Defined Argument (UDA).","units":{"field":"Mscf/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"1 x 1020","value_type":"UDA","dimension":"GasSurfaceVolume/Time"},{"index":4,"name":"GSALEMIN","description":"A real positive value that must be less than GSALE that defines the minimum allowed gas sales rate. If GSALE is less than GSALEMIN then one of the following actions will be implemented at the end of the current time step: If the group’s maximum gas production rate constraint is constraining the gas rate, then reset the constraint to satisfy the group’s minimum gas sales rate (GSALEMIN), else: If the group has active subordinate dedicated gas producers, as defined by the WGASPROD keyword in the SCHEDULE section, then reset their gas target rates to satisfy GSALEMIN, else: If there are subordinate dedicated gas producers for the group in a drilling queue, open the next dedicated well and set the well’s gas rate to satisfy GSALEMIN. Note that only wells that are subordinate to the group and are not under gas rate control or group prioritization are considered for opening. If there are no appropriate subordinate dedicated gas producers for the group in a drilling queue, open the next non-dedicated well and set the well’s gas rate to satisfy GSALEMIN. Again, note that only wells that are subordinate to the group and are not under gas rate control or group prioritization are considered for opening. If none of the above actions can be implemented then the minimum gas sales rate will not be satisfied. This value may be specified using a User Defined Argument (UDA).","units":{},"default":"-1 x 1020","value_type":"UDA","dimension":"GasSurfaceVolume/Time"},{"index":5,"name":"ACTION","description":"A defined character string that defines the action to be taken if the maximum gas sales rate, GSALEMAX, is violated. ACTION should be set to one of the following character strings: NONE: no action is taken. CON: close the worst offending connection in the worst offending well. If connections have been grouped as completions then the worst offending completion in the worst offending well will be closed. +CON: close the worst offending connection and all below it in the worst offending well. If connections have been grouped as completions then the worst offending completion and all below it in the worst offending well will be closed. WELL: close the worst offending well. PLUG: plug back the worst offending well. This option is not implemented in OPM Flow. RATE: the group’s production rate target is reduced to equal GSALEMAX, after accounting for fuel gas (GCONSUMP keyword) and the current rate of re-injection. This will also place the group on gas production control. END: stop the simulation at the end of the report step. The corrective action takes places at the end of the time step in which the constraint is violated.","units":{},"default":"None","value_type":"STRING","options":["NONE","CON","WELL","PLUG","RATE","END"]}],"example":"The following examples sets the field gas sales target rate:\n--\n-- GROUP GAS SALES FOR OIL FIELDS\n--\n-- GRUP GAS MAX MIN CNTL\n-- NAME SALES RATE RATE ACTN\nGCONSALE\nFIELD 40E3 50E3 20E3 RATE /\n/\nHere the field has a gas sales target of 40 MMscf/d, with a maximum rate of 50 MMscf/d and a minimum of 20 MMscf/d. If the maximum gas sales rate is exceeded then the group’s gas production rate target is reduced to equal GSALEMAX, after accounting for fuel gas and the current rate of re-injection. This will also place the group on gas production control.\n| [\"Gas Sales Rate\" ~ = ~ \"Total Group Gas Production Rate\"\nnewline \n~~~~~~~~~~~~~~ - ` \"Group Gas Injection Rate\"\nnewline \n~~~~~~~~~~~~~~~~~~ + ` \"Total Group Gas Import Rate\" \nnewline \n~~~~~~~~~~~~~~~~~~~ - ` \"Total Group Gas Consumption\"] | (12.23) |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|","expected_columns":5,"size_kind":"list"},"GCONSUMP":{"name":"GCONSUMP","sections":["SCHEDULE"],"supported":false,"summary":"GCONSUMP defines the group gas consumption rate either as an actual rate or as a percentage of the group’s production. In both oil and gas fields produced gas is commonly used as fuel to support the processing and utility facilities needed to run the plant.","parameters":[{"index":1,"name":"GRPNAME","description":"A character string of up to eight characters in length that defines the group name for which the group gas consumption is being defined. The group named FIELD is the top most group and should be used to set the fuel consumption for the field. Note that the group hierarchy should be defined by the GRUPTREE keyword when there is more than one level of groups, otherwise all the groups will sit directly under the FIELD group in the group tree hierarchy.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"GASFUEL","description":"A real value that defines the gas consumption, that is the fuel gas consumed by the group, either defined as a volumetric rate or as a fraction of the group’s gas production. The two options are implemented by: Volumetric Rate Option: Setting GASFUEL to a value greater than zero will be interpreted as the actual fuel gas rate consumed by the group. Fraction of Produced Gas: Setting GASFUEL to a negative value between minus one and zero will be interpreted as a fraction of the groups production rate. For example, if GASFUEL is entered as -0.05, would mean 5% of the group’s produced gas will be consumed as fuel. This value may be specified using a User Defined Argument (UDA).","units":{"field":"Mscf/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"0.0","value_type":"UDA","dimension":"GasSurfaceVolume/Time"},{"index":3,"name":"GASIMP","description":"A real positive value greater than zero that defines the amount of gas to be imported into the group. This value may be specified using a User Defined Argument (UDA). This option is currently not supported by OPM Flow","units":{"field":"stb/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"0.0","value_type":"UDA","dimension":"GasSurfaceVolume/Time"},{"index":4,"name":"GASNODE","description":"A character string of up to eight characters in length that defines the network node in the Extended Network Model, for which the fuel gas should be removed (GASFUEL) or the imported gas (GASIMP) assigned. This option is currently not supported by OPM Flow","units":{},"default":"None","value_type":"STRING"}],"example":"The first example sets the fuel gas consumption to 3.0 MMscf/d for the field.\n--\n-- GROUP GAS CONSUMPTION (FUEL) AND IMPORT\n--\n-- GRUP GAS GAS\n-- NAME FUEL IMPORT\n-- ------ -------\nGCONSUMP\nFIELD 3.0E3 /\n/\nThe second example sets group PLAT-WST’s fuel consumption to be 5% of the platform’s produced gas and group PLAT-EST’s to a constant 1.0 MMscf/d.\n--\n-- GROUP GAS CONSUMPTION (FUEL) AND IMPORT\n--\n-- GRUP GAS GAS\n-- NAME FUEL IMPORT\n-- ------ -------\nGCONSUMP\nPLAT-WST -0.050 /\nPLAT-EST 1.0E3 /\n/\n| [\"Gas Sales Rate\" ~ = ~ \"Total Group Gas Production Rate\"\nnewline \n~~~~~~~~~~~~~~ - ` \"Group Gas Injection Rate\"\nnewline \n~~~~~~~~~~~~~~~~~~ + ` \"Total Group Gas Import Rate\" \nnewline \n~~~~~~~~~~~~~~~~~~~ - ` \"Total Group Gas Consumption\"] | (12.24) |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|\n| [{ \"Group Gas Injection Rate\" ~ = ~ \"Group Gas Injection Rate\" ` times ` \"Group Re-Injection Fraction\" } newline {~~~~ + ` \"Total Group Gas Import Rate\" } newline { ~~~~~ - ` \"Total Group Gas Consumption\" }] | (12.25) |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|\n| Note In oil fields with no gas compression typical values of fuel gas range from three to five percent. |\n|---------------------------------------------------------------------------------------------------------|","expected_columns":4,"size_kind":"list"},"GCONTOL":{"name":"GCONTOL","sections":["SCHEDULE"],"supported":false,"summary":"The GCONTOL keyword defines the tolerance and parameters used to control the accuracy of group targets and constraints, including the field’s targets and constraints. The keyword sets the tolerance and number of Newton iterations for each time step so that the wells under group control can match the desired group targets and constraints.","parameters":[{"index":1,"name":"GRPCNV","description":"GRPCNV is a real positive value less than one that sets the group tolerance criteria used to define if convergence has been satisfied for group’s under rate control. Here, GRPCNV is an acceptable fraction of the group’s rate target. Thus, the a numerical quantity 0.01 means that values must be with 0.01 (or 1.0%) of the groups’ production target. For groups under priority control, as per GCONPRI keyword in the SCHEDULE section, GRPCNV is ignored. Note that this criteria may not be satisfied if the number of Newton iterations used in updating the well targets, as set by the NUPCOL keyword in the RUNSPEC section, or the NUPCOL parameter on this keyword, is exceeded. In this case, and only if the well potentials allow, the well rates are re-calculated ignoring the NUPCOL limit. Group tolerance criteria can also be set by the GRPCNV parameter on the NETBALAN keyword in the SCHEDULE section. If both values of GRPCNV have been entered, then the minimum of the two is used. The default value means there is no convergence criteria.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0 x 1020","value_type":"DOUBLE"},{"index":2,"name":"NUPCOL","description":"A positive integer that defines the maximum number of Newton iterations used to update well targets within a time step. Wells under group control may suffer from some dependency with other wells in the same group that are under group control. This may cause some oscillation in the production and injection well rates within the group. In order to avoid this, after the number Newton iterations within a time step surpasses NUPCOL, the group well rates are frozen until the time step has converged. Reducing the potential of well rate oscillations within the time step may result in the group targets and limits not being exactly being met in this case. Increasing the value of NUPCOL will improve the accuracy of the group targets and limits at the expense of computational efficiency. NUPCOL can also be set by the NUPCOL keyword in the RUNSPEC section. A value entered on this keyword overwrites any previously entered values of NUPCOL, including the value set by the NUPCOL keyword. The default value of 1* invokes the last previously entered value of either by the NUPCOL keyword or this keyword.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1*","value_type":"INT"},{"index":3,"name":"GASCNV","description":"In the commercial compositional simulator GASCNV is a real positive value less than one that sets the tolerance criteria used to define if convergence has been satisfied for well gas injection rates. GASCNV is also used in conjunction with well availability gas fraction quantities in the commercial compositional simulator The value is ignored by OPM Flow.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0 x 10-3","value_type":"DOUBLE"},{"index":4,"name":"GASMXITE","description":"In the commercial compositional simulator GASMXITE is a positive integer value that defines the maximum number of iterations for the gas injection computation. The value is ignored by OPM Flow.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"5","value_type":"INT"}],"example":"The example sets the group target convergence criteria to 1% (0.01) with a maximum of four Newton iterations (NUPCOL).\n--\n-- GROUP CONSTRAINT TOLERANCE\n--\n-- GROUP NEWTON INJEC NEWTON\n-- TOL ITERS TOL ITERS\n-- ----- ----- ----- ------\nGCONTOL\n0.01 4 1* 1* /","expected_columns":4,"size_kind":"fixed","size_count":1},"GCUTBACK":{"name":"GCUTBACK","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, GCUTBACK, defines a production group’s cutback limits and parameters. See also the WCUTBACK keyword in the SCHEDULE section that provides similar functionality for wells.","parameters":[{"index":1,"name":"GROUP_NAME","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"WATER_CUT_UPPER_LIM","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"GAS_OIL_UPPER_LIM","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":4,"name":"GAS_LIQ_UPPER_LIM","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":5,"name":"WAT_GAS_UPPER_LIM","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":6,"name":"RATE_CUTBACK_FACTOR","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":7,"name":"CONTROL_PHASE","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":7,"size_kind":"list"},"GCUTBACT":{"name":"GCUTBACT","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, GCUTBACT, defines a production group’s cutback limits and parameters based on the named produced tracer from the group. See also the WCUTBACT keyword in the SCHEDULE section that provides similar functionality for groups.","parameters":[],"example":"","size_kind":"none","size_count":0},"GDCQ":{"name":"GDCQ","sections":["SCHEDULE"],"supported":false,"summary":"The GDCQ keyword defines the Daily Contract Quantities (“DCQ”) for when multiple group contracts are required when the Gas Field Operations model has been activated by the GASFIELD keyword in the RUNSPEC section, or the GWSINGF has been invoked to define multiple group contracts in the SCHEDULE section. The group contracts must first be defined by the GSWINGF keyword, followed by the GCDQ keyword, and then the GASYEAR or GASPERIO keywords. GCDQ may be repeated in the SCHEDULE section to reset group DCQs.","parameters":[{"index":1,"name":"GROUP_NAME","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"INIT_DCQ","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":3,"name":"DCQ_TYPE","description":"","units":{},"default":"VAR","value_type":"STRING"}],"example":"","expected_columns":3,"size_kind":"list"},"GDCQECON":{"name":"GDCQECON","sections":["SCHEDULE"],"supported":false,"summary":"The GDCQECON keyword defines economic criteria for DCQ production groups, including the field level group FIELD, that have previously been defined by the GCONPROD keywords in the SCHEDULE section. Note that wells are allocated to a group when they are specified by the WELSPECS keyword and wells can also have economic controls. Wells under group control are therefore subject to the economic criteria set via the GCONPROD and CECON keywords in the SCHEDULE section and the controls specified by the WECON keyword.","parameters":[{"index":1,"name":"GRPNAME","description":"A character string of up to eight characters in length that defines the group name for which the group target and constraints are being defined. The group named FIELD is the top most group and should be used to set targets and constraints for the field. Note that the group hierarchy should be defined by the GRUPTREE keyword when there is more than one level of groups, otherwise all the groups will sit directly under the FIELD group in the group tree hierarchy.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"DCQ","description":"A real positive value that defines the minimum economic DCQ gas production rate, below which an economic action of shutting in or stopping all the wells in the group, as requested by item (9) of the WELSPECS keyword. Note if GRPNAME is equal to FIELD then the run will be terminated. A value less than or equal to zero switches of this criteria.","units":{"field":"Mscf/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"0.0","value_type":"DOUBLE"}],"example":"The following example defines the minimum DCQ for the field to be 10 MMscf/d.\n--\n-- GROUP ECONOMIC CRITERIA FOR DCQ PRODUCTION GROUPS\n--\n-- GRUP GAS\n-- NAME DCQ\nGDCQECON\nFIELD 10E3 /\n/","expected_columns":2,"size_kind":"list"},"GDRILPOT":{"name":"GDRILPOT","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, GDRILPOT, defines the minimum group potential rate that will result in a well from the one of the automatic drilling queues, as defined by either the QDRILL or WDRILPRI keywords in the SCHEDULE section, to be drilled and placed on production. The advantage of using a group’s potential, as oppose to a minimum rate limit, is that setting the potential greater than the group’s minimum flow rate, will result in well being drilled in time to support the desired production rate.","parameters":[{"index":1,"name":"GROUP_NAME","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"QNTY_TYPE","description":"","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"MIN_POTENTIAL_RATE","description":"","units":{},"default":"0","value_type":"DOUBLE"}],"example":"","expected_columns":3,"size_kind":"list"},"GECON":{"name":"GECON","sections":["SCHEDULE"],"supported":true,"summary":"The GECON keyword defines economic criteria for production groups, including the top level FIELD group, that have been created by having wells assigned to them via the WELSPECS keyword in the SCHEDULE section.","parameters":[{"index":1,"name":"GRPNAME","description":"A character string of up to eight characters in length that defines the group name for which the group target and constraints are being defined. The group named FIELD is the top most group and should be used to set targets and constraints for the field. Note that the group hierarchy should be defined by the GRUPTREE keyword when there is more than one level of groups, otherwise all the groups will sit directly under the FIELD group in the group tree hierarchy.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"ORAT","description":"A real positive value that defines the minimum economic surface oil production rate, below which an economic action of shutting in or stopping all the wells in the group, as requested by the AUTO variable item (9) of the WELSPECS keyword. This value may be specified using a User Defined Argument (UDA). A value less than or equal to zero switches off this criteria.","units":{"field":"stb/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"0.0","value_type":"UDA","dimension":"LiquidSurfaceVolume/Time"},{"index":3,"name":"GRAT","description":"A real positive value that defines the minimum economic surface gas production rate, below which an economic action of shutting in or stopping all the wells in the group, as requested by the AUTO variable item (9) of the WELSPECS keyword. This value may be specified using a User Defined Argument (UDA). A value less than or equal to zero switches off this criteria,","units":{"field":"Mscf/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"0.0","value_type":"UDA","dimension":"GasSurfaceVolume/Time"},{"index":4,"name":"WCUT","description":"A real positive value that defines the maximum economic surface water cut, above which an economic action will take place. This value may be specified using a User Defined Argument (UDA). Water cut is defined as:[f sub w ~=~ {q sub w } over {q sub w `+` q sub o}], and the various actions that are available if the water cut limit is exceeded are described in item (7)., and the various actions that are available if the water cut limit is exceeded are described in item (7). A value less than or equal to zero switches off this criteria.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.0","value_type":"UDA"},{"index":5,"name":"GOR","description":"A real positive value that defines the maximum economic surface gas-oil ratio, above which an economic action will take place, as defined by item (7). This value may be specified using a User Defined Argument (UDA). A value less than or equal to zero switches off this criteria.","units":{"field":"Mscf/stb","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"0.0","value_type":"UDA"},{"index":6,"name":"WGR","description":"A real positive value that defines the maximum economic surface water-gas ratio, above which an economic action will take place, as defined by item (7). This value may be specified using a User Defined Argument (UDA). A value less than or equal to zero switches off this criteria.","units":{"field":"stb/Mscf","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"0.0","value_type":"UDA"},{"index":7,"name":"ACTION","description":"A defined character string that defines the action to be taken if the economic WCUT, GOR, or WGR limits are violated. ACTION should be set to one of the following character strings: NONE: no action is taken. CON: close the worst offending connection in the worst offending well. If connections have been grouped as completions then the worst offending completion will be closed. +CON: close the worst offending connection and all below it in the worst offending well. If connections have been grouped as completions then the worst offending completion and all below it will be closed. WELL: shut or stop the worst offending well as per the AUTO variable on the WELSPECS keyword. PLUG: plug back the worst offending well based on the plug back length and options defined on the WPLUG keyword in the SCHEDULE. The corrective action takes places at the end of the time step in which the constraint is violated. Only the NONE option is currently supported by the simulator.","units":{},"default":"None","value_type":"STRING","options":["NONE","CON","WELL","PLUG"]},{"index":8,"name":"END","description":"A defined character string that defines if the simulation should terminate if all the producing wells in the group, including the FIELD group, are shut or stopped. END should be set to one of the following character strings: NO: no action is taken and the run continues. YES: terminate the run at the next report time step. Only the NO option is currently supported by the simulator.","units":{},"default":"NO","value_type":"STRING","options":["NO","YES"]},{"index":9,"name":"MXWELS","description":"A positive integer defining the maximum number of producing and injecting wells for this this group and any subordinate groups. The default value of zero implies that there is no limit to the number of wells. This is not currently supported by the simulator and must be defaulted.","units":{},"default":"0","value_type":"INT"}],"example":"The following example defines the economic criteria for the field with a minimum oil rate of 2,000 m3/day and a maximum water cut of 95%.\n--\n-- GROUP ECONOMIC CRITERIA FOR PRODUCTION GROUPS\n--\n-- GRUP OIL GAS WCT GOR WGR WORK END MAX\n-- NAME MIN MIN MAX MAX MAX OVER RUN WELLS\nGECON\nFIELD 2E3 1* 0.95 1* 1* CON 'YES' 1* /\n/\nIf the economic limits are violated then the run will stop at the next report time step.","expected_columns":9,"size_kind":"list"},"GECONT":{"name":"GECONT","sections":["SCHEDULE"],"supported":false,"summary":"The GECONT keyword defines tracer economic criteria for production groups, including the field level group FIELD, that have previously been defined by the GCONPROD keywords in the SCHEDULE section, for tracers define by the TRACER keyword in the PROPS section.","parameters":[{"index":1,"name":"GRPNAME","description":"A character string of up to eight characters in length that defines the group name for which the group target and constraints are being defined. The group named FIELD is the top most group and should be used to set targets and constraints for the field. Note that the group hierarchy should be defined by the GRUPTREE keyword when there is more than one level of groups, otherwise all the groups will sit directly under the FIELD group in the group tree hierarchy.","units":{},"default":"None","record":1},{"index":2,"name":"ACTION","description":"A defined character string that defines the action to be taken if the economic WCUT, GOR, or WGR limits are violated. ACTION should be set to one of the following character strings: NONE: no action is taken. CON: close the worst offending connection in the worst offending. If connections have been grouped as completions then the worst offending completion will be closed. +CON: close the worst offending connection and all below it in the worst offending well. If connections have been grouped as completions then the worst offending completion and all below it in the worst offending well will be closed. WELL: shut or stop the well as per the AUTO variable on the WELSPECS keyword. PLUG: plug back the worst offending well based on the plug back length and options defined on the WPLUG keyword in the SCHEDULE. The corrective action takes places at the end of the time step in which the constraint is violated.","units":{},"default":"None","record":1},{"index":3,"name":"END","description":"A defined character string that defines if the simulation should terminate if all the producing wells in the group, including the FIELD group, are shut or stopped. END should be set to one of the following character strings: NO: no action is taken and the run continues. YES: terminate the run at the next report time step.","units":{},"default":"NO","record":1},{"index":4,"name":"MXWELS","description":"A positive integer defining the maximum number of producing and injecting wells for this group and any subordinate groups. The default value of zero implies that there is no limit to the number of wells.","units":{},"default":"0","record":1},{"index":1,"name":"NAME","description":"A three letter character string defining the tracer’s name. Note it is best to void names beginning with the letters F, S, and T as these names may create naming issues in post-processing software.","units":{},"default":"None","record":2},{"index":2,"name":"MXTOTAL","description":"A real positive value that defines the maximum total (free plus solution) tracer rate. Tracer units are per those defined by the carrying fluid, oil, gas, water, etc.","units":{},"default":"None","record":2},{"index":3,"name":"MXFREET","description":"A real positive value that defines the maximum total (free plus solution) tracer concentration. Tracer units are per those defined by the carrying fluid, oil, gas, water, etc.","units":{},"default":"None","record":2},{"index":4,"name":"MXFREEQ","description":"A real positive value that defines the maximum free tracer rate. Tracer units are per those defined by the carrying fluid, oil, gas, water, etc.","units":{},"default":"None","record":2},{"index":5,"name":"MXCONC","description":"A real positive value that defines the maximum free tracer concentration. Tracer units are per those defined by the carrying fluid, oil, gas, water, etc.","units":{},"default":"None","record":2},{"index":6,"name":"MXSOLNQ","description":"A real positive value that defines the maximum solution rate. Tracer units are per those defined by the carrying fluid, oil, gas, water, etc.","units":{},"default":"None","record":2},{"index":7,"name":"MXSOLNC","description":"A real positive value that defines the maximum solution concentration. Tracer units are per those defined by the carrying fluid, oil, gas, water, etc.","units":{},"default":"None","record":2}],"example":"The following example defines the tracer economic criteria for the field and two groups, FLTBLK1 and FLTBLK,.\n--\n-- GROUP TRACER ECONOMIC CRITERIA FOR PRODUCTION GROUPS\n--\n-- GRUP WORK END MAX\n-- NAME OVER RUN WELLS\nGECONT\nFIELD +CON 'YES' 1* / START OF GROUP\n--\n-- TRACER TRACER TRACER TRACER TRACER TRACER TRACER\n-- NAME TOTAL TOTAL FREE FREE SOLN SOLN\n-- RATE CONCEN RATE CONCEN RATE CONCEN\nPLY 1000.0 /\nBRI 1000.0 /\nTR1 1* 0.7500 /\n/\nFLTBLK1 +CON 'YES' 1* / START OF GROUP\n--\n-- TRACER TRACER TRACER TRACER TRACER TRACER TRACER\n-- NAME TOTAL TOTAL FREE FREE SOLN SOLN\n-- RATE CONCEN RATE CONCEN RATE CONCEN\nPLY 800.0 /\nBRI 800.0 /\n/\nFLTBLK2 +CON 'YES' 1* / START OF GROUP\n--\n-- TRACER TRACER TRACER TRACER TRACER TRACER TRACER\n-- NAME TOTAL TOTAL FREE FREE SOLN SOLN\n-- RATE CONCEN RATE CONCEN RATE CONCEN\nPLY 800.0 /\nBRI 800.0 / END OF GROUP\n/ END OF KEYWORD\nIf the economic limits are violated then the worst offending connection and all below it in the worst offending well will be closed, If connections have been grouped as completions then the worst offending completion and all below it in the worst offending well will be closed.","size_kind":"none","size_count":0},"GEFAC":{"name":"GEFAC","sections":["SCHEDULE"],"supported":null,"summary":"Defines a group’s efficiency or up-time factor as opposed to setting the efficiency factors for individual wells.","parameters":[{"index":1,"name":"GRPNAME","description":"A character string of up to eight characters in length that defines the group name for which the group efficiency factor is being defined. The group named FIELD is the top most group and cannot have an efficiency factor set. Note that the group hierarchy should be defined by the GRUPTREE keyword when there is more than one level of groups, otherwise all the groups will sit directly under the FIELD group in the group tree hierarchy.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"FACTOR","description":"A real positive value less than or equal to one that defines the efficiency factor for the group. If a group’s down time is 5% then FACTOR should be set to 0.95 (1.0 – 0.05).","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0","value_type":"DOUBLE"},{"index":3,"name":"GRPNETWK","description":"A defined character string that determines if the GRPNAME efficiency factor should be transferred to the equivalent Extended Network Model node, and should be set to either: NO:The group’s equivalent Extended Network Model node flow rates are not multiplied by the efficiency factor FACTOR. YES:The group’s equivalent Extended Network Model node flow rates are multiplied by the efficiency factor FACTOR This option is only applicable for the Extended Network Model. In the Standard Network Model groups' reported flow rates are always used in the calculation of pressure drops.","units":{},"default":"YES","value_type":"STRING"}],"example":"--\n-- GROUP EFFICIENCY FACTORS\n--\n-- GRUP EFF NETWK\n-- NAME FACT OPTN\n-- ------ ------\nGEFAC\nPLATFORM 0.950 /\nSUBSEA1 0.860 /\n/\nIn the above example the group PLATFORM has its up-time factor set to 95% and the subsea group SUBSEA1 has an up-time factor of 86%.","expected_columns":3,"size_kind":"list"},"GLIFTLIM":{"name":"GLIFTLIM","sections":["SCHEDULE"],"supported":false,"summary":"The GLIFTLIM keyword defines the maximum number of wells on artificial lift and the maximum amount of the artificial lift that is available for a group, including the top most group in the group hierarchy known as the FIELD group. Wells are allocated to groups when the wells are specified by the WELSPECS keyword in the SCHEDULE section. Wells defined to be under group control will have their production rates controlled by the group to which they belong, in addition to any well constraints defined for the wells.","parameters":[{"index":1,"name":"GRPNAME","description":"A character string of up to eight characters in length that defines the group name for which the group’s artificial lift constraints are being defined. The group named FIELD is the top most group and should be used to set targets and constraints for the field. Note that the group hierarchy should be defined by the GRUPTREE keyword when there is more than one level of groups, otherwise all the groups will sit directly under the FIELD group in the group tree hierarchy.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"MXLIFT","description":"A real positive value that defines the total amount of artificial lift available for this group and any subordinate groups. The units for MXLIFT are the same as that defined by the ALQ parameter on the VFPPROD keyword in the SCHEDULE section. For example, if ALQ has been set to GRAT on the VFPPROD keyword, then MXLIFT would be the maximum amount of gas lift gas available for this group and any subordinate groups, and the units would Mscf, assuming FIELD units had been activated in the RUNSPEC section. The default value of zero implies that there is no limit applied to the group and its subordinate groups.","units":{"field":"See VFPPROD (ALQ)","metric":"See VFPPROD (ALQ)","laboratory":"See VFPPROD (ALQ)"},"default":"0","value_type":"DOUBLE"},{"index":3,"name":"MXWELS","description":"A positive integer defining the maximum number of producing wells on artificial lift for this group and any subordinate groups. The default value of zero implies that there is no limit to the number of wells.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0","value_type":"INT"}],"example":"The following example defines the artificial lift constraints for the field, assuming all the wells are on gas lift.\n---\n-- GROUP ARTIFICIAL LIFT CONSTRAINTS\n--\n-- GRUP MAX MAX\n-- NAME ALQ WELLS\nGLIFTLIM\nFIELD 20E3 20 /\n/\nHere the maximum amount of gas lift gas for the field is set to 20.0 MMscf/f and a maximum of 20 wells can utilize gas lift at a time.","expected_columns":3,"size_kind":"list"},"GLIFTOPT":{"name":"GLIFTOPT","sections":["SCHEDULE"],"supported":null,"summary":"The GLIFTOPT keyword defines the maximum amount of gas lift gas available and the maximum amount of gas the group can produce, including the top most group in the group hierarchy known as the FIELD group, for when gas lift optimization has been activated via the LIFTOPT keyword in the SCHEDULE section. Note that the LIFTOPT keyword should precede the GLIFTOPT keyword in the SCHEDULE section in order to activate the gas lift optimization facility.","parameters":[{"index":1,"name":"GRPNAME","description":"A character string of up to eight characters in length that defines the group name for which the group’s gas lift optimization parameters are being defined. The group named FIELD is the top most group and should be used to set targets and constraints for the field. Note that the group hierarchy should be defined by the GRUPTREE keyword when there is more than one level of groups, otherwise all the groups will sit directly under the FIELD group in the group tree hierarchy.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"MXLIFT","description":"A real value that defines the total amount of gas lift gas available for this group and any subordinate groups, multiplied by their respective efficiency factors. The units for MXLIFT are the same as that defined by the ALQ parameter on the VFPPROD keyword in the SCHEDULE section. In this case ALQ should be GRAT on the VFPPROD keyword, as MXLIFT applies to the maximum amount of gas lift gas available. The default value of zero, or a negative value implies that there is no limit applied to the group and its subordinate groups.","units":{"field":"Mscf/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"0","value_type":"DOUBLE","dimension":"GasSurfaceVolume/Time"},{"index":3,"name":"MXGAS","description":"A real value that defines the total amount of gas the group can process. This is the sum of the gas lift gas plus the produced gas for this group and any subordinate groups, multiplied by their respective efficiency factors. The default value of zero, or a negative value implies that there is no limit applied to the group and its subordinate groups","units":{"field":"Mscf/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"0","value_type":"DOUBLE","dimension":"GasSurfaceVolume/Time"}],"example":"The following example first switches on gas lift optimization via the LIFTOPT keyword and then defines the artificial lift constraints for the field, assuming all the well are on gas lift, using the GLIFTOPT keyword.\n-- ACTIVATE GAS LIFT OPTIMIZATION AND PARAMETERS\n--\n-- INCR INCR TSTEP NEWTON\n-- GAS OIL INTVAL OPTN\nLIFTOPT\n12.5E3 5E-3 0.0 YES /\n/\n--\n-- GROUP GAS LIFT OPTIMIZATION CONSTRAINTS\n--\n-- GRUP MAX MAX\n-- NAME GAS ALQ TOTAL GAS\nGLIFTOPT\nFIELD 200E3 1* /\n/\nHere the LIFTOPT keyword defines the maximum incremental gas lift gas quantity to be 12.5 x 103 m3, the minimum incremental oil gain per m3 of gas lift gas is set to 5.0 x 10-3 m3, the time step interval is set to zero to perform the gas optimization every time step, and finally the gas lift optimization will be performed NUPCOL Newton iterations for the time step.\nThe GLIFTOPT sets the maximum amount of gas lift gas for the field to 200,000 m3 and there is no maximum limit for the total maximum amount of gas that the group can process.","expected_columns":3,"size_kind":"list"},"GNETDP":{"name":"GNETDP","sections":["SCHEDULE"],"supported":false,"summary":"The GNETDP keyword sets a group’s minimum and maximum network pressure and rate controls for when the either the Standard Network or the Extended Network options have been activated, and the group is part of a network. The keywords allows for the pressure of the group to vary in order to satisfy the rate conditions declared by this keyword. The Standard Network option is invoked if the GRUPTREE, GRUPNET, GNETINJE, GNETPUMP, etc. series of keywords have been used in the SCHEDULE section. Whereas, the Extended Network option is activated by the NETWORK keyword in the RUNSPEC section. Several keywords, including, GNETDP, can be used by both network options.","parameters":[{"index":1,"name":"FIXED_PRESSURE_GROUP","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"PHASE_TYPE","description":"","units":{},"default":"GA","value_type":"STRING"},{"index":3,"name":"MIN_RATE_TRIGGER","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":4,"name":"MAX_RATE_TRIGGER","description":"","units":{},"default":"1e+20","value_type":"DOUBLE"},{"index":5,"name":"PRESSURE_INCR_SUBTRACT","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Pressure"},{"index":6,"name":"PRESSURE_INCR_ADD","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Pressure"},{"index":7,"name":"MIN_ALLOW_PRESSURE","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Pressure"},{"index":8,"name":"MAX_ALLOW_PRESSURE","description":"","units":{},"default":"1e+20","value_type":"DOUBLE","dimension":"Pressure"}],"example":"","expected_columns":8,"size_kind":"list"},"GNETINJE":{"name":"GNETINJE","sections":["SCHEDULE"],"supported":false,"summary":"The GNETINJE keyword defines the configuration of a group injection network for when the either the Standard Network or the Extended Network options have been activated. The Standard Network option is invoked if the GRUPTREE, GRUPNET, GNETINJE, GNETPUMP, etc. series of keywords have been used in the SCHEDULE section. Whereas, the Extended Network option is activated by the NETWORK keyword in the RUNSPEC section. Several keywords, including, GNETINJE, can be used by both network options.","parameters":[{"index":1,"name":"GROUP","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"PHASE","description":"","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"PRESSURE","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":4,"name":"VFP_TABLE","description":"","units":{},"default":"0","value_type":"INT"}],"example":"","expected_columns":4,"size_kind":"list"},"GNETPUMP":{"name":"GNETPUMP","sections":["SCHEDULE"],"supported":false,"summary":"The GNETPUMP keyword defines the configuration of automatic compressors and pumps in a production Standard Network, for when the Standard Network option is invoked by the GRUPTREE, GRUPNET, GNETINJE, GNETPUMP, etc., series of keywords in the SCHEDULE section. Although several keywords can be used by both the Standard and Extended Network options, GNETPUMP can only be used with the Standard Network option. The equivalent keyword for the Extended Network option is the NETCOMPA keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"GROUP","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"PROD_RATE_SWITCH","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":3,"name":"PHASE_TYPE","description":"","units":{},"default":"OIL","value_type":"STRING"},{"index":4,"name":"NEW_VFT_TABLE_NUM","description":"","units":{},"default":"4","value_type":"INT"},{"index":5,"name":"NEW_ARTIFICIAL_LIFT_QNTY","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":6,"name":"NEW_GAS_CONUMPTION_RATE","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"GasSurfaceVolume/Time"}],"example":"","expected_columns":6,"size_kind":"list"},"GPMAINT":{"name":"GPMAINT","sections":["SCHEDULE"],"supported":null,"summary":"The GPMAINT keyword defines the groups under pressure maintenance control, the associated flow rate and pressure targets, and fluid in-place regions associated with pressure maintenance, as well as various pressure maintenance controls. GPMAINT allows for various regions, as defined by the FIPNUM or FIP keywords in the REGIONS section, to have their average reservoir pressure maintained at a specified value.","parameters":[{"index":0,"name":"","description":"","units":{},"default":""},{"index":0,"name":"","description":"","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":""},{"index":1,"name":"GRPNAME","description":"A character string of up to eight characters in length that defines the group name for which the group’s associated FIPNUM region will have a targeted average reservoir pressure maintained. The group named FIELD is the top most group and can also be used to set pressure target for the whole field. Note that the group hierarchy should be defined by the GRUPTREE keyword when there is more than one level of groups, otherwise all the groups will sit directly under the FIELD group in the group tree hierarchy.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"GRPCNTL","description":"A defined character string of length four, that sets the production or injection control for the group, used to maintain the average pressure for the FIPNUM region. GRPCNTL should be set to one of the following character strings: NONE: the group will no longer maintain the average reservoir pressure for the FIPNUM region by adjusting production and injection rates. GINJ: GRPNAME’s gas in situ reservoir volume injection rate (RESV) will be adjusted in order to maintain FIPNUM’s average reservoir pressure. GINS: GRPNAME’s gas surface rate (GRAT) will be used to maintain FIPNUM’s average reservoir pressure. OINJ: GRPNAME’s oil in situ reservoir volume injection rate (RESV) will be adjusted in order to maintain FIPNUM’s average reservoir pressure. OINS: GRPNAME’s oil surface rate (ORAT) will be used to maintain FIPNUM’s average reservoir pressure. PROD: GRPNAME’s total in situ reservoir volume production rate (RESV) will be adjusted in order to maintain FIPNUM’s average reservoir pressure. Note that group cannot be under prioritization group control, as per the GCONPRI keyword in the SCHEDULE section, with this option. WINJ: GRPNAME’s water in situ reservoir volume injection rate (RESV) will be adjusted in order to maintain FIPNUM’s average reservoir pressure WINS: GRPNAME’s water surface rate (WRAT) will be used to maintain FIPNUM’s average reservoir pressure.","units":{},"default":"None","value_type":"STRING"},{"index":3,"name":"REGION","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"FIPNAME","description":"A character string of up to five characters in length, defining the fluid in-place’s name, as defined by the FIP keyword in the REGIONS section. For example, if the FIP keyword has been used to define a FIP group or family, named FIPBLK-A, then FIPNAME would be set to BLK-A. The default value of 1* means that FIPNUM on this keyword applies to the standard FIPNUM array and not to the FIP defined group regions.","units":{},"default":"1*","value_type":"STRING"},{"index":5,"name":"PRESSURE_TARGET","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":6,"name":"ALPHA","description":"A real positive value that defines the proportionality constant used to control the flow rates in order to maintain/reach the TARGET average hydrocarbon pore volume pressure for the region. See equation (12.26). Larger values of ALPHA accelerate the time for the region’s pressure to satisfy the required target pressure (TARGET). However, ALPHA values that are too large may cause the region’s pressure to oscillate. Thus, the value of ALPHA should be a value that gives the expected steady state flow rate (TARGET) of the group divided by a reasonable transient pressure error.","units":{"field":"Liquid: stb/d/psi Gas: Mscf/d/psi RESV: rb/d/psi","metric":"Liquid: sm3/day/bars Gas: sm3/day/bars RESV: rm3/day/bars","laboratory":"Liquid: scc/hour/atm Gas: scc/hour/atm RESV: rcc/hour/atm"},"default":"None","value_type":"DOUBLE","dimension":"ReservoirVolume/Time*Pressure"},{"index":7,"name":"BETA","description":"A real positive value that defines the time interval used to control the flow rates in order to maintain the TARGET average hydrocarbon pore volume pressure for the region. See equation (12.26). Larger values of BETA reduce the tendency for the regional pressure to oscillate, but consequently decrease the rate at which the pressure reaches its target value. This is because the pressure error is measured at the end of the previous time step, resulting in a “delay” in the response. Also, the larger the time steps the greater the propensity for the pressure to oscillate for given ALPHA and BETA. As a guide BETA should be set to a value that is at least as large as the maximum time step size (see the TUNING keyword in the SCHEDULE section and section 2.2Running OPM Flow 2023-04 From The Command Linefor setting the maximum time step size).","units":{"field":"day","metric":"day","laboratory":"day"},"default":"1*","value_type":"DOUBLE","dimension":"Time"}],"example":"The first example uses the gas surface rate to maintain the fields’ average hydrocarbon pore volume pressure at 225 barsa, with the ALPHA and BETA parameters set to 40.0 and 70.0 respectively.\n--\n-- GROUP PRESSURE MAINTENANCE TARGETS AND CONTROLS\n--\n-- GRUP CNTL FIPNUM FIP PRESS ALPHA BETA\n-- NAME MODE REGION FIPNAME TARGET CONST CONST\nGPMAINT\nFIELD GINS 0 1* 225 40.0 70.0 /\n/\nThe second example uses group’s BLK-A gas surface rate to maintain the average hydrocarbon pore volume pressure at 200 barsa for FIPNUM regions one to four, with the ALPHA and BETA parameters set to 40.0 and 70.0 respectively.\n--\n-- GROUP PRESSURE MAINTENANCE TARGETS AND CONTROLS\n--\n-- GRUP CNTL FIPNUM FIP PRESS ALPHA BETA\n-- NAME MODE REGION FIPNAME TARGET CONST CONST\nGPMAINT\nBLK-A GINS 1 1* 200 40.0 70.0 /\nBLK-A GINS 2 1* 200 40.0 70.0 /\nBLK-A GINS 3 1* 200 40.0 70.0 /\nBLK-A GINS 4 1* 200 40.0 70.0 /\nBLK-B WINJ 1 FLT-B 215 30.0 65.0 /\nBLK-B WINJ 2 FLT-B 215 30.0 65.0 /\nBLK-B WINJ 3 FLT-B 215 30.0 65.0 /\nBLK-B WINJ 4 FLT-B 215 30.0 65.0 /\n/\nFor group BLK-B, water in situ reservoir volume injection rate (RESV) is used to maintain FIP group/family FLT-B’s average reservoir pressure at 215 barsa for FIPFLT-B regions one to four. Here the ALPHA and BETA parameters set to 30.0 and 65.0 respectively.\n| 0 |\n|---|\n| 0 |\n|---|\n| [Q~=~Q_i``+`` %alpha `` left( left(P_TARGET``-``P_{i-1} right)``+`` sum from{i=1} to{i-1} {left(P_TARGET``-``P_{i-1} right) times %DELTA t_i} over %beta right )] | (12.26) |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|","expected_columns":7,"size_kind":"list"},"GRADGRUP":{"name":"GRADGRUP","sections":["SCHEDULE"],"supported":false,"summary":"The GRADGRUP keyword defines the SUMMARY field and group vectors that should be written to the History Match Gradient output file, for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"MNENONIC","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"list"},"GRADRESV":{"name":"GRADRESV","sections":["SCHEDULE"],"supported":false,"summary":"The GRADRESV keyword defines the SOLUTION derivative arrays that should be written to the History Match Gradient output file, for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"MNENONIC","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"list"},"GRADRFT":{"name":"GRADRFT","sections":["SCHEDULE"],"supported":false,"summary":"The GRADRFT keyword defines the derivative well RFT data, the SOLUTION pressure and saturations at a well’s connected grid block, that should be written to the History Match Gradient output file, for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"MNENONIC","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"list"},"GRADWELL":{"name":"GRADWELL","sections":["SCHEDULE"],"supported":false,"summary":"The GRADWELL keyword defines the SUMMARY well vectors that should be written to the History Match Gradient output file, for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"MNENONIC","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"list"},"GRDREACH":{"name":"GRDREACH","sections":["SCHEDULE"],"supported":false,"summary":"The GRDREACH keyword defines the location of grid blocks connecting to a previously defined river, for when the River option has been activated via the RIVRDIMS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"RIVER","description":"","units":{},"default":"","value_type":"STRING","record":1},{"index":1,"name":"I","description":"","units":{},"default":"","value_type":"INT","record":2},{"index":2,"name":"J","description":"","units":{},"default":"","value_type":"INT","record":2},{"index":3,"name":"K","description":"","units":{},"default":"","value_type":"INT","record":2},{"index":4,"name":"BRANCH_NAME","description":"","units":{},"default":"","value_type":"STRING","record":2},{"index":5,"name":"DISTANCE_TO_START","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length","record":2},{"index":6,"name":"DISTANCE_TO_END","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length","record":2},{"index":7,"name":"RCH_CONNECT_TO","description":"","units":{},"default":"","value_type":"INT","record":2},{"index":8,"name":"PENETRATION_DIRECTION","description":"","units":{},"default":"","value_type":"STRING","record":2},{"index":9,"name":"GRID_BLOCK_COORD","description":"","units":{},"default":"","value_type":"INT","record":2},{"index":10,"name":"CONTACT_AREA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length*Length","record":2},{"index":11,"name":"TABLE_NUM","description":"","units":{},"default":"","value_type":"INT","record":2},{"index":12,"name":"PRODUCTIVITY_INDEX","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Length/Time*Pressure","record":2},{"index":13,"name":"LENGTH_DEAD_GRID_BLOCK","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length","record":2},{"index":14,"name":"OPTION_CONNECT_REACH","description":"","units":{},"default":"0","value_type":"INT","record":2},{"index":15,"name":"ADJUSTMENT_REACH","description":"","units":{},"default":"0","value_type":"INT","record":2},{"index":16,"name":"REMOVE_CAP_PRESSURE","description":"","units":{},"default":"NO","value_type":"STRING","record":2},{"index":17,"name":"INFILTR_EQ","description":"","units":{},"default":"0","value_type":"INT","record":2},{"index":18,"name":"HYDRAULIC_CONDUCTIVITY","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Length/Time","record":2},{"index":19,"name":"RIVER_BED_THICKNESS","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Length","record":2}],"example":"","records_meta":[{"expected_columns":1},{"expected_columns":19}],"size_kind":"list"},"GRUPMAST":{"name":"GRUPMAST","sections":["SCHEDULE"],"supported":false,"summary":"The GRUPMAST keyword defines master groups and their associated slave groups for when the Reservoir Coupling option as been activated by the GRUPMAST and SLAVES keywords in the SCHEDULE section. Reservoir coupling allows for independent reservoir simulation decks (SLAVES) to be controlled by a separate master run file. For example, if there are five separate reservoir models each representing one field, one of the four would be used as the master and the other four would be the subordinate SLAVES.","parameters":[{"index":1,"name":"MASTER_GROUP","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"SLAVE_RESERVOIR","description":"","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"SLAVE_GROUP","description":"","units":{},"default":"","value_type":"STRING"},{"index":4,"name":"LIMITING_FRACTION","description":"","units":{},"default":"1e+20","value_type":"DOUBLE","dimension":"1"}],"example":"","expected_columns":4,"size_kind":"list"},"GRUPNET":{"name":"GRUPNET","sections":["SPECIAL","SCHEDULE"],"supported":true,"summary":"I don’t think this is supported.","parameters":[{"index":1,"name":"GRPNAME","description":"A character string of up to eight characters in length that defines the group name for which the network parameters are being defined. The group named FIELD is the top most group and may be used as a GRPNAME.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"PRES","description":"A real value that defines the fixed pressure for this group when the group is a terminating group. If the group is not a terminating group then PRES should be defaulted with 1* or set to a negative number.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1*","value_type":"DOUBLE","dimension":"Pressure"},{"index":3,"name":"VFPTAB","description":"A positive integer greater than or equal to zero that defines the VFPPROD or VFPINJ vertical lift performance table to be used for calculating the pipeline pressures connecting the LOWER and HIGHER groups in the network. Note that: The default value of zero implies that there is no pipeline connecting the LOWER and HIGHER groups. If PRES is set to a real positive number then VFPTAB should be set to zero as this implies that GRPNAME is a terminating group and therefore there is no pipeline connecting GRPNAME to a HIGHER group. If PRES and VFPTAB are defaulted with 1* or zero, then GRPNAME is not part of the network. IF VFPTAB is set equal to 9999 then this implies that there is no pressure change between the LOWER and HIGHER group. If a non-zero value is entered then the vertical lift performance tables must be entered via the VFPPROD or VFPINJ keyword in the SCHEDULE section.","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"ALQ-PIPE","description":"A real positive value that defines the artificial lift quantity to be used in conjunction with the vertical lift performance table (VFPPROD) assigned to the group via VPFTAB variable. The vertical lift performance table and the artificial lift quantity ALQ-WELL are used with the pipeline fluid rates to calculate the pipeline change pressure between the LOWER and HIGHER groups. Note that the units for ALQ-PIPE are dependent on the associated variable on the VFPPROD keyword and may represent a pump or a compressor depending how the VFPPROD table was generated by an external program.","units":{},"default":"0.0","value_type":"DOUBLE"},{"index":5,"name":"OPTION1","description":"A defined character string that defines if a group’s production target should be achieved by adjusting the tubing pressure of the wells within the group or by the adjusting the well rates by their guide rate. OPTION1 should be set to one of the following character strings: YES: the group production target is achieved by adjusting the tubing pressure of the wells within the group, so that all wells flow at the same tubing head pressure. This is normally used for wells that flow into a common manifold, for example a sub-sea completion manifold. If a group is using this option and has a higher group with production targets or constraints, then this group should have it’s guide rate set via the GCONPROD keyword in the SCHEDULE section, to ensure that the well’s within this group operate at the same tubing head pressure. NO: the group production target is achieved by adjusting the guide rates of the wells within the group. This is the standard method in matching group targets and may result with the wells within the having different tubing head pressures. Only groups containing wells can use OPTION1 equal to YES or NO, a group without wells should set OPTION1 to NO. Numerical convergence controls and iteration limits for wells using OPTION1 set equal to YES are defined via the NETBALAN keyword in the SCHEDULE section. Only the NO option is currently supported by the simulator.","units":{},"default":"NO","value_type":"STRING","options":["YES","NO"]},{"index":6,"name":"OPTION2","description":"A defined character string that defines if well gas lift gas flows through the group’s pipeline. OPTION2 should be set to one of the following character strings: NO: no well gas lift gas is allowed to flow through the pipeline only produced reservoir gas is allowed to flow through the pipeline. FLO: the well gas lift gas is added to the gas flow along the pipeline. The well gas lift gas is the sum of the calculated ALQ-WELL values for all the subordinate wells multiplied by their efficiency factors. ALQ: the pipeline gas lift gas value (ALQ-PIPE) is the sum of the calculated ALQ-WELL values for all the subordinate wells multiplied by their efficiency factors. This means that the ALQ-PIPE gas lift gas value declared on item (4) is ignored. If either FLO or ALQ have been selected then artificial lift quantity for the pipeline (ALQ-PIPE) and the wells (ALQ-WELL) must be defined as gas lift gas on the VFPPROD tables. A well’s specific gas lift gas quantity is set via the ALQ-WELL variable on the WCONPROD keyword in the SCHEDULE section. Only the NO and FLO options are currently supported by the simulator.","units":{},"default":"NO","value_type":"STRING","options":["NO","FLO","ALQ"]},{"index":7,"name":"OPTION3","description":"A defined character string that defines if the ALQ-PIPE variable should be reset to an equivalent surface oil or gas density flowing along the pipeline. OPTION3 should be set to one of the following character strings: DENO: set ALQ-PIPE to the average surface density of the oil flowing along the pipeline. DENG: set ALQ-PIPE to the average surface density of the gas flowing along the pipeline. NONE: no change to ALQ-PIPE. If either DENO or DENG have been selected then artificial lift quantity on the VFPPROD tables must be based on the same density parameter. These options are normally used when a mixture of oil or gas with different surface densities flows into the network. Only the NONE option is currently supported by the simulator.","units":{},"default":"NONE","value_type":"STRING","options":["DENO","DENG","NONE"]}],"example":"The following example defines a network based on two groups\n--\n-- DEFINE GROUP STANDARD NETWORK PARAMETERS\n--\n-- GRUP CNTL VFP PUMP MANIFOLD INCLUDE ALQ\n-- NAME PRES TABLE POWER GROUP LIFT GAS DENS\nGRUPNET\nPROD-A 1200. 1* /\nPROD-B 1* 1 1* 'YES' 1* 1* /\n/\nThe next example is more complex and is taken form the Norne model.\n--\n-- DEFINE GROUP STANDARD NETWORK PARAMETERS\n--\n-- GRUP CNTL VFP PUMP MANIFOLD INCLUDE ALQ\n-- NAME PRES TABLE POWER GROUP LIFT GAS DENS\nGRUPNET\nFIELD 20.0 5* /\nPROD 20.0 5* /\nMANI-B2 1* 8 1* NO 2* /\nMANI-B1 1* 8 1* NO 2* /\nMANI-K1 1* 9999 4* /\nB1-DUMMY 1* 9999 4* /\nMANI-D1 1* 8 1* NO 2* /\nMANI-D2 1* 8 1* NO 2* /\nMANI-K2 1* 9999 4* /\nD2-DUMMY 1* 9999 4* /\nMANI-E1 1* 9 1* NO 2* /\nMANI-E2 1* 9 4* /\n/\nHere the FIELD controlling pressure is set at 20 barsa and the same limit is used for group PROD which sits directly under the FIELD group (see Figure 12.4).","expected_columns":7,"size_kind":"list"},"GRUPRIG":{"name":"GRUPRIG","sections":["SCHEDULE"],"supported":false,"summary":"Defines a groups drilling and workover specifications.","parameters":[{"index":1,"name":"GROUP","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"WORKOVER_RIG_NUM","description":"","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"DRILLING_RIG_NUM","description":"","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"ADD_OR_REMOVE","description":"","units":{},"default":"ADD","value_type":"STRING"}],"example":"","expected_columns":4,"size_kind":"list"},"GRUPSLAV":{"name":"GRUPSLAV","sections":["SCHEDULE"],"supported":false,"summary":"The GRUPSLAV keyword defines slave groups in a slave input deck and their associated master groups in the master run, for when the Reservoir Coupling option as been activated by the GRUPMAST and SLAVES keywords in the SCHEDULE section. This keyword is required for every slave input deck. Reservoir coupling allows for independent reservoir simulation decks (SLAVES) to be controlled by a separate master run file. For example, if there are five separate reservoir models each representing one field, one of the four would be used as the master and the other four would be the subordinate SLAVES.","parameters":[{"index":1,"name":"SLAVE_GROUP","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"MASTER_GROUP","description":"","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"OIL_PROD_CONSTRAINTS","description":"","units":{},"default":"MAST","value_type":"STRING"},{"index":4,"name":"WAT_PROD_CONSTRAINTS","description":"","units":{},"default":"MAST","value_type":"STRING"},{"index":5,"name":"GAS_PROD_CONSTRAINTS","description":"","units":{},"default":"MAST","value_type":"STRING"},{"index":6,"name":"FLUID_VOL_PROD_CONSTRAINTS","description":"","units":{},"default":"MAST","value_type":"STRING"},{"index":7,"name":"OIL_INJ_CONSTRAINTS","description":"","units":{},"default":"MAST","value_type":"STRING"},{"index":8,"name":"WAT_INJ_CONSTRAINTS","description":"","units":{},"default":"MAST","value_type":"STRING"},{"index":9,"name":"GAS_INJ_CONSTRAINTS","description":"","units":{},"default":"MAST","value_type":"STRING"}],"example":"","expected_columns":9,"size_kind":"list"},"GRUPTARG":{"name":"GRUPTARG","sections":["SCHEDULE"],"supported":false,"summary":"The GRUPTARG keyword modifies the target and constraints values of both rates and pressures for previously defined groups without having to define all the variables on the group control keywords: GCONPROD or GCONPRI keywords. Variables not changed by the GRUPTARG keyword remain the same as those previously entered via the group control keywords or previously entered GRUPTARG keywords. Note that the group must still be initially be fully defined using the GCONPROD or GCONPRI keywords. All the aforementioned keywords are described in the SCHEDULE section.","parameters":[{"index":1,"name":"GRPNAME","description":"A character string of up to eight characters in length that defines the group name for which the group target and constraints are being defined. The group named FIELD is the top most group and should be used to set targets and constraints for the field. Note that the group hierarchy should be defined by the GRUPTREE keyword when there is more than one level of groups, otherwise all the groups will sit directly under the FIELD group in the group tree hierarchy.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"TARGET","description":"A defined character string that sets the item to be changed for the group the value of the item is set by item (3). ORAT: reset the surface oil production rate value as defined by item (3). WRAT: reset the surface water production rate value as defined by item (3). GRAT: reset the surface gas production rate value as defined by item (3). LRAT: reset the surface liquid (oil plus water) production rate value as defined by (3). RESV: reset the in situ reservoir volume rate value as defined by (3). GUID: reset the guide rate value for wells operating under group control. Note TARGET only defines the variable to be changed, it does not change how a group is controlled. For example, if a group is operating on ORAT control, as defined by the previously entered GCONPROD keyword, entering TARGET equal to LRAT with a value, changes the liquid constraint but the group still remains on ORAT control. Use the GCONPROD or GCONPRI keywords in the SCHEDULE section to change the control mode of a well.","units":{},"default":"None","value_type":"STRING","options":["ORAT","WRAT","GRAT","LRAT","RESV","GUID"]},{"index":3,"name":"VALUE Liquid Gas Res Vol Pressure","description":"A real positive value that defines the value of the variable declared by TARGET","units":{"field":"stb/d Mscf/d rb/d psia","metric":"sm3/day sm3/day rm3/day barsa","laboratory":"scc/hour scc/hour rcc/hour atma"},"default":"None","value_type":"DOUBLE"}],"example":"The following example below shows the oil rates for the field at the start of the schedule section (January 1, 2000).\n-- ------------------------------------------------------------------------------\n-- 01 JAN 2000 START OF SCHEDULE SECTION\n-- ------------------------------------------------------------------------------\n--\n-- GROUP PRODUCTION CONTROLS\n--\n-- GRUP CNTL OIL WAT GAS LIQ CNTL GRUP GUIDE GUIDE CNTL\n-- NAME MODE RATE RATE RATE RATE OPT CNTL RATE DEF WAT\nGCONPROD\nFIELD ORAT 40E3 60E3 30E3 65E3 1* 1* 1* 1* 1* /\n/ DATES\n01 FEB 2000 /\n/\n--\n-- GROUP PRODUCTION AND INJECTION TARGETS\n--\n-- GROUP GROUP TARGET\n-- NAME TARG VALUE\nGRUPTARG\nFIELD ORAT 45E3 /\nFIELD LIQ 75E3 /\n/\nFrom January 1, 2000 to February 1, 2000 the field is on oil rate control and has a target oil rate of 40,000 stb/d, a maximum water handling capacity of 60,000 stb/d, a maximum liquid capacity of 65,000 stb/d, and a maximum gas constraint of 30 MMscf/d. After February 1, 2000 the field’s target oil rate is increased to 45,000 stb/d and the maximum liquid constraint is increased to 75,000 stb/s; all the other parameters remain unchanged.","expected_columns":3,"size_kind":"list"},"GRUPTREE":{"name":"GRUPTREE","sections":["SCHEDULE"],"supported":null,"summary":"GRUPTREE defines the group hierarchy of groups that have been created by having wells assigned to them via the WELSPECS keyword in the SCHEDULE section, By default three group levels are defined that sets the wells as level three, reporting directly to defined groups at level two, and the level two groups reporting to the FIELD group at level one. If a different configuration is required then the GRUPTREE keyword should be used to define the group hierarchy by defining a lower level group that reports directly to a higher level group.","parameters":[{"index":1,"name":"LOWER","description":"A character string of up to eight characters in length that defines the group name which belongs to the HIGHER group. The group named FIELD is the top most group and should NOT be used as as a group name for the LOWER group name. Undefined group relationships are automatically assigned to the FIELD group.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"HIGHER","description":"A character string of up to eight characters in length that defines the HIGHER group name that the LOWER group belongs to. The group named FIELD is the top most group and can be used as as the HIGHER group name. Undefined group relationships are automatically assigned to the FIELD group.","units":{},"default":"None","value_type":"STRING"}],"example":"The first example defines PLAT01 and PLAT03 reporting to the FIELD level (default if these records are omitted) and PLAT02 reporting to PLAT01.\n--\n-- DEFINE GROUP TREE HIERARCHY\n--\n-- LOWER HIGHER\n-- GROUP GROUP\nGRUPTREE\nPLAT01 FIELD /\nPLAT02 PLAT01 /\nPLAT03 FIELD /\n/\nThe next example is more complex and is taken form the Norne model.\n--\n-- DEFINE GROUP TREE HIERARCHY\n--\n-- LOWER HIGHER\n-- GROUP GROUP\nGRUPTREE\n'INJE' 'FIELD' /\n'PROD' 'FIELD' /\n'MANI-B2' 'PROD' /\n'MANI-B1' 'PROD' /\n'MANI-D1' 'PROD' /\n'MANI-D2' 'PROD' /\n'MANI-E1' 'PROD' /\n'MANI-E2' 'PROD' /\n'MANI-K1' 'MANI-B1' /\n'MANI-K2' 'MANI-D2' /\n'MANI-C' 'INJE' /\n'MANI-F' 'INJE' /\n'WI-GSEG' 'INJE' /\n'B1-DUMMY' 'MANI-B1' /\n'D2-DUMMY' 'MANI-D2' /\n/\nThe group hierarchy for this example is shown below.\n[formula]\n[formula]Figure 12.4: Norne Group Tree Hierarchy Example\nHere groups PROD, INJ, MAN-B1, and MAN-D2 report to higher level groups and the other remaining groups all have individual wells allocated to them instead.","expected_columns":2,"size_kind":"list"},"GSATINJE":{"name":"GSATINJE","sections":["SCHEDULE"],"supported":false,"summary":"The GSATINJE keyword defines a satellite group’s oil, gas and water injection rates in the model. Satellite groups are not connected to the reservoir model and therefore have no wells or subordinate groups associated with them, they are nevertheless connected to other higher level groups and higher level groupswithin a network model (if activated).Thus, they provide a means to “add-in” outside injection and production to the model without modeling the “add-in” reservoirs.","parameters":[{"index":1,"name":"GRPNAME","description":"A character string of up to eight characters in length that defines the satellite group name for which the group injection rates are being defined. The group named FIELD is the top most group and should not be used to define a satellite group. Note that the group hierarchy should be defined by the GRUPTREE keyword in the SCHEDULE section, when there is more than one level of groups, otherwise all the groups will sit directly under the FIELD group in the group tree hierarchy. Note that a satellite group cannot have subordinate groups or wells.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"TYPE","description":"A defined character string that specifies the type of injection fluid. TYPE should be set to one of the following character strings: GAS: for gas injection. OIL: for oil injection. WAT: for water injection. If the satellite group injects more than one phase then the rates should be specified in separate records.","units":{},"default":"None","value_type":"STRING","options":["GAS","OIL","WAT"]},{"index":3,"name":"RATE","description":"A positive real value that defines the surface injection rate for the phase declared by the TYPE variable.","units":{"field":"Liquid: stb/d Gas: Mscf/d","metric":"Liquid: sm3/day Gas: sm3/day","laboratory":"Liquid: scc/hour Gas: scc/hour"},"default":"0.0","value_type":"DOUBLE"},{"index":4,"name":"RESV","description":"A positive real value that defines the reservoir volume injection rate for the phase declared by the TYPE variable for the satellite group. Generally, RESV should be set to zero, unless one wishes to have the satellite reservoir volume rate added to the group’s superordinate groups. If RESV is set to zero for all satellite groups and if the superordinate group has a reservoir volume injection target, a voidage replacement target, or a production balancing fraction target, then only the non-satellite group volumes will be used. This item is not supported by OPM Flow and should be defaulted (1*) or set to zero.","units":{"field":"rb/d","metric":"rm3/day","laboratory":"rcc/hour"},"default":"0.0","value_type":"DOUBLE","dimension":"ReservoirVolume/Time"},{"index":5,"name":"CALRATE","description":"A positive real value that defines the calorific injection rate used in the commercial compositional simulator. This item is not supported by OPM Flow and should be defaulted (1*) or set to zero.","units":{},"default":"0.0","value_type":"DOUBLE","dimension":"Energy/GasSurfaceVolume"}],"example":"The example below is based on an oil field, with the main field FLD-A being modeled in the input deck with two groups (FLD-A1 and FLD-A2), combined with one satellite field supplementing oil production and water injection (FLD-B).\n-- ==============================================================================\n--\n-- SCHEDULE SECTION\n--\n-- ==============================================================================\nSCHEDULE\n--\n-- DEFINE GROUP TREE HIERARCHY\n-- LOWER HIGHER\n-- GROUP GROUP\nGRUPTREE\nFLD-A FIELD /\nFLD-A1 FLD-A /\nFLD-A2 FLD-A /\nFLD-B FIELD /\n/\n--\n-- GROUP PRODUCTION CONTROLS\n--\n-- GRUP CNTL OIL WAT GAS LIQ CNTL GRUP GUIDE GUIDE CNTL\n-- NAME MODE RATE RATE RATE RATE OPT CNTL RATE DEF WAT\nGCONPROD\nFIELD ORAT 20E3 30E3 50E3 1* 1* 1* /\nFLD-A FLD 20E3 30E3 50E3 1* 1* 1* /\n/ --\n-- LOAD INCLUDE FILE - LOAD ALL WELLS AND VFP TABLES\n--\nINCLUDE\n'FLD-A-P50-WELLS.INC' /\n--\n-- GROUP INJECTION TARGETS AND CONSTRAINTS\n--\n-- GRUP FLUID CNTL SURF RESV REINJ VOID GRUP GUIDE GUIDE GRUP GRUP\n-- NAME TYPE MODE RATE RATE FRAC FRAC CNTL RATE DEF REINJ RESV\nGCONINJE\nFIELD WAT REIN 35E3 1* 1* 1.0 NO 1* 1* 1* 1* /\n/ --\n-- SATELLITE GROUP PRODUCTION CONTROLS\n--\n-- GRUP OIL WAT GAS RESV GAS CALORIFIC\n-- NAME RATE RATE RATE RATE LIFT RATE\nGSATPROD\nFLD-B 5E3 0.00 2E3 1* 1* /\n/\n--\n-- SATELLITE GROUP INJECTION CONTROLS\n--\n-- GRUP FLUID SURF RESV CALORIFIC\n-- NAME TYPE RATE RATE RATEV\nGSATINJE\nFLD-B WAT 10E3 1* 1* /\n/\n--\n-- ADVANCE SIMULATION BY REPORTING DATE\n--\nDATES\n1 FEB 2021 /\n/\n--\n-- SATELLITE GROUP PRODUCTION CONTROLS\n--\n-- GRUP OIL WAT GAS RESV GAS CALORIFIC\n-- NAME RATE RATE RATE RATE LIFT RATE\nGSATPROD\nFLD-B 5E3 0.00 2E3 0.0 1* /\n/\n--\n-- SATELLITE GROUP INJECTION CONTROLS\n--\n-- GRUP FLUID SURF RESV CALORIFIC\n-- NAME TYPE RATE RATE RATEV\nGSATINJE\nFLD-B WAT 10E3 1* 1* /\n/\nHere FLD-B will supplement FLD-A’s water re-injection rate by 10,000 stb/d, subject to a maximum field water injection rate of 35,000 stb/d on the GCONINJE keyword. This means that FLD-A’s maximum water injection rate cannot exceed 25,000 stb/d. In terms of oil rates, GCONPROD defines a maximum oil rate of 20,000 stb/d of which 5,000 stb/d is from FLD-B. If any of the constraints on the GCONINJE and GCONPROD keywords are violated, then the appropriate action will occur only for FLD-A, in order to ensure the group constraints are honored.\n| Note Once a group has been defined to be a satellite group, via the GSATINJE and GSATPROD keywords, then the equivalent modeled group keywords, GCONINJE and GCONPROD in the SCHEDULE section, cannot be used to set the operating conditions for satellite groups, only the GSATINJE and GSATPROD keywords may be used. |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":5,"size_kind":"list"},"GSATPROD":{"name":"GSATPROD","sections":["SCHEDULE"],"supported":false,"summary":"The GSATPROD keyword defines a satellite group’s oil, water and gas production rates in the model. Satellite groups are not connected to the reservoir model and therefore have no wells or subordinate groups associated with them, they are nevertheless connected to other higher level groups and higher level groups within a network model (if activated).They provide a means to “add-in” outside injection and production to the model without modeling the “add-in” reservoirs.","parameters":[{"index":1,"name":"GRPNAME","description":"A character string of up to eight characters in length that defines the satellite group name for which the group production import rates are being defined. The group named FIELD is the top most group and should not be used with this keyword. Note that the group hierarchy should be defined by the GRUPTREE keyword in the SCHEDULE section when there is more than one level of groups, otherwise all the groups will sit directly under the FIELD group in the group tree hierarchy. Note that a satellite group cannot have subordinate groups or wells.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"ORAT","description":"A real value, greater than or equal to zero, that defines the satellite’s surface oil production rate to be imported into the model. This value may be specified using a User Defined Argument (UDA).","units":{"field":"stb/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"0.0","value_type":"UDA","dimension":"LiquidSurfaceVolume/Time"},{"index":3,"name":"WRAT","description":"A real value, greater than or equal to zero, that defines the satellite’s surface water production rate to be imported into the model. This value may be specified using a User Defined Argument (UDA).","units":{"field":"stb/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"0.0","value_type":"UDA","dimension":"LiquidSurfaceVolume/Time"},{"index":4,"name":"GRAT","description":"A real value, greater than or equal to zero, that defines the satellite’s surface gas production rate to be imported into the model. This value may be specified using a User Defined Argument (UDA).","units":{"field":"Mscf/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"0.0","value_type":"UDA","dimension":"GasSurfaceVolume/Time"},{"index":5,"name":"RESV","description":"A real value, greater than or equal to zero, that defines the satellite’s reservoir volume production rate to be imported into the model. This item is not supported by OPM Flow and should be defaulted (1*) or set to zero.","units":{"field":"rb/d","metric":"rm3/day","laboratory":"rcc/hour"},"default":"0.0","value_type":"UDA","dimension":"ReservoirVolume/Time"},{"index":6,"name":"GASLIFT","description":"A real value, greater than or equal to zero, that defines the satellite’s gas lift gas to be imported for this group. A value for GASLIFT is only required if externally supplied gas lift is being imported into the model, and: The Network Model is active in the input deck via the NETWORK keyword in the RUNSPEC section. Here, GASLIFT is applied to the production network in order to calculate the pressure drop through the network, for branches that have: OPTION2 set to FLO on the GRUPNET keyword in the SCHEDULE section, or the GASLIFT parameter on the NODEPROP keyword in the SCHEDULE section set to YES, for when the Extended Network Model is being used. as per the BRANPROP and NODEPROP keywords, in the SCHEDULE section. The Gas Lift Optimization Model is active in the deck via the LIFTOPT keyword in the SCHEDULE section. In this case GASLIFT is applied to GRPNAME’s superordinate group’s gas supply constraints based on the GLIFTOPT keyword in the SCHEDULE section. For clarity, GLIFTOPT constraint violations result in the groups being modeled having their rates adjusted, whereas satellite group rates are not affected. This item is not supported by OPM Flow and should be defaulted (1*) or set to zero.","units":{"field":"Mscf/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"0.0","value_type":"UDA","dimension":"GasSurfaceVolume/Time"},{"index":7,"name":"CALRATE","description":"A real value greater than or equal to zero that defines the satellite's calorific production rate. This item is not supported by OPM Flow and should be defaulted (1*) or set to zero.","units":{},"default":"0.0","value_type":"UDA","dimension":"1"}],"example":"The example below is based on a dry gas field, with the main field FLD-A being modeled in the input deck with two groups (FLD-A1 and FLD-A2), combined with two satellite gas fields, FLD-B and FLD-C.\n-- ==============================================================================\n--\n-- SCHEDULE SECTION\n--\n-- ==============================================================================\nSCHEDULE\n--\n-- DEFINE GROUP TREE HIERARCHY\n-- LOWER HIGHER\n-- GROUP GROUP\nGRUPTREE\nFLD-A FIELD /\nFLD-A1 FLD-A /\nFLD-A2 FLD-A /\nFLD-B FIELD /\nFLD-C FIELD /\n/\n--\n-- GROUP PRODUCTION CONTROLS\n--\n-- GRUP CNTL OIL WAT GAS LIQ CNTL GRUP GUIDE GUIDE CNTL\n-- NAME MODE RATE RATE RATE RATE OPT CNTL RATE DEF WAT\nGCONPROD\nFIELD GRAT 1* 1* 450E3 1* 1* 1* /\nFLD-A FLD 1* 1* 450E3 1* 1* 1* /\n/\n--\n-- LOAD INCLUDE FILE - LOAD ALL WELLS AND VFP TABLES\n--\nINCLUDE\n'FLD-A-P50-WELLS.INC' /\n--\n-- SATELLITE GROUP PRODUCTION CONTROLS\n--\n-- GRUP OIL WAT GAS RESV GAS CALORIFIC\n-- NAME RATE RATE RATE RATE LIFT RATE\nGSATPROD\nFLD-B 10.0 0.00 30E3 1* 1* /\nFLD-C 20.0 5.50 20E3 0.0 1* /\n/\n--\n-- ADVANCE SIMULATION BY REPORTING DATE\n--\nDATES\n1 FEB 2021 /\n/\n--\n-- SATELLITE GROUP PRODUCTION CONTROLS\n--\n-- GRUP OIL WAT GAS RESV GAS CALORIFIC\n-- NAME RATE RATE RATE RATE LIFT RATE\nGSATPROD\nFLD-B 10.0 0.00 30E3 0.0 1* /\nFLD-C 20.0 9.00 20E3 0.0 1* /\n/\nSince the field gas rate is set to 450 MMscf/d and the satellite production is 50 MMscf/d, then FLD-A will produce only 400 MMscf/d and not the stipulated 450 MMscf/d on the GCONPROD keyword.\n| Note Once a group has been defined to be a satellite group, via the GSATINJE and GSATPROD keywords, then the equivalent modeled group keywords, GCONINJE and GCONPROD in the SCHEDULE section, cannot be used to set the operating conditions for satellite groups, only the GSATINJE and GSATPROD keywords may be used. |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":7,"size_kind":"list"},"GSEPCOND":{"name":"GSEPCOND","sections":["SCHEDULE"],"supported":false,"summary":"The GSEPCOND keyword assigns previously defined separators to a group. Group separators are specified by the SEPVALS keyword in the SCHEDULE section. The facility is used in black-oil modeling to re-scale the PVT data entered via the PROPS section, based on the saturation point oil formation volume factor (Bob) and the initial saturated gas-oil ratio (Rsi) entered on the SEVPALS keyword.","parameters":[{"index":1,"name":"GROUP","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"SEPARATOR","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":2,"size_kind":"list"},"GSSCPTST":{"name":"GSSCPTST","sections":["SCHEDULE"],"supported":false,"summary":"The GSSCPTST keyword instructs the simulator to perform a sustainable capacity test. This causes the model to be saved in it’s current state via the RESTART file, and the test performed by running the simulation under the current conditions combine with the parameters on this keyword. After the test is perform, the simulator will restart from the point prior to the test by loading in the RESTART file. This type of testing is normally applied to gas fields for which the gas sales contracts stipulate that the gas sales rates are based on a sustainable capacity rate over a fixed period of time.","parameters":[{"index":1,"name":"GROUP","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"CONTROL_MODE","description":"","units":{},"default":"GRAT","value_type":"STRING"},{"index":3,"name":"TARGET_PROD_RATE","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":4,"name":"TARGET_PROD_PERIOD","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Time"},{"index":5,"name":"MAX_PROD_RATE_FLAG","description":"","units":{},"default":"1","value_type":"INT"},{"index":6,"name":"CONV_TOLERANCE","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":7,"name":"MAT_IT","description":"","units":{},"default":"6","value_type":"INT"},{"index":8,"name":"SUB_GRP_CONTROL_FLAG","description":"","units":{},"default":"1","value_type":"INT"}],"example":"","expected_columns":8,"size_kind":"fixed","size_count":1},"GSWINGF":{"name":"GSWINGF","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, GSWINGF, defines the gas contract parameters, swing factor and the monthly seasonal profile factor, for when there are multiple gas contracts being used in the model. The keyword is used with the Gas Field Operations option which is activated by the GASFIELD keyword in the RUNSPEC section. Gas contracts are commonly based on a Daily Contract Quantity (“DCQ”) that determines the gas rate that the field should be produced at, which is normally expressed as a multiple of the DCQ, for example 1.33, and is often referred to as the “swing factor”. Some gas contracts also define a maximum DCQ (“Max DCQ”) and/or a minimum take or pay DCQ (“Min DCQ”), as well as seasonal demand characteristics. For example, gas rates may be set higher in the winter months in order to meet heating demand compared with summer months in colder climates, and the opposite in warmer climates where air conditioning demand is high.","parameters":[{"index":1,"name":"GROUP","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"SWING_JAN","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"SWING_FEB","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":4,"name":"SWING_MAR","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":5,"name":"SWING_APR","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":6,"name":"SWING_MAY","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":7,"name":"SWING_JUN","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":8,"name":"SWING_JUL","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":9,"name":"SWING_AUG","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":10,"name":"SWING_SEP","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":11,"name":"SWING_OCT","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":12,"name":"SWING_NOV","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":13,"name":"SWING_DEC","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":14,"name":"PROFILE_JAN","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":15,"name":"PROFILE_FEB","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":16,"name":"PROFILE_MAR","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":17,"name":"PROFILE_APR","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":18,"name":"PROFILE_MAY","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":19,"name":"PROFILE_JUN","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":20,"name":"PROFILE_JUL","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":21,"name":"PROFILE_AUG","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":22,"name":"PROFILE_SEP","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":23,"name":"PROFILE_OCT","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":24,"name":"PROFILE_NOV","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":25,"name":"PROFILE_DEC","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"}],"example":"| [Q sub{month}`=` DCQ times SWINGFAC sub{ month }] | (12.27) |\n|---------------------------------------------------|---------|","expected_columns":25,"size_kind":"list"},"GTADD":{"name":"GTADD","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, GTADD, adds a numerical constant to a group’s target or constraint value. The group must have been initially fully defined using the GCONPROD or GCONPRI keywords for producers or GCONINJE for injectors. Variables not changed by the GTADD keyword remain the same as those previously entered via the group control keywords or previously entered GTADD keywords. See also the GRUPTARG keyword that sets the values for a group’s target and constraints and the GTMULT keyword that multiplies a group target or constraint by a constant. All the aforementioned keywords are described in the SCHEDULE section.","parameters":[{"index":1,"name":"GROUP","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"TARGET","description":"","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"QUANTITY","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":4,"name":"NUM_ADDITIONS","description":"","units":{},"default":"1","value_type":"INT"}],"example":"","expected_columns":4,"size_kind":"list"},"GTMULT":{"name":"GTMULT","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, GTMULT, multiplies a group’s target or constraint value by a numerical constant. The group must have been initially fully defined using the GCONPROD or GCONPRI keywords for producers or GCONINJE for injectors. Variables not changed by the GTMULT keyword remain the same as those previously entered via the group control keywords or previously entered GTMULT keywords. See also the GRUPTARG keyword that sets the values for a group’s target and constraints, and the GTADD keyword that adds a constant to a group’s target or constraint. All the aforementioned keywords are described in the SCHEDULE section.","parameters":[{"index":1,"name":"GROUP","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"TARGET","description":"","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"QUANTITY","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":4,"name":"NUM_MULT","description":"","units":{},"default":"1","value_type":"INT"}],"example":"","expected_columns":4,"size_kind":"list"},"GUIDECAL":{"name":"GUIDECAL","sections":["SCHEDULE"],"supported":false,"summary":"The GUIDECAL keyword defines a well or group’s guide rate as a function of their calorific values, for when the individual wells and groups are under guide rate control. Group and well guide rates that have not been directly defined are set equal to their production potentials at the start of each time step. In this case the GUIDECAL keyword can be used to specify the coefficients of a function that takes into account the calorific value of the produced gas, effectively scaling the guide rates based on the calorific value of the gas being produced.","parameters":[{"index":1,"name":"COEFF_A","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":2,"name":"COEFF_B","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","expected_columns":2,"size_kind":"fixed","size_count":1},"GUIDERAT":{"name":"GUIDERAT","sections":["SCHEDULE"],"supported":true,"summary":"This keyword defines a general formulae used to define a group’s and well’s guide rate as a function of the their potential. The default behavior, that is when this keyword is not invoked, is to set the target control mode and rate via the GCONPROD keyword in the SCHEDULE section. In this case the target rate is distributed between the group’s wells that are under group control using a well’s guide rate. If a well’s guide rate has not been defined, for example by this keyword, then the well potential of the group controlling phase at the beginning of the time step is used. For example, if the group target rate and phase is oil, then the well’s under group control will have their oil rates determined by their oil rate potential309\n Production and injection potentials are based on rates that are unrestricted. For wells this implies that well potential is calculated based on either the BHP or THP limit, which ever is the more constraining.. The GUIDERAT keyword substitutes the pote...","parameters":[{"index":1,"name":"TSTEP","description":"A real positive value that defines the minimum time interval to re-calculate the guide rates. The guide rates are calculated at the start of a time step and the default value of zero means that the guide rates are calculated for each time step. A non-zero value for TSTEP resets the minimum interval, for example setting TSTEP equal to 30 would mean the guide rates are calculate every 30 days, or to the nearest associated time step. Calculating guide rates every time step may cause issues due to the rate dependent behavior, for example gas cusping or water coning causing the well rates to oscillate. In this case using a non-zero value of TSTEP may eliminate this oscillating behavior.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"0.0","value_type":"DOUBLE","dimension":"Time"},{"index":2,"name":"PHASE","description":"A defined character string that sets the potential phase guide rate for the group and well, the resulting Phase Guide Rate in equation (12.28). PHASE should be set to one of the following character strings: OIL: is set as the potential phase guide rate and in this case the Potential Ratio1 variable is the water-oil ratio (“WOR”) and Potential Ratio2 refers to the gas-oil ratio (“GOR”) in equation (12.28). LIQ: is set as the potential phase guide rate and the Potential Ratio1 variable is the water cut (“WCT”) and Potential Ratio2 refers to the gas-liquid ratio (“GLR”) in equation (12.28). GAS: is set as the potential phase guide rate with the Potential Ratio1 variable being the water cut (“WCT”) and Potential Ratio2 referring to the oil-gas ratio (“OGR”) in equation (12.28). RES: here the potential phase guide rate is defined as the reservoir fluid volume rate and the Potential Ratio1 variable is the water-oil ratio (“WOR”) and Potential Ratio2 refers to the gas-oil ratio (“GOR”) in equation (12.28). COMB: this option uses the linearly combined phase guide rate based on the values entered on the LINCOM keyword in the SCHEDULE section. Here the Potential Ratio1 variable is the water divided by linearly combined phase and Potential Ratio2 refers to the gas divided by linearly combined phase in equation (12.28). This option is not available in OPM Flow. NONE: the Phase Guide Rate calculation is switched off and the well guide rates revert to the well potentials of their group target phase. For reference, the units for the various options is given below .","units":{"field":"WOR: dimensionless WCT: dimensionless WGR: stb/Mscf","metric":"dimensionless dimensionless dimensionless","laboratory":"dimensionless dimensionless dimensionless"},"default":"None","value_type":"STRING","options":["OIL","LIQ","GAS","RES","COMB","NONE"]},{"index":3,"name":"A","description":"A real value greater than or equal to -3 and less than or equal to 3, that defines coefficient A in equation (12.28).","units":{},"default":"0.0","value_type":"DOUBLE"},{"index":4,"name":"B","description":"B is a real positive value that defines coefficient B in equation (12.28).","units":{},"default":"0.0","value_type":"DOUBLE"},{"index":5,"name":"C","description":"C is a real value that defines coefficient C in equation (12.28).","units":{},"default":"0.0","value_type":"DOUBLE"},{"index":6,"name":"D","description":"D is a real value greater than or equal to -3 and less than or equal to 3, that defines coefficient D in equation (12.28).","units":{},"default":"0.0","value_type":"DOUBLE"},{"index":7,"name":"E","description":"E is a real value that defines coefficient E in equation (12.28).","units":{},"default":"0.0","value_type":"DOUBLE"},{"index":8,"name":"F","description":"F is a real value greater than or equal to -3 and less than or equal to 3, that defines coefficient F in equation (12.28).","units":{},"default":"0.0","value_type":"DOUBLE"},{"index":9,"name":"GROPT01","description":"A defined character string that determines if calculated phase guide rates should be allowed to increase (YES) or not (NO), and should be set to one of the following: NO: The phase guide rates calculated from equation (12.28)are not allowed to increase above the current value, and will be reset to the current value if the calculated value does exceed the current value. YES: The phase guide rates calculated from equation (12.28)are allowed to increase at each calculation. This may increase the propensity for oscillations in the rates if the water cut and GOR are rate dependent. Note only the default value is currently supported by OPM Flow.","units":{},"default":"YES","value_type":"STRING"},{"index":10,"name":"GROPT02","description":"A real positive value greater than or equal to zero and less than or equal to one that “dampens” the calculated phase guide rate based on the following formula: [( Phase`Guide`Rate )_t ^new``=``GROPT02 times ( Phase`Guide`Rate )_t``+` newline( 1`-`GROPT02) times (Phase`Guide`Rate )_(t-1)] The option is intended to have a similar effect as the GROPT01 NO option to reduce oscillations as a result of either the water cut or GOR being rate dependent. Values approaching one allows the calculated phase guide rates to change instantaneously with the phase potentials, whereas values approaching zero dampen the potential guide rates towards the previously calculated values, thereby reducing the potential for oscillating behavior.","units":{},"default":"1.0","value_type":"DOUBLE"},{"index":11,"name":"GROPT03","description":"A defined character string that determines if “free” gas potential rates for the Potential Ratio2 variable in equation (12.28)should be used (YES), or if “free and associated” gas should be used (NO), and should be set to one of the following: NO: Use “free and associated” gas, that is total gas in the Potential Ratio2 variable. YES: Only utilize “free” gas in the Potential Ratio2 variable.","units":{},"default":"NO","value_type":"STRING"},{"index":12,"name":"GROPT04","description":"A real positive value that sets the minimum potential guide rate. If the calculated potential guide is below this value it will be reset to GROPT04. The option is meant to avoid groups and wells being ignored due to the calculated potential guide rates being minuscule.","units":{},"default":"1.0 x10-6","value_type":"DOUBLE"}],"example":"The first example sets the guide phase to oil and the resulting Phase Guide Rate based on oil potential based on setting the A and B coefficients to to one, that is:\n[Phase Guide Rate``= { (Potental _Phase) ^A } over { B``+``C(Potential Ratio_1)^D``+`` E(Potential Ratio_2)^F} newline newline\n~=~{Oil Potential^1.0} over 1.0]\n(12.29)\nwith all the other parameters defaulted, except for the minimum time interval to re-calculate the guide rates which is set to 30 days.\n--\n-- SETS GUIDE RATES FOR GROUPS AND WELLS UNDER GUIDE RATE CONTROL\n--\n-- TIME GUIDE A B C D E F INCR DAMP FREE\n-- STEP PHASE POW CON CON POW CON POW OPTN OPTN GAS\nGUIDERAT\n30 'OIL' 1.0 1.0 1* 1* 1* 1* 1* 1* 1* /\nThe next example sets the Phase Guide Rate to the reservoir fluid volume rate, with preference given to low GOR wells and with high GOR wells penalized, based on setting A and B to one, C and D to zero, E equal to 10 and F equal to two, that is:\n[Phase Guide Rate``= { (Potental _Phase) ^A } over { B``+``C(Potential Ratio_1)^D``+`` E(Potential Ratio_2)^F}~newline newline\n~~~~~`` =~{Reservoir` Fluid `Volume` Potential^1.0} over {1.0`` + ``10 times (GOR)^2}]\n(12.30)\nwith all the other parameters defaulted.\n--\n-- SETS GUIDE RATES FOR GROUPS AND WELLS UNDER GUIDE RATE CONTROL\n--\n-- TIME GUIDE A B C D E F INCR DAMP FREE\n-- STEP PHASE POW CON CON POW CON POW OPTN OPTN GAS\nGUIDERAT\n1* 'RES' 1.0 1.0 1* 1* 10 2 1* 1* 1* /\nThe GUIDERAT keyword is very flexible but can also lead to unexpected results, thus it is probably useful to perform some manual calculations outside of the simulator before implementing the selected scheme in the input deck.\n| [Phase Guide Rate``= { (Potental _Phase) ^A } over { B``+``C(Potential Ratio_1)^D``+`` E(Potential Ratio_2)^F}] | (12.28) |\n|------------------------------------------------------------------------------------------------------------------|---------|\n| Note GUIDERAT can be used to penalize wells producing excessive water by utilizing the C and D coefficients in equation (12.28), and to discriminate against wells that are gassing out by setting the E and F coefficients. Note that the value range through which Potential Ratio1 and Potential Ratio2 vary is variable. For example, if Potential Ratio1 is water cut, then the value should be between zero and one, whereas for the water-oil ratio the value can vary between zero and infinity. The same applies to the units of Potential Ratio2 which are dependent on if the GOR, GLR or OGR ratio is used in the calculation. One can use the C and E coefficients to scale these terms to the required relative magnitudes in the denominator and the D and F powers to influence how quickly the penalty increases with increasing water and gas fractions. High positive value for D and F coefficients will make production fall off rapidly as the water or gas fraction increases, while a negative values will favor producing these type of wells. Note that the B coefficient should always be positive to prevent the denominator's going to zero. Finally, if one wishes each well to produce in proportion to its potential when the water fraction and gas fraction are equal (the usual case), then the A coefficient should be set to one. |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------","expected_columns":12,"size_kind":"fixed","size_count":1},"GUPFREQ":{"name":"GUPFREQ","sections":["SCHEDULE"],"supported":false,"summary":"The GUPFREQ keyword sets the update frequency of the Instantaneous Gradient option for when this option has been activated by the GDIMS keyword in the RUNSPEC section. The Instantaneous Gradient option calculates derivatives of solution quantities at the current time step with respect to variations in the variables at the current time step. This is different to Gradient option that calculates the derivatives of solution quantities at the current time step with respect to variations in the variables at the initial time step, that is a time equal to zero. Consequently, the Instantaneous Gradient option can be switched on and off by the GUPFREQ keyword in the SCHEDULE section, whereas the Gradient option cannot.","parameters":[{"index":1,"name":"UPDATE_FREQ_TYPE","description":"","units":{},"default":"ALL","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"GWRTWCV":{"name":"GWRTWCV","sections":["SCHEDULE"],"supported":false,"summary":"The GWRTWCV keyword defines the wells and instantaneous gradient parameters to be calculated and exported as SUMMARY vectors to the summary file, for when the Instantaneous Gradient option has been activated by the GDIMS keyword in the RUNSPEC section. The Instantaneous Gradient option calculates derivatives of solution quantities at the current time step with respect to variations in the variables at the current time step. This is different to Gradient option that calculates the derivatives of solution quantities at the current time step with respect to variations in the variables at the initial time step, that is a time equal to zero. Consequently, the Instantaneous Gradient option can be switched on and off by the GUPFREQ keyword in the SCHEDULE section, whereas the Gradient option cannot.","parameters":[{"index":1,"name":"WELLS","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","size_kind":"list","variadic_record":true},"HMWPIMLT":{"name":"HMWPIMLT","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, HMWPIMLT, defines the history match gradient parameters for well productiviity indices, for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section. Wells must be specified using the WELPSECS keyword in the SCHEDULE section and their connections defined by the COMPDAT and/or COMPDATL keywords, also in the SCHEDULE section","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"list"},"LGRFREE":{"name":"LGRFREE","sections":["SCHEDULE"],"supported":null,"summary":"The LGRFREE keyword activates the Local Grid Refinement (“LGR”) Independent Time Step option that allows the LGR to have solution time steps independent of the host grid for the stated LGR, and for when LGRs have been declared by the LGR keyword in the RUNSPEC section, and defined by the CARFIN (Cartesian LGR grid) or RADIN/RADIN4 (radial LGR grid) keywords in the GRID section. LGR independent solution time stepping can be deactivated by the LGRLOCK keyword in the SCHEDULE section.","parameters":[{"index":1,"name":"LGRNAME","description":"A character string of up to eight characters in length that defines the LGR name for which independent solution time stepping is to be activated. The LGR must have been previously defined by the CARFIN (Cartesian LGR grid) or RADIN/RADIN4 (radial LGR grid) keywords in the GRID section.","units":{},"default":"None","value_type":"STRING"}],"example":"The example below defines three oil LGRs(LGR-OP01,-OP02, and -OP03) and all the gas well LGRs (LGR-GP*) that should use independent solution time steps.\n--\n-- ACTIVATE LOCAL GRID REFINEMENT INDEPENDENT TIME STEPS\n--\n-- LGRNAME\nLGRFREE\nLGR-OP01 /\nLGR-OP02 /\nLGR-OP03 /\nLGR-GP* /\n/","expected_columns":1,"size_kind":"list"},"LGRLOCK":{"name":"LGRLOCK","sections":["SCHEDULE"],"supported":null,"summary":"The LGRLOCK keyword deactivates the Local Grid Refinement (“LGR”) Independent Time Step option that allows the LGR to have solution time steps independent of the host grid for the stated LGR, that is the LGR will now follow the global grid solution time steps. LGRs must have declared by the LGR keyword in the RUNSPEC section, and defined by the CARFIN (Cartesian LGR grid) or RADIN/RADIN4 (radial LGR grid) keywords in the GRID section. LGR independent solution time stepping can be activated by the LGRFREE keyword in the SCHEDULE section.","parameters":[{"index":1,"name":"LGRNAME","description":"A character string of up to eight characters in length that defines the LGR name for which independent solution time stepping is to be deactivated. The LGR must have been previously defined by the CARFIN (Cartesian LGR grid) or RADIN/RADIN4 (radial LGR grid) keywords in the GRID section.","units":{},"default":"None","value_type":"STRING"}],"example":"The example below defines three oil LGRs(LGR-OP01,-OP02, and -OP03) and all the gas well LGRs (LGR-GP*) that should have their independent solution time steps deactivated.\n--\n-- DEACTIVATE LOCAL GRID REFINEMENT INDEPENDENT TIME STEPS\n--\n-- LGRNAME\nLGRLOCK\nLGR-OP01 /\nLGR-OP02 /\nLGR-OP03 /\nLGR-GP* /\n/","expected_columns":1,"size_kind":"list"},"LGROFF":{"name":"LGROFF","sections":["SCHEDULE"],"supported":null,"summary":"The LGROFF keyword deactivates a stated Local Grid Refinement (“LGR”) and optionally sets the minimum number of wells below which the LGR will be automatically deactivated. LGRs must have declared by the LGR keyword in the RUNSPEC section, and defined by the CARFIN (Cartesian LGR grid) or RADIN/RADIN4 (radial LGR grid) keywords in the GRID section. LGRs can subsequently be activated by the LGRON keyword in the SCHEDULE section.","parameters":[{"index":1,"name":"LGRNAME","description":"A character string of up to eight characters in length that defines the LGR name for which the LGR is being deactivated. The LGR must have been previously defined by the CARFIN (Cartesian LGR grid) or RADIN/RADIN4 (radial LGR grid) keywords in the GRID section.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"MNWELLS","description":"A positive integer greater than or equal to zero that defines the minimum number of active wells, below which the LGR will be automatically deactivated. The default value of zero implies that there is no limit to the number of wells and results in the LGR being unconditionally being deactivated.","units":{},"default":"0","value_type":"INT"}],"example":"The example below unconditionally deactivates LGR-OP01, and sets the minimum number of active wells for deactivating LGR-OP02 and LGR-OP03 to one. For all the gas well LGRs (LGR-GP*) the minimum number of wells for deactivation is set to two.\n--\n-- DEACTIVATE LOCAL GRID REFINEMENTS\n--\n-- LGRNAME MNWELLS\nLGROFF\nLGR-OP01 /\nLGR-OP02 1 /\nLGR-OP03 1 /\nLGR-GP* 2 /\n/","expected_columns":2,"size_kind":"fixed","size_count":1},"LGRON":{"name":"LGRON","sections":["SCHEDULE"],"supported":null,"summary":"The LGRON keyword activates a stated Local Grid Refinement (“LGR”) and optionally sets the minimum number of wells above which the LGR will remain active. LGRs must have declared by the LGR keyword in the RUNSPEC section, and defined by the CARFIN (Cartesian LGR grid) or RADIN/RADIN4 (radial LGR grid) keywords in the GRID section. LGRs can subsequently be deactivated by the LGROFF keyword in the SCHEDULE section.","parameters":[{"index":1,"name":"LGRNAME","description":"A character string of up to eight characters in length that defines the LGR name for which the LGR is being activated. The LGR must have been previously defined by the CARFIN (Cartesian LGR grid) or RADIN/RADIN4 (radial LGR grid) keywords in the GRID section.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"MNWELLS","description":"A positive integer greater than or equal to zero that defines the minimum number of active wells, below which the LGR will be automatically deactivated. The default value of zero implies that there is no limit to the number of wells and results in the LGR being unconditionally being activated.","units":{},"default":"0","value_type":"INT"}],"example":"The example below unconditionally activates LGR-OP01, and sets the minimum number of active wells for activating LGR-OP02 and LGR-OP03 to one. For all the gas well LGRs (LGR-GP*) the minimum number of wells for activating these LGRs is set to two.\n--\n-- ACTIVATE LOCAL GRID REFINEMENTS\n--\n-- LGRNAME MNWELLS\nLGRON\nLGR-OP01 /\nLGR-OP02 1 /\nLGR-OP03 1 /\nLGR-GP* 2 /\n/","expected_columns":2,"size_kind":"fixed","size_count":1},"LIFTOPT":{"name":"LIFTOPT","sections":["SCHEDULE"],"supported":null,"summary":"The LIFTOPT keyword actives the gas lift optimization option and defines the gas lift gas increment size, the minimum incremental oil improvement, as well as the timing of the calculations. Note that the LIFTOPT keyword should precede any GLIFTOPT and WLIFTOPT keywords in the SCHEDULE section in order to activate the gas lift optimization facility.","parameters":[{"index":1,"name":"GASLIFT","description":"A real positive number that defines the gas lift gas size increment that is used to increase the gas lift size quantity in steps. For example, if GASLIFT is set to 0.5 MMscf/d then gas lift gas will be allocated in step of 0.5 MMscf/d to each well during the optimization process. A zero or negative value switches off gas lift optimization.","units":{"field":"Mscf/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"None","value_type":"DOUBLE","dimension":"GasSurfaceVolume/Time"},{"index":2,"name":"MINOIL","description":"MINOIL is a real positive value that defines the minimum increase in oil rate for a given quantity of gas lift gas, for when gas lift gas should be applied to a well. Additional GASLIFT will only be assigned to a well if: [{%DELTA Q_Oil ``times`` OPTWGT} over GASLIFT~ > ~MINOIL] Where ΔQOil is the incremental oil and OPTWGT is the well’s weighting factor defined by the OPTWGT variable on the WLIFTOPT keyword in the SCHEDULE section.","units":{"field":"stb/Mscf","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"None","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/GasSurfaceVolume"},{"index":3,"name":"TSTEP","description":"TSTEP is a real positive value that defines the frequency of the gas lift optimization calculations, for example setting TSTEP equal to 30 days would result in the gas lift optimization calculation being performed approximately every 30 days. The default value of zero will result in the calculations being performed every time step. Note if the group or well is part of a production network then gas lift optimization is performed at the same time as the network is being balance, that is this parameter is ignored in this scenario. See the NETBALAN keyword in the SCHEDULE section to set the network balancing frequency in this case.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"0.0","value_type":"DOUBLE","dimension":"Time"},{"index":4,"name":"OPTLIFT","description":"A defined character string that determines if the gas lift optimization iterations should be performed for the same number of Newton iterations within a time step as used to update well targets, or to just use the first Newton iteration only. The NUPCOL keyword in the RUNSPEC section determines the number of Newton iterations used to update well targets during a time step. OPTLIFT should be set to one of the following: NO: In this case the gas lift optimization is only performed for the first Newton iteration for a time step and the distributed gas lift gas is then held constant for the groups and wells through resultant Newton iterations during the time step. This leads to better numerical performance, but may lead to the targets and constraints not being exactly satisfied if the reservoir conditions change during the time step calculations. YES: Sets the number gas lift optimization iterations to the same number of Newton iterations within a time step as used to update well targets, as per the NUPCOL keyword in the RUNSPEC section. This results in greater target and constraint accuracy even if the reservoir conditions change during the time step calculations, but at the expense of numerical performance. Similar to the NO option, after the NUPCOL Newton iteration during the time step, the distributed gas lift gas is then held constant for the groups and wells in subsequent Newton iterations.","units":{},"default":"","value_type":"STRING"}],"example":"The following example activates gas lift optimization for the field and defines the optimization parameters.\n--\n-- ACTIVATE GAS LIFT OPTIMIZATION AND PARAMETERS\n--\n-- INCR INCR TSTEP NEWTON\n-- GAS OIL INTVAL OPTN\nLIFTOPT\n12.5E3 5E-3 0.0 YES /\nHere the maximum incremental gas lift gas quantity is set to 12.5 x 103 m3, the minimum incremental oil gain per m3 of gas lift gas is set to 5.0 x 10-3 m3, the time step interval is set to zero to perform the gas optimization every time step, and finally the gas lift optimization will be performed NUPCOL Newton iterations for the time step.","expected_columns":4,"size_kind":"fixed","size_count":1},"LINCOM":{"name":"LINCOM","sections":["SCHEDULE"],"supported":false,"summary":"The LINCOM keyword defines the oil, gas and water coefficients for the Linear Combination facility which allows for a linear combination of the aforementioned phase rates and volumes to be used as targets and constraints in controlling group and well production and injection data. See also the LCUNIT in the PROPS section that defines the units for linear combination equation.","parameters":[{"index":1,"name":"ALPHA","description":"","units":{},"default":"0","value_type":"UDA"},{"index":2,"name":"BETA","description":"","units":{},"default":"0","value_type":"UDA"},{"index":3,"name":"GAMMA","description":"","units":{},"default":"0","value_type":"UDA"}],"example":"","expected_columns":3,"size_kind":"fixed","size_count":1},"MATCORR":{"name":"MATCORR","sections":["SCHEDULE"],"supported":false,"summary":"The MATCORR keyword activates the Material Balance Correction option used to adjust the accumulated material balance error in the simulation.","parameters":[{"index":1,"name":"NEWTON_IT_NUM","description":"","units":{},"default":"12","value_type":"INT"},{"index":2,"name":"NON_LIN_CONV_ERR","description":"","units":{},"default":"0.01","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"MATERIAL_BALANCE_ERR","description":"","units":{},"default":"1e-06","value_type":"DOUBLE","dimension":"1"}],"example":"","expected_columns":3,"size_kind":"fixed","size_count":1},"MESSOPTS":{"name":"MESSOPTS","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, MESSOPTS, resets the severity level for time steps that are forced to be accepted by the simulator. The normal severity level for this type of simulator generated message is PROBLEM and this can result in the run stopping depending on the parameters entered on the MESSAGES keyword. MESSOPTS can be used to reset the severity level to MESSAGE, COMMENT, WARNING, or PROBLEM; for example, to avoid the run terminating due to too many PROBLEM messages.","parameters":[{"index":1,"name":"MNEMONIC","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"SEVERITY","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":2,"size_kind":"fixed","size_count":1},"MULSGGD":{"name":"MULSGGD","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, MULSGGD, defines a constant multiplier to modify the matrix-fracture coupling transmissibility for dual porosity and dual permeability models, for when the alternative matrix-fracture coupling transmissibilities for oil-gas gravity drainage has been selected. The alternative matrix-fracture coupling transmissibilities for oil-gas gravity drainage option is activated via the SIGMAGD or SIGMAGDV keywords in the GRID section, and the dual porosity or dual permeability models are activated by the DUALPORO or DUALPERM keywords in the RUNSPEC section, respectively.","parameters":[],"example":"","size_kind":"array"},"MULSGGDV":{"name":"MULSGGDV","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, MULSGGDV, defines a constant multiplier to modify the matrix-fracture coupling transmissibility for dual porosity and dual permeability models, for when the alternative matrix-fracture coupling transmissibilities for oil-gas gravity drainage has been selected. The alternative matrix-fracture coupling transmissibilities for oil-gas gravity drainage option is activated via the SIGMAGD or SIGMAGDV keywords in the GRID section, and the dual porosity or dual permeability models are activated by the DUALPORO or DUALPERM keywords in the RUNSPEC section, respectively.","parameters":[],"example":"","size_kind":"array"},"MULTSIG":{"name":"MULTSIG","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, MULTSIG, defines a constant multiplier to modify the matrix-fracture coupling transmissibility for dual porosity and dual permeability models, for when the matrix-fracture coupling transmissibilities have been specified via the SIGMAGD or SIGMAGDV keywords in the GRID section, and the dual porosity or dual permeability models have been activated by the DUALPORO or DUALPERM keywords in the RUNSPEC section, respectively.","parameters":[{"index":1,"name":"VALUE","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"MULTSIGV":{"name":"MULTSIGV","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, MULTSIGV, defines a constant multiplier to modify the matrix-fracture coupling transmissibility for dual porosity and dual permeability models, for when the matrix-fracture coupling transmissibilities have been specified via the SIGMAGD or SIGMAGDV keywords in the GRID section, and the dual porosity or dual permeability models have activated by the DUALPORO or DUALPERM keywords in the RUNSPEC section, respectively.","parameters":[],"example":"","size_kind":"array"},"NCONSUMP":{"name":"NCONSUMP","sections":["SCHEDULE"],"supported":false,"summary":"The NCONSUMP keyword defines an extended network node’s gas consumption rate, for when the Extended Network option has been activated by the NETWORK keyword in the RUNSPEC section. The keyword can also be used to attribute the gas consumption to a previously defined group. See also the GCONSUMP keyword in the SCHEDULE section that overs more flexibility and can also be used with the Extended Network option.","parameters":[{"index":1,"name":"NODE","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"GAS_CONSUMPTION_RATE","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"GasSurfaceVolume/Time"},{"index":3,"name":"REMOVAL_GROUP","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":3,"size_kind":"list"},"NEFAC":{"name":"NEFAC","sections":["SCHEDULE"],"supported":null,"summary":"The NEFAC keyword defines an extended network node’s efficiency factor, for when the Extended Network option has been activated by the NETWORK keyword in the RUNSPEC section. See also the GEFAC keyword in the SCHEDULE section that can also be used with the Extended Network option.","parameters":[{"index":1,"name":"NODE","description":"A character string of up to eight characters in length that defines the node name for which the node efficiency factor is being defined.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"FACTOR","description":"A real positive value that is less than or equal to one that defines the efficiency factor for the node. If a node’s down time is 5% then FACTOR should be set to 0.95 (1.0 – 0.05).","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0","value_type":"DOUBLE","dimension":"1"}],"example":"","expected_columns":2,"size_kind":"list"},"NETBALAN":{"name":"NETBALAN","sections":["SCHEDULE"],"supported":true,"summary":"NETBALAN keyword causes the simulator to perform a network balancing operation at the next time step. In addition, the keyword defines the network balancing parameters used to control how network balancing is performed on a network, as well as the frequency of the network balancing calculations. If any of the parameters on the keyword are defaulted, then either the previously entered values are used, or if there are no previously entered values, then the keyword default values are employed.","parameters":[{"index":1,"name":"NTSTEP","description":"NSTEP is a real value that defines the criteria for the network balancing interval, used to define the frequency of the network balancing algorithm. NSTEP may be a negative number, a value of zero, or a positive number, as described below: Negative Value: If NSTEP is any negative value then the time stepping interval for the network balancing is based on the number of Newton iterations used in updating the well targets, as set by the NUPCOL keyword in the RUNSPEC section, or the NUPCOL parameter on the GCONTOL keyword in the SCHEDULE section. If NUPCOL is defined on both keywords, then the GCONTOL value takes precedence. Thus, any negative value of NSTEP means the network will be balanced for the first NUPCOL Newton iterations for each time step. Consequently, if this option is used it may result in some oscillations as the THP of the wells are updated at each Newton network re-balance computation. Zero Value: Here the network is balanced at the beginning of every time step, and should result in small network balancing errors for the time step, provided of course the reservoir conditions are fairly constant over the time step. This is the default value. Positive Value: In this case NSTEP is a time interval between the previous network balance and the next schedule network balancing. For example, if NSTEP is set equal to 91.25 days (365/4), then network balancing will occur every quarter. Again, the balancing occurs at the beginning of the time step. Note only negative or zero values are currently supported.","units":{"field":"days or dimensionless","metric":"days or dimensionless","laboratory":"hours or dimensionless"},"default":"0.0"},{"index":2,"name":"NCNV","description":"NCNV is a real positive value that defines the nodal pressure convergence variance, used to define if convergence has been satisfied.","units":{"field":"psia 1.45","metric":"barsa 0.10","laboratory":"atma 0.09869"},"default":"Defined"},{"index":3,"name":"NMXITER","description":"A positive integer value that defines the maximum number of network balancing operations that may be performed during a network balancing computation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"10"},{"index":4,"name":"GRPCNV","description":"GRPCNV is a real positive value less than one that sets the group tolerance criteria used to define if convergence has been satisfied for: Wells in subsea completion manifold groups under rate control. In this case GRPCNV is applied to the THP values of the wells within the group. In the field, these type of wells must flow against a common manifold pressure, that is all the wells must flow at approximately the same THP, for a given group’s flow rate. Automatic chokes for group’s under rate control. Here, GRPCNV is applied to the pressure drop across the automatic chokes. In both cases GRPCNV is an acceptable fraction of the group’s rate target. Thus, the default value 0.01 means that network balance calculated rate must be within 0.01 (or 1.0%) of the groups’ production target. Note that this criteria may not be satisfied if the number of Newton iterations used in updating the well targets, as set by the NUPCOL keyword in the RUNSPEC section, or the NUPCOL parameter on the GCONTOL keyword in the SCHEDULE section, is exceeded. Group convergence criteria can also be set by the GRPCNV parameter on the GCONTOL keyword in the SCHEDULE section. If both values of GRPCNV have been entered, then the minimum of the two is used.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.01"},{"index":5,"name":"THPMXITE","description":"A positive integer value that defines the maximum number of well THP iterations for wells in subsea completion.anifold groups under rate control. There is no equivalent iteration maximum for automatic chokes in groups under rate control, as the pressure drop across the chokes is automatically calculated in the network balancing calculation. Thus, NMXITER is used for these calculations.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"10"},{"index":6,"name":"NTRGERR","description":"A real positive value that stipulates the maximum target branch error in a network balance calculation, at the end of the time step. NTRGERR is compared with the branch error (Error), where Error is the difference between the pressure drop along the branch from the previous network balance and the current calculation, again, at the end of the time step. Subject to existing targets and constraints, the simulator will attempt to adjust the time step size in order to roughly match NTRGERR. Note also that NTRGERR should be a value that is sufficient to allow convergence as defined by NCNV and GRPNCN parameters. The default value of 1.0 x 1020 means that this parameter has no effect in the selection of the time step size.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1.0 x 1020"},{"index":7,"name":"NMAXERR","description":"A real positive value that stipulates the maximum branch error in a network balance calculation, at the end of the time step. Again, NMAXERR is compared against the branch error (Error), where Error is the difference between the pressure drop along the branch from the previous network balance and the current calculation, at the end of the time step. If Error is greater than NMAXERR then the simulator will enforce a time step chop. Time step chops are computationally expensive and should therefore be minimized. Hence, care should be used in setting this value, which should be significantly greater than NTRGERR. The default value of 1.0 x 1020 means that this parameter has no effect in the selection of the time step size.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1.0 x 1020"},{"index":8,"name":"NTSMIN","description":"NTSMIN is a real positive value that sets the minimum time step size for when NTRGERR and NMAXERR have values. Large network balancing errors (Error) can take place for various reasons, a common occurrence is for wells producing near their operating limit which may shut in during a network balance operation. If NTRGERR and NMAXERR have values, then this will result in the simulator enforcing time step chops to perhaps very small time steps. NTSMIN can therefore be used to set the minimum time step size under, and only, these circumstances. The default value, TSMINZ, is taken from TSMINZ parameter on the TUNING keyword in the SCHEDULE section.","units":{"field":"days","metric":"days","laboratory":"hour"},"default":"TSMINZ"}],"example":"The first example sets network balancing to occur at the beginning of each time step using a 1.0 psia convergence criteria, and a maximum of 10 iterations. All the other parameters are defaulted.\n--\n-- NETWORK BALANCE CONTROL OPTIONS\n--\n-- BAL CONV MAX WTHP WTHP ERR ERR TSTEP\n-- INTV TOL ITRS TOL ITS TARG MAX MIN\nNETBALAN\n0.0 1.0 10 1* 1* 1* 1* 1* /\nThe next example sets network balancing to occur for the first NUPCOL Newton iterations for each time step. All the other parameters are defaulted.\n--\n-- NETWORK BALANCE CONTROL OPTIONS\n--\n-- BAL CONV MAX WTHP WTHP ERR ERR TSTEP\n-- INTV TOL ITRS TOL ITS TARG MAX MIN\nNETBALAN\n-1 1* 1* 1* 1* 1* 1* 1* /"},"NETCOMPA":{"name":"NETCOMPA","sections":["SCHEDULE"],"supported":false,"summary":"The NETCOMPA keyword defines automatic compressors in an extended network, for when the Extended Network option has been activated by the NETWORK keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"INLET","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"OUTLET","description":"","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"GROUP","description":"","units":{},"default":"","value_type":"STRING"},{"index":4,"name":"PHASE","description":"","units":{},"default":"GAS","value_type":"STRING"},{"index":5,"name":"VFT_TABLE_NUM","description":"","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"ALQ","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":7,"name":"GAS_CONSUMPTION_RATE","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"GasSurfaceVolume/Time"},{"index":8,"name":"EXTRACTION_GROUP","description":"","units":{},"default":"","value_type":"STRING"},{"index":9,"name":"COMPRESSOR_TYPE","description":"","units":{},"default":"","value_type":"STRING"},{"index":10,"name":"NUM_COMPRESSION_LEVELS","description":"","units":{},"default":"","value_type":"INT"},{"index":11,"name":"ALQ_LEVEL1","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":12,"name":"COMP_SWITCH_SEQ_NUM","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":12,"size_kind":"list"},"NEXT":{"name":"NEXT","sections":["SCHEDULE"],"supported":false,"summary":"This keyword defines the maximum time step size the simulator should take for the next time step. This keyword can be used to reset the time step for when known large changes to the model are taking place that may result in time step chops. For example, if the reporting time size is using monthly reporting steps via the DATES keyword in the SCHEDULE section, then if for example, a group of wells start production at a given date, then the NEXT keyword can be used to shorten the next step in order to avoid a time step chop.","parameters":[{"index":1,"name":"NSTEP1","description":"NSTEP1 is a real positive value that defines the maximum length of the next time step.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"None","value_type":"DOUBLE","dimension":"Time"},{"index":2,"name":"NSTEP2","description":"NSTEP2 is a character string that should be set to either NO or YES to state if the NSTEP1 should be applied to future reporting time steps. NO: Means that NSTEP1 should not be applied to subsequent reporting time steps. YES: Means that NSTEP1 should be applied to subsequent reporting time steps. The default value of NO means that NSTEP1 will only be applied once.","units":{},"default":"NO","value_type":"STRING"}],"example":"-- NEXT ALL\n-- STEP TIME\n-- ---- ----\nNEXT\n1 'NO' /\nHere the next step size is set to one day and should only be used once.","expected_columns":2,"size_kind":"fixed","size_count":1},"NEXTSTEP":{"name":"NEXTSTEP","sections":["SCHEDULE"],"supported":null,"summary":"This keyword defines the maximum time step size the simulator should take for the next time step. This keyword can be used to limit the time step size when known large changes to the model are taking place that may otherwise result in time step chops. For example, if the simulator is using monthly reporting steps defined by the DATES keyword in the SCHEDULE section, then if a group of wells start production at a given date, then the NEXTSTEP keyword can be used to limit the next time step in order to avoid a time step chop.","parameters":[{"index":1,"name":"NSTEP1","description":"A real positive value that defines the maximum length of the next time step.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"None","value_type":"DOUBLE","dimension":"Time"},{"index":2,"name":"NSTEP2","description":"A defined character string that should be set to either NO or YES to state if the NSTEP1 should be applied to future reporting time steps. NO: Means that NSTEP1 should not be applied to subsequent reporting time steps. YES: Means that NSTEP1 should be applied to subsequent reporting time steps. The default value of NO means that NSTEP1 will only be applied once.","units":{},"default":"NO","value_type":"STRING"}],"example":"The first example shows the direct use of the NEXTSTEP keyword. Here the next time step size is limited to one day for the first time step following the next report time only.\n-- NEXT ALL\n-- STEP TIME\n-- ---- ----\nNEXTSTEP\n1 'NO' /\nThe next example shows a more complete use of the keyword for when the field oil production has increased dramatically from 10,000 stb/d to 50,000 stb/d as indicated by the two GCONPROD keywords.\n-- ------------------------------------------------------------------------------\n-- SCHEDULE SECTION - 2021-01-01\n-- ------------------------------------------------------------------------------\n--\n-- GROUP PRODUCTION CONTROLS\n--\n-- GRUP CNTL OIL WAT GAS LIQ CNTL GRUP GUIDE GUIDE CNTL\n-- NAME MODE RATE RATE RATE RATE OPT CNTL RATE DEF WAT\nGCONPROD\n'FIELD' 'ORAT' 10E3 60E3 300E3 60E3 1* 1* 1* 1* 1* /\n/\nRPTSCHED\n'WELLS=2' 'WELSPECS' 'CPU=2' 'FIP=2' /\nDATES\n2 JAN 2021 /\n/\nRPTSCHED\n'NOTHING' /\nDATES\n1 FEB 2021 /\n1 MAR 2021 /\n/\n-- GROUP PRODUCTION CONTROLS\n--\n-- GRUP CNTL OIL WAT GAS LIQ CNTL GRUP GUIDE GUIDE CNTL\n-- NAME MODE RATE RATE RATE RATE OPT CNTL RATE DEF WAT\nGCONPROD\n'FIELD' 'ORAT' 50E3 90E3 300E3 90E3 1* 1* 1* 1* 1* /\n/\n--\n-- NEXT ALL\n-- STEP TIME\n-- ---- ----\nNEXTSTEP\n1 'NO' /\nDATES\n1 APR 2021 /\n1 MAY 2021 /\n1 JUN 2021 /\n1 JLY 2021 /\n1 AUG 2021 /\n1 SEP 2021 /\n1 OCT 2021 /\n1 NOV 2021 /\n1 DEC 2021 /\n/\nGiven a start date of January 1, 2020 set via the START keyword in the RUNSPEC section, the above example shows the initial oil production of 10,000 stb/d starting in January 1, 2020, and continuing up to March 1, 2021. At the March 1, 2021 report time the field oil production rate is increased to 50,000 stb/d and the maximum next time step is set to one day. After the one day time step is completed (March 2, 2012), the simulator will progressively in increase the time step size until a maximum of 31 days is reached. The 31 day maximum is a result of requesting monthly time steps via the DATES keyword. The intent of using the NEXTSTEP keyword in this case is to prevent time step chops occurring due to the “shock” to the system caused by the large increase in oil production.","expected_columns":2,"size_kind":"fixed","size_count":1},"NEXTSTPL":{"name":"NEXTSTPL","sections":["SCHEDULE"],"supported":false,"summary":"This keyword defines the maximum time step size the simulator should take for the next time step for all Local Grid Refinements (“LGR”). This keyword can be used to reset the time step for when known large changes to the model are taking place that may result in time step chops. For example, if the reporting time size is using monthly reporting steps via the DATES keyword in the SCHEDULE section, then if for example, a group of wells start production at a given date, then the NEXTSTPL keyword can be used to shorten the next step in all the LGRs in order to avoid a time step chop.","parameters":[{"index":1,"name":"NSTEP1","description":"NSTEP1 is a real positive value that defines the maximum length of the next time step.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"None","value_type":"DOUBLE","dimension":"Time"},{"index":2,"name":"NSTEP2","description":"NSTEP2 is a character string that should be set to either NO or YES to state if the NSTEP1 should be applied to future reporting time steps. NO: Means that NSTEP1 should not be applied to subsequent reporting time steps. YES: means that STEP1 should be applied to subsequent reporting time steps. The default value of NO means that NSTEP1 will only be applied once.","units":{},"default":"NO","value_type":"STRING"}],"example":"--\n-- NEXT ALL\n-- STEP TIME\n-- ---- ----\nNEXTSTEP\n1 'NO' /\nHere the next step size for all LGRs is set to one day and should only be used once.","expected_columns":2,"size_kind":"fixed","size_count":1},"NODEPROP":{"name":"NODEPROP","sections":["SCHEDULE"],"supported":true,"summary":"This keyword defines the network node properties for the extended network option for when the Extended Network Model has been invoked by the NETWORK keyword in the RUNSPEC section. There are two types of network facilities in the simulator, the Standard Network model, which is defined with the GRUPNET keyword in the SCHEDULE section and the Extended Network Model defined by the BRANPROP and NODEPROP keywords, again in the SCHEDULE section.","parameters":[{"index":1,"name":"NODE","description":"A character string of up to eight characters in length that defines the node name for the data on this keyword record.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"PRESS","description":"A real value that sets the terminal fixed pressure for the node, this should be set to: A real positive value to define the fixed pressure for the node if the node is a terminal node, otherwise: PRESS should be set to the default value of 1* or a real negative value if the node is not a terminal node.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"1*","value_type":"DOUBLE","dimension":"Pressure"},{"index":3,"name":"CHOKE","description":"CHOKE is a defined character string that sets if the downstream branch (or uptree branch, being the one closer towards the terminal node) from this node should have the capability to choke back the flow rate in order impose a flow constraint. Here the downstream branch is the node furthermost from the wells. Thus for a production network, this will be an outlet branch as the wells are exporting fluid from the branch node. Whereas for an injection node, this is an inlet branch as the wells are importing the injection fluid.","units":{},"default":"NO","value_type":"STRING"},{"index":4,"name":"GASLIFT","description":"A defined character string that sets if the associated subordinate well’s produced gas lift gas should be included in the node’s flow stream (YES), or not (NO). GASLIFT should be set to either: NO: Do not include gas lift gas in the node's production. This means that only the produced gas from the node's subordinate wells will be included in the node's production stream. YES: Include both gas lift gas and produced gas in the node's production. This means that all gas from the subordinate wells will be included in the node's production stream. If NODE does not have any subordinate wells or satellite groups (see the GSATPROD keyword in the SCHEDULE section) directly attached to the node, then GASLIFT should be defaulted (1*) or set to NO. The option is only valid for producing networks","units":{},"default":"NO","value_type":"STRING"},{"index":5,"name":"GROUP","description":"A character string of up to eight characters in length that defines the group for which the automatic choke will be applied in order to match the group’s target rate (the TARGET variable on the GCONPROD keyword in the SCHEDULE section). The target rate is matched by adjusting the pressure drops across the automatic choke. The default value of 1* uses NODE (item one) as the group if it exists in the run. In addition, if NODE is just connected to subordinate wells then GROUP should also be defaulted.","units":{},"default":"1*","value_type":"STRING"},{"index":6,"name":"GRPNAME","description":"GRPNAME defines the name of the source or sink group in the commercial compositional simulator; however, the variable is not used as sources and sinks nodes must have the same name as their comparable groups in the Extended Network Model in both OPM Flow and the commercial black-oil simulator.","units":{},"default":"1*","value_type":"STRING"},{"index":7,"name":"NETYPE","description":"NETYPE defines the network type in the commercial compositional simulator: PROD, WINJ or GINJ. However, the variable is not used as only production networks are supported in the Extended Network Model in both OPM Flow and the commercial black-oil simulator.","units":{},"default":"1*","value_type":"STRING"}],"example":"Given the following Extended Network model in Figure 12.5.\n[formula]\n[formula]\nFigure 12.5: Extend Network Example\nFirst the Extended Network model should be used invoked in the RUNSPEC section, and then the BRANPROP keyword should be used to define the branch network, and finally the NODEPROP keyword is used to describe the node properties with the network.\n-- ==============================================================================\n--\n-- RUNSPEC SECTION\n--\n-- ==============================================================================\nRUNSPEC\n--\n-- ACTIVATE THE EXTENDED NETWORK OPTION AND DEFINE PARAMETERS\n--\n-- MAX. MAX NOT\n-- NODE LINK USED\nNETWORK\n3 2 1* /\n…..…………..\n..……..…..\n-- ==============================================================================\n--\n-- SCHEDULE SECTION\n--\n-- ==============================================================================\nSCHEDULE\n--\n-- EXTENDED NETWORK BRANCH PROPERTIES\n--\n-- DOWN UP VFP VFP\n-- NODE NODE TABLE ALFQ\nBRANPROP\nB1 PLAT-A 5 1* /\nC1 PLAT-A 4 1* /\n/\n--\n-- EXTENDED NETWORK NODE PROPERTIES\n--\n-- NODE NODE CHOKE GAS CHOKE SOURCE NETWORK\n-- NAME PRESS OPTN LIFT GROUP SINK TYPE\nNODEPROP\nPLAT-A 21.0 NO NO /\nB1 1* NO NO /\nC1 1* NO NO /\n/\nHere the main platform for the field, PLAT-A, has a fixed 21 barsa pressure applied as an operating constraint.","expected_columns":7,"size_kind":"list"},"NWATREM":{"name":"NWATREM","sections":["SCHEDULE"],"supported":false,"summary":"The NWATREM keyword defines an extended network node as a point where water is removed from the network, for when the Extended Network option has been activated by the NETWORK keyword in the RUNSPEC section. The water to be removed can be specified as a rate or as a fraction of the total volume passing through the node.","parameters":[{"index":1,"name":"NODE","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"WAX_RATE","description":"","units":{},"default":"1e+100","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time"},{"index":3,"name":"MAX_FRAC_REMOVAL","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"}],"example":"","expected_columns":3,"size_kind":"list"},"PICOND":{"name":"PICOND","sections":["SCHEDULE"],"supported":false,"summary":"The PICOND keyword defines the Generalized Pseudo Pressure (“GPP”)310\n Whitson, C. H. and Fevang, Ø. “Generalised Pseudopressure Well Treatment in Reservoir Simulation,” Presented at the IBC Technical Services Conference on Optimisation of Gas Condensate Fields, Aberdeen, UK (June 26-27, 1997) and 311\n Whitson, C. H. and Fevang, Ø. “Modeling Gas Condensate Well Deliverability,” paper SPE 30714, SPE Reservoir Engineering (1996) 11, No. 4, 221-230; also presented at the SPE Annual Technical Conference and Exhibition, Dallas, Texas, USA (October 22-25, 1995).parameters used in a gas condensate well connection inflow equations. GPP accounts for both the impact of condensate drop out and compressibility in the mobility inflow term . If the keyword is absent from the input deck then the default values are applied.","parameters":[{"index":1,"name":"MAX_INTERVAL_BELOW_DEWPOINT","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":2,"name":"MAX_INTERVAL_ABOVE_DEWPOINT","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":3,"name":"D_F","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"},{"index":4,"name":"INCLUDE","description":"","units":{},"default":"NO","value_type":"STRING"},{"index":5,"name":"F_L","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"1"},{"index":6,"name":"F_U","description":"","units":{},"default":"1.1","value_type":"DOUBLE","dimension":"1"},{"index":7,"name":"DELTA_WAT_SAT","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":8,"name":"DELTA_PRESSURE","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":9,"name":"DELTA_FRAC_COMP","description":"","units":{},"default":"0.01","value_type":"DOUBLE","dimension":"1"},{"index":10,"name":"MAX_DELTA_TIME","description":"","units":{},"default":"-1","value_type":"DOUBLE","dimension":"Time"},{"index":11,"name":"ADAPTIVE_ORD_CONTROL","description":"","units":{},"default":"-1","value_type":"DOUBLE"},{"index":12,"name":"ADAPTIVE_ORD_MIN_SPACING","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"}],"example":"","expected_columns":12,"size_kind":"fixed","size_count":1},"PIMULTAB":{"name":"PIMULTAB","sections":["SCHEDULE"],"supported":false,"summary":"Not supported. (But perhaps it should be!)","parameters":[{"index":1,"name":"WCUT","description":"A real monotonically increasing positive columnar vector that defines the maximum surface water cut for the corresponding PIMULT vector. Water cut is defined as[f sub w ~=~ {q sub w } over {q sub w `+` q sub o}]..","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE"},{"index":2,"name":"PIMULT","description":"A real positive decreasing columnar vector that defines the productivity index multiplier used to scale a well’s connection factors, for the corresponding WCUT vector.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"Given NTPIMT equals two and NRPIMT equals four on PIMTDIMS keyword in the RUNSPEC section, then:\n-- DEFINE WELL PRODUCTIVITY INDEX VERSUS WATER CUT TABLES\n--\n-- MAX PI\n-- WCUT MULT\n-- ------ ------\nPIMULTAB\n0.0000 1.0000\n0.2500 0.9500\n0.5000 0.8500\n0.7500 0.7500 /\n--\n--\n0.0000 1.0000\n0.2500 0.9500\n0.5000 0.8500\n0.7500 0.7500 /\nThe next example is summarized from the Norne model with NTPIMT equals one and NRPIMT equals to 51 on the PIMTDIMS keyword in the RUNSPEC section.\n--\n-- DEFINE WELL PRODUCTIVITY INDEX VERSUS WATER CUT TABLES\n-- The following is the reviewed model in Aug-2006, low-high case\n-- a=0.25, b=0.1; PIMULT=(1-a)/exp(fw/b)+a\n--\n-- MAX PI\n-- WCUT MULT\n-- ------ ------\nPIMULTAB\n0.000 1.0000\n0.025 0.8341\n0.050 0.7049\n0.075 0.6043\n0.100 0.5259\n0.125 0.4649\n0.150 0.4173\n0.175 0.3803\n0.200 0.3515\n0.225 0.3290\n0.250 0.3116\n0.275 0.2979\n0.300 0.2873\n0.325 0.2791\n0.350 0.2726\n0.375 0.2676\n0.400 0.2637\n0.425 0.2607\n0.450 0.2583\n0.475 0.2565\n0.500 0.2551\n0.525 0.2539\n0.550 0.2531\n0.575 0.2524\n0.600 0.2519\n0.625 0.2514\n0.650 0.2511\n0.675 0.2509\n0.700 0.2507\n0.725 0.2505\n0.750 0.2504\n0.775 0.2503\n0.800 0.2503\n0.825 0.2502\n0.850 0.2502\n0.875 0.2501\n0.900 0.2501\n0.925 0.2501\n0.950 0.2501\n0.975 0.2500\n1.000 0.2500 /","size_kind":"fixed","variadic_record":true},"PLYROCKM":{"name":"PLYROCKM","sections":["SCHEDULE"],"supported":false,"summary":"The PLYROCKM keyword modifies rock properties entered via the PLYCAMAX, PLYKRRF, PLYRMDEN, and PLYROCK keywords in the PROPS section, for when the Polymer option has been activated by the POLYMER keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"IPV","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":2,"name":"RRF","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"ROCK_DENSITY","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Density"},{"index":4,"name":"AI","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"},{"index":5,"name":"MAX_ADSORPTION","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"}],"example":"","expected_columns":5,"size_kind":"fixed"},"PRIORITY":{"name":"PRIORITY","sections":["SCHEDULE"],"supported":false,"summary":"The PRIORITY keyword activates the Well Priority option and defines the coefficients in the well priority equation. Wells under group control are ranked based on their well potential in order to satisfy group controls. For example if a group’s oil target is exceeded, then the group may shut-in the lease productive oil wells based on their well potential. The Priority option is an alternative form of ranking the wells based on the following equation:","parameters":[{"index":1,"name":"TIME","description":"A real positive integer that defines the minimum time interval between executing the well priority calculation. The calculation is performed at the beginning of the time step that exceeds the previous calculation (t0) by a minimum of TIME, that is for when tn ≥ ( t0 + TIME). Note that the default value of zero means that the calculation is performed at each time step. As a consequence, this may result in some oscillation as well wells are switched on/off at subsequent time steps.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"0","value_type":"DOUBLE","dimension":"Time"},{"index":2,"name":"A1","description":"A real positive integer greater than or equal to zero that defines a1 priority coefficient in equation (12.31).","units":{},"default":"0","value_type":"DOUBLE"},{"index":3,"name":"A2","description":"A real positive integer greater than or equal to zero that defines a2 priority coefficient in equation (12.31).","units":{},"default":"0","value_type":"DOUBLE"},{"index":4,"name":"A3","description":"A real positive integer greater than or equal to zero that defines a3 priority coefficient in equation (12.31).","units":{},"default":"0","value_type":"DOUBLE"},{"index":5,"name":"A4","description":"A real positive integer greater than or equal to zero that defines a4 priority coefficient in equation (12.31).","units":{},"default":"0","value_type":"DOUBLE"},{"index":6,"name":"B1","description":"A real positive integer greater than or equal to zero that defines b1 priority coefficient in equation (12.31).","units":{},"default":"0","value_type":"DOUBLE"},{"index":7,"name":"B2","description":"A real positive integer greater than or equal to zero that defines b2 priority coefficient in equation (12.31).","units":{},"default":"0","value_type":"DOUBLE"},{"index":8,"name":"B3","description":"A real positive integer greater than or equal to zero that defines b3 priority coefficient in equation (12.31).","units":{},"default":"0","value_type":"DOUBLE"},{"index":9,"name":"B4","description":"A real positive integer greater than or equal to zero that defines b4 priority coefficient in equation (12.31).","units":{},"default":"0","value_type":"DOUBLE"},{"index":10,"name":"A2","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":11,"name":"B2","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":12,"name":"C2","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":13,"name":"D2","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":14,"name":"E2","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":15,"name":"F2","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":16,"name":"G2","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":17,"name":"H2","description":"","units":{},"default":"0","value_type":"DOUBLE"}],"example":"--\n-- SETS COEFFICIENTS FOR WELL PRIORITIZATION OPTION\n--\n-- TIME A B C D E F G H\n-- STEP Qo Qw Qg Qo Qw Qg\nPRIORITY\n0.0 0.0 1.0 0.0 0.0 1.0 0.0 0.0 0.0 / High Oil Pot\n-- 0.0 0.0 1.0 1.0 0.0 0.0 0.0 1.0 0.0 / Low Water Cut Pot\n-- 0.0 0.0 1.0 0.0 0.0 0.0 0.0 0.0 1.0 / Low GOR Pot\nThe above example defines the well priority calculation to be based on a well’s oil potential, with calculation to be performed at each time step. Note that the low water cut and low GOR options are given for reference but are commented out and therefore ignored by the simulator.\n| [\"Priority\"`=`{ a sub{1}`+`a sub{2}Q sub{oil}`+a sub{3}Q sub{water}`+a sub{4}Q sub{gas}} over { b sub{1}`+`b sub{2}Q sub{oil}`+b sub{3}Q sub{water}`+b sub{4}Q sub{gas} }] | (12.31) |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|","expected_columns":17,"size_kind":"fixed","size_count":1},"PRORDER":{"name":"PRORDER","sections":["SCHEDULE"],"supported":false,"summary":"PRORDER defines the order of group production rules to be implemented fore when a group’s target is not satisfied.","parameters":[{"index":1,"name":"NO1","description":"","units":{},"default":"","value_type":"STRING","record":1},{"index":2,"name":"NO2","description":"","units":{},"default":"","value_type":"STRING","record":1},{"index":3,"name":"NO3","description":"","units":{},"default":"","value_type":"STRING","record":1},{"index":4,"name":"NO4","description":"","units":{},"default":"","value_type":"STRING","record":1},{"index":5,"name":"NO5","description":"","units":{},"default":"","value_type":"STRING","record":1},{"index":1,"name":"OPT1","description":"","units":{},"default":"YES","value_type":"STRING","record":2},{"index":2,"name":"OPT2","description":"","units":{},"default":"YES","value_type":"STRING","record":2},{"index":3,"name":"OPT3","description":"","units":{},"default":"YES","value_type":"STRING","record":2},{"index":4,"name":"OPT4","description":"","units":{},"default":"YES","value_type":"STRING","record":2},{"index":5,"name":"OPT5","description":"","units":{},"default":"YES","value_type":"STRING","record":2}],"example":"","records_meta":[{"expected_columns":5},{"expected_columns":5}],"size_kind":"fixed","size_count":2},"PYACTION":{"name":"PYACTION","sections":["SCHEDULE"],"supported":true,"summary":"The PYACTION keyword is part of OPM Flow’s Python scripting facility that loads a standard Python script file that can be used to define a series of conditions and actions as the simulation proceeds through time. The “included” Python script file is executed by the standard Python interpreter. Thus, OPM Flow’s Python scripting facility offers greater flexibility compared to the commercial simulator’s ACTION series of keywords (ACTION, ACTIONG, ACTIONR, ACTIONS, ACTIONW and ACTIONX) that can apply Boolean conditional tests to variables at the field, group, region, well segment and well levels. Note that OPM Flow has also implemented the commercial simulator’s ACTIONX keyword, but not the ACTION, ACTIONG, ACTIONR, ACTIONS and ACTIONW keywords, as the ACTIONX keyword implements their functionality with greater flexibility. For a python class documentation and for further documentation and examples, also refer to the OPM Online Python Documentation.","parameters":[{"index":1,"name":"ACTNAME","description":"ACTNAME is a character sting of any length enclose in quotes that defines the name of this action definition.","units":{},"default":"None","record":1,"value_type":"STRING"},{"index":2,"name":"ACTNSTEP","description":"ACTNSTEP is a defined character string that indicates the number of times the action should be performed, and should be set to one of the following: SINGLE: Here the action script is run only once. UNLIMITED: If this option is selected then the action is run at the end of every time step. FIRST_TRUE: This option forces the action to be run at the end of every time step until the script returns a value of True. Note that the FIRST_TRUE option is only supported for back compatibility when using the deprecated run() function style Python scripts.","units":{},"default":"SINGLE","record":1,"value_type":"STRING"},{"index":1,"name":"FILENAME","description":"A character string enclosed in quotes that defines the Python module/script file to read in and to be processed by OPM Flow.","units":{},"default":"None","record":2,"value_type":"STRING"}],"example":"The first example checks if well OP01 has a water cut greater than 0.8 and if so then the well is shut in. In the input deck we would have:\n--\n-- START OF PYACTION SECTION\n--\n-- ACTNAME ACTNSTEP\nPYACTION\n'MAXWCUT' 'UNLIMITED' /\n'pthon/script/MAXWCUT.py' /\n--\n-- END OF PYACTION SECTION\n--\nAnd then in the Python module file 'pthon/script/MAXWCUT.py' one would have:\n#\n# OPM Flow PYACTION Module Script\n#\nimport opm_embedded\nschedule = opm_embedded.current_schedule\nsummary_state = opm_embedded.current_summary_state\nif (not 'setup_done' in locals()):\nexecuted = False\nsetup_done = True\nif (not executed and summary_state.well_var(\"OP1\", \"WWCT\") > 0.80):\nmessage = \"Well OP01 has been shut-in due to WWCT > 0.80\\n\"\nopm_embedded.OpmLog.info(message)\nschedule.shut_well(\"OP1\")\nexecuted = True\nNote how the 'executed' variable is used to ensure that the action is only executed once the first time the water cut is greater than 0.8.\nThe next example is based on the first example from the ACTIONX keyword (ACTIONX – Define Action Conditions and Command Processing). The Python script first checks if the field’s water production is greater than 30,000 stb/d, and if not returns control back to the simulator. If the field water production is greater than 30,000 stb/d then the script uses a Python variable count to keep track of the number of times the script has been executed, and then sorts the wells from high water cut to low, via the wct_list variable, and then shuts in the worst offending well. If a well is shut-in the count variable is increased by one and control is passed back to the simulator. The script is executed as maximum of ten times.\n--\n-- START OF PYACTION SECTION\n--\n-- ACTNAME ACTNSTEP\nPYACTION\n'WSHUTIN' 'UNLIMITED' /\n'pthon/script/WSHUTIN.py' /\n--\n-- END OF PYACTION SECTION\n--\nAnd then in the Python module file 'pthon/script/WSHUTIN.py' one would have:\n#\n# OPM Flow PYACTION Module Script\n#\nimport opm_embedded\nschedule = opm_embedded.current_schedule\nsummary_state = opm_embedded.current_summary_state\nif (not 'setup_done' in locals()):\nexecution_counter = 0\nsetup_done = True\nif (execution_counter < 10 and summary_state[\"FWPR\"] >= 30000):\n#\n# Get Sorted Well List\n#\nwct_list = sorted( [ (well, summary_state.well_var(well, \"WWCT\"))\nfor well in summary_state.wells], reverse=True )\n#\n# Shut-in Well with Highest Water Cut\n#\nwell, wwct = wct_list[0]\nif wwct > 0:\nschedule.shut_well(well)\nexecution_counter += 1\nNote that by using PYACTION it makes sense to combine the UDQ variable into the PYACTION statement, like shown in the example above, although this is not necessary, as one could in principle use a normal UDQ statement and then access the variables in the PYACTION script using the summary_state variable.\nThe final example checks to see if the field’s gas rate is below 600 MMscf/d and if the simulation time is greater that January 1, 2030. If it is, then compression is installed by re-setting all the gas producing well’s THP and BHP pressures to 450 psia and 300 psia respectively. In addition all gas wells currently shut-in are tested to see if they can be opened up under the new THP and BHP constraints.\n--\n-- START OF PYACTION SECTION\n--\n-- ACTNAME ACTNSTEP\nPYACTION\n'WSHUTIN' 'UNLIMITED' /\n'pthon/script/PHASE3.py' /\n--\n-- END OF PYACTION SECTION\n--\nAnd then in the Python module file 'pthon/script/PHASE3.py' one would have:\n#\n# OPM Flow PYACTION Module Script\n#\nimport datetime\nimport opm_embedded\nschedule = opm_embedded.current_schedule\nsummary_state = opm_embedded.current_summary_state\nif (not 'setup_done' in locals()):\nexecuted = False\nsetup_done = True\nif not executed:\nsim_time = schedule.start +\ndatetime.timedelta( seconds = summary_state.elapsed() )\nif (summary_state[\"FGPR\"] < 600000 and\nsim_time > datetime.datetime(2030, 1, 1)):\n#\n# Do WELTARG and WTEST action\n#\n...\nexecuted = True\nNote how the current simulation time (sim_time) is evaluated from the simulation start time (schedule.start) and elapsed time (summary_state.elapsed); an","records_meta":[{"expected_columns":2},{"expected_columns":1}],"size_kind":"fixed","size_count":2},"QDRILL":{"name":"QDRILL","sections":["SCHEDULE"],"supported":false,"summary":"The QDRILL keyword places previously defined wells in the Sequential Drilling Queue. Wells in this type of queue will be automatically drilled and completed in the sequence entered in order to satisfy group targets, as defined by the GCONPROD, GCONINJE and GCONSALE keywords. or a group’s production potential as per the GDRILLPOT keyword. All the previously mentioned keywords are in the SCHEDULE section.","parameters":[{"index":1,"name":"WELL_NAME","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","size_kind":"fixed","size_count":1,"variadic_record":true},"RCMASTS":{"name":"RCMASTS","sections":["SCHEDULE"],"supported":false,"summary":"RCMASTS is used when reservoir coupling is invoked by the GRUPMAST and SLAVES keywords in the SCHEDULE section. The keyword should be placed within the master file and it sets the minimum time step size for groups for when a group is being restricted by a group’s limiting flow rate fractional change (see the GRUPMAST keyword in the SCHEDULE section).","parameters":[{"index":1,"name":"MIN_TSTEP","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Time"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"REACHES":{"name":"REACHES","sections":["SCHEDULE"],"supported":false,"summary":"The REACHES keyword defines the reach structure of a previously characterized river system using the RIVERSYS keyword in the SCHEDULE section. The River option must be activated via the RIVRDIMS keyword in the RUNSPEC section in order to use these keywords.","parameters":[{"index":1,"name":"RIVER","description":"","units":{},"default":"","value_type":"STRING","record":1},{"index":2,"name":"XPOS","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length","record":1},{"index":3,"name":"YPOS","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length","record":1},{"index":4,"name":"ZPOS","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length","record":1},{"index":5,"name":"LENGTH1","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length","record":1},{"index":6,"name":"INPUT_TYPE","description":"","units":{},"default":"","value_type":"STRING","record":1},{"index":1,"name":"START_REACH","description":"","units":{},"default":"","value_type":"INT","record":2},{"index":2,"name":"END_REACH","description":"","units":{},"default":"","value_type":"INT","record":2},{"index":3,"name":"OUTLET_REACH","description":"","units":{},"default":"","value_type":"INT","record":2},{"index":4,"name":"BRANCH","description":"","units":{},"default":"","value_type":"STRING","record":2},{"index":5,"name":"LENGTH2","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length","record":2},{"index":6,"name":"DEPTH","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length","record":2},{"index":7,"name":"PROFILE","description":"","units":{},"default":"1","value_type":"INT","record":2},{"index":8,"name":"ROUGHNESS","description":"","units":{},"default":"","value_type":"DOUBLE","record":2},{"index":9,"name":"XLENGTH","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length","record":2},{"index":10,"name":"YLENGTH","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length","record":2},{"index":11,"name":"REACH_LENGTH","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Length","record":2},{"index":12,"name":"NUM_REACHES","description":"","units":{},"default":"1","value_type":"INT","record":2},{"index":13,"name":"DEPTH_SOMETHING","description":"","units":{},"default":"1","value_type":"INT","record":2}],"example":"","records_meta":[{"expected_columns":6},{"expected_columns":13}],"size_kind":"list"},"READDATA":{"name":"READDATA","sections":["SCHEDULE"],"supported":false,"summary":"The READDATA keyword enables the simulator to read SCHEDULE data files generated by external programs on the fly, that is as the run is progressing. The external program can “hold” the simulation by using a file lock, in order for the external program to evaluate the current simulation results, then write out a SCHEDULE data file for the next time step, and finally releasing the “hold” by deleting the file lock and continuing with newly written SCHEDULE data file. The mechanism can be repeated so that the external program is dictating how the simulation progresses through time,","parameters":[{"index":1,"name":"INPUT_METHOD","description":"","units":{},"default":"FILE","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"RIVDEBUG":{"name":"RIVDEBUG","sections":["SCHEDULE"],"supported":false,"summary":"This keyword defines the debug data associated with rivers to be written to the debug file (*.DBG), for when the River option has been activated via the RIVRDIMS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"RIVER","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"DEBUG_CONTROL","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":2,"size_kind":"list"},"RIVRPROP":{"name":"RIVRPROP","sections":["SCHEDULE"],"supported":false,"summary":"The RIVRPROP keyword modifies the individual reaches in a river structure of a previously characterized river system using the RIVERSYS and the REACHES keywords in the SCHEDULE section. The River option must be activated via the RIVRDIMS keyword in the RUNSPEC section in order to use this keyword. RIVRPROP is an alternative and a more concise way to changing the individual reaches in a river structure than the REACHES keyword.","parameters":[{"index":1,"name":"RIVER","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"REACH1","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"REACH2","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"ROUGHNESS","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","expected_columns":4,"size_kind":"list"},"RIVSALT":{"name":"RIVSALT","sections":["SCHEDULE"],"supported":false,"summary":"The RIVSALT keyword defines the injected salt concentration in individual river branches in a previously characterized river system using the RIVERSYS and the REACHES keywords in the SCHEDULE section. The River option must be activated via the RIVRDIMS keyword in the RUNSPEC section in order to use this keyword. In addition, the Brine option must also be enabled via the BRINE keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"RIVER","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"SALINITY","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Mass/LiquidSurfaceVolume"},{"index":3,"name":"BRANCH","description":"","units":{},"default":"","value_type":"STRING"},{"index":4,"name":"REACH","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":4,"size_kind":"list"},"RIVTRACE":{"name":"RIVTRACE","sections":["SCHEDULE"],"supported":false,"summary":"The RIVTRACE keyword defines the injected tracer concentration in individual river branches in a previously characterized river system using the RIVERSYS and the REACHES keywords in the SCHEDULE section. The River option must be activated via the RIVRDIMS keyword in the RUNSPEC section in order to use this keyword. In addition, the Tracer option must also be enabled by the TRACER keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"RIVER","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"TRACER","description":"","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"TC","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":4,"name":"TCUM","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1/LiquidSurfaceVolume"},{"index":5,"name":"BRANCH","description":"","units":{},"default":"","value_type":"STRING"},{"index":6,"name":"REACH","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":6,"size_kind":"list"},"RPTHMG":{"name":"RPTHMG","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, RPTHMG, either enables or disables history match output reporting to the history match file (*.HMD) for the named group, for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"GROUP","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"INCLUDE","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":2,"size_kind":"list"},"RPTHMW":{"name":"RPTHMW","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, RPTHMG, either enables or disables history match output reporting to the history match file (*.HMD) for the named well, for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"GROUP","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"INCLUDE","description":"","units":{},"default":"ON","value_type":"STRING"},{"index":3,"name":"INCLUDE_RFT","description":"","units":{},"default":"OFF","value_type":"STRING"}],"example":"","expected_columns":3,"size_kind":"list"},"RPTSCHED":{"name":"RPTSCHED","sections":["SCHEDULE"],"supported":true,"summary":"This keyword defines the data in the SCHEDULE section that is to be printed to the output print file in human readable format. The keyword has two distinct forms, the first of which consists of the keyword followed by a series of integers on the next line indicating the data to be printed (see the first example). This is the original format in the commercial simulator and was subsequently superseded by the second format. The second format consists of the keyword followed by a series of character strings that indicate the data to be printed. In most cases the character string is the keyword used to define the data in the OPM Flow input deck, for example WELSPECS to defined the basic well definitions.","parameters":[{"index":1,"name":"FIP","description":"Print the fluid in-place report. The parameter is assigned a value, OPTION, using the form FIP = OPTION, where OPTION is an integer variable set to: OPTION = 1 then the report is for the field only. OPTION = 2 then in addition to the field report, a report is produced for each FIPNUM region, as defined by the FIPNUM keyword in the REGIONS section. Note the commercial simulator also prints the flows to other regions as well as the flows from the wells. This additional reporting option has not been implemented in OPM Flow. OPTION = 3 then in addition to the above, a balance report is also produced for fluid in-place regions defined by the FIP keyword in the REGIONS section.","units":{},"default":"FIP=2","value_type":"STRING"},{"index":2,"name":"FIPRESV","description":"Print the reservoir volumes in-place report.","units":{},"default":"None"},{"index":3,"name":"NOTHING","description":"Switches off all printed reports in the SCHEDULE section.","units":{},"default":"N/A"},{"index":4,"name":"SALT","description":"Print grid block salt concentration values. Note this is an OPM Flow specific keyword.","units":{},"default":"N/A"},{"index":5,"name":"RESTART","description":"RESTART defines the frequency at which the restart data for restarting a run is written to the RESTART file. The parameter is assigned a value, OPTION, using the form RESTART = OPTION, where OPTION is an integer variable set to: OPTION = 1 then the restart files are written at every report time, but only the last one in the run is kept. This minimizes the restart file size but only the final results are stored, limiting the visualization in OPM ResInsight. OPTION = 2 then the phase inter-blocks are written to the restart files, in addition to the standard data. OPTION = 3 then the fluid in-place and phase potentials are also written to the restart file. OPTION = 6 then the restart files are written at every time step. See the RPTRST keyword in the SOLUTION section for a more flexible way to write out restart files.","units":{},"default":""},{"index":6,"name":"WELLS","description":"The WELLS option turns on production and injection rate and cumulative volume reporting for produced and injected fluids. The parameter has several levels of reporting details set by the assigned OPTION value, using the form WELLS = OPTION, where OPTION is an integer variable set to: OPTION = 1 report volumes at the well level. OPTION = 2 report volumes at the well and the well connection levels. OPTION = 3 report volumes for layer totals. OPTION = 4 report volumes for layer totals and for wells. OPTION = 5 report volumes for layer totals and for wells and well connections. Only OPTION equal to one is supported by OPM Flow.","units":{},"default":"WELLS=1"},{"index":7,"name":"WELSPECS","description":"WELSPECS switches on reporting of the well connections, wells and groups at each report time step. There are numerous reports associated with this option. Unlike the other reporting parameters that produce a report for each reporting time step, the WELSPECS report option only produces a report if an associated keyword has been activated at the current reporting time step. For example, if the reporting time steps are January, February, and March 2020, and the RPTSCHED WELSPECS option is activated in January, with wells OP01 and OP02 being declared via the WELSPECS and COMPDAT keywords, then a report will be printed for January for these two wells. If there are no further well activations until March, with well OP03 being declared, then there will be no report for February, and only well OP03 will reported at the March reporting time step.","units":{},"default":""}],"example":"The first example shows the original format of this keyword.\n--\n-- DEFINE SCHEDULE SECTION REPORT OPTION (ORIGINAL FORMAT)\n--\nRPTSCHED\n1 2*0 1 3*1 /\nThe next example shows the second format of the keyword.\n-- ==============================================================================\n--\n-- SCHEDULE SECTION\n--\n-- ==============================================================================\nSCHEDULE\n-- ------------------------------------------------------------------------------\n-- SCHEDULE SECTION - 2000-01-01\n-- ------------------------------------------------------------------------------\nRPTSCHED\n'WELLS=2' 'WELSPECS' 'CPU=2' 'FIP=2' /\nDATES\n1 JAN 2000 /\n/\nRPTSCHED\n'NOTHING' /\nDATES\n1 FEB 2000 /\n1 MAR 2000 /\n1 APR 2000 /\n1 MAY 2000 /\n1 JUN 2000 /\n1 JLY 2000 /\n1 AUG 2000 /\n1 SEP 2000 /\n1 OCT 2000 /\n1 NOV 2000 /\n1 DEC 2000 /\n/\nIn the above example monthly reporting time steps have been used with a SCHEDULE section report on the January 1, 2000; after which all reports are switched off for the subsequent reporting time steps.\n| Note Unlike the other reporting keywords in the RUNSPEC, GRID, EDIT, PROPS and SOLUTION keywords, the requested reports on the this keyword remain in effect until they are switched off by this keyword, that is, the reports are written out every report time step until requested to stop. Use the ‘NOTHING’ parameter to switch off all reporting. |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Note Note that the “PORV” quantity in the FIP (Balance) Report, as shown in Figure 12.6, is reported at reference conditions, meaning there is no pressure dependence involved. However, the “TOTAL PORE VOLUME” values in the Reservoir Volumes Report (Figure 12.7) are pressure dependent pore volumes. Thus, for region one the “PORV” value is 44,729,956 rm3 (Figure 12.6) and the “TOTAL PORE VOLUME” (Figure 12.7) is 44,719,142 rm3. This is the same as the commercial simulator. |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"fixed","size_count":1,"variadic_record":true},"SCDATAB":{"name":"SCDATAB","sections":["SCHEDULE"],"supported":false,"summary":"SCDATAB defines well connection Productivity Index (“PI”) reduction multipliers versus scale deposited per unit length of the perforated interval tables, for when the Scale Deposition option has been activated by declaring the dimensions of the scaling deposition tables using the SCDPDIMS keyword in the RUNSPEC section. The SCDATAB tables are allocated to individual wells using the WSCTAB keyword and the rate of scale accumulation around the well connections is given by the SCDPTAB keyword; both keywords are in the SCHEDULE section.","parameters":[{"index":1,"name":"SCALE_DATA","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":["1","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"SCDETAB":{"name":"SCDETAB","sections":["SCHEDULE"],"supported":false,"summary":"SCDETAB defines well connection karst314\n Karst is a topography formed from the dissolution of soluble rocks such as limestone, dolomite, and gypsum. Karst aquifers are characterized by a network of conduits and caves, with the conduits and caves draining the pore space between the limestone grains (intergranular or primary porosity) and the fractures (secondary porosity) formed by joints, bedding planes, and faults. aquifer properties for modeling scale deposited by dissolution of calcite from the aquifer water, for when the Scale Deposition option has been activated by declaring the dimensions of the scaling deposition tables using the SCDPDIMS keyword in the RUNSPEC section. The SCDETAB tables are allocated to individual wells using the WSCTAB keyword in the SCHEDULE section.","parameters":[{"index":1,"name":"SCALE_DATA","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":["1","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"SCDPTAB":{"name":"SCDPTAB","sections":["SCHEDULE"],"supported":false,"summary":"SCDATAB defines the well connection scale deposition rate as a function of sea water flow rate, for when the Scale Deposition option has been activated by declaring the dimensions of the scaling deposition tables using the SCDPDIMS keyword in the RUNSPEC section. The SCDATAB tables are allocated to individual wells using the WSCTAB keyword and the sea water fraction is based on a water tracer entered via the SCDPTRAC keyword; both keywords are in the SCHEDULE section.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["1","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"SCDPTRAC":{"name":"SCDPTRAC","sections":["SCHEDULE"],"supported":false,"summary":"The SCDPTRAC keyword is used to allocate an existing passive water tracer defined by the TRACER keyword in the PROPS section, to represent the sea water flowing into a well connection as a fraction of the total water influx. The keyword is used together with the SCDPTAB keyword in the SCHEDULE section to calculated the volume of scale deposited around the well connections.","parameters":[{"index":1,"name":"NAME","description":"A three letter character string defining the tracer’s name that has previously been defined by the TRACER keyword in the PROPS section","units":{},"default":"None","value_type":"STRING"}],"example":"In the PROPS section define a tracer in the water phase, for example:\n--\n-- DEFINE TRACER NAMES\n--\n-- TRACER TRACER\n-- NAME PHASE\n-- ------ ------\nTRACER\n'SEA' 'WAT' / SEA WATER TRACER\n/\nThen in the SCHEDULE section allocate the previously defined water tracer as a sea water tracer to be used with the scale deposition facility, that is:\n--\n-- ALLOCATE SEA WATER TRACER FOR SCALE DEPOSITION\n--\n-- TRACER\n-- NAME\n-- ------\nSCDPTRAC\n'SEA' / SEA WATER TRACER\n/","expected_columns":1,"size_kind":"fixed","size_count":1},"SCHEDULE":{"name":"SCHEDULE","sections":["SCHEDULE"],"supported":null,"summary":"The SCHEDULE activation keyword marks the end of the SUMMARY section and the start of the SCHEDULE section that defines the group and well definitions, operating and economic constraints, as well as how OPM Flow should advance through time. Numerical controls are also defined in this section and all parameters can be varied through time.","parameters":[],"example":"-- ==============================================================================\n--\n-- SCHEDULE SECTION\n--\n-- ==============================================================================\nSCHEDULE\nThe above example marks the end of the SUMMARY section and the start of the SCHEDULE section in the OPM Flow data input file.","size_kind":"none","size_count":0},"SEPVALS":{"name":"SEPVALS","sections":["SCHEDULE"],"supported":false,"summary":"The SEPVALS keyword defines the initial and subsequent separator oil formation volume factor (Bo) and Gas Oil Ratio (“GOR” or Rs). The facility is used in black-oil modeling to re-scale the PVT data entered via the PROPS section, based on the saturation point oil formation volume factor (Bob) and the initial saturated gas-oil ratio (Rsi) entered on the SEPVALS keyword. The first occurrence of this keyword sets the initial conditions and must be followed by the GSEPCOND keyword that assigns previously defined separators to a group.","parameters":[{"index":1,"name":"SEPARATOR","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"BO","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"RS","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"}],"example":"","expected_columns":3,"size_kind":"list"},"SIMULATE":{"name":"SIMULATE","sections":["SCHEDULE"],"supported":false,"summary":"SIMULATE switches the mode of the simulation to run simulation mode from the data input checking mode activated by the NOSIM keyword in the SCHEDULE section. Note that if NOSIM has been used in the RUNSPEC section then SIMULATE will have no effect.","parameters":[],"example":"The example below switches OPM Flow to no simulation mode for data checking of the input deck.\n--\n-- ACTIVATE SIMULATION MODE TO RUN THE MODEL\n--\nSIMULATE","size_kind":"none","size_count":0},"SKIPREST":{"name":"SKIPREST","sections":["SCHEDULE"],"supported":null,"summary":"This keyword turns on skipping of keywords up to the start of the restart point, as defined on the RESTART keyword in the RUNSPEC section. The RESTART keyword defines the parameters to restart the simulation from a previous run that has written a RESTART file out to disk. Activating the SKIPREST keyword causes the simulator to only read in data it requires for restarting the run up to the RESTART point (RSNUM on the RESTART keyword in the SOLUTION section). Note that certain keywords always need to be present in a restart run in the SCHEDULE section as the data is not stored on the RESTART file, for example the VFP tables (VFPPROD and VFPINJ keywords). The SKIPREST keyword automatically processes the input deck and reads the required data.","parameters":[],"example":"The example below defines a restart from the previously run NOR-OPM-A01 case at time step number 40.\n-- ==============================================================================\n--\n-- SOLUTION SECTION\n--\n-- ==============================================================================\nSOLUTION\n--\n-- FLEXIBLE RESTART FROM PREVIOUS SIMULATION RUN\n--\n-- FILE RESTART RESTART FILE\n-- NAME NUMBER TYPE FORMAT\nRESTART\n'NOR-OPM-A01' 40 1* 1* /\nThen in the SCHEDULE section the SKIPREST keyword is used to correctly read in the schedule data up to the RESTART point.\n-- ==============================================================================\n--\n-- SCHEDULE SECTION\n--\n-- ==============================================================================\nSCHEDULE\n--\n-- ACTIVATE SKIPREST OPTION TO AVOID MODIFYING SCHEDULE SECTION\n--\nSKIPREST","size_kind":"none","size_count":0},"SLAVES":{"name":"SLAVES","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, SLAVES, defines the name of the slave reservoirs and their associated simulation input files, for when the Reservoir Coupling option has been declared active by the GRUPMAST and SLAVES keywords in the SCHEDULE section.","parameters":[{"index":1,"name":"SLAVE_RESERVOIR","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"SLAVE_ECLBASE","description":"","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"HOST_NAME","description":"","units":{},"default":"","value_type":"STRING"},{"index":4,"name":"DIRECTORY","description":"","units":{},"default":"","value_type":"STRING"},{"index":5,"name":"NUM_PE","description":"","units":{},"default":"1","value_type":"INT"}],"example":"","expected_columns":5,"size_kind":"list"},"SOURCE":{"name":"SOURCE","sections":["SCHEDULE"],"supported":false,"summary":"The SOURCE keyword defines a mass and heat source term for a given pseudo component in the specified grid block.","parameters":[{"index":1,"name":"I","description":"A positive integer greater than zero and less than or equal to NX that defines the location of the source term in the I-direction.","units":{},"default":"None","value_type":"INT"},{"index":2,"name":"J","description":"A positive integer greater than zero and less than or equal to NY that defines the location of the source term in the J-direction.","units":{},"default":"None","value_type":"INT"},{"index":3,"name":"K","description":"A positive integer greater than zero and less than or equal to NZ that defines the location of the source term in the K-direction.","units":{},"default":"None","value_type":"INT"},{"index":4,"name":"COMP","description":"A defined character string that defines the pseudo component to be injected by the source term, COMP should be set to one of the following character strings: OIL: the source term will inject oil. GAS: the source term will inject gas. WATER: the source term will inject water. SOLVENT: the source term will inject solvent. POLYMER: the source term will inject polymer. MICR: the source term will inject microbes. OXYG: the source term will inject oxygen. UREA: the source term will inject urea. NONE: no pseudo component specified. The SOLVENT or POLYMER option should only be specified if the solvent or polymer model has been activated by the SOLVENT or POLYMER keyword respectively in the RUNSPEC section. MICR, OXYG, or UREA requires the MICP keyword. A pseudo component must be specified if the mass injection rate is non-zero.","units":{},"default":"NONE","value_type":"STRING","options":["OIL","GAS","WATER","SOLVENT","POLYMER","MICR","OXYG","UREA","NONE"]},{"index":5,"name":"RATE","description":"A real value that defines the source term’s mass injection rate of the specified component COMP.","units":{"field":"lb/day","metric":"kg/day","laboratory":"gm/hour"},"default":"0.0","value_type":"DOUBLE","dimension":"Mass/Time"},{"index":6,"name":"HRATE","description":"A real value that defines the source term’s heat injection rate1. The heat injection rate should only be specified if the thermal model has been activated by the THERMAL keyword in the RUNSPEC section.","units":{"field":"Btu/day","metric":"kJ/day","laboratory":"J/hour"},"default":"0.0","value_type":"DOUBLE","dimension":"Energy/Time"},{"index":7,"name":"TEMP","description":"A real value that defines the temperature of the injected component1. The temperature of the source term should only be specified if the thermal model has been activated by the THERMAL keyword in the RUNSPEC section.","units":{"field":"°F","metric":"°C","laboratory":"°C"},"default":"None","value_type":"DOUBLE","dimension":"Temperature"}],"example":"The first example adds two source terms to block (I=2, J=4, K=6) that inject gas at a mass flow rate of 25,000 lb/day and inject water at a mass flow rate of 1,000 lb/day respectively.\n--\n-- DEFINE SOURCE TERM\n--\n-- I J K COMP MASS HEAT TEMP\n-- -------------- RATE RATE\nSOURCE\n2 4 6 GAS 25000 1* 1* /\n2 4 6 WATER 1000 1* 1* /\n/\nThe second example adds a source term to block (I=2, J=4, K=6) that injects gas at a mass flow rate of 25,000 lb/day and a heat injection rate of 1.25 × 106 Btu/day in a thermal black-oil simulation.\n--\n-- DEFINE SOURCE TERM\n--\n-- I J K COMP MASS HEAT TEMP\n-- -------------- RATE RATE\nSOURCE\n2 4 6 GAS 25000 1.25E6 1* /\n/\nThe third example adds a source term to block (I=2, J=4, K=6) that injects gas at a mass flow rate of 25,000 lb/day and a temperature of 200°F in a thermal black-oil simulation.\n--\n-- DEFINE SOURCE TERM\n--\n-- I J K COMP MASS HEAT TEMP\n-- -------------- RATE RATE\nSOURCE\n2 4 6 GAS 25000 1* 200 /\n/","expected_columns":7,"size_kind":"list"},"SWINGFAC":{"name":"SWINGFAC","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, SWINGFAC, defines the gas contract parameters, swing factor and the monthly seasonal profile factor, for when there is a single gas contract being used in the model. The keyword is used with the Gas Field Operations option which is activated by the GASFIELD keyword in the RUNSPEC section. Gas contracts are commonly based on a Daily Contract Quantity (“DCQ”) that determines the gas rate that the field should be produced at, which is normally expressed as a multiple of the DCQ, for example 1.33, and is often referred to as the “swing factor”. Some gas contracts also define a maximum DCQ (“Max DCQ”) and/or a minimum take or pay DCQ (“Min DCQ”), as well as seasonal demand characteristics. For example, gas rates may be set higher in the winter months in order to meet heating demand compared with summer months in colder climates, and the opposite in warmer climates where air conditioning demand is high.","parameters":[{"index":1,"name":"SWING_FACTOR1","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":2,"name":"SWING_FACTOR2","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":3,"name":"SWING_FACTOR3","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":4,"name":"SWING_FACTOR4","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":5,"name":"SWING_FACTOR5","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":6,"name":"SWING_FACTOR6","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":7,"name":"SWING_FACTOR7","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":8,"name":"SWING_FACTOR8","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":9,"name":"SWING_FACTOR9","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":10,"name":"SWING_FACTOR10","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":11,"name":"SWING_FACTOR11","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":12,"name":"SWING_FACTOR12","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":13,"name":"PROFILE_FACTOR1","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":14,"name":"PROFILE_FACTOR2","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":15,"name":"PROFILE_FACTOR3","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":16,"name":"PROFILE_FACTOR4","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":17,"name":"PROFILE_FACTOR5","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":18,"name":"PROFILE_FACTOR6","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":19,"name":"PROFILE_FACTOR7","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":20,"name":"PROFILE_FACTOR8","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":21,"name":"PROFILE_FACTOR9","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":22,"name":"PROFILE_FACTOR10","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":23,"name":"PROFILE_FACTOR11","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":24,"name":"PROFILE_FACTOR12","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"| [Q sub{month}`=` DCQ times SWINGFAC sub{ month }] | (12.32) |\n|---------------------------------------------------|---------|","expected_columns":24,"size_kind":"fixed","size_count":1},"TIGHTEN":{"name":"TIGHTEN","sections":["SCHEDULE"],"supported":false,"summary":"The TIGHTEN keyword tightens up or slackens the numerical controls for the linear, non-linear and material balance convergence targets and also tightens or relaxes the maximum values for the aforementioned parameters. The keyword should be used with caution as it may result in significantly increasing the run times.","parameters":[{"index":1,"name":"FACTOR","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","expected_columns":1,"size_kind":"list"},"TIGHTENP":{"name":"TIGHTENP","sections":["SCHEDULE"],"supported":false,"summary":"The TIGHTENP keyword is similar to the TIGHTEN keyword in the SCHEDULE section, in that it tightens up or slackens the numerical controls for the linear, non-linear and material balance convergence targets and also tightens or relaxes the maximum values for the aforementioned parameters. However, TIGHTENP allows for greater flexibility as there are four parameters on this keyword, as opposed to just one on the TIGHTEN keyword, that can be used to modify the numerical controls. The keyword should be used with caution as it may result in significantly increasing the run times.","parameters":[{"index":1,"name":"LINEAR_FACTOR","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":2,"name":"MAX_LINEAR","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"NONLINEAR_FACTOR","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":4,"name":"MAX_NONLINEAR","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":4,"size_kind":"fixed","size_count":1},"TIME":{"name":"TIME","sections":["SCHEDULE"],"supported":false,"summary":"This keyword advances the simulation to a given cumulative report time after which additional keywords may be entered to instruct OPM Flow to perform additional functions via the SCHEDULE section keywords, or further TIME keywords may be entered to advance the simulator to the next report time.","parameters":[{"index":1,"name":"TIME","description":"A vector of real positive numbers that define the cumulative length of the of report times.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"None","value_type":"DOUBLE","dimension":"Time"}],"example":"The fist example shows how to advance the simulation three years using the TIME keyword, from the given start date of January 1, 2022 set via the START keyword in the RUNSPEC section.\n-- ==============================================================================\n--\n-- SCHEDULE SECTION\n--\n-- ==============================================================================\nSCHEDULE\n-- ------------------------------------------------------------------------------\n-- SCHEDULE SECTION - 2022-01-01\n-- ------------------------------------------------------------------------------\n--\n-- ADVANCE SIMULATION BY REPORTING TIME\n--\nTIME\n365.25 730.50 1095.75\n/\nThe second example shows the same advance but using the TSTEP keyword instead.\n Atgeirr Rasmussen\n 2017-09-22T12:22:06.652621000\n AFR\n Again, 2020 has 366 days.\n \n David Baxendale\n 2017-10-02T19:01:11.673000000\n DBx\n Reply to Atgeirr Rasmussen (09/22/2017, 12:22): \"...\"\n I changed the year to simplify the example.\nAgain, 2020 has 366 days.\nReply to Atgeirr Rasmussen (09/22/2017, 12:22): \"...\"\nI changed the year to simplify the example.\n-- ==============================================================================\n--\n-- SCHEDULE SECTION\n--\n-- ==============================================================================\nSCHEDULE\n-- ------------------------------------------------------------------------------\n-- SCHEDULE SECTION - 2022-01-01\n-- ------------------------------------------------------------------------------\nRPTSCHED\n'WELLS=2' 'WELSPECS' 'CPU=2' FIP=2' /\n--\n-- ADVANCE SIMULATION BY REPORTING TIME\n--\nTSTEP\n3*365.25\n/\nAgain, if the simulated production targets are actual production data or the results are going to be used in economic evaluations then the DATES keyword may be more useful in advancing the simulation via the reporting time steps, as the exact dates will be honored.","size_kind":"fixed","size_count":1,"variadic_record":true},"TSTEP":{"name":"TSTEP","sections":["SCHEDULE"],"supported":null,"summary":"This keyword advances the simulation to a given report time after which additional keywords may be entered to instruct OPM Flow to perform additional functions via the SCHEDULE section keywords, or further TSTEP keywords may be entered to advance the simulator to the next report time.","parameters":[{"index":1,"name":"TSTEP","description":"A vector of real positive numbers that define the length of the time intervals to subsequent report steps. Repeat counts may be used, for example 10*365.25.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"None","value_type":"DOUBLE","dimension":"Timestep"}],"example":"The first example shows how to advance the simulation via the reporting time steps from the given start date of January 1, 2022 set via the START keyword in the RUNSPEC section, to the next year, without any actions or reporting taking place.\n-- ==============================================================================\n--\n-- SCHEDULE SECTION\n--\n-- ==============================================================================\nSCHEDULE\n-- ------------------------------------------------------------------------------\n-- SCHEDULE SECTION - 2022-01-01\n-- ------------------------------------------------------------------------------\n--\n-- ADVANCE SIMULATION BY REPORTING TIME\n--\n-- JAN FEB MAR APR MAY JUN JLY AUG SEP OCT NOV DEC\nTSTEP\n31 28 31 30 31 30 31 31 30 31 30 31\n/\nThe second example is similar to the previous example but with quarterly reporting time steps used instead based on [365.25 over 4 = 91.3125]days per quarterdays per quarter\n-- ==============================================================================\n--\n-- SCHEDULE SECTION\n--\n-- ==============================================================================\nSCHEDULE\n-- ------------------------------------------------------------------------------\n-- SCHEDULE SECTION - 2022-01-01\n-- ------------------------------------------------------------------------------\nRPTSCHED\n'WELLS=2' 'WELSPECS' 'CPU=2' FIP=2' /\n--\n-- ADVANCE SIMULATION BY REPORTING TIME\n--\n-- QUARTERLY\nTSTEP\n4*91.3125\n/\nAgain, if the simulated production targets are actual production data or the results are going to be used in economic evaluations then the DATES keyword may be more useful in advancing the simulation via the reporting time steps, as the exact dates will be honored.","size_kind":"fixed","size_count":1,"variadic_record":true},"TUNING":{"name":"TUNING","sections":["SCHEDULE"],"supported":null,"summary":"The TUNING keyword defines the parameters used to control the commercial simulator’s time stepping and numerical convergence for the global grid. The keyword is similar to the TUNINGDP keyword in the SCHEDULE section that is optimized for high throughput runs. The keyword is mostly ignored by OPM Flow; however, the simulator can be instructed to read some parameters from the TUNING keyword if the appropriate command line parameter has been activated (see section 2.2Running OPM Flow 2023-04 From The Command Line).","parameters":[{"index":1,"name":"TSINIT","description":"TSINIT is a positive real value that defines the maximum length of the next time step. Note that whenever the keyword is used TSINIT is always set back to the default value of one, unless explicitly over written.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"1.0","record":1,"value_type":"DOUBLE","dimension":"Time"},{"index":2,"name":"TSMAXZ","description":"TSMAXZ is a positive real value that defines the maximum length of time steps following the next time step (TSINIT).","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"365.0","record":1,"value_type":"DOUBLE","dimension":"Time"},{"index":3,"name":"TSMINZ","description":"TSMINZ is a positive real value that defines the minimum length of all time steps.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"0.1","record":1,"value_type":"DOUBLE","dimension":"Time"},{"index":4,"name":"TSMCHP","description":"TSMCHP is a positive real value that sets the minimum time step length that can be chopped.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"0.15","record":1,"value_type":"DOUBLE","dimension":"Time"},{"index":5,"name":"TSFMAX","description":"TSFMAX is a positive real value that specifies the maximum growth rate a time step can be increased by, subject to the maximum allowable time step size set by TSMAXZ. For example, if the current time step has converged at 10 days and TSFMAX is set to the default value, then the next time step will be 3.0 x 10 days, that is 30 days provided it is less than TSMAXZ.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"3.0","record":1,"value_type":"DOUBLE"},{"index":6,"name":"TSFMIN","description":"TSFMIN is a positive real value that specifies the minimum decay rate a time step can be decreased by, subject to the minimum allowable time step size set by TSMINZ. For example, if the current time step has not converged at 10 days and TSFMIN is set to the default value, then the next time step will be 0.3 x 10 days, that is the maximum of 3 days and TSMINZ.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.3","record":1,"value_type":"DOUBLE"},{"index":7,"name":"TSFCNV","description":"TSFCNV is a positive real value that specifies the decay rate a time step can be decreased by after a convergence failure.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.1","record":1,"value_type":"DOUBLE"},{"index":8,"name":"TFDIFF","description":"TFDIFF is a positive real value that sets the time step growth factor of the time step after a convergence failure. For example, if the chopped current convergent time step is 10 days and TFDIFF is set to the default value, then the time step will be increased to 1.25 x 10 days, that is the minimum of 12.5 days and TSMAXZ.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.25","record":1,"value_type":"DOUBLE"},{"index":9,"name":"THRUPT","description":"THRURT is a positive real value that specifies the maximum throughput ratio over a time step.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0 x 1020","record":1,"value_type":"DOUBLE"},{"index":10,"name":"TMAXWC","description":"TMAXWC is a positive real value that defines maximum allowed time step after a well event; for example, when a well is opened or closed, etc.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"None","record":1,"value_type":"DOUBLE","dimension":"Time"},{"index":1,"name":"TRGTTE","description":"TRGTTE is a positive real value that sets the target time truncation error.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.1","record":2,"value_type":"DOUBLE"},{"index":2,"name":"TRGCNV","description":"TRGCNV is a positive real value that defines the target non-linear convergence error.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.001","record":2,"value_type":"DOUBLE"},{"index":3,"name":"TRGMBE","description":"TRGMBE is a positive real value that specifies the target material balance error.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0 x 10-7","record":2,"value_type":"DOUBLE"},{"index":4,"name":"TRGLCV","description":"TRGLCV is a positive real value that specifies the target linear convergence error.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.0001","record":2,"value_type":"DOUBLE"},{"index":5,"name":"XXXTTE","description":"XXXTTE is a positive real value that sets the maximum time truncation error.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"10.0","record":2,"value_type":"DOUBLE"},{"index":6,"name":"XXXCNV","description":"XXXCNV is a positive real value that defines the maximum non-linear convergence error.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.01","record":2,"value_type":"DOUBLE"},{"index":7,"name":"XXXMBE","description":"XXXMBE is a positive real value that specifies the maximum mass balance error, that is the tolerated mass balance error relative to total mass present.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0 x 10-6","record":2,"value_type":"DOUBLE"},{"index":8,"name":"XXXLCV","description":"XXXLCV is a positive real values that sets the maximum linear convergence error.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.0001","record":2,"value_type":"DOUBLE"},{"index":9,"name":"XXXWFL","description":"XXXWFL is a positive real values that fixes the maximum well flow convergence error.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.001","record":2,"value_type":"DOUBLE"},{"index":10,"name":"TRGFIP","description":"TRGFIP is a positive real value that stipulates the target fluid in-place error in Local Grid Refinements.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.025","record":2,"value_type":"DOUBLE"},{"index":11,"name":"TRGSFT","description":"TRGSFT is a positive real values that defines the target surfactant change when the Surfactant Model is active in the run.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","record":2,"value_type":"DOUBLE"},{"index":12,"name":"THIONX","description":"THIONX is a positive real value used to set the threshold for damping in the ion echange calculation for when the Brine Model is active in the run.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.01","record":2,"value_type":"DOUBLE"},{"index":13,"name":"TRWGHT","description":"TRWGHT is an integer that stipulates the implicitness for active tracer updates within the Newton iterations, and should be set to: The calculation is explicit, that is fully decoupled. The calculation is implicit, that is fully coupled.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1","record":2,"value_type":"INT"},{"index":1,"name":"NEWTMX","description":"NEWTMX is a positive integer greater or equal to NEWTMN that stipulates the maximum number of Newton iterations for a time step.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"12","record":3,"value_type":"INT"},{"index":2,"name":"NEWTMN","description":"NEWTMN is a positive integer that is less or equal to NEWTMX that defines the minimum number of Newton iterations for a time step.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1","record":3,"value_type":"INT"},{"index":3,"name":"LITMAX","description":"LITMAX is a positive integer greater or equal to LITMIN that sets the maximum number of linear iterations within a Newton iteration.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"25","record":3,"value_type":"INT"},{"index":4,"name":"LITMIN","description":"LITMIN is a positive integer less or equal to LITMAX that sets the minimum number of linear iterations within a Newton iteration.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1","record":3,"value_type":"INT"},{"index":5,"name":"MXWSIT","description":"MXWSIT is a positive integer that defines the maximum number of iterations within a well flow calculation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"8","record":3,"value_type":"INT"},{"index":6,"name":"MXWPIT","description":"MXWPIT is a positive integer that stipulates the maximum number of iterations for solving the bottom-hole pressure for wells under tubing head pressure control within a well flow calculation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"8","record":3,"value_type":"INT"},{"index":7,"name":"DDPLIM","description":"DDPLIM is a positive real value that stipulates the maximum pressure change at the last Newton iteration.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1.0 x 106","record":3,"value_type":"DOUBLE","dimension":"Pressure"},{"index":8,"name":"DDSLIM","description":"DDSLIM is a positive real value that sets the maximum saturation change at the last Newton iteration.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0 x 106","record":3,"value_type":"DOUBLE"},{"index":9,"name":"TRGDPR","description":"TRGDPR is a positive real value that defines the target maximum pressure change within a time step.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1.0 x 106","record":3,"value_type":"DOUBLE","dimension":"Pressure"},{"index":10,"name":"XXXDPR","description":"XXXDPR is a positive real value that stipulates the maximum tolerable pressure change within a time step.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","record":3,"value_type":"DOUBLE","dimension":"Pressure"},{"index":11,"name":"MNWRFP","description":"MNWRFP is a positive integer greater than one and less than NEWTMX that defines the minimum number of Newton iterations before invoking the bisection algorithm for when the polymer phase is active in the model via the POLYMER keyword in the RUNSPEC section.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"4","record":3,"value_type":"INT"}],"example":"--\n-- DEFAULT TUNING PARAMETERS\n--\nTUNING\n1.0 365.0 0.1 0.15 3 0.3 0.1 1.25 1E20 1* /\n/\n/\nThe above example explicitly sets the default parameters for OPM Flow for when the appropriate command line parameter has been activated (see section 2.2Running OPM Flow 2023-04 From The Command Line) to instruct the simulator to read the first record of the TUNING keyword.Alternatively one could just use the following to accomplish the same thing.\nTUNING\n/\n/\n/","records_meta":[{"expected_columns":10},{"expected_columns":13},{"expected_columns":11}],"size_kind":"fixed","size_count":3},"TUNINGDP":{"name":"TUNINGDP","sections":["SCHEDULE"],"supported":false,"summary":"The TUNINGDP keyword defines the parameters used for controlling the commercial simulator’s numerical convergence parameters. This keyword is similar to the TUNING keyword in the SCHEDULE section, but the defaults on this keyword are optimized for high throughput runs.","parameters":[{"index":1,"name":"TRGLCV","description":"TRGLCV is a positive real value that specifies the linear convergence error target. The default value is ten times lower than the default value on the TUNING keyword.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.00001","value_type":"DOUBLE"},{"index":2,"name":"XXXLCV","description":"XXXLCV is a positive real values that sets the maximum linear convergence error. The default value is ten times lower than the default value on the TUNING keyword.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.0001","value_type":"DOUBLE"},{"index":3,"name":"TRGDDP","description":"TRGDDP a positive real value that stipulates the maximum pressure change during a Newton iteration that enables the solution to be accepted when the residual pressure is still outside its convergence criteria.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1.0","value_type":"DOUBLE","dimension":"Pressure"},{"index":4,"name":"TRGDDS","description":"TRGDDS a positive real value that sets the maximum saturation change during a Newton iteration that enables the solution to be accepted when the residual saturation is still outside its convergence criteria.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.01","value_type":"DOUBLE"},{"index":5,"name":"TRGDDRS","description":"TRGDDRS a positive real value that sets the maximum gas dissolution factor change during a Newton iteration that enables the solution to be accepted when the residual gas dissolution factor is still outside its convergence criteria. This is an OPM Flow specific item that is not supported by the commercial simulator.","units":{"field":"Mscf/stb","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"0.0","value_type":"DOUBLE","dimension":"GasDissolutionFactor"},{"index":6,"name":"TRGDDRV","description":"TRGDDRV a positive real value that sets the maximum oil dissolution factor change during a Newton iteration that enables the solution to be accepted when the residual oil dissolution factor change is still outside its convergence criteria. This is an OPM Flow specific item that is not supported by the commercial simulator.","units":{"field":"stb/Mscf","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"0.0","value_type":"DOUBLE","dimension":"OilDissolutionFactor"}],"example":"--\n-- DEFAULT TUNINGDP PARAMETERS\n--\nTUNINGDP\n/\nThe above example explicitly sets the default parameters.","expected_columns":6,"size_kind":"fixed","size_count":1},"TUNINGH":{"name":"TUNINGH","sections":["SCHEDULE"],"supported":false,"summary":"Defines the parameters used for controlling the commercial simulator’s numerical convergence parameters. The keyword is similar to the TUNING keyword in the SCHEDULE section, but the defaults on this keyword are optimized for high throughput runs. See section 2.2Running OPM Flow 2023-04 From The Command Lineon how to invoke various numerical schemes via the OPM Flow command line interface.","parameters":[{"index":1,"name":"GRGLCV","description":"GRGLCV is a real positive value that specifies the linear convergence error target.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.0001","value_type":"DOUBLE"},{"index":2,"name":"GXXLCV","description":"GXXLCV is a real positive values that sets the maximum linear convergence error.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.001","value_type":"DOUBLE"},{"index":3,"name":"GMSLCV","description":"GMSLCV is a real positive value that specifies the linear convergence residual reduction.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0 x 10-20","value_type":"DOUBLE"},{"index":4,"name":"LGTMIN","description":"LGTMIN is a positive integer less or equal to LGTMAX that sets the minimum number of linear iterations within a Newton iteration.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1","value_type":"INT"},{"index":5,"name":"LGTMAX","description":"LGTMAX is a positive integer greater or equal to LGTMIN that sets the maximum number of linear iterations within a Newton iteration.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"25","value_type":"INT"}],"example":"--\n-- DEFAULT TUNINGH PARAMETERS\n--\nTUNINGH\n/\nThe above example explicitly sets the default parameters.","expected_columns":5,"size_kind":"fixed","size_count":1},"TUNINGL":{"name":"TUNINGL","sections":["SCHEDULE"],"supported":false,"summary":"TUNINGL defines the parameters used for controlling the commercial simulator’s numerical convergence parameters for all Local Grid Refinements (\"LGR\"). The keyword is the same as the TUNING keyword in the SCHEDULE section that applies the tuning parameters to the global grid. See section 2.2Running OPM Flow 2023-04 From The Command Lineon how to invoke various numerical schemes via the OPM Flow command line interface.","parameters":[{"index":1,"name":"TSINIT","description":"TSINT is a real positive value that defines the maximum length of the next time step. Note that whenever the keyword is used TSINIT is always set back to the default value of one, unless explicitly over written.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"1.0","record":1,"value_type":"DOUBLE","dimension":"Time"},{"index":2,"name":"TSMAXZ","description":"TSMAXZ is a real positive value that defines the maximum length of the next time step following TSINIT.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"365.0","record":1,"value_type":"DOUBLE","dimension":"Time"},{"index":3,"name":"TSMINZ","description":"TSMINZ is a real positive value that defines the minimum length of all time steps.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"0.1","record":1,"value_type":"DOUBLE","dimension":"Time"},{"index":4,"name":"TSMCHP","description":"TSMCHP is a real positive values that sets the minimum length of all chopped time steps.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"0.15","record":1,"value_type":"DOUBLE","dimension":"Time"},{"index":5,"name":"TSFMAX","description":"TSFMAX is a real positive value that specifies the maximum growth rate a time step can be increased by, subject to the maximum allowable time step size set by TSMAXZ. For example, if the current time step has converged at 10 days and TSFMAX is set to the default value, then the next time step will be 3.0 x 10 days, that is 30 days provided it is less than TSMAXZ.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"3.0","record":1,"value_type":"DOUBLE"},{"index":6,"name":"TSFMIN","description":"TSFMIN is a real positive value that specifies the minimum decay rate a time step can be decreased by, subject to the minimum allowable time step size set by TSMINZ. For example, if the current time step has not converged at 10 days and TSFMAX is set to the default value, then the next time step will be 0.3 x 10 days, that is the maximum of 0.3 days and TSMINZ.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.3","record":1,"value_type":"DOUBLE"},{"index":7,"name":"TSFCNV","description":"TSFCNV real positive value that specifies the decay rate a time step can be decreased by after the number of target iterations has been exceeded.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.1","record":1,"value_type":"DOUBLE"},{"index":8,"name":"TFDIFF","description":"TFDIFFA is a real positive value that sets the time step growth factor of the time step after a convergence failure. For example, if the chopped current convergent time step is 10 days and TFDIFF is set to the default value, then the time step will be increased to 1.25 x 10 days, that is the minimum of 11.25 days and TSMAXZ.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.25","record":1,"value_type":"DOUBLE"},{"index":9,"name":"THRURPT","description":"THRURPT is a real positive value that specifies the maximum throughput ratio over a time step.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0 x 1020","record":1,"value_type":"DOUBLE"},{"index":10,"name":"TMAXWC","description":"TMAXWC is a real double precision value that defines maximum allowed time step after a well event; for example, when a well is opened or closed, etc.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"None","record":1,"value_type":"DOUBLE","dimension":"Time"},{"index":1,"name":"TRGTTE","description":"TRGTTE is a real positive value that sets the time truncation error target.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.1","record":2,"value_type":"DOUBLE"},{"index":2,"name":"TRGCNV","description":"TRGCNV a real positive value that defines the non-linear convergence error.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.001","record":2,"value_type":"DOUBLE"},{"index":3,"name":"TRGMBE","description":"TRGMBE is a real positive value that specifies then target material balance error.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0 x 10-7","record":2,"value_type":"DOUBLE"},{"index":4,"name":"TRGLCV","description":"TRGLCV is a real positive value that specifies the linear convergence error target.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.00001","record":2,"value_type":"DOUBLE"},{"index":5,"name":"XXXTTE","description":"XXXTTE is a real positive value that sets the maximum time truncation error.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"10.0","record":2,"value_type":"DOUBLE"},{"index":6,"name":"XXXCNV","description":"XXXCNV is a real positive value that defines the maximum non-linear convergence error.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.01","record":2,"value_type":"DOUBLE"},{"index":7,"name":"XXXMBE","description":"XXXMBE is a real positive value that specifies the maximum mass balance error, that is the tolerated mass balance error relative to total mass present.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0 x 10-6","record":2,"value_type":"DOUBLE"},{"index":8,"name":"XXXLCV","description":"XXXLCV is a real positive values that sets the maximum linear convergence error.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.0001","record":2,"value_type":"DOUBLE"},{"index":9,"name":"XXXWFL","description":"XXXWFL is a real positive values that fixes the maximum well flow convergence error.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.001","record":2,"value_type":"DOUBLE"},{"index":10,"name":"TRGFIP","description":"TRGFIP is a real positive value that stipulates the target fluid in-place error in Local Grid Refinements.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.025","record":2,"value_type":"DOUBLE"},{"index":11,"name":"TRGSFT","description":"TRGSFT is a real positive values that defines the target surfactant change when the Surfactant Model is active in the run.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","record":2,"value_type":"DOUBLE"},{"index":12,"name":"THIONX","description":"THIONX is a positive real value used to set the threshold for damping in the ion echange calculation for when the Brine Model is active in the run.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.01","record":2,"value_type":"DOUBLE"},{"index":13,"name":"TRWGHT","description":"TRWGHT is a positive integer that stipulates the implicitness for active tracer updates within the Newton iterations, and should be set to: The calculation is explicit, that is fully decoupled. The calculation is implicit, that is fully coupled.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1","record":2,"value_type":"INT"},{"index":1,"name":"NEWTMX","description":"NEWTMX is a positive integer greater or equal to NEWTMN that stipulates the maximum number of Newton iterations for a time step.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"12","record":3,"value_type":"INT"},{"index":2,"name":"NEWTMN","description":"NEWTMN is a positive integer that is less or equal to NEWTMX that defines the minimum number of Newton iterations for a time step.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1","record":3,"value_type":"INT"},{"index":3,"name":"LITMAX","description":"LITMAX is a positive integer greater or equal to LITMIN that sets the maximum number of linear iterations within a Newton iteration.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"25","record":3,"value_type":"INT"},{"index":4,"name":"LITMIN","description":"LITMIN is a positive integer less or equal to LITMAX that sets the minimum number of linear iterations within a Newton iteration.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1","record":3,"value_type":"INT"},{"index":5,"name":"MXWSIT","description":"MXWSIT is a positive integer that defines the maximum number of iterations within a well flow calculation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"8","record":3,"value_type":"INT"},{"index":6,"name":"MXWPIT","description":"MXWPIT is a positive integer that stipulates the maximum number of iterations for solving the bottom-hole pressure for wells under tubing head pressure control within a well flow calculation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"8","record":3,"value_type":"INT"},{"index":7,"name":"DDPLIM","description":"DDPLIM a real positive value that stipulates the maximum pressure change at the last Newton iteration.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1.0 x 10-6","record":3,"value_type":"DOUBLE","dimension":"Pressure"},{"index":8,"name":"DDSLIM","description":"DDSLIM a real positive value that sets the maximum saturation change at the last Newton iteration.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0 x 10-6","record":3,"value_type":"DOUBLE"},{"index":9,"name":"TRGDPR","description":"TRGDP is a real positive value that defines the target pressure change within a time step.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1.0 x 10-6","record":3,"value_type":"DOUBLE","dimension":"Pressure"},{"index":10,"name":"XXXDPR","description":"XXXDPR is a real positive value that stipulates the maximum tolerable pressure change within a time step.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1.0 x 10-6","record":3,"value_type":"DOUBLE","dimension":"Pressure"},{"index":11,"name":"MNWRFP","description":"MNWRFP is a positive integer greater than one and less than NEWTMX that defines the minimum number of Newton iterations before invoking the bisection algorithm for when the polymer phase is active in the model via the POLYMER keyword in the RUNSPEC section.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"4","record":3,"value_type":"INT"}],"example":"-\n-- DEFAULT TUNINGL PARAMETERS\n--\nTUNINGL\n/\n/\n/\nThe above example explicitly sets the default parameters for all LGRs.","records_meta":[{"expected_columns":10},{"expected_columns":13},{"expected_columns":11}],"size_kind":"fixed","size_count":3},"TUNINGS":{"name":"TUNINGS","sections":["SCHEDULE"],"supported":false,"summary":"TUNINGS defines the parameters used for controlling the commercial simulator’s numerical convergence parameters for individual Local Grid Refinements (\"LGR\"). The keyword is similar to the TUNINGL keyword in the SCHEDULE section that applies the tuning parameters to the all LGRs, except for an additional first record that includes the LGR name.","parameters":[{"index":1,"name":"LGRNAME","description":"A character string of up to eight characters in length that defines the LGR name for which the tuning data is being being defined.","units":{},"default":"None","record":1,"value_type":"STRING"},{"index":1,"name":"TSINIT","description":"TSINT is a real positive value that defines the maximum length of the next time step. Note that whenever the keyword is used TSINIT is always set back to the default value of one, unless explicitly over written.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"1.0","record":2,"value_type":"DOUBLE","dimension":"Time"},{"index":2,"name":"TSMAXZ","description":"TSMAXZ is a real positive value that defines the maximum length of the next time step following TSINIT.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"365.0","record":2,"value_type":"DOUBLE","dimension":"Time"},{"index":3,"name":"TSMINZ","description":"TSMINZ is a real positive value that defines the minimum length of all time steps.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"0.1","record":2,"value_type":"DOUBLE","dimension":"Time"},{"index":4,"name":"TSMCHP","description":"TSMCHP is a real positive values that sets the minimum length of all chopped time steps.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"0.15","record":2,"value_type":"DOUBLE","dimension":"Time"},{"index":5,"name":"TSFMAX","description":"TSFMAX is a real positive value that specifies the maximum growth rate a time step can be increased by, subject to the maximum allowable time step size set by TSMAXZ. For example, if the current time step has converged at 10 days and TSFMAX is set to the default value, then the next time step will be 3.0 x 10 days, that is 30 days provided it is less than TSMAXZ.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"3.0","record":2,"value_type":"DOUBLE"},{"index":6,"name":"TSFMIN","description":"TSFMIN is a real positive value that specifies the minimum decay rate a time step can be decreased by, subject to the minimum allowable time step size set by TSMINZ. For example, if the current time step has not converged at 10 days and TSFMAX is set to the default value, then the next time step will be 0.3 x 10 days, that is the maximum of 0.3 days and TSMINZ.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.3","record":2,"value_type":"DOUBLE"},{"index":7,"name":"TSFCNV","description":"TSFCNV real positive value that specifies the decay rate a time step can be decreased by after the number of target iterations has been exceeded.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.1","record":2,"value_type":"DOUBLE"},{"index":8,"name":"TFDIFF","description":"TFDIFFA is a real positive value that sets the time step growth factor of the time step after a convergence failure. For example, if the chopped current convergent time step is 10 days and TFDIFF is set to the default value, then the time step will be increased to 1.25 x 10 days, that is the minimum of 11.25 days and TSMAXZ.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.25","record":2,"value_type":"DOUBLE"},{"index":9,"name":"THRURPT","description":"THRURPT is a real positive value that specifies the maximum throughput ratio over a time step.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0 x 1020","record":2,"value_type":"DOUBLE"},{"index":10,"name":"TMAXWC","description":"TMAXWC is a real double precision value that defines maximum allowed time step after a well event; for example, when a well is opened or closed, etc.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"None","record":2,"value_type":"DOUBLE","dimension":"Time"},{"index":1,"name":"TRGTTE","description":"TRGTTE is a real positive value that sets the time truncation error target.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.1","record":3,"value_type":"DOUBLE"},{"index":2,"name":"TRGCNV","description":"TRGCNV a real positive value that defines the non-linear convergence error.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.001","record":3,"value_type":"DOUBLE"},{"index":3,"name":"TRGMBE","description":"TRGMBE is a real positive value that specifies then target material balance error.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0 x 10-7","record":3,"value_type":"DOUBLE"},{"index":4,"name":"TRGLCV","description":"TRGLCV is a real positive value that specifies the linear convergence error target.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.00001","record":3,"value_type":"DOUBLE"},{"index":5,"name":"XXXTTE","description":"XXXTTE is a real positive value that sets the maximum time truncation error.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"10.0","record":3,"value_type":"DOUBLE"},{"index":6,"name":"XXXCNV","description":"XXXCNV is a real positive value that defines the maximum non-linear convergence error.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.01","record":3,"value_type":"DOUBLE"},{"index":7,"name":"XXXMBE","description":"XXXMBE is a real positive value that specifies the maximum mass balance error, that is the tolerated mass balance error relative to total mass present.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0 x 10-6","record":3,"value_type":"DOUBLE"},{"index":8,"name":"XXXLCV","description":"XXXLCV is a real positive values that sets the maximum linear convergence error.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.0001","record":3,"value_type":"DOUBLE"},{"index":9,"name":"XXXWFL","description":"XXXWFL is a real positive values that fixes the maximum well flow convergence error.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.001","record":3,"value_type":"DOUBLE"},{"index":10,"name":"TRGFIP","description":"TRGFIP is a real positive value that stipulates the target fluid in-place error in Local Grid Refinements.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.025","record":3,"value_type":"DOUBLE"},{"index":11,"name":"TRGSFT","description":"TRGSFT is a real positive values that defines the target surfactant change when the Surfactant Model is active in the run.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","record":3,"value_type":"DOUBLE"},{"index":12,"name":"THIONX","description":"THIONX is a positive real value used to set the threshold for damping in the ion echange calculation for when the Brine Model is active in the run.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.01","record":3,"value_type":"DOUBLE"},{"index":13,"name":"TRWGHT","description":"TRWGHT is a positive integer that stipulates the implicitness for active tracer updates within the Newton iterations, and should be set to: The calculation is explicit, that is fully decoupled. The calculation is implicit, that is fully coupled.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1","record":3,"value_type":"INT"},{"index":1,"name":"NEWTMX","description":"NEWTMX is a positive integer greater or equal to NEWTMN that stipulates the maximum number of Newton iterations for a time step.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"12","record":4,"value_type":"INT"},{"index":2,"name":"NEWTMN","description":"NEWTMN is a positive integer that is less or equal to NEWTMX that defines the minimum number of Newton iterations for a time step.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1","record":4,"value_type":"INT"},{"index":3,"name":"LITMAX","description":"LITMAX is a positive integer greater or equal to LITMIN that sets the maximum number of linear iterations within a Newton iteration.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"25","record":4,"value_type":"INT"},{"index":4,"name":"LITMIN","description":"LITMIN is a positive integer less or equal to LITMAX that sets the minimum number of linear iterations within a Newton iteration.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1","record":4,"value_type":"INT"},{"index":5,"name":"MXWSIT","description":"MXWSIT is a positive integer that defines the maximum number of iterations within a well flow calculation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"8","record":4,"value_type":"INT"},{"index":6,"name":"MXWPIT","description":"MXWPIT is a positive integer that stipulates the maximum number of iterations for solving the bottom-hole pressure for wells under tubing head pressure control within a well flow calculation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"8","record":4,"value_type":"INT"},{"index":7,"name":"DDPLIM","description":"DDPLIM a real positive value that stipulates the maximum pressure change at the last Newton iteration.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1.0 x 10-6","record":4,"value_type":"DOUBLE","dimension":"Pressure"},{"index":8,"name":"DDSLIM","description":"DDSLIM a real positive value that sets the maximum saturation change at the last Newton iteration.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0 x 10-6","record":4,"value_type":"DOUBLE"},{"index":9,"name":"TRGDPR","description":"TRGDP is a real positive value that defines the target pressure change within a time step.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1.0 x 10-6","record":4,"value_type":"DOUBLE","dimension":"Pressure"},{"index":10,"name":"XXXDPR","description":"XXXDPR is a real positive value that stipulates the maximum tolerable pressure change within a time step.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1.0 x 10-6","record":4,"value_type":"DOUBLE","dimension":"Pressure"},{"index":11,"name":"MNWRFP","description":"MNWRFP is a positive integer greater than one and less than NEWTMX that defines the minimum number of Newton iterations before invoking the bisection algorithm for when the polymer phase is active in the model via the POLYMER keyword in the RUNSPEC section.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"4","record":4,"value_type":"INT"}],"example":"--\n-- DEFAULT TUNINGS PARAMETERS\n--\nTUNINGS\nOP01-LGR\n/\n/\n/\nThe above example explicitly sets the default parameters for the LGR named OP01-LGR","records_meta":[{"expected_columns":1},{"expected_columns":10},{"expected_columns":13},{"expected_columns":11}],"size_kind":"fixed","size_count":4},"UDQ":{"name":"UDQ","sections":["SCHEDULE"],"supported":true,"summary":"This keyword starts the definition of a UDQ section that stipulates the variables and operations used to access the User Defined Quantities features in OPM Flow. UDQ variables can be constants, SUMMARY variables, as defined in the SUMMARY section,or a formula using various mathematical functions together with constants and SUMMARY variables. Available operations include the ASSIGN, DEFINE, UNITS and UPDATE commands that are sub-keywords to the UDQ section keyword.","parameters":[{"index":1,"name":"OPERATOR","description":"OPERATOR is a defined character string that specifies the type of operation to perform, and should be one of the following: ASSIGN: Assigns a constant numerical value to the UDQ defined by VARIABLE and sets the UPDATE status to OFF. DEFINE: Defines a mathematical formula and assigns it to the UDQ defined by VARIABLE. The UDQ is initialized with the formula and the UPDATE status is set to ON. UNITS: Sets the reporting units for the UDQ defined by VARIABLE. The units have no effect on the calculations. The UDQ must already have been defined prior to using this option. UPDATE: Stipulates when the UDQ defined by VARIABLE should be evaluated.","units":{},"default":"","value_type":"RAW_STRING"},{"index":2,"name":"VARIABLE","description":"VARIABLE is a character string of length eight that stipulates the name of the user defined variable that will processed by the OPERATOR command. The first two characters of VARIABLE must be set based on the type of variable being defined, that is: CU: For variables that are associated with connections, for example SUMMARY variable COFR (Connection Oil Flow Rate). FU: For variables that are associated with field data, for example SUMMARY variable FOPR (Field Oil Production Rate). GU: For variables that are associated with groups, for example SUMMARY variable GLPR (Group Liquid Production Rate). RU: For variables that are associated with regions, for example SUMMARY variable RPR (Region Pressure). SU: For variables that are associated with multi-segment wells, for example SUMMARY variable SOFR (Segment Oil Flow Rate). WU: For variables that are associated with wells, for example SUMMARY variable WWCT (Well Water Cut). AU: For variables that are associated with aquifers, for example SUMMARY variable AAQP (Analytical Aquifer Pressure). BU: For variables that are associated with blocks, for example SUMMARY variable BPR (Block oil phase Pressure). OPM Flow currently only supports field, group, segment and well variables (FU*, GU*, SU* and WU*).","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"EXPRESSION","description":"The data type for EXPRESSION is based on the OPERATOR option above, namely if OPERATOR is set to: ASSIGN:EXPRESSION should be a numerical value. DEFINE: EXPRESSION should be a mathematical expression. Allowable tokens for the expression include SUMMARY or UDQ variables, real numbers (can be integers or scientific notation), opening and closing brackets '(' and ')', and basic mathematical operators plus '+', minus '-', multiply '*', divide '/' and exponent '^'. UNITS: EXPRESSION should be a character string (enclosed in quotes if it contains blanks) with a maximum length of eight characters, that declares the units that will used when reporting the UDQ defined by VARIABLE. UPDATE: EXPRESSION should be a defined character string (ON, OFF or NEXT): ON to evaluate the UDQ defined by VARIABLE at all time steps, OFF to not evaluate the UDQ, or NEXT to evaluate the UDQ at the next time step.","units":{},"default":"","value_type":"RAW_STRING"}],"example":"The first example shows how to define some constant field variables used for calculating facilities corrected condensate and Liquefied Petroleum Gas315\n Liquefied Petroleum Gas or LPG consists mainly of propane, propylene, butane, and butylene in various mixtures. It is produced as a by-product of natural gas processing and petroleum refining. The components of LPG are gases at standard conditions. (“LPG “) yields in a wet gas model:\nLiquefied Petroleum Gas or LPG consists mainly of propane, propylene, butane, and butylene in various mixtures. It is produced as a by-product of natural gas processing and petroleum refining. The components of LPG are gases at standard conditions.\n--\n-- DEFINE START OF USER DEFINED QUANTITY SECTION\n--\nUDQ\n--\n-- OPERATOR VARIABLE EXPRESSION\n--\nASSIGN FUNGLYLD 1.100000 / -- Condensate Yield (stb/Mscf)\nASSIGN FUNGLSHK 0.000000 / Condensate Shrinkage Factor to Zero\nASSIGN FULPGYLD 0.065775 / -- LPG Sep Gas Yield (stb/Mscf)\nASSIGN FULPGSHK 0.080410 / LPG Shrinkage Factor\nASSIGN FUFACSHK 0.000935 / Facilities Shrinkage Factor\nASSIGN FUFULSHK 0.052924 / Fuel Utilization\nASSIGN FUDELTA 1E-10 / Value to avoid dividing by zero errors\n/ DEFINE END OF USER DEFINED QUANTITY SECTION\nThe next example is a continuation of this example by showing how one can calculate the adjusted field condensate and LPG rates. Note both examples could be merged into a single UDQ definition but have been stated separately for ease of reference.\n--\n-- DEFINE START OF USER DEFINED QUANTITY SECTION\n--\nUDQ\n--\n-- OPERATOR VARIABLE EXPRESSION\n--\nDEFINE FU_FNGLR FGPR * (FOGR * FUNGLYLD) / Calculate Condensate Rate Field\nUPDATE FU_FNGLR ON /\nUNITS FU_FNGLR STBD /\nDEFINE FU_FLPGR FU_FWGPR * FULPGYLD / Calculate LPG Rate Field\nUPDATE FU_FLPGR ON /\nUNITS FU_FLPGR STBD /\n/ DEFINE END OF USER DEFINED QUANTITY SECTION\nIn the above the DEFINE operator is use to define the equations to calculate the corrected condensate (FU_FNGLR) and LPG rates (FU_FLPGR) with the UPDATE operator set to ON so that the rates are calculate at every time step, and finally, the UNITS operator is used to set the units of the calculated rates.\nThe final example show the use of the UDADIMS and UDQDIMS keywords in the RUNSPEC section, followed by the keywords in the SCHEDULE section that define a UDQ definition that uses the DEFINE operator to calculate adjusted well rates based on an expression. The final set of keywords show how the UDQ defined variables are employed on the WCONPROD keyword to control the production constraints for several wells.\nRUNSPEC SECTION KEYWORDS\n------------------------\n--\n-- USER DEFINED ARGUMENT DIMENSIONS\n-- NO. NOT TOTAL\n-- ARGS USED UDQ\nUDADIMS\n10 1* 10 /\n--\n-- USER DEFINED ARGUMENT DIMENSIONS FACILITY\n-- MAX MAX MAX MAX MAX MAX MAX MAX MAX MAX RAND\n-- FUNCS ITEMS CONNS FIELD GROUP REGS SEGTM WELL AQUF BLCKS OPT\nUDQDIMS\n50 25 0 50 50 0 0 0 0 0 N /\nAnd the SCHEDULE section part of the example is shown below.\nSCHEDULE SECTION KEYWORDS\n--------------------------\n--\n-- DEFINE START OF USER DEFINED QUANTITY SECTION\n--\nUDQ\n--\n-- OPERATOR VARIABLE EXPRESSION\n--\nDEFINE WUOPRL (WOPR OPL01 - 150) * 0.90 / OIL & LIQ CAPACITIES\nDEFINE WULPRL (WLPR OPL01 - 200) * 0.90 / at GEFAC = 0.8995\nDEFINE WUOPRU (WOPR OPU01 - 250) * 0.80 /\nDEFINE WULPRU (WLPR OPU01 - 300) * 0.80 /\n--\nUNITS WUOPRL SM3/DAY / DEFINE REPORTING UNITS\nUNITS WULPRL SM3/DAY / FOR UDQ VARIABLES\nUNITS WUOPRU SM3/DAY /\nUNITS WULPRU SM3/DAY /\n/ DEFINE END OF USER DEFINED QUANTITY SECTION\n--\n-- WELL PRODUCTION WELL CONTROLS\n--\n-- WELL OPEN/ CNTL OIL WAT GAS LIQ RES BHP THP VFP VFP\n-- NAME SHUT MODE RATE RATE RATE RATE RATE PRES PRES TABLE ALFQ\nWCONPROD\nOP01 SHUT GRUP 1* 1* 1* 1* 1* 200.0 /\nOP02 SHUT GRUP 1* 1* 1* 1* 1* 200.0 /\n/\nDATES\n1 FEB 2020 /\n--\n-- WELL PRODUCTION WELL CONTROLS\n--\n-- WELL OPEN/ CNTL OIL WAT GAS LIQ RES BHP THP VFP VFP\n-- NAME SHUT MODE RATE RATE RATE RATE RATE PRES PRES TABLE ALFQ\nWCONPROD\nOP01 OPEN GRUP WUOPRL 1* 1* WULPRL 1* 60.0 /\nOP02 OPEN GRUP WUOPRL 1* 1*","size_kind":"list","variadic_record":true},"UDT":{"name":"UDT","sections":["SCHEDULE"],"supported":true,"summary":"The UDT keyword defines a single multi-dimensional User Defined Table (“UDT”).","parameters":[{"index":1,"name":"NAME","description":"A character string of up to eight characters in length beginning with ‘TU’ that defines the table name.","units":{},"default":"None","record":1},{"index":2,"name":"NDIMS","description":"An integer value between one and MXDIMS that defines the number of dimensions for the table. MXDIMS is the maximum number of UDT table dimensions defined using the UDTDIMS keyword in the RUNSPEC section. OPM Flow only supports one-dimensional tables (NDIMS = 1).","units":{},"default":"None","record":1},{"index":1,"name":"TYPE","description":"A defined character string that defines the type of interpolation for this dimension and must one of the following: ‘NV’ this dimension will use the nearest value. ‘LC’ this dimension will use linear interpolation within the table and clamp to the first or last value respectively for extrapolation. ‘LL’ this dimension will use linear interpolation within the table and linear extrapolation outside of the table. ‘ID’ this dimension will use a string or identifier to select the interpolation point. If no matching interpolation point is found then the lookup will return the value given to undefined UDQ variables as specifed by the DEFAULT value on the UDQPARAM keyword in the RUNSPEC section.","units":{},"default":"None","record":2},{"index":2,"name":"POINTS","description":"A monotonically increasing vector of real values that defines the numerical value of the interpolation points for this dimension if the specified type of interpolation TYPE is either ‘NV’, ‘LC’ or ‘LL’. Otherwise, a vector of character strings of up to eight characters in length defining the ‘ID’.","units":{},"default":"None","record":2},{"index":1,"name":"VALUES","description":"A vector of real values corresponding to each of the interpolations points POINTS in the first dimension.","units":{},"default":"None","record":3}],"example":"The following example shows a one-dimension User Defined Table that will linearly interpolate between values of 100 and 180 for values of FOPR between 100 and 500 and will clamp to the end points for values of FOPR outside this range.\n--\n-- DECLARE USER DEFINED TABLE\n--\nUDT\n-- NAME NDIMS\n'TU_FBHP' 1 /\n-- TYPE POINTS\n'LC' 100.0 500.0 / -- FOPR values\n-- VALUES\n100.0 180.0 / -- FBHP values\n/\n/\n--\n-- DECLARE USER DEFINED QUANTITIES\n--\nUDQ\nASSIGN FU_WBHP 0 /\nDEFINE FU_WBHP0 FU_WBHP /\nDEFINE FU_WBHP (TU_FBHP[FOPR] UMIN WBHP 'PROD') UMIN FU_WBHP0 /\n/\n--\n-- WELL PRODUCTION TARGETS AND CONSTRAINTS\n--\nWCONPROD\n'PROD' 'OPEN' ORAT 500.0 4* FU_WBHP /\n/\nIn the example above, the UDT specifies how the bottom hole pressure limit should reduce as the field oil production rate decreases (note the interpolation point values must be monotone increasing). The User Defined Quantity FU_WBHP uses a lookup value from the UDT in the form TU_BHP[FOPR].","size_kind":"none","size_count":0},"USECUPL":{"name":"USECUPL","sections":["SCHEDULE"],"supported":false,"summary":"The USECUPL keyword causes the simulator to read a Reservoir Coupling file that has been previously created in a master run using the DUMPCUPL keyword in the SCHEDULE section, for when reservoir coupling is invoked by the GRUPMAST and SLAVES keywords in the SCHEDULE section.","parameters":[{"index":1,"name":"BASE","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"FMT","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":2,"size_kind":"fixed","size_count":1},"VFPCHK":{"name":"VFPCHK","sections":["SCHEDULE"],"supported":false,"summary":"The VFPPROD keyword defines production Vertical Flow Performance (“VFP”) tables that are used to determine the outflow or downstream pressure based on the inlet or upstream pressure and the phases flowing through the system. For a well this means the table relates the flowing bottom-hole pressure (“BHP”) to the well’s tubing head pressure (“THP”) based on the oil, gas and water rates (and any artificial lift quantities like gas lift gas), or phases ratios, flowing up the wellbore.","parameters":[{"index":1,"name":"VFPCHK","description":"VFPCHK is a real positive value that defines the BHP pressure above which crossing VFP curves will be ignored. Setting VFPCHK to a large number like the default value number will cause all crossing curves to be checked. Also if the keyword is omitted from the input deck then the check is performed using the default value.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1.010","value_type":"DOUBLE","dimension":"Pressure"}],"example":"Here the example sets the maximum BHP to be 1.0 x106 above which crossing VFP curves will be ignored.\n--\n-- DEFINE PRODUCTION VFP CHECK MAX BHP\n--\n-- MXBHP\nVFPCHK\n1.0E6\n/\n| Note One reason for external programs generating crossing VFP curves is that the curves have been generated with too much resolution. For example, if the GOR entries has been generated with values of 100, 150, 200, 250, 300, 350, 400, 450 and 500, then use a geometric spacing instead to generated the VFP table, that is: 100, 300, 900. This will enable the simulator to interpolate the curves consistently and avoid crossing VFP curves. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":1,"size_kind":"fixed","size_count":1},"VFPINJ":{"name":"VFPINJ","sections":["SCHEDULE"],"supported":null,"summary":"The VFPINJ keyword defines injection Vertical Flow Performance (“VFP”) tables that are used to determine the outflow or downstream pressure based on the inlet or upstream pressure and the phases being injected into the system. For an injection well this means the table relates the flowing bottom-hole pressure (“BHP”) to the well’s tubing head pressure (“THP”) based on the oil, gas or water injection rates. The table is also used to describe the pressure relationship when the network option is being used, although the Network option is not currently implemented in OPM Flow. In this case the table describes the pipeline pressure behavior from the HIGHER group (inlet node) to the LOWER group (outlet node) given the current flowing conditions (the group relationship is defined by the GRUPTREE keyword in SCHEDULE section).","parameters":[{"index":1,"name":"VFPTAB","description":"A positive integer greater than zero and less than or equal to the MXVFPTAB variable as defined on the VFPIDIMS keyword in the RUNSPEC section, that defines the vertical flow performance table number.","units":{},"default":"None","record":1,"value_type":"INT"},{"index":2,"name":"VFPREF","description":"A real positive value that defines the reference depth used to generate this VFPINJ table data set. OPM Flow automatically corrects any difference between VFPREF and the BHPREF on the WELSPECS and WPAVDEP keywords in the SCHEDULE section, using the current hydrostatic head.","units":{},"default":"None","record":1,"value_type":"DOUBLE","dimension":"Length"},{"index":3,"name":"FLO","description":"A defined character string that defines the injection phases, and should be set to one of the following character strings: OIL: for injecting phase being oil. GAS: for injecting phase being gas. WAT: for injecting phase being water.","units":{},"default":"None","record":1,"value_type":"STRING","options":["OIL","GAS","WAT"]},{"index":4,"name":"VFPTYPE","description":"A defined character string that should be defaulted or set equal to THP.","units":{},"default":"THP","record":1,"value_type":"STRING"},{"index":5,"name":"VFPUNITS","description":"A defined character string that specifies the units system for the VFP table. An error message is output if this is not the same as the model units.","units":{"field":"FIELD","metric":"METRIC","laboratory":"LAB"},"default":"Model units","record":1,"value_type":"STRING"},{"index":6,"name":"VFPVALUE","description":"A defined character string that defines the type of data in the VFP-DATA vector. This should be defaulted or set equal to BHP.","units":{},"default":"BHP","record":1,"value_type":"STRING"},{"index":1,"name":"FLO-DATA","description":"A real positive monotonically increasing vector that defines the numerical values of the injection phase declared by the FLO variable. The number of entries must greater than two and less than or equal to MXMFLO as defined on the VFPIDIMS keyword in the RUNSPEC section.","units":{"field":"Liquid: stb Gas: Mscf","metric":"Liquid: sm3 Gas: sm3","laboratory":"Liquid: scc Gas: scc"},"default":"None","record":2,"value_type":"DOUBLE"},{"index":1,"name":"THP-DATA","description":"A real positive monotonically increasing vector that defines the numerical values of the tubing head pressure values. The number of entries must be greater than two and less than or equal to MXMTHP as defined on the VFPIDIMS keyword in the RUNSPEC section.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","record":3,"value_type":"DOUBLE"},{"index":1,"name":"NTHP","description":"This data record consists of an integer value that defines the index of THP values entered via the THP-DATA records on this keyword. For example, if THP-DATA is equal to 1000, 2000, 3000 and 3500 and NTHP is equal to three then NTHP refers to third entry, that is THP equal to 3000.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"","record":4,"value_type":"INT"},{"index":2,"name":"VALUES","description":"","units":{},"default":"","value_type":"DOUBLE","record":4}],"example":"The following example shows the VFPINJ table for a water injection well and is taken from the Norne OPM Flow model.\nVFPINJ\n-- Table Datum Depth Rate Type\n-- ----- ----------- ---------\n12 2718.07 'WAT' /\n-- 'WAT' units - SM3/DAY\n500.0 1263.2 2026.3 2789.5 3552.6\n4315.8 5078.9 5842.1 6605.3 7368.4\n8131.6 8894.7 9657.9 10421.1 11184.2\n11947.4 12710.5 13473.7 14236.8 15000.0 /\n-- 'THP' units - BARSA\n21.01 63.24 105.46 147.68 189.90\n232.12 274.35 316.57 358.79 401.01 /\n1 254.51 253.95 252.27 249.83 246.69\n242.88 238.42 233.32 227.59 221.22\n214.23 206.62 198.38 189.53 180.06\n169.97 159.26 147.95 136.00 123.46\n/\n2 297.02 296.49 294.82 292.39 289.26\n285.47 281.01 275.92 270.20 263.84\n256.87 249.28 241.05 232.22 222.76\n212.70 202.01 190.71 178.79 166.27\n/\n……………………………………….………………………….……………………………………………………………………\n……………………………………….………………………….……………………………………………………………………\n9 594.67 594.29 592.70 590.34 587.29\n583.57 579.16 574.17 568.55 562.25\n555.40 547.92 539.79 531.09 521.74\n511.82 501.25 490.13 478.34 466.01\n/\n10 637.19 636.83 635.26 632.91 629.86\n626.16 621.76 616.78 611.17 604.89\n598.05 590.59 582.47 573.79 564.45\n554.56 544.01 532.91 521.14 508.83\n/\nThe example shows the first two and the last two records of the fourth kind, as the data is too voluminous to be included.\nNote\nThe VFPTAB variable defines the table number of the VFPINJ data set; if more then one VFPINJ keyword is entered with the same VFPTAB number then the VFPINJ data set will be overwritten by the last VFPINJ keyword with the same VFPTAB number.\nThe same comment is also applicable to the VFPPROD keyword.\n| Note The VFPTAB variable defines the table number of the VFPINJ data set; if more then one VFPINJ keyword is entered with the same VFPTAB number then the VFPINJ data set will be overwritten by the last VFPINJ keyword with the same VFPTAB number. The same comment is also applicable to the VFPPROD keyword. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","records_meta":[{"expected_columns":6},{},{},{}],"size_kind":"list"},"VFPPROD":{"name":"VFPPROD","sections":["SCHEDULE"],"supported":false,"summary":"The VFPPROD keyword defines production Vertical Flow Performance (“VFP”) tables that are used to determine the outflow or downstream pressure based on the inlet or upstream pressure and the phases flowing through the system. For a production well this means the table relates the flowing bottom-hole pressure (“BHP”) to the well’s tubing head pressure (“THP”) based on the oil, gas and water rates (and any artificial lift quantities (\"ALQ\") like gas lift gas), or phases ratios, flowing up the wellbore. The table is also used to describe the pressure relationship when the network option is being used. In this case the table describes the pipeline pressure behavior from the LOWER group (inlet node) to the HIGHER group (outlet node) given the current flowing conditions (the group relationship is defined by the GRUPTREE keyword in SCHEDULE section).","parameters":[{"index":1,"name":"VFPTAB","description":"A positive integer greater than zero and less than or equal to the MXVFPTAB variable as defined on the VFPPDIMS keyword in the RUNSPEC section, that defines the vertical lift performance table number.","units":{},"default":"None","record":1,"value_type":"INT"},{"index":2,"name":"VFPREF","description":"A real positive value that defines the reference depth used to generate this VFPPROD table data set. OPM Flow automatically corrects any difference between VFPREF and the BHPREF on the WELSPECS and WPAVEDEP keywords in the SCHEDULE section, using the current hydrostatic head.","units":{},"default":"None","record":1,"value_type":"DOUBLE","dimension":"Length"},{"index":3,"name":"FLO","description":"A defined character string that defines the flowing phases, and should be set to one of the following character strings: GAS: for flowing phase being the gas rate. OIL: for flowing phase being the oil rate. LIQ: for flowing phase being the liquid (oil plus water) rate.","units":{},"default":"None","record":1,"value_type":"STRING","options":["GAS","OIL","LIQ"]},{"index":4,"name":"WFR","description":"A defined character string that defines the flowing water fraction and should be set to one of the following character strings: WOR: for the water fraction being the water-oil ratio[{ q sub w } over{ q sub o }] and should be used if FLO is set to 'OIL' or 'LIQ' and should be used if FLO is set to 'OIL' or 'LIQ' WCT: for the water fraction being the water cut[{ q sub w } over{ q sub {o} + q sub{w} }]and should be used if FLO is set to 'OIL' or 'LIQ'and should be used if FLO is set to 'OIL' or 'LIQ' WGR: for the water fraction being the water-gas ratio[{ q sub w } over{ q sub {g}}]and should be used if FLO is set to 'GAS'.and should be used if FLO is set to 'GAS'.","units":{},"default":"None","record":1,"value_type":"STRING","options":["WOR","WCT","WGR"]},{"index":5,"name":"GFR","description":"A defined character string that defines the flowing gas fraction and should be set to one of the following character strings: GOR: for the gas fraction being the gas-oil ratio[{ q sub g } over{ q sub o }]and should be used if FLO is set to 'OIL' or 'LIQ' and should be used if FLO is set to 'OIL' or 'LIQ' GLR: for the gas fraction being the gas-liquid ratio[{ q sub g } over{ q sub {o} + q sub{w} }]and should be used if FLO is set to 'OIL' or 'LIQ'and should be used if FLO is set to 'OIL' or 'LIQ' OGR: for the gas fraction being the oil-gas ratio[{ q sub o } over{ q sub {g}}]and should be used if FLO is set to 'GAS'.and should be used if FLO is set to 'GAS'.","units":{},"default":"None","record":1,"value_type":"STRING","options":["GOR","GLR","OGR"]},{"index":6,"name":"VFPTYPE","description":"A defined character string that should be defaulted or set equal to THP.","units":{},"default":"THP","record":1,"value_type":"STRING"},{"index":7,"name":"ALQ","description":"A defined character string that defines the artificial lift quantity and should be set to one of the following character strings: GRAT: for the artificial lift quantity being the gas lift gas injection rate. IGLR: for the artificial lift quantity being the gas lift gas, injection gas-liquid ratio. TGLR: for the artificial lift quantity being the gas lift gas, total gas-liquid ratio. COMP: for the artificial lift quantity being the compressor power, for a compressor. PUMP: for the artificial lift quantity being the pump rating for a pump. DENO: for oil surface density. DENG: for gas surface density. BEAN: for multi-segment wells choke parameter. ' ': for undefined, that is for no ALQ data. The DENO and DENG options are not supported by OPM Flow. The ALQ parameter is just another variable used to interpolate the outflow pressure based on the inlet pressure, together with the phases flowing through the system. As such, ALQ can represent any parameter; however, the units should be consistent with that used to set the value. For example, if pump speed (Hz) is used to set a well’s artificial lift quantity via the WCONPROD(ALQ-WELL) parameter in the SCHEDULE section, then the ALQ-DATA should represent pump speed in Hz. The default value is' ' or undefined, that covers the case when the ALQ variable is not entered, except for when gas lift is employed in the model.When gas lift is active then the default value for ALQ is set to GRAT provided: Gas lift optimization is active via the LIFTOPT keyword, or The GLIFTLIM keyword in the SCHEDULE section is used to constrain the total amount of gas lift used within a group, or Gas lift flows are included in the network pressure loss calculations as determined by the GRUPNET(OPTION2), or the NODEPROP(GASLIFT) parameters in the SCHEDULE section. In addition, if any of the above is true than ALQ must be set to GRAT.","units":{},"default":"' '","record":1,"value_type":"STRING","options":["GRAT","IGLR","TGLR","COMP","PUMP","DENO","DENG","BEAN"]},{"index":8,"name":"VFPUNITS","description":"A defined character string that specifies the units system for the VFP table. An error message is output if this is not the same as the model units.","units":{"field":"FIELD","metric":"METRIC","laboratory":"LAB"},"default":"Model units","record":1,"value_type":"STRING"},{"index":9,"name":"VFPVALUE","description":"A defined character string that defines the type of data in the VFP-DATA vector. This should be set equal to BHP if the vector contains bottom-hole pressure data, or TEMP if the vector contains Tubing Head Temperature (THT) data. OPM Flow only supports the (default) BHP option.","units":{},"default":"BHP","record":1,"value_type":"STRING"},{"index":1,"name":"FLO-DATA","description":"A real positive monotonically increasing vector that defines the numerical values of the flowing phase declared by the FLO variable. The number of entries must greater than two and less than or equal to MXMFLO as defined on the VFPPDIMS keyword in the RUNSPEC section.","units":{"field":"Liquid: stb Gas: Mscf","metric":"Liquid: sm3 Gas: sm3","laboratory":"Liquid: scc Gas: scc"},"default":"None","record":2,"value_type":"DOUBLE"},{"index":1,"name":"THP-DATA","description":"A real positive monotonically increasing vector that defines the numerical values of the tubing head pressure values. The number of entries must greater than two and less than or equal to MXMTHP as defined on the VFPPDIMS keyword in the RUNSPEC section.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","record":3,"value_type":"DOUBLE"},{"index":1,"name":"WFR-DATA","description":"A real positive monotonically increasing vector that defines the numerical values of the flowing water fraction declared by the WFR variable. The number of entries must greater than two and less than or equal to MXMWFR as defined on the VFPPDIMS keyword in the RUNSPEC section.","units":{"field":"WOR: stb/stb WCT: stb/stb WGR: stb/Mscf","metric":"sm3/sm3 sm3/sm3 sm3/sm3","laboratory":"scc/scc scc/scc scc/scc"},"default":"None","record":4,"value_type":"DOUBLE"},{"index":1,"name":"GFR-DATA","description":"A real positive monotonically increasing vector that defines the numerical values of the flowing gas fraction declared by the GFR variable. The number of entries must greater than two and less than or equal to MXMGFR as defined on the VFPPDIMS keyword in the RUNSPEC section.","units":{"field":"GOR: Mscf/stb GLR: Mscf/stb OGR: stb/Mscf","metric":"sm3/sm3 sm3/sm3 sm3/sm3","laboratory":"scc/scc scc/scc scc/scc"},"default":"None","record":5,"value_type":"DOUBLE"},{"index":1,"name":"ALQ-DATA","description":"A real positive monotonically increasing vector that defines the numerical values of the artificial lift quantity declared by the ALQ variable. The number of entries must greater than two and less than or equal to MXMALQ as defined on the VFPPDIMS keyword in the RUNSPEC section.","units":{"field":"GRAT: Mscf/d IGLR: Mscf/stb TGLR: Mscf/stb DENO: lb/ft3 DENG: lb/ft3 BEAN: 1/64 inch","metric":"sm3/day sm3/sm3 sm3/sm3 kg/m3 kg/m3 mm","laboratory":"scc/hour scc/scc scc/scc gm/cc gm/cc mm"},"default":"None","record":6,"value_type":"DOUBLE"},{"index":1,"name":"NTHP","description":"This data record consists of a series of integer values that defines the index of THP, WFR, GFR, ALQ entered via the those records on this keyword. The first index, NTHP, is an integer value that defines the index of THP values entered via the THP-DATA records on this keyword. For example, if THP-DATA is equal to 100, 200, 300 and 350 and NTHP is equal to three then NTHP refers to third entry, that is THP equal to 300.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","record":7,"value_type":"INT"},{"index":2,"name":"WFR_INDEX","description":"","units":{},"default":"","value_type":"INT","record":7},{"index":3,"name":"GFR_INDEX","description":"","units":{},"default":"","value_type":"INT","record":7},{"index":4,"name":"ALQ_INDEX","description":"","units":{},"default":"","value_type":"INT","record":7},{"index":5,"name":"VALUES","description":"","units":{},"default":"","value_type":"DOUBLE","record":7}],"example":"The following example shows the VFPPROD table for a production gas well and is taken from the Norne OPM Flow model. Here WFR has been set to water-gas ratio and GFR has been set to the oil-gas ratio, and the ALQ value is defaulted.\nVFPPROD\n-- Table Datum Depth Rate Type WFR Type GFR Type\n-- ----- ----------- --------- -------- --------\n5 2623.39 'GAS' 'WGR' 'OGR' /\n-- 'GAS' units - SM3/DAY\n50000.0 100000.0 200000.0 400000.0 800000.0\n1200000.0 1600000.0 1999999.9 3000000.0 3999999.8\n5000000.5 /\n-- 'THP' units - BARSA\n10.00 20.00 40.00 80.00 120.00\n150.00 200.00 250.00 /\n-- 'WGR' units - SM3/SM3\n0 1e-9 1e-6 1e-5 0.0001\n0.001 0.01 0.1 /\n-- 'OGR' units - SM3/SM3\n1e-7 1e-6 1e-5 0.0001 0.001\n0.01 /\n-- 'ALQ' units -\n0 /\n1 1 1 1 11.93 12.22 13.35 17.24 27.93\n39.83 52.06 64.38 95.20 125.89\n156.52\n/\n1 1 2 1 11.93 12.22 13.35 17.24 27.94\n39.84 52.07 64.39 95.21 125.91\n156.55\n/\n……………………………………….………………………….……………………………………………………………………\n……………………………………….………………………….……………………………………………………………………\n8 8 5 1 483.75 511.15 614.09 1044.78 2757.56\n5592.55 9528.36 14567.24 32005.79 56375.24\n87684\n/\n8 8 6 1 487.68 516.24 624.74 1075.40 2860.16\n5803.92 9880.58 15093.76 33119.59 58297.57\n90639\n/\nThe example shows the first two and the last two records of type seven, as the data is too voluminous to be included.\nThe next example below shows an example oil producing well VFPPROD, again taken from Norne OPM Flow model. Here WFR has been set to water cut and GFR has been set to the gas-oil ratio, and the ALQ value is defaulted.\nVFPPROD\n-- Table Datum Depth Rate Type WFR Type GFR Type TAB Type\n-- ----- ----------- --------- -------- -------- --------\n-- 37 2641.02 'LIQ' 'WCT' 'GOR' /\n-- Prosper files are corrected from RKB to MSL depth. lmarr\n-- Table Datum Depth Rate Type WFR Type GFR Type TAB Type\n-- ----- ----------- --------- -------- -------- --------\n37 2617.02 'LIQ' 'WCT' 'GOR' /\n-- 'LIQ' units - SM3/DAY\n200.0 500.0 1000.0 1500.0 2000.0\n2500.0 3000.0 3500.0 4000.0 4500.0\n5000.0 5500.0 6000.0 6500.0 7000.0\n7500.0 8000.0 10000.0 14000.0 /\n-- 'THP' units - BARSA\n21.01 51.01 61.01 81.01 101.01\n121.01 141.01 161.01 181.01 201.01 /\n-- 'WCT' units - FRACTION\n0 0.1 0.2 0.3 0.4\n0.5 0.6 0.7 0.8 1 /\n-- 'GOR' units - SM3/SM3\n90 100 150 200 500\n1000 2000 /\n-- 'ALQ' units -\n0 /\n1 1 1 1 160.82 136.70 119.79 115.86 117.38\n121.16 126.08 131.56 137.48 143.74\n150.29 157.07 164.02 171.07 178.13\n185.11 192.09 220.38 280.86\n/\n1 1 2 1 155.63 129.40 112.32 108.64 110.44\n114.74 120.15 126.09 132.47 139.05\n146.02 153.41 160.67 167.91 175.13\n182.34 189.55 218.81 281.02\n/\n……………………………………….………………………….……………………………………………………………………\n……………………………………….………………………….……………………………………………………………………\n10 10 6 1 439.30 437.95 437.53 437.79 438.39\n439.26 440.36 441.67 443.19 444.92\n446.85 448.99 451.32 453.85 456.58\n459.51 462.64 477.11 515.47\n/\n10 10 7 1 439.30 437.95 437.53 437.79 438.39\n439.26 440.36 441.67 443.19 444.92\n446.85 448.99 451.32 453.85 456.58\n459.51 462.64 477.11 515.47\n/\nThe example shows the first two and the last two records of type seven, as the data is too voluminous to be included.\n| Note It is possible to have only the OIL and WATER keywords in the RUNSPEC section and to use gas lift for the wells, without declaring the GAS phase in the RUNSPEC section. In this case, the FLO parameter in Table 12.75must be set to either OIL or LIQ, WFR to either WCT or WOR, and GFR to GOR. In this case the ALQ parameter is optional, but if present must set to GRAT. If the ALQ and ALQ-DATA parameters are absent then the GFR-DATA will be used based on the flowing GOR plus the stipulated gas lift gas. |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------","records_meta":[{"expected_columns":9},{},{},{},{},{},{}],"size_kind":"list"},"VFPTABL":{"name":"VFPTABL","sections":["SCHEDULE"],"supported":false,"summary":"The VFPTABL keyword defines the interpolation method for production Vertical Flow Performance (“VFP”) tables for the Artificial Lift Quantity (“ALQ”). Production VFP data is entered via the VFPPROD keyword in the SCHEDULE section. By default the simulator interpolates all the variables in the VFP tables using linear interpolation, including the ALQ quantity. However, if the ALQ values represent gas lift, then linear interpolation may not be insufficient, as the gradient change between the tabulated ALQ values may result in sudden changes. This is particularly important in gas lift optimization studies where the available gas lift gas is being allocated to a group of wells in order to maximize oil production rates. To overcome this issue the VFPTABL keyword allows the ALQ values to be interpolated using cubic spline interpolation, and results in a smother transition between the various ALQ entries.","parameters":[{"index":1,"name":"VFPTABL","description":"VFPTABL is a defined positive integer that specifies the interpolation method to be used with the ALQ quantity in the VFP production tables, and should be set to one of the following: Apply linear interpolation to all VFPPROD variables. Apply linear interpolation to all VFPPROD variables, except for the ALQ variable, for which cubic spline interpolation should be used. If the keyword is absent from the input deck then linear interpolation will be used for all variables.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1","value_type":"INT"}],"example":"The example sets cubic spline interpolation for the ALQ quantity in the VFPPROD tables, with linear interpolation used for all the variables.\n--\n-- ALQ INTERPOLATION OPTION\n--\n-- OPTION\nVFPTABL\n2\n/","expected_columns":1,"size_kind":"fixed","size_count":1},"WAITBAL":{"name":"WAITBAL","sections":["SCHEDULE"],"supported":false,"summary":"This keyword sets the network balance option for all networks when networks are active in the model. Basically, the keyword either activates the PRORDER and GDRILPOT stipulated actions before or after the network has been balanced","parameters":[{"index":1,"name":"WAIT_NETWORK_BALANCE","description":"","units":{},"default":"NO","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"WALKALIN":{"name":"WALKALIN","sections":["SCHEDULE"],"supported":false,"summary":"WAKALIN keyword defines the water injection alkaline concentration for water injection wells for when the surfactant and/or polymer models have been activated by the SURFACT, SURFACTW, or the POLYMER keywords in the RUNSPEC section, combined with the ALKALINE keyword which is also in the RUNSPEC section.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"ALKALINE_CONCENTRAION","description":"","units":{},"default":"","value_type":"UDA","dimension":"Mass/LiquidSurfaceVolume"}],"example":"","expected_columns":2,"size_kind":"list"},"WALQCALC":{"name":"WALQCALC","sections":["SCHEDULE"],"supported":false,"summary":"The WALQCALC keyword defines the well VFP surface ALQ phase density use in the VFP table lookup and interpolation to be gas surface density, oil surface density, or neither. Note that the user should ensure that generated VFP tables have been generated consistent with the setting on this keyword.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"ALQ_DEF","description":"","units":{},"default":"NONE","value_type":"STRING"}],"example":"","expected_columns":2,"size_kind":"list"},"WAPI":{"name":"WAPI","sections":["SCHEDULE"],"supported":false,"summary":"This keyword defines an oil injection well’s API gravity for when API tracking has been made active via the API keyword in the RUNSPEC section. The American Petroleum Institute (API) classifies oils based on an API gravity (γAPI), or degrees API (oAPI), the relationship between relative density (γo) of oil and API gravity (γAPI) is given by:","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"API","description":"","units":{},"default":"","value_type":"UDA"}],"example":"| [%gamma SUB { API } ~ = ~ { 141.5 } OVER { %gamma SUB { o }}~-~ 131.5] | (12.33) |\n|------------------------------------------------------------------------|---------|","expected_columns":2,"size_kind":"list"},"WBHGLR":{"name":"WBHGLR","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, WBHGLR, defines a well’s bottom-hole Gas Liquid Ratio (“GLR”) constraint, where the GLR is the is the ratio of the “free” gas rate and liquid rate at bottom-hole conditions. The reference depth for bottom-hole conditions is given by the BHPREF variable on the WELSPECS keyword in the SCHEDULE section.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"MAX_GLR_CUTBACK","description":"","units":{},"default":"1e+20","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"MIN_GLR_CUTBACK_REVERSE","description":"","units":{},"default":"1e+20","value_type":"DOUBLE","dimension":"1"},{"index":4,"name":"RATE_CUTBACK_FACTOR","description":"","units":{},"default":"1","value_type":"DOUBLE"},{"index":5,"name":"PHASE","description":"","units":{},"default":"RESV","value_type":"STRING"},{"index":6,"name":"MAX_GLR_ELIMIT","description":"","units":{},"default":"1e+20","value_type":"DOUBLE","dimension":"1"},{"index":7,"name":"WORKOVER_ACTION","description":"","units":{},"default":"NONE","value_type":"STRING"},{"index":8,"name":"WORKOVER_REMOVE_CUTBACKS","description":"","units":{},"default":"NO","value_type":"STRING"}],"example":"","expected_columns":8,"size_kind":"list"},"WBOREVOL":{"name":"WBOREVOL","sections":["SCHEDULE"],"supported":false,"summary":"The WBOREVOL defines a well’s effective wellbore storage volume. The primary purpose of the keyword is to enable matching of the wellbore storage effects in well tests and the corresponding pressure response observed in the test. Normally, as part of well test interpretation, the pressure, permeability, effective wellbore storage, etc., are derived from the analytical interpretation of the test. This keyword therefore allows the engineer to enter the analytical derived effective wellbore storage.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"WELLBORE_VOL","description":"","units":{},"default":"1e-05","value_type":"DOUBLE","dimension":"Length*Length*Length"},{"index":3,"name":"START_BHP","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"}],"example":"","expected_columns":3,"size_kind":"list"},"WCALCVAL":{"name":"WCALCVAL","sections":["SCHEDULE"],"supported":false,"summary":"This keyword defines a gas well’s calorific value for when the Gas Calorific Value option has been activated by specifying a target calorific value for a group via the GCONCAL keyword in the SCHEDULE section. If this option is invoked then the gas calorific value must be set either by this keyword for a well by well allocation of the calorific value, or by using the Tracer Tracking option (activated by the TRACER keyword in the RUNSPEC section) combined with CALTRAC keyword in the SCHEDULE section that defines the tracer for the calorific value.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"CALORIFIC_GAS_VALUE","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Energy/GasSurfaceVolume"}],"example":"","expected_columns":2,"size_kind":"list"},"WCONHIST":{"name":"WCONHIST","sections":["SCHEDULE"],"supported":null,"summary":"The WCONHIST keyword defines production rates and pressures for wells that have been declared history matching wells by the use of this keyword. History matching wells are handled differently than ordinary wells that use the WCONPROD keyword for controlling their production targets and constraints. However, the wells still need to be defined like ordinary production wells using the WELSPECS keyword in the SCHEDULE section.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the wells observed production rates and pressures are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"STATUS","description":"A defined character string that declares the status of the well. STATUS should be set to one of the following character strings: OPEN: the well is open to flow and will attempt to produce the required production volumes. STOP: the well is “stopped” at the surface and will not produce any fluids to surface; however, if there any open connections then flow may occur within the wellbore and between the open connections depending on a connection’s potential with respect to all the other connections. Inter-connection flow (cross flow) can be prevented by setting the XFLOW variable on the WELSPECS keyword to NO. In this case the well’s behavior will be similar to the SHUT option described below. SHUT: the well is shut at the surface and downhole, this results in no flow at the surface and no cross flow downhole. Note a well’s STATUS should always be set either STOP or SHUT if the well’s production is to be set to zero. Just setting a well’s production rate to zero means that the well is open to flow with a zero rate.","units":{},"default":"OPEN","value_type":"STRING","options":["OPEN","STOP","SHUT"]},{"index":3,"name":"TARGET","description":"A defined character string that sets the observed target production phase for the well, all the other phases are calculated unconstrained and used for reporting only. The simulator will attempt to meet the TARGET based on the phase rate stated in items (4) to (6) and (10) on this keyword. TARGET should be set to one of the following character strings: ORAT: the target is set to the surface oil production rate as defined by item (4). WRAT: the target is set to the surface water production rate as defined by item (5). GRAT: the target is set to the surface gas production rate as defined by item (6). LRAT: the target is set to the surface liquid (oil plus water) production rate and is calculated by the simulator using (4) and (5). RESV: the target is set to the in situ reservoir volume rate and is calculated by the simulator using items (4), (5) and (6). BHP: the target rate is set to the bottom-hole pressure as defined by item (10). Note the TARGET control mode may be reset using the WHISTCTL keyword in the SCHEDULE section, from the time the WHISTCTL is invoked, thus avoiding changing the control mode on all subsequent WCONHIST keywords.","units":{},"default":"None","value_type":"STRING","options":["ORAT","WRAT","GRAT","LRAT","RESV","BHP"]},{"index":4,"name":"ORAT","description":"A real positive value that defines the observed surface oil production rate target or constraint. This value may be specified using a User Defined Argument (UDA).","units":{"field":"stb/d 0.0","metric":"sm3/day 0.0","laboratory":"scc/hour 0.0"},"default":"Defined","value_type":"UDA","dimension":"LiquidSurfaceVolume/Time"},{"index":5,"name":"WRAT","description":"A real positive value that defines the observed surface water production rate target or constraint. This value may be specified using a User Defined Argument (UDA).","units":{"field":"stb/d 0.0","metric":"sm3/day 0.0","laboratory":"scc/hour 0.0"},"default":"Defined","value_type":"UDA","dimension":"LiquidSurfaceVolume/Time"},{"index":6,"name":"GRAT","description":"A real positive value that defines the observed surface gas production rate target or constraint This value may be specified using a User Defined Argument (UDA).","units":{"field":"Mscf/d 0.0","metric":"sm3/day 0.0","laboratory":"scc/hour 0.0"},"default":"Defined","value_type":"UDA","dimension":"GasSurfaceVolume/Time"},{"index":7,"name":"VFPTAB","description":"A positive integer greater than or equal to zero that defines the vertical lift performance tables to be used for calculating the tubing head pressure for the well. If a non-zero value is entered then the vertical lift performance tables must be entered via the VFPPROD keyword in the SCHEDULE section and allocated to the well via this item. The default value of zero implies no vertical lift performance table initially. If this value is then reset to be greater than zero then the table will be used to calculate the well’s tubing head pressure. Subsequently, the default is to use the previously declared table number.","units":{},"default":"0","value_type":"INT"},{"index":8,"name":"ALQ-WELL","description":"A real positive value that defines the artificial lift quantity to be used in conjunction with the VFPPROD assigned to the well via that keyword's VFPTAB variable. This value may be specified using a User Defined Argument (UDA). VFPTAB vertical lift performance table and the artificial lift quantity ALQ-WELL are used with the well fluid rates to calculate the well’s tubing head pressures values from the bottom-hole pressure. Note that the units for ALQ-WELL is dependent on the associated variable on the VFPPROD keyword.","units":{},"default":"None","value_type":"UDA"},{"index":9,"name":"THP","description":"A real positive value that defines the observed tubing head pressure. This value may be specified using a User Defined Argument (UDA). This parameter is only used for comparing the actual tubing head pressure given here with those calculated by the simulator, that is history matching wells can only be controlled by either the surface injection rate or their bottom-hole pressure.","units":{"field":"psia 0.0","metric":"barsa 0.0","laboratory":"atma 0.0"},"default":"Defined","value_type":"UDA","dimension":"Pressure"},{"index":10,"name":"BHP","description":"A real positive value that defines the observed bottom-hole pressure. This value may be specified using a User Defined Argument (UDA).","units":{"field":"psia 0.0","metric":"barsa 0.0","laboratory":"atma 0.0"},"default":"Defined","value_type":"UDA","dimension":"Pressure"},{"index":11,"name":"WGRA","description":"A real positive value that defines the observed wet gas rate in the commercial compositional simulator. The parameter is ignored by OPM Flow and should be defaulted or set to the default value of zero.","units":{},"default":"0.0","value_type":"DOUBLE","dimension":"GasSurfaceVolume/Time"},{"index":12,"name":"NGL","description":"A real positive value that defines the observed Natural Gas Liquid (“NGL”) rate in the commercial compositional simulator. The parameter is ignored by OPM Flow and should be defaulted or set to the default value of zero.","units":{},"default":"0.0","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time"}],"example":"The following example below shows the observed production rates for the OP01 oil producer for the first quarter of 2000.\n-- ------------------------------------------------------------------------------\n-- 01 JAN 2000 START OF SCHEDULE SECTION\n-- ------------------------------------------------------------------------------\n--\n-- WELL HISTORICAL PRODUCTION CONTROLS\n--\n-- WELL OPEN/ CNTL OIL WAT GAS VFP VFP THP BHP\n-- NAME SHUT MODE RATE RATE RATE TABLE ALFQ PRES PRES\nWCONHIST OP01 OPEN ORAT 15.5E3 100.0 1550 10 1* 900.0 1* /\n/ DATES\n01 FEB 2000 /\n/\n--\n-- WELL HISTORICAL PRODUCTION CONTROLS\n--\n-- WELL OPEN/ CNTL OIL WAT GAS VFP VFP THP BHP\n-- NAME SHUT MODE RATE RATE RATE TABLE ALFQ PRES PRES\nWCONHIST OP01 OPEN ORAT 15.2E3 150.0 1520 1* 1* 875.0 3250.0 /\n/ DATES\n01 MAR 2000 /\n/\n--\n-- WELL HISTORICAL PRODUCTION CONTROLS\n--\n-- WELL OPEN/ CNTL OIL WAT GAS VFP VFP THP BHP\n-- NAME SHUT MODE RATE RATE RATE TABLE ALFQ PRES PRES\nWCONHIST OP01 OPEN ORAT 15.0E3 200.0 1500 1* 1* 850.0 1* /\n/\nFrom January 1, 2000 well OP01 is open and is on oil rate control, and produces 15,500 stb/d oil, with the observed rates of 100 stb/d of water and 15.5 MMscf/d of gas. The well uses VFPPROD vertical lift table number 10 so that OPM Flow can calculate the tubing head pressures based on the fluids produced and the calculated pressures in the simulator.\nThe next example illustrates how to convert OP01 from a history match well to a normal production well at the start for the forecast run at August 1, 2017 using the WELTARG keyword.\nDATES\n01 AUG 2017 /\n/\n--\n-- WELL PRODUCTION AND INJECTION TARGETS\n--\n-- WELL WELL TARGET\n-- NAME TARG VALUE\nWELTARG\nOP01 THP 1* /\n/\nHere by defaulting the bottom-hole pressure via 1* OPM Flow automatically applies the last bottom-hole pressure from the previous time step as the “constraining phase” together with the last historical rates as constraints. This ensures a smooth transition between history and prediction without having to resort to unreasonable changes to the model. This option is currently not implemented in OPM Flow but is expected to be incorporated in a future release.\n| Note One can use TARGET set to RESV in the initial history matching runs to get a “reasonable” pressure match, this ensures that the total reservoir withdrawals are correct, although the individual phase withdrawals will not match. Once a reasonable pressure match is achieved for the reservoir then one can reset TARGET to the sales phase, OIL or GAS, and continue with the matching of all the phases. In oil reservoirs some engineers prefer to use LIQ rather than OIL as the TARGET phase, although one should consider that as the water phase has no commercial value, the measurement accuracy is significantly less than the oil sales phase. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":12,"size_kind":"list"},"WCONINJ":{"name":"WCONINJ","sections":["SCHEDULE"],"supported":false,"summary":"The WCONINJ is a legacy keyword that is no longer used in the commercial simulator and is not supported by OPM Flow. Instead well injection targets and constraints should be defined using the WCONINJE keyword in the SCHEDULE section.","parameters":[],"example":"","size_kind":"none","size_count":0},"WCONINJE":{"name":"WCONINJE","sections":["SCHEDULE"],"supported":false,"summary":"The WCONINJE keyword defines injection targets and constraints for wells that have previously been defined by the WELSPECS keyword in the SCHEDULE section. Note that wells can be allocated to a group when they are specified by the WELSPECS keyword. Wells defined to be under group control will have their injection rates controlled by the group to which they belong, in addition to any well constraints defined for the wells using this keyword.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well injection targets and constraints data are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"TYPE","description":"A defined character string that defines the type of injection well. TYPE should be set to one of the following character strings: GAS: for a gas injection well. OIL: for an oil injection well. WAT: for a water injection well.","units":{},"default":"None","value_type":"STRING","options":["GAS","OIL","WAT"]},{"index":3,"name":"STATUS","description":"A defined character string that declares the status of the well. STATUS should be set to one of the following character strings: OPEN: the well is open for injection and will attempt to inject the required injection volumes. STOP: the well is “stopped” at the surface and will not inject any fluids; however, if there any open connections then flow may occur within the wellbore and between the open connections depending on a connection’s potential with respect to all the other connections. Inter-connection flow (cross flow) can be prevented by setting the XFLOW variable on the WELSPECS keyword to NO. In this case the well’s behavior will be similar to the SHUT option described below. SHUT: the well is shut at the surface and downhole, this results in no injection and no cross flow downhole. AUTO: the well is initially SHUT, but may be opened automatically if an economic limit is violated. This option is currently not supported by OPM Flow. Note a well’s STATUS should always be set either STOP or SHUT if the well’s injection is to be set to zero. Just setting a well’s injection rate to zero means that the well is open for injection with a zero rate, this will cause numerical issues especially for wells under THP control.","units":{},"default":"OPEN","value_type":"STRING","options":["OPEN","STOP","SHUT","AUTO"]},{"index":4,"name":"TARGET","description":"A defined character string that sets the target injection control mode for the well. TARGET should be set to one of the following character strings: RATE: the injection phase will be controlled by the surface fluid rate for the given well type as defined by the TYPE variable. For example, if TYPE has been set to WAT then this would mean the surface water injection rate as defined by item (5). RESV: the injection phase will be controlled by the in situ reservoir volume fluid rate for the given well type as defined by the TYPE variable. For example, if TYPE has been set to GAS then this would mean the gas reservoir volume injection rate as defined by item (6). BHP: the target rate is set according to the bottom-hole pressure as defined by item (7). THP: the target rate is set according to the tubing head pressure as defined by item (8). If this option is selected then the vertical lift performance tables must be entered via the VFPINJ keyword in the SCHEDULE section and allocated to the well via item (9). GRUP: the well is under group control and injects its share of the group's target as set using the GCONINJE keyword in the SCHEDULE section.","units":{},"default":"None","value_type":"STRING","options":["RATE","RESV","BHP","THP","GRUP"]},{"index":5,"name":"RATE","description":"A real positive value that defines the maximum surface injection rate target or constraint. This value may be specified using a User Defined Argument (UDA).","units":{"field":"Liquid stb/d Gas Mscf/d","metric":"Liquid sm3/day Gas sm3/day","laboratory":"Liquid scc/hour Gas scc/hour"},"default":"None","value_type":"UDA"},{"index":6,"name":"RESV","description":"A real positive value that defines the maximum reservoir volume injection rate target or constraint. This value may be specified using a User Defined Argument (UDA).","units":{"field":"rb/d","metric":"rm3/day","laboratory":"rcc/hour"},"default":"None","value_type":"UDA","dimension":"ReservoirVolume/Time"},{"index":7,"name":"BHP","description":"A real positive value that defines the maximum bottom-hole pressure target or constraint. This value may be specified using a User Defined Argument (UDA). Note the default value basically means unlimited injection or no constraint and should therefore be avoided as the BHP will result in unrealistic well potentials as well as optimistic injection forecasts for the well.","units":{"field":"psia 10,0000","metric":"barsa 6,895","laboratory":"atma 6,803"},"default":"Defined","value_type":"UDA","dimension":"Pressure"},{"index":8,"name":"THP","description":"A real positive value that defines the maximum tubing head pressure target or constraint. This value may be specified using a User Defined Argument (UDA).","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"UDA","dimension":"Pressure"},{"index":9,"name":"VFPTAB","description":"A positive integer greater than or equal to zero that defines the vertical lift performance tables to be used for calculating the tubing head pressure for the well. If a non-zero value is entered then the vertical lift performance tables must be entered via the VFPINJ keyword in the SCHEDULE section and allocated to the well via this item. The default value of zero implies no vertical lift performance tables and in this case TARGET cannot be set to THP and in addition item (10) should be defaulted or set to zero.","units":{},"default":"0","value_type":"INT"},{"index":10,"name":"RSRVINJ","description":"The dissolved gas-oil ratio in the injected oil, or the vaporized oil-gas ratio in the injected gas.","units":{"field":"Gas Injection: stb/Mscf Oil Injection: Mscf/stb","metric":"Gas Injection: sm3/sm3 Oil Injection: sm3/sm3","laboratory":"Gas Injection: scc/scc Oil Injection: scc/scc"},"default":"0.0","value_type":"DOUBLE","dimension":"OilDissolutionFactor"},{"index":11,"name":"RSSTEAM","description":"Thermal/Temperature gas-steam ratio for steam-gas injectors. The parameter is ignored by OPM Flow and should be defaulted or set to the default value of zero.","units":{},"default":"0.0","value_type":"DOUBLE"},{"index":12,"name":"OILFRAC","description":"Surface oil fraction in a multi-phase injector. The parameter is ignored by OPM Flow and should be defaulted or set to the default value of zero.","units":{},"default":"0.0","value_type":"DOUBLE"},{"index":13,"name":"WATFRAC","description":"Surface water fraction in a multi-phase injector. The parameter is ignored by OPM Flow and should be defaulted or set to the default value of zero.","units":{},"default":"0.0","value_type":"DOUBLE"},{"index":14,"name":"GASFRAC","description":"Surface gas fraction in a multi-phase injector. The parameter is ignored by OPM Flow and should be defaulted or set to the default value of zero.","units":{},"default":"0.0","value_type":"DOUBLE"},{"index":15,"name":"OILSTEAM","description":"Surface oil volume to steam volume ratio in a steam-oil injector. The parameter is ignored by OPM Flow and should be defaulted or set to the default value of zero.","units":{},"default":"0.0","value_type":"DOUBLE"}],"example":"The following example defines the injection targets and constraints for one gas injection well and one water injection well as follows:\n--\n-- WELL INJECTION CONTROLS\n--\n-- WELL FLUID OPEN/ CNTL SURF RESV BHP THP VFP\n-- NAME TYPE SHUT MODE RATE RATE PRSES PRES TABLE\nWCONINJE\nGI01 GAS OPEN GRUP 50E3 1* 1* 1* 1* /\nWI01 WAT OPEN RATE 25E3 1* 5000. 1* 1* /\n/\nWell GI01 is a gas injection well directly under group control constrained by a maximum surface gas injection rate of 50 MMscf/d and well WI01 is an open water injection well with a surface water injection rate target of 25,000 stb/d, subject to a maximum bottom-hole pressure constraint 5,000 psia.","expected_columns":15,"size_kind":"list"},"WCONINJH":{"name":"WCONINJH","sections":["SCHEDULE"],"supported":null,"summary":"The WCONINJH keyword defines injection rates and pressures for wells that have been declared history matching wells by the use of this keyword. History matching wells are handled differently then ordinary wells that use the WCONINJE keyword for controlling their injection targets and constraints. However, the wells still need to be defined like ordinary injection wells using the WELSPECS keyword in the SCHEDULE section.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the wells observed injection rates and pressures are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"TYPE","description":"A defined character string that defines the type of injection well. TYPE should be set to one of the following character strings: GAS: for a gas injection well. OIL: for an oil injection well. WAT: for a water injection well.","units":{},"default":"None","value_type":"STRING","options":["GAS","OIL","WAT"]},{"index":3,"name":"STATUS","description":"A defined character string that declares the status of the well. STATUS should be set to one of the following character strings: OPEN: the well is open for injection and will attempt to inject the observed injection volumes. STOP: the well is “stopped” at the surface and will not inject fluids; however, if there any open connections then flow may occur within the wellbore and between the open connections depending on a connection’s potential with respect to all the other connections. Inter-connection flow (cross flow) can be prevented by setting the XFLOW variable on the WELSPECS keyword to NO. In this case the well’s behavior will be similar to the SHUT option described below. SHUT: the well is shut at the surface and downhole, this results in no injection and no cross flow downhole. Note a well’s STATUS should always be set either STOP or SHUT if the well’s injection is to be set to zero. Just setting a well’s injection rate to zero means that the well is open to flow with a zero injection rate, this may cause numerical issues.","units":{},"default":"OPEN","value_type":"STRING","options":["OPEN","STOP","SHUT"]},{"index":4,"name":"RATE","description":"A real positive value that defines the observed surface injection rate.","units":{"field":"Liquid stb/d Gas Mscf/d","metric":"Liquid sm3/day Gas sm3/day","laboratory":"Liquid scc/hour Gas scc/hour"},"default":"0.0","value_type":"DOUBLE","dimension":"ContextDependent"},{"index":5,"name":"BHP","description":"A real positive value that defines the observed bottom-hole pressure.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"0.0","value_type":"DOUBLE","dimension":"Pressure"},{"index":6,"name":"THP","description":"A real positive value that defines the observed tubing head pressure. This parameter is only used for comparing the actual tubing head pressure given here with those calculated by the simulator, that is history matching wells can only be controlled by either the surface injection rate or their bottom-hole pressure.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":"Pressure"},{"index":7,"name":"VFPTAB","description":"A positive integer greater than or equal to zero that defines the vertical lift performance tables to be used for calculating the tubing head pressure for the well. If a non-zero value is entered then the vertical lift performance tables must be entered via the VFPINJ keyword in the SCHEDULE section and allocated to the well via this item. The default value of zero implies no vertical lift performance table initially. If this value is then reset to be greater than zero then the table will be used to calculate the well’s tubing head pressure. Subsequently, the default is to use the previously declared table number.","units":{},"default":"0","value_type":"INT"},{"index":8,"name":"RSRVINJ","description":"Dissolved gas fraction in injected oil or vaporized oil fraction in injected gas. The parameter is ignored by OPM Flow and should be defaulted or set to the default value of zero.","units":{},"default":"0.0","value_type":"DOUBLE","dimension":"OilDissolutionFactor"},{"index":9,"name":"OILFRAC","description":"Surface oil fraction in a multi-phase injector. The parameter is ignored by OPM Flow and should be defaulted or set to the default value of zero.","units":{},"default":"0.0","value_type":"DOUBLE"},{"index":10,"name":"WATFRAC","description":"Surface water fraction in a multi-phase injector. The parameter is ignored by OPM Flow and should be defaulted or set to the default value of zero.","units":{},"default":"0.0","value_type":"DOUBLE"},{"index":11,"name":"GASFRAC","description":"Surface gas fraction in a multi-phase injector. The parameter is ignored by OPM Flow and should be defaulted or set to the default value of zero.","units":{},"default":"0.0","value_type":"DOUBLE"},{"index":12,"name":"TARGET","description":"A defined character string that sets the target injection control mode for the well. TARGET should be set to one of the following character strings: RATE: the injection well will be controlled by the surface injection rate for the given well type as defined by the TYPE variable. For example, if TYPE has been set to WAT then this would mean the surface water injection rate as defined by item (4). BHP: the injection well will be controlled by the bottom-hole pressure as defined by item (5).","units":{},"default":"RATE","value_type":"STRING","options":["RATE","BHP"]}],"example":"The following example below shows the observed gas rates for the GI01 gas injector for the first quarter of 2000.\n-- ------------------------------------------------------------------------------\n-- 01 JAN 2000 START OF SCHEDULE SECTION\n-- ------------------------------------------------------------------------------\n--\n-- WELL HISTORICAL INJECTION CONTROLS\n--\n-- WELL FLUID OPEN/ SURF BHP THP VFP NOT CNTL\n-- NAME TYPE SHUT RATE PRES PRES TABLE USED MODE\nWCONINJH\nGI01 GAS OPEN 15.5E3 1* 5462 12 4* 1* /\n/ DATES\n01 FEB 2000 /\n/\n--\n-- WELL HISTORICAL INJECTION CONTROLS\n--\n-- WELL FLUID OPEN/ SURF BHP THP VFP NOT CNTL\n-- NAME TYPE SHUT RATE PRES PRES TABLE USED MODE\nWCONINJH\nGI01 GAS OPEN 15.9E3 1* 5468 1* 4* 1* /\n/ DATES\n01 MAR 2000 /\n/\n--\n-- WELL HISTORICAL INJECTION CONTROLS\n--\n-- WELL FLUID OPEN/ SURF BHP THP VFP NOT CNTL\n-- NAME TYPE SHUT RATE PRES PRES TABLE USED MODE\nWCONINJH\nGI01 GAS OPEN 17.2E3 1* 5489 1* 4* 1* /\n/\nWell GI01is declared as a gas injection well under gas rate control as TARGET variable is defaulted to rate control by using 1* (the last entry on the record). In addition, the well uses vertical lift table VFPINJ number 12 (as shown at January 1, 2000) to calculate the tubing head pressures for the well. Note that it is not necessary to declare the VFPINJ table number if it remains the same for subsequent time steps and thus the default 1* is used to indicate the last entry should be used.","expected_columns":12,"size_kind":"list"},"WCONINJP":{"name":"WCONINJP","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, WCONINJP, defines well injection targets and constraints for pattern flood wells. The keyword is similar to the WCONINJE keyword in the SCHEDULE section except that the injection control is applied to a group of wells defined by the first record of this keyword, combined with a second record that defines the wells in the pattern and their contribution to the pattern.","parameters":[{"index":1,"name":"PATTERN_WELL","description":"","units":{},"default":"","value_type":"STRING","record":1},{"index":2,"name":"INJECTOR_TYPE","description":"","units":{},"default":"","value_type":"STRING","record":1},{"index":3,"name":"STATUS","description":"","units":{},"default":"OPEN","value_type":"STRING","record":1},{"index":4,"name":"BHP_MAX","description":"","units":{},"default":"6895","value_type":"DOUBLE","dimension":"Pressure","record":1},{"index":5,"name":"THP_MAX","description":"","units":{},"default":"","value_type":"DOUBLE","record":1},{"index":6,"name":"VFP_TABLE","description":"","units":{},"default":"0","value_type":"INT","record":1},{"index":7,"name":"VOIDAGE_TARGET_MULTIPLIER","description":"","units":{},"default":"1","value_type":"DOUBLE","record":1},{"index":8,"name":"OIL_FRACTION","description":"","units":{},"default":"0","value_type":"DOUBLE","record":1},{"index":9,"name":"WATER_FRACTION","description":"","units":{},"default":"0","value_type":"DOUBLE","record":1},{"index":10,"name":"GAS_FRACTION","description":"","units":{},"default":"0","value_type":"DOUBLE","record":1},{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING","record":2},{"index":2,"name":"PROD_FRACTION","description":"","units":{},"default":"","value_type":"DOUBLE","record":2},{"index":3,"name":"FIPNUM_VALUE","description":"","units":{},"default":"0","value_type":"INT","record":2}],"example":"","records_meta":[{"expected_columns":10},{"expected_columns":3}],"size_kind":"list"},"WCONPROD":{"name":"WCONPROD","sections":["SCHEDULE"],"supported":false,"summary":"The WCONPROD keyword defines production targets and constraints for wells that have previously been defined by the WELSPECS keyword in the SCHEDULE section. Note that wells can be allocated to a group when they are specified by the WELSPECS keyword. Wells defined to be under group control will have their production rates controlled by the group to which they belong, in addition to any well constraints defined for the wells using this keyword.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well production targets and constraints data are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"STATUS","description":"A defined character string that declares the status of the well. STATUS should be set to one of the following character strings: OPEN: the well is open to flow and will attempt to produce the required production volumes. STOP: the well is “stopped” at the surface and will not produce any fluids to surface; however, if there any open connections then flow may occur within the wellbore and between the open connections depending on a connection’s potential with respect to all the other connections. Inter-connection flow (cross flow) can be prevented by setting the XFLOW variable on the WELSPECS keyword to NO. In this case the well’s behavior will be similar to the SHUT option described below. SHUT: the well is shut at the surface and downhole, this results in no flow at the surface and no cross flow downhole. AUTO: the well is initially SHUT, but may be opened automatically if an economic limit is violated. This option is currently not supported by OPM Flow. Note a well’s STATUS should always be set either STOP or SHUT if the well’s production is to be set to zero. Just setting a well’s production rate to zero means that the well is open to flow with a zero rate, this will cause numerical issues especially for wells under THP control.","units":{},"default":"OPEN","value_type":"STRING","options":["OPEN","STOP","SHUT","AUTO"]},{"index":3,"name":"TARGET","description":"A defined character string that sets the target production phase for the well, all the other phases will therefore act as constraints. The simulator will attempt to meet the TARGET based on the phase rate stated in items (4) to (10) on this keyword. TARGET should be set to one of the following character strings: ORAT: the target is set to the surface oil production rate as defined by item (4). WRAT: the target is set to the surface water production rate as defined by item (5). GRAT: the target is set to the surface gas production rate as defined by item (6). LRAT: the target is set to the surface liquid (oil plus water) production rate as defined by item (7). RESV: the target is set to the in situ reservoir volume rate as defined by item (8). BHP: the target rate is set to the bottom-hole pressure as defined by item (9). THP: the target rate is set to the tubing head pressure as defined by item (10). If this option is selected then the vertical lift performance tables must be entered via the VFPPROD keyword in the SCHEDULE section and allocated to the well via item (11). GRUP: the well is under group control and produces its share of the group's target as set using the GCONPROD keyword in the SCHEDULE section. Here the default tokens of 1* or '' may be used, and both default tokens behave in the same manner; however, the actual default value used when TARGET is defaulted is dependent on the data entered on this keyword as described below: If the well’s group parameters have not been defined via the GCONPROD keyword, in the SCHEDULE section, then TARGET is set to the first non-defaulted hydrocarbon rate (ORAT, GRAT, LRAT, or RESV). If all the rates are defaulted and a value for BHP is entered, then TARGET is set to BHP control. Similarly, if BHP is also defaulted, and THP has been entered, then TARGET is set to THP control. Finally, if all parameters are defaulted, then the default value for BHP, one atmosphere, will be used with BHP control. If, and only if, the well’s group parameters have been defined via the GCONPROD keyword, then TARGET is set equal to GRUP, and the remaining parameters on the WCONPROD keyword are used as well constraints. Note the default value of one atmosphere should be avoided as the BHP will result in unrealistic well potentials as well as optimistic production forecasts for the well.","units":{},"default":"1*","value_type":"STRING","options":["ORAT","WRAT","GRAT","LRAT","RESV","BHP","THP","GRUP"]},{"index":4,"name":"ORAT","description":"A real positive value that defines the maximum surface oil production rate target or constraint. This value may be specified using a User Defined Argument (UDA).","units":{"field":"stb/day","metric":"sm3/day","laboratory":"scc/hour"},"default":"None","value_type":"UDA","dimension":"LiquidSurfaceVolume/Time"},{"index":5,"name":"WRAT","description":"A real positive value that defines the maximum surface water production rate target or constraint. This value may be specified using a User Defined Argument (UDA).","units":{"field":"stb/day","metric":"sm3/day","laboratory":"scc/hour"},"default":"None","value_type":"UDA","dimension":"LiquidSurfaceVolume/Time"},{"index":6,"name":"GRAT","description":"A real positive value that defines the maximum surface gas production rate target or constraint This value may be specified using a User Defined Argument (UDA).","units":{"field":"Mscf/day","metric":"sm3/day","laboratory":"scc/hour"},"default":"None","value_type":"UDA","dimension":"GasSurfaceVolume/Time"},{"index":7,"name":"LRAT","description":"A real positive value that defines the maximum surface liquid (oil plus water) production rate target or constraint. This value may be specified using a User Defined Argument (UDA).","units":{"field":"stb/day","metric":"sm3/day","laboratory":"scc/hour"},"default":"None","value_type":"UDA","dimension":"LiquidSurfaceVolume/Time"},{"index":8,"name":"RESV","description":"A real positive value that defines the maximum reservoir volume production rate target or constraint. This value may be specified using a User Defined Argument (UDA).","units":{"field":"rtb/day","metric":"rm3/day","laboratory":"rcc/hour"},"default":"None","value_type":"UDA","dimension":"LiquidSurfaceVolume/Time"},{"index":9,"name":"BHP","description":"A real positive value that defines the minimum bottom-hole pressure target or constraint. This value may be specified using a User Defined Argument (UDA). Note the default value of one atmosphere should be avoided as the BHP will result in unrealistic well potentials as well as optimistic production forecasts for the well.","units":{"field":"psia 14.70","metric":"barsa 1.01325.","laboratory":"atma 1.0"},"default":"Defined","value_type":"UDA","dimension":"Pressure"},{"index":10,"name":"THP","description":"A real positive value that defines the minimum tubing head pressure target or constraint. This value may be specified using a User Defined Argument (UDA). Note the default value of zero should be avoided if the well’s control TARGET has been set to THP, as this will result in optimistic production forecasts for a well, since a well must flow against a back pressure imposed by the surface facilities.","units":{"field":"psia 0.0","metric":"barsa 0.0","laboratory":"atma 0.0"},"default":"Defined","value_type":"UDA","dimension":"Pressure"},{"index":11,"name":"VFPTAB","description":"A positive integer greater than or equal to zero that defines the vertical lift performance tables to be used for calculating the tubing head pressure for the well. If a non-zero value is entered then the vertical lift performance tables must be entered via the VFPPROD keyword in the SCHEDULE section and allocated to the well via this item. The default value of zero implies no vertical lift performance tables and in this case TARGET cannot be set to THP and in addition item (10) should be defaulted or set to zero.","units":{},"default":"0","value_type":"INT"},{"index":12,"name":"ALQ-WELL","description":"A real positive value that defines the artificial lift quantity to be used in conjunction with the VFPPROD assigned to the well via the VFPTAB variable. This value may be specified using a User Defined Argument (UDA). VFPTAB vertical lift performance table and the artificial lift quantity ALQ-WELL are used with the well fluid rates to calculate the well’s tubing head pressures values from the bottom-hole pressure. Note that the units for ALQ-WELL are dependent on the associated variable on the VFPPROD keyword.","units":{},"default":"0.0","value_type":"UDA"},{"index":13,"name":"WGASRATE","description":"Wet gas production rate used in the commercial compositional simulator. Not used and should be defaulted with 1*.","units":{},"default":"1*","value_type":"DOUBLE"},{"index":14,"name":"MOLARATE","description":"Total molar rate used in the commercial compositional simulator. Not used and should be defaulted with 1*.","units":{},"default":"1*","value_type":"DOUBLE"},{"index":15,"name":"STEAMRAT","description":"Thermal/Temperature steam rate (Cold Water Equivalent) for steam producers used in the commercial compositional simulator. Not used and should be defaulted with 1*.","units":{},"default":"1*","value_type":"DOUBLE"},{"index":16,"name":"DELTAP","description":"Thermal/Temperature delta pressure offset for steam producers used in the commercial compositional simulator. Not used and should be defaulted with 1*.","units":{},"default":"1*","value_type":"DOUBLE"},{"index":17,"name":"DELTAT","description":"Thermal/Temperature delta temperature offset for steam producer used in the commercial compositional simulator. Not used and should be defaulted with 1*.","units":{},"default":"1*","value_type":"DOUBLE"},{"index":18,"name":"CALRATE","description":"Calorific production rate used in the commercial compositional simulator. Not used and should be defaulted with 1*.","units":{},"default":"1*","value_type":"DOUBLE"},{"index":19,"name":"COMBPROC","description":"Linearly combined procedure for when exceeding COMBRATE, used in the commercial compositional simulator. Not used and should be defaulted with 1*.","units":{},"default":"1*","value_type":"DOUBLE"},{"index":20,"name":"NGL","description":"A real positive value that defines the observed Natural Gas Liquid (“NGL”) rate in the commercial compositional simulator. Not used and should be defaulted with 1*.","units":{},"default":"1*","value_type":"DOUBLE"}],"example":"The following example defines the production targets and constraints for five wells as follows:\n--\n-- WELL PRODUCTION WELL CONTROLS\n--\n-- WELL OPEN/ CNTL OIL WAT GAS LIQ RES BHP THP VFP VFP\n-- NAME SHUT MODE RATE RATE RATE RATE RATE PRES PRES TABLE ALFQ\nWCONPROD\nOP01 OPEN GRUP 5E3 1* 1* 1* 1* 500.0 /\nOP02 OPEN GRUP 10E3 1* 1* 1* 1* 200.0 500.0 2 0.0 /\nOP03 OPEN GRUP 15E3 1* 1* 1* 1* 200.0 500.0 3 10.0 /\nOP04 OPEN ORAT 20E3 1* 1* 1* 1* 500.0 /\nOP05 SHUT GRUP 20E3 1* 1* 1* 1* 500.0 /\n/\nWell OP01 is open and is on group control, subject to a maximum oil rate constraint of 5,000 stb/d and a minimum bottom-hole pressure of 500 psia. OP02 is also open and on group control but it’s maximum oil rate constraint has been set 10,000 stb/d, and is subject to a minimum bottom-hole pressure limit of 200 psia and a minimum tubing head pressure limit of 500 psia using VFPPROD vertical lift table number two. Well OP03 is very similar to OP02, but with a 15,000 stb/d maximum oil constraint and using VFPPROD vertical lift table number three with an artificial lift parameter of 10. The next well is not on group control. Well OP04 is open and has an oil rate target of 20,000 stb/d, subject to a minimum bottom-hole pressure of 500 psia. Finally, well OP05 is shut and will not be brought back on production despite being put under group control, as the well has been declared shut.\nThe next example defines the production targets and constraints for five wells, of which well OP01 is under group control as the well’s group target and constraints have been set with the GCONPROD keyword, and wells OP02 to OP05 belong to groups that have not had their group constraints set by GCONPROD.\n--\n-- GROUP PRODUCTION CONTROLS\n--\n-- GRUP CNTL OIL WAT GAS LIQ CNTL GRUP GUIDE GUIDE CNTL\n-- NAME MODE RATE RATE RATE RATE OPT CNTL RATE DEF WAT\nGCONPROD\nGRP01 SAT 25E3 1* 1* 1* 1* 1* 1* 1* 1* /\n/\n--\n-- WELL SPECIFICATION DATA\n--\n-- WELL GROUP LOCATION BHP PHASE DRAIN INFLOW OPEN CROSS PVT\n-- NAME NAME I J DEPTH FLUID AREA EQUANS SHUT FLOW TABLE\nWELSPECS\nOP01 SAT 14 13 1* OIL 1* P-P SHUT NO 1* /\n0P02 PLATFORM 64 80 1* OIL 1* GPP SHUT NO 1* /\nOP03 PLATFORM 24 110 1* OIL 1* STD SHUT NO 1* /\nOP04 PLATFORM 24 110 1* OIL 1* STD SHUT NO 1* /\nOP05 PLATFORM 24 110 1* OIL 1* STD SHUT NO 1* /\n/\n--\n-- WELL PRODUCTION WELL CONTROLS\n--\n-- WELL OPEN/ CNTL OIL WAT GAS LIQ RES BHP THP VFP VFP\n-- NAME SHUT MODE RATE RATE RATE RATE RATE PRES PRES TABLE ALFQ\nWCONPROD\nOP01 OPEN 1* 15E3 1* 1* 1* 1* 500.0 /\nOP02 OPEN 1* 1* 5E3* 15E6 1* 1* 200.0 500.0 2 0.0 /\nOP03 OPEN 1* 1* 1* 1* 1* 1* 1* 500.0 3 10.0 /\nOP04 OPEN '' 1* 1* 1* 1* 1* 1* 1* 1* 1* /\nOP05 SHUT 1* 1* 1* 1* 1* 1* 1* 1* 1* 1* /\n/\nHere, well OP01’s control mode, TARGET, will be set to group control (GRUP) and the well’s production parameters will all act as constraints. For well OP02, the well’s control mode is set to GRAT, and the other production parameters all act as constraints. Well OP03 control mode is set to THP and if the well’s BHP value has been previously defined then that value will be used as a constraint; otherwise the default value of one atmosphere will be used instead. Finally, wells OP04 and OP05 will have their control mode set to BHP control. Note in this case, OP04’s status has been set to OPEN; thus the well will produce at a target BHP of one atmosphere, which is unrealistic.","expected_columns":20,"size_kind":"list"},"WCUTBACK":{"name":"WCUTBACK","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, WCUTBACK, defines a well’s cutback limits and parameters for both production and injection wells. See also the GCUTBACK keyword in the SCHEDULE section that provides similar functionality for groups.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"WCT_LIMIT","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/LiquidSurfaceVolume"},{"index":3,"name":"GOR_LIMIT","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"GasDissolutionFactor"},{"index":4,"name":"GLR_LIMIT","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"GasDissolutionFactor"},{"index":5,"name":"WGR_LIMIT","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"OilDissolutionFactor"},{"index":6,"name":"RATE_CUTBACK","description":"","units":{},"default":"1","value_type":"DOUBLE"},{"index":7,"name":"PHASE","description":"","units":{},"default":"","value_type":"STRING"},{"index":8,"name":"PRESSURE_LIMIT","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Pressure"},{"index":9,"name":"PRESSURE_LIMIT_REVERSE","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Pressure"},{"index":10,"name":"WCT_LIMIT_REVERSE","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/LiquidSurfaceVolume"},{"index":11,"name":"GOR_LIMIT_REVERSE","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"GasDissolutionFactor"},{"index":12,"name":"GLR_LIMIT_REVERSE","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"GasDissolutionFactor"},{"index":13,"name":"WGR_LIMIT_REVERSE","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"OilDissolutionFactor"},{"index":14,"name":"WORKOVER_REMOVE","description":"","units":{},"default":"NO","value_type":"STRING"}],"example":"","expected_columns":14,"size_kind":"list"},"WCUTBACT":{"name":"WCUTBACT","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, WCUTBACT, defines a production well’s cutback limits and parameters based on the named produced tracer from the well. See also the GCUTBACT keyword in the SCHEDULE section that provides similar functionality for groups.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"RATE_CUTBACK","description":"","units":{},"default":"1","value_type":"DOUBLE"},{"index":3,"name":"PHASE","description":"","units":{},"default":"","value_type":"STRING"},{"index":4,"name":"WORKOVER_REMOVE","description":"","units":{},"default":"NO","value_type":"STRING"}],"example":"","expected_columns":4,"size_kind":"list"},"WCYCLE":{"name":"WCYCLE","sections":["SCHEDULE"],"supported":null,"summary":"The WCYCLE keyword defines automatic well opening and closing cycling parameters. These are used to model for example “Huff and Puff” cyclic steam injection in heavy oil reservoirs or Water-Alternating-Gas (“WAG”) processes in enhanced oil recovery modeling. The keyword defines specific time periods for automatically cycling wells on and off. For example in a WAG scheme the water injection wells would have one set of cycling parameters and the gas injection wells another, such that only one type of well is active at a time.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well automatic cycling parameters are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"ON_TIME","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Time"},{"index":3,"name":"OFF_TIME","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Time"},{"index":4,"name":"ONTIME","description":"A real positive value that defines the length of time for the on period. The well will be turned off at the beginning of the first time step after the on period has elapsed. If ONTIME is zero or negative then the well will not be turned on by the automatic well cycling.","units":{"field":"day","metric":"day","laboratory":"hour"},"default":"0.0","value_type":"DOUBLE","dimension":"Time"},{"index":5,"name":"OFFTIME","description":"A real positive value that defines the length of time for the off period. If the well was turned off by automatic cycling then it will be turned on at the beginning of the first time step after the off period has elasped. If the well was turned off other than by automatic cycling then the well will remain turned off. If OFFTIME is zero or negative then the well will not be turned on by the automatic well cycling.","units":{"field":"day","metric":"day","laboratory":"hour"},"default":"0.0","value_type":"DOUBLE","dimension":"Time"},{"index":6,"name":"STARTTIME","description":"A real positive value that defines the length of time for the start-up period during which the well efficiency factor will be ramped up. The start-up period begins at the start of the on period. The well’s efficiency factor is ramped up linearly from zero at the start of the on period to the value specified previously by the WEFAC keyword after the start-up period has elasped. The well efficiency factor to apply during each time step is linearly interpolated based on the time at the end of the time step. If the time step size is small compared with STARTTIME then the rate will be ramped up gradually. Whereas, if the time step size is greater than STARTTIME then the rate will ramp up instantaneously potentially causing convergence problems.","units":{"field":"day","metric":"day","laboratory":"hour"},"default":"0.0","value_type":"STRING"},{"index":7,"name":"MAXTS","description":"A real positive value that defines the maximum time step length when the well is turned on by automatic cycling. This overrides the standard maximum time step length. This can help to reduce potential convergence problems caused when a high rate well is opened. If MAXTS is zero then the standard maximum time step length applies.","units":{"field":"day","metric":"day","laboratory":"hour"},"default":"0.0"},{"index":13,"name":"CTRLTS","description":"A defined character string that specifies whether the time steps should be controlled to coincide exactly with the automatic cycling times for this well. CTRLTS should be set to one of the following: YES: time steps are controlled to coincide exactly with the automatic cycling times for this well. Note this will exactly match the specified on and off periods for this well. However, this is likely to reduce the time step size, especially if this option is set for a number automatic cycling wells that have different parameters. NO: time steps are not controlled to coincide exactly with the automatic cycling times for this well. Note this is unlikely to match the specified on and off periods for this well unless they coincide with the report steps. The next period will start at the next time step after the current on/off period has elasped. Therefore, the on/off periods are likely to be longer than specified.","units":{},"default":"NO"}],"example":"The following example defines the cycle lengths for a Water-Alternating-Gas injection scheme with a water-gas slug length ratio of 1:2, and initiates automatic cycling in the water injection well. A maximum time step of 5 days has been specified following the start of each injection period. The simulation then proceeds to the end of the first water injection cycle when automatic cycling is initiated in the gas injection well.\n--\n-- AUTOMATIC CYCLING OF WELLS ON AND OFF\n--\nWCYCLE\n--WELL ON OFF STARTUP STARTUP CTRL\n--NAME PERIOD PERIOD TIME MAXTS TIMESTEP\nI01W 30.0 60.0 1* 5.0 YES /\nI01G 60.0 30.0 1* 5.0 YES /\n--\n-- OPEN WELLS\n--\nWELOPEN\n--WELL OPEN\n--NAME SHUT\nI01W OPEN /\nI01G SHUT /\n/\n--\n-- REPORT STEPS\n--\nTSTEP\n30.0 /\n--\n-- OPEN WELLS\n--\nWELOPEN\n--WELL OPEN\n--NAME SHUT\nI01G OPEN /\n/\nNote that the wells initially need to be opened manually in order to start the automatic cycling. In addition, this needs to be done at the correct times to ensure that the water and gas injection wells are syncronised.","expected_columns":6,"size_kind":"list"},"WDFAC":{"name":"WDFAC","sections":["SCHEDULE"],"supported":null,"summary":"The WDFAC keyword defines a gas well’s D-factor (flow dependent skin factor), which is normally derived from well tests or calculated analytically based on the coefficient of inertial resistance, usually known as β, in Forchheimer’s flow equation,1\n Geertsma, J., 1974. Estimating the Coefficient of Inertial Resistance in Fluid Flow Through Porous Media. Soc.Pet.Eng.J., October: 445-450., 2\n Gewers, C.W.W. and Nichol, L.R., 1969. Gas Turbulence Factor in a Microvugular Carbonate. J.Can.Pet.Tech., April.and 3\n Wong, S.W., 1970. Effects of Liquid Saturation on Turbulence Factors for Gas Liquid Systems. J.Can.Pet.Tech., October.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well D-factor is being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"DFACTOR","description":"A real positive value greater than or equal to zero that defines the D-factor for the well.","units":{"field":"day/Mscf","metric":"day/m3","laboratory":"hour/scc"},"default":"0.0","value_type":"DOUBLE","dimension":"Time/GasSurfaceVolume"}],"example":"--\n-- WELL D-FACTORS\n--\n-- WELL D-\n-- NAME FACTOR\nWEFAC\nGP01 1.0E-03 /\n/\nIn the above example a well D-factor of 10-3 is specified for gas well GP01.","expected_columns":2,"size_kind":"list"},"WDFACCOR":{"name":"WDFACCOR","sections":["SCHEDULE"],"supported":null,"summary":"WDFACCOR keyword defines the parameters to calculate a gas well’s connection D-factors (flow dependent skin factor) for each connection based on a correlation for the coefficient of inertial resistance, usually known as β, in Forchheimer’s flow equation1\n Dake, L.P. Fundamentals of Reservoir Engineering, Amsterdam, The Netherlands, Elsevier Science BV (1978) Chapter 8.6, pages 252-257.,2\n Geertsma, J., 1974. Estimating the Coefficient of Inertial Resistance in Fluid Flow Through Porous Media. Soc.Pet.Eng.J., October: 445-450., 3\n Gewers, C.W.W. and Nichol, L.R., 1969. Gas Turbulence Factor in a Microvugular Carbonate. J.Can.Pet.Tech., April.and 4\n Wong, S.W., 1970. Effects of Liquid Saturation on Turbulence Factors for Gas Liquid Systems. J.Can.Pet.Tech., October. This keyword uses Dake’s correlation to calculate the D-factor.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well D-factor correlation is being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"A","description":"A real value greater than or equal to zero that defines the coefficient A in the D-factor correlation.","units":{"field":"cP.day.ft2/mD/Mscf","metric":"cP.day.m2/mD/sm3","laboratory":"cP.hour.cm2/mD/scc"},"default":"0.0","value_type":"DOUBLE","dimension":"Viscosity*Time*Area/Permeability*GasSurfaceVolume"},{"index":3,"name":"B","description":"A real value that defines the exponent B of the grid block permeability in the D-factor correlation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.0","value_type":"DOUBLE","dimension":"1"},{"index":4,"name":"C","description":"A real value that defines the exponent C of the grid block porosity in the D-factor correlation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.0","value_type":"DOUBLE","dimension":"1"}],"example":"In the first example the connection D-factors for gas well GP01 are evaluated for correlation coefficients specified in field units based on the laboratory determined relationship between β and the absolute permeability presented by Dake in Fig. 8.8 (variation of β with porosity has been neglected).\n--\n-- WELL D-FACTOR CORRELATIONS\n--\n-- WELL\n-- NAME A B C\nWEFAC\nGP01 6.04E-05 -1.1045 0.0 /\n/\nIn the second example the same correlation coefficients are specified in metric units.\n--\n-- WELL D-FACTOR CORRELATIONS\n--\n-- WELL\n-- NAME A B C\nWEFAC\nGP01 1.20E-07 -1.1045 0.0 /\n/\n| [D``=``A K_e^B %phi^C K_e over h 1 over r_w { %gamma_g } over { %mu_g }] | (12.3.260.1) |\n|--------------------------------------------------------------------------|--------------|","expected_columns":4,"size_kind":"list"},"WDRILPRI":{"name":"WDRILPRI","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, WDRILPRI, adds wells to the Drilling Priority Drilling Queue and defines the well priority and drilling unit number or batch queue sequence for the well. The batch queue sequence number enables all wells with the same sequence number to drilled at the same time.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"PRIORITY","description":"","units":{},"default":"-1","value_type":"DOUBLE"},{"index":3,"name":"DRILLING_UNIT","description":"","units":{},"default":"0","value_type":"INT"}],"example":"","expected_columns":3,"size_kind":"list"},"WDRILRES":{"name":"WDRILRES","sections":["SCHEDULE"],"supported":false,"summary":"The WDRILRES keyword activates the prevention of multi-completions being completed in the same cell for wells in a drilling queue. Setting this option stops any well defined as a queued well via the QDRILL and WDRILLPRI keywords in the SCHEDULE section, or any wells set to automatic opening by setting the STATUS variable to AUTO on the WCONPROD keyword in the RUNSPEC section, from opening if there is an already existing active well connection to a cell.","parameters":[],"example":"","size_kind":"none","size_count":0},"WDRILTIM":{"name":"WDRILTIM","sections":["SCHEDULE"],"supported":false,"summary":"WDRILTIM defines the automatic drilling parameters used to describe the numbers of days taken to drill a well, the drilling status of the well, and status of other wells when drilling an automatically drilled well.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"DRILL_TIME","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Time"},{"index":3,"name":"WORKOVER_CLOSE","description":"","units":{},"default":"","value_type":"STRING"},{"index":4,"name":"COMPARTMENT","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":4,"size_kind":"list"},"WECON":{"name":"WECON","sections":["SCHEDULE"],"supported":true,"summary":"The WECON keyword defines the economic criteria for production wells that have previously been defined by the WELSPECS and WCONPROD keywords in the SCHEDULE section.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well economic criteria data is being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"ORAT","description":"A real positive value that defines the minimum economic surface oil production rate, below which an economic action will take place, as outlined below: If there are any remaining connections in the well with the STATUS variable set to AUTO on the COMPDAT keyword in the SCHEDULE section, then one of these connections (or completion) will be opened. If there are no remaining connections in the well with the STATUS variable set to AUTO on the COMPDAT keyword, then the well will be shut or stopped as requested by item (9) of the WELSPECS keyword. Only option (2) is supported by OPM Flow as STATUS equals AUTO on the COMPDAT keyword is currently not supported by the simulator. Hence, the well be either shut or stopped. A value less than or equal to zero switches off this criterion. This value may be specified using a User Defined Argument (UDA).","units":{"field":"stb/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"0.0","value_type":"UDA","dimension":"LiquidSurfaceVolume/Time"},{"index":3,"name":"GRAT","description":"A real positive value that defines the minimum economic surface gas production rate, below which an economic action will take place, as outlined below: If there are any remaining connections in the well with the STATUS variable set to AUTO on the COMPDAT keyword in the SCHEDULE section, then one of these connections (or completion) will be opened. If there are no remaining connections in the well with the STATUS variable set to AUTO on the COMPDAT keyword, then the well will be shut or stopped as requested by item (9) of the WELSPECS keyword. Only option (2) is supported by OPM Flow as STATUS equals AUTO on the COMPDAT keyword is currently not supported by the simulator. Hence, the well be either shut or stopped. A value less than or equal to zero switches off this criterion. This value may be specified using a User Defined Argument (UDA).","units":{"field":"Mscf/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"0.0","value_type":"UDA","dimension":"GasSurfaceVolume/Time"},{"index":4,"name":"WCUT","description":"A real positive value that defines the maximum economic surface water cut, above which an economic action will take place. This value may be specified using a User Defined Argument (UDA). Water cut is defined as:[f sub w ~=~ {q sub w } over {q sub w `+` q sub o}], and the various actions that are available if the water cut limit is exceeded are described in item (7)., and the various actions that are available if the water cut limit is exceeded are described in item (7). A value less than or equal to zero switches off this criterion.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.0","value_type":"UDA"},{"index":5,"name":"GOR","description":"A real positive value that defines the maximum economic surface gas-oil ratio, above which an economic action will take place, as defined by item (7). A value less than or equal to zero switches off this criterion. This value may be specified using a User Defined Argument (UDA).","units":{"field":"Mscf/stb","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"0.0","value_type":"UDA","dimension":"GasSurfaceVolume/LiquidSurfaceVolume"},{"index":6,"name":"WGR","description":"A real positive value that defines the maximum economic surface water-gas ratio, above which an economic action will take place, as defined by item (7). A value less than or equal to zero switches off this criterion. This value may be specified using a User Defined Argument (UDA).","units":{"field":"stb/Mscf","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"0.0","value_type":"UDA","dimension":"LiquidSurfaceVolume/GasSurfaceVolume"},{"index":7,"name":"ACTION","description":"A defined character string that defines the action to be taken if the economic WCUT, GOR, or WGR limits are violated. ACTION should be set to one of the following character strings: NONE: no action is taken. CON: close the worst offending connection. If connections have been grouped as completions then the worst offending completion will be closed. +CON: close the worst offending connection and all below it. If connections have been grouped as completions then the worst offending completion and all below it will be closed. WELL: shut or stop the well as per the AUTO variable on the WELSPECS keyword. The corrective action takes places at the end of the time step in which the constraint is violated. The +CON option is not currently supported by OPM Flow.","units":{},"default":"NONE","value_type":"STRING","options":["NONE","CON","WELL"]},{"index":8,"name":"END","description":"A defined character string that defines if the simulation should terminate if the well is shut or stopped. END should be set to one of the following character strings: NO: no action is taken and the run continues. YES: terminate the run at the next report time step. The YES option is not currently supported by OPM Flow.","units":{},"default":"NO","value_type":"STRING","options":["NO","YES"]},{"index":9,"name":"WELOPEN","description":"A character string of up to eight characters in length that defines the name of the well, which will be opened when the current well (WELNAME) has been automatically closed/shut by the simulator. Wells closed manually do not invoke this opton. The well name (WELOPEN) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":10,"name":"ELTOPT","description":"A defined character string that defines the type of quantity used to test the economic limit, and should be set to one of the following character strings: POTN: The Economic Limit Test (“ELT”) is based on a well’s potential rate. A well’s potential rate is calculated using only the flowing bottom-hole pressure and tubing head pressure constraints, all other constraints are ignored, including group constraints. However, if the WELDRAW keyword in the SCHEDULE section has been used to limit a well’s pressure draw down, then this will also be considered in the potential calculation, as it influences the bottom-hole pressure constraint. RATE: The economic limit is based a well’s surface production rate as oppose to the potential rate, this is the default behavior. Wells under group control via the GCONPROD keyword in the SCHEDULE section will be subject to the ELT, except for when the group’s production target rate is set to zero. Wells under group control via the GCONPRI keyword in the SCHEDULE section will be subject to the ELT, except for when the group has curtailed a well’s production.","units":{},"default":"RATE","value_type":"STRING"},{"index":11,"name":"WCUT2","description":"A real positive value that defines the secondary maximum economic surface water cut, above which an economic action will take place. A value less than or equal to zero switches off this criterion. This item is not supported by OPM Flow and should be defaulted (1*) or set to zero.","units":{},"default":"0.0","value_type":"DOUBLE"},{"index":12,"name":"ACTION2","description":"A defined character string that defines the action to be taken if the secondary economic WCUT2 limits is violated. This item is not supported by OPM Flow and should be defaulted (1*).","units":{},"default":"1*","value_type":"STRING"},{"index":13,"name":"GLR","description":"A real positive value that defines the maximum economic surface gas-liquid ratio, above which an economic action will take place, as defined by item (7). A value less than or equal to zero switches off this criterion. This item is not supported by OPM Flow and should be defaulted (1*).","units":{},"default":"None","value_type":"DOUBLE"},{"index":14,"name":"LRAT","description":"A real positive value that defines the minimum liquid rate, below which the well (WELNAME) is shut-in. This item is not supported by OPM Flow and should be defaulted (1*).","units":{},"default":"0.0","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time"},{"index":15,"name":"TEMP","description":"A real positive value that defines the maximum economic temperature in the commercial compositional Thermal/Temperature model for a well. This item is not supported by OPM Flow and should be defaulted (1*).","units":{},"default":"None","value_type":"DOUBLE","dimension":"Temperature"},{"index":16,"name":"RESV","description":"A real positive value that defines the minimum reservoir volume rate, below which the well (WELNAME) is shut-in. This item is not supported by OPM Flow and should be defaulted (1*).","units":{},"default":"0.0","value_type":"DOUBLE","dimension":"ReservoirVolume/Time"}],"example":"The following example defines one oil well and one gas well using the WELSPECS keyword, together with their economic criteria.\n--\n-- WELL SPECIFICATION DATA\n--\n-- WELL GROUP LOCATION BHP PHASE DRAIN INFLOW SHUT CROSS PRESS\n-- NAME NAME I J DEPTH FLUID AREA EQUA. IN FLOW TABLE\nWELSPECS\nGP01 PLATFORM 14 13 1* GAS 1* GPP SHUT NO 1* /\nOP01 PLATFORM 28 96 1* OIL 1* STD SHUT NO 1* /\n/\n--\n-- WELL ECONOMIC CRITERIA FOR PRODUCTION WELLS\n-- WELL MIN MIN MAX MAX MAX CNTL END\n-- NAME ORAT GRAT WCUT GOR WGR MODE RUN\nWECON\nGP01 1* 5.0E3 1* 1* 1* 'WELL' 'NO' /\nOP01 500 1* 0.95 15 1* 'WELL' 'YES' /\n/\nWell GP01 has a minimum economic gas rate of 5 MMscf/d and will shut-in if the gas rate falls below this rate, but the simulation will continue even if this occurs. Well OP01 has a minimum economic oil rate of 500 stb/d, a maximum water cut limit of 95%, and a maximum GOR of 15 Mscf/stb, if any any of these limits are violated the well will be shut-in and the run should be terminated at the next reporting time step, however the option to end the run is not currently supported by OPM Flow.","expected_columns":16,"size_kind":"list"},"WECONINJ":{"name":"WECONINJ","sections":["SCHEDULE"],"supported":false,"summary":"The WECONINJ keyword defines economic criteria for injection wells that have previously been defined by the WELSPECS and WCONINJE keywords in the SCHEDULE section.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well economic injection criteria data is being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"MINVALUE","description":"A real positive value that defines the minimum economic injection value, below which an economic action will take place, as defined by the AUTO parameter on the WELSPECS keyword (SHUT or STOP). Note that TYPE determines if the minimum value is applied to the well’s actual injection rate or the well’s potential. A value less than or equal to zero switches off this criterion.","units":{"field":"Liquid stb/d Gas Mscf/d","metric":"Liquid sm3/day Gas sm3/day","laboratory":"Liquid scc/hour Gas scc/hour"},"default":"0.0","value_type":"DOUBLE"},{"index":3,"name":"TYPE","description":"A defined character string that determines if MINVALUE is applied to a well’s actual rate or potential, and should be set to one of the following: RATE: In this case the MINVALUE is applied to a well’s actual rate. POTN: Here, MINVALUE is applied to the well’s potential with only the BHP and THP constraints applied. The default value is RATE.","units":{},"default":"RATE","value_type":"STRING"}],"example":"The following example defines the economic injection parameters for all gas and water injection wells.\n--\n-- WELL ECONOMIC LIMIT DATA FOR INJECTION WELLS\n--\n-- WELL MIN RATE\n-- NAME VALUE POTN\nWECONINJ\nGI* 2.0E3 RATE /\nWI* 5.0E3 POTN /\n/\nHere all the gas injection wells have a minimum economic gas injection rate of 2 MMscf/d and the water injection wells have a minimum water potential rate of 5,000 stb/d. The AUTO parameter on the WELSPECS keyword will determine if the wells will be shut-in or stopped.","expected_columns":3,"size_kind":"list"},"WECONT":{"name":"WECONT","sections":["SCHEDULE"],"supported":false,"summary":"The WECONT keyword defines the tracer economic criteria for production wells that have previously been defined by the WELSPECS and WCONPROD keywords in the SCHEDULE section, for tracers define by the TRACER keyword in the PROPS section.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well target and constraints are being defined.","units":{},"default":"None","record":1,"value_type":"STRING"},{"index":1,"name":"NAME","description":"A three letter character string defining the tracer’s name. Note it is best to void names beginning with the letters F, S, and T as these names may create naming issues in post-processing software.","units":{},"default":"None","record":2,"value_type":"STRING"},{"index":2,"name":"ACTION","description":"A defined character string that defines the action to be taken if the economic WCUT, GOR, or WGR limits are violated. ACTION should be set to one of the following character strings: NONE: no action is taken. CON: close the worst offending connection in the worst offending. If connections have been welled as completions then the worst offending completion will be closed. +CON: close the worst offending connection and all below it in the worst offending well. If connections have been welled as completions then the worst offending completion and all below it in the worst offending well will be closed. WELL: shut or stop the well as per the AUTO variable on the WELSPECS keyword. PLUG: plug back the worst offending well based on the plug back length and options defined on the WPLUG keyword in the SCHEDULE. The corrective action takes places at the end of the time step in which the constraint is violated.","units":{},"default":"None","record":1,"value_type":"STRING","options":["NONE","CON","WELL","PLUG"]},{"index":2,"name":"MXTOTAL","description":"A real positive value that defines the maximum total (free plus solution) tracer rate. Tracer units are per those defined by the carrying fluid, oil, gas, water, etc.","units":{},"default":"None","record":2,"value_type":"STRING"},{"index":3,"name":"END","description":"A defined character string that defines if the simulation should terminate if the well is shut or stopped. END should be set to one of the following character strings: NO: no action is taken and the run continues. YES: terminate the run at the next report time step.","units":{},"default":"NO","record":1,"value_type":"STRING","options":["NO","YES"]},{"index":3,"name":"MXFREET","description":"A real positive value that defines the maximum total (free plus solution) tracer concentration. Tracer units are per those defined by the carrying fluid, oil, gas, water, etc.","units":{},"default":"None","record":2,"value_type":"STRING"},{"index":4,"name":"WELL","description":"A character string of up to eight characters in length that defines the well name of a fully defined well that will be “opened” when the well WELNAME is shut-in or stopped.","units":{},"default":"None","record":1,"value_type":"STRING"},{"index":4,"name":"MXFREEQ","description":"A real positive value that defines the maximum free tracer rate. Tracer units are per those defined by the carrying fluid, oil, gas, water, etc.","units":{},"default":"None","record":2,"value_type":"STRING"},{"index":5,"name":"MXCONC","description":"A real positive value that defines the maximum free tracer concentration. Tracer units are per those defined by the carrying fluid, oil, gas, water, etc.","units":{},"default":"None","record":2},{"index":6,"name":"MXSOLNQ","description":"A real positive value that defines the maximum solution rate. Tracer units are per those defined by the carrying fluid, oil, gas, water, etc.","units":{},"default":"None","record":2},{"index":7,"name":"MXSOLNC","description":"A real positive value that defines the maximum solution concentration. Tracer units are per those defined by the carrying fluid, oil, gas, water, etc.","units":{},"default":"","record":2}],"example":"The following example defines the tracer economic criteria for the field and two wells, OP01 and OP02.\n--\n-- WELL TRACER ECONOMIC CRITERIA FOR PRODUCTION WELLS\n--\n-- WELL WORK END MAX\n-- NAME OVER RUN WELLS\nWECONT\nOP01 +CON 'YES' 1* / START OF WELL\n--\n-- TRACER TRACER TRACER TRACER TRACER TRACER TRACER\n-- NAME TOTAL TOTAL FREE FREE SOLN SOLN\n-- RATE CONCEN RATE CONCEN RATE CONCEN\nPLY 800.0 /\nBRI 800.0 /\n/\nOP02 +CON 'YES' 1* / START OF WELL\n--\n-- TRACER TRACER TRACER TRACER TRACER TRACER TRACER\n-- NAME TOTAL TOTAL FREE FREE SOLN SOLN\n-- RATE CONCEN RATE CONCEN RATE CONCEN\nPLY 800.0 /\nBRI 800.0 / END OF WELL\n/ END OF KEYWORD\nIf the economic limits are violated then the worst offending connection and all below it in the worst offending well will be closed, If connections have been grouped as completions then the worst offending completion and all below it in the worst offending well will be closed","expected_columns":4,"size_kind":"list"},"WEFAC":{"name":"WEFAC","sections":["SCHEDULE"],"supported":null,"summary":"Defines a well’s efficiency or up-time as opposed to setting the efficiency at the group level.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well efficiency factor is being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"FACTOR","description":"A real positive value greater than zero and less than or equal to one that defines the efficiency factor for the well. If a well’s down time is 5% then FACTOR should be set to 0.95 (1.0 – 0.05). Note that well pressures and rates are calculated at their full flowing conditions but subject to any operating constraints, that is without the well efficiency being applied (FACTOR), in order to represent the actual flowing conditions in the field. The effective rates and volumes are calculated by applying FACTOR when summing individual well rates to their group level and higher, including summing to the top most group FIELD. In terms of a well’s cumulative production, FACTOR is applied to the well rate times the time interval for the time step. This ensures that correct effective volume is withdrawn from (or injected to) the reservoir. This approach means that wells are effectively arbitrarily offline for a period during a time step, as opposed to all wells going offline concurrently. And thus the group and field rates and volumes are the effective rates and volumes for the field.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0","value_type":"DOUBLE"},{"index":3,"name":"WELNETWK","description":"A defined character string that determines if the WELNAME efficiency factor should be applied when calculating the flows and pressure losses in the Extended Network Model, and should be set to either: NO: The well’s equivalent Extended Network Model node flow rates are not multiplied by the efficiency factor FACTOR. YES: The well’s equivalent Extended Network Model node flow rates are multiplied by the efficiency factor FACTOR This option is only applicable for the Extended Network Model, as in the Standard Network Model groups flow rates are always used in the calculation of pressure drops (this is equivalent to the default option, YES).","units":{},"default":"YES","value_type":"STRING"}],"example":"--\n-- WELL EFFICIENCY FACTORS\n--\n-- WELL EFF NETWK\n-- NAME FACT OPTN\nWEFAC\n'GP* ' 0.950 /\n'OP* ' 0.862 /\n/\nIn the above example the all the gas wells are are defined as having a well efficiency factor (up time) of 0.950 and all the oil wells have a lower efficiency factor of 0.862.\n| Note One can also apply plant efficiencies through the GEFAC keyword in the SCHEDULE section. If all the wells in a group are flowing through a facility that has an overall efficiency factor, then it is more appropriate to apply the efficiency factor at the group level. This of course does not preclude applying additional well efficiencies to individual wells. For example, subsea wells (wet trees) may have additional down time compared to platform wells (dry trees) even though both sets of well are flowing through the same platform. Another example would be gas lift wells and wells using electrical submersible pumps, as their artificial lift mechanisms. |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":3,"size_kind":"list"},"WELCNTL":{"name":"WELCNTL","sections":["SCHEDULE"],"supported":false,"summary":"The WELCNTL keyword modifies a well’s target control and value, both rates and pressures, for previously defined wells without having to define all the variables on the well control keywords: WCONPROD, WCONHIST, WCONINJE, or WCONINJH keywords. Variables not changed by the WELCNTL keyword remain the same as those previously entered via the well control keywords or previously entered WELCNTL keywords. Note that the well must still be initially be fully defined using the WCONPROD or WCONINJE keywords. All the aforementioned keywords are described in the SCHEDULE section.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well production rates and pressures data are being redefined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS and WCONPROD (or WCONINJE) keywords in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"TARGET","description":"A defined character string that sets the item to be changed for the well the value of the item is set by item (3). ORAT: reset the surface oil production rate value as defined by item (3). WRAT: reset the surface water production rate value as defined by item (3). GRAT: reset the surface gas production rate value as defined by item (3). LRAT: reset the surface liquid (oil plus water) production rate value as defined by (3). RESV: reset he in situ reservoir volume rate value as defined by (3). BHP: reset the bottom-hole pressure value as defined by item (3). THP: reset the tubing head pressure value for the well as defined by item (3). VFP: reset the vertical lift performance table number as defined by (3). LIFT: reset the artificial lift quantity for use with vertical lift performance tables. GUID: reset the guide rate value for wells operating under group control. Note TARGET redefines the target controlled for a well and the control value on item (4). For example, if a well is operating on ORAT control, as defined by the previously entered WCONPROD keyword, entering TARGET equal to LRAT with a value, sets the TARGET to liquid rate with the given value. That is the well will be targeting a liquid rate not the previously requested oil ratel. Use the WELTARG keyword in the SCHEDULE section to change the target and constraint values for a well.","units":{},"default":"None","value_type":"STRING","options":["ORAT","WRAT","GRAT","LRAT","RESV","BHP","THP","VFP","LIFT","GUID"]},{"index":3,"name":"VALUE Liquid Gas Res Vol Pressure VFP LIFT","description":"A real positive value that defines the value of the variable declared by TARGET","units":{"field":"stb/d Mscf/d rb/d psia dimensionless same as VFPPROD or VFPINJ","metric":"sm3/day sm3/day rm3/day barsa dimensionless same as VFPPROD or VFPINJ","laboratory":"scc/hour scc/hour rcc/hour atma dimensionless same as VFPPROD or VFPINJ"},"default":"None","value_type":"DOUBLE"}],"example":"The following example below shows the oil rates for the OP01 oil producer at the start of the schedule section (January 1, 2000).\n-- ------------------------------------------------------------------------------\n-- 01 JAN 2000 START OF SCHEDULE SECTION\n-- ------------------------------------------------------------------------------\n--\n-- WELL PRODUCTION WELL CONTROLS\n--\n-- WELL OPEN/ CNTL OIL WAT GAS LIQ RES BHP THP VFP VFP\n-- NAME SHUT MODE RATE RATE RATE RATE RATE PRES PRES TABLE ALFQ\nWCONPROD\nOP01 OPEN ORAT 3000 1* 1* 1* 1* 750.0 500. 9 1* /\n/ DATES\n01 FEB 2000 /\n/\n--\n-- WELL CONTROL MODE AND OPERATING TARGET\n--\n-- WELL WELL TARGET\n-- NAME CNTL VALUE WELCNTL\nOP01 LRAT 5000 /\n/\nFrom January 1, 2000 to February 1, 2000 well OP01 is open and is on oil rate control and has a target oil rate of 3,000 stb/d and uses VFPPROD vertical lift table number 9 with a minimum tubing head pressure constraint of 500 psia. After February 1, 2000 the well is changed to liquid control with a target rate of 5,000 stb/d of liquid and all the other parameters remain unchanged.","expected_columns":3,"size_kind":"list"},"WELDEBUG":{"name":"WELDEBUG","sections":["SCHEDULE"],"supported":false,"summary":"This keyword defines the well debug data to be written to the debug file (*.DBG). This keyword is not supported by OPM Flow but would change the results if supported so the simulation will be stopped.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"DEBUG_FLAG","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":2,"size_kind":"list"},"WELDRAW":{"name":"WELDRAW","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, WELDRAW, defines the maximum draw down for production wells The keyword may be useful in wells that are subject to fines or sand production to limit the draw down between the sand face and the well in order to limit or avoid sand production.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"MAX_DRAW","description":"","units":{},"default":"","value_type":"UDA","dimension":"Pressure"},{"index":3,"name":"PHASE","description":"","units":{},"default":"","value_type":"STRING"},{"index":4,"name":"USE_LIMIT","description":"","units":{},"default":"NO","value_type":"STRING"},{"index":5,"name":"GRID_BLOCKS","description":"","units":{},"default":"AVG","value_type":"STRING"}],"example":"","expected_columns":5,"size_kind":"list"},"WELEVNT":{"name":"WELEVNT","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, WELEVNT, defines an integer value to be assigned to an individual well’s WPWEM summary variable that is written to the SUMMARY file. The value is set to zero after the current time step.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"WPWEM_VALUE","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":2,"size_kind":"list"},"WELLSTRE":{"name":"WELLSTRE","sections":["SCHEDULE"],"supported":true,"summary":"The WELLSTRE keyword defines a well stream together with the compositional component mole factions, associated with the well stream, as such it should have the same number of entries as that declared via the COMPS keyword in the RUNSPEC section, and the NCOMPS keyword in the PROPS section. Once a gas well stream has been defined, it can be used with either the WINJGAS or GINJGAS keywords in the SCHEDULE section, to set the injected gas composition. Similarly, if an oil well stream has been defined by WELLSTRE, then the well stream can be used with the WINJOIL keyword in the SCHEDULE section, to specify the injected oil composition.","parameters":[{"index":1,"name":"STREAM","description":"STREAM is a character string of up to eight characters in length, representing the well stream name. The WELLDIMS(MXSTRMS) parameter in the RUNSPEC section determines the maximum number of well streams allowed in the model.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"ZCOMP","description":"A row vector, with each item representing a compositional component mole fraction for a given component. In addition, the sum of the compositional component mole fractions must sum to one, otherwise an error will occur. Note that the number ZCOMP values, should be the same as that entered via the NCOMPS keyword in the PROPS section, and the COMPS keyword in the RUNSPEC section. However, for a given ZCOMP component, the mole fraction may be defaulted with 1*, in which case the mole fraction is set to zero. Secondly, ZCOMP may be terminated early, in this case the undefined mole fractions will be set to zero. Finally, only the default value of two components are currently supported by OPM Flow.","units":{"field":"mole fraction","metric":"mole fraction","laboratory":"mole fraction"},"default":"None","value_type":"DOUBLE","dimension":"1"}],"example":"The following example defines how to specify a two component formulation, together with defining the names of the composition components, to be used with the CO2STORE and GASWAT options.\n-- ==============================================================================\n--\n-- PROPS SECTION\n--\n-- ==============================================================================\nPROPS --\n-- CONFIRM NUMBER OF COMPOSITIONAL COMPONENTS (OPM FLOW KEYWORD)\n--\nNCOMPS\n2 /\n--\n-- DEFINE COMPOSITIONAL COMPONENTS NAMES (OPM FLOW KEYWORD)\n--\nCNAMES\n'CO2'\n'H2O' /\nThe second part of the example, defines the well stream for the above two component CO2 water system.\n-- ==============================================================================\n--\n-- SCHEDULE SECTION\n--\n-- ==============================================================================\nSCHEDULE\n--\n-- WELL STREAM INJECTION COMPOSITION (OPM FLOW Keyword)\n--\n-- WELL -- WELL STREAM COMPOSITIONAL COMPONENT --\n-- STREAM -- MOLE FRACTIONS --\nWELLSTRE\n'C02STREAM' 1.000 0.000 /\n/\nHere the well stream consists of 100% CO2 and zero water.\n| Note This is an OPM Flow keyword used with OPM Flow’s CO2STORE and GASWAT keywords in the RUNSPEC section, and should not be confused with the more general version of the WELLSTRE keyword used in the commercial compositional simulator. Secondly, although OPM Flow parses the keyword, the simulator currently ignores the data for this keyword. |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"list","variadic_record":true},"WELMOVEL":{"name":"WELMOVEL","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, WELMOVEL, moves a previously defined gloabal well into a previously declared Local Grid Refinement (“LGR”), in a RESTART run. The keyword should only be used in RESTART runs.","parameters":[{"index":1,"name":"WELLNAME","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"LGRNAME","description":"","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"WELLHEAD_I","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"WELLHEAD_J","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":4,"size_kind":"list"},"WELOPEN":{"name":"WELOPEN","sections":["SCHEDULE"],"supported":null,"summary":"The WELOPEN keyword defines the status of wells and well connections, and is used to open and shut previously defined wells and well connections without having to re-specify all the data on the well control keywords: WCONPROD, WCONHIST, WCONINJE, or WCONINJH keywords. Note that the well must still be initially fully defined using the WCONPROD or WCONINJE keywords. All the aforementioned keywords are described in the SCHEDULE section.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well or well connection status data are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"STATUS","description":"A defined character string of length four that defines the well or well connection operational status, STATUS should be set to one of the following character strings: OPEN: the well or connections are open to flow. SHUT: the well or connections are closed to flow (shut-in). AUTO: the well or connections are initially closed, but may be opened automatically if an economic limit is violated.","units":{},"default":"OPEN","value_type":"STRING","options":["OPEN","SHUT","AUTO"]},{"index":3,"name":"I","description":"An integer less than or equal to NX that defines the connection location in the I-direction.","units":{},"default":"Negative","value_type":"INT"},{"index":4,"name":"J","description":"An integer less than or equal to NY that defines the connection location in the J-direction.","units":{},"default":"Negative","value_type":"INT"},{"index":5,"name":"K","description":"An integer less than or equal to NZ that defines the connection location in the K-direction.","units":{},"default":"Negative","value_type":"INT"},{"index":6,"name":"C1","description":"An integer less than or equal to the total number of completions that defines the first completion in the range.","units":{},"default":"Negative","value_type":"INT"},{"index":7,"name":"C2","description":"An integer less than or equal to the total number of completions that defines the last completion in the range.","units":{},"default":"Negative","value_type":"INT"}],"example":"The following example defines two vertical oil wells using the WELSPECS keyword and their associated connection data.\n-- WELL SPECIFICATION DATA\n--\n-- WELL GROUP LOCATION BHP PHASE DRAIN INFLOW SHUT CROSS PRESS\n-- NAME NAME I J DEPTH FLUID AREA EQUA. IN FLOW TABLE\nWELSPECS\nOP01 PLATFORM 14 13 1* OIL 1* STD OPEN NO 1* /\nOP02 PLATFORM 28 96 1* OIL 1* STD OPEN NO 1* /\n/\n--\n-- WELL PRODUCTION WELL CONTROLS\n--\n-- WELL OPEN/ CNTL OIL WAT GAS LIQ RES BHP THP VFP VFP\n-- NAME SHUT MODE RATE RATE RATE RATE RATE PRES PRES TABLE ALFQ\nWCONPROD\n‘*’ SHUT GRUP 1* 1* 1* 1* 1* 200.0 /\n/\n-- WELL CONNECTION DATA\n--\n-- WELL --- LOCATION --- OPEN SAT CONN WELL KH SKIN D DIR\n-- NAME II JJ K1 K2 SHUT TAB FACT DIA FACT FACT FACT PEN\nCOMPDAT\nOP01 1* 1* 1 10 SHUT 1* 1* 0.708 1* 0.0 1* 'Z' /\nOP01 1* 1* 15 30 SHUT 1* 1* 0.708 1* 0.0 1* 'Z' /\nOP01 1* 1* 35 90 SHUT 1* 1* 0.708 1* 0.0 1* 'Z' /\nOP02 1* 1* 1 10 SHUT 1* 1* 0.708 1* 0.0 1* 'Z' /\n/\n--\n-- DEFINE WELL AND WELL CONNECTIONS FLOWING STATUS\n--\n-- WELL WELL --LOCATION-- COMPLETION\n-- NAME STAT I J K FIRST LAST\nWELOPEN\nOP01 OPEN /\nOP01 OPEN 0 0 1 /\nOP01 OPEN 0 0 2 /\nOP01 OPEN 0 0 3 /\nOP01 OPEN 0 0 4 /\nOP02 OPEN /\nOP02 OPEN 0 0 0 /\n/\nIn this example the first record for each well in the WELOPEN keyword changes the well status from shut (as per the WCONPROD keyword) to open. Then for well OP01 well connections in layers one to four are opened for flow and all the connections for well OP02 are opened, that is the connections in layers one to ten.\nThe next example shows the use of the COMPLUMP keyword to group the well connections into well completions for wells OP01, OP02 and OP03, and then use the WELOPEN keyword to open the well and the well completions.\n--\n-- ASSIGN WELL CONNECTIONS TO COMPLETIONS\n--\n-- WELL --- LOCATION --- COMPL\n-- NAME II JJ K1 K2 NO.\nCOMPLUMP\nOP01 0 0 1 10 1 / COMPLETION NO. 01\nOP01 0 0 15 30 2 / COMPLETION NO. 02\nOP01 0 0 35 90 3 / COMPLETION NO. 03\nOP02 0 0 15 30 2 / COMPLETION NO. 02\nOP02 0 0 35 90 3 / COMPLETION NO. 03\nOP03 0 0 1 10 1 / COMPLETION NO. 01\nOP03 0 0 35 90 3 / COMPLETION NO. 03\n/\n--\n-- DEFINE WELL AND WELL CONNECTIONS FLOWING STATUS\n--\n-- WELL WELL --LOCATION-- COMPLETION\n-- NAME STAT I J K FIRST LAST\nWELOPEN\nOP01 OPEN /\nOP01 OPEN 0 0 0 3 3 /\nOP02 OPEN /\nOP02 OPEN 0 0 0 2 2 /\nOP03 OPEN /\nOP03 OPEN 0 0 0 0 0 /\n/\nAgain, the first record of each well WELOPEN keyword changes the well status from shut (as per the WCONPROD keyword) to open. Then for well OP01 well completion number three is opened (connections 35 to 90), completion two (connections 15 to 30) for well OP02 and completion numbers one to three (all the connections) for well OP03. Note that there is no completion number two for OP03 so connections 15 to 30 will not be opened.\nNote the last completion number for well OP03 was named completion number three, but it could have been named number two as well. The reason why it was named number three instead of two was because it was assumed (for the example) that layers 35 to 90 represent a particular reservoir, and therefore allowing for the tracking of completions for individual reservoirs, as shown in the example.\nThis example shows how one can open all the wells and well completions for a given reservoir.\n--\n-- DEFINE WELL AND WELL CONNECTIONS FLOWING STATUS\n--\n-- WELL WELL --LOCATION-- COMPLETION\n-- NAME STAT I J K FIRST LAST\nWELOPEN\n‘*’ OPEN /\n‘*’ OPEN 0 0 0 3 3 /\nOP02 SHUT 0 0 0 0 0 /\nOP02 OPEN 0 0 0 2 2 /\n/\nIn this case wells OP01, OP02 and OP03 are opened via completion number three. All the connections for OP02 are then shut, and the connections associated with completion two are opened instead for this well.","expected_columns":7,"size_kind":"list"},"WELOPENL":{"name":"WELOPENL","sections":["SCHEDULE"],"supported":false,"summary":"The WELOPENL keyword defines the status of wells and well connection in Local Grid Refinement Grids (“LGR”) and is used to open and shut previously defined well and well connections without having to re-specify all the data on the well control keywords: WCONPROD, WCONHIST, WCONINJE, or WCONINJH keywords. Note that the well must still be initially be fully defined using the WCONPROD or WCONINJE keywords. All the aforementioned keywords are described in the SCHEDULE section","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well and well connection status data is being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"LGRNAME","description":"A character string of up to eight characters in length that defines the LGR name for which the well LGR connection data are being defined. Note that the well name (LGRNAME) must have been declared previously using the WELSPECL keyword in the SCHEDULE section, otherwise an error may occur. If defaulted with 1* the LGR on the WELSPECL keyword will be utilized.","units":{},"default":"Defined","value_type":"STRING"},{"index":3,"name":"STATUS","description":"A character string of length four that defines the well and a well’s connections’ operational status, STATUS should be set to one of the following character strings: OPEN: the connections are open to flow. SHUT: the connections are closed to flow (shut-in). AUTO: the connection are initially closed, but may be opened automatically if an economic limit is violated.","units":{},"default":"OPEN","value_type":"STRING","options":["OPEN","SHUT","AUTO"]},{"index":4,"name":"I","description":"An integer less than or equal to NX that defines the connection location in the I-direction.","units":{},"default":"1*","value_type":"INT"},{"index":5,"name":"J","description":"An integer less than or equal to NY that defines the connection location in the J-direction.","units":{},"default":"1*","value_type":"INT"},{"index":6,"name":"K","description":"An integer less than or equal to NZ that defines the connection location in the K-direction.","units":{},"default":"1*","value_type":"INT"},{"index":7,"name":"K1","description":"An integer less than or equal to NZ that defines the UPPER completion location in the K-direction. Connections are lumped into completions via the COMPLUMP keyword, and K1 refers to the first completion number, as defined by the COMPLUMP keyword, and all the connections contained within the K1 completion.","units":{},"default":"1*","value_type":"INT"},{"index":8,"name":"K2","description":"An integer less than or equal to NZ that defines the LOWER completion location in the K-direction. Connections are lumped into completions via the COMPLUMP keyword, and K2 refers to the last completion number, as defined by the COMPLUMP keyword, and all the connections contained within the K2 completion.","units":{},"default":"1*","value_type":"INT"}],"example":"The following example shows the use of the COMPLMPL keyword to group the well connections into well completions for well OP01 and then use the WELOPEN keyword to open the well and the well connections.\n--\n-- ASSIGN WELL LGR CONNECTIONS TO COMPLETIONS\n--\n-- WELL LGR ---LOCATION--- COMPL\n-- NAME NAME II JJ K1 K2 NO.\nCOMPLMPL\nOP01 LGR1 26 58 1 3 1 /\nOP01 LGR1 26 58 4 10 2 /\nOP01 LGR1 26 58 11 12 3 /\n/\n--\n-- WELL PRODUCTION STATUS FOR LGR WELLS\n--\n-- WELL LGR WELL --LOCATION-- COMPLETION\n-- NAME NAME STAT I J K FIRST LAST\nWELOPENL\nOP01 LGR1 OPEN /\nOP01 LGR1 OPEN 0 0 0 1 2 /\nOP01 LGR2 SHUT 0 0 0 3 3 /\n/\nThe first record of the WELOPENL keyword changes the well status from shut (as per the WCONPROD keyword) to open, in case it has been shut-in. Then well completion number one and two are opened (connections 1 to 10), and completion number three shut-in (connections 11 to 12).","expected_columns":8,"size_kind":"list"},"WELPI":{"name":"WELPI","sections":["SCHEDULE"],"supported":null,"summary":"The WELPI keyword is used to define a well’s productivity or injectivity index at the time the keyword is activated. Productivity and injectivity indices are a function of both bottom-hole pressure and mobility and thus will vary in time as the bottom-hole pressure and fluids produce by the well are changing. Thus, the values enter on this keyword for a given well will override any previously calculated values, or values previously entered, using this keyword. This keyword should only be invoked after a well’s connection factors have been declared via the COMPDAT keyword in the SCHEDULE section.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well productivity index is being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"WELPI","description":"A real positive value that defines the productivity or injectivity of a well at the time the keyword is activated in the input deck. Subsequent use of the keyword for a given well will override all previously entered data, including the original productivity index calculated from the well’s COMPDAT connection data. Note that: Only the connections currently opened will have their connection factors re-scaled to honor the productivity and injectivity index. Connections not opened will remain unchanged. Additional, previously defined connections added to the well at a later time, will not be influenced by a previous WELPI keyword. It may therefore be necessary to add another WELPI keyword at the time the new connections are opened, if desired. However, re-defining connections via the COMPDAT keyword resets the calculated productivity and injectivity index for those re-defined connections in the well. Subsequent usage of the keyword for the same well may lead to unintended values; use the WPI series of variables in the SUMMARY section to output and verify that the values are consistent with the desired results.","units":{"field":"Liquid stb/d/psia Gas Mscf/d/psia","metric":"Liquid sm3/day/bars Gas sm3/day/bars","laboratory":"Liquid scc/hour/atm Gas scc/hour/atm"},"default":"1.0","value_type":"DOUBLE"}],"example":"--\n-- DEFINE WELL PRODUCTIVITY/INJECTIVITY INDEX\n--\n-- WELL PI\n-- NAME MULT\nWELPI\nOP01 1.250 /\nOP02 2.750 /\nOP03 1.100 /\n/\nIn the above example the oil wells are are defined as having a well productivity indices of 1.250, 2.750 and 1.100 for the OP01, OP02 and OP03 wells, respectively.\n| Note One should not modify the productivity and injectivity index of gas wells that use: Russell Goodrich326\n Russell, D.G., Goodrich, J.H., Perry, G.E and Bruskotter, J.F \"Methods of Predicting Gas Well Performance\", Transactions of the ASME, Journal of Petroleum Technology (1966) 99-108. pressure square inflow equation, as declared via 'R-G' or 'YES' for the INFLOW parameter on the WELSPECS keyword in the SCHEDULE section, or Russell, D.G., Goodrich, J.H., Perry, G.E and Bruskotter, J.F \"Methods of Predicting Gas Well Performance\", Transactions of the ASME, Journal of Petroleum Technology (1966) 99-108. the general dry gas pseudo pressure inflow equation, as declared via 'P-P' for the INFLOW parameter on the WELSPECS keyword in the SCHEDULE section, or the generalized gas pseudo pressure inflow equation, as declared via 'GPP' for the INFLOW parameter on the WELSPECS keyword in the SCHEDULE section, or those gas wells that use the non-Darcy D factor coefficient, as declared by the DFACT property on the COMPDAT and WDFAC keywords in the SCHEDULE section. |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":2,"size_kind":"list"},"WELPRI":{"name":"WELPRI","sections":["SCHEDULE"],"supported":false,"summary":"The WELPRI keyword is used to re-assign a priority number to a well for when the PRIORITY keyword has been used in the SCHEDULE section. The PRIORITY keyword activates the Well Priority option and defines the coefficients in the well priority equation; WELPRI keyword can be used to over write these calculated priority numbers","parameters":[{"index":1,"name":"WELL_NAME","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"PRI1","description":"","units":{},"default":"-1","value_type":"INT"},{"index":3,"name":"SCALING1","description":"","units":{},"default":"1","value_type":"DOUBLE"},{"index":4,"name":"PRI2","description":"","units":{},"default":"-1","value_type":"INT"},{"index":5,"name":"SCALING2","description":"","units":{},"default":"1","value_type":"DOUBLE"}],"example":"","expected_columns":5,"size_kind":"list"},"WELSEGS":{"name":"WELSEGS","sections":["SCHEDULE"],"supported":false,"summary":"The WELSEGS keyword defines a well to be a multi-segment well and defines the well’s segment structure. Note that the well must have previously been defined by the WELSPECS keyword in the SCHEDULE section and that the WELSEGS keyword should be repeated for each multi-segment well in the model.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which a multi-segment well is being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","record":1,"value_type":"STRING"},{"index":2,"name":"TOPDEP","description":"A real value that defines the depth of the nodal point of the top segment. This is used as the reference depth for reporting the bottom-hole pressure for the multi-segment well. If the keyword is entered multiple times for the same well, due to for example the well configuration changing through time, then it is only necessary to enter this data the first time the keyword is used for a well.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","record":1,"value_type":"DOUBLE","dimension":"Length"},{"index":3,"name":"TOPLEN","description":"A real positive value that defines the length of the tubing from the tubing reference point (for example Measured Depth Relative to Kelly Bushing, MDRKB) to the nodal point of the top segment. Tubing pressures between the nodal point of the top segment and the well head are not calculated by the multi-segment well option as these are taken into account by the VFP tables allocated to the well and entered via the VFPPROD and VFPINJ keywords in the SCHEDULE section. If TOPLEN is set to zero or defaulted then the tubing length is measured from the nodal point of the top segment.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"0","record":1,"value_type":"DOUBLE","dimension":"Length"},{"index":4,"name":"WBORVOL","description":"A real positive value that defines the effective wellbore volume for the top segment, that is from the tubing head or wellhead at the surface to the nodal point of the top segment. The default value of 1.0 x 10-5 results in minimal wellbore storage.","units":{"field":"ft3","metric":"m3","laboratory":"cm3"},"default":"1.0E-5","record":1,"value_type":"DOUBLE","dimension":"Length*Length*Length"},{"index":5,"name":"TUBOPT","description":"A defined character string that specifies the type of length and depth data entered for LENGTH and DEPTH on the second record and should be set to one of the following: INC: Incremental changes in values of length and depth for each segment. ABS: Absolute values of length and depth for each segment. As there is no default value for TUBOPT one of the above options must be explicitly defined.","units":{},"default":"None","record":1,"value_type":"STRING"},{"index":6,"name":"PRESOPT","description":"A defined character string that specifies the pressure drop calculation used for each well segment and should be set to one of the following: HFA: Sets the pressure calculation to include the hydrostatic, friction and acceleration terms. HF-: Sets the pressure calculation to include the hydrostatic and friction terms only. H--: Sets the pressure calculation to include the hydrostatic pressure drop term only. The default value for PRESOPT of HFA sets the pressure calculation to include the hydrostatic, friction and acceleration terms.","units":{},"default":"HFA","record":1,"value_type":"STRING"},{"index":7,"name":"FLOWOPT","description":"A defined character string that specifies the type of multi-phase calculation used for each well segment and should be set to one of the following: HO: Sets the multi-phase calculation to the homogeneous model, that is all phases flow at the same velocity. DF-: Sets the multi-phase calculation to the Drift Flux Slip model. OPM Flow only supports the default value of HO.","units":{},"default":"HO","record":1,"value_type":"STRING"},{"index":8,"name":"TOPX","description":"A real positive value equal to or greater than zero that defines the coordinate in the x-direction of the nodal point of the top segment that is used for display purposes only. Currently this option is not supported by OPM Flow.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","record":1,"value_type":"DOUBLE","dimension":"Length"},{"index":9,"name":"TOPY","description":"A real positive value equal to or greater than zero that defines the coordinate in the y-direction of the nodal point of the top segment that is used for display purposes only. Currently this option is not supported by OPM Flow.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","record":1,"value_type":"DOUBLE","dimension":"Length"},{"index":10,"name":"XAREATH","description":"A real positive value equal to or greater than zero that defines the cross-sectional area of the pipe wall used in thermal conductivity calculations for when the temperature calculation is activated by the TEMP keyword in the RUNSPEC section. Currently this option is not supported by OPM Flow.","units":{"field":"ft2","metric":"m2","laboratory":"cm2"},"default":"None","record":1},{"index":11,"name":"VHEATCAP","description":"A real positive value equal to or greater than zero that defines the volumetric heat capacity of the pipe wall used in thermal conductivity calculations for when the temperature calculation is activated by the TEMP keyword in the RUNSPEC section. Currently this option is not supported by OPM Flow.","units":{"field":"Btu/ft/day/°R","metric":"kJ/m/day/K","laboratory":"J/cm/hr/K"},"default":"None","record":1},{"index":12,"name":"THCON","description":"A real positive value equal to or greater than zero that defines the thermal conductivity of the pipe wall used in thermal conductivity calculations for when the temperature calculation is activated by the TEMP keyword in the RUNSPEC section. Currently this option is not supported by OPM Flow.","units":{"field":"Btu/ft/day/°R","metric":"kJ/m/day/K","laboratory":"J/cm/hr/K"},"default":"None","record":1},{"index":1,"name":"ISEG1","description":"A positive integer greater than or equal to two and less than or equal to MXSEGS on WSEGDIMS keyword in the RUNSPEC section that defines the start of the segment range.","units":{},"default":"None","record":2,"value_type":"INT"},{"index":2,"name":"ISEG2","description":"A positive integer greater than or equal to ISEG1 on this record and less than or equal to MXSEGS on the WSEGDIMS keyword in the RUNSPEC section that defines the end of the segment range.","units":{},"default":"None","record":2,"value_type":"INT"},{"index":3,"name":"IBRANCH","description":"A positive integer greater than or equal to one and less than or equal to MXBRAN on WSEGDIMS keyword in the RUNSPEC section that defines the branch number of a segment. All segments on the main stem must have IBRANCH set to one, and those on lateral branches should have IBRANCH set to between two and MXBRAN.","units":{},"default":"None","record":2,"value_type":"INT"},{"index":4,"name":"ISEG3","description":"A positive integer greater than or equal to one and less than or equal to MXSEGS on the WSEGDIMS keyword in the RUNSPEC section that defines the outlet segment for the segment at the start of the segment range (ISEG1).","units":{},"default":"None","record":2,"value_type":"INT"},{"index":5,"name":"LENGTH","description":"A real positive value that: If TUBOPT is set to INC then LENGTH is the incremental length of the tubing for each segment in the segment range. If TUBOPT is set to ABS then LENGTH is the length of the tubing from the tubing reference point to the last segment in the range. The length between the nodal point of the last segment and the outlet segment is divided equally between each of the segments in the segment range.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","record":2,"value_type":"DOUBLE","dimension":"Length"},{"index":6,"name":"DEPTH","description":"A real positive value that: If TUBOPT is set to INC then DEPTH is the incremental depth change of the tubing for each segment in the segment range. If TUBOPT is set to ABS then DEPTH defines the depth of the tubing at the nodal point of the last segment in the segment range. The depths for other segments in the segment range are obtained by linear interpolation.","units":{},"default":"","record":2,"value_type":"DOUBLE","dimension":"Length"},{"index":7,"name":"ID","description":"A real positive value that defines the tubing internal diameter of each segment in the segment range.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","record":2,"value_type":"DOUBLE","dimension":"Length"},{"index":8,"name":"EPSILON","description":"A real positive value that defines the tubing absolute roughness of each segment in the segment range.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","record":2,"value_type":"DOUBLE","dimension":"Length"},{"index":9,"name":"XAREA","description":"A real positive value equal to or greater than zero that defines the cross-sectional area for fluid flow. Currently this option is not supported by OPM Flow.","units":{"field":"ft2","metric":"m2","laboratory":"cm2"},"default":"None","record":2,"value_type":"DOUBLE","dimension":"Length*Length"},{"index":10,"name":"VOLSEG","description":"VOLSEG is a real positive value that defines the effective segment volume for the this segment. Currently this option is not supported by OPM Flow.","units":{"field":"ft3","metric":"m3","laboratory":"cm3"},"default":"None","record":2,"value_type":"DOUBLE","dimension":"Length*Length*Length"},{"index":11,"name":"XCORDS","description":"A real positive value that: If TUBOPT is set to INC then XCORDS is the incremental change in the x-coordinate of the tubing for each segment in the segment range. If TUBOPT is set to ABS then XCORDS defines the x-coordinate of the tubing at the nodal point of the last segment in the segment range. The x-coordinates for other segments in the segment range are obtained by linear interpolation. Currently this option is not supported by OPM Flow.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","record":2,"value_type":"DOUBLE","dimension":"Length"},{"index":12,"name":"YCORDS","description":"A real positive value that: If TUBOPT is set to INC then YCORDS is the incremental change in the y-coordinate of the tubing for each segment in the segment range. If TUBOPT is set to ABS then YCORDS defines the y-coordinate of the tubing at the nodal point of the last segment in the segment range. The y-coordinates for other segments in the segment range are obtained by linear interpolation. Currently this option is not supported by OPM Flow.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","record":2,"value_type":"DOUBLE","dimension":"Length"},{"index":13,"name":"XAREAS","description":"A real positive value equal to or greater than zero that defines the cross-sectional area of the pipe wall for this segment, that is used in thermal conductivity calculations for when the temperature calculation is activated by the TEMP keyword in the RUNSPEC section. Currently this option is not supported by OPM Flow.","units":{"field":"ft2","metric":"m2","laboratory":"cm2"},"default":"None","record":2},{"index":14,"name":"VHEATSEG","description":"A real positive value equal to or greater than zero that defines the volumetric heat capacity of the pipe wall for this segment, that is used in thermal conductivity calculations for when the temperature calculation is activated by the TEMP keyword in the RUNSPEC section. Currently this option is not supported by OPM Flow.","units":{"field":"Btu/ft/day/°R","metric":"kJ/m/day/K","laboratory":"J/cm/hr/K"},"default":"None","record":2},{"index":15,"name":"THCSEG","description":"A real positive value equal to or greater than zero that defines the thermal conductivity of the pipe wall for this segment, that is used in thermal conductivity calculations for when the temperature calculation is activated by the TEMP keyword in the RUNSPEC section. Currently this option is not supported by OPM Flow.","units":{"field":"Btu/ft/day/°R","metric":"kJ/m/day/K","laboratory":"J/cm/hr/K"},"default":"None","record":2}],"example":"The following example defines one multi-segment oil production well (OP01) using the WELSPECS, WELSEGS, COMPDAT and COMPSEGS keywords, and one standard water injection well (WI01) using the WELSPECS and COMPDAT keywords.\n--\n-- WELL SPECIFICATION DATA\n--\n-- WELL GROUP LOCATION BHP PHASE DRAIN INFLOW OPEN CROSS PVT\n-- NAME NAME I J DEPTH FLUID AREA EQUANS SHUT FLOW TABLE\nWELSPECS\nOP01 PLATFORM 10 10 1* OIL /\nWI01 PLATFORM 1 1 1* WATER /\n/\n--\n-- WELL CONNECTION DATA\n--\n-- WELL --- LOCATION --- OPEN SAT CONN WELL KH SKIN D DIR\n-- NAME II JJ K1 K2 SHUT TAB FACT DIA FACT FACT FACT PEN\nCOMPDAT\nOP01 10 10 1 1 OPEN 1* 200. 0.5 /\nOP01 10 10 2 2 OPEN 1* 200. 0.5 /\nOP01 10 10 3 3 OPEN 1* 200. 0.4 /\nOP01 10 10 4 4 OPEN 1* 200. 0.4 /\nOP01 10 10 5 5 OPEN 1* 200. 0.4 /\nOP01 10 10 6 6 OPEN 1* 200. 0.4 /\nOP01 9 10 2 2 OPEN 1* 200. 0.4 /\nOP01 8 10 2 2 OPEN 1* 200. 0.4 /\nOP01 7 10 2 2 OPEN 1* 200. 0.4 /\nOP01 6 10 2 2 OPEN 1* 200. 0.4 /\nOP01 5 10 2 2 OPEN 1* 200. 0.4 /\nOP01 10 9 3 3 OPEN 1* 200. 0.4 /\nOP01 10 8 3 3 OPEN 1* 200. 0.4 /\nOP01 10 7 3 3 OPEN 1* 200. 0.4 /\nOP01 10 6 3 3 OPEN 1* 200. 0.4 /\nOP01 10 5 3 3 OPEN 1* 200. 0.4 /\nOP01 9 10 5 5 OPEN 1* 200. 0.4 /\nOP01 8 10 5 5 OPEN 1* 200. 0.4 /\nOP01 7 10 5 5 OPEN 1* 200. 0.4 /\nOP01 6 10 5 5 OPEN 1* 200. 0.4 /\nOP01 5 10 5 5 OPEN 1* 200. 0.4 /\nOP01 10 9 6 6 OPEN 1* 200. 0.4 /\nOP01 10 8 6 6 OPEN 1* 200. 0.4 /\nOP01 10 7 6 6 OPEN 1* 200. 0.4 /\nOP01 10 6 6 6 OPEN 1* 200. 0.4 /\nOP01 10 5 6 6 OPEN 1* 200. 0.4 /\nWI01 1 1 7 9 OPEN 1* 200. 0.5 /\n/\n--\n-- WELL SEGMENT SPECIFICATION DATA\n--\n-- WELL NODAL LEN WELL DEPH PRESS FLOW\n-- NAME DEPTH TUBING VOLM OPTN CALC MODEL\nWELSEGS\nOP01 2512.5 2512.5 1.0E-5 ABS HFA HO /\n--\n-- SEG SEG BRAN SEG TUBING NODAL TUBE TUBE XSEC VOL\n-- ISTR IEND NO NO LENGTH DEPTH ID ROUGH AREA SEG\n2 2 1 1 2537.5 2534.5 0.3 0.00010 /\n3 3 1 2 2562.5 2560.5 0.3 0.00010 /\n4 4 1 3 2587.5 2593.5 0.3 0.00010 /\n5 5 1 4 2612.5 2614.5 0.3 0.00010 /\n6 6 1 5 2637.5 2635.5 0.3 0.00010 /\n7 7 2 2 2737.5 2538.5 0.2 0.00010 /\n8 8 2 7 2937.5 2537.5 0.2 0.00010 /\n9 9 2 8 3137.5 2539.5 0.2 0.00010 /\n10 10 2 9 3337.5 2535.5 0.2 0.00010 /\n11 11 2 10 3537.5 2536.5 0.2 0.00010 /\n12 12 3 3 2762.5 2563.5 0.2 0.00010 /\n13 13 3 12 2962.5 2562.5 0.1 0.00010 /\n14 14 3 13 3162.5 2562.5 0.1 0.00010 /\n15 15 3 14 3362.5 2564.5 0.1 0.00010 /\n16 16 3 15 3562.5 2562.5 0.1 0.00010 /\n17 17 4 5 2812.5 2613.5 0.2 0.00010 /\n18 18 4 17 3012.5 2612.5 0.1 0.00010 /\n19 19 4 18 3212.5 2612.5 0.1 0.00010 /\n20 20 4 19 3412.5 2612.5 0.1 0.00010 /\n21 21 4 20 3612.5 2613.5 0.1 0.00010 /\n22 22 5 6 2837.5 2634.5 0.2 0.00010 /\n23 23 5 22 3037.5 2637.5 0.2 0.00010 /\n24 24 5 23 3237.5 2638.5 0.2 0.00010 /\n25 25 5 24 3437.5 2639.5 0.1 0.00010 /\n26 26 5 25 3637.5 2639.5 0.1 0.00010 /\n/\n--\n-- COMPLETION SEGMENT SPECIFICATION DATA\n--\n-- WELL\n-- NAME\nCOMPSEGS\nOP01 /\n--\n-- --LOCATION-- BRAN START END DIR LOC MID COMP ISEG\n-- II JJ K1 NO LENGTH LENGTHPEN I,J,K PERFS LENGTH NO.\n10 10 1 1 2512.5 2525.0 /\n10 10 2 1 2525.0 2550.0 /\n10 10 3 1 2550.0 2575.0 /\n10 10 4 1 2575.0 2600.0 /\n10 10 5 1 2600.0 2625.0 /\n10 10 6 1 2625.0 2650.0 /\n9 10 2 2 2637.5 2837.5 /\n8 10 2 2 2837.5 3037.5 /\n7 10 2 2 3037.5 3237.5 /\n6 10 2 2 3237.5 3437.5 /\n5 10 2 2 3437.5 3637.5 /\n10 9 3 3 2662.5 2862.5 /\n10 8 3 3 2862.5 3062.5 /\n10 7 3 3 3062.5 3262.5 /\n10 6 3 3 3262.5 3462.5 /\n10 5 3 3 3462.5 3662.5 /\n9 10 5 4 2712.5 2912.5 /\n8 10 5 4 2912.5 3112.5 /\n7 10 5 4 3112.5 3312.5 /\n6 10 5 4 3312.5 3512.5 /\n5 10 5 4 3512.5 3712.5 /\n10 9 6 5 2737.5 2937.5 /\n10 8 6 5 2937.5 3137.5 /\n10 7 6 5 3137.5 3337.5 /\n10 6 6 5 3337.5 3537.5 /\n10 5 6 5 3537.5 3737.5 /\n/\nNote the use of both the COMPDAT and COMPSEGS keywords to fully define a multi-segment well’s completion.\nFinally, Figure 12.15depicts the resulting well configuration for both wells, with the conventional water injection well shown in blue and the multi-segment oil producer shown in green.\n[formula]\n[formula]Figure 12.15: Multi-Segment Well OP01 Completion 3D View","records_meta":[{"expected_columns":9},{"expected_columns":12}],"size_kind":"list"},"WELSOMIN":{"name":"WELSOMIN","sections":["SCHEDULE"],"supported":false,"summary":"WELSOMIN defines a minimum oil saturation for a well connection above which the connection will be opened automatically. If the grid block connection is below WELSOMIN then connection will not be automatically opened. Automatic opening of connection is controlled by the STATUS parameter on the COMPDAT keyword in the SCHEDULE section. Note that if the COMPLUMP keyword in the SCHEDULE section has been used to lump connections into completions then WELSOMIN is compared to the average oil saturation of the completion.","parameters":[{"index":1,"name":"SOMIN","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"WELSPECL":{"name":"WELSPECL","sections":["SCHEDULE"],"supported":false,"summary":"The WELSPECL keyword defines the general well specification data for all well types and must be used for all wells contained within a Local Grid Refinement (“LGR”) instead of the WELSPECS keyword. WELSPECL must declare wells first before any other LGR well specification keywords are used in the input file. The keyword declares the name of well, the group the well belongs to, the LGR the well is incorporated into, the wellhead location and other key parameters.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well specification data is being defined.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"GRPNAME","description":"A character string of up to eight characters in length that defines the group name for which the well is assigned to. The group named FIELD is the top most group and thus GRPNAME cannot be set to FIELD, although this is allowed in the commercial compositional simulator but not the commercial black-oil simulator. Note that the group hierarchy should be defined by the GRUPTREE keyword when there is more than one level of groups, otherwise all the groups will sit directly under the FIELD group in the group tree hierarchy. Secondly, groups defined by the GRUPTREE keyword cannot contain other groups and wells; that is, groups must either contain other groups or wells but not both. If necessary, wells can be re-allocated to a different group by re-entering a well's WELSPECS data together with a new value for GRPNAME.","units":{},"default":"None","value_type":"STRING"},{"index":3,"name":"LGRNAME","description":"A character string of up to eight characters in length that defines the name of the local grid refinement for which the well is assigned to.","units":{},"default":"None","value_type":"STRING"},{"index":4,"name":"I","description":"A positive integer greater than or equal to zero and less than or equal to NX on the CARFIN keyword for Cartesian grids, that defines the wellhead location for a vertical or deviated well, or the heel for a horizontal well in the I-direction within the LGR. For radial LGRs this parameter should be set to one.","units":{},"default":"None","value_type":"INT"},{"index":5,"name":"J","description":"A positive integer greater than or equal to zero and less than or equal to NY on the CARFIN keyword for Cartesian grids, that defines the wellhead location for a vertical or deviated well, or the heel for a horizontal well in the J-direction within the LGR. For radial LGRs this parameter should be set to one.","units":{},"default":"None","value_type":"INT"},{"index":6,"name":"BHPREF","description":"A real value that defines the reference depth for reporting the bottom-hole pressure for the well. Ideally this value should be set to the midpoint of the perforations as defined by the COMPDATL keyword in the SCHEDULE section. If defaulted by 1* or set to a value less than or equal to zero, then the mid-point of shallowest connection defined by the COMPDATL keyword will be used.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"Mid-point of shallowest connection defined by the COMPDATL keyword","value_type":"DOUBLE","dimension":"Length"},{"index":7,"name":"TYPE","description":"A defined character that defines the “main” phase for the well, and should be set to one of the following character strings: GAS: for a gas well. OIL: for an oil well. WAT: for a water injection well. LIQ: for an oil well when the liquid productivity index is required for the well. This parameter defines the phase used to calculate a well’s productivity or injectivity index and the type of well, or a well’s connection, to close when a group’s production constraints, as defined on the GCONPROD keyword in the SCHEDULE section, have been violated. For example, if the well is declared as an oil well, then excessive gas and water connections will be subject to closure.","units":{},"default":"None","value_type":"STRING","options":["GAS","OIL","WAT","LIQ"]},{"index":8,"name":"DRADIUS","description":"A real value that defines the well drainage radius for the well used to calculate a well’s productivity or injectivity index. A default of zero results in the pressure equivalent radius of the grid blocks containing the well connections are used.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"0.0","value_type":"DOUBLE","dimension":"Length"},{"index":9,"name":"INFLOW","description":"A defined character string that defines the inflow equation to be used for the well in calculating the well’s flow rates. INFLOW should be set to one of the following character strings: STD: the standard inflow equation will be used. This is normally used for wells that are primary oil or water wells. NO: an alias for STD. R-G: the Russell Goodrich1\n Russell, D.G., Goodrich, J.H., Perry, G.E and Bruskotter, J.F \"Methods of Predicting Gas Well Performance\", Transactions of the ASME, Journal of Petroleum Technology (1966) 99-108. pressure square inflow equation will used. This option can be used for dry gas wells. Russell, D.G., Goodrich, J.H., Perry, G.E and Bruskotter, J.F \"Methods of Predicting Gas Well Performance\", Transactions of the ASME, Journal of Petroleum Technology (1966) 99-108. YES: an alias for R-G. P-P: the general dry gas pseudo pressure inflow equation will be used. Normally used for dry gas wells. GPP: the generalized gas pseudo pressure inflow equation used with wet gas wells, that is condensate gas wells. This inflow equation is based on the formulation of Whitson et al.2\n Whitson, C. H. and Fevang, Ø. “Generalised Pseudopressure Well Treatment in Reservoir Simulation,” Presented at the IBC Technical Services Conference on Optimisation of Gas Condensate Fields, Aberdeen, UK (June 26-27, 1997). Whitson, C. H. and Fevang, Ø. “Generalised Pseudopressure Well Treatment in Reservoir Simulation,” Presented at the IBC Technical Services Conference on Optimisation of Gas Condensate Fields, Aberdeen, UK (June 26-27, 1997). For oil and water wells the INFLOW should be set to STD, why for dry gas wells INFLOW can be set to either R-G or P-P; however, the P-P option is preferred for dry gas wells due to the more rigorous treatment of gas flow. For wet gas wells, that is gas condensate wells, INFLOW should be set to GPP. Only INFLOW equal to STD and NO are currently implemented in OPM Flow.","units":{},"default":"STD","value_type":"STRING","options":["STD","NO","YES","GPP"]},{"index":10,"name":"AUTO","description":"A defined character string that defines the automatic action to be taken if the economic WCUT, GOR, or WGR limits are violated and the well is to cease production. AUTO should be set to one of the following character strings: STOP: the well is “stopped” at the surface and will not produce any fluids to surface; however, if there any open connections then flow may occur within the wellbore and between the open connections depending on a connection’s potential with respect to all the other connections. Inter-connection flow (cross flow) can be prevented by setting the XFLOW variable to NO. In this case the well’s behavior will be similar to the SHUT option described below. SHUT: the well is shut at the surface and downhole, this results in no flow at the surface and no cross flow downhole. The corrective action takes places at the end of the time step in which the constraint is violated.","units":{},"default":"SHUT","value_type":"STRING","options":["STOP","SHUT"]},{"index":11,"name":"XFLOW","description":"A defined character string that defines the if cross flow should occur within the wellbore, and should be set to either: YES: to allow cross flow in the wellbore through well connections. NO: to disallow cross flow within the wellbore, even if the flow potentials in the well connections would allow such flow to occur. In some cases numerical issues can occur if this variable is set to YES, and resetting it to NO may resolve the issue; however the results may not represent the physical process in this case.","units":{},"default":"YES","value_type":"STRING","options":["YES","NO"]},{"index":12,"name":"PVTNUM","description":"A positive integer greater than or equal to zero that defines the PVT table used to calculate the wellbore fluid properties that define the relationship between reservoir and surface volume rates. The default value of zero sets PVTNUM to be the PVT table of the deepest connection in the well.","units":{},"default":"0","value_type":"INT"},{"index":13,"name":"DENOPT","description":"A defined character string that sets the type of density calculation used in calculating the wellbore hydrostatic head, and should be set to one of the following character strings: SEG: sets the hydrostatic head density calculation to segmented. In this cases the density is calculated between neighboring well connections and the volumes flowing from the connections. This is the more accurate calculation if the fluid properties flowing from the well connections are variable. The density calculation itself is explicit, i.e. uses the flowing volumes of the last time step. AVG: sets the hydrostatic head density calculation to the average density calculation. Here the density is considered uniform across a given reservoir and is dependent on total inflow rates of each phase and the well’s bottom-hole pressure The default option of 1* invokes the SEG option and is the only option implemented in OPM Flow.","units":{},"default":"SEG","value_type":"STRING","options":["SEG","AVG"]},{"index":14,"name":"FIPNUM","description":"An integer value defines the FIPNUM region used to determine the reservoir conditions in calculating the well’s reservoir volumes. If set to a negative integer value then the FIPNUM region of the deepest connection in the well will be used. If set to zero, the default value, then the average properties for the field will be used. If set to an integer value greater than zero, then the FIPNUM indicated by this value will be used.","units":{},"default":"0","value_type":"INT"},{"index":15,"name":"","description":"Not used.","units":{},"default":"","value_type":"STRING"},{"index":16,"name":"","description":"Not used.","units":{},"default":"","value_type":"STRING"},{"index":17,"name":"","description":"Not used.","units":{},"default":"","value_type":"STRING"},{"index":18,"name":"","description":"Not used.","units":{},"default":"","value_type":"INT"}],"example":"The following example defines three wells using the WELSPECL keyword\n--\n-- WELL SPECIFICATION DATA FOR LGR WELLS\n--\n-- WELL GROUP LGR LOCATION BHP PHASE DRAIN INFLOW SHUT CROSS PVT\n-- NAME NAME NAME I J DEPTH FLUID AREA EQUA. IN FLOW TABLE\nWELSPECL\nGI01 PLATFORM LGR01 14 13 1* GAS 1* P-P SHUT NO 1* /\nGP01 PLATFORM LGR01 64 80 1* GAS 1* GPP SHUT NO 1* /\nOP01 PLATFORM LGR02 24 10 1* OIL 1* STD SHUT NO 1* /\n/\nHere, well GI01 and GP01 are in the same LGR named LGR01 and OP01 is in a separate LGR named LGR02. GI01 is a dry gas injection well that uses the dry gas pseudo inflow equation, GP01 is a gas condensate well that uses the generalized gas pseudo pressure inflow equation, and finally, OP01 is an oil well that uses the standard inflow equation. All wells: will be shut if they are required to cease production, all wells disallow cross flow, and the hydrostatic head calculation is defaulted to the segment option for all wells.","expected_columns":18,"size_kind":"list"},"WELSPECS":{"name":"WELSPECS","sections":["SCHEDULE"],"supported":false,"summary":"The WELSPECS keyword defines the general well specification data for all well types, and must be used for all wells before any other well specification keywords are used in the input file. The keyword declares the well, the name of the well, the group the well initial belongs to, the wellhead location and other key parameters.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well specification data are being defined.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"GRPNAME","description":"A character string of up to eight characters in length that defines the group name for which the well is assigned to. The group named FIELD is the top most group. GRPNAME can be set to FIELD although this is discouraged and a warning message will be issued. This is allowed in the commercial compositional simulator but not the commercial black-oil simulator. The FIELD group cannot contain both groups and wells. Note that the group hierarchy should be defined by the GRUPTREE keyword when there is more than one level of groups, otherwise all the groups will sit directly under the FIELD group in the group tree hierarchy. Secondly, groups defined by the GRUPTREE keyword cannot contain other groups and wells; that is, groups must either contain other groups or wells but not both. If necessary, wells can be re-allocated to a different group by re-entering a well's WELSPECS data together with a new value for GRPNAME.","units":{},"default":"None","value_type":"STRING"},{"index":3,"name":"I","description":"A positive integer greater than or equal to zero and less than or equal to NX that defines the wellhead location for a vertical or deviated well, or the heel for a horizontal well in the I-direction. For wells being specified with the COMPTRAJ and WELTRAJ keywords in SCHEDULE section, that allow for an alternative manner to define the well connections to the simulation grid blocks, this parameter should be defaulted with 1*. Since the simulator will calculate the wellhead location from the trajectory data on the WELTRAJ keyword. Note that the COMPTRAJ and WELTRAJ keywords are OPM Flow specific keywords, and will cause an error in the commercial simulator.","units":{},"default":"None","value_type":"INT"},{"index":4,"name":"J","description":"A positive integer greater than or equal to zero and less than or equal to NY that defines the wellhead location for a vertical or deviated well, or the heel for a horizontal well in the J-direction. For wells being specified with the COMPTRAJ and WELTRAJ keywords in SCHEDULE section, that allows for an alternative manner to define the well connections to the simulation grid blocks, this parameter should be defaulted with 1*. Since the simulator will calculate the wellhead location from the trajectory data on the WELTRAJ keyword. Note that the COMPTRAJ and WELTRAJ keywords are OPM Flow specific keywords, and will cause an error in the commercial simulator.","units":{},"default":"None","value_type":"INT"},{"index":5,"name":"BHPREF","description":"A real value that defines the reference depth for reporting the bottom-hole pressure for the well. Ideally this value should be set to the midpoint of the perforations as defined by the COMPDAT keyword in the SCHEDULE section. If defaulted by 1* or set to a value less than or equal to zero, then the mid-point of shallowest connection defined by the COMPDAT keyword will be used.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"Mid-point of shallowest connection defined by the COMPDAT keyword","value_type":"DOUBLE","dimension":"Length"},{"index":6,"name":"TYPE","description":"A defined character string that defines the “main” phase for the well, and should be set to one of the following character strings: GAS: for a gas well. OIL: for an oil well. WAT: for a water injection well. LIQ: for an oil well when the liquid productivity index is required for the well. This parameter defines the phase used to calculate a well’s productivity or injectivity index and the type of well, or a well’s connection, to close when a group’s production constraints, as defined on the GCONPROD keyword in the SCHEDULE section, have been violated. For example, if the well is declared as an oil well, then excessive gas and water connections will be subject to closure. Note OPM Flow only currently supports options one to three, that is option four (LIQ) is not supported. For producing wells this mostly matters if one plots the WPI summary vector (productivity index for well's preferred phase). In the current treatment WPI will not have contributions from the water phase if the declared preferred phase is LIQ. For injecting wells WELSPECS's preferred phase does not matter, since the preferred phase is (typically) reset to the injected phase via the WCONINJE and WCONINJH keywords.","units":{},"default":"None","value_type":"STRING","options":["GAS","OIL","WAT","LIQ"]},{"index":7,"name":"DRADIUS","description":"A real value that defines the well drainage radius for the well used to calculate a well’s productivity or injectivity index. A default of zero results in the pressure equivalent radius of the grid blocks containing the well connections are used.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"0.0","value_type":"DOUBLE","dimension":"Length"},{"index":8,"name":"INFLOW","description":"A defined character string that defines the inflow equation to be used for the well in calculating the well’s flow rates. INFLOW should be set to one of the following character strings: STD: the standard inflow equation will be used. This is normally used for wells that are primary oil or water wells. NO: an alias for STD. R-G: the Russell Goodrich1\n Russell, D.G., Goodrich, J.H., Perry, G.E and Bruskotter, J.F \"Methods of Predicting Gas Well Performance\", Transactions of the ASME, Journal of Petroleum Technology (1966) 99-108. pressure square inflow equation will used. This option can be used for dry gas wells. Russell, D.G., Goodrich, J.H., Perry, G.E and Bruskotter, J.F \"Methods of Predicting Gas Well Performance\", Transactions of the ASME, Journal of Petroleum Technology (1966) 99-108. YES: an alias for R-G. P-P: the general dry gas pseudo pressure inflow equation will be used. Normally used for dry gas wells. GPP: the generalized gas pseudo pressure inflow equation used with wet gas wells, that is condensate gas wells. This inflow equation is based on the formulation of Whitson et al.2\n Whitson, C. H. and Fevang, Ø. “Generalised Pseudopressure Well Treatment in Reservoir Simulation,” Presented at the IBC Technical Services Conference on Optimisation of Gas Condensate Fields, Aberdeen, UK (June 26-27, 1997). Whitson, C. H. and Fevang, Ø. “Generalised Pseudopressure Well Treatment in Reservoir Simulation,” Presented at the IBC Technical Services Conference on Optimisation of Gas Condensate Fields, Aberdeen, UK (June 26-27, 1997). For oil and water wells the INFLOW should be set to STD, whereas for dry gas wells INFLOW can be set to either R-G or P-P; however, the P-P option is preferred for dry gas wells due to the more rigorous treatment of gas flow. For wet gas wells, that is gas condensate wells, INFLOW should be set to GPP. Only INFLOW equal to STD and NO are currently implemented in OPM Flow.","units":{},"default":"STD","value_type":"STRING","options":["STD","NO","YES","GPP"]},{"index":9,"name":"AUTO","description":"A defined character string that specifies the action to be taken if the well is automatically closed/shut by the simulator, and should be set to one of the following: STOP: the well is “stopped” at the surface and will not produce any fluids to surface; however, if there any open connections then flow may occur within the wellbore and between the open connections depending on a connection’s potential with respect to all the other connections. Inter-connection flow (cross flow) can be prevented by setting the XFLOW variable to NO. In this case the well’s behavior will be similar to the SHUT option described below. SHUT: the well is shut at the surface and downhole, this results in no flow at the surface and no cross flow downhole. The corrective action takes places at the end of the time step in which the constraint is violated.","units":{},"default":"SHUT","value_type":"STRING","options":["STOP","SHUT"]},{"index":10,"name":"XFLOW","description":"A defined character string that defines the if cross flow should occur within the wellbore, and should be set to either: YES: to allow cross flow in the wellbore through well connections. NO: to disallow cross flow within the wellbore, even if the flow potentials in the well connections would allow such flow to occur. In some cases numerical issues can occur if this variable is set to YES, and resetting it to NO may resolve the issue; however, the results may not represent the physical down hole process in this case.","units":{},"default":"YES","value_type":"STRING","options":["YES","NO"]},{"index":11,"name":"PVTNUM","description":"A positive integer greater than or equal to zero that defines the PVT table used to calculate the wellbore fluid properties that define the relationship between reservoir and surface volume rates. The default value of zero sets PVTNUM to be the PVT table of the deepest connection in the well.","units":{},"default":"0","value_type":"INT"},{"index":12,"name":"DENOPT","description":"A defined character string that sets the type of density calculation used in calculating the wellbore hydrostatic head, and should be set to one of the following character strings: SEG: sets the hydrostatic head density calculation to segmented. In this cases the density is calculated between neighboring well connections and the volumes flowing from the connections. This is the more accurate calculation if the fluid properties flowing from the well connections are variable. The density calculation itself is explicit, i.e. uses the flowing volumes of the last time step. AVG: sets the hydrostatic head density calculation to the average density calculation. Here the density is considered uniform across a given reservoir and is dependent on total inflow rates of each phase and the well’s bottom-hole pressure The default option of 1* invokes the SEG option and is the only option implemented in OPM Flow.","units":{},"default":"SEG","value_type":"STRING","options":["SEG","AVG"]},{"index":13,"name":"FIPNUM","description":"An integer value defines the FIPNUM region used to determine the reservoir conditions in calculating the well’s reservoir volumes and is determined by: If set to a negative integer value then the FIPNUM region of the deepest connection in the well will be used. If set to zero, the default value, then the average properties for the field will be used. If set to an integer value greater than zero, then the FIPNUM indicated by this value will be used.","units":{},"default":"0","value_type":"INT"},{"index":14,"name":"STRMLIN1","description":"Not used and should be defaulted with 1*.","units":{},"default":"1*","value_type":"STRING"},{"index":15,"name":"STRMLIN2","description":"Not used and should be defaulted with 1*.","units":{},"default":"1*","value_type":"STRING"},{"index":16,"name":"TYPECOMP","description":"Commercial compositional simulator well type model option that is not used and should be defaulted with either STD or 1*.","units":{},"default":"STD","value_type":"STRING"},{"index":17,"name":"POLYTAB","description":"A positive integer greater than or equal to zero that defines the polymer mixing table, as defined by the PLMIXPAR and PLYMAX keywords, to be used in calculating the well’s well bore properties. The default value of zero means the table allocated via the PLMIXNUM array for the deepest connection in the well bore is utilized. Only the default value of zero is supported by OPM Flow.","units":{},"default":"0","value_type":"INT"}],"example":"The following example defines three wells using the WELSPECS keyword\n--\n-- WELL SPECIFICATION DATA\n--\n-- WELL GROUP LOCATION BHP PHASE DRAIN INFLOW OPEN CROSS PVT\n-- NAME NAME I J DEPTH FLUID AREA EQUANS SHUT FLOW TABLE\nWELSPECS\nGI01 PLATFORM 14 13 1* GAS 1* P-P SHUT NO 1* /\nGP01 PLATFORM 64 80 1* GAS 1* GPP SHUT NO 1* /\nOP01 PLATFORM 24 110 1* OIL 1* STD SHUT NO 1* /\n/\nHere, well GI01 is a dry gas injection well that uses the dry gas pseudo inflow equation, GP01 is a gas condensate well that uses the generalized gas pseudo pressure inflow equation, and finally, OP01 is an oil well that uses the standard inflow equation. All wells will be shut if they are required to cease production, all wells disallow cross flow, and the hydrostatic head calculation is defaulted to the segment option for all wells.\nIf the same three wells are using the COMPTRAJ and WELTRAJ keywords to specify the connections to the simulation grid, then the WELSPECS keyword should be;\n--\n-- WELL SPECIFICATION DATA\n--\n-- WELL GROUP LOCATION BHP PHASE DRAIN INFLOW OPEN CROSS PVT\n-- NAME NAME I J DEPTH FLUID AREA EQUANS SHUT FLOW TABLE\nWELSPECS\nGI01 PLATFORM 1* 1* 1* GAS 1* P-P SHUT NO 1* /\nGP01 PLATFORM 1* 1* 1* GAS 1* GPP SHUT NO 1* /\nOP01 PLATFORM 1* 1* 1* OIL 1* STD SHUT NO 1* /\n/\nNotice how the well location parameters have been defaulted with 1* in this case.\nThe following example illustrates how the WELSPECS keyword can be used to change the controlling group for oil production wells previously specified by the WELSPECS keyword that have an oil production rate less than 100.\n--\n-- ACTIONX BLOCK\n--\nACTIONX\nACT01 1 /\nWOPR 'OP*' < 100.0 /\n/\nWELSPECS\n'?' 'LOWPRESS' /\n/\nENDACTIO","expected_columns":17,"size_kind":"list"},"WELTARG":{"name":"WELTARG","sections":["SCHEDULE"],"supported":false,"summary":"The WELTARG keyword modifies the target and constraints values of both rates and pressures for previously defined wells without having to define all the variables on the well control keywords: WCONPROD, WCONHIST, WCONINJE, or WCONINJH. Variables not changed by the WELTARG keyword remain the same as those previously entered via the well control keywords or previously entered WELTARG keywords. Note that the well must still be initially fully defined using the WCONPROD or WCONINJE keywords. All the aforementioned keywords are described in the SCHEDULE section.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well production rates and pressures data are being redefined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS and WCONPROD (or WCONINJE) keywords in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"TARGET","description":"A defined character string that sets the item to be changed for the well the value of the item is set by item (3). ORAT: reset the surface oil production rate value as defined by item (3). WRAT: reset the surface water production rate value as defined by item (3). GRAT: reset the surface gas production rate value as defined by item (3). LRAT: reset the surface liquid (oil plus water) production rate value as defined by (3). CRAT: reset the linearly combined calculated rate value as defined by (3). This option is not supported. RESV: reset the in situ reservoir volume rate value as defined by (3). BHP: reset the bottom-hole pressure value as defined by item (3). THP: reset the tubing head pressure value for the well as defined by item (3). VFP: reset the vertical lift performance table number as defined by (3). LIFT: reset the artificial lift quantity for use with vertical lift performance tables. GUID: reset the guide rate value for wells operating under group control. The commercial compositional simulator options: WGRA, NGL, CVAL, REIN, STRA, SATP and SATT are not applicable. Note that TARGET only defines the variable to be changed, it does not change how a well is controlled. For example, if a well is operating on ORAT control, as defined by the previously entered WCONPROD keyword, entering TARGET equal to LRAT with a value, changes the liquid constraint but the well still remains on ORAT control. Use the WELCNTL keyword in the SCHEDULE section to change the control mode of a well.","units":{},"default":"None","value_type":"STRING","options":["ORAT","WRAT","GRAT","LRAT","CRAT","RESV","BHP","THP","VFP","LIFT","GUID"]},{"index":3,"name":"VALUE Liquid Gas Res Vol Pressure VFP LIFT","description":"A real positive value that defines the value of the variable declared by TARGET This value may be specified using a User Defined Argument (UDA).","units":{"field":"stb/d Mscf/d rb/d psia dimensionless same as VFPPROD or VFPINJ","metric":"sm3/day sm3/day rm3/day barsa dimensionless same as VFPPROD or VFPINJ","laboratory":"scc/hour scc/hour rcc/hour atma dimensionless same as VFPPROD or VFPINJ"},"default":"None","value_type":"UDA"}],"example":"The following example below shows the oil rates for the OP01 oil producer at the start of the schedule section (January 1, 2000).\n-- ------------------------------------------------------------------------------\n-- 01 JAN 2000 START OF SCHEDULE SECTION\n-- ------------------------------------------------------------------------------\n--\n-- WELL PRODUCTION WELL CONTROLS\n--\n-- WELL OPEN/ CNTL OIL WAT GAS LIQ RES BHP THP VFP VFP\n-- NAME SHUT MODE RATE RATE RATE RATE RATE PRES PRES TABLE ALFQ\nWCONPROD\nOP01 OPEN ORAT 3000 1* 1* 1* 1* 750.0 500. 9 1* /\n/ DATES\n01 FEB 2000 /\n/\n--\n-- WELL PRODUCTION AND INJECTION TARGETS\n--\n-- WELL WELL TARGET\n-- NAME TARG VALUE\nWELTARG\nOP01 ORAT 2000 /\n/\nFrom January 1, 2000 to February 1, 2000 well OP01 is open and is on oil rate control and has a target oil rate of 3,000 stb/d, and uses VFPPROD vertical lift table number 9 with a minimum tubing head pressure constraint of 500 psia. After February 1, 2000 the well’s oil rate is reduced to 2,000 stb/d and all the other parameters remain unchanged.","expected_columns":3,"size_kind":"list"},"WELTRAJ":{"name":"WELTRAJ","sections":["SCHEDULE"],"supported":true,"summary":"The WELTRAJ keyword defines a trajectory well together with the well trajectory data (simplified directional survey data), and is used in conjunction with the COMPTRAJ keyword in the SCHEDULE section to define the well connections to the simulation grid blocks. The keyword can only be used for trajectory wells that employ the COMPTRAJ keyword to define the connections to the grid, that is, one cannot use COMPDAT keyword in the SCHEDULE section for declaring the connections to the grid for these type of wells.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well trajectory data are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur. Secondly, the wellhead location parameters on the WELSPECS keyword, WELSPECS(I, J), should be defaulted with 1* for trajectory wells, as the well location will be calculated by the simulator.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"IBRANCH","description":"A positive integer greater than or equal to one and less than or equal to MXBRAN on WSEGDIMS keyword in the RUNSPEC section that defines the branch number of a segment. All segments on the main stem must have IBRANCH set to one and lateral branches should have values between two and MXSEGS on the WSEGDIMS keyword in the RUNSPEC section. Only the default value of one is currently supported, that is only the main branch of a multi-segment well is supported, or a single trajectory for a conventional well.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"1","value_type":"INT"},{"index":3,"name":"X","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":4,"name":"Y","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":5,"name":"TVD","description":"A real negative or positive value that defines the True Vertical Depth along the wellbore path at XCORD and YCORD. Normally, TVD is referenced to the subsea elevation, that is TVDSS.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":"Length"}],"example":"The following example defines two trajectory wells oil wells, OP01 and OP02, using the WELSPECS and WELTRAJ keywords, together with their perforations using the COMPTRAJ keyword.\n--\n-- WELL SPECIFICATION DATA\n--\n-- WELL GROUP LOCATION BHP PHASE DRAIN INFLOW OPEN CROSS PVT\n-- NAME NAME I J DEPTH FLUID AREA EQUANS SHUT FLOW TABLE\nWELSPECS\nOP01 PLATFORM 1* 1* 1* OIL 1* STD SHUT NO 1* /\nOP02 PLATFORM 1* 1* 1* OIL 1* STD SHUT NO 1* /\n/\n--\n-- WELL TRAJECTORY DATA\n--\n-- WELL BRAN XCORD YCORD TVDSS MD\n-- NAME NO DEPTH DEPTH\n-- ----- ---- ------------ ------------ ------------ ------------\nWELTRAJ\nOP01 1* 2.805445e+06 3.602948e+06 -100.000000 0.0 /\nOP01 1* 2.805445e+06 3.602948e+06 877.0000000 977.0 /\nOP01 1* 2.805445e+06 3.602948e+06 957.9950240 1058.0 /\nOP01 1* 2.805444e+06 3.602946e+06 1051.976081 1152.0 /\n…………………... /\nOP02 1* 2.810828e+06 3.604507e+06 9371.792711 11418.0 /\nOP02 1* 2.810885e+06 3.604525e+06 9443.657000 11511.0 /\nOP02 1* 2.810952e+06 3.604546e+06 9531.966162 11624.0 /\nOP02 1* 2.810973e+06 3.604553e+06 9560.411742 11660.0 /\n/\n--\n--\n-- WELL TRAJECTORY CONNECTION DATA\n--\n-- WELL BRAN -- PERFORATION -- COMPL OPEN SAT CONN WELL KH SKIN D\n-- NAME NO. TOP BOT REF NO. SHUT TAB FACT DIA FACT FACT FACT\nCOMPTRAJ\nOP01 1* 8230 8244 MD 1 SHUT 1* 1* 0.708 1* 0.0 1* /\nOP01 1* 8352 8380 MD 1 SHUT 1* 1* 0.708 1* 0.0 1* /\nOP01 1* 9070 9100 MD 1 SHUT 1* 1* 0.708 1* 0.0 1* /\nOP01 1* 9220 9250 MD 2 SHUT 1* 1* 0.708 1* 0.0 1* /\nOP01 1* 9266 9280 MD 2 SHUT 1* 1* 0.708 1* 0.0 1* /\nOP01 1* 9693 9703 MD 3 SHUT 1* 1* 0.708 1* 0.0 1* /\nOP01 1* 9940 9974 MD 3 SHUT 1* 1* 0.708 1* 0.0 1* /\nOP02 1* 9979 9985 TVD 1* SHUT 1* 1* 0.708 1* 0.0 1* /\nOP02 1* 10173 10183 TVD 1* SHUT 1* 1* 0.708 1* 0.0 1* /\nOP02 1* 10190 10204 TVD 1* SHUT 1* 1* 0.708 1* 0.0 1* /\nOP02 1* 10327 10333 TVD 1* SHUT 1* 1* 0.708 1* 0.0 1* /\nOP02 1* 10339 10345 TVD 1* SHUT 1* 1* 0.708 1* 0.0 1* /\nOP02 1* 11528 11538 TVD 1* SHUT 1* 1* 0.708 1* 0.0 1* /\nHere, well OP01 has eight perforation intervals, with the intervals one to three grouped into one completion, perforation intervals four to five grouped into completion number two, and finally the bottom three perforations are grouped into completion number three. In contrast, OP02 has six perforated intervals with their completion interval defaulted to one.\n| Note This is an OPM Flow specific keyword and will therefore cause an error in the commercial simulator. |\n|----------------------------------------------------------------------------------------------------------|","expected_columns":6,"size_kind":"list"},"WFOAM":{"name":"WFOAM","sections":["SCHEDULE"],"supported":null,"summary":"The WFOAM keyword defines an injection wells foam concentration. The foam option must be activated by the FOAM keyword in the RUNSPEC section in order to use this keyword. Note if a well’s foam concentration is not set with this keyword then default value of zero is assigned to a well.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well injection foam concentration is being defined.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"FOAMCON","description":"A real positive value that defines the well’s injection foam concentration. This value may be specified using a User Defined Argument (UDA). Units are dependent on the transport phase specified via the FOAMOPT1 variable on the FOAMOPTS keyword in the PROPS section. FOAMOPT1 should be set to either GAS or WATER. Currently OPM Flow only supports injecting foam via the GAS phase.","units":{"field":"Gas: lb/Mscf Water: lb/stb","metric":"Gas: kg/sm3 Water: kg/sm3","laboratory":"Gas: gm/scc Water: gm/scc"},"default":"None","value_type":"UDA","dimension":"FoamDensity"}],"example":"--\n-- WELL INJECTION FOAM CONCENTRATION\n--\n-- WELL FOAM\n-- NAME FOAMCON\nWFOAM\nGI01 0.020 /\nGI02 0.020 /\nGI03 0.020 /\n/\nHere three gas wells are given an injection foam concentration of 0.020 lb/Mscf, assuming field units.","expected_columns":2,"size_kind":"list"},"WFRICSEG":{"name":"WFRICSEG","sections":["SCHEDULE"],"supported":false,"summary":"WFRICSEG converts a previously defined friction well, as per the WFRICTN keyword in the SCHEDULE section, to a multi-segment well. The keyword thus acts as a replacement for the WELSEGS and COMPSEGS keywords for multi-segment wells. See also the WFRICSGL keyword in the SCHEDULE section that performs similar functionality for wells in Local Grid Refinements.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"TUBINGD","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":3,"name":"ROUGHNESS","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":4,"name":"FLOW_SCALING","description":"","units":{},"default":"1","value_type":"DOUBLE"}],"example":"","expected_columns":4,"size_kind":"list"},"WFRICSGL":{"name":"WFRICSGL","sections":["SCHEDULE"],"supported":false,"summary":"WFRICSGL converts a previously defined Local Grid Refinement (“LGR”) friction well, as per the WFRICTNL keyword in the SCHEDULE section, to a multi-segment LGR well. The keyword thus acts as a replacement for the WELSEGS and COMPSEGL keywords for LGR multi-segment wells. See also the WFRICSEG keyword in the SCHEDULE section that performs similar functionality for wells in the global grid.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"TUBINGD","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":3,"name":"ROUGHNESS","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":4,"name":"FLOW_SCALING","description":"","units":{},"default":"1","value_type":"DOUBLE"}],"example":"","expected_columns":4,"size_kind":"list"},"WFRICTN":{"name":"WFRICTN","sections":["SCHEDULE"],"supported":false,"summary":"The WFRICTN keyword is used to declare a previously defined well as a friction well and to set the characteristics for this type of well including: tubing size, pipe roughness, and the connections to the grid. Wellbore friction is important in horizontal and multi-lateral wells where the pressure loss along the pipe can effect a well’s performance. Note that unlike other SCHEDULE section well keywords, multiple wells cannot be entered with one WFRICTN keyword, that is, the keyword must be repeated for each well.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"TUBINGD","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":3,"name":"ROUGHNESS","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":4,"name":"FLOW_SCALING","description":"","units":{},"default":"1","value_type":"DOUBLE"}],"example":"","expected_columns":4,"size_kind":"list"},"WFRICTNL":{"name":"WFRICTNL","sections":["SCHEDULE"],"supported":false,"summary":"The WFRICTNL keyword is used to declare a previously defined Local Grid Refinement (“LGR”) well as a LGR friction well and to set the characteristics for this type of well including: tubing size, pipe roughness, and the connections to the grid. Wellbore friction is important in horizontal and multi-lateral wells where the pressure loss along the pipe can effect a well’s performance. Note that unlike other SCHEDULE section well keywords, multiple wells cannot be entered with one WFRICTNL keyword, that is, the keyword must be repeated for each well.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"TUBINGD","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":3,"name":"ROUGHNESS","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":4,"name":"FLOW_SCALING","description":"","units":{},"default":"1","value_type":"DOUBLE"}],"example":"","expected_columns":4,"size_kind":"list"},"WGASPROD":{"name":"WGASPROD","sections":["SCHEDULE"],"supported":false,"summary":"The WGASPROD keyword declares wells to be Sales Gas producers and sets the incremental gas rate for a well and the maximum number of increments that this rate can be increased. Wells must have been previously been defined via the WELSPECS and WCONPROD keywords in the SCHEDULE section and are subject to any targets or constraints on WCONPROD keyword.","parameters":[{"index":1,"name":"WELL_NAME","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"INCREMENTAL_GAS_PRODUCTION_RATE","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":3,"name":"MAX_INCREMENTS","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":3,"size_kind":"list"},"WGORPEN":{"name":"WGORPEN","sections":["SCHEDULE"],"supported":false,"summary":"The WGORPEN keyword defines a well’s Gas-Oil Ratio (“GOR”) penalty parameters used to calculate a well’s oil production target for the current month, as a function of the well’s previous month’s average GOR. The WGORPEN calculated oil rate overwrites any oil targets set by the WCONPROD and WELTARG keywords in the SCHEDULE section. In North American, it is common practice for the regulator to enforce GOR penalties, in order to control gas production in depletion drive oil reservoirs, with the stated intention to maximize oil recovery by limiting the energy loss from the reservoir by excessive gas production.","parameters":[{"index":1,"name":"WELL_NAME","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"BASE_GOR","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":3,"name":"MAX_OIL_RATE","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time"},{"index":4,"name":"AVG_GOR0","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","expected_columns":4,"size_kind":"list"},"WGRUPCON":{"name":"WGRUPCON","sections":["SCHEDULE"],"supported":false,"summary":"The WGRUPCON keyword defines a well’s production or injection guide rate for when a well is under group control. The guide rate is used to determine a well’s production target under group control in order to satisfy a group’s targets and constraints, including any higher level related groups as well as the FIELD group.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well production targets and constraints data are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"STATUS","description":"A defined character string that declares the status of the well to be under group control or not under group control. STATUS should be set to one of the following character strings: YES: the well is under group control and its production behavior will be influenced by its assigned group, including connecting higher level groups as well as the FIELD group. NO: the well is NOT under group control and its production behavior will only be influenced by its own targets and constraints. Note the default value of YES puts all wells under group control unless specified otherwise by the STATUS variable, or the TARGET variable on the WCONPROD and WCONINJE keywords in the SCHEDULE section.","units":{},"default":"YES","value_type":"STRING","options":["YES","NO"]},{"index":3,"name":"GUIDERAT","description":"A dimensionless real number that determines the well’s share of its group production (or injection) target rate. If GUIDERAT is a positive number then the guide rate for the well is fixed until modified by this keyword at a subsequent time. If TARGET variable on this keyword is not equal to the group’s controlling phase, then the GUIDERAT is converted into the groups’ controlling phase and is updated every time step. If GUIDERAT is less than or equal to zero then the well’s guide rate is based on the well’s potential (unrestricted flow) and the potential is calculated every time step.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"-1.0","value_type":"DOUBLE"},{"index":4,"name":"TARGET","description":"A defined character string that sets the well’s guide rate phase that the GUIDERAT value should be applied to. TARGET should be set to one of the following character strings: OIL: the well's guide rate applies to the surface oil production rate. WAT: the well's guide rate applies to the surface water production rate. GAS: the well's guide rate applies to the surface gas production rate. LIQ: the well's guide rate applies to the surface liquid (oil plus water) production rate. RES: the well's guide rate applies to the in situ reservoir volume rate. RAT: the well’s guide rate applies to the surface rate of the injection phase. This should only be used if the well has been declared an injection well via the WCONINJE keyword in the SCHEDULE section. COMB: the well’s guide rate applies to the linearly combined calculated rate. This option is not supported by OPM Flow. TARGET may be defaulted if GUIDERAT has been defaulted, either by 1* or a value less than or equal to zero.","units":{},"default":"None","value_type":"STRING","options":["OIL","WAT","GAS","LIQ","RES","RAT","COMB"]},{"index":5,"name":"SCALE","description":"A real value that is used to multiple the GUIDERAT or the calculated well potentials to determine the final GUIDERAT for the well.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0","value_type":"DOUBLE"}],"example":"The following example defines the guides rates for all oil and gas producers and the gas injectors as follows:\n--\n-- DEFINE WELL GUIDES FOR GROUP CONTROL\n--\n-- WELL GRUP GUIDE GUIDE SCALE\n-- NAME CNTL RATE PHASE FACT\nWGRUPCON\n'GI*' YES 0 RAT 1.0 /\n'GP*' YES 0 GAS 1.0 /\n'OP*' NO 2 OIL 1.0 /\n/\nBoth the gas producers (‘GP*’) and injectors (‘GI’*) are under group control with their guide rates based on their potentials. The gas injectors are controlled based on their potential surface gas injection rates and the gas producers on their potential surface gas production rates. In comparison, the oil wells (OP*) are controlled by their own targets and constraints.","expected_columns":5,"size_kind":"list"},"WHEDREFD":{"name":"WHEDREFD","sections":["SCHEDULE"],"supported":false,"summary":"The WHEDREFD keyword sets the hydraulic head reference depth for reporting the hydraulic head pressure for the well, for wells that have previously been defined by the WELSPECS keyword in the SCHEDULE section.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well hydraulic head reference depth data is being defined.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"HYDREF","description":"A real value that defines the hydraulic head reference depth for reporting the hydraulic head pressure for the well. HYDREF cannot be defaulted on the keyword; however if a well has not been set by this keyword HYDREF is set equal to the value on the HYDRHEAD keyword.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":"Length"}],"example":"The following example defines three wells hydraulic head reference depths for reporting, using the WHEDREFD keyword\n--\n-- WELL HYDRAULIC HEAD REFERENCE DEPTH\n--\n-- WELL HYDREF\n-- NAME DEPTH\nWHEDREFD\nOP01 150.0 /\nOP02 175.0 /\nOP03 150.0 /\n/\nHere, well OP01 and OP03 have their hydraulic head reference depths set to 150.0 ft and well OP02’s hydraulic head reference depth is set to 175.0 ft.","expected_columns":2,"size_kind":"list"},"WHISTCTL":{"name":"WHISTCTL","sections":["SCHEDULE"],"supported":true,"summary":"The WHISTCTL keyword changes the target control for wells declared as history match wells via the WCONHIST keyword in the SCHEDULE section. The target phase is set on the WCONHIST keyword and WHISTCTL overrides this value for all subsequent entries on the WCONHIST keyword.","parameters":[{"index":1,"name":"TARGET","description":"A defined character string that sets the observed target production phase for the well, all the other phases are calculated unconstrained and used for reporting only. The simulator will attempt to meet the TARGET based on the phase rate stated in items (4) to (6) and (10) on the WCONHIST keyword. TARGET should be set to one of the following character strings: ORAT: the target is set to the surface oil production rate as defined by item (4) on the WCONHIST keyword. WRAT: the target is set to the surface water production rate as defined by item (5) on the WCONHIST keyword. GRAT: the target is set to the surface gas production rate as defined by item (6) on the WCONHIST keyword. LRAT: the target is set to the surface liquid (oil plus water) production rate and is calculated by the simulator using (4) and (5) on the WCONHIST keyword. RESV: the target is set to the in situ reservoir volume rate and is calculated by the simulator using items (4), (5) and (6) on the WCONHIST keyword. BHP: the target rate is set to the bottom-hole pressure as defined by item (10) on the WCONHIST keyword. NONE: revert back to the TARGET control mode on the WCONHIST keyword. The TARGET control mode defined on this keyword resets the TARGET control mode on the WCONHIST keyword in the SCHEDULE section, from the time the WHISTCTL is invoked, thus avoiding changing the control model on all subsequent WCONHIST keywords.","units":{},"default":"None","value_type":"STRING","options":["ORAT","WRAT","GRAT","LRAT","RESV","BHP","NONE"]},{"index":2,"name":"END","description":"A defined character string that defines if the simulation should terminate if the well has switch to BHP control by the simulator, and should be set to one of the following character strings: NO: no action is taken and the run continues. YES: terminate the run at the next report time step. Wells set to BHP control via the WCONHIST or WHISCTL keywords are ignored. Only END equal to NO is currently supported in OPM Flow.","units":{},"default":"NO","value_type":"STRING","options":["NO","YES"]}],"example":"The example below shows the observed gas rates for the OP01 oil producer for the first quarter of 2000.\n-- ------------------------------------------------------------------------------\n-- 01 JAN 2000 START OF SCHEDULE SECTION\n-- ------------------------------------------------------------------------------\n--\n-- DEFINE WELL HISTORICAL TARGET PHASE\n--\n-- CNTL BHP\n-- MODE STOP\nWHISTCTL\nRESV NO /\n--\n-- WELL HISTORICAL PRODUCTION CONTROLS\n--\n-- WELL OPEN/ CNTL OIL WAT GAS VFP VFP THP BHP\n-- NAME SHUT MODE RATE RATE RATE TABLE ALFQ PRES PRES\nWCONHIST OP01 OPEN ORAT 15.5E3 100.0 1550 10 1* 900.0 1* /\n/ DATES\n01 FEB 2000 /\n/\n--\n-- WELL HISTORICAL PRODUCTION CONTROLS\n--\n-- WELL OPEN/ CNTL OIL WAT GAS VFP VFP THP BHP\n-- NAME SHUT MODE RATE RATE RATE TABLE ALFQ PRES PRES\nWCONHIST OP01 OPEN ORAT 15.2E3 150.0 1520 1* 1* 875.0 3250.0 /\n/ DATES\n01 MAR 2000 /\n/\n--\n-- WELL HISTORICAL PRODUCTION CONTROLS\n--\n-- WELL OPEN/ CNTL OIL WAT GAS VFP VFP THP BHP\n-- NAME SHUT MODE RATE RATE RATE TABLE ALFQ PRES PRES\nWCONHIST OP01 OPEN ORAT 15.0E3 200.0 1500 1* 1* 850.0 1* /\n/\nFrom January 1, 2000 the WCONHIST keyword defines well OP01, which is open and is on oil rate control, to produce 15,500 stb/d oil, with the observed rates of 100 stb/d of water and 15.5 MMscf/d of gas. However the WHISCTL keyword resets the target control to reservoir voidage from January 1, 2000 and onward. This is useful in initial history matching runs to get a “reasonable” pressure match, by ensuring that the total reservoir withdrawals are correct, although the individual phase withdrawals will not match. Once a reasonable pressure match is achieved for the reservoir then one can reset TARGET to the sales phase, OIL or GAS, and continue with the matching of all the phases.","expected_columns":2,"size_kind":"fixed","size_count":1},"WHTEMP":{"name":"WHTEMP","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, WHTEMP, sets the parameters for the Tubing Head Temperature calculation, which can either be a constant value, or from a table lookup using a VFPPROD table, via the VFPPROD keyword in the SCHEDULE section, containing tubing head temperature data.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well production targets and constraints data are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"VFPTAB","description":"A positive integer greater than or equal to zero that references the production vertical lift performance table (VFPPROD), containing the tubing head temperature data for the well. Note, a well must have both a VFPPROD pressure and a VFPPROD temperature table, if the tubing head temperatures are to be calculated. Alternatively, if a constant tubing head temperature for a production well is to be defined via the TEMP parameter, then VFPTAB should be defaulted with 1* instead.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"INT"},{"index":3,"name":"TEMP","description":"A real positive value greater than zero that defines a constant tubing head temperature for a production well. In this case the VFPTAB parameter should be defaulted with 1* if a constant tubing head temperature for a production well.","units":{"field":"oF","metric":"oC","laboratory":"oC"},"default":"None","value_type":"DOUBLE","dimension":"Temperature"}],"example":"The following example defines three wells tubing head temperature parameters using the WHTEMP keyword\n--\n-- DEFINE WELL TUBING HEAD TEMPERATURE PARAMETERS\n--\n-- WELL VFP TUB\n-- NAME TABLE TEMP\nWHTEMP\nOP01 5 /\nOP02 1* 150 /\nOP03 5 /\n/\nHere, well OP01 and OP03 used VFPPROD table number five to calculate the tubing head temperature, and well OP02’s uses a constant 150o tubing head temperature.","expected_columns":3,"size_kind":"list"},"WINJCLN":{"name":"WINJCLN","sections":["SCHEDULE"],"supported":null,"summary":"The WINJCLN keyword signals that a filter cake should be completely or partially cleaned – this effectively multiplies the accumulated filter cake skin.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the filter cake properties are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"FCLNFRAC","description":"A real positive value between 0 and 1 that defines the fraction of filter cake permeability (skin factor) to be removed. The accumulated filter cake skin factor for matching connections will be multiplied by (1 – FCLNFRAC), so the default value of 1 will completely clean the filter cake.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"I","description":"An integer that defines the matching connection location in the I-direction. If set to < 1 then all connections in the I-direction that also satisfy J and K criteria are selected.","units":{},"default":"-1","value_type":"INT"},{"index":4,"name":"J","description":"An integer that defines the matching connection location in the J-direction. If set to < 1 then all connections in the J-direction that also satisfy I and K criteria are selected.","units":{},"default":"-1","value_type":"INT"},{"index":5,"name":"K","description":"An integer that defines the matching connection location in the K-direction. If set to < 1 then all connections in the K-direction that also satisfy I and J criteria are selected.","units":{},"default":"-1","value_type":"INT"}],"example":"The following example signals the filter cake clean up for water injection wells using WINJCLN:\n--\n-- WELL FILTER CAKE CLEAN UP\n--\n-- WELL CLEAN --LOCATION--\n-- NAME FRAC II JJ KK\nWINJDAM\nINJ-A1 0.4 0 0 3 /\nINJ-A1 0.4 0 0 4 /\nINJ-B* 0.9 /\n/\nIn well INJ-A1 forty percent of the filter cake is cleaned up in well connections in layers 3 and 4 (filter cake skin is multiplied by 0.6). In wells matching INJ-B* ninety percent of the filter cake is cleaned up in all well connections (filter cake skin is multiplied by 0.1).","expected_columns":5,"size_kind":"list"},"WINJDAM":{"name":"WINJDAM","sections":["SCHEDULE"],"supported":null,"summary":"The WINJDAM keyword defines filter cake properties for wells that have previously been defined by the WELSPECS keyword in the SCHEDULE section. This keyword must be accompanied by the WINJFCNC keyword to define the injected filtrate concentration.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the filter cake properties are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"GEOMETRY","description":"A defined character string that the filter cake geometry of the well. GEOMETRY must be set to one of the following character strings: LINEAR: the filter cake model will assume a linear geometry. RADIAL: the filter cake model will assume a radial geometry.","units":{},"default":"None","value_type":"STRING","options":["LINEAR","RADIAL"]},{"index":3,"name":"FCPERM","description":"A real positive value that defines the filter cake permeability.","units":{"field":"mD","metric":"mD","laboratory":"mD"},"default":"None","value_type":"DOUBLE","dimension":"Permeability"},{"index":4,"name":"FCPORO","description":"A real positive value that defines the filter cake porosity.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.3","value_type":"DOUBLE","dimension":"1"},{"index":5,"name":"FCRADIUS","description":"Well radius to use in skin factor calculations. If FCRADIUS is defaulted then half the diameter from the COMPDAT keyword item 9 will be used if it is defined otherwise 0.5 feet will be used.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"0.5 feet","value_type":"DOUBLE","dimension":"Length"},{"index":6,"name":"FCAOF","description":"A real positive value that defines the flow area for each connection. If FCAOF is defaulted then the value will be evaluated as 2πrwh, where rw is equal to FCRADIUS, and h is evaluated using the permeability thickness kh value from the COMPDAT keyword item 10 and the permeability FCPERM item 3 above.","units":{"field":"ft2","metric":"m2","laboratory":"cm2"},"default":"2πrwh","value_type":"DOUBLE","dimension":"Length*Length"},{"index":7,"name":"I","description":"An integer that defines the matching connection location in the I-direction. If set to < 1 then all connections in the I-direction that also satisfy J and K criteria are selected.","units":{},"default":"-1","value_type":"INT"},{"index":8,"name":"J","description":"An integer that defines the matching connection location in the J-direction. If set to < 1 then all connections in the J-direction that also satisfy I and K criteria are selected.","units":{},"default":"-1","value_type":"INT"},{"index":9,"name":"K","description":"An integer that defines the matching connection location in the K-direction. If set to < 1 then all connections in the K-direction that also satisfy I and J criteria are selected.","units":{},"default":"-1","value_type":"INT"}],"example":"The following example defines the filter cake properties for a water injection well using WINJDAM:\n--\n-- WELL FILTER CAKE PROPERTIES\n--\n-- WELL LINEAR/ PERM PORO WELL FLOW --LOCATION--\n-- NAME RADIAL RAD AREA II JJ KK\nWINJDAM\nINJ LINEAR 10 0.32 /\nINJ RADIAL 1 0.25 1* 1* 0 0 3 /\n/\nWell INJ initially has a linear filter cake model for all completions with permeability of 10 mD, porosity of 0.32, and default well radius and flow area based on data from the COMPDAT keyword. This is then overwritten for completions in layer 3 with a radial filter cake model with permeability of 1 mD and porosity of 0.25 (again with default well radius and flow area).","expected_columns":9,"size_kind":"list"},"WINJFCNC":{"name":"WINJFCNC","sections":["SCHEDULE"],"supported":null,"summary":"The WINJFCNC keyword defines the injected filtrate concentration for wells that have previously been defined by the WELSPECS keyword in the SCHEDULE section.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the filter cake properties are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"FCONCPPM","description":"A real positive value that defines the volumetric concentration of filtrate in the injected water. This value may be specified using a User Defined Argument (UDA).","units":{"field":"ppm","metric":"ppm","laboratory":"ppm"},"default":"0","value_type":"UDA","dimension":"PPM"}],"example":"The following example defines the filtrate injection concentration for a water injection well using WINJFCNC:\n--\n-- WELL FILTRATE INJECTION CONCENTRATION\n--\n-- WELL FILTRATE\n-- NAME CONC\nWINJFCNC\nINJ-A1 10 /\nINJ-B* 30 /\n/\nWell INJ-A1 has a filtrate concentration of 10 ppm in the injection water, and wells matching INJ-B* have a concentration of 30 ppm.","expected_columns":2,"size_kind":"list"},"WINJGAS":{"name":"WINJGAS","sections":["SCHEDULE"],"supported":true,"summary":"The WINJGAS keyword defines the properties of the injection gas stream, for a given well. Once a gas well stream has been defined via the WELLSTRE keyword in the RUNSPEC section, it can be used with either the WINJGAS or GINJGAS keywords, to set the injected gas composition. Similarly, if an oil well stream has been defined by WELLSTRE, then the well stream can be used with the WINJOIL keyword in the SCHEDULE section, to specify the injected oil composition. Note that, it is unnecessary to use WINJGAS for wells subordinate to a group having gas injection control, with the gas properties set by GINJGAS keyword in the RUNSPEC section. In this case the injection stream is defined by the GINJGAS keyword. However, if a gas injection well under group control users the WINJGAS keyword, then this fluid, and not the group's fluid will be injected instead, at a rate controlled by the group.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the injection well name, for which the gas injection properties are being specified. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"STREAM","description":"A defined character string that determines the properties of the injection gas, and as should be set to one of the following values: GAS: The field separator gas composition is used as the injected gas. GRUP: The well's group or upstream group injection fluid is used as the injected gas. GV: This option enables the vapor production of a group, as declared via the SOURCE parameter on this record, to be used as the injected gas composition. MIX: In this case, the gas injection composition is taken from either the WINJMIX or WINJORD keywords in the SCHEDULE section, with the name of injected fluid given by the SOURCE parameter on this record. STREAM: Here the gas injection composition is given by the WELLSTRE keyword in the SCHEDULE section, with the name of injected fluid given by the SOURCE parameter on this record. WV: This option enables the vapor production from a given well to be used as the injected gas, with the name of the well given by the SOURCE parameter on this record. Only the STREAM option is supported by OPM Flow.","units":{},"default":"GRUP","value_type":"STRING"},{"index":3,"name":"SOURCE","description":"A character string of up to eight characters in length, that defines the source of the gas injection stream, based on the value of STREAM. If STREAM equals GV, then source should be set to a group name. For STREAM equal to MIX or STREAM, then SOURCE should be set to the name of the gas stream, as defined by the WINJMIX, WINJORD, or WELLSTRE keywords.","units":{},"default":"None","value_type":"STRING"},{"index":4,"name":"MAKEUP","description":"The name of the well stream used for the make-up gas, if make-up gas is required for WELNAME to match the injection target for the well. This option is not supported by OPM Flow.","units":{},"default":"None","value_type":"STRING"},{"index":5,"name":"STAGE","description":"STAGE defines the separator stage from which the injection gas should be taken from. In this case, the vapor phase from any stage may be used, and the default value of zero users the total vapor phase from the separator. This option is not supported by OPM Flow.","units":{},"default":"0","value_type":"DOUBLE","dimension":"1"}],"example":"The following example defines how to specify a two component formulation, together with defining the names of the composition components, to be used with the CO2STORE and GASWAT options.\n-- ==============================================================================\n--\n-- PROPS SECTION\n--\n-- ==============================================================================\nPROPS --\n-- CONFIRM NUMBER OF COMPOSITIONAL COMPONENTS (OPM FLOW KEYWORD)\n--\nNCOMPS\n2 /\n--\n-- DEFINE COMPOSITIONAL COMPONENTS NAMES (OPM FLOW KEYWORD)\n--\nCNAMES\n'CO2'\n'H2O' /\nThe second part of the example, defines the well stream for the above two component CO2 water system.\n-- ==============================================================================\n--\n-- SCHEDULE SECTION\n--\n-- ==============================================================================\nSCHEDULE\n--\n-- WELL STREAM INJECTION COMPOSITION (OPM FLOW Keyword)\n--\n-- WELL -- WELL STREAM COMPOSITIONAL COMPONENT --\n-- STREAM -- MOLE FRACTIONS --\nWELLSTRE\n'C02STREAM' 1.000 0.000 /\n/\n--\n-- WELL GAS INJECTION PROPERTIES\n--\n-- WELL STREAM SOURCE MAKEUP SEP\n-- NAME OPTION DEPTH GAS STAGE\nWINJGAS\nGI01 STREAM C02STREAM 1* 1* /\n/\nHere the well stream consists of 100% CO2 and zero water, with well GI01 using the gas injection properties as defined by the WELLSTRE keyword and allocated via the WINJGAS keyword.\nFinally, the gas injection rate is set via the WCONINJE keyword as shown below.\n--\n-- WELL INJECTION CONTROLS\n--\n-- WELL FLUID OPEN/ CNTL SURF RESV BHP THP VFP\n-- NAME TYPE SHUT MODE RATE RATE PRES PRES TABLE\nWCONINJE\nGI01 GAS OPEN RATE 10E4 1* 300 1* 1* /\n/\nThus, gas injector GI01 will inject 10 x 104 m3 of CO2 per day, assuming metric units.\n| Note This is an OPM Flow keyword used with OPM Flow’s CO2STORE and GASWAT keywords in the RUNSPEC section, and should not be confused with the more general version of the WINJGAS keyword used in the commercial compositional simulator. Secondly, although OPM Flow parses the keyword, the simulator currently ignores the data for this keyword. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":5,"size_kind":"list"},"WINJMULT":{"name":"WINJMULT","sections":["SCHEDULE"],"supported":null,"summary":"The WINJMULT keyword defines pressure dependent injectivity multipliers for injection wells and can be used to approximate the increase or decrease in a well’s injectivity due to hydraulic fracturing in water injection wells. Only injection wells are processed by this keyword, even if production wells have been entered by the keyword.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well connection data are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"FRACPRES","description":"FRACPRES is the fracture opening pressure (Pfractue) used in equation 12.3.296.1.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":"Pressure"},{"index":3,"name":"ALPHA","description":"ALPHA is the multiplier gradient, α, in equation 12.3.296.1.","units":{"field":"1/psia 0.0","metric":"1/barsa 0.0","laboratory":"1/atma 0.0"},"default":"Defined","value_type":"DOUBLE","dimension":"1/Pressure"},{"index":4,"name":"OPTION","description":"A defined character string that determines how the data on this keyword is applied, and should be set to one of the following character strings: CIRR: The injectivity multiplier as applied to the selected connections (I, J, K) is irreversible, and the pressure at the connection’s sand face (Pwbhp) is used in equation 12.3.296.1, instead of the well’s flowing bottom-hole pressure. This option means that even if the pressures in the wellbore, and therefore the sand face pressures, later declines, injectivity remains unchanged for all the connections. CREV: The injectivity multiplier as applied to the selected connections (I, J, K) is reversible, and the pressure at the connection’s sand face is used in equation 12.3.296.1, The reversibility of this option means that if the pressures in the wellbore, and therefore the sand face pressures, later declines, injectivity will also decline for all the connections. WREV: The injectivity multiplier as applied to all connections in the well is reversible, and the wells’ flowing bottom-hole pressure (Pwbhp) is used in equation 12.3.296.1, instead of the pressure at the connection’s sand face. The connections stipulated by (I, J, K) are ignored. The reversibility of this option means that if the pressures in the wellbore, later declines, injectivity will also decline for all the connections.","units":{},"default":"WREV","value_type":"STRING"},{"index":5,"name":"I","description":"An integer value less than or equal to NX that defines the connection location in the I-direction. If set to zero, a negative value, or defaulted with 1* then all connections in the I-direction will be multiplied by ALPHA, depending on the selected OPTION value.","units":{},"default":"1*","value_type":"INT"},{"index":6,"name":"J","description":"An integer value less than or equal to NY that defines the connection location in the J-direction. If set to zero, a negative value, or defaulted with 1* then all connections in the J-direction will be multiplied by ALPHA, depending on the selected OPTION value.","units":{},"default":"1*","value_type":"INT"},{"index":7,"name":"K","description":"An integer value less than or equal to NZ that defines the connection location in the K-direction. If set to zero, a negative value, or defaulted with 1* then all connections in the K-direction will be multiplied by ALPHA, depending on the selected OPTION value.","units":{},"default":"1*","value_type":"INT"}],"example":"The example below show the WINJMULT keyword for three water injection wells.\n--\n-- DEFINE WELL CONNECTION MULTIPLIERS\n--\n-- WELL FRAC MULT FRAC --LOCATION--\n-- NAME PRES VALUE OPTN I J K\nWINJMULT\nWI01 4200 0.0250 1* 1* 1* 1* /\nWI02 4250 0.0025 CIRR 1* 1* 145 /\nWI02 4250 0.0025 CIRR 1* 1* 146 /\nWI02 4250 0.0025 CIRR 1* 1* 147 /\nWI03 4400 0.0055 CREV 1* 1* 160 /\nWI03 4400 0.0055 CREV 1* 1* 165 /\n/\nThe first well, WI01, uses the default value for OPTION, that is WREV, which means that the injectivity multiplier will be applied to all the connections in the well and the well’s bottom-hole pressure is used in the calculation. In this case the process is reversible. The second well, WI02, applies the injectivity multiplier to all connections in layers 145 to 147 using the sand face pressures in the calculation, and the process is irreversible. Finally for well WI03, the multiplier is applied to all connections in layers 160 and 165 using the sand face pressures in the calculation, and in this case the process is reversible.\n| [matrix{ \nalignr Multiplier {}={} # 1.0 `+` %alpha ` left( P_WBHP `` - `` P_fracture right) #alignl \" for \" {P sub WBHP} `>` {P sub fracture} \n##\nalignr Multiplier {}={} # 1.0 # alignl \" for \" {P sub WBHP} `<` {P sub fracture}\n}] | (12.3.296.1) |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|\n| Note If all the connection parameters (I, J, K) are defaulted, or OPTION is set equal to WREV, then the multiplier is applied to all connections in the well. If any of the connection parameters (I, J, K) have positive values and OPTION is set equal to CIRR or CREV, then the multiplier is applied to the selected connections as determined by the (I, J, K) parameters. |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":7,"size_kind":"list"},"WINJTEMP":{"name":"WINJTEMP","sections":["SCHEDULE"],"supported":true,"summary":"WINJTEMP defines the injection fluid thermal properties for when the thermal option has been activated by the THERMAL keyword in the RUNSPEC section. Only water and gas injection is supported.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well injection fluid thermal properties are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"STEAMQAL","description":"STEAMQAL is a real positive value greater than or equal to zero and less than or equal to one that defines the steam quality of the injected fluid for the defined well. This parameter should be defaulted using 1* as STEAMQAL is not used by OPM FLOW, as only water and gas injection is supported. This data is used by the commercial simulator’s THERMAL option and is not supported by OPM Flow’s THERMAL option.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1*","value_type":"DOUBLE"},{"index":3,"name":"TEMP","description":"TEMP is a real positive value that defines the temperature of the injected fluid for the defined well.","units":{"field":"oF","metric":"oC","laboratory":"oC"},"default":"None","value_type":"DOUBLE","dimension":"Temperature"},{"index":4,"name":"PRES","description":"PRES is a real positive value that defines the pressure of the injected fluid for the defined well.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":"Pressure"},{"index":5,"name":"ENTHALPY","description":"ENTHALPY is a real positive value that defines the specific enthalpy of the injected fluid for the defined well. This is data is used by the commercial simulator’s THERMAL option and is not supported by OPM Flow’s THERMAL option.","units":{"field":"Btu/lbs-M","metric":"kJ/kg-M","laboratory":"J/gm-M"},"default":"None","value_type":"DOUBLE","dimension":"Energy/Mass"}],"example":"The following example shows the WINJTEMP keyword for when OPM Flow’s temperature option has been activated by the THERMAL keyword in the RUNSPEC section.\n--\n-- INJECTION FLUID THERMAL PROPERTIES\n--\n-- WELL STEAM INJ INJ SPEC\n-- NAME QUAL TEMP PRES ENTH\nWINJTEMP\nWI01 1* 68.0 220.0 1* /\nWI02 1* 70.0 230.0 1* /\n/\nHere the water injection fluid’s temperature and pressure, in field units, for two water injections well are defined. Notice that both the steam quality and the specific enthalpy of the injected fluid for the defined wells are defaulted (or skipped), as OPM Flow’s THERMAL option does not support this data.","expected_columns":5,"size_kind":"list"},"WLIFT":{"name":"WLIFT","sections":["SCHEDULE"],"supported":null,"summary":"The WLIFT defines the automatic workovers parameters for changing out wellbore tubing, changing the THP limit (for example switching from the high stage pressure separator to the low stage pressure separator), or changing the artificial lift parameters, for wells.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"TRIGGER_LIMIT","description":"The dimension here depends on the phase - must be handled in the application","units":{},"default":"","value_type":"DOUBLE"},{"index":3,"name":"TRIGGRE_PHASE","description":"","units":{},"default":"","value_type":"STRING"},{"index":4,"name":"NEW_VFP_TABLE","description":"","units":{},"default":"","value_type":"INT"},{"index":5,"name":"NEW_ALQ_VALUE","description":"The dimension here depends on the phase - must be handled in the application","units":{},"default":"","value_type":"DOUBLE"},{"index":6,"name":"NEW_WEFAC","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":7,"name":"WWCT_LIMIT","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":8,"name":"NEW_THP_LIMIT","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":9,"name":"WGOR_LIMIT","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":10,"name":"ALQ_SHIFT","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":11,"name":"THP_SHIFT","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"}],"example":"","expected_columns":11,"size_kind":"list"},"WLIFTOPT":{"name":"WLIFTOPT","sections":["SCHEDULE"],"supported":null,"summary":"The WLIFTOPT defines which wells should use the Gas Lift Optimization facility in order to maximize oil production, as well as defining the associated gas lift optimization parameters for a given well. The keyword can also be used to switch off gas lift optimization for a well. Gas lift optimization is invoked via the LIFTOPT keyword in the SCHEDULE section. Note that the LIFTOPT keyword should precede the WLIFTOPT keyword in the SCHEDULE section in order to activate the gas lift optimization facility.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well gas lift optimization parameters are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"OPTLIFT","description":"A defined character string that sets if a well’s gas lift gas rate should be calculated by the gas lift optimization facility or not, and should be set to: NO: In this case the gas lift gas is a constant determined from the MXLIFT variable on this keyword, the ALQ-WELL variable on the WCONPROD keyword, or the TARGET and VALUE variables on the WELTARG keyword. YES: Activates the gas lift optimization for the given well.","units":{},"default":"None","value_type":"STRING"},{"index":3,"name":"MXLIFT","description":"A real value that defines the total amount of gas lift gas available for this well, multiplied by the well’s efficiency factor. If OPTLIFT is defined as NO then MXLIFT is considered a fixed gas lift gas rate. However, if MXLIFT is defaulted (1*) then MXLIFT is unchanged from the previously entered value. If OPTLIFT equals YES and MXLIFT is defaulted (1*), then MXLIFT is taken from the largest value of the ALQ variable on the well’s associated VFPPROD table. Note that the value entered here should be in the range entered in the VFPPROD table allocated to the well, otherwise errors may occur when optimizing the gas lift gas injection rate for the well.","units":{"field":"Mscf/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"1*","value_type":"DOUBLE","dimension":"GasSurfaceVolume/Time"},{"index":4,"name":"OPTWGT","description":"OPTWGT (βw) is real positive value that defines a weighting factor for allocating the available gas lift gas to a well. An increment of gas lift gas supply is allocated to a well based on the well’s current incremental gradient multiplied by OPTWGT using the following formulae: [Gradient`=` left ( left ( %beta _w times %DELTA Q_Oil right ) over left (%DELTA Q_GasLift``+`` %beta_g times %DELTA Q_Gas right) right)] Where: βw = is OPTWGT, the weighting factor for the preferential allocation of lift gas, βg = is the gas production rate weighting factor, ∆QOil = is the increment/decrement in oil production rate, ∆Qgas = is the increment/decrement in gas production rate, and ∆QGasLift = is the increment/decrement in gas lift gas rate. Note by default βg, the gas production rate weighting factor, is set to zero, and therefore the gradient equation simplifies to: [Gradient`=` left ( { %beta _w times %DELTA Q_Oil } over {%DELTA Q_GasLift} right)] OPTWGT is ignored if OPTLIFT is equal to NO.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1","value_type":"DOUBLE"},{"index":5,"name":"MINGAS","description":"A real value that defines the minimum amount of gas lift gas available to the well, multiplied by the well’s efficiency factor. The allocation of the gas lift gas is determined by: If MINGAS is a positive value then this value is allocated to the well unless the well is unable flow with this quantity of gas lift gas. Alternatively, if the well is able to meet it’s target rate without applying MINGAS, then the MINGAS rate is not applied to the well. If MINGAS is a negative value, then the well is supplied with sufficient gas lift gas to allow the well to flow, subject to the maximum allowed gas lift quantity, as per MXLIFT variable on this keyword. The negative value itself is not used in any calculations. If there is insufficient available gas lift gas, the wells are assigned values of MINGAS based on the decreasing order of their weighting factors as calculated per OPTWGT variable. Wells belonging to groups that can meet their production targets without gas lift, will have their MINGAS values not applied, that is no gas lift is applied. The exception is that if OPTWGT has been set to a value greater than or equal to one, then the well will use the MINGAS value for it’s gas lift gas, even if the group’s target can be satisfied without gas lift. However, if both the well’s group and the well can meet their production targets, then MINGAS will not be applied. This parameter is ignored if OPTLIFT is defined as NO.","units":{"field":"Mscf/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"0.0","value_type":"DOUBLE","dimension":"GasSurfaceVolume/Time"},{"index":6,"name":"OPTGAS","description":"OPTGAS (βg) is real positive value that defines the incremental gas weighting factor for allocating the available gas lift gas to a well. An increment of gas lift gas supply is allocated to a well based on the well’s current incremental gradient as described by the definition of the OPTWGT (βg) variable above, that is by the following formulae: [Gradient`=` left ( left ( %beta _w times %DELTA Q_Oil right ) over left (%DELTA Q_GasLift``+`` %beta_g times %DELTA Q_Gas right) right)] See OPTWGT for a definition of the variables in the equation. This parameter is ignored if OPTLIFT is defined as NO.","units":{"field":"dimensionless1","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.0","value_type":"DOUBLE"},{"index":7,"name":"OPTLIMIT","description":"A defined character string that defines if additional gas lift gas should be applied to the well, if the well’s group gas target has been satisfied but the group’s oil rate limit has not been achieved. NO: Additional gas lift gas is not available for the given well. YES: Additional gas lift gas is available for the given well. In cases where a well receiving additional gas lift may cause the well’s group to exceed the group’s gas target, normally the well will not be assigned the additional gas lift gas. However, if OPTLIMIT is set to YES, then this constraint is removed. This results in the gas lift optimization procedure continuing to maximize the oil rate, subject to available constraints. However, upon completion of the optimization process, applying the group controls may negate the gain from the gas lift optimization process. This parameter is ignored if OPTLIFT is defined as NO.","units":{},"default":"NO","value_type":"STRING"}],"example":"The following example first switches on gas lift optimization via the LIFTOPT keyword and then defines the artificial lift constraints for PLAT-A, using the GLIFTOPT keyword and sets the well gas lift parameters using the WLIFTOPT keyword.\n-- ACTIVATE GAS LIFT OPTIMIZATION AND PARAMETERS\n--\n-- INCR INCR TSTEP NEWTON\n-- GAS OIL INTVAL OPTN\nLIFTOPT\n12.5E3 5E-3 0.0 YES /\n/\n--\n-- GROUP GAS LIFT OPTIMIZATION CONSTRAINTS\n--\n-- GRUP MAX MAX\n-- NAME GAS ALQ TOTAL GAS\nGLIFTOPT\nPLAT-A 200E3 1* /\n/\n--\n-- WELL GAS LIFT OPTIMIZATION PARAMETERS\n--\n-- WELL OPTN MAX WEIGHT MIN GAS OPTN\n-- NAME LIFT LIFT FACTOR LIFT FACTOR LIMIT\nWLIFTOPT\nOP01 YES 150E3 1.01 -1.0 /\nOP02 YES 150E3 1.01 -1.0 /\nOPO3 YES 150E3 1.01 -1.0 /\nOP04 YES 150E3 1.01 -1.0 /\nOP05 YES 150E3 1.01 -1.0 /\n/\nHere the LIFTOPT keyword defines the maximum incremental gas lift gas quantity to be 12.5 x 103 m3, the minimum incremental oil gain per m3 of gas lift gas is set to 5.0 x 10-3 m3, the time step interval is set to zero to perform the gas optimization every time step, and finally the gas lift optimization will be performed NUPCOL Newton iterations for the time step.\nThe GLIFTOPT keyword sets the maximum amount of gas lift gas for PLAT-A to 200,000 m3 and there is no maximum limit for the total maximum amount of gas that the group can process. In addition, WLIFTOPT sets all five wells to have gas lift gas optimization implemented with a maximum gas lift gas value of 150,000 m3 per well, with equal weighting factors and all wells are supplied with sufficient gas lift gas to allow the wells to flow, (minimum lift set to a negative value) subject to the maximum allowed gas lift quantity for the well (150,000 m3).","expected_columns":7,"size_kind":"list"},"WLIMTOL":{"name":"WLIMTOL","sections":["SCHEDULE"],"supported":false,"summary":"WLIMTOL keyword defines the tolerance to be used for various constraints applied to connections, completions (if connections have been lumped via the COMPLUMP keyword in the SCHEDULE section), wells, and groups, including the field group. See also the GCONTOL keyword in the SCHEDULE section that sets the tolerance parameters for groups.","parameters":[{"index":1,"name":"TOLERANCE_FRACTION","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"WLIST":{"name":"WLIST","sections":["SCHEDULE"],"supported":null,"summary":"WLIST declares a group of wells to belong to a named static well list. Wells in a named well list are treated as a group of wells for which the standard well keywords can be applied. For example, instead of repeating a well keyword for each well, the keyword only needs to have the named well list instead, for the action to be applied to all wells in the named well list. In general any well keyword that allows well name roots as a well name, for example, PROD*, can use a named well list.","parameters":[{"index":1,"name":"WLIST","description":"A character string of up to eight characters in length, enclosed in quotes, that defines the well list name for the WELNAMES declared by this record. Note the first character must be asterisk (“*”) and the second character must be a letter, for example, *PROD.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"ACTION","description":"A defined character string that determines how the WELNAMES should be handled with respect to the named well list (WLIST). ACTION should be set to one of the following:: ADD: Add the WELNAMES to an existing WLIST. DEL; Delete WELNAMES from an existing WLIST. MOV: WELNAMES from another existing named well list and ADD them to WLIST. NEW: Define a new named well list and add the WELNAMES to WLIST.","units":{},"default":"","value_type":"STRING"},{"index":"3-52","name":"WELNAMES","description":"A character string of up to eight characters in length that defines the well name that belongs to the named well list (WLIST). A total of 50 well names can be added to WLIST at a time. If additional wells are needed to added then use the ADD option of ACTION to add additional wells. Well names roots may all be used in WELNAMES as long as they are enclosed in quotes and end with an asterisk (“*”). In this case all wells that match the specification will be added to the list. For example, wells named OP01, OP02 and OP03, can be added as group by using “OP*” as the well name. Note that the well names must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur","units":{},"default":"","value_type":"STRING"}],"example":"The following example defines two named well lists using the WLIST keyword.\n--\n-- WELL LIST SPECIFICATION\n--\n-- LIST OPER WELL NAME LIST\n-- NAME\nWLIST\n'*BLK-1' NEW WEL-01M WEL-02M WEL-03M WEL-04M WEL-05M WEL-06M WEL-07M /\n'*BLK-1' ADD WEL-08M WEL-09M WEL-10M WEL-11M WEL-12M WEL-13M WEL-14M /\n'*BLK-1' ADD WEL-15M WEL-16M WEL-17M WEL-18M WEL-19M WEL-20M WEL-23M /\n'*BLK-1' ADD WEL-24M WEL-25M WEL-26M WEL-28M /\n'*BLK-2' NEW WEL-03U WEL-05U WEL-06U WEL-10U WEL-11U WEL-13U WEL-14U /\n'*BLK-2' ADD WEL-15U WEL-16U WEL-17U WEL-18U WEL-19U WEL-25U WEL-27U /\n/\nDATES\n1 JAN 2020 /\n/\n--\n-- DEFINE WELL AND WELL CONNECTIONS FLOWING STATUS\n--\n-- WELL WELL --LOCATION-- COMPLETION\n-- NAME STAT I J K FIRST LAST\nWELOPEN\n'*BLK-1' OPEN /\n'*BLK-1' OPEN 0 0 0 0 0 /\n/\nDATES\n1 JAN 2021 /\n1 JLY 2021 /\n1 OCT 2021 /\n/\n--\n-- DEFINE WELL AND WELL CONNECTIONS FLOWING STATUS\n--\n-- WELL WELL --LOCATION-- COMPLETION\n-- NAME STAT I J K FIRST LAST\nWELOPEN\n'*BLK-2' OPEN /\n'*BLK-2' OPEN 0 0 0 0 0 /\n/\nIn this example the wells in named well list ‘’*BLK-1” are opened on January 1, 2020 and wells in named well list ’*BLK-2” are opened October 1, 2021.","size_kind":"list","variadic_record":true},"WLISTARG":{"name":"WLISTARG","sections":["SCHEDULE"],"supported":false,"summary":"The WLISTARG keyword modifies the target and constraint values of both rates and pressures for wells previously defined in a well list by the WLIST or WLISTNAM keywords. WLISTARG is similar to the WELTARG keyword in it that allows for modifying targets and constraints without having to define all the variables on the well control keywords: WCONPROD, WCONHIST, WCONINJE, or WCONINJH keywords. Variables not changed by the WLISTARG keyword remain the same as those previously entered via the well control keywords or previously entered WLISTARG keywords. Note that the well must still be initially be fully defined using the WCONPROD or WCONINJE keywords. All the aforementioned keywords are described in the SCHEDULE section.","parameters":[{"index":1,"name":"WLIST","description":"A character string of up to eight characters in length, enclosed in quotes, that defines the well list name declared by the WLIST keyword. Note the first character must be asterisk (“*”) and the second character must be a letter, for example, *PROD.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"TARGET","description":"A defined character string that sets the item to be changed for the well the value of the item is set by item (3). ORAT: reset the surface oil production rate value as defined by item (3). WRAT: reset the surface water production rate value as defined by item (3). GRAT: reset the surface gas production rate value as defined by item (3). LRAT: reset the surface liquid (oil plus water) production rate value as defined by (3). RESV: reset the in situ reservoir volume rate value as defined by (3). BHP: reset the bottom-hole pressure value as defined by item (3). THP: reset the tubing head pressure value for the well as defined by item (3). VFP: reset the vertical lift performance table number as defined by (3). LIFT: reset the artificial lift quantity for use with vertical lift performance tables. GUID: reset the guide rate value for wells operating under group control. Note TARGET only defines the variable to be changed, it does not change how a well is controlled. For example, if a well is operating on ORAT control, as defined by the previously entered WCONPROD keyword, entering TARGET equal to LRAT with a value, changes the liquid constraint but the well still remains on ORAT control. Use the WELCNTL keyword in the SCHEDULE section to change the control mode of a well.","units":{},"default":"None","value_type":"STRING","options":["ORAT","WRAT","GRAT","LRAT","RESV","BHP","THP","VFP","LIFT","GUID"]},{"index":3,"name":"VALUE Liquid Gas Res Vol Pressure VFP LIFT","description":"A real positive vector of values that defines the value of the variable declared by TARGET for all the wells contained in WLIST. For example if there are four wells in WLIST then there must four real numbers for VALUE. The vector should be terminated by a “/” as indicated in the notes below.","units":{"field":"stb/d Mscf/d rb/d psia dimensionless same as VFPPROD or VFPINJ","metric":"sm3/day sm3/day rm3/day barsa dimensionless same as VFPPROD or VFPINJ","laboratory":"scc/hour scc/hour rcc/hour atma dimensionless same as VFPPROD or VFPINJ"},"default":"None","value_type":"DOUBLE"}],"example":"The following example defines two named well lists using the WLIST keyword.\n--\n-- WELL LIST SPECIFICATION\n--\n-- LIST OPER WELL NAME LIST\n-- NAME\nWLIST\n'*BLK-1' NEW WEL-01M WEL-02M WEL-03M /\n'*BLK-2' NEW WEL-03U WEL-05U WEL-06U WEL-10U /\n/\n--\n-- WELL PRODUCTION AND INJECTION TARGETS\n--\n-- WELL WELL TARGET\n-- NAME TARG VALUE\nWLISTARG\n‘*BLK-1’ ORAT 2000.0 2000.00 2000.0 /\n‘*BLK-2’ ORAT 3000.0 3500.00 4000.0 2000.0 /\n/\nThe wells in the '*BLK-1' well list are all given an oil rate of 2,000 stb/d and wells in the '*BLK-2' well list are given rates of 3,000, 3,500, 4,000 and 2,000 stb/d.","size_kind":"list","variadic_record":true},"WLISTNAM":{"name":"WLISTNAM","sections":["SCHEDULE"],"supported":false,"summary":"WLISTNAM declares a group of wells to belong to a named WLISTARG well list for use with the WLISTARG keyword. Only the WLISTARG keyword can be used with this type of well list, and therefore it is better to use the WLIST keyword instead, that defines a static well list but offers more flexibility than a WLISTNAM well list.","parameters":[{"index":1,"name":"WLIST","description":"A character string of up to eight characters in length, enclosed in quotes, that defines the well list name for the WELLNAMES declared by this record. Note the first character must be asterisk (“*”) and the second character must be a letter, for example, *PROD.","units":{},"default":"None","value_type":"STRING"},{"index":"2-51","name":"WELNAMES","description":"A character string of up to eight characters in length that defines the well name that belongs to the named well list (WLIST). A total of 50 well names can be added to WLISTNAM at a time. If the first well name in the list is the default value (“*1”), then the list is first cleared of all wells, before adding the subsequent wells in WELLNAMES. Well names roots may all be used in WELLNAMES as long as they are enclosed in quotes and end with an asterisk (“*”). In this case all wells that match the specification will be added to the list. For example, wells named OP01, OP02 and OP03, can be added as group by using “OP*” as the well name. Note that the well names must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"1*","value_type":"STRING"}],"example":"The following example defines two named well lists using the WLISTNAM keyword.\n--\n-- WELL LIST SPECIFICATION\n--\n-- LIST WELL NAME LIST\n-- NAME\nWLISTNAM\n'*BLK-1' WEL-01M WEL-02M WEL-03M WEL-04M WEL-05M WEL-06M WEL-07M /\n'*BLK-1' WEL-08M WEL-09M WEL-10M WEL-11M WEL-12M WEL-13M WEL-14M /\n'*BLK-1' WEL-15M WEL-16M WEL-17M WEL-18M WEL-19M WEL-20M WEL-23M /\n'*BLK-1' WEL-24M WEL-25M WEL-26M WEL-28M /\n'*BLK-2' 1* WEL-03U WEL-05U WEL-06U WEL-10U WEL-11U WEL-13U WEL-14U /\n'*BLK-2' WEL-15U WEL-16U WEL-17U WEL-18U WEL-19U WEL-25U WEL-27U /\n/\nHere well list '’*BLK-1’ contains 28 wells, that is wells WEL-01M to WEL-28M. For the '*BLK-2' well list all wells are first deleted due to the “1*” default value and then wells WEL-03U to WEL-27U are added to the list.","size_kind":"list","variadic_record":true},"WMICP":{"name":"WMICP","sections":["SCHEDULE"],"supported":null,"summary":"The WMICP keyword defines a water injection well's microbial, growth, and cementation injection stream solutions, where the rate-limiting components are suspended microbes, oxygen, and urea concentrations respectively. These concentrations are used when the MICP keyword in the RUNSPEC section has been used to activate OPM Flow’s Microbially Induced Calcite Precipitation model. See Landa-Marbán et al331\n Landa-Marbán, D., Tveit, S., Kumar, K., Gasda, S.E., 2021. Practical approaches to study microbially induced calcite precipitation at the eld scale. Int. J. Greenh. Gas Control 106, 103256. https://doi.org/10.1016/j.ijggc.2021.103256. and 332\n Landa-Marbán, D., Kumar, K., Tveit, S., Gasda, S.E., 2021. Numerical studies of CO2 leakage remediation by micp-based plugging technology. In: Røkke, N.A. and Knuutila, H.K. (Eds) Short Papers from the 11th International Trondheim CCS conference, ISBN: 978-82-536-1714-5, 284-290.for a description of the model.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well connection data is being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"MICRCON","description":"MICRCON is a real positive value that defines the microbial concentration of the well’s injection stream.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"0.0","value_type":"DOUBLE","dimension":"Concentration"},{"index":3,"name":"OXYGCON","description":"A real positive value that defines the oxygen concentration of the well’s injection stream.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"0.0","value_type":"DOUBLE","dimension":"Concentration"},{"index":4,"name":"UREACON","description":"UREACON is a real positive value that defines the urea concentration of the well’s injection stream.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"0.0","value_type":"DOUBLE","dimension":"Concentration"}],"example":"--\n-- DEFINE WATER INJECTION WELL MICROBIAL, OXYGEN, AND UREA CONCENTRATIONS\n--\n-- WELL MICROBIAL OXYGEN UREA\n-- NAME MICRCON OXYGCON UREACON\n-- -------- -------- --------\nWMICP\nWI01 0.01 /\nWI02 1* 0.04 /\nWI03 1* 1* 60.0 /\nWI04 1* 0.04 60.0 /\n/\nHere the microbial concentration for well WI01 is set to 0.01, the oxygen concentration for well WI02 is set to 0.04, the urea concentration for well WI03 is set to 60, and the oxygen and urea concentrations for well WI04 are set to 0.04 and 60 respectively.\n| Note This is an OPM Flow specific keyword. |\n|--------------------------------------------|","expected_columns":4,"size_kind":"list"},"WNETCTRL":{"name":"WNETCTRL","sections":["SCHEDULE"],"supported":false,"summary":"The WNETCNTL keyword sets a well’s control mode that should remain fixed after each network balancing calculation, for when the either the Standard Network or the Extended Network options have been activated, and the well is part of a network. The keyword allows for a well’s Tubing Head Pressure (“THP”), oil, gas, liquid, or water rate to be selected as fixed after each network balance calculation. Normally this should be the THP, and if the keyword is absent from the input deck then THP will be used as the default value. The Standard Network option is invoked if the GRUPTREE, GRUPNET, GNETINJE, GNETPUMP, etc. series of keywords have been used in the SCHEDULE section. Whereas, the Extended Network option is activated by the NETWORK keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"CONTROL","description":"","units":{},"default":"THP","value_type":"STRING"}],"example":"","expected_columns":2,"size_kind":"list"},"WNETDP":{"name":"WNETDP","sections":["SCHEDULE"],"supported":false,"summary":"The WNETDP keyword allows for a constant pressure drop between a well’s Tubing Head Pressure (“THP”) and the well’s connecting network node, for when the either the Standard Network or the Extended Network options have been activated, and the well is part of a network. For production wells in a production network, WNETDP is added to the well’s connecting network node pressure to arrive at the well’s THP value. Whereas for injection wells in an injection network, WNETDP is subtracted from the well’s connecting network node pressure to arrive at the well’s THP value. The Standard Network option is invoked if the GRUPTREE, GRUPNET, GNETINJE, GNETPUMP, etc. series of keywords have been used in the SCHEDULE section. The Extended Network option is activated by the NETWORK keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"DP","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Pressure"}],"example":"","expected_columns":2,"size_kind":"list"},"WORKLIM":{"name":"WORKLIM","sections":["SCHEDULE"],"supported":false,"summary":"WORKLIM sets the numbers of days taken to complete a workover.","parameters":[{"index":1,"name":"LIMIT","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"WORKTHP":{"name":"WORKTHP","sections":["SCHEDULE"],"supported":false,"summary":"The WORKTHP keyword defines workover options for when a well dies, that is unable to produce at the current operating conditions, when under Tubing Head Pressure (“THP”) control. For example, if a well is producing to the high pressure separator and therefore has a high THP constraint, then the WORKTHP keyword can be used to switch the well to the lower pressure separator via re-setting the THP constraint.","parameters":[{"index":1,"name":"WELL_NAME","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"WORK_OVER_PROCEDURE","description":"","units":{},"default":"NONE","value_type":"STRING"}],"example":"","expected_columns":2,"size_kind":"list"},"WPAVE":{"name":"WPAVE","sections":["SCHEDULE"],"supported":false,"summary":"Not supported. It is used on Norne, but investigations showed no significant effect so we did not implement it.","parameters":[{"index":1,"name":"WPAVE1","description":"A real dimensionless value that defines the weighting factor between the inner block and the surrounding blocks used in the calculation of the connection factor weighted average pressure. If WPAVE1 is greater than or equal to zero and less than or equal to one, then the average pressure for each well connection is calculated based on this weighting factor. A value of zero indicates only the surrounding blocks should be used in the calculation; and a value of one indicates only the inner blocks should be used. If WPAVE1 is less than zero, then the average pressure for each well connection is weighted based on the pore volumes of the inner and surrounding blocks.","units":{},"default":"0.5","value_type":"DOUBLE"},{"index":2,"name":"WPAVE2","description":"A real dimensionless value greater than or equal to zero and less than or equal to one, that defines the weighting factor between the connection factor weighted average pressures and the pore volume weighted average pressures. If WPAVE2 is equal to one, then the average pressures are calculated based only on the connection factor weighted average pressures. If WPAVE2 is equal to zero, then average pressures are calculated based only on the pore volumes weighted average pressures.","units":{},"default":"1.0","value_type":"DOUBLE"},{"index":3,"name":"WPAVE3","description":"A defined character string that determines how the hydrostatic head calculation is performed in correcting the pressures to the BHP reference depth on the WELSPECS or WPAVEDEP keywords in the SCHEDULE section. WPAVE3 should be set to one of the following character strings: WELL: the hydrostatic head is calculated using the density of the fluid in the wellbore at the well connections. RES: he hydrostatic head is calculated using the density of the fluid in the reservoir with well connections and averaged over the connections. NONE: no hydrostatic correction is applied to the pressures.","units":{},"default":"WELL","value_type":"STRING","options":["WELL","RES","NONE"]},{"index":4,"name":"WPAVE4","description":"A defined character string that determines which connections should be used in the calculations, WPAVE4 should be set to one of the following character strings: OPEN: only open connections and associated grid blocks should be used in the calculations. This option may result in pressure discontinuities if connections are opened and closed during the run. ALL: all currently defined open and closed connections and associated grid blocks are used in the calculations. The pressure discontinuities issue mentioned above can be avoided with this option and defining all the well connections for a well at the beginning of the run. Only the OPEN option is currently supported by the simulator.","units":{},"default":"OPEN","value_type":"STRING","options":["OPEN","ALL"]}],"example":"The following example defines the default well block average pressure calculation parameters\n--\n-- DEFINE WELL BLOCK AVERAGE PRESSURE CALCULATION PARAMETERS\n--\n-- INNER PORV WELL OPEN\n-- OUTER CONN RES ALL\nWPAVE\n0.5 1.0 WELL ALL /\nAnd the next example shows the parameters used in the Norne model.\n--\n-- DEFINE WELL BLOCK AVERAGE PRESSURE CALCULATION PARAMETERS\n--\n-- INNER PORV WELL OPEN\n-- OUTER CONN RES ALL\nWPAVE\n1* 0.0 WELL ALL /\nHere only pore volume weighting is used instead of connection weighting.","expected_columns":4,"size_kind":"fixed","size_count":1},"WPAVEDEP":{"name":"WPAVEDEP","sections":["SCHEDULE"],"supported":null,"summary":"The WPAVEDEP keyword defines the reference depth to be used to calculate and report grid block average bottom-hole pressures for a well. This keyword can be used to override the values entered or defaulted on the WELSPECS keyword in the SCHEDULE section. The simulator corrects the grid block calculated pressures to a well’s reference depth using the hydrostatic well of the producing fluids.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well and well connection status data is being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"BHPREF","description":"A real value that defines the reference depth for reporting the bottom-hole pressure for the well. Ideally this value should be set to the midpoint of the perforations as defined by the COMPDAT keyword in the SCHEDULE section. If defaulted by 1* or set to a value less than or equal to zero, then the mid-point of shallowest connection defined by the COMPDAT keyword will be used.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"Mid-point of shallowest connection defined by the COMPDAT keyword","value_type":"DOUBLE","dimension":"Length"}],"example":"The following example illustrates how to set the bottom-hole reference depth for wells completed in different reservoirs that have different datum depths. Here it is assumed that all wells in a reservoir A have RES-A as part of their well name, and similarly for reservoirs B and C.\n--\n-- WELL SPECIFICATION DATA\n--\n-- WELL GROUP LOCATION BHP PHASE DRAIN INFLOW SHUT CROSS PRESS\n-- NAME NAME I J DEPTH FLUID AREA EQUA. IN FLOW TABLE\nWELSPECS\nRES-AOP1 PLATFORM 14 13 1* OIL 1* STD OPEN NO 1* /\nRES-AOP2 PLATFORM 17 16 1* OIL 1* STD OPEN NO 1* /\nRES-AOP3 PLATFORM 21 19 1* OIL 1* STD OPEN NO 1* /\nRES-BOP4 PLATFORM 28 96 1* OIL 1* STD OPEN NO 1* /\nRES-BOP5 PLATFORM 34 89 1* OIL 1* STD OPEN NO 1* /\nRES-COP6 PLATFORM 128 52 1* OIL 1* STD OPEN NO 1* /\nRES-COP7 PLATFORM 134 56 1* OIL 1* STD OPEN NO 1* /\nRES-COP8 PLATFORM 138 50 1* OIL 1* STD OPEN NO 1* /\nRES-COP9 PLATFORM 120 52 1* OIL 1* STD OPEN NO 1* /\n/\n--\n-- DEFINE WELL REFERENCE DEPTH FOR PRESSURE CALCULATIONS\n--\n-- WELL REF\n-- NAME DEPTH\n-- ---- ------\nWPAVEDEP\n'RES-A*’ 3100.0 /\n'RES-B*’ 3300.0 /\n'RES-C*’ 5909.0 /\n/\nIn the example the all wells dedicated to RES-A will have their bottom-hole reference depth set to 3,000 ft. TVDSS, RES-B wells to 3,300 ft. TVDSS and well RES-C wells to 5909 ft. TVDSS.\n| Note The keyword is normally used to reset a well’s bottom-hole pressure depth to match the pressure gauge depth for when observed pressure is available, for example when conducting a history match for a well test, or when attempting to match static bottom-hole surveys conducted on a well. |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":2,"size_kind":"list"},"WPIMULT":{"name":"WPIMULT","sections":["SCHEDULE"],"supported":null,"summary":"The WPIMULT keyword defines a well connection factor multiplier that scales the existing well connection factor values. The resulting effect is to scale the well’s productivity at the reporting time step the keyword is entered.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well and well connection status data is being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"PIMULT","description":"A real positive value that will be used to scale the well connection factors defined by I, J, K, C1 and C2 below.","units":{},"default":"1.0","value_type":"DOUBLE"},{"index":3,"name":"I","description":"An integer less than or equal to NX that defines the connection locations in the I-direction.","units":{},"default":"1*","value_type":"INT"},{"index":4,"name":"J","description":"An integer less than or equal to NY that defines the connection locations in the J-direction.","units":{},"default":"1*","value_type":"INT"},{"index":5,"name":"K","description":"An integer less than or equal to NZ that defines the connection locations in the K-direction.","units":{},"default":"1*","value_type":"INT"},{"index":6,"name":"C1","description":"An integer value that defines the first completion number in the range. Connections are lumped into completions via the COMPLUMP keyword, and C1 refers to the first completion number, as defined by the COMPLUMP keyword, and all the connections contained within the C1 completion.","units":{},"default":"1*","value_type":"INT"},{"index":7,"name":"C2","description":"An integer that defines the last completion in the range. Connections are lumped into completions via the COMPLUMP keyword, and C2 refers to the last completion number, as defined by the COMPLUMP keyword, and all the connections contained within the C2 completion.","units":{},"default":"1*","value_type":"INT"}],"example":"The following example defines three vertical oil wells using the WELSPECS keyword and their associated connection data.\n--\n-- WELL SPECIFICATION DATA\n--\n-- WELL GROUP LOCATION BHP PHASE DRAIN INFLOW SHUT CROSS PRESS\n-- NAME NAME I J DEPTH FLUID AREA EQUA. IN FLOW TABLE\nWELSPECS\nOP01 PLATFORM 14 13 1* OIL 1* STD OPEN NO 1* /\nOP02 PLATFORM 28 96 1* OIL 1* STD OPEN NO 1* /\nOP03 PLATFORM 128 56 1* OIL 1* STD OPEN NO 1* /\n/\n--\n-- WELL PRODUCTION WELL CONTROLS\n--\n-- WELL OPEN/ CNTL OIL WAT GAS LIQ RES BHP THP VFP VFP\n-- NAME SHUT MODE RATE RATE RATE RATE RATE PRES PRES TABLE ALFQ\nWCONPROD\n‘*’ SHUT GRUP 1* 1* 1* 1* 1* 200.0 /\n/\n--\n-- WELL CONNECTION DATA\n--\n-- WELL --- LOCATION --- OPEN SAT CONN WELL KH SKIN D DIR\n-- NAME II JJ K1 K2 SHUT TAB FACT DIA FACT FACT FACT PEN\nCOMPDAT\nOP01 1* 1* 1 10 OPEN 1* 1* 0.708 1* 0.0 1* 'Z' /\nOP01 1* 1* 15 30 OPEN 1* 1* 0.708 1* 0.0 1* 'Z' /\nOP01 1* 1* 35 90 OPEN 1* 1* 0.708 1* 0.0 1* 'Z' /\nOP02 1* 1* 1 10 OPEN 1* 1* 0.708 1* 0.0 1* 'Z' /\nOP03 1* 1* 35 90 OPEN 1* 1* 0.708 1* 0.0 1* 'Z' /\n/\n-- ASSIGN WELL CONNECTIONS TO COMPLETIONS\n--\n-- WELL --- LOCATION --- COMPL\n-- NAME II JJ K1 K2 NO. COMPLUMP OP03 1* 1* 35 45 1 / COMPLETION NO. 01\nOP03 1* 1* 50 90 2 / COMPLETION NO. 02\n/\n--\n-- DEFINE WELL CONNECTION MULTIPLIERS\n--\n-- WELL PI --LOCATION-- COMPLETION\n-- NAME MULT I J K FIRST LAST\nWPIMULT\nOP01 1.250 1* 1* 1* 1* 1* /\nOP02 0.750 1* 1* 10 1* 1* /\nOP03 1.100 1* 1* 1* 1 2 /\n/\nIn this example the WPIMULT scales the well productivity of well OP01 by 1.25, and scales all the well connection factors in layer 10 only by 0.75 for well OP02. For well OP03, WPIMULT scales all the connections in completions one and two by 1.1.","expected_columns":7,"size_kind":"list"},"WPIMULTL":{"name":"WPIMULTL","sections":["SCHEDULE"],"supported":false,"summary":"The WPIMULTL keyword defines a well connection factor multiplier that scales the existing well connection factor values, for a well in a Local Grid Refinement (“LGR”). The resulting effect is scale the well’s productivity at the reporting time step the keyword is entered.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well and well connection status data is being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECL keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"PIMULT","description":"A real positive value that will be used to scale the well connection factors defined by I, J, K, C1 and C2 below.","units":{},"default":"1.0","value_type":"DOUBLE"},{"index":3,"name":"LGRNAME","description":"A character string of up to eight characters in length that defines the LGR name for which the well LGR connection multiplier factor (PIMULT) is being defined. Note that LGRNAME must have been declared previously using the WELSPECL keyword in the SCHEDULE section, otherwise an error may occur. If defaulted with 1* the LGR on the WELSPECL keyword will be utilized.","units":{},"default":"Defined","value_type":"STRING"},{"index":3,"name":"I","description":"An integer less than or equal to NX that defines the connection location in the I-direction.","units":{},"default":"1*","value_type":"STRING"},{"index":4,"name":"J","description":"An integer less than or equal to NY that defines the connection location in the J-direction.","units":{},"default":"1*","value_type":"INT"},{"index":5,"name":"K","description":"An integer less than or equal to NZ that defines the connection location in the K-direction.","units":{},"default":"1*","value_type":"INT"},{"index":6,"name":"C1","description":"An integer value that defines the first completion in the range. Connections are lumped into completions via the COMPLUMP keyword, and C1 refers to the first completion number, as defined by the COMPLUMP keyword, and all the connections contained within the C1 completion","units":{},"default":"1*","value_type":"INT"},{"index":7,"name":"C2","description":"An integer value that defines the last completion in the range. Connections are lumped into completions via the COMPLUMP keyword, and C2 refers to the last completion number, as defined by the COMPLUMP keyword, and all the connections contained within the C2 completion","units":{},"default":"1*","value_type":"INT"},{"index":8,"name":"LAST","description":"","units":{},"default":"","value_type":"INT"}],"example":"The following example defines two vertical oil wells using the WELSPECL keyword and their associated connection data.\n--\n-- WELL LGR SPECIFICATION DATA\n--\n-- WELL GROUP LGR -LOCATION- BHP PHASE DRAIN INFLOW SHUT CROSS PVT\n-- NAME NAME NAME I J DEPTH FLUID AREA EQUA. IN FLOW TABLE\nWELSPECL\nOP01 PLAT OP01LGR 14 13 1* OIL 1* STD SHUT NO 1* /\nOP02 PLAT OP02LGR 28 96 1* OIL 1* STD SHUT NO 1* /\n/\n--\n-- WELL LGR CONNECTION DATA\n--\n-- WELL LGR ---LOCATION--- OPEN SAT CONN WELL KH SKIN D DIR\n-- NAME NAME II JJ K1 K2 SHUT TAB FACT DIA FACT FACT FACT PEN\nCOMPDATL\nOP01 OP01LGR 1* 1* 20 56 OPEN 1* 1* 0.708 1* 1* 1* Z /\nOP01 OP01LGR 1* 1* 75 100 SHUT 1* 1* 0.708 1* 1* 1* Z / OP02 OP02LGR 1* 1* 75 100 OPEN 1* 1* 0.708 1* 1* 1* Z /\nOP03 OP02LGR 1* 1* 75 100 OPEN 1* 1* 0.708 1* 1* 1* Z /\n/\n--\n-- ASSIGN WELL CONNECTIONS TO COMPLETIONS\n--\n-- WELL LGR --- LOCATION --- COMPL\n-- NAME NAME II JJ K1 K2 NO. COMPLMPL OP03 OP02LGR 1* 1* 75 85 1 / COMPLETION NO. 01\nOP03 OP21LGR 1* 1* 86 100 2 / COMPLETION NO. 02\n/\n--\n-- DEFINE WELL CONNECTION MULTIPLIERS\n--\n-- WELL PI LGR --LOCATION-- COMPLETION\n-- NAME MULT NAME I J K FIRST LAST\nWPIMULTL\nOP01 1.250 OP01LGR 1* 1* 1* 1* 1* /\nOP02 0.750 OP01LGR 1* 1* 10 1* 1* /\nOP03 1.100 OP02LGR 1* 1* 1* 1 2 /\n/\nIn this example the WPIMULTL keyword scales the well productivity of well OP01 by 1.25, scales all the well connection factors in layer 10 only by 0.75 for well OP02, and for OP03, scales all the connections in completions one and two by 1.100.","expected_columns":8,"size_kind":"list"},"WPITAB":{"name":"WPITAB","sections":["SCHEDULE"],"supported":false,"summary":"The WPITAB keyword assigns the well productivity index multiplier versus water cut tables, that are used to scaled a well’s connection factors based on the connection’s current producing water cut, to a well. The tables are defined via the PIMULTAB keyword in the SCHEDULE section.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well productivity index multiplier versus water cut table, PIMULTAB, is being assigned. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"PIMULTAB","description":"A positive integer value that defines the corresponding PIMULTAB table to be allocated to the well. A value less than or equal to zero means that no PIMULTAB table is allocated to the well","units":{},"default":"0","value_type":"DOUBLE"}],"example":"Given NTPIMT equals two on the PIMTDIMS keyword in the RUNSPEC section, then:\n--\n-- ASSIGN WELL PRODUCTIVITY INDEX VS WATER CUT TABLE\n--\n-- WELL PI\n-- NAME TABLE\nWPITAB\nOP01 1 /\nOP02 1 /\nOP03 2 /\n/\nAssigns PIMULTAB table one to wells OP01 and OP02 and table two to OP03.","expected_columns":2,"size_kind":"list"},"WPLUG":{"name":"WPLUG","sections":["SCHEDULE"],"supported":false,"summary":"Various keywords in the SCHEDULE section (WECON, GECON etc.) allow for a well to be automatically plugged back if the well violates a constraint, that is to close existing perforations (well connections). For example if the water cut exceeds 90%, then plug back the well. The WPLUG keyword defines for automatic plug backs the length of the perforations (length of connections) to be closed each time an automatic plug back is performed, together with various options on how the workover should be performed, top down, bottom up, etc.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"LENGTH_TOP","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":3,"name":"LENGTH_BOTTOM","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":4,"name":"SOURCE","description":"","units":{},"default":"WELL","value_type":"STRING"}],"example":"","expected_columns":4,"size_kind":"list"},"WPMITAB":{"name":"WPMITAB","sections":["SCHEDULE"],"supported":null,"summary":"The WPMITAB keyword assigns the well polymer molecular injection tables to water injection wells in OPM Flow's Polymer Molecular Weight Transport option, that uses the polymer molecular weight in calculating the polymer viscosity, as well as accounting for formation damage due to the water and polymer injection, by adjusting the wellbore skin pressure. This keyword should only be used if the POLYMER and POLYMW keywords in the RUNSPEC section are also activated. The keyword assigns the PLYMWINJ tables that are defined via the PLYMWINJ keyword in the PROPS section.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length, that defines the water injection well name, for which the well polymer molecular injection table, PLYMWINJ, is to be assigned. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"PLYMWINJ","description":"A positive integer value that defines the corresponding PLYMWINJ table to be allocated to the water injection well. A value less than or equal to zero means that no PLYMWIN table is allocated to the well","units":{},"default":"0","value_type":"INT"}],"example":"Given NTPMWINJ equals two on the PINTDIMS keyword in the RUNSPEC section, then:\n--\n-- ASSIGN WELL POLYMER MOLECULAR MODEL INJECTION TABLES\n--\n-- WELL PLYMWINJ\n-- NAME TABLE\nWPMITAB\nWI01 1 /\nWI02 1 /\nWI03 2 /\n/\nAssigns PLYMWINJ table one to wells WI01 and WI02 and table two to WI03.\n| Note This is an OPM Flow specific keyword that employs an alternative polymer flood model based on a Polymer Molecular Weight Transport equation, that is not available in the commercial simulator. |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":2,"size_kind":"list"},"WPOLYMER":{"name":"WPOLYMER","sections":["SCHEDULE"],"supported":false,"summary":"The WPOLYMER keyword defines a water injection well’s polymer and salt injection stream concentrations that are to be used for when the polymer and salt options have been activated by the POLYMER and BRINE keywords in the RUNSPEC section.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well connection data is being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"POLCON","description":"A real positive value that defines the polymer concentration of the well’s injection stream. This value may be specified using a User Defined Argument (UDA).","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None","value_type":"UDA","dimension":"Concentration"},{"index":3,"name":"SALTCON","description":"A real positive value that defines the salt concentration of the well’s injection stream. This value may be specified using a User Defined Argument (UDA). This keyword is not supported by OPM Flow but has no effect on the results so it will be ignored.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None","value_type":"UDA","dimension":"Concentration"},{"index":4,"name":"GRPPOL","description":"A character string of up to eight characters in length that defines the group name for which the group’s produced polymer concentration should be used instead of the well’s POLCON value stated on this keyword.","units":{},"default":"None","value_type":"STRING"},{"index":5,"name":"GRPSALT","description":"A character string of up to eight characters in length that defines the group name for which the group’s produced salt concentration should be used instead of the well’s SALTCON value stated on this keyword. This keyword is not supported by OPM Flow but has no effect on the results so it will be ignored.","units":{},"default":"None","value_type":"STRING"}],"example":"The following example defines the polymer and salt injection stream concentrations for three water injection wells for when the polymer option has been activated by the POLYMER keyword in the RUNSPEC section.\n--\n-- DEFINE WATER INJECTION WELL POLYMER AND SALT CONCENTRATIONS\n--\n-- WELL POLYMER SALT POLYMER SALT\n-- NAME POLCON SALTCON GROUP GROUP\n-- ------- -------- -------- --------\nWPOLYMER\nWI01 0.2500 /\nWI02 1* 1* GRPINJ1 /\nWI03 0.2500 1* GRPINJ1 /\n/\nThe polymer concentration for well WI01 is set to 0.25 and the stated polymer concentration for well WI02 will be ignored, as both WI02 and WI03 will re-inject the produced polymer from the GRPINJ1 group.","expected_columns":5,"size_kind":"list"},"WPOLYRED":{"name":"WPOLYRED","sections":["SCHEDULE"],"supported":false,"summary":"The WPOLYRED keyword defines the polymer-water reduction factor for injection wells, for when the polymer phase has been activated by the POLYMER keyword in the RUNSPEC section. WPOLYRED should be set to a value greater than or equal to zero and less than or equal to one that determines the injection mixture’s viscosity. A value of zero indicates for pure water injection and a value of one will use the simulator’s valuated mixture viscosity. A value between zero and one will use an interpolated mixture viscosity.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"POLYMER_VISCOSITY_RED","description":"","units":{},"default":"1","value_type":"DOUBLE"}],"example":"","expected_columns":2,"size_kind":"list"},"WREGROUP":{"name":"WREGROUP","sections":["SCHEDULE"],"supported":false,"summary":"WREGROUP defines the criteria to automatically re-assign wells to various other groups. This can be used, for example, to move wells on THP control flowing through a high pressure separator group to a low pressure separator group in order for the wells to be under different group controls for low pressure wells.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"QUANTITY","description":"","units":{},"default":" ","value_type":"STRING"},{"index":3,"name":"GROUP_UPPER","description":"","units":{},"default":"","value_type":"STRING"},{"index":4,"name":"UPPER_LIMIT","description":"","units":{},"default":"1e+20","value_type":"DOUBLE"},{"index":5,"name":"GROUP_LOWER","description":"","units":{},"default":"","value_type":"STRING"},{"index":6,"name":"LOWER_LIMIT","description":"","units":{},"default":"0","value_type":"DOUBLE"}],"example":"","expected_columns":6,"size_kind":"list"},"WRFT":{"name":"WRFT","sections":["SCHEDULE"],"supported":null,"summary":"This keyword activates reporting of a well’s pressure and saturation profile versus depth for the connected grid blocks, to the RFT file for the requested wells at the time the keyword is activated. Data written out by OPM Flow is used to match the field measured data collected from a Repeat Formation Tester (“RFT”) tool.","parameters":[{"index":1,"name":"WELNAME","description":"A columnar vector of character strings of up to eight characters in length for each item, that defines the well name for which the RFT data should be written to the RFT file. Note that the WELNAME must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur. If the WELNAME is left blank then the data is written out for all wells at the time they are first opened to flow. If the WELNAME is given, then the RFT data for the well at the time step the keyword is invoked is written out.","units":{},"default":"None","value_type":"STRING"}],"example":"The first example activates RFT reporting for all wells at the time a well is first opened to flow:\n--\n-- ACTIVATE WELL RFT REPORTING TO THE RFT FILE\n--\n-- WELL\n-- NAME\nWRFT\n/\nIdeally, this version of the keyword should be place at the beginning of the SCHEDULE section to obtain the data for the wells in the run before they are opened up through time.\nThe next example shows how to use the keyword to request the output for several wells at different reporting time steps.\n-- ------------------------------------------------------------------------------\n-- 01 JAN 2000 START OF SCHEDULE SECTION\n-- ------------------------------------------------------------------------------\nDATES\n15 JAN 2000 /\n/\n--\n-- WELL HISTORICAL PRODUCTION CONTROLS\n--\n-- WELL OPEN/ CNTL OIL WAT GAS VFP VFP THP BHP\n-- NAME SHUT MODE RATE RATE RATE TABLE ALFQ PRES PRES\nWCONHIST OP01 OPEN ORAT 15.5E3 0.0 1550 10 1* 900.0 1* /\nOP02 SHUT /\n/\n--\n-- ACTIVATE WELL RFT REPORTING TO THE RFT FILE\n--\n-- WELL\n-- NAME\nWRFT\nOP01 /\nOP02 /\n/\nDATES\n01 FEB 2000 /\n/\n--\n-- WELL HISTORICAL PRODUCTION CONTROLS\n--\n-- WELL OPEN/ CNTL OIL WAT GAS VFP VFP THP BHP\n-- NAME SHUT MODE RATE RATE RATE TABLE ALFQ PRES PRES\nWCONHIST OP01 OPEN ORAT 15.5E3 0.0 1550 10 1* 900.0 1* /\nOP02 SHUT /\n/ --\n-- ACTIVATE WELL RFT REPORTING TO THE RFT FILE\n--\n-- WELL\n-- NAME\nWRFT\nOP01 /\nOP02 /\n/\nDATES\n01 MAR 2000 /\n/\n--\n-- WELL HISTORICAL PRODUCTION CONTROLS\n--\n-- WELL OPEN/ CNTL OIL WAT GAS VFP VFP THP BHP\n-- NAME SHUT MODE RATE RATE RATE TABLE ALFQ PRES PRES\nWCONHIST OP01 OPEN ORAT 15.5E3 0.0 1550 10 1* 900.0 1* /\nOP02 OPEN ORAT 10.5E3 0.0 1000 10 1* 900.0 1* /\n/\nIn this example, both well’s have their RFT written out on February 1 and March 1 2000.","expected_columns":1,"size_kind":"list"},"WRFTPLT":{"name":"WRFTPLT","sections":["SCHEDULE"],"supported":null,"summary":"This keyword activates reporting of a well’s depth pressure and fluid rates profile to the RFT file for the requested wells at the time the keyword is activated. Data written out by the simulator is used to match the field measured data collected from both the Repeat Formation Tester (“RFT”) tool and various Production Logging Tools (“PLT”).","parameters":[{"index":1,"name":"WELNAME","description":"A columnar vector of character strings of up to eight characters in length for each item, that defines the well name for which the RFT data should be written to the RFT file. Note that the WELNAME must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur. If the WELNAME is left blank then the data is written out for all wells at the time they are first opened to flow. If the WELNAME is given, then the RFT data for the well at the time step the keyword is invoked is written out.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"RFT","description":"A defined character string that sets the RFT data set output options and should be set to one of the following character strings. NO: do not write RFT data for the well. YES: write out the RFT data at the current reporting time step. REPT: write out the RFT data at the current reporting time step and all subsequent reporting time steps. TIMESTEP: write out the RFT data at the current reporting time step and all subsequent time steps. FOPN: write out the RFT data at the current reporting time step for the well if it is opened, otherwise write the RFT data out the first time the named well is opened.","units":{},"default":"NO","value_type":"STRING","options":["NO","YES","REPT","TIMESTEP","FOPN"]},{"index":3,"name":"PLT","description":"A defined character string that sets the PLT data set output options and should be set to one of the following character strings. NO: do not write PLT data for the well. YES: write out the PLT data at the current reporting time step. REPT: write out the PLT data at the current reporting time step and all subsequent reporting time steps. TIMESTEP: write out the PLT data at the current reporting time step and all subsequent time steps.","units":{},"default":"NO","value_type":"STRING","options":["NO","YES","REPT","TIMESTEP"]},{"index":4,"name":"MULTISEG","description":"A defined character string that sets the output options for multi-segment wells, that is the flow rates and pressures through each well segment, and should be set to one of the following character strings. NO: do not write multi-segment well data for the well. YES: write out the multi-segment well data at the current reporting time step. REPT: write out the multi-segment well data at the current reporting time step and all subsequent reporting time steps. TIMESTEP: write out the multi-segment well data at the current reporting time step and all subsequent time steps. Note the commercial simulator also uses MULTISEG to control the output of “rivers” for when the RIVERS Model has been enabled via the RIVRDIMS keyword in the RUNSPEC section. OPM Flow does not support the RIVERS Model.","units":{},"default":"NO","value_type":"STRING","options":["NO","YES","REPT","TIMESTEP"]}],"example":"The first example activates RFT output at the current reporting time step for all the wells that are opened to flow, otherwise the RFT data is written out the first time a well is opened.\n--\n-- WELL RFT, PLT AND SEGMENT DATA\n--\n-- WELL RFT PLT SEGMENT\n-- NAME DATA DATA DATA\nWRFTPLT\n'*' FOPN /\n/\nThe next example writes out the RFT and PLT data for two wells at the current reporting time step.\n--\n-- WELL RFT, PLT AND SEGMENT DATA\n--\n-- WELL RFT PLT SEGMENT\n-- NAME DATA DATA DATA\nWRFTPLT\nOP01 YES YES /\nOP02 YES YES /\n/\nThe final example is shown below:\n--\n-- WELL RFT, PLT AND SEGMENT DATA\n--\n-- WELL RFT PLT SEGMENT\n-- NAME DATA DATA DATA\nWRFTPLT\nOP01 REPT NO /\nOP02 NO YES /\n/\nIn this case the RFT data for well OP01 is written out at the current reporting time step and all subsequent reporting time steps. For well OP02, no RFT is written out but the PLT data is written out for the current report time step only.","expected_columns":4,"size_kind":"list"},"WSALT":{"name":"WSALT","sections":["SCHEDULE"],"supported":true,"summary":"The WSALT keyword defines a water injection well’s salt injection stream concentration that is to be used for when the salt option has been activated by the BRINE keywords in the RUNSPEC section. Note that if the Polymer option has also been activated by the POLYMER keyword in the RUNSPEC section, then the WPOLYMER keyword in the SCHEDULE section should be used to enter both the polymer and salt concentrations.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the injection salt concentrations are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"SALTCON","description":"A real positive vector of values that defines the salt concentration of the well’s injection stream and consists of: If the Standard Brine model has been invoked by the BRINE keyword, then SALTCON consist of one value representing the injection salt concentration; If OPM Flow’s Water Vaporization and Salt Precipitation models have been activated by the VAPWAT and PRECSALT keywords in the RUNSPEC section, then SALTCON consist of one value representing the injection salt concentration; or, If the Multi-Component Brine option has been activated by the BRINE and ECLMC keywords in the RUNSPEC section, then SALTCON consists of a vector of values representing the salt concentration of each brine within the injected brine mixture. Only options (1) and (2) are currently supported. This value may be specified using a User Defined Argument (UDA). Note if SALTCON is defaulted (1*) then the well’s salt concentration will be equal to the well’s group salt concentration.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"1*","value_type":"UDA","dimension":"Concentration"}],"example":"The following example defines the salt injection stream concentration for three water injection wells for when the brine phase has been activated by the BRINE keyword in the RUNSPEC section.\n--\n-- DEFINE WATER INJECTION WELL SALT CONCENTRATIONS (STANDARD)\n--\n-- WELL SALT-1 SALT-2 SALT-3 SALT-4\n-- NAME SALTCON SALTCON SALTCON SALTCON\n-- ------- ------- ------- -------\nWSALT\nWI01 0.2500 /\nWI02 1* /\nWI03 0.2500 /\n/\nThe salt concentration for both well WI01 and WI03 is set to 0.25, and for well WI02 the salt concentration will be taken from the well’s group salt concentration.\nThe next example is based on using the Multi-Component Brine option, that is the BRINE and ECLMC keywords have been used in the RUNSPEC section, and assuming three salts.\n--\n-- DEFINE WATER INJECTION WELL SALT CONCENTRATIONS (MULTIPLE)\n--\n-- WELL SALT-1 SALT-2 SALT-3 SALT-4\n-- NAME SALTCON SALTCON SALTCON SALTCON\n-- ------- ------- ------- -------\nWSALT\nWI01 0.1500 0.0500 0.0500 /\nWI02 0.1500 0.0500 0.0500 /\nWI03 0.2000 0.0500 0.0600 /\n/\nHere the salt concentrations for both well WI01 and WI02 are set to 0.1500, 0.0500, 0.0500 for the three salts and for well WI03 the salt concentrations are 0.2000, 0.0500 and 0.0600.\nNote that OPM Flow does not currently support the Multi-Component brine model.","expected_columns":2,"size_kind":"list"},"WSCCLEAN":{"name":"WSCCLEAN","sections":["SCHEDULE"],"supported":false,"summary":"The WSCCLEAN keyword adjusts the amount of scale currently accumulated around a well’s well connections for wells located in the global grid. For example, if a workover has been performed on a well to remove (or reduce) the deposited scale over the perforations, then this keyword can be used to implement the effects of the workover. Scale deposits reduce the productivity of well and this relationship is defined in the SCDPTAB and SCDATAB keywords in SCHEDULE section. The tables are allocated to a well via the WSCTAB keyword, which is also in the SCHEDULE section. Note that the Scale Deposition option must have been activated by declaring the dimensions of the scaling deposition tables using the SCDPDIMS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"SCALE_MULTIPLIER","description":"","units":{},"default":"1","value_type":"DOUBLE"},{"index":3,"name":"I","description":"","units":{},"default":"-1","value_type":"INT"},{"index":4,"name":"J","description":"","units":{},"default":"-1","value_type":"INT"},{"index":5,"name":"K","description":"","units":{},"default":"-1","value_type":"INT"},{"index":6,"name":"C1","description":"","units":{},"default":"-1","value_type":"INT"},{"index":7,"name":"C2","description":"","units":{},"default":"-1","value_type":"INT"}],"example":"","expected_columns":7,"size_kind":"list"},"WSCCLENL":{"name":"WSCCLENL","sections":["SCHEDULE"],"supported":false,"summary":"The WSCCLENL keyword adjusts the amount of scale currently accumulated around a well’s well connections for wells located in a Local Grid Refinement (\"LGR\"). For example, if a workover has been performed on a well to remove (or reduce) the deposited scale over the perforations, then this keyword can be used to implement the effects of the workover. Scale deposits reduce the productivity of well and this relationship is defined in the SCDPTAB and SCDATAB keywords in SCHEDULE section. The tables are allocated to a well via the WSCTAB keyword, which is also in the SCHEDULE section. Note that the Scale Deposition option must have been activated by declaring the dimensions of the scaling deposition tables using the SCDPDIMS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"SCALE_MULTIPLIER","description":"","units":{},"default":"1","value_type":"DOUBLE"},{"index":3,"name":"LGR","description":"","units":{},"default":"","value_type":"STRING"},{"index":4,"name":"I","description":"","units":{},"default":"-1","value_type":"INT"},{"index":5,"name":"J","description":"","units":{},"default":"-1","value_type":"INT"},{"index":6,"name":"K","description":"","units":{},"default":"-1","value_type":"INT"},{"index":7,"name":"C1","description":"","units":{},"default":"-1","value_type":"INT"},{"index":8,"name":"C2","description":"","units":{},"default":"-1","value_type":"INT"}],"example":"","expected_columns":8,"size_kind":"list"},"WSCTAB":{"name":"WSCTAB","sections":["SCHEDULE"],"supported":false,"summary":"WSCTAB assigns scale deposition and scale damage tables to a well, for when the Scale Deposition option has been activated by declaring the dimensions of the scaling deposition tables using the SCDPDIMS keyword in the RUNSPEC section. Scale deposits reduce the productivity of well and this relationship is defined in the SCDPTAB and SCDATAB keywords in the SCHEDULE section, and are allocated to a well by the WSCTAB keyword.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"SCALE_DEPOSITION_TABLE","description":"","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"SCALE_DAMAGE_TABLE","description":"","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"UNUSED","description":"","units":{},"default":"","value_type":"STRING"},{"index":5,"name":"SCALE_DISSOLUTION_TABLE","description":"","units":{},"default":"0","value_type":"INT"}],"example":"","expected_columns":5,"size_kind":"list"},"WSEGAICD":{"name":"WSEGAICD","sections":["SCHEDULE"],"supported":null,"summary":"The WSEGAICD keyword defines a multi-segment well segment to be an autonomous Inflow Control Device (“ICD”) as part of a completion for a multi-segment well. Note that the well must have been previously defined by the WELSPECS and WELSEGS keywords in the SCHEDULE section and that the data for the keyword should be repeated for each multi-segment completion that contains an autonomous ICD.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which a multi-segment well is being defined. Note that the well name (WELNAME) must have been declared previously using both the WELSPECS and WELSEGS keywords in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"ISEG1","description":"An integer greater than or equal to two and less than or equal to MXSEGS on the WSEGDIMS keyword in the RUNSPEC section that defines the start of the segment range.","units":{},"default":"None","value_type":"INT"},{"index":3,"name":"ISEG2","description":"An integer greater than or equal to two and not less then ISEG1 on this record and less than or equal to MXSEGS on the WSEGDIMS keyword in the RUNSPEC section, that defines the end of the segment range.","units":{},"default":"None","value_type":"INT"},{"index":4,"name":"ICDSTREN","description":"A positive real value that defines an empirical constant for the strength of the given ICD as determined from measurements using the calibrated fluid.","units":{"field":"psi/((lb/ft3)(rft3/day)2)","metric":"bars/((kg/m3)(rm3/day)2)","laboratory":"atm/((gm/cc)(rcc/hr)2)"},"default":"None","value_type":"DOUBLE","dimension":"Pressure*Time*Time/GeometricVolume*GeometricVolume*Density"},{"index":5,"name":"ICDLEN","description":"A real value that defines the length of the ICD used in conjunction with NSCALFAC to calculate a scaling factor to be applied to the reservoir flow to adjust the flow through each ICD, that is: If NSCALFAC equals zero: then the scale factor is equal to the length of the ICD (ICDLEN) divided by the length of the tubing section, that is the parent of the ICDs, then this allows for the case when the ICD segment may represent a number of ICDs in parallel. If NSCALFAC equals one: then the scale factor is equal to the absolute value of ICDLEN. If NSCALFAC equals two: then the scale factor is equal to the length of ICDLEN, divided by the total length of the completions which supply the ICD. NSCALFAC explicitly sets which of the above three options is used. If NSCALFAC is defaulted, then option 1) is used whenever ICDLEN is positive and option 2) when ICDLEN is negative.","units":{"field":"feet 39.37","metric":"m 12.00","laboratory":"cm 1,2000"},"default":"Defined","value_type":"DOUBLE","dimension":"Length"},{"index":6,"name":"CALDEN","description":"A positive real value that defines the density of the calibrating fluid at surface conditions.","units":{"field":"lb/ft3 62.416","metric":"kg/m3 1000.25","laboratory":"gm/cc 1.00025"},"default":"Defined","value_type":"DOUBLE","dimension":"Density"},{"index":7,"name":"CALVISC","description":"A positive real value that defines the viscosity of the calibrating fluid at surface conditions.","units":{"field":"cP","metric":"cP","laboratory":"cP"},"default":"1.45","value_type":"DOUBLE","dimension":"Viscosity"},{"index":8,"name":"EMLCRT","description":"A positive real value that defines the “local water” in liquid fraction used to determine whether the “water-in-oil” or “oil-in-water” emulsion viscosity equation should be applied.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.5","value_type":"DOUBLE","dimension":"1"},{"index":9,"name":"EMLTRANS","description":"A positive real value that defines the width of the transition zone around EMLCRT and is used to ensure that the calculated viscosity forms a continuous function of water in liquid fraction. Within this region, the emulsion viscosity is a linear interpolation between the “water-in-oil” and “oil-in-water” viscosity values either side of the region.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.05","value_type":"DOUBLE","dimension":"1"},{"index":10,"name":"EMLMAX","description":"A positive real value that defines the maximum emulsion viscosity to continuous phase viscosity (oil or water) ratio.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"5.0","value_type":"DOUBLE","dimension":"1"},{"index":11,"name":"NSCALFAC","description":"An integer value greater than or equal to zero, that specifies the method to be used when applying the scaling factor and should be set to one of the following: If NSCALFAC equals zero: then the scale factor is equal to the length of the ICD (ICDLEN) divided by the length of the tubing section, that is the parent of the ICDs, then this allows for the case when the ICD segment may represent a number of ICDs in parallel. If NSCALFAC equals one: then the scale factor is equal to the absolute value of ICDLEN. If NSCALFAC equals two: then the scale factor is equal to the length of ICDLEN, divided by the total length of the completions which supply the ICD. NSCALFAC explicitly sets which of the above three options is used. If NSCALFAC is negative, then option 1) is used whenever ICDLEN is positive and option 2) when ICDLEN is negative.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"-1","value_type":"INT"},{"index":12,"name":"CALRATE","description":"A positive real value that defines the maximum surface flow rate for which the ICD was calibrated. Values calculated greater than CALRATE will use linear extrapolation.","units":{"field":"scf/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"None","value_type":"DOUBLE","dimension":"GeometricVolume/Time"},{"index":13,"name":"RATEXP","description":"A real value greater than or equal to zero that defines the flow rate exponent in equation (12.35).","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE"},{"index":14,"name":"VISCEXP","description":"A real value that defines the viscosity exponent in equation (12.35).","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE"},{"index":15,"name":"STATUS","description":"A defined character string that specifies the ICD’s operational status, STATUS should be set to one of the following character strings: OPEN: the ICD connections are open to flow. SHUT: the ICD connections are closed to flow (shut-in).","units":{},"default":"OPEN","value_type":"STRING","options":["OPEN","SHUT"]},{"index":16,"name":"A1","description":"A real value that defines the density mixture OIL flowing fraction exponent in equation (12.36)","units":{},"default":"1.0","value_type":"DOUBLE"},{"index":17,"name":"A2","description":"A real value that defines the density mixture WATER flowing fraction exponent in equation (12.36)","units":{},"default":"1.0","value_type":"DOUBLE"},{"index":18,"name":"A3","description":"A real value that defines the density mixture GAS flowing fraction exponent in equation (12.36)","units":{},"default":"1.0","value_type":"DOUBLE"},{"index":19,"name":"B1","description":"A real value that defines the viscosity mixture OIL flowing fraction exponent in equation (12.37)","units":{},"default":"1.0","value_type":"DOUBLE"},{"index":20,"name":"B2","description":"A real value that defines the viscosity mixture WATER flowing fraction exponent in equation (12.37)","units":{},"default":"1.0","value_type":"DOUBLE"},{"index":21,"name":"B3","description":"A real value that defines the viscosity mixture GAS flowing fraction exponent in equation (12.37)","units":{},"default":"1.0","value_type":"DOUBLE"},{"index":22,"name":"DENEXP","description":"A real value that defines the density exponent in equation (12.35).","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0","value_type":"DOUBLE"}],"example":"The following example defines a multi-segment oil production well (OP01) using the WELSPECS, WELSEGS COMPDAT and COMPSEGS keywords, followed by the WSEGAICD keyword to define the autonomous inflow control devices for the well.\n--\n-- WELL SPECIFICATION DATA\n--\n-- WELL GROUP LOCATION BHP PHASE DRAIN INFLOW OPEN CROSS PVT DEN FIP\n-- NAME NAME I J DEPTH FLUID AREA EQUANS SHUT FLOW TABLE CAL NUM\nWELSPECS\nOP01 PLATFORM 14 8 1* OIL 0.0 STD SHUT YES 0 SEG 0 /\n/\n--\n-- WELL CONNECTION DATA\n--\n-- WELL --- LOCATION --- OPEN SAT CONN WELL KH SKIN D DIR\n-- NAME II JJ K1 K2 SHUT TAB FACT DIA FACT FACT FACT PEN\nCOMPDAT\nOP01 14 8 1 1 OPEN 1* 1.972960E+2 0.216 1* 0.00 1* 'Z' /\nOP01 14 7 1 1 OPEN 1* 1.619450E+2 0.216 1* 0.00 1* 'Z' /\nOP01 14 7 2 2 OPEN 1* 4.126449E+2 0.216 1* 0.00 1* 'Z' /\nOP01 14 7 3 3 OPEN 1* 2.033290E+1 0.216 1* 0.00 1* 'Z' /\nOP01 15 7 3 3 OPEN 1* 9.095613E+1 0.216 1* 0.00 1* 'Z' /\nOP01 15 6 3 3 OPEN 1* 2.090607E+2 0.216 1* 0.00 1* 'Y' /\nOP01 15 6 4 4 OPEN 1* 3.010669E+1 0.216 1* 0.00 1* 'Y' /\nOP01 16 6 4 4 OPEN 1* 7.123814E+1 0.216 1* 0.00 1* 'Y' /\nOP01 16 5 4 4 OPEN 1* 4.414386E+2 0.216 1* 0.00 1* 'Y' /\nOP01 16 4 4 4 OPEN 1* 4.345126E+2 0.216 1* 0.00 1* 'Y' /\nOP01 16 3 4 4 OPEN 1* 2.894573E+2 0.216 1* 0.00 1* 'Y' /\nOP01 17 3 4 4 OPEN 1* 1.329523E+2 0.216 1* 0.00 1* 'Y' /\nOP01 17 2 4 4 OPEN 1* 6.981252E+1 0.216 1* 0.00 1* 'Y' /\nOP01 17 2 5 5 OPEN 1* 1.392382E+2 0.216 1* 0.00 1* 'Y' /\n/\n--\n-- WELL SEGMENT SPECIFICATION DATA\n--\n-- WELL NODAL LEN WELL DEPH PRESS FLOW\n-- NAME DEPTH TUBING VOLM OPTN CALC MODEL\nWELSEGS\nOP01 2041.56259 0.0000 1* INC 'HF-' /\n--\n-- SEG SEG BRAN SEG TUBING NODAL TUBE TUBE XSEC VOL\n-- ISTR IEND NO NO LENGTH DEPTH ID ROUGH AREA SEG\n2 2 1 1 9.56005 0.61168 0.152 0.0000100 /\n3 3 1 2 17.40714 1.11376 0.152 0.0000100 /\n4 4 1 3 41.24996 2.38255 0.152 0.0000100 /\n5 5 1 4 38.35922 2.06899 0.152 0.0000100 /\n6 6 1 5 27.13029 1.02248 0.152 0.0000100 /\n7 7 1 6 73.45099 2.40389 0.152 0.0000100 /\n8 8 1 7 54.95304 1.64832 0.152 0.0000100 /\n9 9 1 8 12.37381 0.23781 0.152 0.0000100 /\n10 10 1 9 62.61459 0.73403 0.152 0.0000100 /\n11 11 1 10 106.9805 1.37749 0.152 0.0000100 /\n12 12 1 11 88.42739 0.90931 0.152 0.0000100 /\n13 13 1 12 51.59899 0.27327 0.152 0.0000100 /\n14 14 1 13 24.75582 0.30814 0.152 0.0000100 /\n15 15 1 14 29.77334 0.49371 0.152 0.0000100 /\n--\n-- PERFORATION VALVE SEGMENTS\n--\n-- SEG SEG BRAN SEG TUBING NODAL TUBE TUBE XSEC VOL\n-- ISTR IEND NO NO LENGTH DEPTH ID ROUGH AREA SEG\n16 16 2 2 0.10000 0 0.152 0.0000100 /\n17 17 3 3 0.10000 0 0.152 0.0000100 /\n18 18 4 4 0.10000 0 0.152 0.0000100 /\n19 19 5 5 0.10000 0 0.152 0.0000100 /\n20 20 6 6 0.10000 0 0.152 0.0000100 /\n21 21 7 7 0.10000 0 0.152 0.0000100 /\n22 22 8 8 0.10000 0 0.152 0.0000100 /\n23 23 9 9 0.10000 0 0.152 0.0000100 /\n24 24 10 10 0.10000 0 0.152 0.0000100 /\n25 25 11 11 0.10000 0 0.152 0.0000100 /\n26 26 12 12 0.10000 0 0.152 0.0000100 /\n27 27 13 13 0.10000 0 0.152 0.0000100 /\n28 28 14 14 0.10000 0 0.152 0.0000100 /\n29 29 15 15 0.10000 0 0.152 0.0000100 /\n/\n--\n-- MULTISEGMENT WELL COMPLETION SEGMENT SPECIFICATION DATA\n--\n-- WELL\n-- NAME\nCOMPSEGS\nOP01 /\n--\n-- --LOCATION-- BRAN TUBING NODAL DIR LOC MID COMP ISEG\n-- II JJ K1 NO LENGTH DEPTH PEN I,J,K PERFS LENGTH NO.\n14 8 1 2 0.000000 0.10000 /\n14 7 1 3 0.000000 0.10000 /\n14 7 2 4 0.000000 0.10000 /\n14 7 3 5 0.000000 0.10000 /\n15 7 3 6 0.000000 0.10000 /\n15 6 3 7 0.000000 0.10000 /\n15 6 4 8 0.000000 0.10000 /\n16 6 4 9 0.000000 0.10000 /\n16 5 4 10 46.76168 46.86168 /\n16 4 4 11 0.000000 0.10000 /\n16 3 4 12 0.000000 0.10000 /\n17 3 4 13 0.000000 0.10000 /\n17 2 4 14 0.000000 0.10000 /\n17 2 5 15 42.50573 42.60573 /\n/\n--\n-- MULTI-SEGMENT WELL ICD SEGMENT SPECIFICATION DATA\n--\n-- WELL SEG SEG ICD ICD CAL CAL EML EML EML SCAL CAL RATE VISC OPEN\n-- NAME ISTR IEND STREN LEN DEN VISC CRIT TRAN MAX FAC RAT EXP EXP CLOSE\nWSEGAICD\nOP01 16 16 7.5e-5 -0.028975 1020 0.48 0.7 1* 1* 1* 1* 2.2 0.5 7* /\nOP01 17 17 7.5e-5 -0.023783 1020 0.48 0.7 1* 1* 1* 1* 2.2 0.5 7* /\nOP01 18 18 7.5e-5 -0.101240 1020 0.48 0.7 1* 1* 1* 1* 2.2 ","expected_columns":22,"size_kind":"list"},"WSEGDFIN":{"name":"WSEGDFIN","sections":["SCHEDULE"],"supported":false,"summary":"The WSEGDFIN keyword defines a multi-segment well’s drift flux slip model parameters. A slip model333\n Shi, H., Holmes, J.A., Durlofsky, L. J., Aziz, K., Diaz, L. R., Alkaya, B., and Oddie, G. “Drift-Flux Modeling of Two-Phase Flow in Wellbores,” paper SPE 84228, Society of Petroleum Engineers Journal (2005) 10, No. 1, 24-33; also presented as “Drift-Flux Modeling of Multiphase Flow in Wellbores,” at the SPE Annual Technical Conference and Exhibition, Denver, Colorado, USA(October 5-8, 2003). and 334\n Shi, H., Holmes, J.A., Diaz, L. R., Durlofsky, L. J., and Aziz, K. “Drift-Flux Parameters for Three-Phase Steady-State Flow in Wellbores,” paper SPE 89836, Society of Petroleum Engineers Journal(2005) 10, No. 2, 130-137; also presented at the SPE Annual Technical Conference and Exhibition, Houston, Texas, USA (September 26-29, 2004).enables the different phases in the wellbore to flow at different velocities, for example gas will flow up the tubing at a higher velocity than...","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","size_kind":"fixed","size_count":1,"variadic_record":true},"WSEGDFMD":{"name":"WSEGDFMD","sections":["SCHEDULE"],"supported":false,"summary":"The WSEGDFMD keyword defines a multi-segment well’s drift flux slip model definition that sets the type of slip model to be used. A slip model335\n Shi, H., Holmes, J.A., Durlofsky, L. J., Aziz, K., Diaz, L. R., Alkaya, B., and Oddie, G. “Drift-Flux Modeling of Two-Phase Flow in Wellbores,” paper SPE 84228, Society of Petroleum Engineers Journal (2005) 10, No. 1, 24-33; also presented as “Drift-Flux Modeling of Multiphase Flow in Wellbores,” at the SPE Annual Technical Conference and Exhibition, Denver, Colorado, USA(October 5-8, 2003). and 336\n Shi, H., Holmes, J.A., Diaz, L. R., Durlofsky, L. J., and Aziz, K. “Drift-Flux Parameters for Three-Phase Steady-State Flow in Wellbores,” paper SPE 89836, Society of Petroleum Engineers Journal(2005) 10, No. 2, 130-137; also presented at the SPE Annual Technical Conference and Exhibition, Houston, Texas, USA (September 26-29, 2004).enables the different phases in the wellbore to flow at different velocities, for example gas will f...","parameters":[{"index":1,"name":"DRIFT_MODEL","description":"","units":{},"default":"ORIGINAL","value_type":"STRING"},{"index":2,"name":"INCLINATION_FACTOR","description":"","units":{},"default":"H-K","value_type":"STRING"},{"index":3,"name":"GAS_EFFECT","description":"","units":{},"default":"NO","value_type":"STRING"}],"example":"","expected_columns":3,"size_kind":"fixed","size_count":1},"WSEGDFPA":{"name":"WSEGDFPA","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, WSEGDFPA, enables modification of a multi-segment well’s drift flux slip model default parameters used by the WSEGDFMA keyword in the SCHEDULE section to define the model. A slip model337\n Shi, H., Holmes, J.A., Durlofsky, L. J., Aziz, K., Diaz, L. R., Alkaya, B., and Oddie, G. “Drift-Flux Modeling of Two-Phase Flow in Wellbores,” paper SPE 84228, Society of Petroleum Engineers Journal (2005) 10, No. 1, 24-33; also presented as “Drift-Flux Modeling of Multiphase Flow in Wellbores,” at the SPE Annual Technical Conference and Exhibition, Denver, Colorado, USA(October 5-8, 2003). and 338\n Shi, H., Holmes, J.A., Diaz, L. R., Durlofsky, L. J., and Aziz, K. “Drift-Flux Parameters for Three-Phase Steady-State Flow in Wellbores,” paper SPE 89836, Society of Petroleum Engineers Journal(2005) 10, No. 2, 130-137; also presented at the SPE Annual Technical Conference and Exhibition, Houston, Texas, USA (September 26-29, 2004).enables the different phases in the wellbore...","parameters":[{"index":1,"name":"GAS_LIQUID_VD_FACTOR","description":"","units":{},"default":"1","value_type":"DOUBLE"},{"index":2,"name":"A1","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":3,"name":"A2","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":4,"name":"C0_A","description":"","units":{},"default":"1.2","value_type":"DOUBLE"},{"index":5,"name":"C0_B","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":6,"name":"FV","description":"","units":{},"default":"1","value_type":"DOUBLE"},{"index":7,"name":"OIL_WATER_VD_FACTOR","description":"","units":{},"default":"-1","value_type":"DOUBLE"},{"index":8,"name":"A","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":9,"name":"B1","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":10,"name":"B2","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":11,"name":"N","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","expected_columns":11,"size_kind":"fixed","size_count":1},"WSEGEXSS":{"name":"WSEGEXSS","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, WSEGEXSS, enables the import or export of fluids from a segment in a multi-segment well. This can be used to, for example, model gas lift injection for oil wells under artificial lift, or to approximate the behavior of a down-hole separator. The import-export fluid volumes can either be expressed as rates or defined as a function of a segment’s pressure value.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"SEGMENT","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"TYPE","description":"","units":{},"default":"NONE","value_type":"STRING"},{"index":4,"name":"GAS_IMPORT_RATE","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"GasSurfaceVolume/Time"},{"index":5,"name":"R","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time*Pressure"},{"index":6,"name":"PEXT","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Pressure"}],"example":"","expected_columns":6,"size_kind":"list"},"WSEGFLIM":{"name":"WSEGFLIM","sections":["SCHEDULE"],"supported":false,"summary":"WSEGFLIM enables an artificial choke that chokes a given phase flow rate for a segment in a multi-segment well. This can be used, for example, to constraint unwanted production phase through a section of tubing, or to model a down-hole choke. The keyword provides coefficients that are applied to the frictional pressure drop across a multi-segment well’s segment in order to inhibit production from that particular zone or segment. As such, the keyword does not actually model a down-hole choke; hence, the term artificial.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"SEGMENT1","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"SEGMENT2","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"LIMITED_PHASE1","description":"","units":{},"default":"NONE","value_type":"STRING"},{"index":5,"name":"FLOW_LIMIT1","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time"},{"index":6,"name":"A1","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":7,"name":"LIMITED_PHASE2","description":"","units":{},"default":"NONE","value_type":"STRING"},{"index":8,"name":"FLOW_LIMIT2","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time"},{"index":9,"name":"A2","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":10,"name":"STATUS","description":"","units":{},"default":"OPEN","value_type":"STRING"}],"example":"","expected_columns":10,"size_kind":"list"},"WSEGFMOD":{"name":"WSEGFMOD","sections":["SCHEDULE"],"supported":false,"summary":"The WSEGFMOD declares the multi-phase flow model to be used to calculate the pressure drop within an individual segment for multi-segment wells. The FLOWOPT parameter on the WELSEGS keyword in the SCHEDULE section sets the default multi-segment well model. FLOWOPT is a character string that can be set to HO that activates the homogeneous model, that is all phases flow at the same velocity, or DF that invokes the Drift Flux Slip model (note OPM Flow only supports the default value of HO for the homogeneous model). Here WSEGFMOD can be used to set the flow model for a segment to either the homogeneous model or the Drift Flux Slip model, and addition a: VLP table allocated via the WSEGTABL keyword, or a specific model as defined by the WSEGVALV, WSEGFLIM and WSEGLABY keywords. All the aforementioned keywords are in the SCHEDULE section.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"SEGMENT1","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"SEGMENT2","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"FLOW_MODEL","description":"","units":{},"default":"HO","value_type":"STRING"},{"index":5,"name":"GAS_LIQUID_VD_FACTOR","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":6,"name":"A","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":7,"name":"B","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":8,"name":"FV","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":9,"name":"B1","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":10,"name":"B2","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","expected_columns":10,"size_kind":"list"},"WSEGINIT":{"name":"WSEGINIT","sections":["SCHEDULE"],"supported":false,"summary":"Normally the simulator calculates the initial conditions for multi-segment wells, that is the pressure and fluid distributions in each segment. However, there are occasions when manually setting the pressures and phase distributions for each segment to investigate certain flow conditions may be useful. In this case the WSEGINIT keyword may be used to specify the initial conditions manually. Note that segments not initialized by this keyword will be automatically initialized by the simulator","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"SEGMENT1","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"SEGMENT2","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"P0","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":5,"name":"W0","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":6,"name":"G0","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":7,"name":"RS","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":8,"name":"RV","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":9,"name":"API","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":10,"name":"POLYMER","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Concentration"},{"index":11,"name":"BRINE","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Concentration"}],"example":"","expected_columns":11,"size_kind":"list"},"WSEGITER":{"name":"WSEGITER","sections":["SCHEDULE"],"supported":null,"summary":"The WSEGITER keyword defines the multi-segment well solution iteration sequence and solution controls.","parameters":[{"index":1,"name":"MAX_WELL_ITERATIONS","description":"","units":{},"default":"40","value_type":"INT"},{"index":2,"name":"MAX_TIMES_REDUCED","description":"","units":{},"default":"5","value_type":"INT"},{"index":3,"name":"REDUCTION_FACTOR","description":"","units":{},"default":"0.3","value_type":"DOUBLE"},{"index":4,"name":"INCREASING_FACTOR","description":"","units":{},"default":"2","value_type":"DOUBLE"}],"example":"","expected_columns":4,"size_kind":"fixed","size_count":1},"WSEGLABY":{"name":"WSEGLABY","sections":["SCHEDULE"],"supported":false,"summary":"The WSEGSICD keyword defines a multi-segment well segment to be a labyrinth Inflow Control Device. (“ICD”) as part of a completion for a multi-segment well. Note that the well must have been previously define by the WELSPECS and WELSEGS keywords in the SCHEDULE section and that the data for the keyword should be repeated for each multi-segment completion that contains a labyrinth ICD.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"SEGMENT1","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"SEGMENT2","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"NCONFIG","description":"","units":{},"default":"","value_type":"INT"},{"index":5,"name":"CHANNELS","description":"","units":{},"default":"2","value_type":"INT"},{"index":6,"name":"A","description":"","units":{},"default":"6e-05","value_type":"DOUBLE","dimension":"Length*Length"},{"index":7,"name":"L1","description":"","units":{},"default":"0.1863","value_type":"DOUBLE","dimension":"Length"},{"index":8,"name":"L2","description":"","units":{},"default":"0.2832","value_type":"DOUBLE","dimension":"Length"},{"index":9,"name":"D","description":"","units":{},"default":"0.006316","value_type":"DOUBLE","dimension":"Length"},{"index":10,"name":"R","description":"","units":{},"default":"1e-05","value_type":"DOUBLE","dimension":"Length"},{"index":11,"name":"GAMMA_INLET","description":"","units":{},"default":"0.35","value_type":"DOUBLE"},{"index":12,"name":"GAMMA_OUTLET","description":"","units":{},"default":"0.5","value_type":"DOUBLE"},{"index":13,"name":"GAMMA_LAB","description":"","units":{},"default":"0.5","value_type":"DOUBLE"},{"index":14,"name":"STATUS","description":"","units":{},"default":"OPEN","value_type":"STRING"}],"example":"","expected_columns":14,"size_kind":"list"},"WSEGLINK":{"name":"WSEGLINK","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, WSEGLINK, specifies multi-segment well looped flow paths as part of a completion for a multi-segment well. A looped segment results in the nodes of the two individual segments that are looped (or connected) having the same solution pressures and oil, water and gas flowing rates.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"SEGMENT1","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"SEGMENT2","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":3,"size_kind":"list"},"WSEGMULT":{"name":"WSEGMULT","sections":["SCHEDULE"],"supported":false,"summary":"WSEGMULT supplies a set of constants used to modify (or scale) a multi-segment well’s segment frictional pressure drop between connecting segments The constants enable either a constant pressure to be applied, or for the pressure drop to vary as a function of the Gas-Oil Ratio (“GOR”) or the Water-Oil Ratio (“WOR”). The simulator calculated pressure drop is multiplied by the following resulting value:","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"SEGMENT1","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"SEGMENT2","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"A","description":"","units":{},"default":"1","value_type":"DOUBLE"},{"index":5,"name":"B","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":6,"name":"C","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":7,"name":"D","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":8,"name":"E","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":9,"name":"GOR","description":"","units":{},"default":"0","value_type":"DOUBLE"}],"example":"| [Frictional`Loss` Multipler~=~min left ( x sub{1}`+`x sub{2}(WOR) sup{x sub{3}}`+`x sub{4} left( GOR over {GOR sub{min} }right) sup {x sup{5}},~ 1.0 right)] | (12.38) |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|","expected_columns":9,"size_kind":"list"},"WSEGPROP":{"name":"WSEGPROP","sections":["SCHEDULE"],"supported":false,"summary":"The WSEGPROP keyword allows for the editing of exiting multi-segment wells created by WELSEGS keyword in the SCHEDULE section without having to re-define all the information that is on the WELSEGS keyword. Note that the well must have been previously define by both the WELSPECS and WELSEGS keywords in the SCHEDULE section to use the WSEGPROP keyword.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which a multi-segment well is being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"ISEG1","description":"A positive integer greater than or equal to two and less than or equal to MXSEGS on WSEGDIMS keyword in the RUNSPEC section that defines the start of a segment","units":{},"default":"None","value_type":"INT"},{"index":3,"name":"ISEG2","description":"A positive integer greater than or equal to two and less than or equal to ISEG1 on this record and MXSEGS on the WSEGDIMS keyword in the RUNSPEC section that defines the end of a segment.","units":{},"default":"None","value_type":"INT"},{"index":4,"name":"ID","description":"A real positive value that defines the tubing internal diameter of the segment for the well.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"Previous Entered Value","value_type":"DOUBLE","dimension":"Length"},{"index":5,"name":"EPSILON","description":"A real positive value that defines the tubing absolute roughness of the segment for the well.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"Previous Entered Value","value_type":"DOUBLE","dimension":"Length"},{"index":6,"name":"XAREA","description":"XAREA is real positive value equal to or greater than zero that defines the cross sectional area for fluid flow. Currently this option is not supported by OPM Flow.","units":{"field":"ft2","metric":"m2","laboratory":"cm2"},"default":"Previous Entered Value","value_type":"DOUBLE","dimension":"Length*Length"},{"index":7,"name":"VOLSEG","description":"VOLSEG is a real positive value that defines the effective segment volume for the this segment. Currently this option is not supported by OPM Flow.","units":{"field":"ft3","metric":"m3","laboratory":"cm3"},"default":"Previous Entered Value","value_type":"DOUBLE","dimension":"Length*Length*Length"},{"index":8,"name":"XAREAS","description":"XAREAS is real positive value equal to or greater than zero that defines the cross sectional area of the pipe wall for this segment, that is used in thermal conductivity calculations for when the temperature calculation is activated by the TEMP keyword in the RUNSPEC section. Currently this option is not supported by OPM Flow.","units":{},"default":"Previous Entered Value","value_type":"DOUBLE","dimension":"Length*Length"},{"index":9,"name":"VHEATCAP","description":"VHEATCAP is real positive value equal to or greater than zero that defines the volumetric heat capacity of the pipe wall used in thermal conductivity calculations for when the temperature calculation is activated by the TEMP keyword in the RUNSPEC section. Currently this option is not supported by OPM Flow.","units":{"field":"Btu/ft/day/°R","metric":"kJ/m/day/K","laboratory":"J/cm/hr/K"},"default":"Previous Entered Value","value_type":"DOUBLE"},{"index":10,"name":"THCON","description":"THCON is real positive value equal to or greater than zero that defines the thermal conductivity of the pipe wall used in thermal conductivity calculations for when the temperature calculation is activated by the TEMP keyword in the RUNSPEC section. Currently this option is not supported by OPM Flow.","units":{"field":"Btu/ft/day/°R","metric":"kJ/m/day/K","laboratory":"J/cm/hr/K"},"default":"Previous Entered Value","value_type":"DOUBLE"}],"example":"The following example modifies two segments in well OP01 and one segment in well OP02.\n--\n-- WELL SEGMENT SPECIFICATION DATA\n--\n-- WELL SEG SEG TUBE TUBE XSEC VOL\n-- NAME ISTR IEND ID ROUGH AREA SEG\nWSEGPROP\nOPO1 12 14 0.3 0.00010 /\nOP01 13 15 0.275 0.00010 /\nOP02 14 14 0.275 0.00010 /\n/\nNote that the two multi-segment wells and their respective segments must have been previously defined by the WELSEGS keyword.","expected_columns":10,"size_kind":"list"},"WSEGPULL":{"name":"WSEGPULL","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, WSEGPULL, specifies a multi-segment well segment to be a pull-through pump for a down-hole water separator, defined by the WSEGSEP keyword in the SCHEDULE section, and defines the various parameters for this type of pump. Down-hole separators are used to separate water or free gas from the in situ fluid entering the wellbore in order to increase hydrocarbon recovery.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"SEGMENT1","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"SEGMENT2","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"P","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":5,"name":"DP","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":6,"name":"OIL_RATE_LIMIT","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Volume/Time"},{"index":7,"name":"GRADIENT_FACTOR","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Pressure*Time/Volume"}],"example":"","expected_columns":7,"size_kind":"list"},"WSEGSEP":{"name":"WSEGSEP","sections":["SCHEDULE"],"supported":false,"summary":"WSEGSEP specifies a multi-segment well segment to be a down-hole separator, that enables the separation of fluids down-hole. Down-hole separators are used to separate water or free gas from the in situ fluid entering the wellbore in order to increase hydrocarbon recovery. See also the WSEGPULL keyword in the SCHEDULE section that specifies a pull-through pump for a down-hole water separator.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"SEGMENT1","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"SEGMENT2","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"PHASE","description":"","units":{},"default":"NONE","value_type":"STRING"},{"index":5,"name":"EMAX","description":"","units":{},"default":"1","value_type":"DOUBLE"},{"index":6,"name":"HOLDUP_FRACTION","description":"","units":{},"default":"0.01","value_type":"DOUBLE"}],"example":"","expected_columns":6,"size_kind":"list"},"WSEGSICD":{"name":"WSEGSICD","sections":["SCHEDULE"],"supported":null,"summary":"The WSEGSICD keyword defines a multi-segment well segment to be a spiral Inflow Control Device (“ICD”) as part of a completion for a multi-segment well. Note that the well must have been previously defined by the WELSPECS and WELSEGS keywords in the SCHEDULE section and that the data for the keyword should be repeated for each multi-segment completion that contains a spiral ICD.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which a multi-segment well is being defined. Note that the well name (WELNAME) must have been declared previously using both the WELSPECS and WELSEGS keywords in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"ISEG1","description":"A positive integer greater than or equal to two and less than or equal to MXSEGS on the WSEGDIMS keyword in the RUNSPEC section that defines the start of a segment","units":{},"default":"None","value_type":"INT"},{"index":3,"name":"ISEG2","description":"A positive integer greater than or equal to two and not less then ISEG1 on this record and less than or equal to MXSEGS on the WSEGDIMS keyword in the RUNSPEC section, that defines the end of a segment","units":{},"default":"None","value_type":"INT"},{"index":4,"name":"ICDSTREN","description":"A real positive value greater than zero that defines an empirical constant for the strength of the given ICD as determined from measurements using the calibrated fluid.","units":{"field":"psia(rft3/day)2","metric":"barsa/(rm3/day)2","laboratory":"atma/(rcc/hr)2"},"default":"None","value_type":"DOUBLE","dimension":"Pressure*Time*Time/GeometricVolume*GeometricVolume"},{"index":5,"name":"ICDLEN","description":"A real value that defines the length of the ICD used in conjunction with NSCALFAC to calculate a scaling factor to be applied to the reservoir flow to adjust the flow through each ICD, that is: If NSCALFAC equals zero: then the scale factor is equal to the length of the ICD (ICDLEN) divided by the length of the tubing section, that is the parent of the ICDs, then this allows for the case when the ICD segment may represent a number of ICDs in parallel. If NSCALFAC equals one: then the scale factor is equal to the absolute value of ICDLEN. If NSCALFAC equals two: then the scale factor is equal to the length of ICDLEN, divided by the total length of the completions which supply the ICD. NSCALFAC explicitly sets which of the above three options is used. If NSCALFAC is defaulted, then option 1) is used whenever ICDLEN is positive and option 2) when ICDLEN is negative.","units":{"field":"feet 39.37","metric":"m 12.00","laboratory":"cm 1,2000"},"default":"Defined","value_type":"DOUBLE","dimension":"Length"},{"index":6,"name":"CALDEN","description":"CALDEN is a real positive value greater than zero that defines the density of the calibrating fluid at surface conditions.","units":{"field":"lb/ft3 62.416","metric":"kg/m3 1000.25","laboratory":"gm/cc 1.00025"},"default":"Defined","value_type":"DOUBLE","dimension":"Density"},{"index":7,"name":"CALVISC","description":"CALVISC is a real positive value greater than zero that defines the viscosity of the calibrating fluid at surface conditions.","units":{"field":"cP","metric":"cP","laboratory":"cP"},"default":"1.45","value_type":"DOUBLE","dimension":"Viscosity"},{"index":8,"name":"EMLCRT","description":"EMLCRT is a real positive value greater than zero that defines the “local water” in liquid fraction used to determine whether the “water-in-oil” or “oil-in-water” viscosity emulation equation should be applied.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.5","value_type":"DOUBLE","dimension":"1"},{"index":9,"name":"EMLTRANS","description":"EMLTRANS is a real positive value greater than zero that defines the width of the transition zone around EMLCRT and is used to ensure that the calculated viscosity forms a continuous function of water in liquid fraction. Within this region, the emulsion viscosity is a linear interpolation between the “water-in-oil” and “oil-in-water” viscosity values either side of the region.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.05","value_type":"DOUBLE","dimension":"1"},{"index":10,"name":"EMLMAX","description":"EMLMAX is a real positive value greater than zero that defines the maximum emulsion viscosity to continuous phase viscosity (oil or water) ratio.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"5.0","value_type":"DOUBLE","dimension":"1"},{"index":11,"name":"NSCALFAC","description":"NSCALFAC is a positive integer value that is greater than or equal to zero, that sets the method to be used when applying the scaling factor and should be set to one of the following: If NSCALFAC equals zero: then the scale factor is equal to the length of the ICD (ICDLEN) divided by the length of the tubing section, that is the parent of the ICDs, then this allows for the case when the ICD segment may represent a number of ICDs in parallel. If NSCALFAC equals one: then the scale factor is equal to the absolute value of ICDLEN. If NSCALFAC equals two: then the scale factor is equal to the length of ICDLEN, divided by the total length of the completions which supply the ICD. NSCALFAC explicitly sets which of the above three options is used. If NSCALFAC is defaulted, then option 1) is used whenever ICDLEN is positive and option 2) when ICDLEN is negative.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"-1","value_type":"INT"},{"index":12,"name":"CALRATE","description":"A real positive value that defines the maximum surface flow rate for which the ICD was calibrated.","units":{"field":"scf/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"None","value_type":"DOUBLE","dimension":"GeometricVolume/Time"},{"index":13,"name":"STATUS","description":"A defined character string of length four that defines the ICD’s operational status, STATUS should be set to one of the following character strings: OPEN: the ICD connections are are open to flow. SHUT: the ICD connections are closed to flow (shut-in).","units":{},"default":"OPEN","value_type":"STRING","options":["OPEN","SHUT"]}],"example":"The following example defines one producing well segment oil well (OP01) using the WELSPECS, WELSEGS COMPDAT and COMPSEGS keywords, followed by the WSEGSICD keyword to define the spiral inflow control devices for the well.\n--\n-- WELL SPECIFICATION DATA\n--\n-- WELL GROUP LOCATION BHP PHASE DRAIN INFLOW OPEN CROSS PVT\n-- NAME NAME I J DEPTH FLUID AREA EQUANS SHUT FLOW TABLE\nWELSPECS\nOP01 PLATFORM 10 10 1* OIL /\n/\n--\n-- WELL CONNECTION DATA\n--\n-- WELL --- LOCATION --- OPEN SAT CONN WELL KH SKIN D DIR\n-- NAME II JJ K1 K2 SHUT TAB FACT DIA FACT FACT FACT PEN\nCOMPDAT\nOP01 10 10 1 1 OPEN 1* 200. 0.5 /\nOP01 10 10 2 2 OPEN 1* 200. 0.5 /\nOP01 10 10 3 3 OPEN 1* 200. 0.4 /\nOP01 10 10 4 4 OPEN 1* 200. 0.4 /\nOP01 10 10 5 5 OPEN 1* 200. 0.4 /\nOP01 10 10 6 6 OPEN 1* 200. 0.4 /\nOP01 9 10 2 2 OPEN 1* 200. 0.4 /\nOP01 8 10 2 2 OPEN 1* 200. 0.4 /\nOP01 7 10 2 2 OPEN 1* 200. 0.4 /\nOP01 6 10 2 2 OPEN 1* 200. 0.4 /\nOP01 5 10 2 2 OPEN 1* 200. 0.4 /\nOP01 10 9 3 3 OPEN 1* 200. 0.4 /\nOP01 10 8 3 3 OPEN 1* 200. 0.4 /\nOP01 10 7 3 3 OPEN 1* 200. 0.4 /\nOP01 10 6 3 3 OPEN 1* 200. 0.4 /\nOP01 10 5 3 3 OPEN 1* 200. 0.4 /\nOP01 9 10 5 5 OPEN 1* 200. 0.4 /\nOP01 8 10 5 5 OPEN 1* 200. 0.4 /\nOP01 7 10 5 5 OPEN 1* 200. 0.4 /\nOP01 6 10 5 5 OPEN 1* 200. 0.4 /\nOP01 5 10 5 5 OPEN 1* 200. 0.4 /\nOP01 10 9 6 6 OPEN 1* 200. 0.4 /\nOP01 10 8 6 6 OPEN 1* 200. 0.4 /\nOP01 10 7 6 6 OPEN 1* 200. 0.4 /\nOP01 10 6 6 6 OPEN 1* 200. 0.4 /\nOP01 10 5 6 6 OPEN 1* 200. 0.4 /\n/\n--\n-- WELL SEGMENT SPECIFICATION DATA\n--\n-- WELL NODAL LEN WELL DEPH PRESS FLOW\n-- NAME DEPTH TUBING VOLM OPTN CALC MODEL\nWELSEGS\nOP01 2512.5 2512.5 1.0E-5 ABS HFA HO /\n--\n-- SEG SEG BRAN SEG TUBING NODAL TUBE TUBE XSEC VOL\n-- ISTR IEND NO NO LENGTH DEPTH ID ROUGH AREA SEG\n2 2 1 1 2537.5 2534.5 0.3 0.00010 /\n3 3 1 2 2562.5 2560.5 0.3 0.00010 /\n4 4 1 3 2587.5 2593.5 0.3 0.00010 /\n5 5 1 4 2612.5 2614.5 0.3 0.00010 /\n6 6 1 5 2637.5 2635.5 0.3 0.00010 /\n7 7 2 2 2737.5 2538.5 0.2 0.00010 /\n8 8 2 7 2937.5 2537.5 0.2 0.00010 /\n9 9 2 8 3137.5 2539.5 0.2 0.00010 /\n10 10 2 9 3337.5 2535.5 0.2 0.00010 /\n11 11 2 10 3537.5 2536.5 0.2 0.00010 /\n12 12 3 3 2762.5 2563.5 0.2 0.00010 /\n13 13 3 12 2962.5 2562.5 0.1 0.00010 /\n14 14 3 13 3162.5 2562.5 0.1 0.00010 /\n15 15 3 14 3362.5 2564.5 0.1 0.00010 /\n16 16 3 15 3562.5 2562.5 0.1 0.00010 /\n17 17 4 5 2812.5 2613.5 0.2 0.00010 /\n18 18 4 17 3012.5 2612.5 0.1 0.00010 /\n19 19 4 18 3212.5 2612.5 0.1 0.00010 /\n20 20 4 19 3412.5 2612.5 0.1 0.00010 /\n21 21 4 20 3612.5 2613.5 0.1 0.00010 /\n22 22 5 6 2837.5 2634.5 0.2 0.00010 /\n23 23 5 22 3037.5 2637.5 0.2 0.00010 /\n24 24 5 23 3237.5 2638.5 0.2 0.00010 /\n25 25 5 24 3437.5 2639.5 0.1 0.00010 /\n26 26 5 25 3637.5 2639.5 0.1 0.00010 /\n/\n--\n-- COMPLETION SEGMENT SPECIFICATION DATA\n--\n-- WELL\n-- NAME\nCOMPSEGS\nOP01 /\n--\n-- --LOCATION-- BRAN TUBING NODAL DIR LOC MID COMP ISEG\n-- II JJ K1 NO LENGTH DEPTH PEN I,J,K PERFS LENGTH NO.\n10 10 1 1 2512.5 2525.0 /\n10 10 2 1 2525.0 2550.0 /\n10 10 3 1 2550.0 2575.0 /\n10 10 4 1 2575.0 2600.0 /\n10 10 5 1 2600.0 2625.0 /\n10 10 6 1 2625.0 2650.0 /\n9 10 2 2 2637.5 2837.5 /\n8 10 2 2 2837.5 3037.5 /\n7 10 2 2 3037.5 3237.5 /\n6 10 2 2 3237.5 3437.5 /\n5 10 2 2 3437.5 3637.5 /\n10 9 3 3 2662.5 2862.5 /\n10 8 3 3 2862.5 3062.5 /\n10 7 3 3 3062.5 3262.5 /\n10 6 3 3 3262.5 3462.5 /\n10 5 3 3 3462.5 3662.5 /\n9 10 5 4 2712.5 2912.5 /\n8 10 5 4 2912.5 3112.5 /\n7 10 5 4 3112.5 3312.5 /\n6 10 5 4 3312.5 3512.5 /\n5 10 5 4 3512.5 3712.5 /\n10 9 6 5 2737.5 2937.5 /\n10 8 6 5 2937.5 3137.5 /\n10 7 6 5 3137.5 3337.5 /\n10 6 6 5 3337.5 3537.5 /\n10 5 6 5 3537.5 3737.5 /\n--\n-- MULTI-SEGMENT WELL ICD SEGMENT SPECIFICATION DATA\n--\n-- WELL SEG SEG ICD ICD CAL CAL EML EML EML SCAL CAL OPEN\n-- NAME ISTR IEND STRNEN LEN DEN VISC CRIT TRANS MAX FAC RATE CLOSE\nWSEGSICD\nOP01 7 10 0.00025 1* 1.0 0.45 0.50 0.05 5.0 2 1* OPEN /\nOP01 12 15 0.00025 1* 1.0 0.45 0.50 0.05 5.0 2 1* OPEN /\nOP01 17 20 0.00025 1* 1.0 0.45 0.50 0.05 5.0 2 1* OPEN /\nOP01 22 22 0.00025 1* 1.0 0.45 0.50 0.05 5.0 2 1* OPEN /\nOP01 23 23 0.00025 1* 1.0 0.45 0.50 0.05 5.0 2 1* OPEN /\nOP01 24 24 0.0002","expected_columns":13,"size_kind":"list"},"WSEGSOLV":{"name":"WSEGSOLV","sections":["SCHEDULE"],"supported":false,"summary":"The WSEGSOLV keyword defines the numerical control parameters for the iterative linear solver for multi-segment well looped flow paths, as defined by the WSEGLINK keyword in the SCHEDULE section. A looped segment results in the nodes of the two individual segments that are looped (or connected) having the same solution pressures and oil, water and gas flowing rates.","parameters":[{"index":1,"name":"USE_ITERATIVE_SOLVER","description":"","units":{},"default":"NO","value_type":"STRING"},{"index":2,"name":"MAX_LINEAR_ITER","description":"","units":{},"default":"30","value_type":"INT"},{"index":3,"name":"CONVERGENCE_TARGET","description":"","units":{},"default":"1e-10","value_type":"DOUBLE"},{"index":4,"name":"PC_FILL","description":"","units":{},"default":"2","value_type":"INT"},{"index":5,"name":"DROP_TOL","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":6,"name":"P_LIMIT","description":"","units":{},"default":"1e-08","value_type":"DOUBLE"},{"index":7,"name":"LOOP_THRESHOLD","description":"","units":{},"default":"-1","value_type":"DOUBLE","dimension":"Length*Length*Length/Time"},{"index":8,"name":"LOOP_MULTIPLIER","description":"","units":{},"default":"-1","value_type":"DOUBLE"}],"example":"","expected_columns":8,"size_kind":"fixed","size_count":1},"WSEGTABL":{"name":"WSEGTABL","sections":["SCHEDULE"],"supported":false,"summary":"WSEGTABL assigns previously defined Vertical Lift Performance (“VLP”) tables as specified by the VFPPROD keyword in the SCHEDULE section, to multi-segment well segments, as well as stipulating how the tables are to be applied.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"SEGMENT1","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"SEGMENT2","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"VFP","description":"","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"VFP_COMPONENTS","description":"","units":{},"default":"FH","value_type":"STRING"},{"index":6,"name":"VFP_OUTLIER","description":"","units":{},"default":"","value_type":"STRING"},{"index":7,"name":"DP_SCALING","description":"","units":{},"default":"LEN","value_type":"STRING"},{"index":8,"name":"ALQ_VALUE","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":9,"name":"STATUS","description":"","units":{},"default":"OPEN","value_type":"STRING"}],"example":"","expected_columns":9,"size_kind":"list"},"WSEGVALV":{"name":"WSEGVALV","sections":["SCHEDULE"],"supported":null,"summary":"The WSEGVALV keyword defines a multi-segment well segment to be a sub-critical valve Inflow Control Device (“ICD”) as part of a completion for a multi-segment well. Note that the well must have been previously defined by the WELSPECS and WELSEGS keywords in the SCHEDULE section and that the data for the keyword should be repeated for each multi-segment completion that contains a sub-critical valve ICD.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which a multi-segment well is being defined. Note that the well name (WELNAME) must have been declared previously using both the WELSPECS and WELSEGS keywords in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"ISEG1","description":"A positive integer greater than or equal to two and less than or equal to MXSEGS on the WSEGDIMS keyword in the RUNSPEC section that defines the segment containing the sub-critical valve.","units":{},"default":"None","value_type":"INT"},{"index":3,"name":"ICDCV","description":"A real positive value greater than zero that defines the dimensionless flow coefficient for the valve (Cv). This a vendor specific value for a given vendor’s ICD.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE"},{"index":4,"name":"AREAREST","description":"A real positive value that defines the cross-sectional area of flow in the restricted section of the valve (Ar) and should have a minimum value of 1.0 x 10-10. This value may be specified using a User Defined Argument (UDA). AREAREST is used to convert the segment volumetric flow rate into the flow velocity at the constriction (υr).","units":{"field":"ft2","metric":"m2","laboratory":"cm2"},"default":"None","value_type":"UDA","dimension":"Length*Length"},{"index":5,"name":"SEGLEN","description":"A real positive value greater than or equal to zero that defines the additional pipe length for the frictional pressure drop (L). If set to zero then there is no additional pressure loss due to friction, whereas, if set to the default (1*), then the segment pipe length is calculated from the corresponding WELSEGS keyword.","units":{"field":"ft","metric":"m","laboratory":"cm"},"default":"Defined","value_type":"DOUBLE","dimension":"Length"},{"index":6,"name":"ID","description":"A real positive value that defines the pipe internal diameter of the segment used to calculate the pressure drop due to friction (D). The value is used to replace the segment pipe internal diameter defined on the WELSEGS keyword in record 2-7, also named ID. If ID is defaulted on this keyword then the equivalent value on the WELSEGS keyword will be used instead. Note for non-circular pipe segments use the equivalent diameter instead, that is: [Equivalent ID``=``{ 4.0 times (Cross-Sectional Area) } over Perimeter]","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"Defined","value_type":"DOUBLE","dimension":"Length"},{"index":7,"name":"EPSILON","description":"A real positive value that defines the pipe absolute roughness for this segment. The value is used to replace the segment pipe absolute roughness defined on the WELSEGS keyword in record 2-8, also named EPSILON. If EPSILON is defaulted on this keyword then the equivalent value on the WELSEGS keyword will be used instead.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"Defined","value_type":"DOUBLE","dimension":"Length"},{"index":8,"name":"AREAPIPE","description":"A real positive value that defines the cross-sectional area of flow in the pipe (Ap), as opposed to the restricted section of the valve (Ar). AREAPIPE is used to convert the segment volumetric flow rate into the flow velocity through the pipe (υp). The value is used to replace the segment pipe cross-sectional area of flow defined on the WELSEGS keyword in record 2-9, named XAREA. If AREAPIPE is defaulted on this keyword then the equivalent value on the WELSEGS keyword will be used instead.","units":{"field":"ft2","metric":"m2","laboratory":"cm2"},"default":"Defined","value_type":"DOUBLE","dimension":"Length*Length"},{"index":9,"name":"STATUS","description":"A character string of length four that defines the ICD’s operational status, STATUS should be set to one of the following character strings: OPEN: the ICD connections are are open to flow. SHUT: the ICD connections are closed to flow (shut-in).","units":{},"default":"OPEN","value_type":"STRING","options":["OPEN","SHUT"]},{"index":10,"name":"AREAMAX","description":"A real positive value that defines the maximum cross-sectional area of flow in the restricted section of the valve (Amax). AREAMAX is used to convert the segment volumetric flow rate into the maximum flow velocity at the constriction (υr). If defaulted then AREAPIPE will be used if defined, otherwise XAREA (item 2-9) on the WELSEGS keyword will be used.","units":{"field":"ft2","metric":"m2","laboratory":"cm2"},"default":"Defined","value_type":"DOUBLE","dimension":"Length*Length"}],"example":"The following example is based on one producing well segment oil well (OP01) using the WELSPECS, WELSEGS COMPDAT and COMPSEGS keywords, as per the WSEGSICD keyword example (Example), and is therefore not repeated here.\n--\n-- MULTI-SEGMENT WELL ICD SEGMENT SPECIFICATION DATA\n--\n-- WELL SEG DEVICE AREA PIPE PIPE PIPE PIPE OPEN MAX\n-- NAME NO CV REST LENG ID EPSI AREA SHUT AREA\nWSEGVALV OP01 7 0.960 0.012 1* 1* 1* 1* OPEN 1* / DEFAULT VALUES\nOP01 12 0.960 0.012 1* 1* 1* 1* OPEN 1* / TAKEN FROM\nOP01 17 0.960 0.012 1* 1* 1* 1* OPEN 1* / WELSEGS KEYWORD\nOP01 22 0.850 0.100 1* 1* 1* 1* OPEN 1* /\nOP01 23 0.850 0.100 1* 1* 1* 1* OPEN 1* /\nOP01 24 0.850 0.100 1* 1* 1* 1* OPEN 1* /\nOP01 25 0.850 0.100 1* 1* 1* 1* OPEN 1* /\n/\nHere segments 7, 12 and 17 have the same type of sub-critical valves with their pipe properties taken from the WELSEGS keyword used to define well OP01 as a multi-segment well. Similarly, segments 22 to 25 have the same ICD properties, and again the pipe properties are taken from the WELSEGS keyword.\n| [%delta P ~=~ %delta P sub restriction ``+``%delta P sub friction newline\nnewline\nwhere newline\n%delta P sub restriction ``=``C sub 1 {%rho {%upsilon sup 2} sub r} over { 2{C sub v} }sup 2 newline\nnewline\n%delta P sub friction ``=`` 2C sub 2 f L over D %upsilon sup 2 sub p] | (12.42) |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|\n| Conversion Factor Constants and Variable Units | | | | | |\n|------------------------------------------------|-----------------|---------------|---------------|---------------|----------|\n| No. | Name | Field | Metric | Laboratory | Property |\n| 1 | C1 | 2.159 x 10-4 | 1.0 x 10-5 | 9.869 x 10-7 | Constant |\n| 2 | C2 | 2.892 x 10-14 | 1.340 x 10-15 | 7.615 x 10-14 | |\n| 3 | Density | lb/ft3 | kg/m3 | gm/cc | Units |\n| 4 | Pressure | psia | bars | atm | |\n| 5 | Velocity | ft/s | m/s | cm/s | |\n| 6 | Volumetric Flow | ft3/day | m3/day | cc/hour | |\n| [q ``=``%upsilon sub r A sub r ``=``%upsilon sub p A sub p] | (12.43) |\n|-------------------------------------------------------------|---------|\n| [%delta P sub restriction ``=``C sub 2 {%rho {q} sup 2} over {{ 2{C sub v} }sup 2 A sup 2 sub r}] | (12.44) |\n|---------------------------------------------------------------------------------------------------|---------|\n| [K ``=` {`C sub 2} over {{ 2{C sub v} }sup 2 A sup 2 sub r}] | (12.45) |\n|--------------------------------------------------------------|---------|\n| [Seting of Device ``=`` { A sub r } over { A sub max }] | (12.46) |\n|---------------------------------------------------------|---------|","expected_columns":10,"size_kind":"list"},"WSKPTAB":{"name":"WSKPTAB","sections":["SCHEDULE"],"supported":null,"summary":"The WSKPTAB keyword assigns the well polymer molecular water and polymer skin tables to water injection wells in OPM Flow's Polymer Molecular Weight Transport option, that uses the polymer molecular weight in calculating the polymer viscosity, as well as accounting for formation damage due to the water and polymer injection, by adjusting the wellbore skin pressure. This keyword should only be used if the POLYMER and POLYMW keywords in the RUNSPEC section are also activated. The keyword assigns the water SKPRWAT tables, that are defined via the SKPRWAT keyword in the PROPS section, that are used to calculable the wellbore skin pressure during water injection. As well as the polymer SKPRPOLY tables, that are defined via the SKPRPOLY keyword in the PROPS section, that are used to calculable the wellbore skin pressure during polymer injection.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length, that defines the water injection well name, for which the well water injection skin table, SKKPRWAT, and the polymer skin injection table, SKPRPOLY, are to be assigned. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"SKPRWAT","description":"A positive integer value that defines the corresponding SKPRWAT table to be allocated to the water injection well. A value less than or equal to zero means that no SKPRWAT table is allocated to the well","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"SKPRPOLY","description":"A positive integer value that defines the corresponding SKPRPOLY table to be allocated to the water injection well. A value less than or equal to zero means that no SKPRPOLY table is allocated to the well","units":{},"default":"0","value_type":"INT"}],"example":"Given NTSKWAT equals two and NTSKPOLY equals three on the PINTDIMS keyword in the RUNSPEC section, then:\n--\n-- ASSIGN WELL POLYMER MOLECULAR MODEL SKIN TABLES\n--\n-- WELL SKPRWAT SKPRPOLY\n-- NAME TABLE TABLE\nWSKPTAB\nWI01 1 1 /\nWI02 1 3 /\nWI03 2 2 /\n/\nAssigns SKPRWAT table one to wells WI01 and WI02 and table two to WI03, and SKPRPOLY tables one, two and three to wells WI01, WI03, and WI02, respectively.\n| Note This is an OPM Flow specific keyword that employs an alternative polymer flood model based on a Polymer Molecular Weight Transport equation, that is not available in the commercial simulator. |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":3,"size_kind":"list"},"WSOLVENT":{"name":"WSOLVENT","sections":["SCHEDULE"],"supported":null,"summary":"WSOLVENT defines a gas injection well’s solvent fraction in the injection stream that is to be used when the Solvent option has been activated by the SOLVENT keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name of a gas injection well for which the solvent fraction data is being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"SOLVENT_FRACTION","description":"","units":{},"default":"","value_type":"UDA","dimension":"1"},{"index":4,"name":"SOLFRA","description":"A real positive value greater than or equal to zero and less than or equal to one that defines the fraction of solvent in the gas well’s injection stream. This value may be specified using a User Defined Argument (UDA).","units":{"field":"fraction","metric":"fraction","laboratory":"fraction"},"default":"None"}],"example":"The following example defines the solvent fractions for three gas injection wells for when the solvent option has been activated by the SOLVENT keyword in the RUNSPEC section.\n--\n-- DEFINE GAS INJECTION WELL SOLVENT FRACTION\n--\n-- WELL SOLVENT\n-- NAME FRACTION\n-- --------\nWSOLVENT\nGI01 0.0000 /\nGI02 0.5000 /\nGI03 0.5000 /\n/\nThe solvent fraction for the GI01 gas injector is set to zero and both GI02 and GI03 gas injectors have solvent fraction values of 0.5 for their injection streams.","expected_columns":2,"size_kind":"list"},"WSURFACT":{"name":"WSURFACT","sections":["SCHEDULE"],"supported":false,"summary":"WSURFACT defines a water injection well’s surfactant concentration in the injection stream that is to be used when the Surfactant phase has been activated by either the SURFACT or SURFACTW keywords in the RUNSPEC section.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name of a gas injection well for which the solvent fraction data is being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"SURCON","description":"A real positive value that defines the surfactant concentration of the well’s injection stream.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None","value_type":"UDA","dimension":"Concentration"}],"example":"The following example defines the surfactant concentrations for three water injection wells for when the surfactant phase option has been activated by either the SURFACT or SURFACTW keywords in the RUNSPEC section. Here the surfactant concentration has been set to 0.200 for all three wells.\n--\n-- DEFINE WATER INJECTION WELL SURFACTANT CONCENTRATION\n--\n-- WELL SURFACT\n-- NAME SURCON\n-- --------\nWSURFACT\nWI01 0.2000 /\nWI02 0.2000 /\nWI03 0.2000 /\n/","expected_columns":2,"size_kind":"list"},"WTADD":{"name":"WTADD","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, WTADD, adds a constant to a previously define well’s target or constraint, as stated on the WCONPROD, WCONINJE, or WELTARG keywords, but not for the history matching wells using the WCONHIST or WCONINJH keywords. All the aforementioned keywords are in the SCHEDULE section. The constant can be positive or negative.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"CONTROL","description":"The control mode seems to be a UDA??","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"SHIFT","description":"","units":{},"default":"","value_type":"UDA"},{"index":4,"name":"NUM","description":"","units":{},"default":"1","value_type":"INT"}],"example":"","expected_columns":4,"size_kind":"list"},"WTEMP":{"name":"WTEMP","sections":["SCHEDULE"],"supported":null,"summary":"The WTEMP keyword defines the temperature of the injection fluid being injected by an injection well.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for an injection well for which the injection well fluid’s temperature data is being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"TEMP","description":"A real positive value greater than zero that defines the temperature of the injected fluid.","units":{"field":"oF","metric":"oC","laboratory":"oC"},"default":"None","value_type":"DOUBLE","dimension":"Temperature"}],"example":"The following example defines the injected fluid temperatures for three water injection wells for when the thermal option has been activated by the THERMAL keyword in the RUNSPEC section.\n--\n-- DEFINE INJECTION WELL FLUID TEMPERATURE\n--\n-- WELL FLUID\n-- NAME TEMP.\n-- --------\nWTEMP\nWI01 39.00 /\nWI02 37.00 /\nWI03 39.00 /\n/\nHere wells WI01 and WI03 inject water with a water temperature of 39 oF and well WI02’s injection water temperature is 37 oF.","expected_columns":2,"size_kind":"list"},"WTEMPQ":{"name":"WTEMPQ","sections":["SCHEDULE"],"supported":false,"summary":"The WTEMPQ prints out a user defined selected list of currently defined wells and well lists to the print file (*.PRT). The keyword allows for sub-setting the well names etc., using the normal well and well list naming conventions. For example to list all wells beginning with the characters “OP” then one would use “OP*” as the well name on this keyword.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"LGR","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":2,"size_kind":"list"},"WTEST":{"name":"WTEST","sections":["SCHEDULE"],"supported":false,"summary":"The WTEST keyword outlines the testing procedures to be applied to wells that are closed for various reasons to see if the wells are capable flowing under the current operating conditions. The keyword can be applied to single wells or groups of wells.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name of the well to be tested. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"TIME","description":"A real value greater than zero that defines the minimum period of time that must elapse between well tests. The next well test is performed at the beginning of the next time step after the specified period of time has elapsed since the previous well test, for example if TIME is set equal to 365.25 (days), the test is performed approximately every year.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"None","value_type":"DOUBLE","dimension":"Time"},{"index":3,"name":"TEST","description":"A character string of up to five characters in length that defines a list of reasons why a well could have been closed. If a well was closed for one of the specified reasons then the well is tested to see if it can be put back on production. The characters that can be used to define TEST are as follows: P: meaning the well was closed due to a bottom-hole or tubing head pressure limit, or other physical limit then the well is tested to see if it can flow, if it can, then it is put back on production, otherwise it remains closed. E: meaning the well was closed due to a well or a well connection economic constraint then the well is tested to see if it can flow, if it can then it is put back on production, otherwise it remains closed. Here, if the well has at least one connection open then the well is opened. If a well has no open connections, then those connections that have been closed due to an economic limit test (\"ELT\"), are all individually tested and reopened if they meet the ELT criteria as defined by the WECON, CECON and WECONINJ keywords in the SCHEDULE section. And the well is opened if it has at least one open connection. Where the ELT applies to ORAT, GRAT, WCUT, GOR and WGR etc. G: meaning the well was closed due to a group economic constraint, as per the GECON, GECONT, GCONCAL, GCONPRI, GCONPROD, and GCONSALE, keywords in the SCHEDULE section, then the well is tested to see if it can flow, if it can, then it is put back on production, otherwise it remains closed. D: not supported by OPM Flow. C: not supported by OPM Flow. The default value is an empty string “ ” that switches off testing. Note that only the P, E and G options are currently supported in OPM Flow.","units":{},"default":"“ ”","value_type":"STRING"},{"index":4,"name":"NTIME","description":"A positive integer greater than or equal to zero that define the number of times a well can be tested. The default value of zero means an infinite number of times.","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"START","description":"A real positive value that defines the start up time used to prorate the rate at which the well is put back on production. If START is large compared to the time step size, then the well is brought on gradually, if it is less than the time step size, then the well is opened faster. The rate is prorated based on the following: [Q_i~=~Q_final times left({T_{End of Time Step}`- `T_opened} over START right)] The default value of 0.0 means the well is opened immediately.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"0.0","value_type":"DOUBLE","dimension":"Time"}],"example":"The following example defines test criteria for all gas wells (‘GP*’) and three oil wells (OP01, OP02, and OP03).\n--\n--\n-- WELL TESTING CRITERIA FOR RE-OPENING CLOSED WELLS\n--\n-- WELL TST TST NO. STRT\n-- NAME INTV TYPE TSTS TIME\n-- ---- ---- ---- ---- ----\nWTEST\n‘GP*’ 365.25 P 5 0.0\nOP01 30.0 PEG 0 0.0 /\nOP02 30.0 PEG 0 0.0 /\nOPO3 30.0 PEG 0 0.0 /\n/\nAll the gas wells are test annually if they have been shut-in due to a bottom-hole or tubing head pressure limit, are tested five times after they have been closed, and are opened up immediately. The oil wells are tested every 30 days if they have been closed due to a bottom-hole or tubing head pressure limit, a well economic limit or a group economic limit. All the oil wells are tested an infinite amount of times and are opened up immediately. Note that only the P, E and G options are currently supported in OPM Flow.","expected_columns":5,"size_kind":"list"},"WTHPMAX":{"name":"WTHPMAX","sections":["SCHEDULE"],"supported":false,"summary":"WTHPMAX stipulates a well’s maximum flowing Tubing Head Pressure (“THP”), above which the well will be shut-in. The facility is useful if the THP exceeds the wellhead maximum design pressure, which can occur if excessive gas invades the wellbore. In addition to setting the maximum THP, the keyword defines the criteria for re-testing the well to see if the THP has fallen below the maximum value.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"MAX_THP_DESIGN_LIMIT","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":3,"name":"CONTROL","description":"","units":{},"default":"ORAT","value_type":"STRING"},{"index":4,"name":"CONTROL_LIMIT","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":5,"name":"THP_OPEN_LIMIT","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"}],"example":"","expected_columns":5,"size_kind":"list"},"WTMULT":{"name":"WTMULT","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, WTMULT, multiplies a defined well’s target or constraint by a constant, for the target and constraints previously stipulated on the WCONPROD, WCONINJE, or WELTARG keywords, but not for the history matching wells using the WCONHIST or WCONINJH keywords. All the aforementioned keywords are in the SCHEDULE section. The constant should be positive value.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well target or constraint (CONTROL) is being adjusted by the multipler (FACTOR). Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"CONTROL","description":"A defined character string that declares the well target or constraint that will be adjusted by multiplying its current value by the FACTOR defined in (3). CONTROL should be set to one of the following character strings: ORAT: the well’s surface oil production rate will be adjusted. WRAT: the well’s surface water production rate will be adjusted. GRAT: the well’s surface gas production rate will be adjusted. LRAT: the well’s surface liquid (oil plus water) production rate will be adjusted. CRAT: the well’s linearly combined maximum surface rate, as per the LINCOM keyword in the SCHEDULE section, will be adjusted. RESV: the well’s in situ reservoir volume rate will be adjusted. BHP: the well’s bottom-hole pressure will be adjusted. THP: the well’s tubing head pressure will be adjusted. In this case a vertical performance table must have been previously assigned to the well via the WCONPROD or WCONINJE keywords. The tables are entered via the VFPINJ or the VFPPROD keywords. All the keywords are in the SCHEDULE section. LIFT: the well’s artificial lift quantity will be adjusted. Again, as for the THP, a vertical performance table must have been assigned to the well. GUID: the well’s guide rate will be adjusted. Only wells under group control and have a guide rate stipulated by the WGRUPCON keyword in the SCHEDULE section, may use this option. CVAL: the well’s calorific rate will be adjusted. NGL: the well’s natural gas liquid rate will be adjusted. Note that the CRAT, CVAL and the NGL options are not available in OPM Flow and should not be used.","units":{},"default":"None","value_type":"STRING","options":["ORAT","WRAT","GRAT","LRAT","CRAT","RESV","BHP","THP","LIFT","GUID","CVAL","NGL"]},{"index":3,"name":"FACTOR","description":"A postive real value that defines the FACTOR that is used to multiply the CONTROL specified in (2). This value may be specified using a User Defined Argument (UDA).","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"UDA"},{"index":4,"name":"NTIME","description":"A positive integer greater than or equal to one that defines the number of report time steps for which the well target or constraint (CONTROL) is multiplied by the FACTOR. This is only applied when the FACTOR is specified by a User Defined Argument (UDA). The default value of one means that the multiplication is applied only at the current time step for the UDA variable. This option is not supported by OPM Flow.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1","value_type":"INT"}],"example":"The example shows three oil wells having the flow streams adjusted.\n--\n-- WELL TARGET/LIMIT MULTIPLIER\n--\n-- WELL WELL MULT REPORT\n-- NAME CNTL FACTOR TIMES\nWTMULT\nOP01 ORAT 0.90 /\nOP02 BHP 0.95 /\nOP03 LIFT 1.25 /\n/\nWell OP01 has its current oil rate target multiplied by 0.90, well OP02 has its bottom-hole pressure constraint multiplied by 0.95, and well OP03 has its artificial lift quantity increased by 1.25 times.","expected_columns":4,"size_kind":"list"},"WTRACER":{"name":"WTRACER","sections":["SCHEDULE"],"supported":false,"summary":"The WTRACER keyword defines the tracer concentration of the injection fluid being injected by an injection well. This keyword should only be used if the Tracer option has been invoked by the TRACERS keyword in the RUNSPEC section and the tracers have be declared via the TRACER keyword in the PROPS section.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name of an injection well for which the tracer fraction data is being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"NAME","description":"A three letter character string defining the tracer’s name which has previously been defined via the TRACER keyword in the PROPS section. Note it is best to avoid names beginning with the letters F, S, and T as these names may create naming issues in post-processing software.","units":{},"default":"None","value_type":"STRING"},{"index":3,"name":"TRCON","description":"A real positive value that defines the tracer concentration of the well’s injection stream. This value may be specified using a User Defined Argument (UDA).","units":{"field":"Liquid: 1/stb Gas: 1/Mscf","metric":"Liquid: 1/sm3 Gas: 1/sm3","laboratory":"Liquid: 1/scc Gas: 1/scc"},"default":"None","value_type":"UDA"},{"index":4,"name":"TRCUM","description":"A real positive value that defines the cumulative tracer concentration factor of the well’s injection stream. This value may be specified using a User Defined Argument (UDA). This feature is currently not supported by OPM Flow.","units":{"field":"Liquid: 1/stb Gas: 1/Mscf","metric":"Liquid: 1/sm3 Gas: 1/sm3","laboratory":"Liquid: 1/scc Gas: 1/scc"},"default":"None","value_type":"UDA"},{"index":5,"name":"GRPNAME","description":"A character string of up to eight characters in length that defines the group from which the produced tracer concentration should be used for the well’s injection stream. GRPNAME must have been previously defined via the GCONPROD keyword in the SCHEDULE section, unless the FIELD group has been specified here. Note if GRPNAME is not defined then TRCON will be used for the tracer concentration of the well’s injection stream. This feature is currently not supported by OPM Flow.","units":{},"default":"None","value_type":"STRING"}],"example":"The following example defines the tracer concentrations for two gas injectors and three water injection wells, with water injection well WI02 having no ‘WAT’ tracer injected in the water phase.\n--\n-- DEFINE CONCENTRATION OF TRACERS IN THE INJECTION STREAMS,\n-- INJECTION TRACER CONCENTRATIONS NOT DEFINED USING THE WTRACER\n-- KEYWORD ARE ASSUMED TO BE ZERO.\n--\n-- WELL NAME TRACER TRACER TRACER\n-- NAME TRACER CONC CUM GROUP\nWTRACER\nGI01 'GAS' 1.0 /\nGI02 'GAS' 1.0 /\nWI01 'WAT' 1.0 /\nWI02 'WAT' 0.0 /\nWI03 'WAT' 1.0 /\n/\nNote the terminating “/” for the keyword.","expected_columns":5,"size_kind":"list"},"WVFPDP":{"name":"WVFPDP","sections":["SCHEDULE"],"supported":null,"summary":"The WVFPDP keyword modifies a well’s Bottom-Hole Pressure (“BHP”) estimated by the simulator by interpolation of the Vertical Flow Performance (“VFP”) tables. The production VFP tables are entered via the VFPPROD keyword and the injection tables by the VFPINJ keyword; both keywords are in the SCHEDULE section.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which VFP interpolated BHP adjustment is to be applied. Note that the well name (WELNAME) must have been declared previously using the WELSPECS and WCONPROD (or WCONINJE) keywords in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"DELTAP","description":"A real positive or negative value that is added to the VFP interpolated BHP value (BHPVFP). A positive value of DELTAP increases the BHP and therefore makes a production well less productive; whereas, a negative value is subtracted from the BHP and therefore increases the productivity of a production well. Consequently, the opposite effect occurs for injection wells, that is, a positive value of BHPVFP increases the BHP and therefore increases an injection well’s injectivity; whereas, a negative value is subtracted from the BHP and therefore decreases the injectivity of an injection well.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"0.0","value_type":"DOUBLE","dimension":"Pressure"},{"index":3,"name":"MULTP","description":"MULTP is a real positive or negative value that scales the tubing pressure loss by the following equation; [BHP sub {Adjusted}~=~THP`+`MULTP left( BHP sub {VFP} `-`THP right)] Thus, a MULTP value greater then 1.0 increases the BHP and therefore makes a production well less productive; whereas, a value less than 1.0 increases the productivity of a production well. Consequently, the opposite effect occurs for injection wells","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0","value_type":"DOUBLE"}],"example":"The following example below shows three oils operating under THP control.\n-- ------------------------------------------------------------------------------\n-- 01 JAN 2000 START OF SCHEDULE SECTION\n-- ------------------------------------------------------------------------------\n--\n-- WELL PRODUCTION WELL CONTROLS\n--\n-- WELL OPEN/ CNTL OIL WAT GAS LIQ RES BHP THP VFP VFP\n-- NAME SHUT MODE RATE RATE RATE RATE RATE PRES PRES TABLE ALFQ\nWCONPROD\nOP01 OPEN THP 1* 1* 1* 5000 1* 750.0 500. 9 1* /\nOP02 OPEN THP 1* 1* 1* 5000 1* 750.0 500. 9 1* /\nOP03 OPEN THP 1* 1* 1* 5000 1* 750.0 500. 9 1* /\n/\n--\n-- WELL VFP BHP-THP CORRECTION DATA\n--\n-- WELL BHP BHP\n-- NAME DELTAP MULTP\nWVFPDP\nOP01 20.O 1* /\nOP01 -5.O 1* /\nOP01 0.O 1.10 /\n/\nWell OP01 has a delta pressure correction of 20 psia applied to it’s BHP resulting in a reduction in the well’s productivity for the given 500.0 psia THP operating target. For well OP02, the well’s productivity is increased by subtracting 5.0 psia from the BHP. And finally for well OP03, the MULTP value of 1.10 decreases the well’s productivity by increasing the pressure loss between the THP and BHP by 10%.","expected_columns":3,"size_kind":"list"},"WVFPEXP":{"name":"WVFPEXP","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, WVFPEXP, defines how Vertical Flow Performance (“VFP”) tables are interpolated and can be used to resolve certain issues with wells operating under tubing head pressure control. For example, setting the VFP table to interpolate explicitly, that is using the previous time step results of the gas and water ratios for an oil well, may improve convergence. The default is to use implicit interpolation that uses the current time step values and may result in solution convergence oscillations in solving the linear equations. The WCONPROD keyword is used to allocate the VFPPROD tables to specific production wells. Note that one VFP table can be allocated to one or more wells; however, WVFPEXP is applied to a well’s allocated VFP table, not to all wells that use the same table, unless specifically requested. All the aforementioned keywords are in the SCHEDULE section.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well’s VFP interpolation options are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"IMPEXP","description":"A defined character string of length three that defines the how the well’s VFPPROD tables are to be interpolated and should be set to one of the following character strings: IMP: For this option the simulator interpolates a well’s VFP table implicitly, that is the latest gas fraction (GOR, GLR, etc.), water fraction (WCUT, WOR etc.), and ALQ is used to determine the required pressure. This is the most accurate option but may lead to oscillating behavior during the Newton/Linear iterations. This is the default behavior. EXP: This options forces the simulator to use the previous time step values of a well’s gas fraction, water fraction, and ALQ to interpolate a well’s VFP table in order to determine the required pressure. This is less accurate than the IMP option but minimizes any oscillating behavior during the Newton/Linear iterations. If a well's WCUT and GOR is varying as a function of BHP inside a Newton/Linear iteration (as for example when gas cusping or water coning is occurring), the implicit lookup of the VFP tables might indicate that the well has died, due to the interpolation/extrapolation. If a well dies using implicit WCUT and GOR VFP lookup then the simulator automatically switches to explicit (previous time step) VFP lookup to prevent the well from premature closure, and writes a message to the screen and print file stating the fact. Note the explicit treatment is just for the VFP lookup only. Using the IMPEXP option allows one to select wells that should use either the implicit or explicit lookup option, which may be useful in improving run time performance. Note that if the default value of IMP is used, the simulator will still switch to explicit VFP lookup to prevent a well from premature closure if the condition occurs.","units":{},"default":"IMP","value_type":"STRING"},{"index":3,"name":"STATUS","description":"A defined character string that defines if the well’s operating condition should be checked to see if the VFP table lookup indicates if the well is operating on the flat or horizontal part of stabilized portion of the VLP table (curve), and should be set to one of the following character strings: NO: For this option the check is not performed. YES: In this case the check is performed. Hence, if a well under THP control is found to operating on the horizontal stabilized portion of the VLP curve, then the well is SHUT or STOPPED depending on the AUTO parameter on the WELSPECS keyword. This option is specific to the commercial simulator’s VFPi program that can generate VFPF tables where the unstable part of the VFP curves to the left of the minimum is replaced with a horizontal line at the minimum BHP value. This option is not supported by OPM Flow.","units":{},"default":"NO","value_type":"STRING"},{"index":4,"name":"CONTROL","description":"A defined character string that defines the behavior of rate control wells operating on the unstabilized portion of the VFP table, and should be set to one of the following character strings: NO: This option does not prevent changes to a well’s operating mode when the well is constrained to be operating on the unstabilized portion of the VFP table. This option may cause the well control to oscillate between rate and THP control during the Newton/Linear iterations. YES1: For this option the well is prevented from changing from rate control to THP control provided it can produce at a higher rate under THP control. In this case the well will continue to produce at the required rate even though the calculated THP may be below the well’s minimum THP value. Note however, the well will still be allowed to die if the IPR does not intersect the VFP curve. In the commercial simulator this option will also print a message the first time a well is prevented from changing its control mode, whereas OPM Flow always prints a message every time a well is prevented from changing its control mode. YES2: This option behaves the same as the YES1 option, except a message is printed every time a well is prevented from changing its control mode. The default value of NO allows wells to die when they are constrained by a lower rate that forces them to operate on the unstable section of the VFP curve. This can occur if a well’s rate is being set to match its group target rate or constraint limit. Using either the YES1 or YES2 option will help prevent the \"hunting between control modes\" issue or the well prematurely being shut-in.","units":{},"default":"NO","value_type":"STRING"},{"index":5,"name":"EXTRAP","description":"The EXTRAP parameter is a defined character string in the commercial composition simulator that declares how the extrapolation of a well’s gas fraction, water fraction, and ALQ values is to be conducted. This option is not supported by OPM Flow.","units":{},"default":"WG","value_type":"STRING"}],"example":"The following example defines two oil wells using the WELSPECS and WCONPROD keywords, together with the WVFPEXP keyword that declares how the VFPPROD table lookup should be performed.\n--\n-- WELL SPECIFICATION DATA\n--\n-- WELL GROUP LOCATION BHP PHASE DRAIN INFLOW SHUT CROSS PRESS\n-- NAME NAME I J DEPTH FLUID AREA EQUA. IN FLOW TABLE\nWELSPECS\nOP01 PLATFORM 14 13 1* OIL 1* STD SHUT NO 1* /\nOP02 PLATFORM 28 96 1* OIL 1* STD SHUT NO 1* /\n/\n--\n-- WELL PRODUCTION WELL CONTROLS\n--\n-- WELL OPEN/ CNTL OIL WAT GAS LIQ RES BHP THP VFP VFP\n-- NAME SHUT MODE RATE RATE RATE RATE RATE PRES PRES TABLE ALFQ\nWCONPROD\nOP01 SHUT GRUP 1* 1* 1* 1* 1* 500.0 100.0 1 /\nOP02 SHUT GRUP 1* 1* 1* 1* 1* 500.0 100.0 1 /\n/\n--\n-- WELL OPTIONS FOR PROBLEMATIC THP CONTROLLED WELLS\n--\n-- WELL IMP CLSE RATE VFP\n-- NAME EXP WELL CNTL EXT\nWVFPEXP\n'OP* ' 1* 1* YES1 1* /\n/\nHere both wells are declared as initially shut on the WELSPECS keyword and use VFPPROD table number one as declared on the WCONPROD keyword. The WVFPEXP keyword declares all wells with a name beginning with OP to use implicit lookup and the wells are prevented from changing from rate control to THP control provided they can produce at a higher rate under THP control.","expected_columns":5,"size_kind":"list"},"WWPAVE":{"name":"WWPAVE","sections":["SCHEDULE"],"supported":true,"summary":"The WWPAVE keyword defines the method and parameters for calculating a well’s block average pressures for individual wells that can be written to the SUMMARY and RSM files via the WBP, WBP4, WBP5 and WBP9 vectors in the SUMMARY section. The resulting average pressure can be written out to the summary file in order to compared with field observed data. The keyword is similar to the WPAVE keyword in the SCHEDULE section that has similar functionality, but is applied to all wells in the model.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well average pressure calculation parameters are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"WPAVE1","description":"A real dimensionless value that defines the weighting factor between the inner block and the surrounding blocks used in the calculation of the connection factor weighted average pressure. If WPAVE1 is greater than or equal to zero and less than or equal to one, then the average pressure for each well connection is calculated based on this weighting factor. A value of zero indicates only the surrounding blocks should be used in the calculation; and a value of one indicates only the inner blocks should be used. If WPAVE1 is less than zero, then the average pressure for each well connection is weighted based on the pore volumes of the inner and surrounding blocks.","units":{},"default":"0.5","value_type":"DOUBLE"},{"index":3,"name":"WPAVE2","description":"A real dimensionless value greater than or equal to zero and less than or equal to one, that defines the weighting factor between the connection weighted average pressures and the pore volume weighted average pressures. If WPAVE2 is equal to one, then the average pressures are calculate based only using the connection factor calculated pressures. If WPAVE2 is equal to zero, then average pressures are calculate based on only using the pore volumes calculated pressures.","units":{},"default":"1.0","value_type":"DOUBLE"},{"index":4,"name":"WPAVE3","description":"A defined character string that determines how the hydrostatic head calculation is performed in correcting the pressures to the BHP reference depth on the WELSPECS or WPAVEDEP keywords in the SCHEDULE section. WPAVE3 should be set to one of the following character strings: WELL: the hydrostatic head is calculated using the density of the fluid in the wellbore at the well connections. RES: he hydrostatic head is calculated using the density of the fluid in the reservoir with well connections and averaged over the connections. NONE: no hydrostatic correction is applied to the pressures.","units":{},"default":"WELL","value_type":"STRING","options":["WELL","RES","NONE"]},{"index":5,"name":"WPAVE4","description":"A defined character string that determines which connections should be used in the calculations, WPAVE4 should be set to one of the following character strings: OPEN: only open connections and associated grid blocks should be used in the calculations. This option may result in pressure discontinuities if connections are opened and closed during the run. ALL: all currently defined open and closed connections and associated grid blocks are used in the calculations. The pressure discontinuities issue mentioned above can be avoided with this option and defining all the well connections for a well at the beginning of the run. Only the OPEN option is currently supported by the simulator.","units":{},"default":"OPEN","value_type":"STRING","options":["OPEN","ALL"]}],"example":"The following example defines the default well block average pressure calculation parameters for three oil wells: OP01, OP02 and OP03.\n--\n-- DEFINE WELL BLOCK AVERAGE PRESSURE CALCULATION PARAMETERS\n--\n-- WELL INNER PORV WELL OPEN\n-- NAME OUTER CONN RES ALL\nWWPAVE\nOP01 0.5 1.0 WELL ALL /\nOP02 0.5 1.0 WELL ALL /\nOP03 0.5 1.0 1* 1* /\nAnd the next example shows the parameters used in the Norne model.\n--\n-- DEFINE WELL BLOCK AVERAGE PRESSURE CALCULATION PARAMETERS\n--\n-- WELL INNER PORV WELL OPEN\n-- NAME OUTER CONN RES ALL\nWPAVE\nOP01 1* 0.0 WELL ALL /\nOP02 1* 0.0 WELL ALL /\nOP03 1* 0.0 WELL ALL /\nHere only pore volume weighting is used instead of connection weighting.","expected_columns":5,"size_kind":"list"},"ZIPP2OFF":{"name":"ZIPP2OFF","sections":["SCHEDULE"],"supported":false,"summary":"The ZIPP2OFF keyword deactivates the commercial simulator’s alternative automatic time step selection algorithm that assumes no prior knowledge of the problem, as opposed to the standard time step algorithm that is controlled via the TUNING keyword in the SCHEDULE section, combined with posterior knowledge gained from previous time steps.","parameters":[],"example":"","size_kind":"none","size_count":0},"ZIPPY2":{"name":"ZIPPY2","sections":["SCHEDULE"],"supported":false,"summary":"The ZIPPY2 keyword activates the commercial simulator’s alternative automatic time step selection algorithm that assumes no prior knowledge of the problem, as opposed to the standard time step algorithm that is controlled via the TUNNING keyword in the SCHEDULE section, combined with posterior knowledge gained from previous time steps.","parameters":[{"index":1,"name":"SETTINGS","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","size_kind":"fixed","size_count":1,"variadic_record":true},"FAQR":{"name":"FAQR","sections":["SUMMARY"],"supported":null,"summary":"Aquifer Influx Rate (Water Aquifers)","parameters":[],"example":"","size_kind":"none"},"AAQR":{"name":"AAQR","sections":["SUMMARY"],"supported":null,"summary":"Aquifer Influx Rate (Water Aquifers)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"ALQR":{"name":"ALQR","sections":["SUMMARY"],"supported":null,"summary":"Aquifer Influx Rate (Water Aquifers)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"ANQR":{"name":"ANQR","sections":["SUMMARY"],"supported":null,"summary":"Aquifer Influx Rate (Water Aquifers)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FAQT":{"name":"FAQT","sections":["SUMMARY"],"supported":null,"summary":"Aquifer Influx Total (Water Aquifers)","parameters":[],"example":"","size_kind":"none"},"AAQT":{"name":"AAQT","sections":["SUMMARY"],"supported":null,"summary":"Aquifer Influx Total (Water Aquifers)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"ALQT":{"name":"ALQT","sections":["SUMMARY"],"supported":null,"summary":"Aquifer Influx Total (Water Aquifers)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"ANQT":{"name":"ANQT","sections":["SUMMARY"],"supported":null,"summary":"Aquifer Influx Total (Water Aquifers)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FAQRG":{"name":"FAQRG","sections":["SUMMARY"],"supported":null,"summary":"Aquifer Influx Rate (Gas Aquifers)","parameters":[],"example":"","size_kind":"none"},"AAQRG":{"name":"AAQRG","sections":["SUMMARY"],"supported":null,"summary":"Aquifer Influx Rate (Gas Aquifers)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"ALQRG":{"name":"ALQRG","sections":["SUMMARY"],"supported":null,"summary":"Aquifer Influx Rate (Gas Aquifers)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FAQTG":{"name":"FAQTG","sections":["SUMMARY"],"supported":null,"summary":"Aquifer Influx Total (Gas Aquifers)","parameters":[],"example":"","size_kind":"none"},"AAQTG":{"name":"AAQTG","sections":["SUMMARY"],"supported":null,"summary":"Aquifer Influx Total (Gas Aquifers)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"ALQTG":{"name":"ALQTG","sections":["SUMMARY"],"supported":null,"summary":"Aquifer Influx Total (Gas Aquifers)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"AAQP":{"name":"AAQP","sections":["SUMMARY"],"supported":null,"summary":"Aquifer Pressure. Water pore volume weighted average","parameters":[],"example":"","size_kind":"fixed","size_count":1},"ANQP":{"name":"ANQP","sections":["SUMMARY"],"supported":null,"summary":"Aquifer Pressure. Water pore volume weighted average","parameters":[],"example":"","size_kind":"fixed","size_count":1},"AAQPD":{"name":"AAQPD","sections":["SUMMARY"],"supported":null,"summary":"Aquifer Carter-Tracy Dimensionless Pressure","parameters":[],"example":"","size_kind":"fixed","size_count":1},"AAQTD":{"name":"AAQTD","sections":["SUMMARY"],"supported":null,"summary":"Aquifer Carter-Tracy Dimensionless Time","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WALQ":{"name":"WALQ","sections":["SUMMARY"],"supported":null,"summary":"Artificial Lift Quantity","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WMVFP":{"name":"WMVFP","sections":["SUMMARY"],"supported":null,"summary":"Artificial Lift and VFP Table Number. Well VFP table number.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"GEFF":{"name":"GEFF","sections":["SUMMARY"],"supported":null,"summary":"Efficiency Factor","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WEFF":{"name":"WEFF","sections":["SUMMARY"],"supported":null,"summary":"Efficiency Factor","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WEFFG":{"name":"WEFFG","sections":["SUMMARY"],"supported":null,"summary":"Efficiency Factor Product. Efficiency factor of the well times the product of all the groups above the well.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FEPR":{"name":"FEPR","sections":["SUMMARY"],"supported":null,"summary":"Energy Production Rate","parameters":[],"example":"","size_kind":"none"},"GEPR":{"name":"GEPR","sections":["SUMMARY"],"supported":null,"summary":"Energy Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WEPR":{"name":"WEPR","sections":["SUMMARY"],"supported":null,"summary":"Energy Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FEPT":{"name":"FEPT","sections":["SUMMARY"],"supported":null,"summary":"Energy Production Total","parameters":[],"example":"","size_kind":"none"},"GEPT":{"name":"GEPT","sections":["SUMMARY"],"supported":null,"summary":"Energy Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WEPT":{"name":"WEPT","sections":["SUMMARY"],"supported":null,"summary":"Energy Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGCR":{"name":"FGCR","sections":["SUMMARY"],"supported":null,"summary":"Gas Consumption Rate","parameters":[],"example":"","size_kind":"none"},"GGCR":{"name":"GGCR","sections":["SUMMARY"],"supported":null,"summary":"Gas Consumption Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGCT":{"name":"FGCT","sections":["SUMMARY"],"supported":null,"summary":"Gas Consumption Total","parameters":[],"example":"","size_kind":"none"},"GGCT":{"name":"GGCT","sections":["SUMMARY"],"supported":null,"summary":"Gas Consumption Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CGFR":{"name":"CGFR","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow Rate. Positive for production and negative for injection.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CGFRL":{"name":"CGFRL","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow Rate. Positive for production and negative for injection.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CGFRF":{"name":"CGFRF","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow Rate (Free)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CGFRS":{"name":"CGFRS","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow Rate (Solution)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CGFRU":{"name":"CGFRU","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow Rate (Upstream). Sum of connection gas flow rates upstream of, and including, this connection.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGIMR":{"name":"FGIMR","sections":["SUMMARY"],"supported":null,"summary":"Gas Import Rate","parameters":[],"example":"","size_kind":"none"},"GGIMR":{"name":"GGIMR","sections":["SUMMARY"],"supported":null,"summary":"Gas Import Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGIMT":{"name":"FGIMT","sections":["SUMMARY"],"supported":null,"summary":"Gas Import Total","parameters":[],"example":"","size_kind":"none"},"GGIMT":{"name":"GGIMT","sections":["SUMMARY"],"supported":null,"summary":"Gas Import Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"GGIGR":{"name":"GGIGR","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Guide Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WGIGR":{"name":"WGIGR","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Guide Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGIR":{"name":"FGIR","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Rate","parameters":[],"example":"","size_kind":"none"},"GGIR":{"name":"GGIR","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WGIR":{"name":"WGIR","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CGIR":{"name":"CGIR","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CGIRL":{"name":"CGIRL","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGIRH":{"name":"FGIRH","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Rate History","parameters":[],"example":"","size_kind":"none"},"GGIRH":{"name":"GGIRH","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Rate History","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WGIRH":{"name":"WGIRH","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Rate History","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGIRT":{"name":"FGIRT","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Rate Target/Limit","parameters":[],"example":"","size_kind":"none"},"GGIRT":{"name":"GGIRT","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Rate Target/Limit","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WGIRT":{"name":"WGIRT","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Rate Target/Limit","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGIT":{"name":"FGIT","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Total","parameters":[],"example":"","size_kind":"none"},"GGIT":{"name":"GGIT","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WGIT":{"name":"WGIT","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CGIT":{"name":"CGIT","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CGITL":{"name":"CGITL","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGITH":{"name":"FGITH","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Total History","parameters":[],"example":"","size_kind":"none"},"GGITH":{"name":"GGITH","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Total History","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WGITH":{"name":"WGITH","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Total History","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGLIR":{"name":"FGLIR","sections":["SUMMARY"],"supported":null,"summary":"Gas Lift Injection Rate. Gas lift gas with group and field total rates based on well efficiency.","parameters":[],"example":"","size_kind":"none"},"GGLIR":{"name":"GGLIR","sections":["SUMMARY"],"supported":null,"summary":"Gas Lift Injection Rate. Gas lift gas with group and field total rates based on well efficiency.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WGLIR":{"name":"WGLIR","sections":["SUMMARY"],"supported":null,"summary":"Gas Lift Injection Rate. Gas lift gas with group and field total rates based on well efficiency.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGLIT":{"name":"FGLIT","sections":["SUMMARY"],"supported":null,"summary":"Gas Lift Injection Total. Gas lift gas with group and field total rates based on well efficiency.","parameters":[],"example":"","size_kind":"none"},"GGLIT":{"name":"GGLIT","sections":["SUMMARY"],"supported":null,"summary":"Gas Lift Injection Total. Gas lift gas with group and field total rates based on well efficiency.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WGLIT":{"name":"WGLIT","sections":["SUMMARY"],"supported":null,"summary":"Gas Lift Injection Total. Gas lift gas with group and field total rates based on well efficiency.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGPI":{"name":"FGPI","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Injection Rate. Also WGIP for WGPI.","parameters":[],"example":"","size_kind":"none"},"GGPI":{"name":"GGPI","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Injection Rate. Also WGIP for WGPI.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WGPI":{"name":"WGPI","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Injection Rate. Also WGIP for WGPI.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CGPI":{"name":"CGPI","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Injection Rate. Also WGIP for WGPI.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGPI2":{"name":"FGPI2","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Injection Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"none"},"GGPI2":{"name":"GGPI2","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Injection Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WGPI2":{"name":"WGPI2","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Injection Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGPP":{"name":"FGPP","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Production Rate","parameters":[],"example":"","size_kind":"none"},"GGPP":{"name":"GGPP","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WGPP":{"name":"WGPP","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CGPP":{"name":"CGPP","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGPP2":{"name":"FGPP2","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Production Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"none"},"GGPP2":{"name":"GGPP2","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Production Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WGPP2":{"name":"WGPP2","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Production Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGPPF":{"name":"FGPPF","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Production Rate (Free)","parameters":[],"example":"","size_kind":"none"},"GGPPF":{"name":"GGPPF","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Production Rate (Free)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WGPPF":{"name":"WGPPF","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Production Rate (Free)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGPPF2":{"name":"FGPPF2","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Production Rate (Free). Including shut and stopped wells.","parameters":[],"example":"","size_kind":"none"},"GGPPF2":{"name":"GGPPF2","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Production Rate (Free). Including shut and stopped wells.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WGPPF2":{"name":"WGPPF2","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Production Rate (Free). Including shut and stopped wells.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGPPS":{"name":"FGPPS","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Production Rate (Soln)","parameters":[],"example":"","size_kind":"none"},"GGPPS":{"name":"GGPPS","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Production Rate (Soln)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WGPPS":{"name":"WGPPS","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Production Rate (Soln)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGPPS2":{"name":"FGPPS2","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Production Rate (Soln). Including shut and stopped wells.","parameters":[],"example":"","size_kind":"none"},"GGPPS2":{"name":"GGPPS2","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Production Rate (Soln). Including shut and stopped wells.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WGPPS2":{"name":"WGPPS2","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Production Rate (Soln). Including shut and stopped wells.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"GGPGR":{"name":"GGPGR","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Guide Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WGPGR":{"name":"WGPGR","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Guide Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGPR":{"name":"FGPR","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Rate. Produced reservoir gas only, gas lift gas excluded.","parameters":[],"example":"","size_kind":"none"},"GGPR":{"name":"GGPR","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Rate. Produced reservoir gas only, gas lift gas excluded.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WGPR":{"name":"WGPR","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Rate. Produced reservoir gas only, gas lift gas excluded.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CGPR":{"name":"CGPR","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Rate. Produced reservoir gas only, gas lift gas excluded.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGPRF":{"name":"FGPRF","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Rate (Free)","parameters":[],"example":"","size_kind":"none"},"GGPRF":{"name":"GGPRF","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Rate (Free)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WGPRF":{"name":"WGPRF","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Rate (Free)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGPRS":{"name":"FGPRS","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Rate (Solution)","parameters":[],"example":"","size_kind":"none"},"GGPRS":{"name":"GGPRS","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Rate (Solution)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WGPRS":{"name":"WGPRS","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Rate (Solution)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGPRH":{"name":"FGPRH","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Rate History","parameters":[],"example":"","size_kind":"none"},"GGPRH":{"name":"GGPRH","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Rate History","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WGPRH":{"name":"WGPRH","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Rate History","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGPRT":{"name":"FGPRT","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Rate Target/Limit","parameters":[],"example":"","size_kind":"none"},"GGPRT":{"name":"GGPRT","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Rate Target/Limit","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WGPRT":{"name":"WGPRT","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Rate Target/Limit","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGPT":{"name":"FGPT","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Total","parameters":[],"example":"","size_kind":"none"},"GGPT":{"name":"GGPT","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WGPT":{"name":"WGPT","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CGPT":{"name":"CGPT","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CGPTL":{"name":"CGPTL","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGPTF":{"name":"FGPTF","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Total (Free)","parameters":[],"example":"","size_kind":"none"},"GGPTF":{"name":"GGPTF","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Total (Free)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WGPTF":{"name":"WGPTF","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Total (Free)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGPTS":{"name":"FGPTS","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Total (Solution)","parameters":[],"example":"","size_kind":"none"},"GGPTS":{"name":"GGPTS","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Total (Solution)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WGPTS":{"name":"WGPTS","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Total (Solution)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGPTH":{"name":"FGPTH","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Total History","parameters":[],"example":"","size_kind":"none"},"GGPTH":{"name":"GGPTH","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Total History","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WGPTH":{"name":"WGPTH","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Total History","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGSR":{"name":"FGSR","sections":["SUMMARY"],"supported":null,"summary":"Gas Sales Rate","parameters":[],"example":"","size_kind":"none"},"GGSR":{"name":"GGSR","sections":["SUMMARY"],"supported":null,"summary":"Gas Sales Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FSGR":{"name":"FSGR","sections":["SUMMARY"],"supported":null,"summary":"Gas Sales Rate. Same as GSR.","parameters":[],"example":"","size_kind":"none"},"GSGR":{"name":"GSGR","sections":["SUMMARY"],"supported":null,"summary":"Gas Sales Rate. Same as GSR.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGST":{"name":"FGST","sections":["SUMMARY"],"supported":null,"summary":"Gas Sales Total","parameters":[],"example":"","size_kind":"none"},"GGST":{"name":"GGST","sections":["SUMMARY"],"supported":null,"summary":"Gas Sales Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FSGT":{"name":"FSGT","sections":["SUMMARY"],"supported":null,"summary":"Gas Sales Total. Same as GST.","parameters":[],"example":"","size_kind":"none"},"GSGT":{"name":"GSGT","sections":["SUMMARY"],"supported":null,"summary":"Gas Sales Total. Same as GST.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WGVIR":{"name":"WGVIR","sections":["SUMMARY"],"supported":null,"summary":"Gas Voidage Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WGVPR":{"name":"WGVPR","sections":["SUMMARY"],"supported":null,"summary":"Gas Voidage Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CLFR":{"name":"CLFR","sections":["SUMMARY"],"supported":null,"summary":"Liquid Flow Rate. Positive for production and negative for injection.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CLFRL":{"name":"CLFRL","sections":["SUMMARY"],"supported":null,"summary":"Liquid Flow Rate. Positive for production and negative for injection.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FLPR":{"name":"FLPR","sections":["SUMMARY"],"supported":null,"summary":"Liquid Production Rate","parameters":[],"example":"","size_kind":"none"},"GLPR":{"name":"GLPR","sections":["SUMMARY"],"supported":null,"summary":"Liquid Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WLPR":{"name":"WLPR","sections":["SUMMARY"],"supported":null,"summary":"Liquid Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CLPR":{"name":"CLPR","sections":["SUMMARY"],"supported":null,"summary":"Liquid Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FLPRH":{"name":"FLPRH","sections":["SUMMARY"],"supported":null,"summary":"Liquid Production Rate History","parameters":[],"example":"","size_kind":"none"},"GLPRH":{"name":"GLPRH","sections":["SUMMARY"],"supported":null,"summary":"Liquid Production Rate History","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WLPRH":{"name":"WLPRH","sections":["SUMMARY"],"supported":null,"summary":"Liquid Production Rate History","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FLPRT":{"name":"FLPRT","sections":["SUMMARY"],"supported":null,"summary":"Liquid Production Rate Target/Limit","parameters":[],"example":"","size_kind":"none"},"GLPRT":{"name":"GLPRT","sections":["SUMMARY"],"supported":null,"summary":"Liquid Production Rate Target/Limit","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WLPRT":{"name":"WLPRT","sections":["SUMMARY"],"supported":null,"summary":"Liquid Production Rate Target/Limit","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FLPT":{"name":"FLPT","sections":["SUMMARY"],"supported":null,"summary":"Liquid Production Total","parameters":[],"example":"","size_kind":"none"},"GLPT":{"name":"GLPT","sections":["SUMMARY"],"supported":null,"summary":"Liquid Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WLPT":{"name":"WLPT","sections":["SUMMARY"],"supported":null,"summary":"Liquid Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CLPT":{"name":"CLPT","sections":["SUMMARY"],"supported":null,"summary":"Liquid Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CLPTL":{"name":"CLPTL","sections":["SUMMARY"],"supported":null,"summary":"Liquid Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FLPTH":{"name":"FLPTH","sections":["SUMMARY"],"supported":null,"summary":"Liquid Production Total History","parameters":[],"example":"","size_kind":"none"},"GLPTH":{"name":"GLPTH","sections":["SUMMARY"],"supported":null,"summary":"Liquid Production Total History","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WLPTH":{"name":"WLPTH","sections":["SUMMARY"],"supported":null,"summary":"Liquid Production Total History","parameters":[],"example":"","size_kind":"fixed","size_count":1},"COFR":{"name":"COFR","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow Rate. Positive for production and negative for injection.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"COFRL":{"name":"COFRL","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow Rate. Positive for production and negative for injection.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"COFRF":{"name":"COFRF","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow Rate (Free)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"COFRS":{"name":"COFRS","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow Rate (Solution)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"COFRU":{"name":"COFRU","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow Rate (Upstream). Sum of connection oil flow rates upstream of, and including this connection.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"GOIGR":{"name":"GOIGR","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Guide Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WOIGR":{"name":"WOIGR","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Guide Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FOIR":{"name":"FOIR","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Rate","parameters":[],"example":"","size_kind":"none"},"GOIR":{"name":"GOIR","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WOIR":{"name":"WOIR","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"COIR":{"name":"COIR","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"COIRL":{"name":"COIRL","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FOIRH":{"name":"FOIRH","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Rate History","parameters":[],"example":"","size_kind":"none"},"GOIRH":{"name":"GOIRH","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Rate History","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WOIRH":{"name":"WOIRH","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Rate History","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FOIRT":{"name":"FOIRT","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Rate Target/Limit","parameters":[],"example":"","size_kind":"none"},"GOIRT":{"name":"GOIRT","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Rate Target/Limit","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WOIRT":{"name":"WOIRT","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Rate Target/Limit","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FOIT":{"name":"FOIT","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Total","parameters":[],"example":"","size_kind":"none"},"GOIT":{"name":"GOIT","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WOIT":{"name":"WOIT","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"COIT":{"name":"COIT","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"COITL":{"name":"COITL","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FOITH":{"name":"FOITH","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Total History","parameters":[],"example":"","size_kind":"none"},"GOITH":{"name":"GOITH","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Total History","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WOITH":{"name":"WOITH","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Total History","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FOPI":{"name":"FOPI","sections":["SUMMARY"],"supported":null,"summary":"Oil Potential Injection Rate","parameters":[],"example":"","size_kind":"none"},"GOPI":{"name":"GOPI","sections":["SUMMARY"],"supported":null,"summary":"Oil Potential Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WOPI":{"name":"WOPI","sections":["SUMMARY"],"supported":null,"summary":"Oil Potential Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FOPI2":{"name":"FOPI2","sections":["SUMMARY"],"supported":null,"summary":"Oil Potential Injection Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"none"},"GOPI2":{"name":"GOPI2","sections":["SUMMARY"],"supported":null,"summary":"Oil Potential Injection Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WOPI2":{"name":"WOPI2","sections":["SUMMARY"],"supported":null,"summary":"Oil Potential Injection Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FOPP":{"name":"FOPP","sections":["SUMMARY"],"supported":null,"summary":"Oil Potential Production Rate","parameters":[],"example":"","size_kind":"none"},"GOPP":{"name":"GOPP","sections":["SUMMARY"],"supported":null,"summary":"Oil Potential Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WOPP":{"name":"WOPP","sections":["SUMMARY"],"supported":null,"summary":"Oil Potential Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"COPP":{"name":"COPP","sections":["SUMMARY"],"supported":null,"summary":"Oil Potential Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FOPP2":{"name":"FOPP2","sections":["SUMMARY"],"supported":null,"summary":"Oil Potential Production Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"none"},"GOPP2":{"name":"GOPP2","sections":["SUMMARY"],"supported":null,"summary":"Oil Potential Production Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WOPP2":{"name":"WOPP2","sections":["SUMMARY"],"supported":null,"summary":"Oil Potential Production Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"GOPGR":{"name":"GOPGR","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Guide Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WOPGR":{"name":"WOPGR","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Guide Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FOPR":{"name":"FOPR","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Rate","parameters":[],"example":"","size_kind":"none"},"GOPR":{"name":"GOPR","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WOPR":{"name":"WOPR","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"COPR":{"name":"COPR","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FOPRF":{"name":"FOPRF","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Rate (Free)","parameters":[],"example":"","size_kind":"none"},"GOPRF":{"name":"GOPRF","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Rate (Free)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WOPRF":{"name":"WOPRF","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Rate (Free)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FOPRS":{"name":"FOPRS","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Rate (Solution)","parameters":[],"example":"","size_kind":"none"},"GOPRS":{"name":"GOPRS","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Rate (Solution)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WOPRS":{"name":"WOPRS","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Rate (Solution)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FOPRH":{"name":"FOPRH","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Rate History","parameters":[],"example":"","size_kind":"none"},"GOPRH":{"name":"GOPRH","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Rate History","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WOPRH":{"name":"WOPRH","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Rate History","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FOPRT":{"name":"FOPRT","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Rate Target/Limit","parameters":[],"example":"","size_kind":"none"},"GOPRT":{"name":"GOPRT","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Rate Target/Limit","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WOPRT":{"name":"WOPRT","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Rate Target/Limit","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FOPT":{"name":"FOPT","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total","parameters":[],"example":"","size_kind":"none"},"GOPT":{"name":"GOPT","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WOPT":{"name":"WOPT","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FOPTF":{"name":"FOPTF","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total (Free)","parameters":[],"example":"","size_kind":"none"},"GOPTF":{"name":"GOPTF","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total (Free)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WOPTF":{"name":"WOPTF","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total (Free)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FOPTS":{"name":"FOPTS","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total (Solution)","parameters":[],"example":"","size_kind":"none"},"GOPTS":{"name":"GOPTS","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total (Solution)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WOPTS":{"name":"WOPTS","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total (Solution)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FOPTH":{"name":"FOPTH","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total History","parameters":[],"example":"","size_kind":"none"},"GOPTH":{"name":"GOPTH","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total History","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WOPTH":{"name":"WOPTH","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total History","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CVFR":{"name":"CVFR","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Flow Rate. Positive for production and negative for injection.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CVFRL":{"name":"CVFRL","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Flow Rate. Positive for production and negative for injection.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CVFRF":{"name":"CVFRF","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Flow Rate (Free)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"GVIGR":{"name":"GVIGR","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Injection Guide Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WVIGR":{"name":"WVIGR","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Injection Guide Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FVIR":{"name":"FVIR","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Injection Rate","parameters":[],"example":"","size_kind":"none"},"GVIR":{"name":"GVIR","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WVIR":{"name":"WVIR","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CVIR":{"name":"CVIR","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CVIRL":{"name":"CVIRL","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FVIRT":{"name":"FVIRT","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Injection Rate Target/Limit","parameters":[],"example":"","size_kind":"none"},"GVIRT":{"name":"GVIRT","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Injection Rate Target/Limit","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WVIRT":{"name":"WVIRT","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Injection Rate Target/Limit","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FVIT":{"name":"FVIT","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Injection Total","parameters":[],"example":"","size_kind":"none"},"GVIT":{"name":"GVIT","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WVIT":{"name":"WVIT","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CVIT":{"name":"CVIT","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CVITL":{"name":"CVITL","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FVPI":{"name":"FVPI","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Potential Injection Rate","parameters":[],"example":"","size_kind":"none"},"GVPI":{"name":"GVPI","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Potential Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WVPI":{"name":"WVPI","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Potential Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FVPI2":{"name":"FVPI2","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Potential Injection Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"none"},"GVPI2":{"name":"GVPI2","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Potential Injection Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WVPI2":{"name":"WVPI2","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Potential Injection Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FVPP":{"name":"FVPP","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Potential Production Rate","parameters":[],"example":"","size_kind":"none"},"GVPP":{"name":"GVPP","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Potential Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WVPP":{"name":"WVPP","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Potential Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CVPP":{"name":"CVPP","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Potential Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FVPP2":{"name":"FVPP2","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Potential Production Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"none"},"GVPP2":{"name":"GVPP2","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Potential Production Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WVPP2":{"name":"WVPP2","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Potential Production Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"GVPGR":{"name":"GVPGR","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Production Guide Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WVPGR":{"name":"WVPGR","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Production Guide Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FVPR":{"name":"FVPR","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Production Rate","parameters":[],"example":"","size_kind":"none"},"GVPR":{"name":"GVPR","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WVPR":{"name":"WVPR","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CVPR":{"name":"CVPR","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FVPRT":{"name":"FVPRT","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Production Rate Target/Limit","parameters":[],"example":"","size_kind":"none"},"GVPRT":{"name":"GVPRT","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Production Rate Target/Limit","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WVPRT":{"name":"WVPRT","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Production Rate Target/Limit","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FVPT":{"name":"FVPT","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Production Total","parameters":[],"example":"","size_kind":"none"},"GVPT":{"name":"GVPT","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WVPT":{"name":"WVPT","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CVPT":{"name":"CVPT","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CWFR":{"name":"CWFR","sections":["SUMMARY"],"supported":null,"summary":"Water Flow Rate. Positive for production and negative for injection.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CWFRL":{"name":"CWFRL","sections":["SUMMARY"],"supported":null,"summary":"Water Flow Rate. Positive for production and negative for injection.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CWFRU":{"name":"CWFRU","sections":["SUMMARY"],"supported":null,"summary":"Water Flow Rate (Upstream). Sum of connection water flow rates upstream of, and including, this connection.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"GWIGR":{"name":"GWIGR","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Guide Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WWIGR":{"name":"WWIGR","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Guide Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FWIR":{"name":"FWIR","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Rate","parameters":[],"example":"","size_kind":"none"},"GWIR":{"name":"GWIR","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WWIR":{"name":"WWIR","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CWIR":{"name":"CWIR","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CWIRL":{"name":"CWIRL","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FWIRH":{"name":"FWIRH","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Rate History","parameters":[],"example":"","size_kind":"none"},"GWIRH":{"name":"GWIRH","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Rate History","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WWIRH":{"name":"WWIRH","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Rate History","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FWIRT":{"name":"FWIRT","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Rate Target/Limit","parameters":[],"example":"","size_kind":"none"},"GWIRT":{"name":"GWIRT","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Rate Target/Limit","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WWIRT":{"name":"WWIRT","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Rate Target/Limit","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FWIT":{"name":"FWIT","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Total","parameters":[],"example":"","size_kind":"none"},"GWIT":{"name":"GWIT","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WWIT":{"name":"WWIT","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CWIT":{"name":"CWIT","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CWITL":{"name":"CWITL","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FWITH":{"name":"FWITH","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Total History","parameters":[],"example":"","size_kind":"none"},"GWITH":{"name":"GWITH","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Total History","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WWITH":{"name":"WWITH","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Total History","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FWPI":{"name":"FWPI","sections":["SUMMARY"],"supported":null,"summary":"Water Potential Injection Rate. Also WWIP for WWPI.","parameters":[],"example":"","size_kind":"none"},"GWPI":{"name":"GWPI","sections":["SUMMARY"],"supported":null,"summary":"Water Potential Injection Rate. Also WWIP for WWPI.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WWPI":{"name":"WWPI","sections":["SUMMARY"],"supported":null,"summary":"Water Potential Injection Rate. Also WWIP for WWPI.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FWPI2":{"name":"FWPI2","sections":["SUMMARY"],"supported":null,"summary":"Water Potential Injection Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"none"},"GWPI2":{"name":"GWPI2","sections":["SUMMARY"],"supported":null,"summary":"Water Potential Injection Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WWPI2":{"name":"WWPI2","sections":["SUMMARY"],"supported":null,"summary":"Water Potential Injection Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FWPP":{"name":"FWPP","sections":["SUMMARY"],"supported":null,"summary":"Water Potential Production Rate","parameters":[],"example":"","size_kind":"none"},"GWPP":{"name":"GWPP","sections":["SUMMARY"],"supported":null,"summary":"Water Potential Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WWPP":{"name":"WWPP","sections":["SUMMARY"],"supported":null,"summary":"Water Potential Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CWPP":{"name":"CWPP","sections":["SUMMARY"],"supported":null,"summary":"Water Potential Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FWPP2":{"name":"FWPP2","sections":["SUMMARY"],"supported":null,"summary":"Water Potential Production Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"none"},"GWPP2":{"name":"GWPP2","sections":["SUMMARY"],"supported":null,"summary":"Water Potential Production Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WWPP2":{"name":"WWPP2","sections":["SUMMARY"],"supported":null,"summary":"Water Potential Production Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FWPIR":{"name":"FWPIR","sections":["SUMMARY"],"supported":null,"summary":"Water Produce/Injected Ratio. Reported as a percent.","parameters":[],"example":"","size_kind":"none"},"GWPIR":{"name":"GWPIR","sections":["SUMMARY"],"supported":null,"summary":"Water Produce/Injected Ratio. Reported as a percent.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WWPIR":{"name":"WWPIR","sections":["SUMMARY"],"supported":null,"summary":"Water Produce/Injected Ratio. Reported as a percent.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"GWPGR":{"name":"GWPGR","sections":["SUMMARY"],"supported":null,"summary":"Water Production Guide Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WWPGR":{"name":"WWPGR","sections":["SUMMARY"],"supported":null,"summary":"Water Production Guide Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FWPR":{"name":"FWPR","sections":["SUMMARY"],"supported":null,"summary":"Water Production Rate","parameters":[],"example":"","size_kind":"none"},"GWPR":{"name":"GWPR","sections":["SUMMARY"],"supported":null,"summary":"Water Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WWPR":{"name":"WWPR","sections":["SUMMARY"],"supported":null,"summary":"Water Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CWPR":{"name":"CWPR","sections":["SUMMARY"],"supported":null,"summary":"Water Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FWPRH":{"name":"FWPRH","sections":["SUMMARY"],"supported":null,"summary":"Water Production Rate History","parameters":[],"example":"","size_kind":"none"},"GWPRH":{"name":"GWPRH","sections":["SUMMARY"],"supported":null,"summary":"Water Production Rate History","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WWPRH":{"name":"WWPRH","sections":["SUMMARY"],"supported":null,"summary":"Water Production Rate History","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FWPRT":{"name":"FWPRT","sections":["SUMMARY"],"supported":null,"summary":"Water Production Rate Target/Limit","parameters":[],"example":"","size_kind":"none"},"GWPRT":{"name":"GWPRT","sections":["SUMMARY"],"supported":null,"summary":"Water Production Rate Target/Limit","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WWPRT":{"name":"WWPRT","sections":["SUMMARY"],"supported":null,"summary":"Water Production Rate Target/Limit","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FWPT":{"name":"FWPT","sections":["SUMMARY"],"supported":null,"summary":"Water Production Total","parameters":[],"example":"","size_kind":"none"},"GWPT":{"name":"GWPT","sections":["SUMMARY"],"supported":null,"summary":"Water Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WWPT":{"name":"WWPT","sections":["SUMMARY"],"supported":null,"summary":"Water Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CWPT":{"name":"CWPT","sections":["SUMMARY"],"supported":null,"summary":"Water Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CWPTL":{"name":"CWPTL","sections":["SUMMARY"],"supported":null,"summary":"Water Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FWPTH":{"name":"FWPTH","sections":["SUMMARY"],"supported":null,"summary":"Water Production Total History","parameters":[],"example":"","size_kind":"none"},"GWPTH":{"name":"GWPTH","sections":["SUMMARY"],"supported":null,"summary":"Water Production Total History","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WWPTH":{"name":"WWPTH","sections":["SUMMARY"],"supported":null,"summary":"Water Production Total History","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WWVIR":{"name":"WWVIR","sections":["SUMMARY"],"supported":null,"summary":"Water Voidage Injection Guide Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WWVIT":{"name":"WWVIT","sections":["SUMMARY"],"supported":null,"summary":"Water Voidage Injection Guide Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FAMIR":{"name":"FAMIR","sections":["SUMMARY"],"supported":null,"summary":"Water Mass Injection Rate","parameters":[],"example":"","size_kind":"none"},"GAMIR":{"name":"GAMIR","sections":["SUMMARY"],"supported":null,"summary":"Water Mass Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WAMIR":{"name":"WAMIR","sections":["SUMMARY"],"supported":null,"summary":"Water Mass Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CAMIR":{"name":"CAMIR","sections":["SUMMARY"],"supported":null,"summary":"Water Mass Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CAMIRL":{"name":"CAMIRL","sections":["SUMMARY"],"supported":null,"summary":"Water Mass Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FAMIT":{"name":"FAMIT","sections":["SUMMARY"],"supported":null,"summary":"Water Mass Injection Total","parameters":[],"example":"","size_kind":"none"},"GAMIT":{"name":"GAMIT","sections":["SUMMARY"],"supported":null,"summary":"Water Mass Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WAMIT":{"name":"WAMIT","sections":["SUMMARY"],"supported":null,"summary":"Water Mass Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CAMIT":{"name":"CAMIT","sections":["SUMMARY"],"supported":null,"summary":"Water Mass Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CAMITL":{"name":"CAMITL","sections":["SUMMARY"],"supported":null,"summary":"Water Mass Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FAMPR":{"name":"FAMPR","sections":["SUMMARY"],"supported":null,"summary":"Water Mass Production Rate","parameters":[],"example":"","size_kind":"none"},"GAMPR":{"name":"GAMPR","sections":["SUMMARY"],"supported":null,"summary":"Water Mass Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WAMPR":{"name":"WAMPR","sections":["SUMMARY"],"supported":null,"summary":"Water Mass Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CAMPR":{"name":"CAMPR","sections":["SUMMARY"],"supported":null,"summary":"Water Mass Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CAMPRL":{"name":"CAMPRL","sections":["SUMMARY"],"supported":null,"summary":"Water Mass Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FAMPT":{"name":"FAMPT","sections":["SUMMARY"],"supported":null,"summary":"Water Mass Production Total","parameters":[],"example":"","size_kind":"none"},"GAMPT":{"name":"GAMPT","sections":["SUMMARY"],"supported":null,"summary":"Water Mass Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WAMPT":{"name":"WAMPT","sections":["SUMMARY"],"supported":null,"summary":"Water Mass Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CAMPT":{"name":"CAMPT","sections":["SUMMARY"],"supported":null,"summary":"Water Mass Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CAMPTL":{"name":"CAMPTL","sections":["SUMMARY"],"supported":null,"summary":"Water Mass Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FMWIA":{"name":"FMWIA","sections":["SUMMARY"],"supported":null,"summary":"Number of abandoned injection wells","parameters":[],"example":"","size_kind":"none"},"GMWIA":{"name":"GMWIA","sections":["SUMMARY"],"supported":null,"summary":"Number of abandoned injection wells","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FMWPA":{"name":"FMWPA","sections":["SUMMARY"],"supported":null,"summary":"Number of abandoned production wells","parameters":[],"example":"","size_kind":"none"},"GMWPA":{"name":"GMWPA","sections":["SUMMARY"],"supported":null,"summary":"Number of abandoned production wells","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FMWDT":{"name":"FMWDT","sections":["SUMMARY"],"supported":null,"summary":"Number of drilling events in total","parameters":[],"example":"","size_kind":"none"},"GMWDT":{"name":"GMWDT","sections":["SUMMARY"],"supported":null,"summary":"Number of drilling events in total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FMWDR":{"name":"FMWDR","sections":["SUMMARY"],"supported":null,"summary":"Number of drilling events this timestep","parameters":[],"example":"","size_kind":"none"},"GMWDR":{"name":"GMWDR","sections":["SUMMARY"],"supported":null,"summary":"Number of drilling events this timestep","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FMWIN":{"name":"FMWIN","sections":["SUMMARY"],"supported":null,"summary":"Number of injection wells currently flowing","parameters":[],"example":"","size_kind":"none"},"GMWIN":{"name":"GMWIN","sections":["SUMMARY"],"supported":null,"summary":"Number of injection wells currently flowing","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FMWIG":{"name":"FMWIG","sections":["SUMMARY"],"supported":null,"summary":"Number of injectors on group control","parameters":[],"example":"","size_kind":"none"},"GMWIG":{"name":"GMWIG","sections":["SUMMARY"],"supported":null,"summary":"Number of injectors on group control","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FMWIV":{"name":"FMWIV","sections":["SUMMARY"],"supported":null,"summary":"Number of injectors on own reservoir volume rate limit control","parameters":[],"example":"","size_kind":"none"},"GMWIV":{"name":"GMWIV","sections":["SUMMARY"],"supported":null,"summary":"Number of injectors on own reservoir volume rate limit control","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FMWIS":{"name":"FMWIS","sections":["SUMMARY"],"supported":null,"summary":"Number of injectors on own surface rate limit control","parameters":[],"example":"","size_kind":"none"},"GMWIS":{"name":"GMWIS","sections":["SUMMARY"],"supported":null,"summary":"Number of injectors on own surface rate limit control","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FMWIP":{"name":"FMWIP","sections":["SUMMARY"],"supported":null,"summary":"Number of injectors on pressure control","parameters":[],"example":"","size_kind":"none"},"GMWIP":{"name":"GMWIP","sections":["SUMMARY"],"supported":null,"summary":"Number of injectors on pressure control","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FMWPO":{"name":"FMWPO","sections":["SUMMARY"],"supported":null,"summary":"Number of producers controlled by own oil rate limit","parameters":[],"example":"","size_kind":"none"},"GMWPO":{"name":"GMWPO","sections":["SUMMARY"],"supported":null,"summary":"Number of producers controlled by own oil rate limit","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FMWPG":{"name":"FMWPG","sections":["SUMMARY"],"supported":null,"summary":"Number of producers on group control","parameters":[],"example":"","size_kind":"none"},"GMWPG":{"name":"GMWPG","sections":["SUMMARY"],"supported":null,"summary":"Number of producers on group control","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FMWPV":{"name":"FMWPV","sections":["SUMMARY"],"supported":null,"summary":"Number of producers on own reservoir volume rate limit control","parameters":[],"example":"","size_kind":"none"},"GMWPV":{"name":"GMWPV","sections":["SUMMARY"],"supported":null,"summary":"Number of producers on own reservoir volume rate limit control","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FMWPS":{"name":"FMWPS","sections":["SUMMARY"],"supported":null,"summary":"Number of producers on own surface rate limit control","parameters":[],"example":"","size_kind":"none"},"GMWPS":{"name":"GMWPS","sections":["SUMMARY"],"supported":null,"summary":"Number of producers on own surface rate limit control","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FMWPP":{"name":"FMWPP","sections":["SUMMARY"],"supported":null,"summary":"Number of producers on pressure control","parameters":[],"example":"","size_kind":"none"},"GMWPP":{"name":"GMWPP","sections":["SUMMARY"],"supported":null,"summary":"Number of producers on pressure control","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FMWPL":{"name":"FMWPL","sections":["SUMMARY"],"supported":null,"summary":"Number of producers using artificial lift (with ALQ > 0.0)","parameters":[],"example":"","size_kind":"none"},"GMWPL":{"name":"GMWPL","sections":["SUMMARY"],"supported":null,"summary":"Number of producers using artificial lift (with ALQ > 0.0)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FMWPR":{"name":"FMWPR","sections":["SUMMARY"],"supported":null,"summary":"Number of production wells currently flowing","parameters":[],"example":"","size_kind":"none"},"GMWPR":{"name":"GMWPR","sections":["SUMMARY"],"supported":null,"summary":"Number of production wells currently flowing","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FMWIU":{"name":"FMWIU","sections":["SUMMARY"],"supported":null,"summary":"Number of unused injection wells","parameters":[],"example":"","size_kind":"none"},"GMWIU":{"name":"GMWIU","sections":["SUMMARY"],"supported":null,"summary":"Number of unused injection wells","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FMWPU":{"name":"FMWPU","sections":["SUMMARY"],"supported":null,"summary":"Number of unused production wells","parameters":[],"example":"","size_kind":"none"},"GMWPU":{"name":"GMWPU","sections":["SUMMARY"],"supported":null,"summary":"Number of unused production wells","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FMWWT":{"name":"FMWWT","sections":["SUMMARY"],"supported":null,"summary":"Number of workover events in total","parameters":[],"example":"","size_kind":"none"},"GMWWT":{"name":"GMWWT","sections":["SUMMARY"],"supported":null,"summary":"Number of workover events in total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FMWWO":{"name":"FMWWO","sections":["SUMMARY"],"supported":null,"summary":"Number of workover events this time step.","parameters":[],"example":"","size_kind":"none"},"GMWWO":{"name":"GMWWO","sections":["SUMMARY"],"supported":null,"summary":"Number of workover events this time step.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WMCON":{"name":"WMCON","sections":["SUMMARY"],"supported":null,"summary":"The number of connections capable of flowing in the well","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FMWIT":{"name":"FMWIT","sections":["SUMMARY"],"supported":null,"summary":"Total number of injection wells","parameters":[],"example":"","size_kind":"none"},"GMWIT":{"name":"GMWIT","sections":["SUMMARY"],"supported":null,"summary":"Total number of injection wells","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FMWPT":{"name":"FMWPT","sections":["SUMMARY"],"supported":null,"summary":"Total number of production wells","parameters":[],"example":"","size_kind":"none"},"GMWPT":{"name":"GMWPT","sections":["SUMMARY"],"supported":null,"summary":"Total number of production wells","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CCDBF":{"name":"CCDBF","sections":["SUMMARY"],"supported":null,"summary":"Blocking Factor (GPP)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WBHP":{"name":"WBHP","sections":["SUMMARY"],"supported":null,"summary":"Bottom-Hole Pressure","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WBP5":{"name":"WBP5","sections":["SUMMARY"],"supported":null,"summary":"Bottom-Hole Pressure (Five Point","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WBP4":{"name":"WBP4","sections":["SUMMARY"],"supported":null,"summary":"Bottom-Hole Pressure (Four Point)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WBP9":{"name":"WBP9","sections":["SUMMARY"],"supported":null,"summary":"Bottom-Hole Pressure (Nine Point)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WBP":{"name":"WBP","sections":["SUMMARY"],"supported":null,"summary":"Bottom-Hole Pressure (One Point)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WBHPH":{"name":"WBHPH","sections":["SUMMARY"],"supported":null,"summary":"Bottom-Hole Pressure History","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WBHPT":{"name":"WBHPT","sections":["SUMMARY"],"supported":null,"summary":"Bottom-Hole Pressure Target/Limit","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CPRL":{"name":"CPRL","sections":["SUMMARY"],"supported":null,"summary":"Connection Pressure. Completion pressure is an average pressure for the completion.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CDFAC":{"name":"CDFAC","sections":["SUMMARY"],"supported":null,"summary":"Connection D-Factor","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CTFAC":{"name":"CTFAC","sections":["SUMMARY"],"supported":null,"summary":"Connection Transmissibility Factor","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WPIG":{"name":"WPIG","sections":["SUMMARY"],"supported":null,"summary":"Productivity (Gas Phase)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WPIL":{"name":"WPIL","sections":["SUMMARY"],"supported":null,"summary":"Productivity (Liquid Phase)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WPIO":{"name":"WPIO","sections":["SUMMARY"],"supported":null,"summary":"Productivity (Oil Phase)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WPI5":{"name":"WPI5","sections":["SUMMARY"],"supported":null,"summary":"Productivity (Preferred Phase – Five Point)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WPI4":{"name":"WPI4","sections":["SUMMARY"],"supported":null,"summary":"Productivity (Preferred Phase – Four Point)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WPI9":{"name":"WPI9","sections":["SUMMARY"],"supported":null,"summary":"Productivity (Preferred Phase – Nine Point)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WPI1":{"name":"WPI1","sections":["SUMMARY"],"supported":null,"summary":"Productivity (Preferred Phase – One Point)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WPI":{"name":"WPI","sections":["SUMMARY"],"supported":null,"summary":"Productivity (Preferred Phase)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CPI":{"name":"CPI","sections":["SUMMARY"],"supported":null,"summary":"Productivity (Preferred Phase)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WPIW":{"name":"WPIW","sections":["SUMMARY"],"supported":null,"summary":"Productivity (Water Phase)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WTHP":{"name":"WTHP","sections":["SUMMARY"],"supported":null,"summary":"Tubing Head Pressure","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WTHPH":{"name":"WTHPH","sections":["SUMMARY"],"supported":null,"summary":"Tubing Head Pressure History","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGLR":{"name":"FGLR","sections":["SUMMARY"],"supported":null,"summary":"Gas-Liquid Ratio","parameters":[],"example":"","size_kind":"none"},"GGLR":{"name":"GGLR","sections":["SUMMARY"],"supported":null,"summary":"Gas-Liquid Ratio","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WGLR":{"name":"WGLR","sections":["SUMMARY"],"supported":null,"summary":"Gas-Liquid Ratio","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CGLR":{"name":"CGLR","sections":["SUMMARY"],"supported":null,"summary":"Gas-Liquid Ratio","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CGLRL":{"name":"CGLRL","sections":["SUMMARY"],"supported":null,"summary":"Gas-Liquid Ratio","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WBGLR":{"name":"WBGLR","sections":["SUMMARY"],"supported":null,"summary":"Gas-Liquid Ratio (Bottom-Hole)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGLRH":{"name":"FGLRH","sections":["SUMMARY"],"supported":null,"summary":"Gas-Liquid Ratio History","parameters":[],"example":"","size_kind":"none"},"GGLRH":{"name":"GGLRH","sections":["SUMMARY"],"supported":null,"summary":"Gas-Liquid Ratio History","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WGLRH":{"name":"WGLRH","sections":["SUMMARY"],"supported":null,"summary":"Gas-Liquid Ratio History","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGOR":{"name":"FGOR","sections":["SUMMARY"],"supported":null,"summary":"Gas-Oil Ratio","parameters":[],"example":"","size_kind":"none"},"GGOR":{"name":"GGOR","sections":["SUMMARY"],"supported":null,"summary":"Gas-Oil Ratio","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WGOR":{"name":"WGOR","sections":["SUMMARY"],"supported":null,"summary":"Gas-Oil Ratio","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CGOR":{"name":"CGOR","sections":["SUMMARY"],"supported":null,"summary":"Gas-Oil Ratio","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CGORL":{"name":"CGORL","sections":["SUMMARY"],"supported":null,"summary":"Gas-Oil Ratio","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGORH":{"name":"FGORH","sections":["SUMMARY"],"supported":null,"summary":"Gas-Oil Ratio History","parameters":[],"example":"","size_kind":"none"},"GGORH":{"name":"GGORH","sections":["SUMMARY"],"supported":null,"summary":"Gas-Oil Ratio History","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WGORH":{"name":"WGORH","sections":["SUMMARY"],"supported":null,"summary":"Gas-Oil Ratio History","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FOGR":{"name":"FOGR","sections":["SUMMARY"],"supported":null,"summary":"Oil-Gas Ratio","parameters":[],"example":"","size_kind":"none"},"GOGR":{"name":"GOGR","sections":["SUMMARY"],"supported":null,"summary":"Oil-Gas Ratio","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WOGR":{"name":"WOGR","sections":["SUMMARY"],"supported":null,"summary":"Oil-Gas Ratio","parameters":[],"example":"","size_kind":"fixed","size_count":1},"COGR":{"name":"COGR","sections":["SUMMARY"],"supported":null,"summary":"Oil-Gas Ratio","parameters":[],"example":"","size_kind":"fixed","size_count":1},"COGRL":{"name":"COGRL","sections":["SUMMARY"],"supported":null,"summary":"Oil-Gas Ratio","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FOGRH":{"name":"FOGRH","sections":["SUMMARY"],"supported":null,"summary":"Oil-Gas Ratio History","parameters":[],"example":"","size_kind":"none"},"GOGRH":{"name":"GOGRH","sections":["SUMMARY"],"supported":null,"summary":"Oil-Gas Ratio History","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WOGRH":{"name":"WOGRH","sections":["SUMMARY"],"supported":null,"summary":"Oil-Gas Ratio History","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FWGR":{"name":"FWGR","sections":["SUMMARY"],"supported":null,"summary":"Water -Gas Ratio","parameters":[],"example":"","size_kind":"none"},"GWGR":{"name":"GWGR","sections":["SUMMARY"],"supported":null,"summary":"Water -Gas Ratio","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WWGR":{"name":"WWGR","sections":["SUMMARY"],"supported":null,"summary":"Water -Gas Ratio","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CWGR":{"name":"CWGR","sections":["SUMMARY"],"supported":null,"summary":"Water -Gas Ratio","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CWGRL":{"name":"CWGRL","sections":["SUMMARY"],"supported":null,"summary":"Water -Gas Ratio","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FWCT":{"name":"FWCT","sections":["SUMMARY"],"supported":null,"summary":"Water Cut","parameters":[],"example":"","size_kind":"none"},"GWCT":{"name":"GWCT","sections":["SUMMARY"],"supported":null,"summary":"Water Cut","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WWCT":{"name":"WWCT","sections":["SUMMARY"],"supported":null,"summary":"Water Cut","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CWCT":{"name":"CWCT","sections":["SUMMARY"],"supported":null,"summary":"Water Cut","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CWCTL":{"name":"CWCTL","sections":["SUMMARY"],"supported":null,"summary":"Water Cut","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FWCTH":{"name":"FWCTH","sections":["SUMMARY"],"supported":null,"summary":"Water Cut History","parameters":[],"example":"","size_kind":"none"},"GWCTH":{"name":"GWCTH","sections":["SUMMARY"],"supported":null,"summary":"Water Cut History","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WWCTH":{"name":"WWCTH","sections":["SUMMARY"],"supported":null,"summary":"Water Cut History","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FWGRH":{"name":"FWGRH","sections":["SUMMARY"],"supported":null,"summary":"Water-Gas Ratio History","parameters":[],"example":"","size_kind":"none"},"GWGRH":{"name":"GWGRH","sections":["SUMMARY"],"supported":null,"summary":"Water-Gas Ratio History","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WWGRH":{"name":"WWGRH","sections":["SUMMARY"],"supported":null,"summary":"Water-Gas Ratio History","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FMCTP":{"name":"FMCTP","sections":["SUMMARY"],"supported":null,"summary":"Production Group.","parameters":[],"example":"","size_kind":"none"},"GMCTP":{"name":"GMCTP","sections":["SUMMARY"],"supported":null,"summary":"Production Group.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FMCTW":{"name":"FMCTW","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Group.","parameters":[],"example":"","size_kind":"none"},"GMCTW":{"name":"GMCTW","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Group.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FMCTG":{"name":"FMCTG","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Group.","parameters":[],"example":"","size_kind":"none"},"GMCTG":{"name":"GMCTG","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Group.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WSTAT":{"name":"WSTAT","sections":["SUMMARY"],"supported":null,"summary":"Well Status indicator.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WMCTL":{"name":"WMCTL","sections":["SUMMARY"],"supported":null,"summary":"Well Mode of Control indicator.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BFLOGI":{"name":"BFLOGI","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow (Inter-Block in I+ Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BFLOGI-":{"name":"BFLOGI-","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow (Inter-Block in I- Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BFLOGJ":{"name":"BFLOGJ","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow (Inter-Block in J+ Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BFLOGJ-":{"name":"BFLOGJ-","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow (Inter-Block in J- Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BFLOGK":{"name":"BFLOGK","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow (Inter-Block in K+ Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BFLOGK-":{"name":"BFLOGK-","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow (Inter-Block in K- Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"RGFR":{"name":"RGFR","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow Rate Inter-Region. OPM Flow implementation.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"RGFR+":{"name":"RGFR+","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow Rate Inter-Region (Positive Contribution)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"RGFR-":{"name":"RGFR-","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow Rate Inter-Region (Negative Contribution)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"RGFT":{"name":"RGFT","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow Total Inter-Region (Liquid and Gas Phases)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"RGFT+":{"name":"RGFT+","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow Total Inter-Region (+VE Liquid and Gas Phases). OPM Flow Implementation","parameters":[],"example":"","size_kind":"fixed","size_count":1},"RGFT-":{"name":"RGFT-","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow Total Inter-Region (-VE Liquid and Gas Phases)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"RGFTG":{"name":"RGFTG","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow Total Inter-Region (Gas Phase)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"RGFTL":{"name":"RGFTL","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow Total Inter-Region (Liquid Phase)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"RGIR":{"name":"RGIR","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"RGIT":{"name":"RGIT","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FPPG":{"name":"FPPG","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential","parameters":[],"example":"","size_kind":"none"},"RPPG":{"name":"RPPG","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BPPG":{"name":"BPPG","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential","parameters":[],"example":"","size_kind":"fixed","size_count":1},"RGPR":{"name":"RGPR","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"RGPRF":{"name":"RGPRF","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Rate (Free)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"RGPRS":{"name":"RGPRS","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Rate (Solution)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"RGPT":{"name":"RGPT","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Total. Liquid and gas phases","parameters":[],"example":"","size_kind":"fixed","size_count":1},"RGPTF":{"name":"RGPTF","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Total (Free)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"RGP":{"name":"RGP","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Total (Net From Region). Minus injected gas.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"RGPTS":{"name":"RGPTS","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Total (Solution)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BVELGI":{"name":"BVELGI","sections":["SUMMARY"],"supported":null,"summary":"Gas Velocity (Inter-Block in I+ Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BVELGI-":{"name":"BVELGI-","sections":["SUMMARY"],"supported":null,"summary":"Gas Velocity (Inter-Block in I- Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BVELGJ":{"name":"BVELGJ","sections":["SUMMARY"],"supported":null,"summary":"Gas Velocity (Inter-Block in J+ Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BVELGJ-":{"name":"BVELGJ-","sections":["SUMMARY"],"supported":null,"summary":"Gas Velocity (Inter-Block in J- Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BVELGK":{"name":"BVELGK","sections":["SUMMARY"],"supported":null,"summary":"Gas Velocity (Inter-Block in K+ Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BVELGK-":{"name":"BVELGK-","sections":["SUMMARY"],"supported":null,"summary":"Gas Velocity (Inter-Block in K- Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BFLOOI":{"name":"BFLOOI","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow (Inter-Block in I+ Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BFLOOI-":{"name":"BFLOOI-","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow (Inter-Block in I- Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BFLOOJ":{"name":"BFLOOJ","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow (Inter-Block in J+ Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BFLOOJ-":{"name":"BFLOOJ-","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow (Inter-Block in J- Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BFLOOK":{"name":"BFLOOK","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow (Inter-Block in K+ Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BFLOOK-":{"name":"BFLOOK-","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow (Inter-Block in K- Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"ROFR":{"name":"ROFR","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow Rate Inter-Region. OPM Flow implementation.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"ROFR+":{"name":"ROFR+","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow Rate Inter-Region (Positive Contribution)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"ROFR-":{"name":"ROFR-","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow Rate Inter-Region (Negative Contribution)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"ROFT":{"name":"ROFT","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow Total Inter-Region (Liquid and Gas Phases)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"ROFT+":{"name":"ROFT+","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow Total Inter-Region (+VE Liquid and Gas Phases). OPM Flow implementation.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"ROFT-":{"name":"ROFT-","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow Total Inter-Region (-VE Liquid and Gas Phases)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"ROFTG":{"name":"ROFTG","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow Total Inter-Region (Gas Phase)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"ROFTL":{"name":"ROFTL","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow Total Inter-Region (Liquid Phase)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"ROIR":{"name":"ROIR","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"ROIT":{"name":"ROIT","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FPPO":{"name":"FPPO","sections":["SUMMARY"],"supported":null,"summary":"Oil Potential","parameters":[],"example":"","size_kind":"none"},"RPPO":{"name":"RPPO","sections":["SUMMARY"],"supported":null,"summary":"Oil Potential","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BPPO":{"name":"BPPO","sections":["SUMMARY"],"supported":null,"summary":"Oil Potential","parameters":[],"example":"","size_kind":"fixed","size_count":1},"ROPR":{"name":"ROPR","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"ROPT":{"name":"ROPT","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"ROP":{"name":"ROP","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total (Net From Region)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BVELOI":{"name":"BVELOI","sections":["SUMMARY"],"supported":null,"summary":"Oil Velocity (Inter-Block in I+ Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BVELOI-":{"name":"BVELOI-","sections":["SUMMARY"],"supported":null,"summary":"Oil Velocity (Inter-Block in I- Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BVELOJ":{"name":"BVELOJ","sections":["SUMMARY"],"supported":null,"summary":"Oil Velocity (Inter-Block in J+ Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BVELOJ-":{"name":"BVELOJ-","sections":["SUMMARY"],"supported":null,"summary":"Oil Velocity (Inter-Block in J- Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BVELOK":{"name":"BVELOK","sections":["SUMMARY"],"supported":null,"summary":"Oil Velocity (Inter-Block in K+ Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BVELOK-":{"name":"BVELOK-","sections":["SUMMARY"],"supported":null,"summary":"Oil Velocity (Inter-Block in K- Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BFLOWI":{"name":"BFLOWI","sections":["SUMMARY"],"supported":null,"summary":"Water Flow (Inter-Block in I+ Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BFLOWI-":{"name":"BFLOWI-","sections":["SUMMARY"],"supported":null,"summary":"Water Flow (Inter-Block in I- Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BFLOWJ":{"name":"BFLOWJ","sections":["SUMMARY"],"supported":null,"summary":"Water Flow (Inter-Block in J+ Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BFLOWJ-":{"name":"BFLOWJ-","sections":["SUMMARY"],"supported":null,"summary":"Water Flow (Inter-Block in J- Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BFLOWK":{"name":"BFLOWK","sections":["SUMMARY"],"supported":null,"summary":"Water Flow (Inter-Block in K+ Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BFLOWK-":{"name":"BFLOWK-","sections":["SUMMARY"],"supported":null,"summary":"Water Flow (Inter-Block in K- Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"RWFR":{"name":"RWFR","sections":["SUMMARY"],"supported":null,"summary":"Water Flow Rate Inter-Region. OPM Flow implementation.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"RWFR+":{"name":"RWFR+","sections":["SUMMARY"],"supported":null,"summary":"Water Flow Rate Inter-Region","parameters":[],"example":"","size_kind":"fixed","size_count":1},"RWFR-":{"name":"RWFR-","sections":["SUMMARY"],"supported":null,"summary":"Water Flow Rate Inter-Region","parameters":[],"example":"","size_kind":"fixed","size_count":1},"RWFT":{"name":"RWFT","sections":["SUMMARY"],"supported":null,"summary":"Water Flow Total Inter-Region","parameters":[],"example":"","size_kind":"fixed","size_count":1},"RWFT+":{"name":"RWFT+","sections":["SUMMARY"],"supported":null,"summary":"Water Flow Total Inter-Region. OPM Flow implementation.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"RWFT-":{"name":"RWFT-","sections":["SUMMARY"],"supported":null,"summary":"Water Flow Total Inter-Region","parameters":[],"example":"","size_kind":"fixed","size_count":1},"RWIR":{"name":"RWIR","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"RWIT":{"name":"RWIT","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FPPW":{"name":"FPPW","sections":["SUMMARY"],"supported":null,"summary":"Water Potential","parameters":[],"example":"","size_kind":"none"},"RPPW":{"name":"RPPW","sections":["SUMMARY"],"supported":null,"summary":"Water Potential","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BPPW":{"name":"BPPW","sections":["SUMMARY"],"supported":null,"summary":"Water Potential","parameters":[],"example":"","size_kind":"fixed","size_count":1},"RWPR":{"name":"RWPR","sections":["SUMMARY"],"supported":null,"summary":"Water Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"RWPT":{"name":"RWPT","sections":["SUMMARY"],"supported":null,"summary":"Water Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"RWP":{"name":"RWP","sections":["SUMMARY"],"supported":null,"summary":"Water Production Total (Net From Region)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BVELWI":{"name":"BVELWI","sections":["SUMMARY"],"supported":null,"summary":"Water Velocity (Inter-Block in I+ Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BVELWI-":{"name":"BVELWI-","sections":["SUMMARY"],"supported":null,"summary":"Water Velocity (Inter-Block in I- Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BVELWJ":{"name":"BVELWJ","sections":["SUMMARY"],"supported":null,"summary":"Water Velocity (Inter-Block in J+ Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BVELWJ-":{"name":"BVELWJ-","sections":["SUMMARY"],"supported":null,"summary":"Water Velocity (Inter-Block in J- Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BVELWK":{"name":"BVELWK","sections":["SUMMARY"],"supported":null,"summary":"Water Velocity (Inter-Block in K+ Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BVELWK-":{"name":"BVELWK-","sections":["SUMMARY"],"supported":null,"summary":"Water Velocity (Inter-Block in K- Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FAMIP":{"name":"FAMIP","sections":["SUMMARY"],"supported":null,"summary":"Water In-place","parameters":[],"example":"","size_kind":"none"},"RAMIP":{"name":"RAMIP","sections":["SUMMARY"],"supported":null,"summary":"Water In-place","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BAMIP":{"name":"BAMIP","sections":["SUMMARY"],"supported":null,"summary":"Water In-place","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BGPR":{"name":"BGPR","sections":["SUMMARY"],"supported":null,"summary":"Gas Phase Pressure","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FPR":{"name":"FPR","sections":["SUMMARY"],"supported":null,"summary":"Oil Phase Pressure. Field and Region HCPV weighted.","parameters":[],"example":"","size_kind":"none"},"RPR":{"name":"RPR","sections":["SUMMARY"],"supported":null,"summary":"Oil Phase Pressure. Field and Region HCPV weighted.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BPR":{"name":"BPR","sections":["SUMMARY"],"supported":null,"summary":"Oil Phase Pressure. Field and Region HCPV weighted.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FPRH":{"name":"FPRH","sections":["SUMMARY"],"supported":null,"summary":"Oil Phase Pressure. Field and Region HCPV weighted.","parameters":[],"example":"","size_kind":"none"},"RPRH":{"name":"RPRH","sections":["SUMMARY"],"supported":null,"summary":"Oil Phase Pressure. Field and Region HCPV weighted.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FPRP":{"name":"FPRP","sections":["SUMMARY"],"supported":null,"summary":"Oil Phase Pressure (PV Weighted). Field and Region PV weighted.","parameters":[],"example":"","size_kind":"none"},"RPRP":{"name":"RPRP","sections":["SUMMARY"],"supported":null,"summary":"Oil Phase Pressure (PV Weighted). Field and Region PV weighted.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BWPR":{"name":"BWPR","sections":["SUMMARY"],"supported":null,"summary":"Water Phase Pressure","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BSTATE":{"name":"BSTATE","sections":["SUMMARY"],"supported":null,"summary":"Block Hydrocarbon Phase State. Gas (1), Gas & Oil (2), and Oil (3).","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BPBUB":{"name":"BPBUB","sections":["SUMMARY"],"supported":null,"summary":"Bubble Point Pressure","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BGPC":{"name":"BGPC","sections":["SUMMARY"],"supported":null,"summary":"Capillary Pressure (Gas-Oil)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BWPC":{"name":"BWPC","sections":["SUMMARY"],"supported":null,"summary":"Capillary Pressure (Water-Oil)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BPDEW":{"name":"BPDEW","sections":["SUMMARY"],"supported":null,"summary":"Dew Point","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FPRGZ":{"name":"FPRGZ","sections":["SUMMARY"],"supported":null,"summary":"Gas P/Z","parameters":[],"example":"","size_kind":"none"},"RPRGZ":{"name":"RPRGZ","sections":["SUMMARY"],"supported":null,"summary":"Gas P/Z","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGDEN":{"name":"FGDEN","sections":["SUMMARY"],"supported":null,"summary":"Gas Reservoir Density","parameters":[],"example":"","size_kind":"none"},"RGDEN":{"name":"RGDEN","sections":["SUMMARY"],"supported":null,"summary":"Gas Reservoir Density","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BGDEN":{"name":"BGDEN","sections":["SUMMARY"],"supported":null,"summary":"Gas Reservoir Density","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BDENG":{"name":"BDENG","sections":["SUMMARY"],"supported":null,"summary":"Gas Reservoir Density. Same as BGDEN.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGSAT":{"name":"FGSAT","sections":["SUMMARY"],"supported":null,"summary":"Gas Saturation. Also BSGAS.","parameters":[],"example":"","size_kind":"none"},"RGSAT":{"name":"RGSAT","sections":["SUMMARY"],"supported":null,"summary":"Gas Saturation. Also BSGAS.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BGSAT":{"name":"BGSAT","sections":["SUMMARY"],"supported":null,"summary":"Gas Saturation. Also BSGAS.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BGSHY":{"name":"BGSHY","sections":["SUMMARY"],"supported":null,"summary":"Gas Saturation (Drainage to Imbibition). Leaving gas saturation for gas capillary pressure hysteresis.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BGTPD":{"name":"BGTPD","sections":["SUMMARY"],"supported":null,"summary":"Gas Saturation (Dynamically Trapped). WAG hysteresis only.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BGSTRP":{"name":"BGSTRP","sections":["SUMMARY"],"supported":null,"summary":"Gas Saturation (Trapped Critical). For gas capillary pressure hysteresis.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BGTRP":{"name":"BGTRP","sections":["SUMMARY"],"supported":null,"summary":"Gas Saturation (Trapped). WAG hysteresis only.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGVIS":{"name":"FGVIS","sections":["SUMMARY"],"supported":null,"summary":"Gas Viscosity","parameters":[],"example":"","size_kind":"none"},"RGVIS":{"name":"RGVIS","sections":["SUMMARY"],"supported":null,"summary":"Gas Viscosity","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BGVIS":{"name":"BGVIS","sections":["SUMMARY"],"supported":null,"summary":"Gas Viscosity","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BRSSAT":{"name":"BRSSAT","sections":["SUMMARY"],"supported":null,"summary":"Gas-Oil Ratio (Saturated)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FPPC":{"name":"FPPC","sections":["SUMMARY"],"supported":null,"summary":"Initial Contact Corrected Potential","parameters":[],"example":"","size_kind":"none"},"RPPC":{"name":"RPPC","sections":["SUMMARY"],"supported":null,"summary":"Initial Contact Corrected Potential","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BPPC":{"name":"BPPC","sections":["SUMMARY"],"supported":null,"summary":"Initial Contact Corrected Potential","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FODEN":{"name":"FODEN","sections":["SUMMARY"],"supported":null,"summary":"Oil Reservoir Density","parameters":[],"example":"","size_kind":"none"},"RODEN":{"name":"RODEN","sections":["SUMMARY"],"supported":null,"summary":"Oil Reservoir Density","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BODEN":{"name":"BODEN","sections":["SUMMARY"],"supported":null,"summary":"Oil Reservoir Density","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BDENO":{"name":"BDENO","sections":["SUMMARY"],"supported":null,"summary":"Oil Reservoir Density. Same as BODEN.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FOSAT":{"name":"FOSAT","sections":["SUMMARY"],"supported":null,"summary":"Oil Saturation. Also BSOIL.","parameters":[],"example":"","size_kind":"none"},"ROSAT":{"name":"ROSAT","sections":["SUMMARY"],"supported":null,"summary":"Oil Saturation. Also BSOIL.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BOSAT":{"name":"BOSAT","sections":["SUMMARY"],"supported":null,"summary":"Oil Saturation. Also BSOIL.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FOVIS":{"name":"FOVIS","sections":["SUMMARY"],"supported":null,"summary":"Oil Viscosity. Also BVOIL.","parameters":[],"example":"","size_kind":"none"},"ROVIS":{"name":"ROVIS","sections":["SUMMARY"],"supported":null,"summary":"Oil Viscosity. Also BVOIL.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BOVIS":{"name":"BOVIS","sections":["SUMMARY"],"supported":null,"summary":"Oil Viscosity. Also BVOIL.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BRVSAT":{"name":"BRVSAT","sections":["SUMMARY"],"supported":null,"summary":"Oil-Gas Ratio (Saturated)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BGKRR-":{"name":"BGKRR-","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Gas in the R- Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BGKRR":{"name":"BGKRR","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Gas in the R+ Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BGKRT-":{"name":"BGKRT-","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Gas in the Theta- Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BGKRT":{"name":"BGKRT","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Gas in the Theta+ Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BGKRX-":{"name":"BGKRX-","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Gas in the X- Direction). Also BGKRI-.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BGKRX":{"name":"BGKRX","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Gas in the X+ Direction). Also BGKRI.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BGKRY-":{"name":"BGKRY-","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Gas in the Y- Direction). Also BGKRJ-.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BGKRY":{"name":"BGKRY","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Gas in the Y+ Direction). Also BGKRJ.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BGKRZ-":{"name":"BGKRZ-","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Gas in the Z- Direction). Also BGKRK-.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BGKRZ":{"name":"BGKRZ","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Gas in the Z+ Direction). Also BGKRK.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BKRG":{"name":"BKRG","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Gas). Also BGWR.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BRK":{"name":"BRK","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Krw Reduction Factor). Due to Polymer.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BKROG":{"name":"BKROG","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Oil Two Phase to Gas)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BKROW":{"name":"BKROW","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Oil Two Phase to Water)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BOKRR-":{"name":"BOKRR-","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Oil in the R- Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BOKRR":{"name":"BOKRR","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Oil in the R+ Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BOKRT-":{"name":"BOKRT-","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Oil in the Theta- Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BOKRT":{"name":"BOKRT","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Oil in the Theta+ Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BOKRX-":{"name":"BOKRX-","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Oil in the X- Direction). Also BOKRI-.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BOKRX":{"name":"BOKRX","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Oil in the X+ Direction). Also BOKRI.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BOKRY-":{"name":"BOKRY-","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Oil in the Y- Direction). Also BOKRJ-.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BOKRY":{"name":"BOKRY","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Oil in the Y+ Direction). Also BOKRJ.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BOKRZ-":{"name":"BOKRZ-","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Oil in the Z- Direction). Also BOKRK-.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BOKRZ":{"name":"BOKRZ","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Oil in the Z+ Direction). Also BOKRK.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BKRO":{"name":"BKRO","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Oil). Also BOKR.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BWKRR-":{"name":"BWKRR-","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Water in the R- Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BWKRR":{"name":"BWKRR","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Water in the R+ Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BWKRT-":{"name":"BWKRT-","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Water in the Theta- Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BWKRT":{"name":"BWKRT","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Water in the Theta+ Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BWKRX-":{"name":"BWKRX-","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Water in the X- Direction). Also BWKRI-.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BWKRX":{"name":"BWKRX","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Water in the X+ Direction). Also BWKRI.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BWKRY-":{"name":"BWKRY-","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Water in the Y- Direction). Also BWKRJ-.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BWKRY":{"name":"BWKRY","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Water in the Y+ Direction). Also BWKRJ.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BWKRZ-":{"name":"BWKRZ-","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Water in the Z- Direction). Also BWKRK-.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BWKRZ":{"name":"BWKRZ","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Water in the Z+ Direction). Also BWKRK.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BKRW":{"name":"BKRW","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Water). Also BWKR.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FWDEN":{"name":"FWDEN","sections":["SUMMARY"],"supported":null,"summary":"Water Reservoir Density","parameters":[],"example":"","size_kind":"none"},"RWDEN":{"name":"RWDEN","sections":["SUMMARY"],"supported":null,"summary":"Water Reservoir Density","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BWDEN":{"name":"BWDEN","sections":["SUMMARY"],"supported":null,"summary":"Water Reservoir Density","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BDENW":{"name":"BDENW","sections":["SUMMARY"],"supported":null,"summary":"Water Reservoir Density. Same as BWDEN.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FWSAT":{"name":"FWSAT","sections":["SUMMARY"],"supported":null,"summary":"Water Saturation. Also BSWAT.","parameters":[],"example":"","size_kind":"none"},"RWSAT":{"name":"RWSAT","sections":["SUMMARY"],"supported":null,"summary":"Water Saturation. Also BSWAT.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BWSAT":{"name":"BWSAT","sections":["SUMMARY"],"supported":null,"summary":"Water Saturation. Also BSWAT.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BWSHY":{"name":"BWSHY","sections":["SUMMARY"],"supported":null,"summary":"Water Saturation (Drainage to Imbibition). Leaving water saturation for gas capillary pressure hysteresis.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BWSMA":{"name":"BWSMA","sections":["SUMMARY"],"supported":null,"summary":"Water Saturation (Maximum Wetting). Capillary pressure hysteresis maximum water saturation.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FWVIS":{"name":"FWVIS","sections":["SUMMARY"],"supported":null,"summary":"Water Viscosity","parameters":[],"example":"","size_kind":"none"},"RWVIS":{"name":"RWVIS","sections":["SUMMARY"],"supported":null,"summary":"Water Viscosity","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BWVIS":{"name":"BWVIS","sections":["SUMMARY"],"supported":null,"summary":"Water Viscosity","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FRS":{"name":"FRS","sections":["SUMMARY"],"supported":null,"summary":"Gas-Oil Ratio","parameters":[],"example":"","size_kind":"none"},"RRS":{"name":"RRS","sections":["SUMMARY"],"supported":null,"summary":"Gas-Oil Ratio","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BRS":{"name":"BRS","sections":["SUMMARY"],"supported":null,"summary":"Gas-Oil Ratio","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FRV":{"name":"FRV","sections":["SUMMARY"],"supported":null,"summary":"Oil-Gas Ratio","parameters":[],"example":"","size_kind":"none"},"RRV":{"name":"RRV","sections":["SUMMARY"],"supported":null,"summary":"Oil-Gas Ratio","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BRV":{"name":"BRV","sections":["SUMMARY"],"supported":null,"summary":"Oil-Gas Ratio","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGIP":{"name":"FGIP","sections":["SUMMARY"],"supported":null,"summary":"Gas In-Place. Liquid and gas phases.","parameters":[],"example":"","size_kind":"none"},"RGIP":{"name":"RGIP","sections":["SUMMARY"],"supported":null,"summary":"Gas In-Place. Liquid and gas phases.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BGIP":{"name":"BGIP","sections":["SUMMARY"],"supported":null,"summary":"Gas In-Place. Liquid and gas phases.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGIPG":{"name":"FGIPG","sections":["SUMMARY"],"supported":null,"summary":"Gas In-Place (Gas Phase)","parameters":[],"example":"","size_kind":"none"},"RGIPG":{"name":"RGIPG","sections":["SUMMARY"],"supported":null,"summary":"Gas In-Place (Gas Phase)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BGIPG":{"name":"BGIPG","sections":["SUMMARY"],"supported":null,"summary":"Gas In-Place (Gas Phase)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGIPL":{"name":"FGIPL","sections":["SUMMARY"],"supported":null,"summary":"Gas In-Place (Liquid Phase). Only for cases that have dissolved gas in the water phase.","parameters":[],"example":"","size_kind":"none"},"RGIPL":{"name":"RGIPL","sections":["SUMMARY"],"supported":null,"summary":"Gas In-Place (Liquid Phase). Only for cases that have dissolved gas in the water phase.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BGIPL":{"name":"BGIPL","sections":["SUMMARY"],"supported":null,"summary":"Gas In-Place (Liquid Phase). Only for cases that have dissolved gas in the water phase.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGIPR":{"name":"FGIPR","sections":["SUMMARY"],"supported":null,"summary":"Gas In-Place (Reservoir Conditions). Compositional vector implemented in OPM Flow.","parameters":[],"example":"","size_kind":"none"},"FOIP":{"name":"FOIP","sections":["SUMMARY"],"supported":null,"summary":"Oil In-Place. Liquid and gas phases.","parameters":[],"example":"","size_kind":"none"},"ROIP":{"name":"ROIP","sections":["SUMMARY"],"supported":null,"summary":"Oil In-Place. Liquid and gas phases.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BOIP":{"name":"BOIP","sections":["SUMMARY"],"supported":null,"summary":"Oil In-Place. Liquid and gas phases.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FOIPG":{"name":"FOIPG","sections":["SUMMARY"],"supported":null,"summary":"Oil In-Place (Gas Phase)","parameters":[],"example":"","size_kind":"none"},"ROIPG":{"name":"ROIPG","sections":["SUMMARY"],"supported":null,"summary":"Oil In-Place (Gas Phase)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BOIPG":{"name":"BOIPG","sections":["SUMMARY"],"supported":null,"summary":"Oil In-Place (Gas Phase)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FOIPL":{"name":"FOIPL","sections":["SUMMARY"],"supported":null,"summary":"Oil In-Place (Liquid Phase)","parameters":[],"example":"","size_kind":"none"},"ROIPL":{"name":"ROIPL","sections":["SUMMARY"],"supported":null,"summary":"Oil In-Place (Liquid Phase)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BOIPL":{"name":"BOIPL","sections":["SUMMARY"],"supported":null,"summary":"Oil In-Place (Liquid Phase)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FOIPR":{"name":"FOIPR","sections":["SUMMARY"],"supported":null,"summary":"Oil In-Place (Reservoir Conditions). Compositional vector implemented in OPM Flow.","parameters":[],"example":"","size_kind":"none"},"FGPV":{"name":"FGPV","sections":["SUMMARY"],"supported":null,"summary":"Pore Volume (Gas)","parameters":[],"example":"","size_kind":"none"},"RGPV":{"name":"RGPV","sections":["SUMMARY"],"supported":null,"summary":"Pore Volume (Gas)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BGPV":{"name":"BGPV","sections":["SUMMARY"],"supported":null,"summary":"Pore Volume (Gas)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FHPV":{"name":"FHPV","sections":["SUMMARY"],"supported":null,"summary":"Pore Volume (HCPV)","parameters":[],"example":"","size_kind":"none"},"RHPV":{"name":"RHPV","sections":["SUMMARY"],"supported":null,"summary":"Pore Volume (HCPV)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BHPV":{"name":"BHPV","sections":["SUMMARY"],"supported":null,"summary":"Pore Volume (HCPV)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FOPV":{"name":"FOPV","sections":["SUMMARY"],"supported":null,"summary":"Pore Volume (Oil)","parameters":[],"example":"","size_kind":"none"},"ROPV":{"name":"ROPV","sections":["SUMMARY"],"supported":null,"summary":"Pore Volume (Oil)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BOPV":{"name":"BOPV","sections":["SUMMARY"],"supported":null,"summary":"Pore Volume (Oil)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FRPV":{"name":"FRPV","sections":["SUMMARY"],"supported":null,"summary":"Pore Volume (Reservoir Conditions). Also BPORV.","parameters":[],"example":"","size_kind":"none"},"RRPV":{"name":"RRPV","sections":["SUMMARY"],"supported":null,"summary":"Pore Volume (Reservoir Conditions). Also BPORV.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BRPV":{"name":"BRPV","sections":["SUMMARY"],"supported":null,"summary":"Pore Volume (Reservoir Conditions). Also BPORV.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FWPV":{"name":"FWPV","sections":["SUMMARY"],"supported":null,"summary":"Pore Volume (Water)","parameters":[],"example":"","size_kind":"none"},"RWPV":{"name":"RWPV","sections":["SUMMARY"],"supported":null,"summary":"Pore Volume (Water)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BWPV":{"name":"BWPV","sections":["SUMMARY"],"supported":null,"summary":"Pore Volume (Water)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BPERMMDX":{"name":"BPERMMDX","sections":["SUMMARY"],"supported":null,"summary":"Rock Compaction (Trans. Multiplier X Direction). Also BPERMOD.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BPERMMDY":{"name":"BPERMMDY","sections":["SUMMARY"],"supported":null,"summary":"Rock Compaction (Trans. Multiplier Y Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BPERMMDZ":{"name":"BPERMMDZ","sections":["SUMMARY"],"supported":null,"summary":"Rock Compaction (Trans. Multiplier Z Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FRTM":{"name":"FRTM","sections":["SUMMARY"],"supported":null,"summary":"Rock Compaction (Trans. Multiplier)","parameters":[],"example":"","size_kind":"none"},"RRTM":{"name":"RRTM","sections":["SUMMARY"],"supported":null,"summary":"Rock Compaction (Trans. Multiplier)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BRTM":{"name":"BRTM","sections":["SUMMARY"],"supported":null,"summary":"Rock Compaction (Trans. Multiplier)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BSIGMMOD":{"name":"BSIGMMOD","sections":["SUMMARY"],"supported":null,"summary":"Rock Compaction (Dual Porosity SIGMA Multiplier)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BPORVMOD":{"name":"BPORVMOD","sections":["SUMMARY"],"supported":null,"summary":"Rock Compaction (PV Multiplier)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FWIP":{"name":"FWIP","sections":["SUMMARY"],"supported":null,"summary":"Water In-Place","parameters":[],"example":"","size_kind":"none"},"RWIP":{"name":"RWIP","sections":["SUMMARY"],"supported":null,"summary":"Water In-Place","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BWIP":{"name":"BWIP","sections":["SUMMARY"],"supported":null,"summary":"Water In-Place","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FWIPR":{"name":"FWIPR","sections":["SUMMARY"],"supported":null,"summary":"Water In-Place (Reservoir Conditions). Compositional vector implemented in OPM Flow.","parameters":[],"example":"","size_kind":"none"},"FOE":{"name":"FOE","sections":["SUMMARY"],"supported":null,"summary":"Oil Recovery Efficiency (STOIIP). Based on STOIIP.","parameters":[],"example":"","size_kind":"none"},"ROE":{"name":"ROE","sections":["SUMMARY"],"supported":null,"summary":"Oil Recovery Efficiency (STOIIP). Based on STOIIP.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FOEW":{"name":"FOEW","sections":["SUMMARY"],"supported":null,"summary":"Oil Recovery Efficiency (Wells). Based on well production and STOIIP.","parameters":[],"example":"","size_kind":"none"},"ROEW":{"name":"ROEW","sections":["SUMMARY"],"supported":null,"summary":"Oil Recovery Efficiency (Wells). Based on well production and STOIIP.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FOEIW":{"name":"FOEIW","sections":["SUMMARY"],"supported":null,"summary":"Oil Recovery Efficiency (STOIIP Mobile with Respect to Water). Based on STOIIP and initial mobile oil saturate with respect to water.","parameters":[],"example":"","size_kind":"none"},"ROEIW":{"name":"ROEIW","sections":["SUMMARY"],"supported":null,"summary":"Oil Recovery Efficiency (STOIIP Mobile with Respect to Water). Based on STOIIP and initial mobile oil saturate with respect to water.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FOEWW":{"name":"FOEWW","sections":["SUMMARY"],"supported":null,"summary":"Oil Recovery Efficiency Wells Mobile with Respect to Water). Based on well production and initial mobile oil saturate with respect to water.","parameters":[],"example":"","size_kind":"none"},"ROEWW":{"name":"ROEWW","sections":["SUMMARY"],"supported":null,"summary":"Oil Recovery Efficiency Wells Mobile with Respect to Water). Based on well production and initial mobile oil saturate with respect to water.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FOEIG":{"name":"FOEIG","sections":["SUMMARY"],"supported":null,"summary":"Oil Recovery Efficiency (STOIIP Mobile with Respect to Gas). Based on STOIIP and initial mobile oil saturate with respect to gas.","parameters":[],"example":"","size_kind":"none"},"ROEIG":{"name":"ROEIG","sections":["SUMMARY"],"supported":null,"summary":"Oil Recovery Efficiency (STOIIP Mobile with Respect to Gas). Based on STOIIP and initial mobile oil saturate with respect to gas.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FOEWG":{"name":"FOEWG","sections":["SUMMARY"],"supported":null,"summary":"Oil Recovery Efficiency (Wells Mobile with Respect to Gas). Based on well production and initial mobile oil saturate with respect to gas.","parameters":[],"example":"","size_kind":"none"},"ROEWG":{"name":"ROEWG","sections":["SUMMARY"],"supported":null,"summary":"Oil Recovery Efficiency (Wells Mobile with Respect to Gas). Based on well production and initial mobile oil saturate with respect to gas.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FOTMF":{"name":"FOTMF","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total (Free Gas Gas). Volumes reported at stock tank conditions.","parameters":[],"example":"","size_kind":"none"},"ROTMF":{"name":"ROTMF","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total (Free Gas Gas). Volumes reported at stock tank conditions.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FORMG":{"name":"FORMG","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total (Gas Influx)","parameters":[],"example":"","size_kind":"none"},"RORMG":{"name":"RORMG","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total (Gas Influx)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FORME":{"name":"FORME","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total (Oil Expansion)","parameters":[],"example":"","size_kind":"none"},"RORME":{"name":"RORME","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total (Oil Expansion)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FORMR":{"name":"FORMR","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total (Rock Compaction)","parameters":[],"example":"","size_kind":"none"},"RORMR":{"name":"RORMR","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total (Rock Compaction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FORMS":{"name":"FORMS","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total (Solution Gas)","parameters":[],"example":"","size_kind":"none"},"RORMS":{"name":"RORMS","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total (Solution Gas)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FORMW":{"name":"FORMW","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total (Water Influx)","parameters":[],"example":"","size_kind":"none"},"RORMW":{"name":"RORMW","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total (Water Influx)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FAPI":{"name":"FAPI","sections":["SUMMARY"],"supported":null,"summary":"Oil API","parameters":[],"example":"","size_kind":"none"},"GAPI":{"name":"GAPI","sections":["SUMMARY"],"supported":null,"summary":"Oil API","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CAPI":{"name":"CAPI","sections":["SUMMARY"],"supported":null,"summary":"Oil API","parameters":[],"example":"","size_kind":"fixed","size_count":1},"RAPI":{"name":"RAPI","sections":["SUMMARY"],"supported":null,"summary":"Oil API","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BAPI":{"name":"BAPI","sections":["SUMMARY"],"supported":null,"summary":"Oil API","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CTFR":{"name":"CTFR","sections":["SUMMARY"],"supported":null,"summary":"Tracer Flow Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"RTFTT":{"name":"RTFTT","sections":["SUMMARY"],"supported":null,"summary":"Tracer Flow Total (Inter Region)","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"RTFTF":{"name":"RTFTF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Flow Total (Free Inter Region)","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"RTFTS":{"name":"RTFTS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Flow Total (Solution Inter Region)","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"FTIC":{"name":"FTIC","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Concentration","parameters":[],"example":"","size_kind":"none","templated":true},"GTIC":{"name":"GTIC","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Concentration","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"WTIC":{"name":"WTIC","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Concentration","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"CTIC":{"name":"CTIC","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Concentration","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"FTICF":{"name":"FTICF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Concentration (Free)","parameters":[],"example":"","size_kind":"none","templated":true},"GTICF":{"name":"GTICF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Concentration (Free)","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"WTICF":{"name":"WTICF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Concentration (Free)","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"CTICF":{"name":"CTICF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Concentration (Free)","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"FTICS":{"name":"FTICS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Concentration (Solution)","parameters":[],"example":"","size_kind":"none","templated":true},"GTICS":{"name":"GTICS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Concentration (Solution)","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"WTICS":{"name":"WTICS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Concentration (Solution)","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"CTICS":{"name":"CTICS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Concentration (Solution)","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"FTIR":{"name":"FTIR","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Rate","parameters":[],"example":"","size_kind":"none","templated":true},"GTIR":{"name":"GTIR","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"WTIR":{"name":"WTIR","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"CTIR":{"name":"CTIR","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"FTIRF":{"name":"FTIRF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Rate (Free)","parameters":[],"example":"","size_kind":"none","templated":true},"GTIRF":{"name":"GTIRF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Rate (Free)","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"WTIRF":{"name":"WTIRF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Rate (Free)","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"CTIRF":{"name":"CTIRF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Rate (Free)","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"FTIRS":{"name":"FTIRS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Rate (Solution)","parameters":[],"example":"","size_kind":"none","templated":true},"GTIRS":{"name":"GTIRS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Rate (Solution)","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"WTIRS":{"name":"WTIRS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Rate (Solution)","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"CTIRS":{"name":"CTIRS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Rate (Solution)","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"FTIT":{"name":"FTIT","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Total","parameters":[],"example":"","size_kind":"none","templated":true},"GTIT":{"name":"GTIT","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"WTIT":{"name":"WTIT","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"CTIT":{"name":"CTIT","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"FTITF":{"name":"FTITF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Total (Free)","parameters":[],"example":"","size_kind":"none","templated":true},"GTITF":{"name":"GTITF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Total (Free)","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"WTITF":{"name":"WTITF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Total (Free)","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"CTITF":{"name":"CTITF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Total (Free)","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"FTITS":{"name":"FTITS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Total (Solution)","parameters":[],"example":"","size_kind":"none","templated":true},"GTITS":{"name":"GTITS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Total (Solution)","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"WTITS":{"name":"WTITS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Total (Solution)","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"CTITS":{"name":"CTITS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Total (Solution)","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"FTPC":{"name":"FTPC","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Concentration","parameters":[],"example":"","size_kind":"none","templated":true},"GTPC":{"name":"GTPC","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Concentration","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"WTPC":{"name":"WTPC","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Concentration","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"CTPC":{"name":"CTPC","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Concentration","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"FTPCF":{"name":"FTPCF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Concentration (Free)","parameters":[],"example":"","size_kind":"none","templated":true},"GTPCF":{"name":"GTPCF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Concentration (Free)","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"WTPCF":{"name":"WTPCF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Concentration (Free)","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"CTPCF":{"name":"CTPCF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Concentration (Free)","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"FTPCS":{"name":"FTPCS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Concentration (Solution)","parameters":[],"example":"","size_kind":"none","templated":true},"GTPCS":{"name":"GTPCS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Concentration (Solution)","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"WTPCS":{"name":"WTPCS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Concentration (Solution)","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"CTPCS":{"name":"CTPCS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Concentration (Solution)","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"FTPR":{"name":"FTPR","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Rate","parameters":[],"example":"","size_kind":"none","templated":true},"GTPR":{"name":"GTPR","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"WTPR":{"name":"WTPR","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"CTPR":{"name":"CTPR","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"FTPRF":{"name":"FTPRF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Rate (Free)","parameters":[],"example":"","size_kind":"none","templated":true},"GTPRF":{"name":"GTPRF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Rate (Free)","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"WTPRF":{"name":"WTPRF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Rate (Free)","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"CTPRF":{"name":"CTPRF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Rate (Free)","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"FTPRS":{"name":"FTPRS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Rate (Solution)","parameters":[],"example":"","size_kind":"none","templated":true},"GTPRS":{"name":"GTPRS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Rate (Solution)","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"WTPRS":{"name":"WTPRS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Rate (Solution)","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"CTPRS":{"name":"CTPRS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Rate (Solution)","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"FTPT":{"name":"FTPT","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Total","parameters":[],"example":"","size_kind":"none","templated":true},"GTPT":{"name":"GTPT","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"WTPT":{"name":"WTPT","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"CTPT":{"name":"CTPT","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"FTPTF":{"name":"FTPTF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Total (Free)","parameters":[],"example":"","size_kind":"none","templated":true},"GTPTF":{"name":"GTPTF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Total (Free)","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"WTPTF":{"name":"WTPTF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Total (Free)","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"CTPTF":{"name":"CTPTF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Total (Free)","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"FTPTS":{"name":"FTPTS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Total (Solution)","parameters":[],"example":"","size_kind":"none","templated":true},"GTPTS":{"name":"GTPTS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Total (Solution)","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"WTPTS":{"name":"WTPTS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Total (Solution)","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"CTPTS":{"name":"CTPTS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Total (Solution)","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"BTCN":{"name":"BTCN","sections":["SUMMARY"],"supported":null,"summary":"Tracer Concentration","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"BTCNF":{"name":"BTCNF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Concentration (Free)","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"BTCNS":{"name":"BTCNS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Concentration (Solution)","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"FTIPT":{"name":"FTIPT","sections":["SUMMARY"],"supported":null,"summary":"Tracer In-Place","parameters":[],"example":"","size_kind":"none","templated":true},"RTIPT":{"name":"RTIPT","sections":["SUMMARY"],"supported":null,"summary":"Tracer In-Place","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"BTIPT":{"name":"BTIPT","sections":["SUMMARY"],"supported":null,"summary":"Tracer In-Place","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"FTIPF":{"name":"FTIPF","sections":["SUMMARY"],"supported":null,"summary":"Tracer In-Place (Free)","parameters":[],"example":"","size_kind":"none","templated":true},"RTIPF":{"name":"RTIPF","sections":["SUMMARY"],"supported":null,"summary":"Tracer In-Place (Free)","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"BTIPF":{"name":"BTIPF","sections":["SUMMARY"],"supported":null,"summary":"Tracer In-Place (Free)","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"FTIPS":{"name":"FTIPS","sections":["SUMMARY"],"supported":null,"summary":"Tracer In-Place (Solution)","parameters":[],"example":"","size_kind":"none","templated":true},"RTIPS":{"name":"RTIPS","sections":["SUMMARY"],"supported":null,"summary":"Tracer In-Place (Solution)","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"BTIPS":{"name":"BTIPS","sections":["SUMMARY"],"supported":null,"summary":"Tracer In-Place (Solution)","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"CSFR":{"name":"CSFR","sections":["SUMMARY"],"supported":null,"summary":"Salt Flow Rate. Brine and Salt Precipitation Models.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FSIR":{"name":"FSIR","sections":["SUMMARY"],"supported":null,"summary":"Salt Injection Rate","parameters":[],"example":"","size_kind":"none"},"GSIR":{"name":"GSIR","sections":["SUMMARY"],"supported":null,"summary":"Salt Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WSIR":{"name":"WSIR","sections":["SUMMARY"],"supported":null,"summary":"Salt Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CSIR":{"name":"CSIR","sections":["SUMMARY"],"supported":null,"summary":"Salt Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FSIT":{"name":"FSIT","sections":["SUMMARY"],"supported":null,"summary":"Salt Injection Total","parameters":[],"example":"","size_kind":"none"},"GSIT":{"name":"GSIT","sections":["SUMMARY"],"supported":null,"summary":"Salt Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WSIT":{"name":"WSIT","sections":["SUMMARY"],"supported":null,"summary":"Salt Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CSIT":{"name":"CSIT","sections":["SUMMARY"],"supported":null,"summary":"Salt Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FSPR":{"name":"FSPR","sections":["SUMMARY"],"supported":null,"summary":"Salt Production Rate","parameters":[],"example":"","size_kind":"none"},"GSPR":{"name":"GSPR","sections":["SUMMARY"],"supported":null,"summary":"Salt Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WSPR":{"name":"WSPR","sections":["SUMMARY"],"supported":null,"summary":"Salt Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CSPR":{"name":"CSPR","sections":["SUMMARY"],"supported":null,"summary":"Salt Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FSPT":{"name":"FSPT","sections":["SUMMARY"],"supported":null,"summary":"Salt Production Total","parameters":[],"example":"","size_kind":"none"},"GSPT":{"name":"GSPT","sections":["SUMMARY"],"supported":null,"summary":"Salt Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WSPT":{"name":"WSPT","sections":["SUMMARY"],"supported":null,"summary":"Salt Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CSPT":{"name":"CSPT","sections":["SUMMARY"],"supported":null,"summary":"Salt Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BEMV_SAL":{"name":"BEMV_SAL","sections":["SUMMARY"],"supported":null,"summary":"Salt Corrected Water Viscosity","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BSCN":{"name":"BSCN","sections":["SUMMARY"],"supported":null,"summary":"Salt Concentration (Block)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FSIC":{"name":"FSIC","sections":["SUMMARY"],"supported":null,"summary":"Salt Concentration (Injection)","parameters":[],"example":"","size_kind":"none"},"GSIC":{"name":"GSIC","sections":["SUMMARY"],"supported":null,"summary":"Salt Concentration (Injection)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WSIC":{"name":"WSIC","sections":["SUMMARY"],"supported":null,"summary":"Salt Concentration (Injection)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CSIC":{"name":"CSIC","sections":["SUMMARY"],"supported":null,"summary":"Salt Concentration (Injection)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FSPC":{"name":"FSPC","sections":["SUMMARY"],"supported":null,"summary":"Salt Concentration (Production)","parameters":[],"example":"","size_kind":"none"},"GSPC":{"name":"GSPC","sections":["SUMMARY"],"supported":null,"summary":"Salt Concentration (Production)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WSPC":{"name":"WSPC","sections":["SUMMARY"],"supported":null,"summary":"Salt Concentration (Production)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CSPC":{"name":"CSPC","sections":["SUMMARY"],"supported":null,"summary":"Salt Concentration (Production)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FSIP":{"name":"FSIP","sections":["SUMMARY"],"supported":null,"summary":"Salt In-Place","parameters":[],"example":"","size_kind":"none"},"RSIP":{"name":"RSIP","sections":["SUMMARY"],"supported":null,"summary":"Salt In-Place","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BSIP":{"name":"BSIP","sections":["SUMMARY"],"supported":null,"summary":"Salt In-Place","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BTCNFANI":{"name":"BTCNFANI","sections":["SUMMARY"],"supported":null,"summary":"Anion Concentration (Block). Multi-Component Brine Model.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CTFRANI":{"name":"CTFRANI","sections":["SUMMARY"],"supported":null,"summary":"Anion Flow Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FTIRANI":{"name":"FTIRANI","sections":["SUMMARY"],"supported":null,"summary":"Anion Injection Rate","parameters":[],"example":"","size_kind":"none"},"GTIRANI":{"name":"GTIRANI","sections":["SUMMARY"],"supported":null,"summary":"Anion Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WTIRANI":{"name":"WTIRANI","sections":["SUMMARY"],"supported":null,"summary":"Anion Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FTITANI":{"name":"FTITANI","sections":["SUMMARY"],"supported":null,"summary":"Anion Injection Total","parameters":[],"example":"","size_kind":"none"},"GTITANI":{"name":"GTITANI","sections":["SUMMARY"],"supported":null,"summary":"Anion Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WTITANI":{"name":"WTITANI","sections":["SUMMARY"],"supported":null,"summary":"Anion Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CTITANI":{"name":"CTITANI","sections":["SUMMARY"],"supported":null,"summary":"Anion Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FTPRANI":{"name":"FTPRANI","sections":["SUMMARY"],"supported":null,"summary":"Anion Production Rate","parameters":[],"example":"","size_kind":"none"},"GTPRANI":{"name":"GTPRANI","sections":["SUMMARY"],"supported":null,"summary":"Anion Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WTPRANI":{"name":"WTPRANI","sections":["SUMMARY"],"supported":null,"summary":"Anion Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FTPTANI":{"name":"FTPTANI","sections":["SUMMARY"],"supported":null,"summary":"Anion Production Total","parameters":[],"example":"","size_kind":"none"},"GTPTANI":{"name":"GTPTANI","sections":["SUMMARY"],"supported":null,"summary":"Anion Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WTPTANI":{"name":"WTPTANI","sections":["SUMMARY"],"supported":null,"summary":"Anion Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CTPTANI":{"name":"CTPTANI","sections":["SUMMARY"],"supported":null,"summary":"Anion Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CTFRCAT":{"name":"CTFRCAT","sections":["SUMMARY"],"supported":null,"summary":"Cation Flow Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FTIRCAT":{"name":"FTIRCAT","sections":["SUMMARY"],"supported":null,"summary":"Cation Injection Rate","parameters":[],"example":"","size_kind":"none"},"GTIRCAT":{"name":"GTIRCAT","sections":["SUMMARY"],"supported":null,"summary":"Cation Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WTIRCAT":{"name":"WTIRCAT","sections":["SUMMARY"],"supported":null,"summary":"Cation Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FTITCAT":{"name":"FTITCAT","sections":["SUMMARY"],"supported":null,"summary":"Cation Injection Total","parameters":[],"example":"","size_kind":"none"},"GTITCAT":{"name":"GTITCAT","sections":["SUMMARY"],"supported":null,"summary":"Cation Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WTITCAT":{"name":"WTITCAT","sections":["SUMMARY"],"supported":null,"summary":"Cation Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CTITCAT":{"name":"CTITCAT","sections":["SUMMARY"],"supported":null,"summary":"Cation Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FTPRCAT":{"name":"FTPRCAT","sections":["SUMMARY"],"supported":null,"summary":"Cation Production Rate","parameters":[],"example":"","size_kind":"none"},"GTPRCAT":{"name":"GTPRCAT","sections":["SUMMARY"],"supported":null,"summary":"Cation Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WTPRCAT":{"name":"WTPRCAT","sections":["SUMMARY"],"supported":null,"summary":"Cation Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FTPTCAT":{"name":"FTPTCAT","sections":["SUMMARY"],"supported":null,"summary":"Cation Production Total","parameters":[],"example":"","size_kind":"none"},"GTPTCAT":{"name":"GTPTCAT","sections":["SUMMARY"],"supported":null,"summary":"Cation Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WTPTCAT":{"name":"WTPTCAT","sections":["SUMMARY"],"supported":null,"summary":"Cation Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CTPTCAT":{"name":"CTPTCAT","sections":["SUMMARY"],"supported":null,"summary":"Cation Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BESALPLY":{"name":"BESALPLY","sections":["SUMMARY"],"supported":null,"summary":"Effective Salinity (Polymer)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BESALSUR":{"name":"BESALSUR","sections":["SUMMARY"],"supported":null,"summary":"Effective Salinity (Surfactant)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BTCNFCAT":{"name":"BTCNFCAT","sections":["SUMMARY"],"supported":null,"summary":"Cation Concentration (Block)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BTRADCAT":{"name":"BTRADCAT","sections":["SUMMARY"],"supported":null,"summary":"Cation Concentration (Rock Associated)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BTSADCAT":{"name":"BTSADCAT","sections":["SUMMARY"],"supported":null,"summary":"Cation Concentration (Surfactant Associated)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGMIR":{"name":"FGMIR","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mass Injection Rate","parameters":[],"example":"","size_kind":"none"},"GGMIR":{"name":"GGMIR","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mass Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WGMIR":{"name":"WGMIR","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mass Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CGMIR":{"name":"CGMIR","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mass Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGMIT":{"name":"FGMIT","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mass Injection Total","parameters":[],"example":"","size_kind":"none"},"GGMIT":{"name":"GGMIT","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mass Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WGMIT":{"name":"WGMIT","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mass Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CGMIT":{"name":"CGMIT","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mass Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGMPR":{"name":"FGMPR","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mass Production Rate","parameters":[],"example":"","size_kind":"none"},"GGMPR":{"name":"GGMPR","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mass Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WGMPR":{"name":"WGMPR","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mass Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CGMPR":{"name":"CGMPR","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mass Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGMPT":{"name":"FGMPT","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mass Production Total","parameters":[],"example":"","size_kind":"none"},"GGMPT":{"name":"GGMPT","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mass Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WGMPT":{"name":"WGMPT","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mass Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CGMPT":{"name":"CGMPT","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mass Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGMIP":{"name":"FGMIP","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 In-place","parameters":[],"example":"","size_kind":"none"},"RGMIP":{"name":"RGMIP","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 In-place","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BGMIP":{"name":"BGMIP","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 In-place","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGMGP":{"name":"FGMGP","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 In-place (Gas Phase)","parameters":[],"example":"","size_kind":"none"},"RGMGP":{"name":"RGMGP","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 In-place (Gas Phase)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BGMGP":{"name":"BGMGP","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 In-place (Gas Phase)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGMDS":{"name":"FGMDS","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 In-place (Liquid Phase)","parameters":[],"example":"","size_kind":"none"},"RGMDS":{"name":"RGMDS","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 In-place (Liquid Phase)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BGMDS":{"name":"BGMDS","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 In-place (Liquid Phase)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGMST":{"name":"FGMST","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Effectively Residual Trapped ('Stranded') in the gas phase","parameters":[],"example":"","size_kind":"none"},"RGMST":{"name":"RGMST","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Effectively Residual Trapped ('Stranded') in the gas phase","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BGMST":{"name":"BGMST","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Effectively Residual Trapped ('Stranded') in the gas phase","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGMUS":{"name":"FGMUS","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Effectively Residual Untrapped ('Unstranded') in the gas phase","parameters":[],"example":"","size_kind":"none"},"RGMUS":{"name":"RGMUS","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Effectively Residual Untrapped ('Unstranded') in the gas phase","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BGMUS":{"name":"BGMUS","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Effectively Residual Untrapped ('Unstranded') in the gas phase","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGMTR":{"name":"FGMTR","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Maximum Potential Residual Trapped in the gas phase","parameters":[],"example":"","size_kind":"none"},"RGMTR":{"name":"RGMTR","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Maximum Potential Residual Trapped in the gas phase","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BGMTR":{"name":"BGMTR","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Maximum Potential Residual Trapped in the gas phase","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGMMO":{"name":"FGMMO","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Maximum Potential Residual Untrapped in the gas phase","parameters":[],"example":"","size_kind":"none"},"RGMMO":{"name":"RGMMO","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Maximum Potential Residual Untrapped in the gas phase","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BGMMO":{"name":"BGMMO","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Maximum Potential Residual Untrapped in the gas phase","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGKTR":{"name":"FGKTR","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Immobile in the gas phase (Non-wetting relative permeability equals zero)","parameters":[],"example":"","size_kind":"none"},"RGKTR":{"name":"RGKTR","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Immobile in the gas phase (Non-wetting relative permeability equals zero)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BGKTR":{"name":"BGKTR","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Immobile in the gas phase (Non-wetting relative permeability equals zero)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGKMO":{"name":"FGKMO","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mobile in the gas phase (Non-wetting relative permeability greater than zero)","parameters":[],"example":"","size_kind":"none"},"RGKMO":{"name":"RGKMO","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mobile in the gas phase (Non-wetting relative permeability greater than zero)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BGKMO":{"name":"BGKMO","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mobile in the gas phase (Non-wetting relative permeability greater than zero)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGCDI":{"name":"FGCDI","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Immobile in the gas phase","parameters":[],"example":"","size_kind":"none"},"RGCDI":{"name":"RGCDI","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Immobile in the gas phase","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BGCDI":{"name":"BGCDI","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Immobile in the gas phase","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGCDM":{"name":"FGCDM","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mobile in the gas phase","parameters":[],"example":"","size_kind":"none"},"RGCDM":{"name":"RGCDM","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mobile in the gas phase","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BGCDM":{"name":"BGCDM","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mobile in the gas phase","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGKDI":{"name":"FGKDI","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Immobile in the gas phase (Non-wetting relative permeability equals zero)","parameters":[],"example":"","size_kind":"none"},"RGKDI":{"name":"RGKDI","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Immobile in the gas phase (Non-wetting relative permeability equals zero)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BGKDI":{"name":"BGKDI","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Immobile in the gas phase (Non-wetting relative permeability equals zero)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FGKDM":{"name":"FGKDM","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mobile in the gas phase (Non-wetting relative permeability greater than zero)","parameters":[],"example":"","size_kind":"none"},"RGKDM":{"name":"RGKDM","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mobile in the gas phase (Non-wetting relative permeability greater than zero)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BGKDM":{"name":"BGKDM","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mobile in the gas phase (Non-wetting relative permeability greater than zero)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FWCD":{"name":"FWCD","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Dissolved in the water phase","parameters":[],"example":"","size_kind":"none"},"RWCD":{"name":"RWCD","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Dissolved in the water phase","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BWCD":{"name":"BWCD","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Dissolved in the water phase","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FWIPG":{"name":"FWIPG","sections":["SUMMARY"],"supported":null,"summary":"Water in the gas phase","parameters":[],"example":"","size_kind":"none"},"RWIPG":{"name":"RWIPG","sections":["SUMMARY"],"supported":null,"summary":"Water in the gas phase","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BWIPG":{"name":"BWIPG","sections":["SUMMARY"],"supported":null,"summary":"Water in the gas phase","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FWIPL":{"name":"FWIPL","sections":["SUMMARY"],"supported":null,"summary":"Water in the water phase","parameters":[],"example":"","size_kind":"none"},"RWIPL":{"name":"RWIPL","sections":["SUMMARY"],"supported":null,"summary":"Water in the water phase","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BWIPL":{"name":"BWIPL","sections":["SUMMARY"],"supported":null,"summary":"Water in the water phase","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WINFC":{"name":"WINFC","sections":["SUMMARY"],"supported":null,"summary":"Filtrate Injection Concentration","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WINJFVR":{"name":"WINJFVR","sections":["SUMMARY"],"supported":null,"summary":"Filtrate Volume Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CINJFVR":{"name":"CINJFVR","sections":["SUMMARY"],"supported":null,"summary":"Filtrate Volume Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WINJFVT":{"name":"WINJFVT","sections":["SUMMARY"],"supported":null,"summary":"Filtrate Volume Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CINJFVT":{"name":"CINJFVT","sections":["SUMMARY"],"supported":null,"summary":"Filtrate Volume Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CFCAOF":{"name":"CFCAOF","sections":["SUMMARY"],"supported":null,"summary":"Filter Cake Area Of Flow","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CFCPERM":{"name":"CFCPERM","sections":["SUMMARY"],"supported":null,"summary":"Filter Cake Permeability","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CFCPORO":{"name":"CFCPORO","sections":["SUMMARY"],"supported":null,"summary":"Filter Cake Porosity","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CFCRAD":{"name":"CFCRAD","sections":["SUMMARY"],"supported":null,"summary":"Filter Cake Radius","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CFCSKIN":{"name":"CFCSKIN","sections":["SUMMARY"],"supported":null,"summary":"Filter Cake Skin","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CFCWIDTH":{"name":"CFCWIDTH","sections":["SUMMARY"],"supported":null,"summary":"Filter Cake Width","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CTFRFOA":{"name":"CTFRFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Flow Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FTIRFOA":{"name":"FTIRFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Injection Rate","parameters":[],"example":"","size_kind":"none"},"GTIRFOA":{"name":"GTIRFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WTIRFOA":{"name":"WTIRFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FTITFOA":{"name":"FTITFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Injection Total","parameters":[],"example":"","size_kind":"none"},"GTITFOA":{"name":"GTITFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WTITFOA":{"name":"WTITFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CTITFOA":{"name":"CTITFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FTPRFOA":{"name":"FTPRFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Production Rate","parameters":[],"example":"","size_kind":"none"},"GTPRFOA":{"name":"GTPRFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WTPRFOA":{"name":"WTPRFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FTPTFOA":{"name":"FTPTFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Production Total","parameters":[],"example":"","size_kind":"none"},"GTPTFOA":{"name":"GTPTFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WTPTFOA":{"name":"WTPTFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CTPTFOA":{"name":"CTPTFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FTADSFOA":{"name":"FTADSFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Adsorption Total. Block is current value.","parameters":[],"example":"","size_kind":"none"},"CTADSFOA":{"name":"CTADSFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Adsorption Total. Block is current value.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"RTADSFOA":{"name":"RTADSFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Adsorption Total. Block is current value.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BTADSFOA":{"name":"BTADSFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Adsorption Total. Block is current value.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BTCNMFOA":{"name":"BTCNMFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Capillary Number","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BTHLFFOA":{"name":"BTHLFFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Decayed Half Life","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FTDCYFOA":{"name":"FTDCYFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Decayed Tracer","parameters":[],"example":"","size_kind":"none"},"RTDCYFOA":{"name":"RTDCYFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Decayed Tracer","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BTDCYFOA":{"name":"BTDCYFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Decayed Tracer","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FTMOBFOA":{"name":"FTMOBFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Gas Mobility Factor. Excluding shear.","parameters":[],"example":"","size_kind":"none"},"FTIPTFOA":{"name":"FTIPTFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam in Solution","parameters":[],"example":"","size_kind":"none"},"CTIPTFOA":{"name":"CTIPTFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam in Solution","parameters":[],"example":"","size_kind":"fixed","size_count":1},"RTIPTFOA":{"name":"RTIPTFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam in Solution","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BTIPTFOA":{"name":"BTIPTFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam in Solution","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BTCNFFOA":{"name":"BTCNFFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Concentration","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WOGLR":{"name":"WOGLR","sections":["SUMMARY"],"supported":null,"summary":"Incremental oil rate per unit of incremental gas lift gas quantity, that is the well’s gradient as defined by equation (11.2.7)below","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FMMIR":{"name":"FMMIR","sections":["SUMMARY"],"supported":null,"summary":"Microbial Mass Injection Rate","parameters":[],"example":"","size_kind":"none"},"GMMIR":{"name":"GMMIR","sections":["SUMMARY"],"supported":null,"summary":"Microbial Mass Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WMMIR":{"name":"WMMIR","sections":["SUMMARY"],"supported":null,"summary":"Microbial Mass Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CMMIR":{"name":"CMMIR","sections":["SUMMARY"],"supported":null,"summary":"Microbial Mass Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CMMIRL":{"name":"CMMIRL","sections":["SUMMARY"],"supported":null,"summary":"Microbial Mass Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FMOIR":{"name":"FMOIR","sections":["SUMMARY"],"supported":null,"summary":"Oxygen Mass Injection Rate","parameters":[],"example":"","size_kind":"none"},"GMOIR":{"name":"GMOIR","sections":["SUMMARY"],"supported":null,"summary":"Oxygen Mass Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WMOIR":{"name":"WMOIR","sections":["SUMMARY"],"supported":null,"summary":"Oxygen Mass Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CMOIR":{"name":"CMOIR","sections":["SUMMARY"],"supported":null,"summary":"Oxygen Mass Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CMOIRL":{"name":"CMOIRL","sections":["SUMMARY"],"supported":null,"summary":"Oxygen Mass Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FMUIR":{"name":"FMUIR","sections":["SUMMARY"],"supported":null,"summary":"Urea Mass Injection Rate","parameters":[],"example":"","size_kind":"none"},"GMUIR":{"name":"GMUIR","sections":["SUMMARY"],"supported":null,"summary":"Urea Mass Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WMUIR":{"name":"WMUIR","sections":["SUMMARY"],"supported":null,"summary":"Urea Mass Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CMUIR":{"name":"CMUIR","sections":["SUMMARY"],"supported":null,"summary":"Urea Mass Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CMUIRL":{"name":"CMUIRL","sections":["SUMMARY"],"supported":null,"summary":"Urea Mass Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FMMIT":{"name":"FMMIT","sections":["SUMMARY"],"supported":null,"summary":"Microbial Mass Injection Total","parameters":[],"example":"","size_kind":"none"},"GMMIT":{"name":"GMMIT","sections":["SUMMARY"],"supported":null,"summary":"Microbial Mass Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WMMIT":{"name":"WMMIT","sections":["SUMMARY"],"supported":null,"summary":"Microbial Mass Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CMMIT":{"name":"CMMIT","sections":["SUMMARY"],"supported":null,"summary":"Microbial Mass Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CMMITL":{"name":"CMMITL","sections":["SUMMARY"],"supported":null,"summary":"Microbial Mass Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FMOIT":{"name":"FMOIT","sections":["SUMMARY"],"supported":null,"summary":"Oxygen Mass Injection Total","parameters":[],"example":"","size_kind":"none"},"GMOIT":{"name":"GMOIT","sections":["SUMMARY"],"supported":null,"summary":"Oxygen Mass Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WMOIT":{"name":"WMOIT","sections":["SUMMARY"],"supported":null,"summary":"Oxygen Mass Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CMOIT":{"name":"CMOIT","sections":["SUMMARY"],"supported":null,"summary":"Oxygen Mass Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CMOITL":{"name":"CMOITL","sections":["SUMMARY"],"supported":null,"summary":"Oxygen Mass Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FMUIT":{"name":"FMUIT","sections":["SUMMARY"],"supported":null,"summary":"Urea Mass Injection Total","parameters":[],"example":"","size_kind":"none"},"GMUIT":{"name":"GMUIT","sections":["SUMMARY"],"supported":null,"summary":"Urea Mass Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WMUIT":{"name":"WMUIT","sections":["SUMMARY"],"supported":null,"summary":"Urea Mass Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CMUIT":{"name":"CMUIT","sections":["SUMMARY"],"supported":null,"summary":"Urea Mass Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CMUITL":{"name":"CMUITL","sections":["SUMMARY"],"supported":null,"summary":"Urea Mass Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FMMPR":{"name":"FMMPR","sections":["SUMMARY"],"supported":null,"summary":"Microbial Mass Production Rate","parameters":[],"example":"","size_kind":"none"},"GMMPR":{"name":"GMMPR","sections":["SUMMARY"],"supported":null,"summary":"Microbial Mass Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WMMPR":{"name":"WMMPR","sections":["SUMMARY"],"supported":null,"summary":"Microbial Mass Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CMMPR":{"name":"CMMPR","sections":["SUMMARY"],"supported":null,"summary":"Microbial Mass Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CMMPRL":{"name":"CMMPRL","sections":["SUMMARY"],"supported":null,"summary":"Microbial Mass Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FMOPR":{"name":"FMOPR","sections":["SUMMARY"],"supported":null,"summary":"Oxygen Mass Production Rate","parameters":[],"example":"","size_kind":"none"},"GMOPR":{"name":"GMOPR","sections":["SUMMARY"],"supported":null,"summary":"Oxygen Mass Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WMOPR":{"name":"WMOPR","sections":["SUMMARY"],"supported":null,"summary":"Oxygen Mass Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CMOPR":{"name":"CMOPR","sections":["SUMMARY"],"supported":null,"summary":"Oxygen Mass Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CMOPRL":{"name":"CMOPRL","sections":["SUMMARY"],"supported":null,"summary":"Oxygen Mass Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FMUPR":{"name":"FMUPR","sections":["SUMMARY"],"supported":null,"summary":"Urea Mass Production Rate","parameters":[],"example":"","size_kind":"none"},"GMUPR":{"name":"GMUPR","sections":["SUMMARY"],"supported":null,"summary":"Urea Mass Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WMUPR":{"name":"WMUPR","sections":["SUMMARY"],"supported":null,"summary":"Urea Mass Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CMUPR":{"name":"CMUPR","sections":["SUMMARY"],"supported":null,"summary":"Urea Mass Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CMUPRL":{"name":"CMUPRL","sections":["SUMMARY"],"supported":null,"summary":"Urea Mass Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FMMPT":{"name":"FMMPT","sections":["SUMMARY"],"supported":null,"summary":"Microbial Mass Production Total","parameters":[],"example":"","size_kind":"none"},"GMMPT":{"name":"GMMPT","sections":["SUMMARY"],"supported":null,"summary":"Microbial Mass Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WMMPT":{"name":"WMMPT","sections":["SUMMARY"],"supported":null,"summary":"Microbial Mass Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CMMPT":{"name":"CMMPT","sections":["SUMMARY"],"supported":null,"summary":"Microbial Mass Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CMMPTL":{"name":"CMMPTL","sections":["SUMMARY"],"supported":null,"summary":"Microbial Mass Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FMOPT":{"name":"FMOPT","sections":["SUMMARY"],"supported":null,"summary":"Oxygen Mass Production Total","parameters":[],"example":"","size_kind":"none"},"GMOPT":{"name":"GMOPT","sections":["SUMMARY"],"supported":null,"summary":"Oxygen Mass Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WMOPT":{"name":"WMOPT","sections":["SUMMARY"],"supported":null,"summary":"Oxygen Mass Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CMOPT":{"name":"CMOPT","sections":["SUMMARY"],"supported":null,"summary":"Oxygen Mass Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CMOPTL":{"name":"CMOPTL","sections":["SUMMARY"],"supported":null,"summary":"Oxygen Mass Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FMUPT":{"name":"FMUPT","sections":["SUMMARY"],"supported":null,"summary":"Urea Mass Production Total","parameters":[],"example":"","size_kind":"none"},"GMUPT":{"name":"GMUPT","sections":["SUMMARY"],"supported":null,"summary":"Urea Mass Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WMUPT":{"name":"WMUPT","sections":["SUMMARY"],"supported":null,"summary":"Urea Mass Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CMUPT":{"name":"CMUPT","sections":["SUMMARY"],"supported":null,"summary":"Urea Mass Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CMUPTL":{"name":"CMUPTL","sections":["SUMMARY"],"supported":null,"summary":"Urea Mass Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FMMIP":{"name":"FMMIP","sections":["SUMMARY"],"supported":null,"summary":"Microbes In-place","parameters":[],"example":"","size_kind":"none"},"RMMIP":{"name":"RMMIP","sections":["SUMMARY"],"supported":null,"summary":"Microbes In-place","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BMMIP":{"name":"BMMIP","sections":["SUMMARY"],"supported":null,"summary":"Microbes In-place","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FMOIP":{"name":"FMOIP","sections":["SUMMARY"],"supported":null,"summary":"Oxygen In-place","parameters":[],"example":"","size_kind":"none"},"RMOIP":{"name":"RMOIP","sections":["SUMMARY"],"supported":null,"summary":"Oxygen In-place","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BMOIP":{"name":"BMOIP","sections":["SUMMARY"],"supported":null,"summary":"Oxygen In-place","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FMUIP":{"name":"FMUIP","sections":["SUMMARY"],"supported":null,"summary":"Urea In-place","parameters":[],"example":"","size_kind":"none"},"RMUIP":{"name":"RMUIP","sections":["SUMMARY"],"supported":null,"summary":"Urea In-place","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BMUIP":{"name":"BMUIP","sections":["SUMMARY"],"supported":null,"summary":"Urea In-place","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FMBIP":{"name":"FMBIP","sections":["SUMMARY"],"supported":null,"summary":"Biofilm In-place","parameters":[],"example":"","size_kind":"none"},"RMBIP":{"name":"RMBIP","sections":["SUMMARY"],"supported":null,"summary":"Biofilm In-place","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BMBIP":{"name":"BMBIP","sections":["SUMMARY"],"supported":null,"summary":"Biofilm In-place","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FMCIP":{"name":"FMCIP","sections":["SUMMARY"],"supported":null,"summary":"Calcite In-place","parameters":[],"example":"","size_kind":"none"},"RMCIP":{"name":"RMCIP","sections":["SUMMARY"],"supported":null,"summary":"Calcite In-place","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BMCIP":{"name":"BMCIP","sections":["SUMMARY"],"supported":null,"summary":"Calcite In-place","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SALQ":{"name":"SALQ","sections":["SUMMARY"],"supported":null,"summary":"Artificial Lift Quantity. See keyword WSEGTABL.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SFR":{"name":"SFR","sections":["SUMMARY"],"supported":null,"summary":"Brine Flow Rate. Surfactant and Polymer model.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SGFR":{"name":"SGFR","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SGFRF":{"name":"SGFRF","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow Rate (Free)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SGFRS":{"name":"SGFRS","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow Rate (Solution)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SGFTA":{"name":"SGFTA","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow Total (Absolute)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SGFT":{"name":"SGFT","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SGFV":{"name":"SGFV","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow Velocity","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SGHF":{"name":"SGHF","sections":["SUMMARY"],"supported":null,"summary":"Gas Holdup Fraction","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SGIMR":{"name":"SGIMR","sections":["SUMMARY"],"supported":null,"summary":"Gas Import Rate. See keyword WSEGEXSS.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SGIMT":{"name":"SGIMT","sections":["SUMMARY"],"supported":null,"summary":"Gas Import Total. See keyword WSEGEXSS.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SOFTA":{"name":"SOFTA","sections":["SUMMARY"],"supported":null,"summary":"Oil Absolute Flow Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SOFR":{"name":"SOFR","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SOFRF":{"name":"SOFRF","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow Rate (Free)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SOFRS":{"name":"SOFRS","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow Rate (Solution)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SOFT":{"name":"SOFT","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SOFV":{"name":"SOFV","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow Velocity","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SOHF":{"name":"SOHF","sections":["SUMMARY"],"supported":null,"summary":"Oil Holdup Fraction","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SCFR":{"name":"SCFR","sections":["SUMMARY"],"supported":null,"summary":"Polymer Flow Rate. Polymer model.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"STFR":{"name":"STFR","sections":["SUMMARY"],"supported":null,"summary":"Tracer Flow Rate. Tracer model.","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"SWFR":{"name":"SWFR","sections":["SUMMARY"],"supported":null,"summary":"Water Flow Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SWFT":{"name":"SWFT","sections":["SUMMARY"],"supported":null,"summary":"Water Flow Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SWFTA":{"name":"SWFTA","sections":["SUMMARY"],"supported":null,"summary":"Water Flow Total (Absolute)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SWFV":{"name":"SWFV","sections":["SUMMARY"],"supported":null,"summary":"Water Flow Velocity","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SWHF":{"name":"SWHF","sections":["SUMMARY"],"supported":null,"summary":"Water Holdup Fraction","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SWIMR":{"name":"SWIMR","sections":["SUMMARY"],"supported":null,"summary":"Water Import Rate. See keyword WSEGEXSS.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SWIMT":{"name":"SWIMT","sections":["SUMMARY"],"supported":null,"summary":"Water Import Total. See keyword WSEGEXSS.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SPR":{"name":"SPR","sections":["SUMMARY"],"supported":null,"summary":"Pressure","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SPRD":{"name":"SPRD","sections":["SUMMARY"],"supported":null,"summary":"Pressure Drop","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SPRDF":{"name":"SPRDF","sections":["SUMMARY"],"supported":null,"summary":"Pressure Drop Component due to Friction","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SPRDH":{"name":"SPRDH","sections":["SUMMARY"],"supported":null,"summary":"Pressure Drop Component due to Hydrostatic head","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SPRDA":{"name":"SPRDA","sections":["SUMMARY"],"supported":null,"summary":"Pressure Drop due to Acceleration head","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SPRDM":{"name":"SPRDM","sections":["SUMMARY"],"supported":null,"summary":"Pressure Drop Frictional Multiplier. See keyword WSEGMULT.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SAPI":{"name":"SAPI","sections":["SUMMARY"],"supported":null,"summary":"API. API model.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SDENM":{"name":"SDENM","sections":["SUMMARY"],"supported":null,"summary":"Fluid Mixture Density (Excludes Exponents). Excludes exponents of flowing fractions.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SMDEN":{"name":"SMDEN","sections":["SUMMARY"],"supported":null,"summary":"Fluid Mixture Density (Includes Exponents). Includes exponents of flowing fractions.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SMVIS":{"name":"SMVIS","sections":["SUMMARY"],"supported":null,"summary":"Fluid Mixture Viscosity (Includes Exponents). Includes exponents of flowing fractions.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SEMVIS":{"name":"SEMVIS","sections":["SUMMARY"],"supported":null,"summary":"Fluid Viscosity (Effective Mixture). Water/polymer fluid.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SGDEN":{"name":"SGDEN","sections":["SUMMARY"],"supported":null,"summary":"Gas Density","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SGVIS":{"name":"SGVIS","sections":["SUMMARY"],"supported":null,"summary":"Gas Viscosity","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SGLVD":{"name":"SGLVD","sections":["SUMMARY"],"supported":null,"summary":"Gas-Liquid Drift Velocity (Vd). Drift flux slip model.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SGLPP":{"name":"SGLPP","sections":["SUMMARY"],"supported":null,"summary":"Gas-Liquid Profile Parameter (C0). Drift flux slip model.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SODEN":{"name":"SODEN","sections":["SUMMARY"],"supported":null,"summary":"Oil Density","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SOVIS":{"name":"SOVIS","sections":["SUMMARY"],"supported":null,"summary":"Oil Viscosity","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SOWVD":{"name":"SOWVD","sections":["SUMMARY"],"supported":null,"summary":"Oil-Water Drift Velocity (Vd). Drift flux slip model.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SOWPP":{"name":"SOWPP","sections":["SUMMARY"],"supported":null,"summary":"Oil-Water Profile Parameter (C0). Drift flux slip model.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SPPOW":{"name":"SPPOW","sections":["SUMMARY"],"supported":null,"summary":"Pump Working Power. See keyword WSEGPULL.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SFD":{"name":"SFD","sections":["SUMMARY"],"supported":null,"summary":"Scale Deposition Diameter (Karst Conduit Calcite Dissolution). Scale Deposition model.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SFOPN":{"name":"SFOPN","sections":["SUMMARY"],"supported":null,"summary":"Setting of Segment. See keywords WSEGVALV, WSEGAICD, WSEGSICD, WSEGTABL, WSEGLABY, and WSEGFLIM.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SSTR":{"name":"SSTR","sections":["SUMMARY"],"supported":null,"summary":"Strength of ICD on Segment. See keywords WSEGVALV, WSEGAICD, and WSEGSICD.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SWDEN":{"name":"SWDEN","sections":["SUMMARY"],"supported":null,"summary":"Water Density (Pure Water)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SWVIS":{"name":"SWVIS","sections":["SUMMARY"],"supported":null,"summary":"Water Viscosity (Pure Water)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SGOR":{"name":"SGOR","sections":["SUMMARY"],"supported":null,"summary":"Gas-Oil Ratio","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SOGR":{"name":"SOGR","sections":["SUMMARY"],"supported":null,"summary":"Oil-Gas Ratio","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SWCT":{"name":"SWCT","sections":["SUMMARY"],"supported":null,"summary":"Water Cut","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SWGR":{"name":"SWGR","sections":["SUMMARY"],"supported":null,"summary":"Water Gas Ratio","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SSCN":{"name":"SSCN","sections":["SUMMARY"],"supported":null,"summary":"Brine Concentration. Surfactant and Polymer model","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SCCN":{"name":"SCCN","sections":["SUMMARY"],"supported":null,"summary":"Polymer Concentration. Polymer model","parameters":[],"example":"","size_kind":"fixed","size_count":1},"STFC":{"name":"STFC","sections":["SUMMARY"],"supported":null,"summary":"Tracer Concentration. Tracer model","parameters":[],"example":"","size_kind":"fixed","size_count":1,"templated":true},"GNETPR":{"name":"GNETPR","sections":["SUMMARY"],"supported":null,"summary":"Group/Node pressure in a production network based on rates at end of timestep (OPM Flow specific). An alias for NPR.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"GPR":{"name":"GPR","sections":["SUMMARY"],"supported":null,"summary":"Group/Node pressure in a production network.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"GPRG":{"name":"GPRG","sections":["SUMMARY"],"supported":null,"summary":"Group /Node pressure in a gas injection network.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"GPRW":{"name":"GPRW","sections":["SUMMARY"],"supported":null,"summary":"Group/Node pressure in a water injection network.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"GPRB":{"name":"GPRB","sections":["SUMMARY"],"supported":null,"summary":"Pressure drop along the group’s or node’s outlet branch in a production network.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"GPRBG":{"name":"GPRBG","sections":["SUMMARY"],"supported":null,"summary":"Pressure drop along the group’s or node’s inlet branch in a gas injection network.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"GPRBW":{"name":"GPRBW","sections":["SUMMARY"],"supported":null,"summary":"Pressure drop along the group’s or node’s inlet branch in a water injection network.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"NPR":{"name":"NPR","sections":["SUMMARY"],"supported":null,"summary":"Group/Node pressure in a production network based on rates at end of timestep (OPM Flow specific).","parameters":[],"example":"","size_kind":"fixed","size_count":1},"GALQ":{"name":"GALQ","sections":["SUMMARY"],"supported":null,"summary":"Artificial Lift Quantity (“ALQ”) in the group’s or node’s outlet branch in a production network. Note no units are stated as ALQ units are variable, for example Hz for ESP or rate for gas lift gas.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"GOPRNB":{"name":"GOPRNB","sections":["SUMMARY"],"supported":null,"summary":"Oil flow rate along the group’s or node’s outlet branch in a production network.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"GWPRNB":{"name":"GWPRNB","sections":["SUMMARY"],"supported":null,"summary":"Water flow rate along the group’s or node’s outlet branch in a production network.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"GGPRNB":{"name":"GGPRNB","sections":["SUMMARY"],"supported":null,"summary":"Gas flow rate along the group’s or node’s outlet branch in a production network.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"GLPRNB":{"name":"GLPRNB","sections":["SUMMARY"],"supported":null,"summary":"Liquid flow rate along the group’s or node’s outlet branch in a production network.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"GWIRNB":{"name":"GWIRNB","sections":["SUMMARY"],"supported":null,"summary":"Water flow rate along the group’s or node’s inlet branch in water injection network.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"GGIRNB":{"name":"GGIRNB","sections":["SUMMARY"],"supported":null,"summary":"Gas flow rate along the group’s or node’s inlet branch in gas injection network.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"DTMWAIT":{"name":"DTMWAIT","sections":["SUMMARY"],"supported":null,"summary":"Elapsed - Cumulative waiting time per process in seconds.","parameters":[],"example":"","size_kind":"none"},"ELAPSED":{"name":"ELAPSED","sections":["SUMMARY"],"supported":null,"summary":"Elapsed - Elapsed time in seconds.","parameters":[],"example":"","size_kind":"none"},"HLINEARS":{"name":"HLINEARS","sections":["SUMMARY"],"supported":null,"summary":"Iterations - Number of linear iterations for each gradient calculation (Gradient Option).","parameters":[],"example":"","size_kind":"none"},"HSUMLINS":{"name":"HSUMLINS","sections":["SUMMARY"],"supported":null,"summary":"Iterations - Total number of linear iterations for each gradient pressure (Gradient Option).","parameters":[],"example":"","size_kind":"none"},"MAXCFL":{"name":"MAXCFL","sections":["SUMMARY"],"supported":null,"summary":"Maximum Courant-Friedrichs-Lewy value for each time step. (Compositional keyword.)","parameters":[],"example":"","size_kind":"none"},"MAXDE":{"name":"MAXDE","sections":["SUMMARY"],"supported":null,"summary":"Maximum variation in energy for each time step. (Compositional keyword.)","parameters":[],"example":"","size_kind":"none"},"MAXDPR":{"name":"MAXDPR","sections":["SUMMARY"],"supported":null,"summary":"Maximum variation in pressure for each time step.","parameters":[],"example":"","size_kind":"none"},"MAXDSG":{"name":"MAXDSG","sections":["SUMMARY"],"supported":null,"summary":"Maximum variation in gas saturation for each time step.","parameters":[],"example":"","size_kind":"none"},"MAXDSO":{"name":"MAXDSO","sections":["SUMMARY"],"supported":null,"summary":"Maximum variation in oil saturation for each time step.","parameters":[],"example":"","size_kind":"none"},"MAXDSW":{"name":"MAXDSW","sections":["SUMMARY"],"supported":null,"summary":"Maximum variation in water saturation for each time step.","parameters":[],"example":"","size_kind":"none"},"MAXDT":{"name":"MAXDT","sections":["SUMMARY"],"supported":null,"summary":"Maximum variation in temperature for each time step. (Compositional keyword.)","parameters":[],"example":"","size_kind":"none"},"MEMORYTS":{"name":"MEMORYTS","sections":["SUMMARY"],"supported":null,"summary":"Memory - Operating system reported maximum current memory usage across all processors.","parameters":[],"example":"","size_kind":"none"},"MLINEARP":{"name":"MLINEARP","sections":["SUMMARY"],"supported":null,"summary":"CPR Solver - Number of pressure iterations for each time step.","parameters":[],"example":"","size_kind":"none"},"MLINEARS":{"name":"MLINEARS","sections":["SUMMARY"],"supported":null,"summary":"Iterations - Number of linear iterations for each time step.","parameters":[],"example":"","size_kind":"none"},"MSUMBUG":{"name":"MSUMBUG","sections":["SUMMARY"],"supported":null,"summary":"Messages - Cumulative number of BUG messages.","parameters":[],"example":"","size_kind":"none"},"MSUMCOMM":{"name":"MSUMCOMM","sections":["SUMMARY"],"supported":null,"summary":"Messages - Cumulative number of COMMENT messages.","parameters":[],"example":"","size_kind":"none"},"MSUMERR":{"name":"MSUMERR","sections":["SUMMARY"],"supported":null,"summary":"Messages - Cumulative number of ERROR messages.","parameters":[],"example":"","size_kind":"none"},"MSUMLINP":{"name":"MSUMLINP","sections":["SUMMARY"],"supported":null,"summary":"CPR Solver - Cumulative number of pressure iterations.","parameters":[],"example":"","size_kind":"none"},"MSUMLINS":{"name":"MSUMLINS","sections":["SUMMARY"],"supported":null,"summary":"Iterations - Cumulative number of linear iterations.","parameters":[],"example":"","size_kind":"none"},"MSUMMESS":{"name":"MSUMMESS","sections":["SUMMARY"],"supported":null,"summary":"Messages - Cumulative number of MESSAGES messages.","parameters":[],"example":"","size_kind":"none"},"MSUMNEWT":{"name":"MSUMNEWT","sections":["SUMMARY"],"supported":null,"summary":"Iterations - Cumulative number of Newton iterations.","parameters":[],"example":"","size_kind":"none"},"MSUMPROB":{"name":"MSUMPROB","sections":["SUMMARY"],"supported":null,"summary":"Messages - Cumulative number of PROBLEM messages.","parameters":[],"example":"","size_kind":"none"},"MSUMWARN":{"name":"MSUMWARN","sections":["SUMMARY"],"supported":null,"summary":"Messages - Cumulative number of WARNING messages.","parameters":[],"example":"","size_kind":"none"},"NBAKFL":{"name":"NBAKFL","sections":["SUMMARY"],"supported":null,"summary":"Number of flash calculations for each time step (Compositional keyword.)","parameters":[],"example":"","size_kind":"none"},"NBYTOT":{"name":"NBYTOT","sections":["SUMMARY"],"supported":null,"summary":"Memory - Peak usage of dynamically allocated memory reported by OPM Flow. For parallel cases this is the maximum across all processors.","parameters":[],"example":"","size_kind":"none"},"NCPRLINS":{"name":"NCPRLINS","sections":["SUMMARY"],"supported":null,"summary":"CPR Solver - Average number of pressure iterations per linear iteration for each time step.","parameters":[],"example":"","size_kind":"none"},"NEWTFL":{"name":"NEWTFL","sections":["SUMMARY"],"supported":null,"summary":"Iterations – Cumulative average number of Newton iterations per cell in flash calculations.. (Compositional keyword.)","parameters":[],"example":"","size_kind":"none"},"NLINEARP":{"name":"NLINEARP","sections":["SUMMARY"],"supported":null,"summary":"CPR Solver - Average number of pressure iterations per Newton iteration per time step.","parameters":[],"example":"","size_kind":"none"},"NLINEARS":{"name":"NLINEARS","sections":["SUMMARY"],"supported":null,"summary":"Iterations - Average number of linear iterations per Newton iteration for each time step. (For runs with LGRs, LLINEARS will automatically be exported for each LGR.)","parameters":[],"example":"","size_kind":"none"},"NLINSMAX":{"name":"NLINSMAX","sections":["SUMMARY"],"supported":null,"summary":"Iterations - Maximum number of linear iterations in the Newton iterations per time step.","parameters":[],"example":"","size_kind":"none"},"NLINSMIN":{"name":"NLINSMIN","sections":["SUMMARY"],"supported":null,"summary":"Iterations - Minimum number of linear iterations in the Newton iterations per time step.","parameters":[],"example":"","size_kind":"none"},"NNUMFL":{"name":"NNUMFL","sections":["SUMMARY"],"supported":null,"summary":"Cumulative number of flash calculations. (Compositional keyword.)","parameters":[],"example":"","size_kind":"none"},"NNUMST":{"name":"NNUMST","sections":["SUMMARY"],"supported":null,"summary":"Cumulative number of stability tests. (Compositional keyword.)","parameters":[],"example":"","size_kind":"none"},"NLRESSUM":{"name":"NLRESSUM","sections":["SUMMARY"],"supported":null,"summary":"Non-linear residual total. (Compositional keyword.)","parameters":[],"example":"","size_kind":"none"},"NLRESMAX":{"name":"NLRESMAX","sections":["SUMMARY"],"supported":null,"summary":"Non-linear residual maximum value. (Compositional keyword.)","parameters":[],"example":"","size_kind":"none"},"NTS":{"name":"NTS","sections":["SUMMARY"],"supported":null,"summary":"Number of time steps – taken. (Compositional keyword.)","parameters":[],"example":"","size_kind":"none"},"NTSPCL":{"name":"NTSPCL","sections":["SUMMARY"],"supported":null,"summary":"Number of time steps – pressure converged. (Compositional keyword.)","parameters":[],"example":"","size_kind":"none"},"NTSMCL":{"name":"NTSMCL","sections":["SUMMARY"],"supported":null,"summary":"Number of time steps – molar density converged. (Compositional keyword.)","parameters":[],"example":"","size_kind":"none"},"NTSECL":{"name":"NTSECL","sections":["SUMMARY"],"supported":null,"summary":"Number of time steps – energy density converged. (Compositional keyword.)","parameters":[],"example":"","size_kind":"none"},"STEPTYPE":{"name":"STEPTYPE","sections":["SUMMARY"],"supported":null,"summary":"Time Step – Criteria used to select the length of the time step, set to one of the following:","parameters":[],"example":"","size_kind":"none"},"TRNC":{"name":"TRNC","sections":["SUMMARY"],"supported":null,"summary":"2 (Controlled via time truncation error.)","parameters":[],"example":"","size_kind":"none"},"MINF":{"name":"MINF","sections":["SUMMARY"],"supported":null,"summary":"3 (Minimum ratio between one time step and the next.)","parameters":[],"example":"","size_kind":"none"},"MAXF":{"name":"MAXF","sections":["SUMMARY"],"supported":null,"summary":"4 (Maximum ratio between one time step and the next.)","parameters":[],"example":"","size_kind":"none"},"MINS":{"name":"MINS","sections":["SUMMARY"],"supported":null,"summary":"5 (Minimum permitted time step.)","parameters":[],"example":"","size_kind":"none"},"MAXS":{"name":"MAXS","sections":["SUMMARY"],"supported":null,"summary":"6 (Maximum permitted time step.)","parameters":[],"example":"","size_kind":"none"},"REPT":{"name":"REPT","sections":["SUMMARY"],"supported":null,"summary":"7 (Report time step.)","parameters":[],"example":"","size_kind":"none"},"HALF":{"name":"HALF","sections":["SUMMARY"],"supported":null,"summary":"8 (Half of the time set to reach the next report time step.)","parameters":[],"example":"","size_kind":"none"},"CHOP":{"name":"CHOP","sections":["SUMMARY"],"supported":null,"summary":"9 (Time step chopped due non-convergence of non-linear equations.)","parameters":[],"example":"","size_kind":"none"},"SATM":{"name":"SATM","sections":["SUMMARY"],"supported":null,"summary":"10 (Maximum saturation change.)","parameters":[],"example":"","size_kind":"none"},"PCHP":{"name":"PCHP","sections":["SUMMARY"],"supported":null,"summary":"11 (Time step chopped due to maximum pressure change in IMPES formulation.)","parameters":[],"example":"","size_kind":"none"},"DIFF":{"name":"DIFF","sections":["GRID"],"supported":null,"summary":"12 (Difficult time step after a time step CHOP.)","parameters":[],"example":"","size_kind":"array"},"LGRC":{"name":"LGRC","sections":["SUMMARY"],"supported":null,"summary":"13 (Determined by LGR fluid in-place error targets.)","parameters":[],"example":"","size_kind":"none"},"NETW":{"name":"NETW","sections":["SUMMARY"],"supported":null,"summary":"15 (Time step determined by network balancing controls.)","parameters":[],"example":"","size_kind":"none"},"THRP":{"name":"THRP","sections":["SUMMARY"],"supported":null,"summary":"16 (Time step controlled by maximum through put ratio.)","parameters":[],"example":"","size_kind":"none"},"EMTH":{"name":"EMTH","sections":["SUMMARY"],"supported":null,"summary":"17 (Time step selected to match the end of a month.)","parameters":[],"example":"","size_kind":"none"},"MAXP":{"name":"MAXP","sections":["SUMMARY"],"supported":null,"summary":"18 (Set by maximum expected grid block pressure change.)","parameters":[],"example":"","size_kind":"none"},"WCYC":{"name":"WCYC","sections":["SUMMARY"],"supported":null,"summary":"19 (Determined by well cycling on/off time.)","parameters":[],"example":"","size_kind":"none"},"MAST":{"name":"MAST","sections":["SUMMARY"],"supported":null,"summary":"20 (Chosen by the master simulation in a reservoir coupling run.)","parameters":[],"example":"","size_kind":"none"},"SLVR":{"name":"SLVR","sections":["SUMMARY"],"supported":null,"summary":"21 (Selected by a slave simulation to match a slave reporting time step, in a reservoir coupling run.)","parameters":[],"example":"","size_kind":"none"},"SLVC":{"name":"SLVC","sections":["SUMMARY"],"supported":null,"summary":"22 (Time step selected by a slave simulation due to a slave’s expected flow rate change in a reservoir coupling run.)","parameters":[],"example":"","size_kind":"none"},"MAXW":{"name":"MAXW","sections":["SUMMARY"],"supported":null,"summary":"23 (Maximum time step size after a well control event.)","parameters":[],"example":"","size_kind":"none"},"EFF+":{"name":"EFF+","sections":["SUMMARY"],"supported":null,"summary":"24 (Selected by ZIPPY optimum time selection algorithm.)","parameters":[],"example":"","size_kind":"none"},"EFF-":{"name":"EFF-","sections":["SUMMARY"],"supported":null,"summary":"25","parameters":[],"example":"","size_kind":"none"},"NLTR":{"name":"NLTR","sections":["SUMMARY"],"supported":null,"summary":"26","parameters":[],"example":"","size_kind":"none"},"EFFT":{"name":"EFFT","sections":["SUMMARY"],"supported":null,"summary":"27","parameters":[],"example":"","size_kind":"none"},"DLYA":{"name":"DLYA","sections":["SUMMARY"],"supported":null,"summary":"28","parameters":[],"example":"","size_kind":"none"},"ACTN":{"name":"ACTN","sections":["SUMMARY"],"supported":null,"summary":"29","parameters":[],"example":"","size_kind":"none"},"RAIN":{"name":"RAIN","sections":["SUMMARY"],"supported":null,"summary":"30","parameters":[],"example":"","size_kind":"none"},"TCPU":{"name":"TCPU","sections":["SUMMARY"],"supported":null,"summary":"CPU - Current CPU usage in seconds. (It does not consider the time taken by inter-process communications in parallel runs, whereas ELAPSED does. Thus, for parallel jobs, ELAPSED is the most relevant time measurement.)","parameters":[],"example":"","size_kind":"none"},"TCPUDAY":{"name":"TCPUDAY","sections":["SUMMARY"],"supported":null,"summary":"CPU - CPU time per day (or hour in lab units depending on run units system).","parameters":[],"example":"","size_kind":"none"},"TCPUH":{"name":"TCPUH","sections":["SUMMARY"],"supported":null,"summary":"CPU – Cumulative CPU time for each gradient calculation (Gradient Option).","parameters":[],"example":"","size_kind":"none"},"TCPUHT":{"name":"TCPUHT","sections":["SUMMARY"],"supported":null,"summary":"CPU - Cumulative CPU time for all gradient calculations (Gradient Option).","parameters":[],"example":"","size_kind":"none"},"TCPUSCH":{"name":"TCPUSCH","sections":["SUMMARY"],"supported":null,"summary":"CPU - Cumulative CPU time used in SCHEDULE section.","parameters":[],"example":"","size_kind":"none"},"TCPUTS":{"name":"TCPUTS","sections":["SUMMARY"],"supported":null,"summary":"CPU - CPU time per time step in seconds.","parameters":[],"example":"","size_kind":"none"},"TCPUTSH":{"name":"TCPUTSH","sections":["SUMMARY"],"supported":null,"summary":"CPU - CPU time per time step for each gradient calculation (Gradient Option).","parameters":[],"example":"","size_kind":"none"},"TCPUTSHT":{"name":"TCPUTSHT","sections":["SUMMARY"],"supported":null,"summary":"CPU - CPU time per time step for all gradient calculations (Gradient Option).","parameters":[],"example":"","size_kind":"none"},"TCPUTR":{"name":"TCPUTR","sections":["SUMMARY"],"supported":null,"summary":"CPU – Cumulative Tracer CPU time. (Compositional keyword.)","parameters":[],"example":"","size_kind":"none"},"TCPUTRSV":{"name":"TCPUTRSV","sections":["SUMMARY"],"supported":null,"summary":"CPU – Cumulative Tracer implicit CPU time. (Compositional keyword.)","parameters":[],"example":"","size_kind":"none"},"TCPULGTR":{"name":"TCPULGTR","sections":["SUMMARY"],"supported":null,"summary":"CPU – Cumulative Tracer Lagrangian tracer stramline CPU time. (Compositional keyword.)","parameters":[],"example":"","size_kind":"none"},"TCPULGSV":{"name":"TCPULGSV","sections":["SUMMARY"],"supported":null,"summary":"CPU – Cumulative Tracer Lagrangian tracer solver CPU time. (Compositional keyword.)","parameters":[],"example":"","size_kind":"none"},"TELAPDAY":{"name":"TELAPDAY","sections":["SUMMARY"],"supported":null,"summary":"Elapsed - Elapsed time per day (or hour in lab units).","parameters":[],"example":"","size_kind":"none"},"TELAPLIN":{"name":"TELAPLIN","sections":["SUMMARY"],"supported":null,"summary":"Elapsed - Elapsed time per linear iteration in seconds.","parameters":[],"example":"","size_kind":"none"},"TELAPTS":{"name":"TELAPTS","sections":["SUMMARY"],"supported":null,"summary":"Elapsed - Elapsed time per time step in seconds.","parameters":[],"example":"","size_kind":"none"},"TIMESTEP":{"name":"TIMESTEP","sections":["SUMMARY"],"supported":null,"summary":"Time Step - Length of time step.","parameters":[],"example":"","size_kind":"none"},"WNEWTON":{"name":"WNEWTON","sections":["SUMMARY"],"supported":null,"summary":"Iterations - Number of well Newton iterations taken in the last global Newton iteration. A negative value indicates that the well failed to converge.","parameters":[],"example":"","size_kind":"none"},"ZIPEFF":{"name":"ZIPEFF","sections":["SUMMARY"],"supported":null,"summary":"Time Step - Predicted efficiency of the time step (developer use).","parameters":[],"example":"","size_kind":"none"},"ZIPEFFC":{"name":"ZIPEFFC","sections":["SUMMARY"],"supported":null,"summary":"Time Step - Predicted efficiency of the time step divided by the actual efficiency (developer use).","parameters":[],"example":"","size_kind":"none"},"CCFR":{"name":"CCFR","sections":["SUMMARY"],"supported":null,"summary":"Polymer Flow Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"RCFT":{"name":"RCFT","sections":["SUMMARY"],"supported":null,"summary":"Polymer Flow Total (Inter-Region)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FCIR":{"name":"FCIR","sections":["SUMMARY"],"supported":null,"summary":"Polymer Injection Rate","parameters":[],"example":"","size_kind":"none"},"GCIR":{"name":"GCIR","sections":["SUMMARY"],"supported":null,"summary":"Polymer Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WCIR":{"name":"WCIR","sections":["SUMMARY"],"supported":null,"summary":"Polymer Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CCIR":{"name":"CCIR","sections":["SUMMARY"],"supported":null,"summary":"Polymer Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FCIT":{"name":"FCIT","sections":["SUMMARY"],"supported":null,"summary":"Polymer Injection Total","parameters":[],"example":"","size_kind":"none"},"GCIT":{"name":"GCIT","sections":["SUMMARY"],"supported":null,"summary":"Polymer Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WCIT":{"name":"WCIT","sections":["SUMMARY"],"supported":null,"summary":"Polymer Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CCIT":{"name":"CCIT","sections":["SUMMARY"],"supported":null,"summary":"Polymer Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FCPR":{"name":"FCPR","sections":["SUMMARY"],"supported":null,"summary":"Polymer Production Rate","parameters":[],"example":"","size_kind":"none"},"GCPR":{"name":"GCPR","sections":["SUMMARY"],"supported":null,"summary":"Polymer Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WCPR":{"name":"WCPR","sections":["SUMMARY"],"supported":null,"summary":"Polymer Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CCPR":{"name":"CCPR","sections":["SUMMARY"],"supported":null,"summary":"Polymer Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FCPT":{"name":"FCPT","sections":["SUMMARY"],"supported":null,"summary":"Polymer Production Total","parameters":[],"example":"","size_kind":"none"},"GCPT":{"name":"GCPT","sections":["SUMMARY"],"supported":null,"summary":"Polymer Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WCPT":{"name":"WCPT","sections":["SUMMARY"],"supported":null,"summary":"Polymer Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CCPT":{"name":"CCPT","sections":["SUMMARY"],"supported":null,"summary":"Polymer Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BCABnnn":{"name":"BCABnnn","sections":["SUMMARY"],"supported":null,"summary":"Polymer Adsorbed (PLYTRRFA). The highest temperature band at which residual resistance factor was calculated, see keyword PLYTRRFA. The band number nnn can range from 001 to 999, but must be less than or equal to the argument on the PLYTRRFA keyword.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FCAD":{"name":"FCAD","sections":["SUMMARY"],"supported":null,"summary":"Polymer Adsorption Total. Block is concentration.","parameters":[],"example":"","size_kind":"none"},"RCAD":{"name":"RCAD","sections":["SUMMARY"],"supported":null,"summary":"Polymer Adsorption Total. Block is concentration.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BCAD":{"name":"BCAD","sections":["SUMMARY"],"supported":null,"summary":"Polymer Adsorption Total. Block is concentration.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BEPVIS":{"name":"BEPVIS","sections":["SUMMARY"],"supported":null,"summary":"Polymer Solution (Effective Viscosity). Also BVPOLY.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BSHWVISI":{"name":"BSHWVISI","sections":["SUMMARY"],"supported":null,"summary":"Polymer Solution Shear Viscosity (Inter-Block I+ Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BSHWVISJ":{"name":"BSHWVISJ","sections":["SUMMARY"],"supported":null,"summary":"Polymer Solution Shear Viscosity (Inter-Block J+ Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BSHWVISK":{"name":"BSHWVISK","sections":["SUMMARY"],"supported":null,"summary":"Polymer Solution Shear Viscosity (Inter-Block K+ Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BCDCS":{"name":"BCDCS","sections":["SUMMARY"],"supported":null,"summary":"Polymer Thermal Degradation. Total mass degraded in previous time step.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BCDCR":{"name":"BCDCR","sections":["SUMMARY"],"supported":null,"summary":"Polymer Thermal Degradation Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BCDCA":{"name":"BCDCA","sections":["SUMMARY"],"supported":null,"summary":"Polymer Thermal Degradation Rate (Adsorbed)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BCDCP":{"name":"BCDCP","sections":["SUMMARY"],"supported":null,"summary":"Polymer Thermal Degradation Rate (Solution)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BEMVIS":{"name":"BEMVIS","sections":["SUMMARY"],"supported":null,"summary":"Polymer Water (Effective Viscosity). Based on block center properties.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BFLOW0I":{"name":"BFLOW0I","sections":["SUMMARY"],"supported":null,"summary":"Water Flow Rate Times Shear Multiplier (Inter-Block I+ Direction). Multiplied by the corresponding shear multiplier (PLYSHLOG and PLYSHEAR options only).","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BFLOW0J":{"name":"BFLOW0J","sections":["SUMMARY"],"supported":null,"summary":"Water Flow Rate Times Shear Multiplier (Inter-Block J+ Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BFLOW0K":{"name":"BFLOW0K","sections":["SUMMARY"],"supported":null,"summary":"Water Flow Rate Times Shear Multiplier (Inter-Block K+ Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BSRTWI":{"name":"BSRTWI","sections":["SUMMARY"],"supported":null,"summary":"Water Shear Rate After Shear Effects (Inter-Block I+ Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BSRTWJ":{"name":"BSRTWJ","sections":["SUMMARY"],"supported":null,"summary":"Water Shear Rate After Shear Effects (Inter-Block J+ Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BSRTWK":{"name":"BSRTWK","sections":["SUMMARY"],"supported":null,"summary":"Water Shear Rate After Shear Effects (Inter-Block K+ Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BSRTW0I":{"name":"BSRTW0I","sections":["SUMMARY"],"supported":null,"summary":"Water Shear Rate Prior to Shear Effects (Inter-Block I+ Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BSRTW0J":{"name":"BSRTW0J","sections":["SUMMARY"],"supported":null,"summary":"Water Shear Rate Prior to Shear Effects (Inter-Block J+ Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BSRTW0K":{"name":"BSRTW0K","sections":["SUMMARY"],"supported":null,"summary":"Water Shear Rate Prior to Shear Effects (Inter-Block K+ Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BVELW0I":{"name":"BVELW0I","sections":["SUMMARY"],"supported":null,"summary":"Water Velocity (Inter-Block I+ Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BVELW0J":{"name":"BVELW0J","sections":["SUMMARY"],"supported":null,"summary":"Water Velocity (Inter-Block J+ Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BVELW0K":{"name":"BVELW0K","sections":["SUMMARY"],"supported":null,"summary":"Water Velocity (Inter-Block K+ Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BEWV_POL":{"name":"BEWV_POL","sections":["SUMMARY"],"supported":null,"summary":"Water Viscosity (Effective)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BPSHLZI":{"name":"BPSHLZI","sections":["SUMMARY"],"supported":null,"summary":"Water Viscosity Sheared Factor (Inter-Block I+ Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BPSHLZJ":{"name":"BPSHLZJ","sections":["SUMMARY"],"supported":null,"summary":"Water Viscosity Sheared Factor (Inter-Block J+ Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BPSHLZK":{"name":"BPSHLZK","sections":["SUMMARY"],"supported":null,"summary":"Water Viscosity Sheared Factor (Inter-Block K+ Direction)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BCCN":{"name":"BCCN","sections":["SUMMARY"],"supported":null,"summary":"Polymer Concentration (Block)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FCIC":{"name":"FCIC","sections":["SUMMARY"],"supported":null,"summary":"Polymer Concentration (Injection)","parameters":[],"example":"","size_kind":"none"},"GCIC":{"name":"GCIC","sections":["SUMMARY"],"supported":null,"summary":"Polymer Concentration (Injection)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WCIC":{"name":"WCIC","sections":["SUMMARY"],"supported":null,"summary":"Polymer Concentration (Injection)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CCIC":{"name":"CCIC","sections":["SUMMARY"],"supported":null,"summary":"Polymer Concentration (Injection)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FCPC":{"name":"FCPC","sections":["SUMMARY"],"supported":null,"summary":"Polymer Concentration (Production)","parameters":[],"example":"","size_kind":"none"},"GCPC":{"name":"GCPC","sections":["SUMMARY"],"supported":null,"summary":"Polymer Concentration (Production)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WCPC":{"name":"WCPC","sections":["SUMMARY"],"supported":null,"summary":"Polymer Concentration (Production)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CCPC":{"name":"CCPC","sections":["SUMMARY"],"supported":null,"summary":"Polymer Concentration (Production)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FCIP":{"name":"FCIP","sections":["SUMMARY"],"supported":null,"summary":"Polymer Solution (In Solution)","parameters":[],"example":"","size_kind":"none"},"RCIP":{"name":"RCIP","sections":["SUMMARY"],"supported":null,"summary":"Polymer Solution (In Solution)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BCIP":{"name":"BCIP","sections":["SUMMARY"],"supported":null,"summary":"Polymer Solution (In Solution)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"RSFT":{"name":"RSFT","sections":["SUMMARY"],"supported":null,"summary":"Salt inter-region Flow Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CNFR":{"name":"CNFR","sections":["SUMMARY"],"supported":null,"summary":"Solvent Flow Rate. Field, group, and well gas rates and cumulative volumes include the solvent gas.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"RNFT":{"name":"RNFT","sections":["SUMMARY"],"supported":null,"summary":"Solvent Flow Total (Inter-Region)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FNIR":{"name":"FNIR","sections":["SUMMARY"],"supported":null,"summary":"Solvent Injection Rate","parameters":[],"example":"","size_kind":"none"},"GNIR":{"name":"GNIR","sections":["SUMMARY"],"supported":null,"summary":"Solvent Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WNIR":{"name":"WNIR","sections":["SUMMARY"],"supported":null,"summary":"Solvent Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FNIT":{"name":"FNIT","sections":["SUMMARY"],"supported":null,"summary":"Solvent Injection Total","parameters":[],"example":"","size_kind":"none"},"GNIT":{"name":"GNIT","sections":["SUMMARY"],"supported":null,"summary":"Solvent Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WNIT":{"name":"WNIT","sections":["SUMMARY"],"supported":null,"summary":"Solvent Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CNIT":{"name":"CNIT","sections":["SUMMARY"],"supported":null,"summary":"Solvent Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FNPR":{"name":"FNPR","sections":["SUMMARY"],"supported":null,"summary":"Solvent Production Rate","parameters":[],"example":"","size_kind":"none"},"GNPR":{"name":"GNPR","sections":["SUMMARY"],"supported":null,"summary":"Solvent Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WNPR":{"name":"WNPR","sections":["SUMMARY"],"supported":null,"summary":"Solvent Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FNPT":{"name":"FNPT","sections":["SUMMARY"],"supported":null,"summary":"Solvent Production Total","parameters":[],"example":"","size_kind":"none"},"GNPT":{"name":"GNPT","sections":["SUMMARY"],"supported":null,"summary":"Solvent Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WNPT":{"name":"WNPT","sections":["SUMMARY"],"supported":null,"summary":"Solvent Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CNPT":{"name":"CNPT","sections":["SUMMARY"],"supported":null,"summary":"Solvent Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BNKR":{"name":"BNKR","sections":["SUMMARY"],"supported":null,"summary":"Solvent Relative Permeability","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FNIP":{"name":"FNIP","sections":["SUMMARY"],"supported":null,"summary":"Solvent In-Place","parameters":[],"example":"","size_kind":"none"},"RNIP":{"name":"RNIP","sections":["SUMMARY"],"supported":null,"summary":"Solvent In-Place","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BNIP":{"name":"BNIP","sections":["SUMMARY"],"supported":null,"summary":"Solvent In-Place","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BNSAT":{"name":"BNSAT","sections":["SUMMARY"],"supported":null,"summary":"Solvent Saturation","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FTIRHEA":{"name":"FTIRHEA","sections":["SUMMARY"],"supported":null,"summary":"Energy Injection Rate","parameters":[],"example":"","size_kind":"none"},"GTIRHEA":{"name":"GTIRHEA","sections":["SUMMARY"],"supported":null,"summary":"Energy Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WTIRHEA":{"name":"WTIRHEA","sections":["SUMMARY"],"supported":null,"summary":"Energy Injection Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FTITHEA":{"name":"FTITHEA","sections":["SUMMARY"],"supported":null,"summary":"Energy Injection Total","parameters":[],"example":"","size_kind":"none"},"GTITHEA":{"name":"GTITHEA","sections":["SUMMARY"],"supported":null,"summary":"Energy Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WTITHEA":{"name":"WTITHEA","sections":["SUMMARY"],"supported":null,"summary":"Energy Injection Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FTPRHEA":{"name":"FTPRHEA","sections":["SUMMARY"],"supported":null,"summary":"Energy Production Rate","parameters":[],"example":"","size_kind":"none"},"GTPRHEA":{"name":"GTPRHEA","sections":["SUMMARY"],"supported":null,"summary":"Energy Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WTPRHEA":{"name":"WTPRHEA","sections":["SUMMARY"],"supported":null,"summary":"Energy Production Rate","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FTPTHEA":{"name":"FTPTHEA","sections":["SUMMARY"],"supported":null,"summary":"Energy Production Total","parameters":[],"example":"","size_kind":"none"},"GTPTHEA":{"name":"GTPTHEA","sections":["SUMMARY"],"supported":null,"summary":"Energy Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WTPTHEA":{"name":"WTPTHEA","sections":["SUMMARY"],"supported":null,"summary":"Energy Production Total","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BTCNFHEA":{"name":"BTCNFHEA","sections":["SUMMARY"],"supported":null,"summary":"Temperature (Block)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FTICHEA":{"name":"FTICHEA","sections":["SUMMARY"],"supported":null,"summary":"Temperature (Injection)","parameters":[],"example":"","size_kind":"none"},"GTICHEA":{"name":"GTICHEA","sections":["SUMMARY"],"supported":null,"summary":"Temperature (Injection)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WTICHEA":{"name":"WTICHEA","sections":["SUMMARY"],"supported":null,"summary":"Temperature (Injection)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FTPCHEA":{"name":"FTPCHEA","sections":["SUMMARY"],"supported":null,"summary":"Temperature (Production)","parameters":[],"example":"","size_kind":"none"},"GTPCHEA":{"name":"GTPCHEA","sections":["SUMMARY"],"supported":null,"summary":"Temperature (Production)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WTPCHEA":{"name":"WTPCHEA","sections":["SUMMARY"],"supported":null,"summary":"Temperature (Production)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BTPCHEA":{"name":"BTPCHEA","sections":["SUMMARY"],"supported":null,"summary":"Temperature (Production)","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FTIPTHEA":{"name":"FTIPTHEA","sections":["SUMMARY"],"supported":null,"summary":"Energy In-Place Difference. Difference in energy in- place from start of run to current time.","parameters":[],"example":"","size_kind":"none"},"RTIPTHEA4":{"name":"RTIPTHEA4","sections":["SUMMARY"],"supported":null,"summary":"Energy In-Place Difference. Difference in energy in- place from start of run to current time.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"BTIPTHEA":{"name":"BTIPTHEA","sections":["SUMMARY"],"supported":null,"summary":"Energy In-Place Difference. Difference in energy in- place from start of run to current time.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"FUXXXXXX":{"name":"FUXXXXXX","sections":["SUMMARY"],"supported":null,"summary":"UDQ Variable","parameters":[],"example":"","size_kind":"none"},"GUXXXXXX":{"name":"GUXXXXXX","sections":["SUMMARY"],"supported":null,"summary":"UDQ Variable","parameters":[],"example":"","size_kind":"fixed","size_count":1},"WUXXXXXX":{"name":"WUXXXXXX","sections":["SUMMARY"],"supported":null,"summary":"UDQ Variable","parameters":[],"example":"","size_kind":"fixed","size_count":1},"CUXXXXXX":{"name":"CUXXXXXX","sections":["SUMMARY"],"supported":null,"summary":"UDQ Variable","parameters":[],"example":"","size_kind":"fixed","size_count":1},"RUXXXXXX":{"name":"RUXXXXXX","sections":["SUMMARY"],"supported":null,"summary":"UDQ Variable","parameters":[],"example":"","size_kind":"fixed","size_count":1},"SUXXXXXX":{"name":"SUXXXXXX","sections":["SUMMARY"],"supported":null,"summary":"UDQ Variable","parameters":[],"example":"","size_kind":"fixed","size_count":1},"AQUIFER_PROBE_ANALYTIC":{"name":"AQUIFER_PROBE_ANALYTIC","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"AQUIFER_PROBE_ANALYTIC_NAMED":{"name":"AQUIFER_PROBE_ANALYTIC_NAMED","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"AQUIFER_PROBE_NUMERIC":{"name":"AQUIFER_PROBE_NUMERIC","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"BLOCK_PROBE":{"name":"BLOCK_PROBE","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"I","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"J","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"K","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":3,"size_kind":"list"},"COMPDATX":{"name":"COMPDATX","sections":["SCHEDULE"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"LGR","description":"","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"I","description":"","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"J","description":"","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"K1","description":"","units":{},"default":"","value_type":"INT"},{"index":6,"name":"K2","description":"","units":{},"default":"","value_type":"INT"},{"index":7,"name":"STATE","description":"","units":{},"default":"OPEN","value_type":"STRING"},{"index":8,"name":"SAT_TABLE","description":"","units":{},"default":"0","value_type":"INT"},{"index":9,"name":"CONNECTION_TRANSMISSIBILITY_FACTOR","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Viscosity*ReservoirVolume/Time*Pressure"},{"index":10,"name":"DIAMETER","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":11,"name":"Kh","description":"","units":{},"default":"-1","value_type":"DOUBLE","dimension":"Permeability*Length"},{"index":12,"name":"SKIN","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"1"},{"index":13,"name":"D_FACTOR","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":14,"name":"DIR","description":"","units":{},"default":"Z","value_type":"STRING"},{"index":15,"name":"PR","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"}],"example":"","expected_columns":15,"size_kind":"list"},"CONNECTION_PROBE":{"name":"CONNECTION_PROBE","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"I","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"J","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"K","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":4,"size_kind":"list"},"DEBUG_":{"name":"DEBUG_","sections":["RUNSPEC","GRID","EDIT","PROPS","REGIONS","SOLUTION","SUMMARY","SCHEDULE"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"Item1","description":"","units":{},"default":"0","value_type":"INT"},{"index":2,"name":"Item2","description":"","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"Item3","description":"","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"Item4","description":"","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"Item5","description":"","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"Item6","description":"","units":{},"default":"0","value_type":"INT"},{"index":7,"name":"Item7","description":"","units":{},"default":"0","value_type":"INT"},{"index":8,"name":"Item8","description":"","units":{},"default":"0","value_type":"INT"},{"index":9,"name":"Item9","description":"","units":{},"default":"0","value_type":"INT"},{"index":10,"name":"Item10","description":"","units":{},"default":"0","value_type":"INT"},{"index":11,"name":"Item11","description":"","units":{},"default":"0","value_type":"INT"},{"index":12,"name":"Item12","description":"","units":{},"default":"0","value_type":"INT"},{"index":13,"name":"Item13","description":"","units":{},"default":"0","value_type":"INT"},{"index":14,"name":"Item14","description":"","units":{},"default":"0","value_type":"INT"},{"index":15,"name":"Item15","description":"","units":{},"default":"0","value_type":"INT"},{"index":16,"name":"Item16","description":"","units":{},"default":"0","value_type":"INT"},{"index":17,"name":"Item17","description":"","units":{},"default":"0","value_type":"INT"},{"index":18,"name":"Item18","description":"","units":{},"default":"0","value_type":"INT"},{"index":19,"name":"Item19","description":"","units":{},"default":"0","value_type":"INT"},{"index":20,"name":"Item20","description":"","units":{},"default":"0","value_type":"INT"},{"index":21,"name":"Item21","description":"","units":{},"default":"0","value_type":"INT"},{"index":22,"name":"Item22","description":"","units":{},"default":"0","value_type":"INT"},{"index":23,"name":"Item23","description":"","units":{},"default":"0","value_type":"INT"},{"index":24,"name":"Item24","description":"","units":{},"default":"0","value_type":"INT"},{"index":25,"name":"Item25","description":"","units":{},"default":"0","value_type":"INT"},{"index":26,"name":"Item26","description":"","units":{},"default":"0","value_type":"INT"},{"index":27,"name":"Item27","description":"","units":{},"default":"0","value_type":"INT"},{"index":28,"name":"Item28","description":"","units":{},"default":"0","value_type":"INT"},{"index":29,"name":"Item29","description":"","units":{},"default":"0","value_type":"INT"},{"index":30,"name":"Item30","description":"","units":{},"default":"0","value_type":"INT"},{"index":31,"name":"Item31","description":"","units":{},"default":"0","value_type":"INT"},{"index":32,"name":"Item32","description":"","units":{},"default":"0","value_type":"INT"},{"index":33,"name":"Item33","description":"","units":{},"default":"0","value_type":"INT"},{"index":34,"name":"Item34","description":"","units":{},"default":"0","value_type":"INT"},{"index":35,"name":"Item35","description":"","units":{},"default":"0","value_type":"INT"},{"index":36,"name":"Item36","description":"","units":{},"default":"0","value_type":"INT"},{"index":37,"name":"Item37","description":"","units":{},"default":"0","value_type":"INT"},{"index":38,"name":"Item38","description":"","units":{},"default":"0","value_type":"INT"},{"index":39,"name":"Item39","description":"","units":{},"default":"0","value_type":"INT"},{"index":40,"name":"Item40","description":"","units":{},"default":"0","value_type":"INT"},{"index":41,"name":"Item41","description":"","units":{},"default":"0","value_type":"INT"},{"index":42,"name":"Item42","description":"","units":{},"default":"0","value_type":"INT"},{"index":43,"name":"Item43","description":"","units":{},"default":"0","value_type":"INT"},{"index":44,"name":"Item44","description":"","units":{},"default":"0","value_type":"INT"},{"index":45,"name":"Item45","description":"","units":{},"default":"0","value_type":"INT"},{"index":46,"name":"Item46","description":"","units":{},"default":"0","value_type":"INT"},{"index":47,"name":"Item47","description":"","units":{},"default":"0","value_type":"INT"},{"index":48,"name":"Item48","description":"","units":{},"default":"0","value_type":"INT"},{"index":49,"name":"Item49","description":"","units":{},"default":"0","value_type":"INT"},{"index":50,"name":"Item50","description":"","units":{},"default":"0","value_type":"INT"},{"index":51,"name":"Item51","description":"","units":{},"default":"0","value_type":"INT"},{"index":52,"name":"Item52","description":"","units":{},"default":"0","value_type":"INT"},{"index":53,"name":"Item53","description":"","units":{},"default":"0","value_type":"INT"},{"index":54,"name":"Item54","description":"","units":{},"default":"0","value_type":"INT"},{"index":55,"name":"Item55","description":"","units":{},"default":"0","value_type":"INT"},{"index":56,"name":"Item56","description":"","units":{},"default":"0","value_type":"INT"},{"index":57,"name":"Item57","description":"","units":{},"default":"0","value_type":"INT"},{"index":58,"name":"Item58","description":"","units":{},"default":"0","value_type":"INT"},{"index":59,"name":"Item59","description":"","units":{},"default":"0","value_type":"INT"},{"index":60,"name":"Item60","description":"","units":{},"default":"0","value_type":"INT"},{"index":61,"name":"Item61","description":"","units":{},"default":"0","value_type":"INT"},{"index":62,"name":"Item62","description":"","units":{},"default":"0","value_type":"INT"},{"index":63,"name":"Item63","description":"","units":{},"default":"0","value_type":"INT"},{"index":64,"name":"Item64","description":"","units":{},"default":"0","value_type":"INT"},{"index":65,"name":"Item65","description":"","units":{},"default":"0","value_type":"INT"},{"index":66,"name":"Item66","description":"","units":{},"default":"0","value_type":"INT"},{"index":67,"name":"Item67","description":"","units":{},"default":"0","value_type":"INT"},{"index":68,"name":"Item68","description":"","units":{},"default":"0","value_type":"INT"},{"index":69,"name":"Item69","description":"","units":{},"default":"0","value_type":"INT"},{"index":70,"name":"Item70","description":"","units":{},"default":"0","value_type":"INT"},{"index":71,"name":"Item71","description":"","units":{},"default":"0","value_type":"INT"},{"index":72,"name":"Item72","description":"","units":{},"default":"0","value_type":"INT"},{"index":73,"name":"Item73","description":"","units":{},"default":"0","value_type":"INT"},{"index":74,"name":"Item74","description":"","units":{},"default":"0","value_type":"INT"},{"index":75,"name":"Item75","description":"","units":{},"default":"0","value_type":"INT"},{"index":76,"name":"Item76","description":"","units":{},"default":"0","value_type":"INT"},{"index":77,"name":"Item77","description":"","units":{},"default":"0","value_type":"INT"},{"index":78,"name":"Item78","description":"","units":{},"default":"0","value_type":"INT"},{"index":79,"name":"Item79","description":"","units":{},"default":"0","value_type":"INT"},{"index":80,"name":"Item80","description":"","units":{},"default":"0","value_type":"INT"},{"index":81,"name":"Item81","description":"","units":{},"default":"0","value_type":"INT"},{"index":82,"name":"Item82","description":"","units":{},"default":"0","value_type":"INT"},{"index":83,"name":"Item83","description":"","units":{},"default":"0","value_type":"INT"},{"index":84,"name":"Item84","description":"","units":{},"default":"0","value_type":"INT"},{"index":85,"name":"Item85","description":"","units":{},"default":"0","value_type":"INT"},{"index":86,"name":"Item86","description":"","units":{},"default":"0","value_type":"INT"},{"index":87,"name":"Item87","description":"","units":{},"default":"0","value_type":"INT"}],"example":"","expected_columns":87,"size_kind":"fixed","size_count":1},"DEPTHZ":{"name":"DEPTHZ","sections":["GRID"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"ENDPOINT_SPECIFIERS":{"name":"ENDPOINT_SPECIFIERS","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"FIELD_PROBE":{"name":"FIELD_PROBE","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"none","size_count":0},"FIP_PROBE":{"name":"FIP_PROBE","sections":["REGIONS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"FIPSEP":{"name":"FIPSEP","sections":["SOLUTION"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"FLUID_IN_PLACE_REGION","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"STAGE_INDEX","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"STAGE_TEMPERATURE","description":"","units":{},"default":"15.56","value_type":"DOUBLE","dimension":"Temperature"},{"index":4,"name":"STAGE_PRESSURE","description":"","units":{},"default":"1.01325","value_type":"DOUBLE","dimension":"Pressure"},{"index":5,"name":"DESTINATION_OUPUT","description":"","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"DESTINATION_STAGE","description":"","units":{},"default":"0","value_type":"INT"},{"index":7,"name":"K_VAL_TABLE_NUM","description":"","units":{},"default":"0","value_type":"INT"},{"index":8,"name":"GAS_PLANT_TABLE_NUM","description":"","units":{},"default":"0","value_type":"INT"},{"index":9,"name":"SURF_EQ_STATE_NUM","description":"","units":{},"default":"","value_type":"INT"},{"index":10,"name":"DENSITY_EVAL_GAS_TEMP","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Temperature"},{"index":11,"name":"DENSITY_EVAL_PRESSURE_TEMP","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"}],"example":"","expected_columns":11,"size_kind":"list"},"GROUP_PROBE":{"name":"GROUP_PROBE","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"GROUPS","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","size_kind":"fixed","size_count":1},"HAxxxxxx":{"name":"HAxxxxxx","sections":["PROPS","REGIONS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"HMMULTxx":{"name":"HMMULTxx","sections":["GRID","EDIT"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"HMxxxxxx":{"name":"HMxxxxxx","sections":["REGIONS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"MSUM_PROBE":{"name":"MSUM_PROBE","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"none","size_count":0},"MULT_XYZ":{"name":"MULT_XYZ","sections":["GRID","EDIT","SCHEDULE"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"PEGTABX":{"name":"PEGTABX","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Pressure","Pressure"]}],"example":"","size_kind":"fixed"},"PEKTABX":{"name":"PEKTABX","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Pressure","Pressure"]}],"example":"","size_kind":"fixed"},"PERFORMANCE_PROBE":{"name":"PERFORMANCE_PROBE","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"none","size_count":0},"PERMXY":{"name":"PERMXY","sections":["GRID"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"PERMYZ":{"name":"PERMYZ","sections":["GRID"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"PERMZX":{"name":"PERMZX","sections":["GRID"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"PLYOPTS":{"name":"PLYOPTS","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"MIN_SWAT","description":"","units":{},"default":"1e-06","value_type":"DOUBLE"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"PSWRG":{"name":"PSWRG","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"PSWRO":{"name":"PSWRO","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"PVT_M":{"name":"PVT_M","sections":["RUNSPEC"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"none","size_count":0},"REGION2REGION_PROBE":{"name":"REGION2REGION_PROBE","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"REGION1","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"REGION2","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":2,"size_kind":"list"},"REGION_PROBE":{"name":"REGION_PROBE","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"ROCKV":{"name":"ROCKV","sections":["EDIT"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"SEGMENT_PROBE":{"name":"SEGMENT_PROBE","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"Well","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"Segment","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":2,"size_kind":"list"},"SIGMATH":{"name":"SIGMATH","sections":["GRID"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"SOLWNUM":{"name":"SOLWNUM","sections":["GRID"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"SURFOPTS":{"name":"SURFOPTS","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"MIN_SWAT","description":"","units":{},"default":"1e-06","value_type":"DOUBLE"},{"index":2,"name":"SMOOTHING","description":"","units":{},"default":"1e-06","value_type":"DOUBLE"}],"example":"","expected_columns":2,"size_kind":"fixed","size_count":1},"WELL_COMPLETION_PROBE":{"name":"WELL_COMPLETION_PROBE","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"COMPLETION","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":2,"size_kind":"list"},"WELL_PROBE":{"name":"WELL_PROBE","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"WELLS","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","size_kind":"fixed","size_count":1},"BLOCK_PROBE300":{"name":"BLOCK_PROBE300","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"I","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"J","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"K","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":3,"size_kind":"list"},"CIRCLE":{"name":"CIRCLE","sections":["GRID"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"none","size_count":0},"CREF":{"name":"CREF","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"COMPRESSIBILITY","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["1/Pressure"]}],"example":"","size_kind":"fixed"},"CREFW":{"name":"CREFW","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"COMPRESSIBILITY","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["1/Pressure"]}],"example":"","size_kind":"fixed"},"CREFWS":{"name":"CREFWS","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"COMPRESSIBILITY","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["1/Pressure"]}],"example":"","size_kind":"fixed"},"DREF":{"name":"DREF","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"DENSITY","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Density"]}],"example":"","size_kind":"fixed"},"DREFS":{"name":"DREFS","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"DENSITY","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Density"]}],"example":"","size_kind":"fixed"},"FIELDSEP":{"name":"FIELDSEP","sections":["SOLUTION"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"STAGE","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"TEMPERATURE","description":"","units":{},"default":"15.56","value_type":"DOUBLE","dimension":"Temperature"},{"index":3,"name":"PRESSURE","description":"","units":{},"default":"1.01325","value_type":"DOUBLE","dimension":"Pressure"},{"index":4,"name":"LIQ_DESTINATION","description":"","units":{},"default":"","value_type":"INT"},{"index":5,"name":"VAP_DESTINATION","description":"","units":{},"default":"","value_type":"INT"},{"index":6,"name":"KVALUE","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"1"},{"index":7,"name":"TABLE_NUM","description":"","units":{},"default":"0","value_type":"INT"},{"index":8,"name":"EOS_NUM","description":"","units":{},"default":"","value_type":"INT"},{"index":9,"name":"REF_TEMP","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Temperature"},{"index":10,"name":"REF_PRESS","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"}],"example":"","expected_columns":10,"size_kind":"list"},"HWELLS":{"name":"HWELLS","sections":["RUNSPEC"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"none","size_count":0},"MWS":{"name":"MWS","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"MOLAR_WEIGHT","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Mass/Moles"}],"example":"","size_kind":"fixed"},"OILCOMPR":{"name":"OILCOMPR","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"COMPRESSIBILITY","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":2,"name":"EXPANSION_COEFF_LINEAR","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"1/AbsoluteTemperature"},{"index":3,"name":"EXPANSION_COEFF_QUADRATIC","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"1/AbsoluteTemperature*AbsoluteTemperature"}],"example":"","expected_columns":3,"size_kind":"fixed"},"OILMW":{"name":"OILMW","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"MOLAR_WEIGHT","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","expected_columns":1,"size_kind":"fixed"},"OILVTIM":{"name":"OILVTIM","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"INTERPOLATION_METHOD","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"list"},"OPTIONS3":{"name":"OPTIONS3","sections":["RUNSPEC","SCHEDULE"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"ITEM1","description":"","units":{},"default":"0","value_type":"INT"},{"index":2,"name":"ITEM2","description":"","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"ITEM3","description":"","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"ITEM4","description":"","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"ITEM5","description":"","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"ITEM6","description":"","units":{},"default":"0","value_type":"INT"},{"index":7,"name":"ITEM7","description":"","units":{},"default":"0","value_type":"INT"},{"index":8,"name":"ITEM8","description":"","units":{},"default":"0","value_type":"INT"},{"index":9,"name":"ITEM9","description":"","units":{},"default":"0","value_type":"INT"},{"index":10,"name":"ITEM10","description":"","units":{},"default":"0","value_type":"INT"},{"index":11,"name":"ITEM11","description":"","units":{},"default":"0","value_type":"INT"},{"index":12,"name":"ITEM12","description":"","units":{},"default":"0","value_type":"INT"},{"index":13,"name":"ITEM13","description":"","units":{},"default":"0","value_type":"INT"},{"index":14,"name":"ITEM14","description":"","units":{},"default":"0","value_type":"INT"},{"index":15,"name":"ITEM15","description":"","units":{},"default":"0","value_type":"INT"},{"index":16,"name":"ITEM16","description":"","units":{},"default":"0","value_type":"INT"},{"index":17,"name":"ITEM17","description":"","units":{},"default":"0","value_type":"INT"},{"index":18,"name":"ITEM18","description":"","units":{},"default":"0","value_type":"INT"},{"index":19,"name":"ITEM19","description":"","units":{},"default":"0","value_type":"INT"},{"index":20,"name":"ITEM20","description":"","units":{},"default":"0","value_type":"INT"},{"index":21,"name":"ITEM21","description":"","units":{},"default":"0","value_type":"INT"},{"index":22,"name":"ITEM22","description":"","units":{},"default":"0","value_type":"INT"},{"index":23,"name":"ITEM23","description":"","units":{},"default":"0","value_type":"INT"},{"index":24,"name":"ITEM24","description":"","units":{},"default":"0","value_type":"INT"},{"index":25,"name":"ITEM25","description":"","units":{},"default":"0","value_type":"INT"},{"index":26,"name":"ITEM26","description":"","units":{},"default":"0","value_type":"INT"},{"index":27,"name":"ITEM27","description":"","units":{},"default":"0","value_type":"INT"},{"index":28,"name":"ITEM28","description":"","units":{},"default":"0","value_type":"INT"},{"index":29,"name":"ITEM29","description":"","units":{},"default":"0","value_type":"INT"},{"index":30,"name":"ITEM30","description":"","units":{},"default":"0","value_type":"INT"},{"index":31,"name":"ITEM31","description":"","units":{},"default":"0","value_type":"INT"},{"index":32,"name":"ITEM32","description":"","units":{},"default":"0","value_type":"INT"},{"index":33,"name":"ITEM33","description":"","units":{},"default":"0","value_type":"INT"},{"index":34,"name":"ITEM34","description":"","units":{},"default":"0","value_type":"INT"},{"index":35,"name":"ITEM35","description":"","units":{},"default":"0","value_type":"INT"},{"index":36,"name":"ITEM36","description":"","units":{},"default":"0","value_type":"INT"},{"index":37,"name":"ITEM37","description":"","units":{},"default":"0","value_type":"INT"},{"index":38,"name":"ITEM38","description":"","units":{},"default":"0","value_type":"INT"},{"index":39,"name":"ITEM39","description":"","units":{},"default":"0","value_type":"INT"},{"index":40,"name":"ITEM40","description":"","units":{},"default":"0","value_type":"INT"},{"index":41,"name":"ITEM41","description":"","units":{},"default":"0","value_type":"INT"},{"index":42,"name":"ITEM42","description":"","units":{},"default":"0","value_type":"INT"},{"index":43,"name":"ITEM43","description":"","units":{},"default":"0","value_type":"INT"},{"index":44,"name":"ITEM44","description":"","units":{},"default":"0","value_type":"INT"},{"index":45,"name":"ITEM45","description":"","units":{},"default":"0","value_type":"INT"},{"index":46,"name":"ITEM46","description":"","units":{},"default":"0","value_type":"INT"},{"index":47,"name":"ITEM47","description":"","units":{},"default":"0","value_type":"INT"},{"index":48,"name":"ITEM48","description":"","units":{},"default":"0","value_type":"INT"},{"index":49,"name":"ITEM49","description":"","units":{},"default":"0","value_type":"INT"},{"index":50,"name":"ITEM50","description":"","units":{},"default":"0","value_type":"INT"},{"index":51,"name":"ITEM51","description":"","units":{},"default":"0","value_type":"INT"},{"index":52,"name":"ITEM52","description":"","units":{},"default":"0","value_type":"INT"},{"index":53,"name":"ITEM53","description":"","units":{},"default":"0","value_type":"INT"},{"index":54,"name":"ITEM54","description":"","units":{},"default":"0","value_type":"INT"},{"index":55,"name":"ITEM55","description":"","units":{},"default":"0","value_type":"INT"},{"index":56,"name":"ITEM56","description":"","units":{},"default":"0","value_type":"INT"},{"index":57,"name":"ITEM57","description":"","units":{},"default":"0","value_type":"INT"},{"index":58,"name":"ITEM58","description":"","units":{},"default":"0","value_type":"INT"},{"index":59,"name":"ITEM59","description":"","units":{},"default":"0","value_type":"INT"},{"index":60,"name":"ITEM60","description":"","units":{},"default":"0","value_type":"INT"},{"index":61,"name":"ITEM61","description":"","units":{},"default":"0","value_type":"INT"},{"index":62,"name":"ITEM62","description":"","units":{},"default":"0","value_type":"INT"},{"index":63,"name":"ITEM63","description":"","units":{},"default":"0","value_type":"INT"},{"index":64,"name":"ITEM64","description":"","units":{},"default":"0","value_type":"INT"},{"index":65,"name":"ITEM65","description":"","units":{},"default":"0","value_type":"INT"},{"index":66,"name":"ITEM66","description":"","units":{},"default":"0","value_type":"INT"},{"index":67,"name":"ITEM67","description":"","units":{},"default":"0","value_type":"INT"},{"index":68,"name":"ITEM68","description":"","units":{},"default":"0","value_type":"INT"},{"index":69,"name":"ITEM69","description":"","units":{},"default":"0","value_type":"INT"},{"index":70,"name":"ITEM70","description":"","units":{},"default":"0","value_type":"INT"},{"index":71,"name":"ITEM71","description":"","units":{},"default":"0","value_type":"INT"},{"index":72,"name":"ITEM72","description":"","units":{},"default":"0","value_type":"INT"},{"index":73,"name":"ITEM73","description":"","units":{},"default":"0","value_type":"INT"},{"index":74,"name":"ITEM74","description":"","units":{},"default":"0","value_type":"INT"},{"index":75,"name":"ITEM75","description":"","units":{},"default":"0","value_type":"INT"},{"index":76,"name":"ITEM76","description":"","units":{},"default":"0","value_type":"INT"},{"index":77,"name":"ITEM77","description":"","units":{},"default":"0","value_type":"INT"},{"index":78,"name":"ITEM78","description":"","units":{},"default":"0","value_type":"INT"},{"index":79,"name":"ITEM79","description":"","units":{},"default":"0","value_type":"INT"},{"index":80,"name":"ITEM80","description":"","units":{},"default":"0","value_type":"INT"},{"index":81,"name":"ITEM81","description":"","units":{},"default":"0","value_type":"INT"},{"index":82,"name":"ITEM82","description":"","units":{},"default":"0","value_type":"INT"},{"index":83,"name":"ITEM83","description":"","units":{},"default":"0","value_type":"INT"},{"index":84,"name":"ITEM84","description":"","units":{},"default":"0","value_type":"INT"},{"index":85,"name":"ITEM85","description":"","units":{},"default":"0","value_type":"INT"},{"index":86,"name":"ITEM86","description":"","units":{},"default":"0","value_type":"INT"},{"index":87,"name":"ITEM87","description":"","units":{},"default":"0","value_type":"INT"},{"index":88,"name":"ITEM88","description":"","units":{},"default":"0","value_type":"INT"},{"index":89,"name":"ITEM89","description":"","units":{},"default":"0","value_type":"INT"},{"index":90,"name":"ITEM90","description":"","units":{},"default":"0","value_type":"INT"},{"index":91,"name":"ITEM91","description":"","units":{},"default":"0","value_type":"INT"},{"index":92,"name":"ITEM92","description":"","units":{},"default":"0","value_type":"INT"},{"index":93,"name":"ITEM93","description":"","units":{},"default":"0","value_type":"INT"},{"index":94,"name":"ITEM94","description":"","units":{},"default":"0","value_type":"INT"},{"index":95,"name":"ITEM95","description":"","units":{},"default":"0","value_type":"INT"},{"index":96,"name":"ITEM96","description":"","units":{},"default":"0","value_type":"INT"},{"index":97,"name":"ITEM97","description":"","units":{},"default":"0","value_type":"INT"},{"index":98,"name":"ITEM98","description":"","units":{},"default":"0","value_type":"INT"},{"index":99,"name":"ITEM99","description":"","units":{},"default":"0","value_type":"INT"},{"index":100,"name":"ITEM100","description":"","units":{},"default":"0","value_type":"INT"},{"index":101,"name":"ITEM101","description":"","units":{},"default":"0","value_type":"INT"},{"index":102,"name":"ITEM102","description":"","units":{},"default":"0","value_type":"INT"},{"index":103,"name":"ITEM103","description":"","units":{},"default":"0","value_type":"INT"},{"index":104,"name":"ITEM104","description":"","units":{},"default":"0","value_type":"INT"},{"index":105,"name":"ITEM105","description":"","units":{},"default":"0","value_type":"INT"},{"index":106,"name":"ITEM106","description":"","units":{},"default":"0","value_type":"INT"},{"index":107,"name":"ITEM107","description":"","units":{},"default":"0","value_type":"INT"},{"index":108,"name":"ITEM108","description":"","units":{},"default":"0","value_type":"INT"},{"index":109,"name":"ITEM109","description":"","units":{},"default":"0","value_type":"INT"},{"index":110,"name":"ITEM110","description":"","units":{},"default":"0","value_type":"INT"},{"index":111,"name":"ITEM111","description":"","units":{},"default":"0","value_type":"INT"},{"index":112,"name":"ITEM112","description":"","units":{},"default":"0","value_type":"INT"},{"index":113,"name":"ITEM113","description":"","units":{},"default":"0","value_type":"INT"},{"index":114,"name":"ITEM114","description":"","units":{},"default":"0","value_type":"INT"},{"index":115,"name":"ITEM115","description":"","units":{},"default":"0","value_type":"INT"},{"index":116,"name":"ITEM116","description":"","units":{},"default":"0","value_type":"INT"},{"index":117,"name":"ITEM117","description":"","units":{},"default":"0","value_type":"INT"},{"index":118,"name":"ITEM118","description":"","units":{},"default":"0","value_type":"INT"},{"index":119,"name":"ITEM119","description":"","units":{},"default":"0","value_type":"INT"},{"index":120,"name":"ITEM120","description":"","units":{},"default":"0","value_type":"INT"},{"index":121,"name":"ITEM121","description":"","units":{},"default":"0","value_type":"INT"},{"index":122,"name":"ITEM122","description":"","units":{},"default":"0","value_type":"INT"},{"index":123,"name":"ITEM123","description":"","units":{},"default":"0","value_type":"INT"},{"index":124,"name":"ITEM124","description":"","units":{},"default":"0","value_type":"INT"},{"index":125,"name":"ITEM125","description":"","units":{},"default":"0","value_type":"INT"},{"index":126,"name":"ITEM126","description":"","units":{},"default":"0","value_type":"INT"},{"index":127,"name":"ITEM127","description":"","units":{},"default":"0","value_type":"INT"},{"index":128,"name":"ITEM128","description":"","units":{},"default":"0","value_type":"INT"},{"index":129,"name":"ITEM129","description":"","units":{},"default":"0","value_type":"INT"},{"index":130,"name":"ITEM130","description":"","units":{},"default":"0","value_type":"INT"},{"index":131,"name":"ITEM131","description":"","units":{},"default":"0","value_type":"INT"},{"index":132,"name":"ITEM132","description":"","units":{},"default":"0","value_type":"INT"},{"index":133,"name":"ITEM133","description":"","units":{},"default":"0","value_type":"INT"},{"index":134,"name":"ITEM134","description":"","units":{},"default":"0","value_type":"INT"},{"index":135,"name":"ITEM135","description":"","units":{},"default":"0","value_type":"INT"},{"index":136,"name":"ITEM136","description":"","units":{},"default":"0","value_type":"INT"},{"index":137,"name":"ITEM137","description":"","units":{},"default":"0","value_type":"INT"},{"index":138,"name":"ITEM138","description":"","units":{},"default":"0","value_type":"INT"},{"index":139,"name":"ITEM139","description":"","units":{},"default":"0","value_type":"INT"},{"index":140,"name":"ITEM140","description":"","units":{},"default":"0","value_type":"INT"},{"index":141,"name":"ITEM141","description":"","units":{},"default":"0","value_type":"INT"},{"index":142,"name":"ITEM142","description":"","units":{},"default":"0","value_type":"INT"},{"index":143,"name":"ITEM143","description":"","units":{},"default":"0","value_type":"INT"},{"index":144,"name":"ITEM144","description":"","units":{},"default":"0","value_type":"INT"},{"index":145,"name":"ITEM145","description":"","units":{},"default":"0","value_type":"INT"},{"index":146,"name":"ITEM146","description":"","units":{},"default":"0","value_type":"INT"},{"index":147,"name":"ITEM147","description":"","units":{},"default":"0","value_type":"INT"},{"index":148,"name":"ITEM148","description":"","units":{},"default":"0","value_type":"INT"},{"index":149,"name":"ITEM149","description":"","units":{},"default":"0","value_type":"INT"},{"index":150,"name":"ITEM150","description":"","units":{},"default":"0","value_type":"INT"},{"index":151,"name":"ITEM151","description":"","units":{},"default":"0","value_type":"INT"},{"index":152,"name":"ITEM152","description":"","units":{},"default":"0","value_type":"INT"},{"index":153,"name":"ITEM153","description":"","units":{},"default":"0","value_type":"INT"},{"index":154,"name":"ITEM154","description":"","units":{},"default":"0","value_type":"INT"},{"index":155,"name":"ITEM155","description":"","units":{},"default":"0","value_type":"INT"},{"index":156,"name":"ITEM156","description":"","units":{},"default":"0","value_type":"INT"},{"index":157,"name":"ITEM157","description":"","units":{},"default":"0","value_type":"INT"},{"index":158,"name":"ITEM158","description":"","units":{},"default":"0","value_type":"INT"},{"index":159,"name":"ITEM159","description":"","units":{},"default":"0","value_type":"INT"},{"index":160,"name":"ITEM160","description":"","units":{},"default":"0","value_type":"INT"},{"index":161,"name":"ITEM161","description":"","units":{},"default":"0","value_type":"INT"},{"index":162,"name":"ITEM162","description":"","units":{},"default":"0","value_type":"INT"},{"index":163,"name":"ITEM163","description":"","units":{},"default":"0","value_type":"INT"},{"index":164,"name":"ITEM164","description":"","units":{},"default":"0","value_type":"INT"},{"index":165,"name":"ITEM165","description":"","units":{},"default":"0","value_type":"INT"},{"index":166,"name":"ITEM166","description":"","units":{},"default":"0","value_type":"INT"},{"index":167,"name":"ITEM167","description":"","units":{},"default":"0","value_type":"INT"},{"index":168,"name":"ITEM168","description":"","units":{},"default":"0","value_type":"INT"},{"index":169,"name":"ITEM169","description":"","units":{},"default":"0","value_type":"INT"},{"index":170,"name":"ITEM170","description":"","units":{},"default":"0","value_type":"INT"},{"index":171,"name":"ITEM171","description":"","units":{},"default":"0","value_type":"INT"},{"index":172,"name":"ITEM172","description":"","units":{},"default":"0","value_type":"INT"},{"index":173,"name":"ITEM173","description":"","units":{},"default":"0","value_type":"INT"},{"index":174,"name":"ITEM174","description":"","units":{},"default":"0","value_type":"INT"},{"index":175,"name":"ITEM175","description":"","units":{},"default":"0","value_type":"INT"},{"index":176,"name":"ITEM176","description":"","units":{},"default":"0","value_type":"INT"},{"index":177,"name":"ITEM177","description":"","units":{},"default":"0","value_type":"INT"},{"index":178,"name":"ITEM178","description":"","units":{},"default":"0","value_type":"INT"},{"index":179,"name":"ITEM179","description":"","units":{},"default":"0","value_type":"INT"},{"index":180,"name":"ITEM180","description":"","units":{},"default":"0","value_type":"INT"},{"index":181,"name":"ITEM181","description":"","units":{},"default":"0","value_type":"INT"},{"index":182,"name":"ITEM182","description":"","units":{},"default":"0","value_type":"INT"},{"index":183,"name":"ITEM183","description":"","units":{},"default":"0","value_type":"INT"},{"index":184,"name":"ITEM184","description":"","units":{},"default":"0","value_type":"INT"},{"index":185,"name":"ITEM185","description":"","units":{},"default":"0","value_type":"INT"},{"index":186,"name":"ITEM186","description":"","units":{},"default":"0","value_type":"INT"},{"index":187,"name":"ITEM187","description":"","units":{},"default":"0","value_type":"INT"},{"index":188,"name":"ITEM188","description":"","units":{},"default":"0","value_type":"INT"},{"index":189,"name":"ITEM189","description":"","units":{},"default":"0","value_type":"INT"},{"index":190,"name":"ITEM190","description":"","units":{},"default":"0","value_type":"INT"},{"index":191,"name":"ITEM191","description":"","units":{},"default":"0","value_type":"INT"},{"index":192,"name":"ITEM192","description":"","units":{},"default":"0","value_type":"INT"},{"index":193,"name":"ITEM193","description":"","units":{},"default":"0","value_type":"INT"},{"index":194,"name":"ITEM194","description":"","units":{},"default":"0","value_type":"INT"},{"index":195,"name":"ITEM195","description":"","units":{},"default":"0","value_type":"INT"},{"index":196,"name":"ITEM196","description":"","units":{},"default":"0","value_type":"INT"},{"index":197,"name":"ITEM197","description":"","units":{},"default":"0","value_type":"INT"},{"index":198,"name":"ITEM198","description":"","units":{},"default":"0","value_type":"INT"},{"index":199,"name":"ITEM199","description":"","units":{},"default":"0","value_type":"INT"},{"index":200,"name":"ITEM200","description":"","units":{},"default":"0","value_type":"INT"},{"index":201,"name":"ITEM201","description":"","units":{},"default":"0","value_type":"INT"},{"index":202,"name":"ITEM202","description":"","units":{},"default":"0","value_type":"INT"},{"index":203,"name":"ITEM203","description":"","units":{},"default":"0","value_type":"INT"},{"index":204,"name":"ITEM204","description":"","units":{},"default":"0","value_type":"INT"},{"index":205,"name":"ITEM205","description":"","units":{},"default":"0","value_type":"INT"},{"index":206,"name":"ITEM206","description":"","units":{},"default":"0","value_type":"INT"},{"index":207,"name":"ITEM207","description":"","units":{},"default":"0","value_type":"INT"},{"index":208,"name":"ITEM208","description":"","units":{},"default":"0","value_type":"INT"},{"index":209,"name":"ITEM209","description":"","units":{},"default":"0","value_type":"INT"},{"index":210,"name":"ITEM210","description":"","units":{},"default":"0","value_type":"INT"},{"index":211,"name":"ITEM211","description":"","units":{},"default":"0","value_type":"INT"},{"index":212,"name":"ITEM212","description":"","units":{},"default":"0","value_type":"INT"},{"index":213,"name":"ITEM213","description":"","units":{},"default":"0","value_type":"INT"},{"index":214,"name":"ITEM214","description":"","units":{},"default":"0","value_type":"INT"},{"index":215,"name":"ITEM215","description":"","units":{},"default":"0","value_type":"INT"},{"index":216,"name":"ITEM216","description":"","units":{},"default":"0","value_type":"INT"},{"index":217,"name":"ITEM217","description":"","units":{},"default":"0","value_type":"INT"},{"index":218,"name":"ITEM218","description":"","units":{},"default":"0","value_type":"INT"},{"index":219,"name":"ITEM219","description":"","units":{},"default":"0","value_type":"INT"},{"index":220,"name":"ITEM220","description":"","units":{},"default":"0","value_type":"INT"},{"index":221,"name":"ITEM221","description":"","units":{},"default":"0","value_type":"INT"},{"index":222,"name":"ITEM222","description":"","units":{},"default":"0","value_type":"INT"},{"index":223,"name":"ITEM223","description":"","units":{},"default":"0","value_type":"INT"},{"index":224,"name":"ITEM224","description":"","units":{},"default":"0","value_type":"INT"},{"index":225,"name":"ITEM225","description":"","units":{},"default":"0","value_type":"INT"},{"index":226,"name":"ITEM226","description":"","units":{},"default":"0","value_type":"INT"},{"index":227,"name":"ITEM227","description":"","units":{},"default":"0","value_type":"INT"},{"index":228,"name":"ITEM228","description":"","units":{},"default":"0","value_type":"INT"},{"index":229,"name":"ITEM229","description":"","units":{},"default":"0","value_type":"INT"},{"index":230,"name":"ITEM230","description":"","units":{},"default":"0","value_type":"INT"},{"index":231,"name":"ITEM231","description":"","units":{},"default":"0","value_type":"INT"},{"index":232,"name":"ITEM232","description":"","units":{},"default":"0","value_type":"INT"},{"index":233,"name":"ITEM233","description":"","units":{},"default":"0","value_type":"INT"},{"index":234,"name":"ITEM234","description":"","units":{},"default":"0","value_type":"INT"},{"index":235,"name":"ITEM235","description":"","units":{},"default":"0","value_type":"INT"},{"index":236,"name":"ITEM236","description":"","units":{},"default":"0","value_type":"INT"},{"index":237,"name":"ITEM237","description":"","units":{},"default":"0","value_type":"INT"},{"index":238,"name":"ITEM238","description":"","units":{},"default":"0","value_type":"INT"},{"index":239,"name":"ITEM239","description":"","units":{},"default":"0","value_type":"INT"},{"index":240,"name":"ITEM240","description":"","units":{},"default":"0","value_type":"INT"},{"index":241,"name":"ITEM241","description":"","units":{},"default":"0","value_type":"INT"},{"index":242,"name":"ITEM242","description":"","units":{},"default":"0","value_type":"INT"},{"index":243,"name":"ITEM243","description":"","units":{},"default":"0","value_type":"INT"},{"index":244,"name":"ITEM244","description":"","units":{},"default":"0","value_type":"INT"},{"index":245,"name":"ITEM245","description":"","units":{},"default":"0","value_type":"INT"},{"index":246,"name":"ITEM246","description":"","units":{},"default":"0","value_type":"INT"},{"index":247,"name":"ITEM247","description":"","units":{},"default":"0","value_type":"INT"},{"index":248,"name":"ITEM248","description":"","units":{},"default":"0","value_type":"INT"},{"index":249,"name":"ITEM249","description":"","units":{},"default":"0","value_type":"INT"},{"index":250,"name":"ITEM250","description":"","units":{},"default":"0","value_type":"INT"},{"index":251,"name":"ITEM251","description":"","units":{},"default":"0","value_type":"INT"},{"index":252,"name":"ITEM252","description":"","units":{},"default":"0","value_type":"INT"},{"index":253,"name":"ITEM253","description":"","units":{},"default":"0","value_type":"INT"},{"index":254,"name":"ITEM254","description":"","units":{},"default":"0","value_type":"INT"},{"index":255,"name":"ITEM255","description":"","units":{},"default":"0","value_type":"INT"},{"index":256,"name":"ITEM256","description":"","units":{},"default":"0","value_type":"INT"},{"index":257,"name":"ITEM257","description":"","units":{},"default":"0","value_type":"INT"},{"index":258,"name":"ITEM258","description":"","units":{},"default":"0","value_type":"INT"},{"index":259,"name":"ITEM259","description":"","units":{},"default":"0","value_type":"INT"},{"index":260,"name":"ITEM260","description":"","units":{},"default":"0","value_type":"INT"},{"index":261,"name":"ITEM261","description":"","units":{},"default":"0","value_type":"INT"},{"index":262,"name":"ITEM262","description":"","units":{},"default":"0","value_type":"INT"},{"index":263,"name":"ITEM263","description":"","units":{},"default":"0","value_type":"INT"},{"index":264,"name":"ITEM264","description":"","units":{},"default":"0","value_type":"INT"},{"index":265,"name":"ITEM265","description":"","units":{},"default":"0","value_type":"INT"},{"index":266,"name":"ITEM266","description":"","units":{},"default":"0","value_type":"INT"},{"index":267,"name":"ITEM267","description":"","units":{},"default":"0","value_type":"INT"},{"index":268,"name":"ITEM268","description":"","units":{},"default":"0","value_type":"INT"},{"index":269,"name":"ITEM269","description":"","units":{},"default":"0","value_type":"INT"},{"index":270,"name":"ITEM270","description":"","units":{},"default":"0","value_type":"INT"},{"index":271,"name":"ITEM271","description":"","units":{},"default":"0","value_type":"INT"},{"index":272,"name":"ITEM272","description":"","units":{},"default":"0","value_type":"INT"},{"index":273,"name":"ITEM273","description":"","units":{},"default":"0","value_type":"INT"},{"index":274,"name":"ITEM274","description":"","units":{},"default":"0","value_type":"INT"},{"index":275,"name":"ITEM275","description":"","units":{},"default":"0","value_type":"INT"},{"index":276,"name":"ITEM276","description":"","units":{},"default":"0","value_type":"INT"},{"index":277,"name":"ITEM277","description":"","units":{},"default":"0","value_type":"INT"},{"index":278,"name":"ITEM278","description":"","units":{},"default":"0","value_type":"INT"},{"index":279,"name":"ITEM279","description":"","units":{},"default":"0","value_type":"INT"},{"index":280,"name":"ITEM280","description":"","units":{},"default":"0","value_type":"INT"},{"index":281,"name":"ITEM281","description":"","units":{},"default":"0","value_type":"INT"},{"index":282,"name":"ITEM282","description":"","units":{},"default":"0","value_type":"INT"},{"index":283,"name":"ITEM283","description":"","units":{},"default":"0","value_type":"INT"},{"index":284,"name":"ITEM284","description":"","units":{},"default":"0","value_type":"INT"},{"index":285,"name":"ITEM285","description":"","units":{},"default":"0","value_type":"INT"},{"index":286,"name":"ITEM286","description":"","units":{},"default":"0","value_type":"INT"},{"index":287,"name":"ITEM287","description":"","units":{},"default":"0","value_type":"INT"},{"index":288,"name":"ITEM288","description":"","units":{},"default":"0","value_type":"INT"}],"example":"","expected_columns":288,"size_kind":"fixed","size_count":1},"PREF":{"name":"PREF","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"PRESSURE","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Pressure"]}],"example":"","size_kind":"fixed"},"PREFS":{"name":"PREFS","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"PRESSURE","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Pressure"]}],"example":"","size_kind":"fixed"},"REGION2REGION_PROBE_E300":{"name":"REGION2REGION_PROBE_E300","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"REGION1","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"REGION2","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":2,"size_kind":"list"},"SOLID":{"name":"SOLID","sections":["RUNSPEC"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"none","size_count":0},"STCOND":{"name":"STCOND","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"TEMPERATURE","description":"","units":{},"default":"15.56","value_type":"DOUBLE","dimension":"Temperature"},{"index":2,"name":"PRESSURE","description":"","units":{},"default":"1.01325","value_type":"DOUBLE","dimension":"Pressure"}],"example":"","expected_columns":2,"size_kind":"fixed","size_count":1},"TREF":{"name":"TREF","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"TEMPERATURE","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["AbsoluteTemperature"]}],"example":"","size_kind":"fixed"},"TREFS":{"name":"TREFS","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"TEMPERATURE","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["AbsoluteTemperature"]}],"example":"","size_kind":"fixed"},"WECONCMF":{"name":"WECONCMF","sections":["SCHEDULE"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"COMPONENT_INDEX","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"MAXIMUM_MOLE_FRACTION","description":"","units":{},"default":"","value_type":"UDA"},{"index":4,"name":"WORKOVER_PROCEDURE","description":"","units":{},"default":"NONE","value_type":"STRING"},{"index":5,"name":"END_RUN_FLAG","description":"","units":{},"default":"NO","value_type":"STRING"}],"example":"","expected_columns":5,"size_kind":"list"},"WELL_PROBE_COMP":{"name":"WELL_PROBE_COMP","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"WELLS","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"COMP_NUM","description":"","units":{},"default":"","value_type":"INT"}],"example":"","size_kind":"list"},"XMF":{"name":"XMF","sections":["SOLUTION"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"YMF":{"name":"YMF","sections":["SOLUTION"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"ZFACT1":{"name":"ZFACT1","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"Z0","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["1"]}],"example":"","size_kind":"fixed"},"ZFACT1S":{"name":"ZFACT1S","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"Z0","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["1"]}],"example":"","size_kind":"fixed"},"ZFACTOR":{"name":"ZFACTOR","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"Z0","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["1"]}],"example":"","size_kind":"fixed"},"ZFACTORS":{"name":"ZFACTORS","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"Z0","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["1"]}],"example":"","size_kind":"fixed"},"ZMF":{"name":"ZMF","sections":["SOLUTION"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"NOGRAV":{"name":"NOGRAV","sections":["RUNSPEC"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"none","size_count":0},"BIOTCOEF":{"name":"BIOTCOEF","sections":["GRID"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"BLOCK_PROBE900":{"name":"BLOCK_PROBE900","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"I","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"J","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"K","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":3,"size_kind":"list"},"CO2STOR":{"name":"CO2STOR","sections":["RUNSPEC"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"none","size_count":0},"CONNECTION_PROBE_OPM":{"name":"CONNECTION_PROBE_OPM","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"I","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"J","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"K","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":4,"size_kind":"list"},"CSTRESS":{"name":"CSTRESS","sections":["GRID"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"FIELD_PROBE_OPM":{"name":"FIELD_PROBE_OPM","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"none","size_count":0},"FRAC":{"name":"FRAC","sections":["RUNSPEC"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"none","size_count":0},"GCOMPIDX":{"name":"GCOMPIDX","sections":["RUNSPEC"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"GAS_COMPONENT_INDEX","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"GEOCHEM":{"name":"GEOCHEM","sections":["RUNSPEC"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"INIT_FILE_NAME","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"MBAL_TOL","description":"","units":{},"default":"1e-07","value_type":"DOUBLE"},{"index":3,"name":"PH_TOL","description":"","units":{},"default":"1e-08","value_type":"DOUBLE"},{"index":4,"name":"ENFORCE_CHARGE_BALANCE","description":"","units":{},"default":"NOCHARGE","value_type":"STRING"},{"index":5,"name":"SPLAY_TREE","description":"","units":{},"default":"0","value_type":"INT"}],"example":"","expected_columns":5,"size_kind":"fixed","size_count":1},"GROUP_PROBE_OPM":{"name":"GROUP_PROBE_OPM","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"GROUPS","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","size_kind":"fixed","size_count":1},"IBLK":{"name":"IBLK","sections":["SOLUTION"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"IONEX":{"name":"IONEX","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"IVDP":{"name":"IVDP","sections":["SOLUTION"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Length","1"]}],"example":"","size_kind":"fixed"},"LAME":{"name":"LAME","sections":["GRID"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"MBLK":{"name":"MBLK","sections":["SOLUTION"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"MECH":{"name":"MECH","sections":["RUNSPEC"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"none","size_count":0},"MECHSOLV":{"name":"MECHSOLV","sections":["RUNSPEC"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"SOLVER","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"COUPLING","description":"","units":{},"default":"LAGGED","value_type":"STRING"},{"index":3,"name":"FIXED_STRESS_MIN_ITER","description":"","units":{},"default":"1","value_type":"INT"},{"index":4,"name":"FIXED_STRESS_MAX_ITER","description":"","units":{},"default":"5","value_type":"INT"}],"example":"","expected_columns":4,"size_kind":"fixed","size_count":1},"MINERAL":{"name":"MINERAL","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"MVDP":{"name":"MVDP","sections":["SOLUTION"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Length","1"]}],"example":"","size_kind":"fixed"},"NETWORK_PROBE":{"name":"NETWORK_PROBE","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"NETWORK_NODES","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","size_kind":"fixed","size_count":1},"OCOMPIDX":{"name":"OCOMPIDX","sections":["RUNSPEC"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"OIL_COMPONENT_INDEX","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"POELCOEF":{"name":"POELCOEF","sections":["GRID"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"PRATIO":{"name":"PRATIO","sections":["GRID"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"REGION_PROBE_OPM":{"name":"REGION_PROBE_OPM","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"RHO":{"name":"RHO","sections":["GRID"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"SBLK":{"name":"SBLK","sections":["SOLUTION"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"SMODULUS":{"name":"SMODULUS","sections":["GRID"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"SPECIES":{"name":"SPECIES","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"STREQUIL":{"name":"STREQUIL","sections":["SOLUTION"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"DATUM_DEPTH","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Length"},{"index":2,"name":"DATUM_POSX","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Length"},{"index":3,"name":"DATUM_POSY","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Length"},{"index":4,"name":"STRESSXX","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":5,"name":"STRESSXXGRAD","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure/Length"},{"index":6,"name":"STRESSYY","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":7,"name":"STRESSYYGRAD","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure/Length"},{"index":8,"name":"STRESSZZ","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":9,"name":"STRESSZZGRAD","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure/Length"},{"index":10,"name":"STRESSXY","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":11,"name":"STRESSXYGRAD","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure/Length"},{"index":10,"name":"STRESSXZ","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":11,"name":"STRESSXZGRAD","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure/Length"},{"index":12,"name":"STRESSYZ","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":13,"name":"STRESSYZGRAD","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure/Length"}],"example":"","expected_columns":15,"size_kind":"list"},"STRESSEQUILNUM":{"name":"STRESSEQUILNUM","sections":["REGIONS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"SVDP":{"name":"SVDP","sections":["SOLUTION"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Length","1"]}],"example":"","size_kind":"fixed"},"THELCOEF":{"name":"THELCOEF","sections":["GRID"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"THERMEXR":{"name":"THERMEXR","sections":["GRID"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"TLPMIXPA":{"name":"TLPMIXPA","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Pressure","1"]}],"example":"","size_kind":"fixed"},"WELL_PROBE_OPM":{"name":"WELL_PROBE_OPM","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"WELLS","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","size_kind":"fixed","size_count":1},"WSEED":{"name":"WSEED","sections":["SCHEDULE"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"I","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"J","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"K","description":"","units":{},"default":"","value_type":"INT"},{"index":5,"name":"NORMAL_X","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":6,"name":"NORMAL_Y","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":7,"name":"NORMAL_Z","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":8,"name":"SIZE_Z","description":"","units":{},"default":"0.3","value_type":"DOUBLE","dimension":"Length"},{"index":9,"name":"SIZE_H","description":"","units":{},"default":"0.3","value_type":"DOUBLE","dimension":"Length"},{"index":10,"name":"WIDTH","description":"","units":{},"default":"0.0001","value_type":"DOUBLE","dimension":"Length"}],"example":"","expected_columns":10,"size_kind":"list"},"WSPECIES":{"name":"WSPECIES","sections":["SCHEDULE"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"SPECIES","description":"","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"CONCENTRATION","description":"","units":{},"default":"","value_type":"UDA"},{"index":4,"name":"CUM_SPECIES_FACTOR","description":"","units":{},"default":"","value_type":"UDA"},{"index":5,"name":"PRODUCTION_GROUP","description":"Defaulted means: use the concentration from the CONCENTRATION item","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":5,"size_kind":"list"},"YMODULE":{"name":"YMODULE","sections":["GRID"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"}} \ No newline at end of file +{"ACTDIMS":{"name":"ACTDIMS","sections":["RUNSPEC"],"supported":null,"summary":"The ACTDIMS keyword defines the maximum number of properties associated with the ACTION keyword. The ACTION keyword allows the user to enter computational logic and calculations to the simulation run based on the how the simulation run is proceeding.","parameters":[{"index":1,"name":"MXACTNS","description":"A positive integer value that defines the maximum number of ACTION keywords defined in the input deck.","units":{},"default":"2","value_type":"INT"},{"index":2,"name":"MXLINES","description":"A positive integer value that defines the maximum number of lines in an ACTION statement.","units":{},"default":"50","value_type":"INT"},{"index":3,"name":"MXCHARS","description":"A positive integer value that defines the maximum characters in an ACTION statement.","units":{},"default":"80","value_type":"INT"},{"index":4,"name":"MXSTATMS","description":"A positive integer value that defines the maximum number of conditional statements in the ACTION statement.","units":{},"default":"3","value_type":"INT"}],"example":"-- ACTION ACTION ACTION ACTION\n-- MXACTNS MXLINES MXCHARS MXSTATMS\nACTDIMS\n2 50 80 3 /\nThe above example defines the default values for the ACTDIMS keyword.","expected_columns":4,"size_kind":"fixed","size_count":1},"ACTPARAM":{"name":"ACTPARAM","sections":["RUNSPEC"],"supported":null,"summary":"The ACTPARAM keyword defines the maximum target percent value for the ACTION series of keywords and the fractional equality tolerance for determining if two numbers are numerically equal when comparing values using the ACTION series of keywords. The ACTION keyword allows the user to enter computational logic and calculations to the simulation run based on the how the simulation run is proceeding.","parameters":[{"index":1,"name":"MXTOLS","description":"A positive real value that defines the maximum target percent number for the ACTION series of keywords. The default value of 100 means the target is not applied.","units":{"field":"percent 100.0","metric":"percent 100.0","laboratory":"percent 100.0"},"default":"Defined"},{"index":2,"name":"MXEQLS","description":"MXEQLS a real positive number greater than zero and less than one that defines the tolerance used to determine if two real values are equal for comparing values in the ACTION series of keywords. Floating-point numbers (as implemented in computers) are never exact, one cannot compare floating point numbers for exact equality. Thus, MXEQLS defines a tolerance. For example, the default value of 1 x 10-4 means that if the difference between two real values is less than 1 x 10-4 then the values are considered equal.","units":{"field":"fraction 1 x 10-4","metric":"fraction 1 x 10-4","laboratory":"fraction 1 x 10-4"},"default":"Defined"}],"example":"--\n-- ACTION ACTION\n-- MXTOLS MXEQLS\nACTPARAM\n5.0 1.0E-4 /\nThe above example defines the maximum tolerance to be 5% and the equality tolerance to be the default value of 1.0 x 10-4.","size_kind":"fixed","size_count":1},"AITS":{"name":"AITS","sections":["RUNSPEC","SCHEDULE"],"supported":false,"summary":"Turns on the commercial simulator’s intelligent time stepping.","parameters":[],"example":"","size_kind":"none","size_count":0},"AITSOFF":{"name":"AITSOFF","sections":["RUNSPEC","SCHEDULE"],"supported":false,"summary":"Turns off the commercial simulator’s intelligent time stepping.","parameters":[],"example":"","size_kind":"none","size_count":0},"ALKALINE":{"name":"ALKALINE","sections":["RUNSPEC"],"supported":false,"summary":"This keyword indicates that an alkaline phase is present in the model and to activate the Alkaline Model in the run. The keyword will also invoke data input file checking to ensure that all the required Alkaline Model input parameters are defined in the input deck.","parameters":[],"example":"--\n-- ALKALINE PHASE IS PRESENT IN THE RUN\n--\nALKALINE\nThe above example declares that the alkaline phase is active in the model to activate Alkaline Model.","size_kind":"none","size_count":0},"API":{"name":"API","sections":["RUNSPEC"],"supported":false,"summary":"This keyword switches on API tracking so that the various “oil types” are tracked in the model.","parameters":[],"example":"--\n-- ACTIVATE THE API TRACKING OPTION\n--\nAPI\nThe above example switches on the API tracking facility.","size_kind":"none","size_count":0},"AQUDIMS":{"name":"AQUDIMS","sections":["RUNSPEC"],"supported":null,"summary":"The AQUDIMS keyword defines the dimensions of the various aquifer property data. The data is normally entered on a single line and is terminated by a “/”.","parameters":[{"index":1,"name":"MXNAQN","description":"A positive integer value that defines the AQUNUM keyword maximum number of lines associated with this keyword, that is the maximum number of numerical aquifers","units":{},"default":"1","value_type":"INT"},{"index":2,"name":"MXNAQC","description":"A positive integer value that defines the AQUCON keyword maximum number of lines of connection data associated with this keyword, that is the maximum number of lines of connection data for numerical aquifers.","units":{},"default":"1","value_type":"INT"},{"index":3,"name":"NIFTBL","description":"A positive integer value that defines the AQUTAB keyword maximum number of Carter-Tracy aquifer tables associated with this keyword.","units":{},"default":"1","value_type":"INT"},{"index":4,"name":"NRIFTB","description":"A positive integer value that defines the AQUTAB keyword maximum number of rows in the Carter-Tracy aquifer tables associated with this keyword. NRIFTB must not be less than 36 in order to accommodate the default infinite acting Carter-Tracy aquifer influence function.","units":{},"default":"36","value_type":"INT"},{"index":5,"name":"NANAQ","description":"A positive integer value that defines the AQUFETP, AQUFLUX and AQUCT maximum number of analytical aquifers defined by these three keywords.","units":{},"default":"1","value_type":"INT"},{"index":6,"name":"NCAMAX","description":"A positive integer value that defines the maximum number of cells connected to an analytical aquifer.","units":{},"default":"1","value_type":"INT"},{"index":7,"name":"MXNALI","description":"A positive integer value that defines the maximum number of aquifer lists.","units":{},"default":"0","value_type":"INT"},{"index":8,"name":"MXAAQL","description":"A positive integer value that defines the maximum number of analytical aquifers in any single aquifer list as defined by (7).","units":{},"default":"0","value_type":"INT"}],"example":"--\n-- AQF AQF AQF AQF AQF AQF AQF AQF\n-- MXAQN MXNAQC NIFTBL NRIFTB NANAQU NCAMAX MXNALI MXAAQL\nAQUDIMS\n1* 1* 1* 1* 1* 1* 1* 1* /\nThe above example defines the default values for the AQUDIMS keyword.","expected_columns":8,"size_kind":"fixed","size_count":1},"AUTOREF":{"name":"AUTOREF","sections":["RUNSPEC"],"supported":false,"summary":"The AUTOREF keyword activates the Auto Refinement option and defines the parameters for this feature.","parameters":[{"index":1,"name":"NX","description":"","units":{},"default":"1","value_type":"INT"},{"index":2,"name":"NY","description":"","units":{},"default":"1","value_type":"INT"},{"index":3,"name":"NZ","description":"","units":{},"default":"1","value_type":"INT"},{"index":4,"name":"OPTION_TRANS_MULT","description":"","units":{},"default":"0","value_type":"DOUBLE"}],"example":"","expected_columns":4,"size_kind":"list"},"BIGMODEL":{"name":"BIGMODEL","sections":["RUNSPEC"],"supported":null,"summary":"The original intention in the commercial simulator was to define an optimized memory allocation method to handle large models; this has since become redundant and has been retired in the commercial simulator.","parameters":[],"example":"","size_kind":"none","size_count":0},"BIOFILM":{"name":"BIOFILM","sections":["RUNSPEC"],"supported":null,"summary":"The BIOFILM keyword activates the biofilm model for the run. Biofilm-related effects in subsurface applications such as hydrogen storage include reduced injectivity and hydrogen loss. The conceptual model includes the following mechanisms: (1) Biofilm is present in the storage site prior to injection and (2) the biofilm consumes injected H2/CO2, leading to clogging effects.","parameters":[],"example":"--\n-- ACTIVATE THE BIOFILM MODEL\n--\nBIOFILM\n--\n-- ACTIVATE THE H2STORE MODEL\n--\nWATER\nGAS\nH2STORE\nThe above example declares that the BIOFILM model is active for the run and activates the H2STORE model. For a complete example of this model, see H2STORE_BIOFILM.DATA.\n| Note This is an OPM Flow specific keyword used to investigate biofilm effects in underground applications. The module requires that either the CO2STORE or H2STORE keywords in the RUNSPEC to be active. |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"none","size_count":0},"BLACKOIL":{"name":"BLACKOIL","sections":["RUNSPEC"],"supported":null,"summary":"This keyword switches on the black-oil formulation, and is equivalent to setting the phases present in the model to be oil, vaporized oil, gas, and dissolved gas. Note if water is present in the model this needs to be explicitly stated via the WATER keyword in the RUNSPEC section (see also the LIVEOIL keywords in the RUNSPEC section). The keyword is used by the commercial simulator’s compositional THERMAL option to set the phases present in the model.","parameters":[],"example":"The following example activates the black-oil phases in the model.\n--\n-- ACTIVATE BLACK-OIL PHASES\n--\nBLACKOIL\nAlternatively one could explicitly declare the phases using the following keywords in the RUNSPEC section.\n--\n-- OIL PHASE IS PRESENT IN THE RUN\n--\nOIL\n--\n-- VAPORIZED OIL IN WET GAS IS PRESENT IN THE RUN\n--\nVAPOIL\n--\n-- GAS PHASE IS PRESENT IN THE RUN\n--\nGAS\n--\n-- DISSOLVED GAS IN LIVE OIL IS PRESENT IN THE RUN\n--\nDISGAS\nThe above example switches on the black-oil phases in the model.","size_kind":"none","size_count":0},"BPARA":{"name":"BPARA","sections":["RUNSPEC"],"supported":false,"summary":"The BPARA keyword activates the block parallel license in the commercial simulator. There is no data required for this keyword; however the keyword should be followed by the PARALLEL keyword in the RUNSPEC section, as illustrated in the example below.","parameters":[],"example":"--\n-- ACTIVATE BLOCK PARALLEL LICENSE\n--\nBPARA\n--\n-- PARALLEL MULTI-CORE OPTIONS\n-- NDMAIN MACHINE TYPE\nPARALLEL\n8 DISTRIBUTED /\nThe above example sets the number of domains (or processors) to eight and for the simulation to run in block parallel mode. This has no effect in OPM Flow input decks.","size_kind":"none","size_count":0},"BPIDIMS":{"name":"BPIDIMS","sections":["RUNSPEC"],"supported":false,"summary":"The BPDIMS keyword defines the dimensions of the interpolated grid block quantities for the BPR_X, BHD_X,BHDF_X, BSCN_X and BCTRA_X, etc. variables declared in the SUMMARY section.","parameters":[{"index":1,"name":"MXNBIP","description":"","units":{},"default":"10","value_type":"INT"},{"index":2,"name":"MXNLBI","description":"","units":{},"default":"1","value_type":"INT"}],"example":"","expected_columns":2,"size_kind":"fixed","size_count":1},"BRINE":{"name":"BRINE","sections":["RUNSPEC"],"supported":false,"summary":"The BRINE keyword activates the standard Brine Tracking model and optionally defines the water phase to have various salinities if the ECLMC keyword in the RUNSPEC section has been used to activate the Multi-Component Brine model, that allows for the water phase to have multiple water salinities. Note that the Multi-Component Brine model is not supported by OPM Flow.","parameters":[{"index":1,"name":"SALTS","description":"An optional character vector string that defines the salts to be tracked for when the Multi-Component Brine model has been activated by the ECLMC keyword in the RUNSPEC section. SALTS should be set to one or more of the following salt chemical formulae:","units":{},"default":"None","value_type":"STRING"}],"example":"The first example actives the standard Brine model and has no terminating “/”.\n--\n-- ACTIVATE STANDARD BRINE MODEL IN THE RUN\n--\nBRINE\nThe second example illustrates how to activate OPM Flow’s Salt Precipitation model.\n--\n-- ACTIVATE STANDARD BRINE MODEL IN THE RUN\n--\nBRINE\n--\n-- ACTIVATE THE OPM FLOW SALT PRECIPITATION MODEL (OPM FLOW KEYWORD)\n--\nPRECSALT\n--\n-- VAPORIZED WATER IN DRY/WET GAS IS PRESENT IN THE RUN (OPM FLOW KEYWORD)\n--\nVAPWAT\nThe third and final example activates the Multi-Component brine model with four different salts.\n--\n-- ACTIVATE MULTI-COMPONENT BRINE MODEL\n--\nECLMC\n--\n-- DEFINE WATER PHASE MULTI-COMPONENT BRINE COMPONENTS\n--\n-- SALT1 SALT2 SALT3 SALT4 SALT5\nBRINE\nNACL CACL2 MGC03 K2CO3 /\nThis option is currently not available in OPM Flow.","size_kind":"fixed","size_count":1,"variadic_record":true},"CART":{"name":"CART","sections":["RUNSPEC"],"supported":false,"summary":"CART activates the Cartesian grid geometry for the main model, as oppose to a radial geometry. This is the default geometry and therefore the keyword does have to be used to activate this type of geometry.","parameters":[],"example":"","size_kind":"none","size_count":0},"CBMOPTS":{"name":"CBMOPTS","sections":["SRUNSPEC"],"supported":false,"summary":"This keyword sets the options for the Coal Bed Methane model which is activated via the COAL keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"ADSORPTION_MODEL","description":"","units":{},"default":"TIMEDEP","value_type":"STRING"},{"index":2,"name":"ALLOW_WATER_FLOW","description":"","units":{},"default":"YES","value_type":"STRING"},{"index":3,"name":"ALLOW_PERMEAB","description":"","units":{},"default":"NOKRMIX","value_type":"STRING"},{"index":4,"name":"COUNT_PASSES","description":"","units":{},"default":"NOPMREB","value_type":"STRING"},{"index":5,"name":"METHOD","description":"","units":{},"default":"PMSTD","value_type":"STRING"},{"index":6,"name":"SCALING_VALUE","description":"","units":{},"default":"PMSCAL","value_type":"STRING"},{"index":7,"name":"APPLICATION","description":"","units":{},"default":"PMPVK","value_type":"STRING"},{"index":8,"name":"PRESSURE_CHOP","description":"","units":{},"default":"NOPMPCHP","value_type":"STRING"},{"index":9,"name":"MIN_PORE_VOLUME","description":"","units":{},"default":"5e-06","value_type":"DOUBLE"}],"example":"","expected_columns":9,"size_kind":"fixed","size_count":1},"CO2SOL":{"name":"CO2SOL","sections":["RUNSPEC"],"supported":null,"summary":"The CO2SOL keyword activates dissolved carbon dioxide (CO2) in the water phase, where CO2 is represented by the SOLVENT pseudo component, using the simulator’s CO2-Brine PVT model. This keyword is a compositional keyword in the commercial simulator but has been implemented in OPM Flow’s black-oil model.","parameters":[],"example":"The example shows the usage of CO2SOL to model CO2 injection in a live-oil reservoir. The RUNSPEC section includes the CO2SOL keyword, which activates dissolved carbon dioxide (CO2) in the water phase. The SOLVENT keyword activates the solvent pseudo component, which represents CO2. The DISGASW keyword has been used to activate dissolved CO2 in the brine.\n-- ==============================================================================\n--\n-- RUNSPEC SECTION\n--\n-- ==============================================================================\nRUNSPEC\n-- ------------------------------------------------------------------------------\n-- FLUID TYPES AND TRACER OPTIONS\n-- ------------------------------------------------------------------------------\n--\n-- ACTIVATE DISSOLVED CO2 IN WATER (OPM FLOW KEYWORD)\n--\nCO2SOL\n--\n-- SOLVENT PHASE IS PRESENT IN THE RUN\n--\nSOLVENT\n--\n-- DISSOLVED CO2 IN WATER IS PRESENT IN THE RUN (OPM FLOW KEYWORD)\n--\nDISGASW\nThe second part of the example covers the additional data required in the PROPS section, in which the CO2-gas miscible relative permeabilities are defined using the SSFN keyword. The initial temperature and salinity are defined using the RTEMP and SALINITY keywords. The oil and gas PVT properties should be defined in the normal way. No water PVT data is required.\n-- ==============================================================================\n--\n-- PROPS SECTION\n--\n-- ==============================================================================\nPROPS\n--\n-- RESERVOIR\n-- TEMPERATURE\n-- -----------\nRTEMP\n80.0 / RESERVOIR TEMP\n--\n-- SET SALINITY FOR ALL CELLS (OPM FLOW KEYWORD)\n--\nSALINITY\n0.7 /\n--\n-- SOLVENT RELATIVE PERMEABILITY TABLES\n--\nSSFN\n-- SGAS KRGT KRST\n-- FRAC\n-- -------- -------- --------\n0.0000 0.0000 0.0000\n1.0000 1.0000 1.0000 /\nThe third part of the example covers initialising the model in the SOLUTION section. Here the EQUIL keyword is used as normal to equilibrate the oil, gas and water phases, and the SSOL keyword to specify that there is initially no CO2 present in the gas phase.\n-- ==============================================================================\n--\n-- SOLUTION SECTION\n--\n-- ==============================================================================\nSOLUTION\n--\n-- DATUM DATUM OWC PCOW GOC PCGO RS RV N E300 RVW\n-- DEPTH PRESS DEPTH ---- DEPTH ---- OPT OPT OPT OPT OPT\nEQUIL\n2000.0 200.0 1900.0 0.00 2000.0 0.00 1* 1* 1* 2* 1* /\n--\n-- DEFINE INITIAL EQUILIBRATION SOLVENT SAT VALUES FOR ALL CELLS IN THE MODEL\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nSSOL\n30000*0.0 /\nFor the summary section, the CO2 storage quantity can be tracked using the solvent injection and production volumes as shown below.\n-- ==============================================================================\n--\n-- SUMMARY SECTION\n--\n-- ==============================================================================\nSUMMARY\n--\n-- EXPORT STANDARD SUMMARY VARIABLE VECTORS TO FILE\n--\nALL\n--\n-- FIELD SOLVENT INJECTION RATE\nFNIR\n--\n-- FIELD SOLVENT PRODUCTION RATE\nFNPR\n--\n-- FIELD SOLVENT INJECTION TOTAL\nFNIT\n--\n-- FIELD SOLVENT PRODUCTION TOTAL\nFNPT\nThe final part of the example covers the SCHEDULE section. The WSOLVENT keyword is used to specify the injected solvent fraction (in this case pure CO2).\n-- ==============================================================================\n--\n-- SCHEDULE SECTION\n--\n-- ==============================================================================\nSCHEDULE\n--\n-- RESTART CONTROL BASIC = 1 (LAST REPORT TIME ONLY)\n--\nRPTRST\n'BASIC=1' 'ALLPROPS' /\n--\n-- DEFINE GAS INJECTION WELL SOLVENT FRACTION\n--\n-- WELL SOLVENT\n-- NAME FRACTION\n-- --------\nWSOLVENT\nGI01 1.0000 /\n/","size_kind":"none","size_count":0},"CO2STORE":{"name":"CO2STORE","sections":["RUNSPEC"],"supported":false,"summary":"The CO2STORE keyword activates the carbon dioxide (CO2) storage model for the run to account for both carbon dioxide and water phase solubility, via the simulator’s CO2-Brine PVT model. This keyword is a compositional keyword in the commercial simulator but has been implemented in OPM Flow’s black-oil model.","parameters":[],"example":"The first example shows the standard usage of CO2STORE with Option (1) the Gas-Water model (GASWAT). Here we also activate the dissolved gas in water (DISGASW) and vaporized water in gas (VAPWAT) options in the RUNSPEC section.\n-- ==============================================================================\n--\n-- RUNSPEC SECTION\n--\n-- ==============================================================================\nRUNSPEC\n-- ------------------------------------------------------------------------------\n-- FLUID TYPES AND TRACER OPTIONS\n-- ------------------------------------------------------------------------------\n--\n-- ACTIVATE CO2 STORAGE IN THE MODEL (OPM FLOW CO2 STORAGE KEYWORD)\n--\nCO2STORE\n--\n-- ACTIVATE GAS-WATER THE MODEL (OPM FLOW KEYWORD)\n--\nGASWAT\n--\n-- DISSOLVED GAS IN WATER IS PRESENT IN THE RUN (OPM FLOW KEYWORD)\n--\nDISGASW\n--\n-- VAPORIZED WATER IN DRY/WET GAS IS PRESENT IN THE RUN (OPM FLOW KEYWORD)\n--\nVAPWAT\nThe second part of the example covers the data required for the PROPS section, in which the two-phase relative permeability functions are set using GSF and WSF keywords.\n-- ==============================================================================\n--\n-- PROPS SECTION\n--\n-- ==============================================================================\nPROPS\n--\n-- RESERVOIR\n-- TEMPERATURE\n-- -----------\nRTEMP\n80.0 / RESERVOIR TEMP\n--\n-- ROCK COMPRESSIBILITY\n--\n-- REFERENCE PRESSURE IS TAKEN FROM THE HCPV WEIGHTED RESERVOIR PRESSURE\n--\n-- REF PRES CF\n-- BARSA 1/BARSA\n-- -------- --------\nROCK\n200.0 5.0E-05 / ROCK COMPRESSIBILITY\n--\n-- GAS RELATIVE PERMEABILITY TABLES (OPM FLOW KEYWORD)\n--\nGSF\n-- SGAS KRG PCGW\n-- FRAC PSIA\n-- -------- -------- -------\n0.000 0.000 0.0\n0.080 0.001 0.0\n0.170 0.010 0.0\n0.350 0.050 0.0\n0.530 0.200 0.0\n0.620 0.350 0.0\n0.650 0.390 0.0\n0.710 0.560 0.0\n0.800 1.000 0.0 / TABLE NO. 01\n--\n-- WATER RELATIVE PERMEABILITY TABLES (OPM FLOW KEYWORD)\n--\nWSF\n-- SWAT KRW\n-- FRAC\n-- -------- --------\n0.200 0.0000\n0.400 0.1000\n0.800 0.5000\n1.000 1.0000 / TABLE NO. 01\n--\n-- SET SALINITY FOR ALL CELLS (OPM FLOW KEYWORD)\n--\nSALINITY\n0.7 /\nNo other data is required to define the fluid and rock properties in the PROPS section as the data is generated from internal analytic correlations and models by the simulator. Finally, note that units for salinity are to the 10-3, thus for metric units we have 10-3 x kg-M/kg.\nThe third part of the example covers initializing the model in the SOLUTION section. Here we set the EQUIL(EQLOPT6) parameter equal to one, to use table number one of the RVWVD keyword, in order to set the vaporized water versus depth distribution for the model.\n-- ==============================================================================\n--\n-- SOLUTION SECTION\n--\n-- ==============================================================================\nSOLUTION\n--\n-- SYSTEM IS SATURATED WITH WATER\n--\n-- DATUM DATUM OWC PCOW GOC PCGO RS RV N E300 RVW\n-- DEPTH PRESS DEPTH ---- DEPTH ---- OPT OPT OPT OPT OPT\nEQUIL\n2000.0 200.0 1800.0 0.00 1800.0 0.00 1* 1* 1* 2* 1 /\n--\n-- WATER VAPOR RATIO VS DEPTH (OPM FLOW KEYWORD)\n--\n-- DEPTH RVW\n-- STB/MSCF\n-- ------ --------\nRVWVD\n1000.0 0.000\n3000.0 0.000 / RVW VS DEPTH EQUIL REGN 01\nIn the SUMMARY section, the simulator supports summary vectors specific to CO2 storage (see Section 11.1.12 Option Specific Variables - CO2STORE/H2STORE Model) including those shown below.\n-- ==============================================================================\n--\n-- SUMMARY SECTION\n--\n-- ==============================================================================\nSUMMARY\n--\n-- EXPORT STANDARD SUMMARY VARIABLE VECTORS TO FILE\n--\nALL\n--\n-- FIELD CO2 DISOLVED IN WATER PHASE\nFWCD\n--\n-- FIELD CO2 TRAPPED IN GAS PHASE\nFGCDI\n--\n-- FIELD CO2 MOBILE IN GAS PHASE\nFGCDM\nThe final part of the example covers the SCHEDULE section. The standard WCONINJE keyword is used to set the gas injection rate, in this case 100,000 sm3/day of CO2.\n-- ===========================================","size_kind":"none","size_count":0},"COAL":{"name":"COAL","sections":["RUNSPEC"],"supported":false,"summary":"The COAL keyword actives the coal phase and the Coal Bed Methane (“CBM”) model for the run.","parameters":[],"example":"--\n-- ACTIVATE THE COAL PHASE (CBM MODEL) IN THE MODEL\n--\nCOAL\nThe above example declares that the Coal phase is active in the run and activates the CBM model option.","size_kind":"none","size_count":0},"COLUMNS":{"name":"COLUMNS","sections":["RUNSPEC","GRID","EDIT","PROPS","REGIONS","SOLUTION","SUMMARY","SCHEDULE"],"supported":null,"summary":"The COLUMNS keyword defines the input file column margins; characters outside the margins are ignored by the input parser.","parameters":[{"index":1,"name":"LEFT_MARGIN","description":"","units":{},"default":"1","value_type":"INT"},{"index":2,"name":"RIGHT_MARGIN","description":"","units":{},"default":"132","value_type":"INT"}],"example":"","expected_columns":2,"size_kind":"fixed","size_count":1},"COMPS":{"name":"COMPS","sections":["RUNSPEC"],"supported":true,"summary":"The COMPS keyword activates the Compositional Modeling Formulation, and declares the number of components active in the model.","parameters":[{"index":1,"name":"COMPS","description":"A positive integer defining the number of compositional components active in the model. Only the default value of two is currently supported by OPM Flow.","units":{},"default":"2","value_type":"INT"}],"example":"The following example shows how to request a two component compositional modeling formulation to be used with the CO2STORE and GASWAT options.\n-- ==============================================================================\n--\n-- RUNSPEC SECTION\n--\n-- ==============================================================================\nRUNSPEC\n--\n-- ACTIVATE CO2 STORAGE IN THE MODEL (OPM FLOW CO2 STORAGE KEYWORD)\n--\nCO2STORE\n--\n-- ACTIVATE COMPOSITIONAL MODELING FORMULATION (OPM FLOW KEYWORD)\n--\nCOMPS\n2 /\n--\n-- ACTIVATE GAS-WATER THE MODEL (OPM FLOW KEYWORD)\n--\nGASWAT\n| Note This keyword is only supported by OPM Flow when the two component gas-water CO2 storage model has been activated using the CO2STORE keyword and either the GASWAT or the GAS and WATER keywords in the RUNSPEC section. Secondly, although OPM Flow parses the keyword, the simulator currently ignores the data for this keyword. |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":1,"size_kind":"fixed","size_count":1},"CPR":{"name":"CPR","sections":["RUNSPEC","SUMMARY"],"supported":null,"summary":"Turns on the Constrained Pressure Residual (“CPR”)66\n Wallis, J. R., Little, T. E., and Nolen, J. S.: \"Constrained Residual Acceleration of Conjugate Residual Methods,\" paper SPE 13536 presented at the SPE Reservoir Simulation Symposium, Dallas, Texas, USA (February 10-13, 1985)., 67\n R. Scheichl, M. Roland, J. Wendebourg, Decoupling and block preconditioning for sedimentary basin simulations, Computational Geosciences 7 (2003) 295{318.and 68\n Klemetsdal, Ø.S., Møyner, O. & Lie, KA. Accelerating multiscale simulation of complex geomodels by use of dynamically adapted basis functions. Comput Geosci 24, 459–476 (2020). https://doi.org/10.1007/s10596-019-9827-z.preconditioner linear solver option, and declares how the solver should be applied. The keyword is equivalent to using the OPM Flow command line parameter --linear-solver= “cprw”. Note that if the command line has been used, then this will take precedence over the CPR keyword.","parameters":[{"index":1,"name":"CPROPTN","description":"A defined character string that determines how the CPR linear solver should be applied, and should be set to one of the following: ORIGINAL: Here the solver is applied for the whole of the simulation. ADAPTIVE: This option applies the more computational demanding CPR linear solver, only in parts of the run that would benefit from its use, for example when linear convergence is challenging. Note that OPM Flow only supports the ORIGINAL option, which is the default value in OPM Flow, whereas the default value in the commercial simulator is ADAPTIVE. .","units":{},"default":"ORIGINAL","value_type":"STRING"},{"index":2,"name":"I","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"J","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"K","description":"","units":{},"default":"","value_type":"INT"}],"example":"--\n-- ACTIVATE CONSTRAINED PRESSURE RESIDUAL LINEAR SOLVER FOR THE RUN\n--\nCPR\n/\nThe above example activates the Constrained Pressure Residual preconditioner linear solver using the default option, that is the ORIGINAL option for OPM Flow.\nTo enable the CPR preconditioner linear solver option using the command line parameter, use:\nflow --linear-solver=\"cpr\" CASENAME.DATA\nwhich should usually be combined with the -matrix-add-well-contributions=true option, that is:\nflow --linear-solver=cpr --matrix-add-well-contributions=true CASENAME.DATA\nHowever, the new CPRW preconditioner, that includes wells does not need the latter option, so in this instance use:\nflow --linear-solver=cprw CASENAME.DATA\nAs of this release the CPRW preconditioner, should be considered experimental, and the recommended configuration for running this is:\nflow --linear-solver=cprw --linear-solver-reduction=0.005 --cpr-reuse-setup=4\n--cpr-reuse-interval=10 CASENAME.DATA\nSee new Rasmussen et al.69\n Atgeirr Flø Rasmussen, Tor Harald Sandve, Kai Bao, Andreas Lauser, Joakim Hove, Bård Skaflestad, Robert Klöfkorn, Markus Blatt, Alf Birger Rustad, Ove Sævareid, Knut-Andreas Lie, Andreas Thune, The Open Porous Media Flow reservoir simulator, Computers & Mathematics with Applications, Volume 81, 2021, Pages 159-185, ISSN 0898-1221, https://doi.org/10.1016/j.camwa.2020.05.014. (https://www.sciencedirect.com/science/article/pii/S0898122120302182). for further information on the available numerical algorithms available in OPM Flow.\nAtgeirr Flø Rasmussen, Tor Harald Sandve, Kai Bao, Andreas Lauser, Joakim Hove, Bård Skaflestad, Robert Klöfkorn, Markus Blatt, Alf Birger Rustad, Ove Sævareid, Knut-Andreas Lie, Andreas Thune, The Open Porous Media Flow reservoir simulator, Computers & Mathematics with Applications, Volume 81, 2021, Pages 159-185, ISSN 0898-1221, https://doi.org/10.1016/j.camwa.2020.05.014. (https://www.sciencedirect.com/science/article/pii/S0898122120302182).","expected_columns":4,"size_kind":"list"},"DEBUG":{"name":"DEBUG","sections":["RUNSPEC","GRID","EDIT","PROPS","REGIONS","SOLUTION","SUMMARY","SCHEDULE"],"supported":false,"summary":"This keyword defines the debug data to be written to the debug file (*.DBG). This keyword is not supported by OPM Flow but has no effect on the results so it will be ignored.","parameters":[],"example":""},"DIFFUSE":{"name":"DIFFUSE","sections":["RUNSPEC"],"supported":null,"summary":"The DIFFUSE keyword activates OPM Flow’s Molecular Diffusion option based on fluid and grid data (Sandve et al.70\n Tor Harald Sandve1, Sarah E. Gasda, Atgeirr Rasmussen, and Alf Birger Rustad. Convective dissolution in field scale CO2 storage simulation using the OPM Flow simulator. Submitted to TCCS 11 – Trondheim Conference on CO2 Capture, Transport and Storage Trondheim, Norway – June 21-23, 2021.), similar to the commercial simulator. For field-scale simulations diffusion is a sub-grid phenomenon and is typically not explicitly represented in the flow equations. However, for simulations on the laboratory scale diffusion plays a direct role and therefore needs to be explicitly represented in the flow equations. Diffusion coefficients that control the diffusion depend on temperature, pressure, and salinity. In OPM Flow, the diffusion coefficients are computed internally for pure water using McLachlan and Danckwerts71\n McLachlan, C. N. S., & Danckwerts, P. V. (1972). Des...","parameters":[],"example":"--\n-- ACTIVATE MOLECULAR DIFFUSION OPTION\n--\nDIFFUSE\nThe above example switches on the molecular diffusion facility.\n| Note The option has been tested in combination with the CO2STORE keyword, but not for the general case at this point. |\n|-----------------------------------------------------------------------------------------------------------------------|","size_kind":"none","size_count":0},"DIMENS":{"name":"DIMENS","sections":["RUNSPEC"],"supported":null,"summary":"DIMENS defines the dimensions of the model entered as integer vector. The keyword can be used with all grid types.","parameters":[{"index":1,"name":"NX","description":"A positive integer value that defines the number of grid blocks in the x direction for Cartesian grids or the number of grid blocks in the r direction for radial grids","units":{},"default":"None","value_type":"INT"},{"index":2,"name":"NY","description":"A positive integer value that defines the number of grid blocks in the y direction for Cartesian grids or the number of grid blocks in the theta direction for radial grids.","units":{},"default":"None","value_type":"INT"},{"index":3,"name":"NZ","description":"A positive integer value that defines the number of grid blocks in the z direction for both Cartesian and radial grids.","units":{},"default":"None","value_type":"INT"}],"example":"--\n-- MAX MAX MAX\n-- NDIVIX NDIVIY NDIVIZ\nDIMENS\n46 112 22 /\nThe above example defines the dimensions for the Norne model of 46 cells in the x direction, 112 cells in the y direction and 22 cells in the z direction.","expected_columns":3,"size_kind":"fixed","size_count":1},"DISGAS":{"name":"DISGAS","sections":["RUNSPEC"],"supported":null,"summary":"This keyword indicates that dissolved gas is present in live74\n “Live” oil is oil that contains gas in solution, which is normally the case for most conventional oil reservoirs. However, for oil reservoirs classified as heavy oil reservoirs, the in situ dissolved gas may be negligible and oil would then be classified as gas-free oil which is commonly referred to as “dead” oil. oil in the model and the keyword should only be used if the there is both oil and gas phases in the model. The keyword may be used for oil-water and oil-water-gas input decks that contain the oil and gas phases. The keyword will also invoke data input file checking to ensure that all the required oil and gas phase input parameters are defined in the input deck.","parameters":[],"example":"--\n-- DISSOLVED GAS IN LIVE OIL IS PRESENT IN THE RUN\n--\nDISGAS\nThe above example declares that the dissolved gas in the oil phase is active in the model.","size_kind":"none","size_count":0},"DISGASW":{"name":"DISGASW","sections":["RUNSPEC"],"supported":null,"summary":"This keyword indicates that dissolved gas is present in the water phase in the model. The keyword may only be used for gas-water input decks that contain just the gas and the water phases, which must also be declared. The keyword will also invoke data input file checking to ensure that all the required gas and water phase input parameters are defined in the input deck.","parameters":[],"example":"--\n-- GAS PHASE IS PRESENT IN THE RUN\n--\nGAS\n--\n-- WATER PHASE IS PRESENT IN THE RUN\n--\nWATER\n--\n-- DISSOLVED GAS IN WATER IS PRESENT IN THE RUN (OPM FLOW KEYWORD)\n--\nDISGASW\n--\n-- ACTIVATE CO2 STORAGE IN THE MODEL (OPM FLOW CO2 STORAGE KEYWORD)\n--\nCO2STORE\nThe above example declares that the gas and water phases are present, and that the dissolved gas in the water phase is also active in the model, for modeling CO2 storage.\n| Note This is an OPM Flow specific keyword for the simulator’s Dissolved Gas in Water Model that is activated by declaring that this phase is present in the run. |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"none","size_count":0},"DISPDIMS":{"name":"DISPDIMS","sections":["RUNSPEC"],"supported":false,"summary":"The DISPDIMS key defines the maximum number of dispersion tables, and the maximum number of velocity and concentration elements per table.","parameters":[{"index":1,"name":"NUM_DISP_TABLES","description":"","units":{},"default":"1","value_type":"INT"},{"index":2,"name":"MAX_VELOCITY_NODES","description":"","units":{},"default":"2","value_type":"INT"},{"index":3,"name":"MAX_CONCENTRATION_NODES","description":"","units":{},"default":"1","value_type":"INT"}],"example":"","expected_columns":3,"size_kind":"fixed","size_count":1},"DUALPERM":{"name":"DUALPERM","sections":["RUNSPEC"],"supported":false,"summary":"The DUALPERM keyword activates the Dual Permeability option and the Dual Porosity option for the run. In a dual porosity system flow occurs between the matrix and the fracture only, whereas in a dual permeability system flow also occurs between the matrix grid blocks76\n Warren, J.E. and Root, P.J. 1963. The Behavior of Naturally Fractured Reservoirs. SPE J. 3 (3): 245–255. SPE-426-PA. http://dx.doi.org/10.2118/426-PA., 77\n Gringarten, A.C. 1984. Interpretation of Tests in Fissured and Multilayered Reservoirs With Double-Porosity Behavior: Theory and Practice. J Pet Technol 36 (4): 549-564. SPE-10044-PA. http://dx.doi.org/10.2118/10044-PA., 78\n Serra, K., Reynolds, A.C., and Raghavan, R. 1983. New Pressure Transient Analysis Methods for Naturally Fractured Reservoirs(includes associated papers 12940 and 13014 ). J Pet Technol 35 (12): 2271-2283. SPE-10780-PA. http://dx.doi.org/10.2118/10780-PA, 79\n Barenblatt, G.E., Zheltov, I.P., and Kochina, I.N. 1960. Basi...","parameters":[],"example":"--\n-- ACTIVATE DUAL PERMEABILITY MODEL\n--\nDUALPERM\nThe above example declares that the Dual Permeability option is active for the run.","size_kind":"none","size_count":0},"DUALPORO":{"name":"DUALPORO","sections":["RUNSPEC"],"supported":false,"summary":"The DUALPORO keyword activates the Dual Porosity option for the run. In a dual porosity system flow occurs between the matrix and the fracture only, whereas in a dual permeability system flow also occurs between the matrix grid blocks81\n Warren, J.E. and Root, P.J. 1963. The Behavior of Naturally Fractured Reservoirs. SPE J. 3 (3): 245–255. SPE-426-PA. http://dx.doi.org/10.2118/426-PA., 82\n Gringarten, A.C. 1984. Interpretation of Tests in Fissured and Multilayered Reservoirs With Double-Porosity Behavior: Theory and Practice. J Pet Technol 36 (4): 549-564. SPE-10044-PA. http://dx.doi.org/10.2118/10044-PA., 83\n Serra, K., Reynolds, A.C., and Raghavan, R. 1983. New Pressure Transient Analysis Methods for Naturally Fractured Reservoirs(includes associated papers 12940 and 13014 ). J Pet Technol 35 (12): 2271-2283. SPE-10780-PA. http://dx.doi.org/10.2118/10780-PA, 84\n Barenblatt, G.E., Zheltov, I.P., and Kochina, I.N. 1960. Basic Concepts in the Theory of Homog...","parameters":[],"example":"--\n-- ACTIVATE DUAL POROSITY MODEL\n--\nDUALPORO\nThe above example declares that the Dual Porosity option is active for the run.","size_kind":"none","size_count":0},"DYNRDIMS":{"name":"DYNRDIMS","sections":["RUNSPEC"],"supported":false,"summary":"The DYNRDIMS keyword defines the dimensions for the parameters used by the Dynamic Regions facility, including the maximum number of dynamic regions. The Dynamic Regions facility allows for property and reporting regions to vary as the run progresses, based on the parameters and logic defined by the DYNAMICR keyword in the SOLUTION and PROPS section.","parameters":[{"index":1,"name":"MNUMDR","description":"","units":{},"default":"0","value_type":"INT"},{"index":2,"name":"MXDYNF","description":"","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"MXDYNR","description":"","units":{},"default":"0","value_type":"INT"}],"example":"","expected_columns":3,"size_kind":"fixed","size_count":1},"ECHO":{"name":"ECHO","sections":["RUNSPEC","GRID","EDIT","PROPS","REGIONS","SOLUTION","SUMMARY","SCHEDULE"],"supported":null,"summary":"Turns on echoing of all the input files to the print file; note that this keyword is activated by default and can subsequently be switched off by the NOECHO activation keyword.","parameters":[],"example":"","size_kind":"none","size_count":0},"ECLMC":{"name":"ECLMC","sections":["RUNSPEC"],"supported":false,"summary":"The ECLMC keyword activates the Multi-Component Brine model that allows for the water phase to have multiple water salinities. The keyword should be used in conjunction with the BRINE keyword in the RUNSPEC. Both keywords must be specified to activate the Multi-Component Brine model, whereas the BRINE keyword only is required to activate the standard brine tracking model.","parameters":[],"example":"The first example activates the standard Brine Tracking model.\n--\n-- ACTIVATE STANDARD BRINE MODEL\n--\nBRINE\nThe next example shows the ECLMC and BRINE keywords for when the Multi-Component Brine model is required.\n--\n-- ACTIVATE MULTI-COMPONENT BRINE MODEL\n--\nECLMC\n--\n-- DEFINE WATER PHASE MULTI-COMPONENT BRINE COMPONENTS\n--\n-- SALT1 SALT2 SALT3 SALT4 SALT5\nBRINE\nNACL CACL2 MGC03 /\nThe above example activates the Multi-Component Brine model with three different water salinities.","size_kind":"none","size_count":0},"END":{"name":"END","sections":["RUNSPEC","GRID","EDIT","PROPS","REGIONS","SOLUTION","SUMMARY","SCHEDULE"],"supported":null,"summary":"This keyword marks the end of the input file and can occur in any section. Any keywords and data after the END keyword are ignored.","parameters":[],"example":"","size_kind":"none","size_count":0},"ENDINC":{"name":"ENDINC","sections":["RUNSPEC","GRID","EDIT","PROPS","REGIONS","SOLUTION","SUMMARY","SCHEDULE"],"supported":null,"summary":"This keyword marks the end of an include file specified on the INCLUDE keyword. When the ENDINC keyword is encountered in the INCLUDE file, input data is read from the next keyword in the current file. Any keywords and data after the ENDINC keyword in the INCLUDE file are ignored.","parameters":[],"example":"","size_kind":"none","size_count":0},"ENDSCALE":{"name":"ENDSCALE","sections":["RUNSPEC"],"supported":true,"summary":"The ENDSCALE keyword activates OPM Flow’s relative permeability end-point scaling option. The relative permeability functions are defined using the either the:","parameters":[{"index":1,"name":"DIRECT","description":"A character string that activates or deactivates directional end-point scaling option. If DIRECT is set to NODIR then directional end-point scaling is switched off and the same saturation function is used in the x, y and z directions (unless activated otherwise by the SATOPTS keyword in the RUNSPEC section). In this case the SWL, SWCR, SWU, SGL, SGCR, SGU, SOWCR and SOGCR saturation grid arrays and the KRG, KRORG, KRORW and KRW relative permeability grid cell arrays should be used to enter the grid block end-point data. If DIRECT is set to DIRECT then directional end-point scaling is switched on and different saturation functions are used in the x, y and z directions (unless activated otherwise by the SATOPTS keyword in the RUNSPEC section). Here the directional form of the SWL, SWCR, SWU, SGL, SGCR, SGU, SOWCR and SOGCR saturation grid arrays and the KRG, KRORG, KRORW and KRW relative permeability grid cell arrays should be use to enter the grid block end-point data. For example SWLX, SWLY and SWLZ for SWL. Only the default option is supported by OPM Flow.","units":{},"default":"NODIR","value_type":"STRING"},{"index":2,"name":"IRREVERS","description":"A character string that activates or deactivates non-reversible end-point scaling option. If IRREVERS is set to REVERS then the end-point scaling is set to reversible and results in the same set of end-point arrays being used for flow from the xI to xI + 1 direction as for the flow from the xI to the xI – 1 for all directions (x, y and z). Here the SWLX, SWLY and SWLZ series of keywords should be used instead of SWL type of keywords. Alternatively, if IRREVERS is set to IRREVERS then the end-point scaling is set to non-reversible and results in different sets of end-point arrays being applied for flow from the xI to xI + 1 direction and the xI to the xI – 1 direction, for all directions (x, y, z). in this case the SWLX+, SWLX-, SWLY+, SWLY- SWLZ+ and SWLZ- series of keywords should be utilized instead of SWL or the SWLX, SWLY and SWLZ set of keywords. Only the default option is supported by OPM Flow.","units":{},"default":"REVERS","value_type":"STRING"},{"index":3,"name":"NTENDP","description":"A positive integer that defines the maximum number of saturation end-point depth tables. The end-point depth tables are used to re-scale the saturation tables as a function of depth as opposed to being a grid block property. NTENDP may also be specified on the TABDIMS keyword, and if specified on both here and on the TABDIMS keyword the maximum value of the two is used. Only the default option is supported by OPM Flow.","units":{},"default":"1","value_type":"INT"},{"index":4,"name":"NNODES","description":"A positive integer the defines the maximum number entries for saturation end-point depth tables.","units":{},"default":"20","value_type":"INT"},{"index":5,"name":"MODE","description":"A positive integer that activates the options for temperature dependent saturation end-point scaling in the commercial compositional simulator. MODE should be defaulted with either 1* or zero, which means that scaling can only be performed by grid block end-point scaling properties or via saturation end-point depth tables.","units":{},"default":"0","value_type":"INT"}],"example":"-- DIRC REVERSE MAX MAX\n-- SCALE SCALE TABLES NODES\nENDSCALE\nNODIR REVERS 1* 1* /\nThe above example invokes the end-point scaling option with end-point scaling being non-directional and reversible with the default number of saturation end-point depth tables (one) with 20 entries per table.","expected_columns":5,"size_kind":"fixed","size_count":1},"ENDSKIP":{"name":"ENDSKIP","sections":["RUNSPEC","GRID","EDIT","PROPS","REGIONS","SOLUTION","SUMMARY","SCHEDULE"],"supported":null,"summary":"The ENDSKIP keyword deactivates the skipping of keywords that was activated by the SKIP, SKIP100, or SKIP300 keywords. Each SKIP keyword should be paired with an ENDSKIP keyword.","parameters":[],"example":"","size_kind":"none","size_count":0},"EOS":{"name":"EOS","sections":["RUNSPEC","PROPS"],"supported":null,"summary":"The EOS keyword specifies the Equation Of State (EOS) to be used for each EOS region. The keyword should only be used if the compositional mode has been requested using the COMPS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"EQUATION","description":"","units":{},"default":"PR","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"fixed"},"EQLDIMS":{"name":"EQLDIMS","sections":["RUNSPEC"],"supported":null,"summary":"The EQLDIMS keyword defines the maximum number of properties associated with equilibrating the model, that is initializing the model. A reservoir grid can be separated into separate regions in order to apply different pressure regimes and/or fluid contacts. Care should be taken that the different regions are not in communication if the pressures or fluid contacts are different for the various regions, as this would lead to an unstable initialization and would also imply errors in the model description as implemented.","parameters":[{"index":1,"name":"NTEQUL","description":"A positive integer value that defines the number of equilibration regions entered using the EQLNUM keyword in the REGIONS section and the number of entries associated with the EQUIL keyword in the SOLUTION section.","units":{},"default":"1","value_type":"INT"},{"index":2,"name":"NPRSVD","description":"A positive integer value setting the number of pressure versus depth entries used by OPM Flow in determining equilibration parameters. Unless there is a requirement for a very fine equilibration this parameter should be defaulted.","units":{},"default":"100","value_type":"INT"},{"index":3,"name":"NDRXVD","description":"A positive integer value that defines the maximum number of depth entries in equilibration property versus depth tables (RSVD, RVVD, PBVD or PDVD etc.) as defined in the SOLUTION section.","units":{},"default":"20","value_type":"INT"},{"index":4,"name":"NTTRVD","description":"A positive integer that defines the maximum number of TVDP tables that describe the initial tracer concentration versus depth.","units":{},"default":"1","value_type":"INT"},{"index":5,"name":"NSTRVD","description":"A positive integer that defines the maximum number of depth entries in the TVDP tables as described in (4)","units":{},"default":"20","value_type":"INT"}],"example":"--\n-- MAX MAX RSVD TVDP TVDP\n-- EQLNUM DEPTH NODES TABLE NODES\nEQLDIMS\n9 1* 20 1* 1* /\nThe above example defines nine equilibration regions the default values for the remaining parameters on the EQLDIMS keyword.","expected_columns":5,"size_kind":"fixed","size_count":1},"EQLOPTS":{"name":"EQLOPTS","sections":["RUNSPEC"],"supported":false,"summary":"The EQLOPTS keyword defines the equilibration options by stating the character command to activate an option to be used for initializing the model. Multiple commands may be utilized to activate several equilibration options following the keyword.","parameters":[{"index":1,"name":"MOBILE","description":"A character string that activates the mobile fluid critical saturation end point correction. If the MOBILE command is stated then this option is activated. This option is not supported by OPM Flow but would change the results if supported so the simulation will be stopped. Therefore this character string should be omitted.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"QUIESC","description":"A character string that activates the initial quiescence option that modifies the equilibrium calculated phase pressures to ensure that a steady state solution is obtained. This options ensures that there is no flow potential between the grid blocks in a given region, which is the normal case when block-centered equilibration is used by setting BOINIT on the EQUIL keyword to zero in the SOLUTION section. If the QUIESC command is stated then this option is activated. This option is not supported by OPM Flow but would change the results if supported so the simulation will be stopped. Therefore this character string should be omitted.","units":{},"default":"None","value_type":"STRING"},{"index":3,"name":"THPRES","description":"A character string that activates the inter-region equilibration flow option. This option allows for a threshold pressure variable entered via the THPRES keyword to define a pressure which prevents flow between regions until the THPRES value between regions is exceeded. If the THPRES command is stated then this option is activated.","units":{},"default":"None","value_type":"STRING"},{"index":4,"name":"IRREVERS","description":"A character string that activates the irreversible inter-region equilibration flow option. This option can only be invoked if the THPRES command has been stated. The option allows for different THPRES values for different directions. If the IRREVERS command is stated then this option is activated. This option is not supported by OPM Flow but would change the results if supported so the simulation will be stopped. Therefore this character string should be omitted.","units":{},"default":"None","value_type":"STRING"}],"example":"--\n-- ACTIVATE EQUILIBRATION OPTIONS\n-- MOBILE END-POINT(MOBILE) STEADY STATE(QUIESC) THRESHOLD(THPRES)\n-- IRREVERSIBLE THRESHOLD(IRREVERS)\nEQLOPTS\n'THPRES' 'IRREVERS' /\nThe above example activates the threshold pressure option with different threshold pressure for different directions.","expected_columns":4,"size_kind":"fixed","size_count":1},"EXTRAPMS":{"name":"EXTRAPMS","sections":["RUNSPEC","GRID","PROPS","REGIONS","SOLUTION","SUMMARY","EDIT","SCHEDULE"],"supported":null,"summary":"The EXTRAPMS keyword activates extrapolation warning messages for when OPM Flow extrapolates the PVT or VFP tables. Frequent extrapolation warning messages should be investigated and resolved as this would indicate possible incorrect data and may result in the simulator extrapolating to unrealistic values.","parameters":[{"index":1,"name":"LEVEL","description":"","units":{},"default":"0","value_type":"INT"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"FAULTDIM":{"name":"FAULTDIM","sections":["RUNSPEC"],"supported":null,"summary":"The FAULTDIM keyword defines the maximum number of records (or segments) that can be entered with the FAULTS keyword. The FAULTS keyword defines the faults in the grid than can be used for setting (or re-setting) transmissibility barriers across the fault planes.","parameters":[{"index":1,"name":"MFSEGS","description":"A positive integer value that defines the maximum number of records (segments) for the FAULTS keyword.","units":{},"default":"0","value_type":"INT"}],"example":"--\n-- FAULT\n-- SEGMS\n--\nFAULTDIM\n10000 /\nThe above example defines the maximum number of records that can be entered using the FAULT keyword to be 10,000 segments.","expected_columns":1,"size_kind":"fixed","size_count":1},"FIELD":{"name":"FIELD","sections":["RUNSPEC"],"supported":null,"summary":"This keyword switches on the oil FIELD system of units for the model.","parameters":[],"example":"--\n-- SWITCH ON THE FIELD SYSTEM OF UNITS FOR BOTH INPUT AND OUTPUT\n--\nFIELD\nThe above example switches on the FIELD system of units for the model.","size_kind":"none","size_count":0},"FMTHMD":{"name":"FMTHMD","sections":["RUNSPEC"],"supported":false,"summary":"This keyword switches on formatted output for the History Match Gradient output file, for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section.","parameters":[],"example":"","size_kind":"none","size_count":0},"FMTIN":{"name":"FMTIN","sections":["RUNSPEC"],"supported":null,"summary":"This keyword switches on the Format Input Files option for all input files. Similar to the commercial simulator, OPM Flow has various options for reading various input files and writing the resulting OPM Flow output files as described in Table 5.14.","parameters":[],"example":"--\n-- SWITCH ON THE FORMAT INPUT FILES OPTION\n--\nFMTIN\nThe above example switches on the format input file option.\n| Process | Keyword | Description | Files |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|\n| Input | FMTIN ","size_kind":"none","size_count":0},"FMTOUT":{"name":"FMTOUT","sections":["RUNSPEC"],"supported":null,"summary":"This keyword switches on the Format Output Files option for all output files. Similar to the commercial simulator, OPM Flow has various options for reading various input files and writing the resulting OPM Flow output files as described in Table 5.15.","parameters":[],"example":"--\n-- SWITCH ON THE FORMAT OUTPUT FILES OPTION\n--\nFMTOUT\nThe above example switches on the format output file option.\n| Process | Keyword | Description | Files |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|\n| Input | FMTIN ","size_kind":"none","size_count":0},"FOAM":{"name":"FOAM","sections":["RUNSPEC"],"supported":null,"summary":"This keyword activates the foam phase and modeling option. The keyword will also invoke data input file checking to ensure that all the required foam phase input parameters are defined in the input deck. Note in the commercial simulator the FOAM phase and model can be used in conjunction with the POLYMER and SURFACT phases; this is not the case for OPM Flow. OPM Flow’s FOAM phase and model is a standalone implementation and cannot be used in conjunction with either the POLYMER or SURFACT phases.","parameters":[],"example":"--\n-- ACTIVATE THE FOAM PHASE IN THE MODEL\n--\nFOAM\nThe above example declares that the foam phase is active in the model.","size_kind":"none","size_count":0},"FORMFEED":{"name":"FORMFEED","sections":["RUNSPEC","GRID","EDIT","PROPS","REGIONS","SOLUTION","SUMMARY","SCHEDULE"],"supported":null,"summary":"The FORMFEED keyword defines the form-feed character, or carriage control character, for the output print (*.PRT) run summary (*.RSM) files. The keyword should be place at the very top of the input file.","parameters":[{"index":1,"name":"VALUE","description":"","units":{},"default":"1","value_type":"INT"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"FRICTION":{"name":"FRICTION","sections":["RUNSPEC"],"supported":false,"summary":"The FRICTION keyword activates the Wellbore Friction option and defines the maximum number of wellbore friction wells together with the maximum number of well branches.","parameters":[{"index":1,"name":"MXWELS","description":"A positive integer defining the maximum number of wellbore friction wells for this model.","units":{},"default":"0","value_type":"INT"},{"index":2,"name":"NWFRIB","description":"","units":{},"default":"1","value_type":"INT"},{"index":3,"name":"MXBRAN","description":"A positive integer defining the maximum number of branches per well. The default value of one implies a standard well with no branches.","units":{},"default":"1"}],"example":"--\n-- WELL BRANCH\n-- MXWELS MXBRAN\nFRICTION\n5 1 /\nThe above example defines the maximum number of wellbore friction wells to be five and the maximum number of branches set to one, for standard wells.","expected_columns":2,"size_kind":"fixed","size_count":1},"FULLIMP":{"name":"FULLIMP","sections":["RUNSPEC"],"supported":null,"summary":"The FULLIMP keyword activates the Fully Implicit Solution formulation and solution options. OPM Flow uses a different numerical scheme which makes this keyword redundant; hence, OPM Flow ignores this keyword. It is documented here for completeness. The keyword as the same function as the IMPLICIT keyword in the RUNSPEC section.","parameters":[],"example":"--\n-- ACTIVATES THE FULLY IMPLICIT SOLUTION OPTION\n--\nFULLIMP\nThe above example switches on the fully implicit solution option; however, this has no effect in OPM Flow input decks.","size_kind":"none","size_count":0},"GAS":{"name":"GAS","sections":["RUNSPEC"],"supported":null,"summary":"This keyword indicate that the gas phase is present in the model and must be used for oil-gas, gas-water, oil-water-gas input decks that contain the gas phase. The keyword will also invoke data input file checking to ensure that all the required gas phase input parameters are defined in the input deck.","parameters":[],"example":"--\n-- GAS PHASE IS PRESENT IN THE RUN\n--\nGAS\nThe above example declares that the gas phase is active in the model.","size_kind":"none","size_count":0},"GASFIELD":{"name":"GASFIELD","sections":["RUNSPEC"],"supported":false,"summary":"The GASFIELD keyword activates and specifies the Gas Field Operations options and determines if extended compressors are present in the run and if the expedited first pass DCQ calculation should be used.","parameters":[{"index":1,"name":"FLAG_COMP","description":"","units":{},"default":"NO","value_type":"STRING"},{"index":2,"name":"FLAG_IT","description":"","units":{},"default":"NO","value_type":"STRING"}],"example":"","expected_columns":2,"size_kind":"fixed","size_count":1},"GASWAT":{"name":"GASWAT","sections":["RUNSPEC"],"supported":null,"summary":"This keyword activates the two-phase Gas-Water model, as such it is equivalent to using both the GAS and WATER keywords in the RUNSPEC section..","parameters":[],"example":"-- ==============================================================================\n--\n-- RUNSPEC SECTION\n--\n-- ==============================================================================\nRUNSPEC\n--\n-- ACTIVATE CO2 STORAGE IN THE MODEL (OPM FLOW CO2 STORAGE KEYWORD)\n--\nCO2STORE\n--\n-- ACTIVATE COMPOSITIONAL MODELING FORMULATION (OPM FLOW KEYWORD)\n--\nCOMPS\n2 /\n--\n-- ACTIVATE GAS-WATER THE MODEL (OPM FLOW KEYWORD)\n--\nGASWAT\nThe above example declares that the run should use the Gas-Water model, together with the CO2STORE option, and with two components.\n| Note This is an OPM Flow keyword, and should not be confused with the more general version of the GASWAT keyword used in the commercial compositional simulator. |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"none","size_count":0},"GDIMS":{"name":"GDIMS","sections":["RUNSPEC"],"supported":false,"summary":"The GDIMS keyword activates the Instantaneous Gradient option and defines the maximum dimensions as used by the GWRTWCV keyword in the SCHEDULE section. The Instantaneous Gradient option calculates derivatives of solution quantities at the current time step with respect to variations in the variables at the current time step. This is different to Gradient option that calculates the derivatives of solution quantities at the current time step with respect to variations in the variables at the initial time step, that is a time equal to zero. Consequently, the Instantaneous Gradient option can be switched on and off by the GUPFREQ keyword in the SCHEDULE section, whereas the Gradient option cannot.","parameters":[{"index":1,"name":"MAX_NUM_GRAD_PARAMS","description":"","units":{},"default":"0","value_type":"INT"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"GIMODEL":{"name":"GIMODEL","sections":["RUNSPEC"],"supported":false,"summary":"This keyword, GIMODEL, activates the Gi Pseudo Compositional option for gas condensate and volatile oil fluids.","parameters":[],"example":"--\n-- ACTIVATE THE GI PSEUDO COMPOSITIONAL OPTION\n--\nGIMODEL\nThe above example switches on the Gi Pseudo Compositional option.","size_kind":"none","size_count":0},"GRAVDR":{"name":"GRAVDR","sections":["RUNSPEC"],"supported":false,"summary":"This keyword switches on gravity drainage and imbibition modeling between the matrix and the fracture grid blocks in dual porosity and dual permeability runs. Note that either DZMTRX or DZMTRXV keywords in the GRID section should be used to set the matrix vertical dimensions if this option is activated.","parameters":[],"example":"--\n-- ACTIVATE GRAVITY DRAINAGE AND IMBIBITION FOR DUAL POROSITY MODEL\n--\nGRAVDR\nThe above example switches on the gravity drainage and imbibition option for the run.","size_kind":"none","size_count":0},"GRAVDRB":{"name":"GRAVDRB","sections":["RUNSPEC"],"supported":false,"summary":"This keyword switches on vertical discretized gravity drainage and imbibition modeling between the matrix and the fracture grid blocks in dual porosity and dual permeability runs. Note that the geometry of the matrix sub-cells should be set to VERTICAL on the NMATOPS keyword in the GRID section if this option is activated.","parameters":[],"example":"--\n-- ACTIVATE VERTICAL DISCRETIZED GRAVITY DRAINAGE AND IMBIBITION\n--\nGRAVDRB\nThe above example switches on the vertical discretized gravity drainage and imbibition option for the run.","size_kind":"none","size_count":0},"GRAVDRM":{"name":"GRAVDRM","sections":["RUNSPEC"],"supported":false,"summary":"This keyword switches on the alternative gravity drainage and imbibition modeling between the matrix and the fracture grid blocks in dual porosity and dual permeability runs. Either the GRAVDRM or GRAVDR keywords should be used to activate this standard or alternative type of formulation.","parameters":[{"index":1,"name":"OPTION1","description":"A defined character string that sets the matrix flow in and out of the matrix block option, and should be set to one of the following: YES: oil flow is bi-directional, that is oil can flow into and out of the matrix block. NO: oil flow is uni-directional, that is oil can flow out of the matrix block.","units":{},"default":"YES","value_type":"STRING","options":["YES","NO"]}],"example":"--\n-- ACTIVATE ALTERNATIVE GRAVITY DRAINAGE AND IMBIBITION MODEL\n--\n-- MATRIX\n-- OPTION\nGRAVDRM\nYES /\nThe above example switches on the alternative gravity drainage and imbibition option for the run and sets oil flow to be bi-directional, that is oil can flow into and out of the matrix block.","expected_columns":1,"size_kind":"fixed","size_count":1},"GRIDOPTS":{"name":"GRIDOPTS","sections":["RUNSPEC"],"supported":null,"summary":"GRIDOPTS activates the negative directional dependent transmissibility multipliers option, defines the maximum number of MULTNUM regions and the number of PINCHNUM regions for the model.","parameters":[{"index":1,"name":"TRANMULT","description":"A character string that activates the negative directional dependent transmissibility multipliers option by setting TRANMULT to YES. Setting the value to NO switches off this option. OPM Flow uses a positive directional dependent transmissibility formulation to describe the flow between two cells, that is for cell (I, J, K) OPM Flow calculates the x face transmissibility between (I, J, K) and (I +1, J, K) cell face. Modification to the transmissibilities in this case is accomplished by the MULTX, MULTY and MULTZ keywords. Setting TRANMULT to YES invokes the option to use a negative directional dependent multiplier scheme using the MULTX-, MULTY- and MULTZ- keywords. In this case OPM Flow applies the x face transmissibility between (I - 1, J, K) and (I, J, K) cell face when using the MULTX-, MULTY- and MULTZ- keywords. Note that if TRANMULT is defaulted, and there are negative directional dependent multiplier keywords in the input deck, then OPM Flow will continue to process the MULTX-, MULTY- and MULTZ keywords correctly. Whereas, the commercial simulator will terminate with an error.","units":{},"default":"NO","value_type":"STRING"},{"index":2,"name":"NRMULT","description":"A positive integer value that defines the maximum number of MULTNUM regions for the MULTNUM array. The MULTNUM array is used in the GRID section to define various inter-region transmissibility regions in the model and NRMULT sets the maximum number of regions which is the maximum value of an element in the MULTNUM array. Inter-region MULTNUM transmissibility multipliers can be defined using the MULTREGT and regional pore volumes multipliers can be set using the MULTREGP keyword.","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"NRPINC","description":"A positive integer value that defines the maximum number of PINCHNUM regions for the PINCHNUM array. The PINCHNUM array is used in the GRID section to define various regions in the model and NRPINC sets the maximum of regions which is the maximum value of an element in the PINCHNUM array. Each regions criteria for setting the pinch out criteria is set by the PINCHREG keyword.","units":{},"default":"0","value_type":"INT"}],"example":"–-\n-- NEG MAX MAX\n-- MULTS MULTNUM PINCHNUM\nGRIDOPTS\nNO 9 1* /\nThe above example switches off the negative directional dependent transmissibility multipliers option and defines the maximum of MULTNUM regions to be nine,. The NRPINC parameter is defaulted which means there the maximum number of PINCHREG regions is zero.","expected_columns":3,"size_kind":"fixed","size_count":1},"H2SOL":{"name":"H2SOL","sections":["RUNSPEC"],"supported":null,"summary":"The H2SOL keyword activates dissolved hydrogen (H2) in the water phase, where H2 is represented by the SOLVENT pseudo component, using the simulator’s H2-Brine PVT model. This keyword is a compositional keyword in the commercial simulator but has been implemented in OPM Flow’s black-oil model.","parameters":[],"example":"The example shows the usage of H2SOL to model H2 injection in a live-oil reservoir. The RUNSPEC section includes the H2SOL keyword, which activates dissolved hydrogen (H2) in the water phase. The SOLVENT keyword activates the solvent pseudo component, which represents H2. The DISGASW keyword has been used to activate dissolved H2 in the brine.\n-- ==============================================================================\n--\n-- RUNSPEC SECTION\n--\n-- ==============================================================================\nRUNSPEC\n-- ------------------------------------------------------------------------------\n-- FLUID TYPES AND TRACER OPTIONS\n-- ------------------------------------------------------------------------------\n--\n-- ACTIVATE DISSOLVED H2 IN WATER (OPM FLOW KEYWORD)\n--\nH2SOL\n--\n-- SOLVENT PHASE IS PRESENT IN THE RUN\n--\nSOLVENT\n--\n-- DISSOLVED H2 IN WATER IS PRESENT IN THE RUN (OPM FLOW KEYWORD)\n--\nDISGASW\nThe second part of the example covers the additional data required in the PROPS section, in which the H2-gas miscible relative permeabilities are defined using the SSFN keyword. The initial temperature and salinity are defined using the RTEMP and SALINITY keywords. The oil and gas PVT properties should be defined in the normal way. No water PVT data is required.\n-- ==============================================================================\n--\n-- PROPS SECTION\n--\n-- ==============================================================================\nPROPS\n--\n-- RESERVOIR\n-- TEMPERATURE\n-- -----------\nRTEMP\n80.0 / RESERVOIR TEMP\n--\n-- SET SALINITY FOR ALL CELLS (OPM FLOW KEYWORD)\n--\nSALINITY\n0.7 /\n--\n-- SOLVENT RELATIVE PERMEABILITY TABLES\n--\nSSFN\n-- SGAS KRGT KRST\n-- FRAC\n-- -------- -------- --------\n0.0000 0.0000 0.0000\n1.0000 1.0000 1.0000 /\nThe third part of the example covers initialising the model in the SOLUTION section. Here the EQUIL keyword is used as normal to equilibrate the oil, gas and water phases, and the SSOL keyword to specify that there is initially no H2 present in the gas phase.\n-- ==============================================================================\n--\n-- SOLUTION SECTION\n--\n-- ==============================================================================\nSOLUTION\n--\n-- DATUM DATUM OWC PCOW GOC PCGO RS RV N E300 RVW\n-- DEPTH PRESS DEPTH ---- DEPTH ---- OPT OPT OPT OPT OPT\nEQUIL\n2000.0 200.0 2100.0 0.00 2000.0 0.00 1* 1* 1* 2* 1* /\n--\n-- DEFINE INITIAL EQUILIBRATION SOLVENT SAT VALUES FOR ALL CELLS IN THE MODEL\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nSSOL\n30000*0.0 /\nFor the summary section, the H2 storage quantity can be tracked using the solvent injection and production volumes as shown below.\n-- ==============================================================================\n--\n-- SUMMARY SECTION\n--\n-- ==============================================================================\nSUMMARY\n--\n-- EXPORT STANDARD SUMMARY VARIABLE VECTORS TO FILE\n--\nALL\n--\n-- FIELD SOLVENT INJECTION RATE\nFNIR\n--\n-- FIELD SOLVENT PRODUCTION RATE\nFNPR\n--\n-- FIELD SOLVENT INJECTION TOTAL\nFNIT\n--\n-- FIELD SOLVENT PRODUCTION TOTAL\nFNPT\nThe final part of the example covers the SCHEDULE section. The WSOLVENT keyword is used to specify the injected solvent fraction (in this case pure H2).\n-- ==============================================================================\n--\n-- SCHEDULE SECTION\n--\n-- ==============================================================================\nSCHEDULE\n--\n-- RESTART CONTROL BASIC = 4 (ALL=2, YEARLY=4, MONTHLY=5, TSTEP=6)\n--\nRPTRST\n'BASIC=1' 'ALLPROPS' /\n--\n-- DEFINE GAS INJECTION WELL SOLVENT FRACTION\n--\n-- WELL SOLVENT\n-- NAME FRACTION\n-- --------\nWSOLVENT\nGI01 1.0000 /\n/","size_kind":"none","size_count":0},"H2STORE":{"name":"H2STORE","sections":["RUNSPEC"],"supported":true,"summary":"The H2STORE keyword activates the hydrogen (H2) storage model for the run to account for both hydrogen and water phase solubility. H2STORE is similar to CO2STORE, which activates the carbon dioxide (CO2) storage model.","parameters":[],"example":"The first example shows the standard useage of H2STORE with Option (1) the Gas-Water model (GASWAT). Here we also activate the dissolved gas in water (DISGASW) and vaporized water in gas (VAPWAT) options.\n-- ==============================================================================\n--\n-- RUNSPEC SECTION\n--\n-- ==============================================================================\nRUNSPEC\n-- ------------------------------------------------------------------------------ -- FLUID TYPES AND TRACER OPTIONS\n-- ------------------------------------------------------------------------------\n--\n-- ACTIVATE H2 STORAGE IN THE MODEL (OPM FLOW H2 STORAGE KEYWORD)\n--\nH2STORE\n--\n-- ACTIVATE GAS-WATER THE MODEL (OPM FLOW KEYWORD)\n--\nGASWAT\n--\n-- DISSOLVED GAS IN WATER IS PRESENT IN THE RUN (OPM FLOW KEYWORD)\n--\nDISGASW\n--\n-- VAPORIZED WATER IN DRY/WET GAS IS PRESENT IN THE RUN (OPM FLOW KEYWORD)\n--\nVAPWAT\nThe second part of the example covers the data required for the PROPS section, in which the two-phase relative permeability functions are set using GSF and WSF keywords.\n-- ==============================================================================\n--\n-- PROPS SECTION\n--\n-- ==============================================================================\nPROPS\n--\n-- RESERVOIR\n-- TEMPERATURE\n-- -----------\nRTEMP\n80.0 / RESERVOIR TEMP\n--\n-- ROCK COMPRESSIBILITY\n--\n-- REFERENCE PRESSURE IS TAKEN FROM THE HCPV WEIGHTED RESERVOIR PRESSURE\n--\n-- REF PRES CF\n-- BARSA 1/BARSA\n-- -------- --------\nROCK\n200.0 5.0E-05 / ROCK COMPRESSIBILITY\n--\n-- GAS RELATIVE PERMEABILITY TABLES (OPM FLOW KEYWORD)\n--\nGSF\n-- SGAS KRG PCGW\n-- FRAC PSIA\n-- -------- -------- -------\n0.000 0.000 0.0\n0.080 0.001 0.0\n0.170 0.010 0.0\n0.350 0.050 0.0\n0.530 0.200 0.0\n0.620 0.350 0.0\n0.650 0.390 0.0\n0.710 0.560 0.0\n0.800 1.000 0.0 / TABLE NO. 01\n--\n-- WATER RELATIVE PERMEABILITY TABLES (OPM FLOW KEYWORD)\n--\nWSF\n-- SWAT KRW\n-- FRAC\n-- -------- --------\n0.200 0.0000\n0.400 0.1000\n0.800 0.5000\n1.000 1.0000 / TABLE NO. 01\n--\n-- SET SALINITY FOR ALL CELLS (OPM FLOW KEYWORD)\n--\nSALINITY\n0.7 /\nNo other data is required to define the fluid and rock properties in the PROPS section as the data is generated from internal analytic correlations and models by the simulator. Finally, note that units for salinity are to the 10-3, thus for metric units we have 10-3 x kg-M/kg.\nThe third part of the example covers initializing the model in the SOLUTION section. Here we use the EQUIL(EQLOPT6) parameter equal to one, to use table number one of the RVWVD keyword, in order to set the vaporized water versus depth distribution for the model.\n-- ==============================================================================\n--\n-- SOLUTION SECTION\n--\n-- ==============================================================================\nSOLUTION\n--\n-- SYSTEM IS SATURATED WITH WATER\n--\n-- DATUM DATUM OWC PCOW GOC PCGO RS RV N E300 RVW\n-- DEPTH PRESS DEPTH ---- DEPTH ---- OPT OPT OPT OPT OPT\nEQUIL\n2000.0 200.0 1800.0 0.00 1800.0 0.00 1* 1* 1* 2* 1 /\n--\n-- WATER VAPOR RATIO VS DEPTH (OPM FLOW KEYWORD)\n--\n-- DEPTH RVW\n-- STB/MSCF\n-- ------ --------\nRVWVD\n1000.0 0.000\n3000.0 0.000 / RVW VS DEPTH EQUIL REGN 01\nIn the SUMMARY section, the simulator supports summary vectors specific to CO2 storage (see Section 11.1.12 Option Specific Variables - CO2STORE/H2STORE Model) many of these can also be used for H2 storage including those shown below.\n-- ==============================================================================\n--\n-- SUMMARY SECTION\n--\n-- ==============================================================================\nSUMMARY\n--\n-- EXPORT STANDARD SUMMARY VARIABLE VECTORS TO FILE\n--\nALL\n--\n-- FIELD H2 DISOLVED IN WATER PHASE\nFWCD\n--\n-- FIELD H2 TRAPPED IN GAS PHASE\nFGCDI\n--\n-- FIELD H2 MOBILE IN GAS PHASE\nFGCDM\nThe final part of the example covers the SCHEDULE section. The standard WCONINJE keyword is then used to set the gas injection rate, in this case 100,000 sm3/day of H2.\n-- ======================","size_kind":"none","size_count":0},"HMDIMS":{"name":"HMDIMS","sections":["RUNSPEC"],"supported":false,"summary":"This keyword, HMDIMS, defines the maximum parameter dimensions for the History Match Gradient option.","parameters":[{"index":1,"name":"MAX_GRAD_REGIONS","description":"","units":{},"default":"0","value_type":"INT"},{"index":2,"name":"MAX_SUB_REGIONS","description":"","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"MAX_GRADS","description":"","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"MAX_FAULTS","description":"","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"MAX_AQUIFER_PARAMS","description":"","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"MAX_WELL_PARAMS","description":"","units":{},"default":"0","value_type":"INT"},{"index":7,"name":"UNUSED","description":"","units":{},"default":"0","value_type":"INT"},{"index":8,"name":"MAX_ROCK_GRAD_PARAMS","description":"","units":{},"default":"0","value_type":"INT"},{"index":9,"name":"MAX_WELL_CONN_PARAMS","description":"","units":{},"default":"0","value_type":"INT"}],"example":"","expected_columns":9,"size_kind":"fixed","size_count":1},"HYST":{"name":"HYST","sections":["RUNSPEC"],"supported":false,"summary":"The HYST keyword activates the hysteresis option, the keyword should be avoided and the hysteresis option should be enabled by the HYSER parameter on the SATOTPS keyword in the RUNSPEC section.","parameters":[],"example":"","size_kind":"none","size_count":0},"IMPES":{"name":"IMPES","sections":["RUNSPEC"],"supported":null,"summary":"The IMPES keyword activates the Implicit Pressure Explicit Saturation formulation and solution options, commonly know as IMPES. OPM Flow uses a different numerical scheme which makes this keyword redundant; hence, OPM Flow ignores this keyword. It is documented here for completeness.","parameters":[],"example":"--\n-- ACTIVATE THE IMPES SOLUTION OPTION\n--\nIMPES\nThe above example switches on the IMPES solution option; however, this has no effect in OPM Flow input decks.","size_kind":"none","size_count":0},"IMPLICIT":{"name":"IMPLICIT","sections":["RUNSPEC"],"supported":null,"summary":"The IMPLICIT keyword activates the Fully Implicit Solution formulation and solution options. OPM Flow uses a different numerical scheme which makes this keyword redundant; hence, OPM Flow ignores this keyword. It is documented here for completeness. The keyword as the same function as the FULLIMP keyword in the RUNSPEC section.","parameters":[],"example":"--\n-- ACTIVATES THE FULLY IMPLICIT SOLUTION OPTION\n--\nIMPLICIT\nThe above example switches on the fully implicit solution option; however, this has no effect in OPM Flow input decks.","size_kind":"none","size_count":0},"INCLUDE":{"name":"INCLUDE","sections":["RUNSPEC","GRID","EDIT","PROPS","REGIONS","SOLUTION","SUMMARY","SCHEDULE"],"supported":null,"summary":"The INCLUDE keyword informs OPM Flow to continue reading input data from the specified INCLUDE file. When the end of the INCLUDE file is reached, or the ENDINC keyword is encountered in the included file, input data is read from the next keyword in the current file.","parameters":[{"index":1,"name":"IncludeFile","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"INSPEC":{"name":"INSPEC","sections":["RUNSPEC"],"supported":false,"summary":"This keyword switches on the writing of the INIT Index file that specifies and defines the format and data type written to the *.INIT data file. The *.INIT data file contains the static data specified in the GRID, PROPS and REGIONS sections. For example, the PORO, PERM and NTG arrays from the GRID section. The data is used in post-processing software, for example OPM ResInsight, to visualize the static grid properties.","parameters":[],"example":"--\n-- ACTIVATE WRITING THE INIT INDEX FILE FOR POST-PROCESSING\n--\nINSPEC\nThe above example switches on the writing of the INIT Index file for post-processing in ResInsight.","size_kind":"none","size_count":0},"LAB":{"name":"LAB","sections":["RUNSPEC"],"supported":null,"summary":"This keyword switches on the LABORATORY system of units for the model.","parameters":[],"example":"--\n-- SWITCH ON THE LABORATORY SYSTEM OF UNITS FOR BOTH INPUT AND OUTPUT\n--\nLAB\nThe above example switches on the LABORATORY system of units for the model.","size_kind":"none","size_count":0},"LGR":{"name":"LGR","sections":["RUNSPEC"],"supported":null,"summary":"The LGR keyword defines the maximum dimensions and parameters for the Local Grid Refinement (“LGR”) option.","parameters":[{"index":1,"name":"MAXLGR","description":"A positive integer value that defines the maximum number of LGRs in the model.","units":{},"default":"0","value_type":"INT"},{"index":2,"name":"MAXCLS","description":"A positive integer value that defines the maximum number of grid blocks in all the LGRs.","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"MCOARS","description":"A positive integer value that defines the maximum number of amalgamated coarse grid blocks in the model.","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"MAMALG","description":"A positive integer value that defines the maximum number of LGR amalgamations in the model.","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"MXLALG","description":"A positive integer value that defines the maximum number of LGRs in any amalgamation in the model.","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"LSTACK","description":"A positive integer that defines the maximum number of previous search directions stored by the linear solver for the LGR. See the NSTACK keyword in the RUNSPEC section for a full description.","units":{},"default":"10","value_type":"INT"},{"index":7,"name":"INTOPT","description":"A character string set to either INTERP to activate the Quandalle87\n Quandalle, Philippe & Besset, P. (1985). Reduction of Grid Effects Due to Local Sub-Gridding in Simulations Using a Composite Grid. 10.2118/13527-MS. pressure correction, or NOINTERP to deactivate this option. The option applies bi-linear interpolation to the global cells surrounding an LGR in order to improve the accuracy of the flow calculations between the LGR and the host cells. Quandalle, Philippe & Besset, P. (1985). Reduction of Grid Effects Due to Local Sub-Gridding in Simulations Using a Composite Grid. 10.2118/13527-MS.","units":{},"default":"NOINTERP","value_type":"STRING"},{"index":8,"name":"NCHCOR","description":"A positive integer value that defines the maximum number of grid blocks within a coarsened grid that overlap parallel domain boundaries for when the Parallel option has been invoked by the PARALLEL keyword in the RUNSPEC section. OPM Flow uses a different numerical scheme which makes this parameter redundant, see section 2.2Running OPM Flow 2023-04 From The Command Lineon how to run OPM Flow in parallel mode.","units":{},"default":"0","value_type":"INT"}],"example":"--\n-- LOCAL GRID REFINEMENT DIMENSIONS AND PARAMETERS\n--\n-- LGR LGR LGR LGR LGR LGR LGR LGR\n-- MAXLGR MAXCLS MCOARS MAMALG MXLALG LSTACK INTOPT NCHCOR\nLGR\n10 1000 1* 1* 1* 1* INTERP 1* /\nThe above example sets the maximum number of LGRs to 10 and the maximum number of grid blocks a LGR may contain to 1,000, and that the Quandalle pressure correction should be used to improve the flow calculation.","expected_columns":8,"size_kind":"fixed","size_count":1},"LGRCOPY":{"name":"LGRCOPY","sections":["RUNSPEC","GRID","EDIT"],"supported":null,"summary":"The LGRCOPY keyword actives the Local Grid Refinement (“LGR”) Inheritance option that allows the LGR to inherit the properties of the global or host cell containing an LGR grid block when it is defined, as opposed to the normal process of applying this transform at the end of the GRID section. LGRCOPY can be used in the RUNSPEC, GRID and EDIT sections. If used in the RUNSPEC section then the option is applied to all LGRs defined in the input file, whereas if used in the GRID or EDIT sections the keyword must be placed inside a LGR definition section, that is between a CARFIN (Cartesian LGR grid) or RADFIN/RADFIN4 (radial LGR grid) keyword and an ENDFIN keyword. In the latter case inheritance is applied on an individual LGR basis.","parameters":[],"example":"The following example activates the LGR Inheritance option for all LGRs in the model.\n-- ==============================================================================\n--\n-- RUNSPEC SECTION\n--\n-- ==============================================================================\nRUNSPEC\n--\n-- ACTIVATE LOCAL GRID REFINEMENT INHERITANCE\n--\nLGRCOPY","size_kind":"none","size_count":0},"LICENSES":{"name":"LICENSES","sections":["RUNSPEC"],"supported":false,"summary":"This keyword defines the additional software licenses that are required to invoke various licensed options in the commercial simulator at the start of the run. The commercial simulator requests a license when keywords associated with a licensed option is encountered in the input deck, this may result in the license being unavailable at the time of request and after the simulation has been initiated, resulting in the run terminating. This keyword avoids this scenario by reserving the license at the start of the run.","parameters":[{"index":1,"name":"FEATURE","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"list"},"LIVEOIL":{"name":"LIVEOIL","sections":["RUNSPEC"],"supported":false,"summary":"This keyword activates oil, free and dissolved gas in the model and therefore makes the oil phase live oil88\n “Live” oil is oil that contains gas in solution, which is normally the case for most conventional oil reservoirs. However, for oil reservoirs classified as heavy oil reservoirs, the in situ dissolved gas may be negligible and oil would then be classified as gas-free oil which is commonly referred to as “dead” oil. in the black-oil formulation, and is equivalent to setting the phases present in the model to be oil, dissolved gas, gas and water phases. Note if water is present in the model this needs to be explicitly stated via the WATER keyword in the RUNSPEC section (see also the BLACKOIL and DEADOIL keywords in the RUNSPEC section). The keyword is used by the commercial simulator’s compositional THERMAL option to set the phases present in the model.","parameters":[],"example":"The following example activates the black-oil phases in the model.\n--\n-- ACTIVATE LIVE-OIL PHASE\n--\nLIVEOIL\nAlternatively one could explicitly declare the phases using the following keywords in the RUNSPEC section.\n--\n-- OIL PHASE IS PRESENT IN THE RUN\n--\nOIL\n--\n-- DISSOLVED GAS IN LIVE OIL IS PRESENT IN THE RUN\n--\nDISGAS\n--\n-- GAS PHASE IS PRESENT IN THE RUN\n--\nGAS\n--\n-- WATER PHASE IS PRESENT IN THE RUN\n--\nWATER\nThe above example switches on the oil, dissolved gas, gas and water phases in the model.","size_kind":"none","size_count":0},"LOAD":{"name":"LOAD","sections":["RUNSPEC"],"supported":false,"summary":"The LOAD keyword loads a previously generated SAVE file to enable a fast restart. A SAVE file contains all the data from a previous run’s RUNSPEC, GRID, EDIT, PROPS and REGIONS sections, and thus there is no need for the simulator to calculate various parameters, including grid block transmissibilities etc. This allows for the current run to restart quicker than a conventional restart run using the RESTART keyword in the SOLUTION section via a RESTART file (*.UNRST or *.FUNRST etc.). The keyword should be the first keyword in the input deck and the RUNSPEC, GRID, EDIT, PROPS and REGIONS sections should be deleted from the input deck.","parameters":[{"index":1,"name":"FILE","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"REPORT_STEP","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"NOSIM","description":"","units":{},"default":"SIM","value_type":"STRING"},{"index":4,"name":"FORMATTED","description":"","units":{},"default":"UNFORMATTED","value_type":"STRING"},{"index":5,"name":"REQUEST_SAVE_OUTPUT","description":"","units":{},"default":"NO","value_type":"STRING"}],"example":"","expected_columns":5,"size_kind":"fixed","size_count":1},"LOWSALT":{"name":"LOWSALT","sections":["RUNSPEC"],"supported":false,"summary":"This keyword, LOWSALT, activates the low salt brine phase for the Brine option and also activates the Brine option. See also the BRINE keyword in the RUNSPEC section.","parameters":[],"example":"--\n-- ACTIVATE THE LOW SALT BRINE PHASE FOR THE BRINE OPTION\n--\nLOWSALT\nThe above example declares that the low salt brine phase is active in the model for the Brine option.","size_kind":"none","size_count":0},"MEMORY":{"name":"MEMORY","sections":["RUNSPEC"],"supported":null,"summary":"This keyword defines the memory allocation for the run.","parameters":[{"index":1,"name":"UNUSED","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"THOUSANDS_CHAR8","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":2,"size_kind":"fixed","size_count":1},"MESSAGE":{"name":"MESSAGE","sections":["RUNSPEC","GRID","EDIT","PROPS","REGIONS","SOLUTION","SUMMARY","SCHEDULE"],"supported":null,"summary":"The MESSAGE keyword outputs a user message to the terminal, as well as to the print (*.PRT) and debug (*.DBG) files. Note this is different to the MESSAGES keyword, that defines OPM Flows message print limits and stop limits generated by the simulator.","parameters":[{"index":1,"name":"MessageText","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","size_kind":"fixed","size_count":1,"variadic_record":true},"MESSAGES":{"name":"MESSAGES","sections":["RUNSPEC","GRID","EDIT","PROPS","REGIONS","SOLUTION","SUMMARY","SCHEDULE"],"supported":null,"summary":"The MESSAGES keyword defines the print and stops levels for various messages. The “print limits” set the maximum number of messages that will be printed, after which no more messages will be printed and the “stop limits” terminate the run when these limits are exceeded. There are six levels of message that increase in severity from informative all the way to programming errors, as outlined in Table 4.5.","parameters":[{"index":1,"name":"MESSAGE_PRINT_LIMIT","description":"","units":{},"default":"1000000","value_type":"INT"},{"index":2,"name":"COMMENT_PRINT_LIMIT","description":"","units":{},"default":"1000000","value_type":"INT"},{"index":3,"name":"WARNING_PRINT_LIMIT","description":"","units":{},"default":"10000","value_type":"INT"},{"index":4,"name":"PROBLEM_PRINT_LIMIT","description":"","units":{},"default":"100","value_type":"INT"},{"index":5,"name":"ERROR_PRINT_LIMIT","description":"","units":{},"default":"100","value_type":"INT"},{"index":6,"name":"BUG_PRINT_LIMIT","description":"","units":{},"default":"100","value_type":"INT"},{"index":7,"name":"MESSAGE_STOP_LIMIT","description":"Not supported","units":{},"default":"1000000","value_type":"INT"},{"index":8,"name":"COMMENT_STOP_LIMIT","description":"Not supported","units":{},"default":"1000000","value_type":"INT"},{"index":9,"name":"WARNING_STOP_LIMIT","description":"Not supported","units":{},"default":"10000","value_type":"INT"},{"index":10,"name":"PROBLEM_STOP_LIMIT","description":"Not supported","units":{},"default":"100","value_type":"INT"},{"index":11,"name":"ERROR_STOP_LIMIT","description":"Not supported","units":{},"default":"10","value_type":"INT"},{"index":12,"name":"BUG_STOP_LIMIT","description":"Not supported","units":{},"default":"1","value_type":"INT"},{"index":13,"name":"GROUP_PRINT_LIMIT","description":"Not supported","units":{},"default":"10","value_type":"INT"}],"example":"","expected_columns":13,"size_kind":"fixed","size_count":1,"variadic_record":true},"MESSSRVC":{"name":"MESSSRVC","sections":["RUNSPEC"],"supported":false,"summary":"The MESSSRVC keyword activates or deactivates output to the database message file (*.DBPRTX). The file contains all the messages from run in binary format and is used in some post-processing software to annotate production line plots from the run.","parameters":[{"index":1,"name":"PRODUCE_MESSAGE","description":"","units":{},"default":"ON","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"METRIC":{"name":"METRIC","sections":["RUNSPEC"],"supported":null,"summary":"This keyword switches on the METRIC system of units for the model.","parameters":[],"example":"--\n-- SWITCH ON THE METRIC SYSTEM OF UNITS FOR BOTH INPUT AND OUTPUT\n--\nMETRIC\nThe above example switches on the METRIC system of units for the model.","size_kind":"none","size_count":0},"MICP":{"name":"MICP","sections":["RUNSPEC"],"supported":null,"summary":"The MICP keyword activates the Microbially Induced Calcite Precipitation (“MICP”) model for the run. MICP is a new and sustainable technology which utilizes biochemical processes to create barriers by calcium carbonate cementation, the technology has the potential to be used for sealing leakage zones in geological formations. Further information on the mathematical model can be found in the open-access publications Landa-Marbán et al89\n Landa-Marbán, D., Tveit, S., Kumar, K., Gasda, S.E., 2021. Practical approaches to study microbially induced calcite precipitation at the eld scale. Int. J. Greenh. Gas Control 106, 103256. https://doi.org/10.1016/j.ijggc.2021.103256. and 90\n Landa-Marbán, D., Kumar, K., Tveit, S., Gasda, S.E., 2021. Numerical studies of CO2 leakage remediation by micp-based plugging technology. In: Røkke, N.A. and Knuutila, H.K. (Eds) Short Papers from the 11th International Trondheim CCS conference, ISBN: 978-82-536-1714-5, 284-290..","parameters":[],"example":"--\n-- ACTIVATE THE MICROBIAL INDUCED CALCITE PRECIPITATION MODEL\n--\nMICP\n--\n-- WATER PHASE IS PRESENT IN THE RUN\n--\nWATER\nThe above example declares that the MICP model is active for the run and activates the water phase for the MICP model. For a complete example of this model, see MICP.DATA.\n| Note This is an OPM Flow specific keyword used to investigate leakage remediation. The module requires that both the MICP and WATER keywords in the RUNSPEC to be active. |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"none","size_count":0},"MINNPCOL":{"name":"MINNPCOL","sections":["RUNSPEC"],"supported":null,"summary":"The MINNPCOL keyword defines the minimum number of Newton iterations within a time step where the well production and injection targets may be updated, after which the well targets will be frozen until the time step calculations have converged and the time step is complete.","parameters":[{"index":1,"name":"MINNPCOL","description":"A positive integer that defines the minimum number of Newton iterations within a timestep where well targets may be updated.","units":{},"default":"3","value_type":"INT"}],"example":"--\n-- DEFINE THE MIN NUMBER OF ITERATIONS TO UPDATE WELL FLOW TARGETS\n--\nMINNPCOL\n3 /\nThe above example sets the MINNPCOL value to its default value of three.\n| Note This is an OPM Flow specific keyword that sets the minimum number of Newton iterations, as opposed to the NUPCOL keyword that defines the maximum number of Newton iterations within a time step, after which well targets are frozen. |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":1,"size_kind":"fixed","size_count":1},"MISCIBLE":{"name":"MISCIBLE","sections":["RUNSPEC"],"supported":true,"summary":"The MISCIBLE keyword defines the options associated with the Todd-Longstaff91\n M. R. Todd and W. J Longstaff, The Development, Testing, and Application Of a Numerical Simulator for Predicting Miscible Flood Performance\". In: J. Petrol. Tech. 24.7 (1972), pages 874-882. mixing parameters used for when polymer flooding or CO2 EOR simulation cases are being run.","parameters":[{"index":1,"name":"NTMISC","description":"A positive integer value that declares the number miscible residual oil saturations versus water saturations tables for SORWMIS keyword and the number Todd-Longstaff mixing parameters entries on the TLMIXPAR keyword.","units":{},"default":"1","value_type":"INT"},{"index":2,"name":"NSMISC","description":"A positive integer value that sets the maximum number of entries (or rows) for each SORWMIS table defined by the SORWMIS keyword.","units":{},"default":"20","value_type":"INT"},{"index":3,"name":"MISOPT","description":"A character string that defines the numerical dispersion control options for the oil and gas relative permeability curves, set to either NONE or TWOPOINT: NONE – standard single point up streaming, that is using the immediate neighbor TWOPOINT – two-point up streaming, that is using the immediate neighbor plus one cell for better numerical dispersion control but with a higher computational cost. Only the default value of NONE is supported.","units":{},"default":"NONE","value_type":"STRING"}],"example":"--\n-- NTAB MAX UPSTRM\n-- NTMISC NSMISC MISOPT\nMISCIBLE\n1 20 NONE /\nThe above example defines the default values for the MISCIBLE keyword, that is one table with a maximum of 20 rows per table using the standard one cell upstream option.","expected_columns":3,"size_kind":"fixed","size_count":1},"MONITOR":{"name":"MONITOR","sections":["RUNSPEC","SUMMARY"],"supported":null,"summary":"The MONITOR keyword activates the writing out of the run time monitoring information used by post-processing graphics software to display run time information, for example the simulated production and injection rates and cumulative values. OPM Flow does not have this functionality.","parameters":[],"example":"--\n-- ACTIVATE MONITORING OUTPUT DATA AND FILES\n--\nMONITOR\nThe above example switches on the output required for run time monitoring required by post-processing graphics software to review the simulation results in real time as the run progresses; however, this has no effect in OPM Flow input decks.","size_kind":"none","size_count":0},"MSGFILE":{"name":"MSGFILE","sections":["RUNSPEC"],"supported":false,"summary":"MSGFILE keyword activates or deactivates the message file output used by pre- and post-processing software. Note that message file processing is not available in OPM Flow.","parameters":[{"index":1,"name":"MSGOPT","description":"A positive integer set to 0 for to deactivate message file output or 1 to activate message file output.","units":{},"default":"1","value_type":"INT"}],"example":"--\n-- OUTPUT\n-- OPTN\nMSGFILE\n0 /\nThe above example deactivates the message file output, but the keyword is ignored by OPM Flow.","expected_columns":1,"size_kind":"fixed","size_count":1},"MULTIN":{"name":"MULTIN","sections":["RUNSPEC"],"supported":null,"summary":"This keyword switches on the Multiple Input Files option for all input files. Similar to the commercial simulator, OPM Flow has various options for reading various input files and writing the resulting OPM Flow output files as described in Table 5.23.","parameters":[],"example":"--\n-- ACTIVATE THE MULTIPLE INPUT FILES OPTION\n--\nMULTIN\nThe above example switches on the multiple input file option.\n| Process | Keyword | Description | Files |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|\n| Input | FMTIN ","size_kind":"none","size_count":0},"MULTOUT":{"name":"MULTOUT","sections":["RUNSPEC"],"supported":null,"summary":"This keyword switches on the Multiple Output Files option for all output files. Similar to the commercial simulator, OPM Flow has various options for reading various input files and writing the resulting OPM Flow output files as described in Table 5.24.","parameters":[],"example":"--\n-- ACTIVATE THE MULTIPLE OUTPUT FILES OPTION\n--\nMULTOUT\nThe above example switches on the multiple output file option.\n| Process | Keyword | Description | Files |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|\n| Input | FMTIN ","size_kind":"none","size_count":0},"MULTOUTS":{"name":"MULTOUTS","sections":["RUNSPEC"],"supported":false,"summary":"This keyword switches on the Multiple Output Files option for SUMMARY files only, and overwrites the UNIFOUT keyword in the RUNSPEC section that activates the Unified Output Files option for all output files.","parameters":[],"example":"--\n-- ACTIVATE MULTIPLE OUTPUT SUMMARY FILES ONLY OPTION\n--\nMULTOUTS\nThe above example switches on the multiple output file option.","size_kind":"none","size_count":0},"MULTREAL":{"name":"MULTREAL","sections":["RUNSPEC"],"supported":false,"summary":"The MULTREAL keyword activates the commercial simulator’s Multi-Realization License option.","parameters":[{"index":1,"name":"SESSION_SPEC","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"STANDARD_LICENCE","description":"","units":{},"default":"YES","value_type":"STRING"}],"example":"","expected_columns":2,"size_kind":"fixed","size_count":1},"NETWORK":{"name":"NETWORK","sections":["RUNSPEC"],"supported":null,"summary":"This keyword activates the Extended Network option and defines the maximum number of nodes and links (branches) in the network. The Extended Network option is a different facility to the Standard Network facility, as such, this keyword should only be used if the former network is required for the run.","parameters":[{"index":1,"name":"NODMAX","description":"NODMAX is a positive integer that defines the maximum number of nodes in the Extended Network model.","units":{},"default":"None","value_type":"INT"},{"index":2,"name":"NBRMAX","description":"NBRMAX is a positive integer that defines the maximum number of links in the Extended Network model.","units":{},"default":"None","value_type":"INT"},{"index":3,"name":"NBCMAX","description":"NBCMAX is a positive integer that defines the maximum number of branches that can be connected to a node in the Extended Network model, used in the commercial compositional simulator. The parameter is ignored by OPM Flow and should be defaulted or set to the default value of 20.","units":{},"default":"20","value_type":"INT"}],"example":"--\n-- ACTIVATE THE EXTENDED NETWORK OPTION AND DEFINE PARAMETERS\n--\n-- MAX. MAX NOT\n-- NODE LINK USED\nNETWORK\n10 12 1* /\nIn the above example the maximum number of nodes is set equal to ten and the maximum number of links (or branches) is set equal to 12, for the Extended Network option.","expected_columns":3,"size_kind":"fixed","size_count":1},"NINEPOIN":{"name":"NINEPOIN","sections":["RUNSPEC"],"supported":false,"summary":"The NINEPOIN keyword activates the Nine-Point Discretization formulation for the whole grid. If the keyword is absent from the run then the conventional standard five-point discretization formulation is used for the model. The nine-point scheme is based on adding additional non-neighbor connections between the diagonal neighbors in the areal plane, in order to reduce grid orientation effects92\n Yanosik, J. L. and McCracken, T. A. “A Nine-Point, Finite-Difference Reservoir Simulator for Realistic Prediction of Adverse Mobility Ratio Displacements,” paper SPE 5734, Society of Petroleum Engineers Journal (1979) 19, No. 4, 253-262..","parameters":[],"example":"--\n-- ACTIVATE THE NINE-POINT DISCRETIZATION OPTION\n--\nNINEPOIN\nThe above example switches on the Nine-Point Discretization option for the whole grid.","size_kind":"none","size_count":0},"NMATRIX":{"name":"NMATRIX","sections":["RUNSPEC"],"supported":false,"summary":"The NMATRIX keyword activates the Discretized Matrix Dual Porosity option and specifies the number of sub-grid blocks in the actual matrix grid blocks. See also the NMATOPS keyword in the GRID section that defines various parameters for this option.","parameters":[{"index":1,"name":"NMATRIX","description":"A positive integer value that specifies the number of sub-grid blocks in the actual matrix grid blocks.","units":{},"default":"1","value_type":"INT"}],"example":"--\n-- SUB-GRIDS\n-- NMATRIX\nNMATRIX\n4 /\nThe above example activates the Discretized Matrix Dual Porosity option and specifies the number of sub-grid blocks in the actual matrix grid block to be four.","expected_columns":1,"size_kind":"fixed","size_count":1},"NNEWTF":{"name":"NNEWTF","sections":["SCHEDULE"],"supported":false,"summary":"This keyword activates the Non-Newtonian Fluid phase and model for when the polymer phase is present in the model, as indicated by the POLYMER keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"NTHRBL","description":"A positive integer that defines the maximum number of Herschel-Bulkley versus polymer concentration tables to be used with the polymer model, as entered via the FHERCHBL keyword in the PROPS section. The tables are allocated to different parts of the grid by the HBNUM keyword in the REGIONS section","units":{},"default":"NTPVT","value_type":"INT"},{"index":2,"name":"NLNHBL","description":"A positive integer that defines the maximum number of rows for each table entered by the FHERCHBL keyword in the PROPS section.","units":{},"default":"2","value_type":"INT"}],"example":"--\n-- MAX MAX\n-- NTHRBL NLNHBL\nNNEWTF\n3 5 /\nThe above example defines maximum number of Herschel-Bulkley tables to be three with a maximum number of rows for each table set to five.","expected_columns":2,"size_kind":"fixed","size_count":1},"NOCASC":{"name":"NOCASC","sections":["RUNSPEC"],"supported":null,"summary":"NOCASC keyword activates the linear solver tracer algorithm for single phase tracers.","parameters":[],"example":"--\n-- TRACER SOLVER OPTION\n--\nNOCASC\nThe above example switches on the linear solver tracer algorithm; however, this has no effect in OPM Flow input decks.","size_kind":"none","size_count":0},"NODPPM":{"name":"NODPPM","sections":["RUNSPEC","GRID"],"supported":false,"summary":"The NODPPM keyword deactivates the default behavior of multiplying the fracture porosity by the fracture permeability to calculate the effective fracture permeability in dual porosity and dual permeability runs. Either the DUALPORO or DUALPERM keywords in the RUNSPEC section must be declared in the input file in order to use this keyword. If the default calculation is switched off by this keyword, then the effective fracture permeability is taken to be those entered for the fracture using the PERMX, PERMY and PERMZ keywords in the GRID section. If the keyword is absent from the input deck, then the entered PERMX, PERMY and PERMZ arrays for the fractures are multiplied by fracture PORO array values in order to obtain the effective fracture permeability.","parameters":[],"example":"--\n-- DEACTIVATE FRACTURE POROSITY-PERMEABILITY CALCULATION\n--\nNODPPM\nThe above example switches off the default behavior of multiplying the fracture porosity by the fracture permeability to calculate the effective fracture permeability.","size_kind":"none","size_count":0},"NOECHO":{"name":"NOECHO","sections":["RUNSPEC","GRID","EDIT","PROPS","REGIONS","SOLUTION","SUMMARY","SCHEDULE"],"supported":null,"summary":"Turns off echoing of all the input files to the print file. Note by default echoing of the inputs files is active. but can subsequently be switched off by the NOECHO activation keyword.","parameters":[],"example":"","size_kind":"none","size_count":0},"NOHYST":{"name":"NOHYST","sections":["RUNSPEC"],"supported":false,"summary":"The NOHYST keyword deactivates the Hysteresis option and informs the simulator to ignore the IMBNUM array in the REGIONS section.","parameters":[],"example":"--\n-- DEACTIVATE THE HYSTERESIS OPTION\n--\nNOHYST\nThe above example switches off the default behavior of multiplying the fracture porosity by the fracture permeability to calculate the effective fracture permeability.","size_kind":"none","size_count":0},"NOINSPEC":{"name":"NOINSPEC","sections":["RUNSPEC"],"supported":null,"summary":"The NOINSPEC keyword deactivates the writing out of the INIT index file (*.INSPEC). The initialization data (or static data) is written out to two files one file contains the data, *.INIT, and the second file contains an index of the data (*.INSPEC) stored in the *.INIT file. This functionality is redundant as most post-processing software require the *.INSPEC file to load the *.INIT data set.","parameters":[],"example":"--\n-- DEACTIVATE OUTPUT OF THE INIT INDEX FILE *.INSPEC\n--\nNOINSPEC\nThe above example switches off the writing of the INIT index file (*.INSPEC); however, this has no effect in OPM Flow input decks.","size_kind":"none","size_count":0},"NOMONITO":{"name":"NOMONITO","sections":["RUNSPEC","SUMMARY"],"supported":null,"summary":"The NOMONITO keyword deactivates the writing out of the run time monitoring information used by post-processing graphics software to display run time information, for example the simulated production and injection rates and cumulative values. OPM Flow does not have this functionality.","parameters":[],"example":"--\n-- DEACTIVATE MONITORING OUTPUT DATA AND FILES\n--\nNOMONITO\nThe above example switches off the output required for run time monitoring required by post-processing graphics software to review the simulation results in real time as the run progresses; however, this has no effect in OPM Flow input decks.","size_kind":"none","size_count":0},"NONNC":{"name":"NONNC","sections":["RUNSPEC"],"supported":null,"summary":"The NONNC keyword deactivates non-neighbor connections (“NNCs”) in the current run. NNCs create off-diagonal elements in the Jacobi matrix that impact the numerical efficiency of the solution algorithms, and thus if the run does not contain NNCs then there is the potential for greater computation efficiency. Unfortunately, nearly all models, except for the most simple models, generate NNCs via for example:","parameters":[],"example":"--\n-- DEACTIVATE NON-NEIGHBOR CONNECTIONS\n--\nNONNC\nThe above example switches off the NNCs.","size_kind":"none","size_count":0},"NORSSPEC":{"name":"NORSSPEC","sections":["RUNSPEC"],"supported":null,"summary":"The NORSSPEC keyword deactivates the writing out of the RESTART index file (*.RSSPEC). The restart data (pressure, saturations etc. through time for each active cell) are written out to two files one file contains the data, *.UNRST for example, and the second file contains an index of the data (*.RSSPEC) stored in the *.UNRST file. This functionality is redundant as most post-processing software require the *.RSSPEC file to load the *.UNRST data set.","parameters":[],"example":"--\n-- DEACTIVATE OUTPUT OF THE RESTART INDEX FILE *.RSSPEC\n--\nNORSSPEC\nThe above example switches off the writing of the restart index file (*.RSSPEC); however, this has no effect in OPM Flow input decks.","size_kind":"none","size_count":0},"NOSIM":{"name":"NOSIM","sections":["RUNSPEC","SCHEDULE"],"supported":null,"summary":"NOSIM switches the mode of OPM Flow to data input checking mode. In this mode the input file is read and all messages and print instructions are sent to the respective output files. The SCHEDULE section is read but the simulation is not performed.","parameters":[],"example":"The example below switches OPM Flow to no simulation mode for data checking of the input deck.\n--\n-- SWITCH NO SIMULATION MODE FOR DATA CHECKING COMMENT OUT TO RUN THE MODEL\n--\nNOSIM\nAnd the next example shows how to commented out the NOSIM activation keyword so that the simulation will proceed.\n--\n-- SWITCH NO SIMULATION MODE FOR DATA CHECKING COMMENT OUT TO RUN THE MODEL\n--\n-- NOSIM\nNote\nSimulation input decks are complex and are therefore prone to typing errors, thus before submitting a run that will take over 15 minutes or so, it is a good idea to run the model with the NOSIM option. If no errors are found then the NOSIM keyword should be commented out by placing “--” before the keyword, and then re-running the model.\nAlternatively, one could use OPMRUN to run all the jobs in the queue in NOSIM mode and have the software re-run jobs in simulation mode if there are no errors.\n| Note Simulation input decks are complex and are therefore prone to typing errors, thus before submitting a run that will take over 15 minutes or so, it is a good idea to run the model with the NOSIM option. If no errors are found then the NOSIM keyword should be commented out by placing “--” before the keyword, and then re-running the model. Alternatively, one could use OPMRUN to run all the jobs in the queue in NOSIM mode and have the software re-run jobs in simulation mode if there are no errors. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"none","size_count":0},"NOWARN":{"name":"NOWARN","sections":["RUNSPEC","GRID","EDIT","PROPS","REGIONS","SOLUTION","SUMMARY","SCHEDULE"],"supported":null,"summary":"Turns off warning messages to be printed to the print file; note that this keyword is deactivated by default and can subsequently be switched off by the WARN activation keyword. The warning messages may be turned on and off using keywords WARN and NOWARN.","parameters":[],"example":"","size_kind":"none","size_count":0},"NRSOUT":{"name":"NRSOUT","sections":["RUNSPEC"],"supported":false,"summary":"The NRSOUT keyword specifies the maximum number of elements that can be written to the RESTART file at each reporting time step.","parameters":[{"index":1,"name":"NRSOUT","description":"A positive integer value that specifies the maximum number of elements that can be written to the RESTART file at each reporting time step.","units":{},"default":"3600","value_type":"INT"}],"example":"--\n-- MAX\n-- NRSOUT\nNRSOUT\n6000 /\nThe above example sets the maximum number of elements that can be written to the RESTART file at each reporting time step to 6000.","expected_columns":1,"size_kind":"fixed","size_count":1},"NSTACK":{"name":"NSTACK","sections":["RUNSPEC","SCHEDULE"],"supported":false,"summary":"The NSTACK keyword defines the maximum number of previous search directions stored by the linear solver. Increasing the value of NSTACK may improve the efficiency of the solver on difficult problems, but will increase the memory requirements of the simulator. The default value of 10 should be sufficient for most problems; however, if OPM Flow is having issues with the convergence of the linear questions then increasing NSTACK and the value of LITMAX on the TUNING keyword may improve performance.","parameters":[{"index":1,"name":"NSTACK","description":"A positive integer that defines the maximum number of previous search directions stored by the linear solver.","units":{},"default":"10","value_type":"INT"}],"example":"--\n-- SET STACK SIZE FOR LINEAR SOLVER\n--\nNSTACK\n30 /\nThe above example sets maximum number of previous search directions stored by the linear solver to 30, this has no effect in OPM Flow input decks.\nNote\nIf the run is suffering from linear convergence problems, then check the data first for any data issues before manipulating the numerical control parameters. For example, if OPM Flow has written some WARNING messages with respect to end-point scaling, etc., then resolve these messages first before adjusting the numerical controls.\n| Note If the run is suffering from linear convergence problems, then check the data first for any data issues before manipulating the numerical control parameters. For example, if OPM Flow has written some WARNING messages with respect to end-point scaling, etc., then resolve these messages first before adjusting the numerical controls. |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":1,"size_kind":"fixed","size_count":1},"NUMRES":{"name":"NUMRES","sections":["RUNSPEC"],"supported":null,"summary":"The NUMRES keyword defines the number of reservoir grids (COORD data sets) that the simulator should process. OPM Flow currently only supports a single reservoir grid.","parameters":[{"index":1,"name":"NUMRES","description":"A positive integer that defines the number of COORD data sets to be processed by OPM Flow. OPM Flow currently only supports a single reservoir grid and so this item should be defaulted (1*) or set to one.","units":{},"default":"1","value_type":"INT"}],"example":"--\n-- DEFINE THE NUMBER OF RESERVOIR GRIDS (COORD DATA SETS)\n--\nNUMRES\n1 /\nThe above example sets the maximum number of COORD data sets to be processed to one.","expected_columns":1,"size_kind":"fixed","size_count":1},"NUPCOL":{"name":"NUPCOL","sections":["RUNSPEC","SCHEDULE"],"supported":null,"summary":"The NUPCOL keyword defines the maximum number of Newton iterations within a time step that may be used to update the well production and injection targets, after which the well targets will be frozen until the time step calculations have converged and the time step is complete.","parameters":[{"index":1,"name":"NUPCOL","description":"A positive integer that defines the maximum number of Newton iterations used to update well targets within a time step.","units":{},"default":"3","value_type":"INT"}],"example":"--\n-- DEFINE THE MAX NUMBER OF ITERATIONS TO UPDATE WELL FLOW TARGETS\n--\nNUPCOL\n3 /\nThe above example sets the NUPCOL value to its default value of 3.","expected_columns":1,"size_kind":"fixed","size_count":1},"OIL":{"name":"OIL","sections":["RUNSPEC"],"supported":null,"summary":"This keyword indicates that the oil phase is present in the model and must be used for oil-gas, oil-water, oil-water-gas input decks that contain the oil phase. The keyword will also invoke data input file checking to ensure that all the required oil phase input parameters are defined in the input deck.","parameters":[],"example":"--\n-- OIL PHASE IS PRESENT IN THE RUN\n--\nOIL\nThe above example declares that the oil phase is active in the model.","size_kind":"none","size_count":0},"OPTIONS":{"name":"OPTIONS","sections":["RUNSPEC","SCHEDULE"],"supported":true,"summary":"The OPTIONS keyword activates various program options in the commercial simulator. Currently, none of the options available in the commercial simulator are implemented in OPM Flow, and it is unlikely that this keyword will be supported in the future releases of OPM Flow.","parameters":[{"index":1,"name":"ITEM1","description":"","units":{},"default":"0","value_type":"INT"},{"index":2,"name":"ITEM2","description":"","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"ITEM3","description":"","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"ITEM4","description":"","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"ITEM5","description":"","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"ITEM6","description":"","units":{},"default":"0","value_type":"INT"},{"index":7,"name":"ITEM7","description":"","units":{},"default":"0","value_type":"INT"},{"index":8,"name":"ITEM8","description":"","units":{},"default":"0","value_type":"INT"},{"index":9,"name":"ITEM9","description":"","units":{},"default":"0","value_type":"INT"},{"index":10,"name":"ITEM10","description":"","units":{},"default":"0","value_type":"INT"},{"index":11,"name":"ITEM11","description":"","units":{},"default":"0","value_type":"INT"},{"index":12,"name":"ITEM12","description":"","units":{},"default":"0","value_type":"INT"},{"index":13,"name":"ITEM13","description":"","units":{},"default":"0","value_type":"INT"},{"index":14,"name":"ITEM14","description":"","units":{},"default":"0","value_type":"INT"},{"index":15,"name":"ITEM15","description":"","units":{},"default":"0","value_type":"INT"},{"index":16,"name":"ITEM16","description":"","units":{},"default":"0","value_type":"INT"},{"index":17,"name":"ITEM17","description":"","units":{},"default":"0","value_type":"INT"},{"index":18,"name":"ITEM18","description":"","units":{},"default":"0","value_type":"INT"},{"index":19,"name":"ITEM19","description":"","units":{},"default":"0","value_type":"INT"},{"index":20,"name":"ITEM20","description":"","units":{},"default":"0","value_type":"INT"},{"index":21,"name":"ITEM21","description":"","units":{},"default":"0","value_type":"INT"},{"index":22,"name":"ITEM22","description":"","units":{},"default":"0","value_type":"INT"},{"index":23,"name":"ITEM23","description":"","units":{},"default":"0","value_type":"INT"},{"index":24,"name":"ITEM24","description":"","units":{},"default":"0","value_type":"INT"},{"index":25,"name":"ITEM25","description":"","units":{},"default":"0","value_type":"INT"},{"index":26,"name":"ITEM26","description":"","units":{},"default":"0","value_type":"INT"},{"index":27,"name":"ITEM27","description":"","units":{},"default":"0","value_type":"INT"},{"index":28,"name":"ITEM28","description":"","units":{},"default":"0","value_type":"INT"},{"index":29,"name":"ITEM29","description":"","units":{},"default":"0","value_type":"INT"},{"index":30,"name":"ITEM30","description":"","units":{},"default":"0","value_type":"INT"},{"index":31,"name":"ITEM31","description":"","units":{},"default":"0","value_type":"INT"},{"index":32,"name":"ITEM32","description":"","units":{},"default":"0","value_type":"INT"},{"index":33,"name":"ITEM33","description":"","units":{},"default":"0","value_type":"INT"},{"index":34,"name":"ITEM34","description":"","units":{},"default":"0","value_type":"INT"},{"index":35,"name":"ITEM35","description":"","units":{},"default":"0","value_type":"INT"},{"index":36,"name":"ITEM36","description":"","units":{},"default":"0","value_type":"INT"},{"index":37,"name":"ITEM37","description":"","units":{},"default":"0","value_type":"INT"},{"index":38,"name":"ITEM38","description":"","units":{},"default":"0","value_type":"INT"},{"index":39,"name":"ITEM39","description":"","units":{},"default":"0","value_type":"INT"},{"index":40,"name":"ITEM40","description":"","units":{},"default":"0","value_type":"INT"},{"index":41,"name":"ITEM41","description":"","units":{},"default":"0","value_type":"INT"},{"index":42,"name":"ITEM42","description":"","units":{},"default":"0","value_type":"INT"},{"index":43,"name":"ITEM43","description":"","units":{},"default":"0","value_type":"INT"},{"index":44,"name":"ITEM44","description":"","units":{},"default":"0","value_type":"INT"},{"index":45,"name":"ITEM45","description":"","units":{},"default":"0","value_type":"INT"},{"index":46,"name":"ITEM46","description":"","units":{},"default":"0","value_type":"INT"},{"index":47,"name":"ITEM47","description":"","units":{},"default":"0","value_type":"INT"},{"index":48,"name":"ITEM48","description":"","units":{},"default":"0","value_type":"INT"},{"index":49,"name":"ITEM49","description":"","units":{},"default":"0","value_type":"INT"},{"index":50,"name":"ITEM50","description":"","units":{},"default":"0","value_type":"INT"},{"index":51,"name":"ITEM51","description":"","units":{},"default":"0","value_type":"INT"},{"index":52,"name":"ITEM52","description":"","units":{},"default":"0","value_type":"INT"},{"index":53,"name":"ITEM53","description":"","units":{},"default":"0","value_type":"INT"},{"index":54,"name":"ITEM54","description":"","units":{},"default":"0","value_type":"INT"},{"index":55,"name":"ITEM55","description":"","units":{},"default":"0","value_type":"INT"},{"index":56,"name":"ITEM56","description":"","units":{},"default":"0","value_type":"INT"},{"index":57,"name":"ITEM57","description":"","units":{},"default":"0","value_type":"INT"},{"index":58,"name":"ITEM58","description":"","units":{},"default":"0","value_type":"INT"},{"index":59,"name":"ITEM59","description":"","units":{},"default":"0","value_type":"INT"},{"index":60,"name":"ITEM60","description":"","units":{},"default":"0","value_type":"INT"},{"index":61,"name":"ITEM61","description":"","units":{},"default":"0","value_type":"INT"},{"index":62,"name":"ITEM62","description":"","units":{},"default":"0","value_type":"INT"},{"index":63,"name":"ITEM63","description":"","units":{},"default":"0","value_type":"INT"},{"index":64,"name":"ITEM64","description":"","units":{},"default":"0","value_type":"INT"},{"index":65,"name":"ITEM65","description":"","units":{},"default":"0","value_type":"INT"},{"index":66,"name":"ITEM66","description":"","units":{},"default":"0","value_type":"INT"},{"index":67,"name":"ITEM67","description":"","units":{},"default":"0","value_type":"INT"},{"index":68,"name":"ITEM68","description":"","units":{},"default":"0","value_type":"INT"},{"index":69,"name":"ITEM69","description":"","units":{},"default":"0","value_type":"INT"},{"index":70,"name":"ITEM70","description":"","units":{},"default":"0","value_type":"INT"},{"index":71,"name":"ITEM71","description":"","units":{},"default":"0","value_type":"INT"},{"index":72,"name":"ITEM72","description":"","units":{},"default":"0","value_type":"INT"},{"index":73,"name":"ITEM73","description":"","units":{},"default":"0","value_type":"INT"},{"index":74,"name":"ITEM74","description":"","units":{},"default":"0","value_type":"INT"},{"index":75,"name":"ITEM75","description":"","units":{},"default":"0","value_type":"INT"},{"index":76,"name":"ITEM76","description":"","units":{},"default":"0","value_type":"INT"},{"index":77,"name":"ITEM77","description":"","units":{},"default":"0","value_type":"INT"},{"index":78,"name":"ITEM78","description":"","units":{},"default":"0","value_type":"INT"},{"index":79,"name":"ITEM79","description":"","units":{},"default":"0","value_type":"INT"},{"index":80,"name":"ITEM80","description":"","units":{},"default":"0","value_type":"INT"},{"index":81,"name":"ITEM81","description":"","units":{},"default":"0","value_type":"INT"},{"index":82,"name":"ITEM82","description":"","units":{},"default":"0","value_type":"INT"},{"index":83,"name":"ITEM83","description":"","units":{},"default":"0","value_type":"INT"},{"index":84,"name":"ITEM84","description":"","units":{},"default":"0","value_type":"INT"},{"index":85,"name":"ITEM85","description":"","units":{},"default":"0","value_type":"INT"},{"index":86,"name":"ITEM86","description":"","units":{},"default":"0","value_type":"INT"},{"index":87,"name":"ITEM87","description":"","units":{},"default":"0","value_type":"INT"},{"index":88,"name":"ITEM88","description":"","units":{},"default":"0","value_type":"INT"},{"index":89,"name":"ITEM89","description":"","units":{},"default":"0","value_type":"INT"},{"index":90,"name":"ITEM90","description":"","units":{},"default":"0","value_type":"INT"},{"index":91,"name":"ITEM91","description":"","units":{},"default":"0","value_type":"INT"},{"index":92,"name":"ITEM92","description":"","units":{},"default":"0","value_type":"INT"},{"index":93,"name":"ITEM93","description":"","units":{},"default":"0","value_type":"INT"},{"index":94,"name":"ITEM94","description":"","units":{},"default":"0","value_type":"INT"},{"index":95,"name":"ITEM95","description":"","units":{},"default":"0","value_type":"INT"},{"index":96,"name":"ITEM96","description":"","units":{},"default":"0","value_type":"INT"},{"index":97,"name":"ITEM97","description":"","units":{},"default":"0","value_type":"INT"},{"index":98,"name":"ITEM98","description":"","units":{},"default":"0","value_type":"INT"},{"index":99,"name":"ITEM99","description":"","units":{},"default":"0","value_type":"INT"},{"index":100,"name":"ITEM100","description":"","units":{},"default":"0","value_type":"INT"},{"index":101,"name":"ITEM101","description":"","units":{},"default":"0","value_type":"INT"},{"index":102,"name":"ITEM102","description":"","units":{},"default":"0","value_type":"INT"},{"index":103,"name":"ITEM103","description":"","units":{},"default":"0","value_type":"INT"},{"index":104,"name":"ITEM104","description":"","units":{},"default":"0","value_type":"INT"},{"index":105,"name":"ITEM105","description":"","units":{},"default":"0","value_type":"INT"},{"index":106,"name":"ITEM106","description":"","units":{},"default":"0","value_type":"INT"},{"index":107,"name":"ITEM107","description":"","units":{},"default":"0","value_type":"INT"},{"index":108,"name":"ITEM108","description":"","units":{},"default":"0","value_type":"INT"},{"index":109,"name":"ITEM109","description":"","units":{},"default":"0","value_type":"INT"},{"index":110,"name":"ITEM110","description":"","units":{},"default":"0","value_type":"INT"},{"index":111,"name":"ITEM111","description":"","units":{},"default":"0","value_type":"INT"},{"index":112,"name":"ITEM112","description":"","units":{},"default":"0","value_type":"INT"},{"index":113,"name":"ITEM113","description":"","units":{},"default":"0","value_type":"INT"},{"index":114,"name":"ITEM114","description":"","units":{},"default":"0","value_type":"INT"},{"index":115,"name":"ITEM115","description":"","units":{},"default":"0","value_type":"INT"},{"index":116,"name":"ITEM116","description":"","units":{},"default":"0","value_type":"INT"},{"index":117,"name":"ITEM117","description":"","units":{},"default":"0","value_type":"INT"},{"index":118,"name":"ITEM118","description":"","units":{},"default":"0","value_type":"INT"},{"index":119,"name":"ITEM119","description":"","units":{},"default":"0","value_type":"INT"},{"index":120,"name":"ITEM120","description":"","units":{},"default":"0","value_type":"INT"},{"index":121,"name":"ITEM121","description":"","units":{},"default":"0","value_type":"INT"},{"index":122,"name":"ITEM122","description":"","units":{},"default":"0","value_type":"INT"},{"index":123,"name":"ITEM123","description":"","units":{},"default":"0","value_type":"INT"},{"index":124,"name":"ITEM124","description":"","units":{},"default":"0","value_type":"INT"},{"index":125,"name":"ITEM125","description":"","units":{},"default":"0","value_type":"INT"},{"index":126,"name":"ITEM126","description":"","units":{},"default":"0","value_type":"INT"},{"index":127,"name":"ITEM127","description":"","units":{},"default":"0","value_type":"INT"},{"index":128,"name":"ITEM128","description":"","units":{},"default":"0","value_type":"INT"},{"index":129,"name":"ITEM129","description":"","units":{},"default":"0","value_type":"INT"},{"index":130,"name":"ITEM130","description":"","units":{},"default":"0","value_type":"INT"},{"index":131,"name":"ITEM131","description":"","units":{},"default":"0","value_type":"INT"},{"index":132,"name":"ITEM132","description":"","units":{},"default":"0","value_type":"INT"},{"index":133,"name":"ITEM133","description":"","units":{},"default":"0","value_type":"INT"},{"index":134,"name":"ITEM134","description":"","units":{},"default":"0","value_type":"INT"},{"index":135,"name":"ITEM135","description":"","units":{},"default":"0","value_type":"INT"},{"index":136,"name":"ITEM136","description":"","units":{},"default":"0","value_type":"INT"},{"index":137,"name":"ITEM137","description":"","units":{},"default":"0","value_type":"INT"},{"index":138,"name":"ITEM138","description":"","units":{},"default":"0","value_type":"INT"},{"index":139,"name":"ITEM139","description":"","units":{},"default":"0","value_type":"INT"},{"index":140,"name":"ITEM140","description":"","units":{},"default":"0","value_type":"INT"},{"index":141,"name":"ITEM141","description":"","units":{},"default":"0","value_type":"INT"},{"index":142,"name":"ITEM142","description":"","units":{},"default":"0","value_type":"INT"},{"index":143,"name":"ITEM143","description":"","units":{},"default":"0","value_type":"INT"},{"index":144,"name":"ITEM144","description":"","units":{},"default":"0","value_type":"INT"},{"index":145,"name":"ITEM145","description":"","units":{},"default":"0","value_type":"INT"},{"index":146,"name":"ITEM146","description":"","units":{},"default":"0","value_type":"INT"},{"index":147,"name":"ITEM147","description":"","units":{},"default":"0","value_type":"INT"},{"index":148,"name":"ITEM148","description":"","units":{},"default":"0","value_type":"INT"},{"index":149,"name":"ITEM149","description":"","units":{},"default":"0","value_type":"INT"},{"index":150,"name":"ITEM150","description":"","units":{},"default":"0","value_type":"INT"},{"index":151,"name":"ITEM151","description":"","units":{},"default":"0","value_type":"INT"},{"index":152,"name":"ITEM152","description":"","units":{},"default":"0","value_type":"INT"},{"index":153,"name":"ITEM153","description":"","units":{},"default":"0","value_type":"INT"},{"index":154,"name":"ITEM154","description":"","units":{},"default":"0","value_type":"INT"},{"index":155,"name":"ITEM155","description":"","units":{},"default":"0","value_type":"INT"},{"index":156,"name":"ITEM156","description":"","units":{},"default":"0","value_type":"INT"},{"index":157,"name":"ITEM157","description":"","units":{},"default":"0","value_type":"INT"},{"index":158,"name":"ITEM158","description":"","units":{},"default":"0","value_type":"INT"},{"index":159,"name":"ITEM159","description":"","units":{},"default":"0","value_type":"INT"},{"index":160,"name":"ITEM160","description":"","units":{},"default":"0","value_type":"INT"},{"index":161,"name":"ITEM161","description":"","units":{},"default":"0","value_type":"INT"},{"index":162,"name":"ITEM162","description":"","units":{},"default":"0","value_type":"INT"},{"index":163,"name":"ITEM163","description":"","units":{},"default":"0","value_type":"INT"},{"index":164,"name":"ITEM164","description":"","units":{},"default":"0","value_type":"INT"},{"index":165,"name":"ITEM165","description":"","units":{},"default":"0","value_type":"INT"},{"index":166,"name":"ITEM166","description":"","units":{},"default":"0","value_type":"INT"},{"index":167,"name":"ITEM167","description":"","units":{},"default":"0","value_type":"INT"},{"index":168,"name":"ITEM168","description":"","units":{},"default":"0","value_type":"INT"},{"index":169,"name":"ITEM169","description":"","units":{},"default":"0","value_type":"INT"},{"index":170,"name":"ITEM170","description":"","units":{},"default":"0","value_type":"INT"},{"index":171,"name":"ITEM171","description":"","units":{},"default":"0","value_type":"INT"},{"index":172,"name":"ITEM172","description":"","units":{},"default":"0","value_type":"INT"},{"index":173,"name":"ITEM173","description":"","units":{},"default":"0","value_type":"INT"},{"index":174,"name":"ITEM174","description":"","units":{},"default":"0","value_type":"INT"},{"index":175,"name":"ITEM175","description":"","units":{},"default":"0","value_type":"INT"},{"index":176,"name":"ITEM176","description":"","units":{},"default":"0","value_type":"INT"},{"index":177,"name":"ITEM177","description":"","units":{},"default":"0","value_type":"INT"},{"index":178,"name":"ITEM178","description":"","units":{},"default":"0","value_type":"INT"},{"index":179,"name":"ITEM179","description":"","units":{},"default":"0","value_type":"INT"},{"index":180,"name":"ITEM180","description":"","units":{},"default":"0","value_type":"INT"},{"index":181,"name":"ITEM181","description":"","units":{},"default":"0","value_type":"INT"},{"index":182,"name":"ITEM182","description":"","units":{},"default":"0","value_type":"INT"},{"index":183,"name":"ITEM183","description":"","units":{},"default":"0","value_type":"INT"},{"index":184,"name":"ITEM184","description":"","units":{},"default":"0","value_type":"INT"},{"index":185,"name":"ITEM185","description":"","units":{},"default":"0","value_type":"INT"},{"index":186,"name":"ITEM186","description":"","units":{},"default":"0","value_type":"INT"},{"index":187,"name":"ITEM187","description":"","units":{},"default":"0","value_type":"INT"},{"index":188,"name":"ITEM188","description":"","units":{},"default":"0","value_type":"INT"},{"index":189,"name":"ITEM189","description":"","units":{},"default":"0","value_type":"INT"},{"index":190,"name":"ITEM190","description":"","units":{},"default":"0","value_type":"INT"},{"index":191,"name":"ITEM191","description":"","units":{},"default":"0","value_type":"INT"},{"index":192,"name":"ITEM192","description":"","units":{},"default":"0","value_type":"INT"},{"index":193,"name":"ITEM193","description":"","units":{},"default":"0","value_type":"INT"},{"index":194,"name":"ITEM194","description":"","units":{},"default":"0","value_type":"INT"},{"index":195,"name":"ITEM195","description":"","units":{},"default":"0","value_type":"INT"},{"index":196,"name":"ITEM196","description":"","units":{},"default":"0","value_type":"INT"},{"index":197,"name":"ITEM197","description":"","units":{},"default":"0","value_type":"INT"},{"index":198,"name":"ITEM198","description":"","units":{},"default":"0","value_type":"INT"},{"index":199,"name":"ITEM199","description":"","units":{},"default":"0","value_type":"INT"},{"index":200,"name":"ITEM200","description":"","units":{},"default":"0","value_type":"INT"},{"index":201,"name":"ITEM201","description":"","units":{},"default":"0","value_type":"INT"},{"index":202,"name":"ITEM202","description":"","units":{},"default":"0","value_type":"INT"},{"index":203,"name":"ITEM203","description":"","units":{},"default":"0","value_type":"INT"},{"index":204,"name":"ITEM204","description":"","units":{},"default":"0","value_type":"INT"},{"index":205,"name":"ITEM205","description":"","units":{},"default":"0","value_type":"INT"},{"index":206,"name":"ITEM206","description":"","units":{},"default":"0","value_type":"INT"},{"index":207,"name":"ITEM207","description":"","units":{},"default":"0","value_type":"INT"},{"index":208,"name":"ITEM208","description":"","units":{},"default":"0","value_type":"INT"},{"index":209,"name":"ITEM209","description":"","units":{},"default":"0","value_type":"INT"},{"index":210,"name":"ITEM210","description":"","units":{},"default":"0","value_type":"INT"},{"index":211,"name":"ITEM211","description":"","units":{},"default":"0","value_type":"INT"},{"index":212,"name":"ITEM212","description":"","units":{},"default":"0","value_type":"INT"},{"index":213,"name":"ITEM213","description":"","units":{},"default":"0","value_type":"INT"},{"index":214,"name":"ITEM214","description":"","units":{},"default":"0","value_type":"INT"},{"index":215,"name":"ITEM215","description":"","units":{},"default":"0","value_type":"INT"},{"index":216,"name":"ITEM216","description":"","units":{},"default":"0","value_type":"INT"},{"index":217,"name":"ITEM217","description":"","units":{},"default":"0","value_type":"INT"},{"index":218,"name":"ITEM218","description":"","units":{},"default":"0","value_type":"INT"},{"index":219,"name":"ITEM219","description":"","units":{},"default":"0","value_type":"INT"},{"index":220,"name":"ITEM220","description":"","units":{},"default":"0","value_type":"INT"},{"index":221,"name":"ITEM221","description":"","units":{},"default":"0","value_type":"INT"},{"index":222,"name":"ITEM222","description":"","units":{},"default":"0","value_type":"INT"},{"index":223,"name":"ITEM223","description":"","units":{},"default":"0","value_type":"INT"},{"index":224,"name":"ITEM224","description":"","units":{},"default":"0","value_type":"INT"},{"index":225,"name":"ITEM225","description":"","units":{},"default":"0","value_type":"INT"},{"index":226,"name":"ITEM226","description":"","units":{},"default":"0","value_type":"INT"},{"index":227,"name":"ITEM227","description":"","units":{},"default":"0","value_type":"INT"},{"index":228,"name":"ITEM228","description":"","units":{},"default":"0","value_type":"INT"},{"index":229,"name":"ITEM229","description":"","units":{},"default":"0","value_type":"INT"},{"index":230,"name":"ITEM230","description":"","units":{},"default":"0","value_type":"INT"},{"index":231,"name":"ITEM231","description":"","units":{},"default":"0","value_type":"INT"},{"index":232,"name":"ITEM232","description":"","units":{},"default":"0","value_type":"INT"},{"index":233,"name":"ITEM233","description":"","units":{},"default":"0","value_type":"INT"},{"index":234,"name":"ITEM234","description":"","units":{},"default":"0","value_type":"INT"},{"index":235,"name":"ITEM235","description":"","units":{},"default":"0","value_type":"INT"},{"index":236,"name":"ITEM236","description":"","units":{},"default":"0","value_type":"INT"},{"index":237,"name":"ITEM237","description":"","units":{},"default":"0","value_type":"INT"},{"index":238,"name":"ITEM238","description":"","units":{},"default":"0","value_type":"INT"},{"index":239,"name":"ITEM239","description":"","units":{},"default":"0","value_type":"INT"},{"index":240,"name":"ITEM240","description":"","units":{},"default":"0","value_type":"INT"},{"index":241,"name":"ITEM241","description":"","units":{},"default":"0","value_type":"INT"},{"index":242,"name":"ITEM242","description":"","units":{},"default":"0","value_type":"INT"},{"index":243,"name":"ITEM243","description":"","units":{},"default":"0","value_type":"INT"},{"index":244,"name":"ITEM244","description":"","units":{},"default":"0","value_type":"INT"},{"index":245,"name":"ITEM245","description":"","units":{},"default":"0","value_type":"INT"},{"index":246,"name":"ITEM246","description":"","units":{},"default":"0","value_type":"INT"},{"index":247,"name":"ITEM247","description":"","units":{},"default":"0","value_type":"INT"},{"index":248,"name":"ITEM248","description":"","units":{},"default":"0","value_type":"INT"},{"index":249,"name":"ITEM249","description":"","units":{},"default":"0","value_type":"INT"},{"index":250,"name":"ITEM250","description":"","units":{},"default":"0","value_type":"INT"},{"index":251,"name":"ITEM251","description":"","units":{},"default":"0","value_type":"INT"},{"index":252,"name":"ITEM252","description":"","units":{},"default":"0","value_type":"INT"},{"index":253,"name":"ITEM253","description":"","units":{},"default":"0","value_type":"INT"},{"index":254,"name":"ITEM254","description":"","units":{},"default":"0","value_type":"INT"},{"index":255,"name":"ITEM255","description":"","units":{},"default":"0","value_type":"INT"},{"index":256,"name":"ITEM256","description":"","units":{},"default":"0","value_type":"INT"},{"index":257,"name":"ITEM257","description":"","units":{},"default":"0","value_type":"INT"},{"index":258,"name":"ITEM258","description":"","units":{},"default":"0","value_type":"INT"},{"index":259,"name":"ITEM259","description":"","units":{},"default":"0","value_type":"INT"},{"index":260,"name":"ITEM260","description":"","units":{},"default":"0","value_type":"INT"},{"index":261,"name":"ITEM261","description":"","units":{},"default":"0","value_type":"INT"},{"index":262,"name":"ITEM262","description":"","units":{},"default":"0","value_type":"INT"},{"index":263,"name":"ITEM263","description":"","units":{},"default":"0","value_type":"INT"},{"index":264,"name":"ITEM264","description":"","units":{},"default":"0","value_type":"INT"},{"index":265,"name":"ITEM265","description":"","units":{},"default":"0","value_type":"INT"},{"index":266,"name":"ITEM266","description":"","units":{},"default":"0","value_type":"INT"},{"index":267,"name":"ITEM267","description":"","units":{},"default":"0","value_type":"INT"},{"index":268,"name":"ITEM268","description":"","units":{},"default":"0","value_type":"INT"},{"index":269,"name":"ITEM269","description":"","units":{},"default":"0","value_type":"INT"},{"index":270,"name":"ITEM270","description":"","units":{},"default":"0","value_type":"INT"},{"index":271,"name":"ITEM271","description":"","units":{},"default":"0","value_type":"INT"},{"index":272,"name":"ITEM272","description":"","units":{},"default":"0","value_type":"INT"},{"index":273,"name":"ITEM273","description":"","units":{},"default":"0","value_type":"INT"},{"index":274,"name":"ITEM274","description":"","units":{},"default":"0","value_type":"INT"},{"index":275,"name":"ITEM275","description":"","units":{},"default":"0","value_type":"INT"},{"index":276,"name":"ITEM276","description":"","units":{},"default":"0","value_type":"INT"},{"index":277,"name":"ITEM277","description":"","units":{},"default":"0","value_type":"INT"},{"index":278,"name":"ITEM278","description":"","units":{},"default":"0","value_type":"INT"},{"index":279,"name":"ITEM279","description":"","units":{},"default":"0","value_type":"INT"},{"index":280,"name":"ITEM280","description":"","units":{},"default":"0","value_type":"INT"},{"index":281,"name":"ITEM281","description":"","units":{},"default":"0","value_type":"INT"},{"index":282,"name":"ITEM282","description":"","units":{},"default":"0","value_type":"INT"},{"index":283,"name":"ITEM283","description":"","units":{},"default":"0","value_type":"INT"},{"index":284,"name":"ITEM284","description":"","units":{},"default":"0","value_type":"INT"},{"index":285,"name":"ITEM285","description":"","units":{},"default":"0","value_type":"INT"},{"index":286,"name":"ITEM286","description":"","units":{},"default":"0","value_type":"INT"},{"index":287,"name":"ITEM287","description":"","units":{},"default":"0","value_type":"INT"},{"index":288,"name":"ITEM288","description":"","units":{},"default":"0","value_type":"INT"},{"index":289,"name":"ITEM289","description":"","units":{},"default":"0","value_type":"INT"},{"index":290,"name":"ITEM290","description":"","units":{},"default":"0","value_type":"INT"},{"index":291,"name":"ITEM291","description":"","units":{},"default":"0","value_type":"INT"},{"index":292,"name":"ITEM292","description":"","units":{},"default":"0","value_type":"INT"},{"index":293,"name":"ITEM293","description":"","units":{},"default":"0","value_type":"INT"},{"index":294,"name":"ITEM294","description":"","units":{},"default":"0","value_type":"INT"},{"index":295,"name":"ITEM295","description":"","units":{},"default":"0","value_type":"INT"},{"index":296,"name":"ITEM296","description":"","units":{},"default":"0","value_type":"INT"},{"index":297,"name":"ITEM297","description":"","units":{},"default":"0","value_type":"INT"},{"index":298,"name":"ITEM298","description":"","units":{},"default":"0","value_type":"INT"},{"index":299,"name":"ITEM299","description":"","units":{},"default":"0","value_type":"INT"},{"index":300,"name":"ITEM300","description":"","units":{},"default":"0","value_type":"INT"},{"index":301,"name":"ITEM301","description":"","units":{},"default":"0","value_type":"INT"},{"index":302,"name":"ITEM302","description":"","units":{},"default":"0","value_type":"INT"},{"index":303,"name":"ITEM303","description":"","units":{},"default":"0","value_type":"INT"},{"index":304,"name":"ITEM304","description":"","units":{},"default":"0","value_type":"INT"},{"index":305,"name":"ITEM305","description":"","units":{},"default":"0","value_type":"INT"},{"index":306,"name":"ITEM306","description":"","units":{},"default":"0","value_type":"INT"},{"index":307,"name":"ITEM307","description":"","units":{},"default":"0","value_type":"INT"},{"index":308,"name":"ITEM308","description":"","units":{},"default":"0","value_type":"INT"},{"index":309,"name":"ITEM309","description":"","units":{},"default":"0","value_type":"INT"},{"index":310,"name":"ITEM310","description":"","units":{},"default":"0","value_type":"INT"},{"index":311,"name":"ITEM311","description":"","units":{},"default":"0","value_type":"INT"},{"index":312,"name":"ITEM312","description":"","units":{},"default":"0","value_type":"INT"},{"index":313,"name":"ITEM313","description":"","units":{},"default":"0","value_type":"INT"},{"index":314,"name":"ITEM314","description":"","units":{},"default":"0","value_type":"INT"},{"index":315,"name":"ITEM315","description":"","units":{},"default":"0","value_type":"INT"},{"index":316,"name":"ITEM316","description":"","units":{},"default":"0","value_type":"INT"},{"index":317,"name":"ITEM317","description":"","units":{},"default":"0","value_type":"INT"},{"index":318,"name":"ITEM318","description":"","units":{},"default":"0","value_type":"INT"},{"index":319,"name":"ITEM319","description":"","units":{},"default":"0","value_type":"INT"}],"example":"--\n-- SKIP ACTIVATE\n-- OPTIONS OPTION\nOPTIONS\n77*0 1 /\nThe above example activates the use of scratch files for pre-processing grid geometry data for non-neighbor connections. Note if multiple options are required then one can just repeat the format of the example to activate multiple options as the keyword does not overwrite previous entries. So for example:\n--\n-- SKIP ACTIVATE\n-- OPTIONS OPTION\nOPTIONS\n7*0 1 /\n--\n-- SKIP ACTIVATE\n-- OPTIONS OPTION\nOPTIONS\n77*0 1 /\n--\n-- SKIP ACTIVATE\n-- OPTIONS OPTION\nOPTIONS\n177*0 1 /\nCould be used to activate the 8, 78 and 178 options if they were available.","expected_columns":319,"size_kind":"fixed","size_count":1},"PARALLEL":{"name":"PARALLEL","sections":["RUNSPEC"],"supported":null,"summary":"The PARALLEL keyword defines the run to use parallel processing and sets the domain decomposition options. See section 2.2Running OPM Flow 2023-04 From The Command Lineon how to run OPM Flow in parallel mode.","parameters":[{"index":1,"name":"NPROCS","description":"A positive integer that defines the number of domains or parallel processors to use for this run.","units":{},"default":"1","value_type":"INT"},{"index":2,"name":"RTYPE","description":"A character string set to either SERIAL to run the parallel code in serial mode for testing the code, or DISTRIBUTED to full utilize parallel processing.","units":{},"default":"DISTRIBUTED","value_type":"STRING"}],"example":"--\n-- PARALLEL MULTI-CORE OPTIONS\n-- NDMAIN MACHINE TYPE\nPARALLEL\n2 DISTRIBUTED /\nThe above example sets the number of domains (or processors) to two and for the simulation to run in parallel mode. This has no effect in OPM Flow input decks.","expected_columns":2,"size_kind":"fixed","size_count":1},"PARTTRAC":{"name":"PARTTRAC","sections":["RUNSPEC"],"supported":false,"summary":"The PARTTRAC keyword activates the Partitioned Tracer option and defines the maximum number of partitioned tracers, the number of TRACERKP or TRACERKM partitioning tables in the PROPS section, and the maximum number of number of rows in the TRACERKP or TRACERKM partitioning tables.","parameters":[{"index":1,"name":"NPARTT","description":"","units":{},"default":"0","value_type":"INT"},{"index":2,"name":"NKPTMX","description":"","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"NPKPMX","description":"","units":{},"default":"0","value_type":"INT"}],"example":"","expected_columns":3,"size_kind":"fixed","size_count":1},"PATHS":{"name":"PATHS","sections":["RUNSPEC"],"supported":null,"summary":"PATHS allows the user to define alias directory filenames to avoid long filenames with the INCLUDE, IMPORT, RESTART or GDFILE keywords. To use the alias with the aforementioned keywords PATHS should be prefixed with the $ symbol.","parameters":[{"index":1,"name":"ALIAS","description":"A character string enclosed in quotes defining the alias.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"DIRC","description":"A character string enclosed in quotes defining the directory filename.","units":{},"default":"None","value_type":"STRING"}],"example":"--\n-- PATH PATH\n-- ALIAS DIRECTORY FILENAME\nPATHS\n'GRID' '/DISK1/NORNE/2017/GRID-INCLUDES' /\n'SCHD' '/DISK1/NORNE/2017/SCHD-INCLUDES' /\n/\nThe above example defines “GRID” and “SCHD” aliases in the RUNSPEC section than can be used in the GRID and SCHEDULE sections of the input deck. The next example shows how to use the “GRID” alias with the INCLUDE keyword in the GRID section.\n--\n-- LOAD INCLUDE FILES\n--\nINCLUDE\n'$GRID/PORO.INC' /\nINCLUDE\n'$GRID/PERMX.INC' /\nINCLUDE\n'$GRID/NTG.INC' /\nHere the porosity, permeability and net-to-gross arrays are loaded in the GRID section using the directory filename aliases declared in the RUNSPEC section.","expected_columns":2,"size_kind":"list"},"PEDIMS":{"name":"PEDIMS","sections":["RUNSPEC"],"supported":false,"summary":"The PEDIMS keyword defines the number of petro-elastic regions to be used with the PENUM keyword in the REGIONS section and the number of rows in the PEGTAB0 to PEGTAB7 keywords, as well as the number of rows in the PEKTAB0 to PEKTAB7 keywords in the PROPS section.","parameters":[{"index":1,"name":"NUM_REGIONS","description":"","units":{},"default":"0","value_type":"INT"},{"index":2,"name":"MAX_PRESSURE_POINTS","description":"","units":{},"default":"0","value_type":"INT"}],"example":"","expected_columns":2,"size_kind":"fixed","size_count":1},"PETOPTS":{"name":"PETOPTS","sections":["RUNSPEC"],"supported":false,"summary":"The PETOPTS keyword defines various Petrel and Generic Simulation (*.GSG) file options.","parameters":[{"index":1,"name":"OPTIONS","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","size_kind":"fixed","size_count":1,"variadic_record":true},"PIMTDIMS":{"name":"PIMTDIMS","sections":["RUNSPEC"],"supported":null,"summary":"PIMTDIMS keyword defines the maximum number of PIMULTAB tables and the maximum number of entries (or rows) per PIMULTAB table. The PIMULTAB keyword is used to define a well’s productivity index factor as a function of a well’s producing water cut.","parameters":[{"index":1,"name":"NTPIMT","description":"A positive integer value that defines the maximum number of PIMULTAB keywords defined in the input deck.","units":{},"default":"0","value_type":"INT"},{"index":2,"name":"NRPIMT","description":"A positive integer value defining the maximum number of entries (rows) in the PIMULTAB keyword.","units":{},"default":"0","value_type":"INT"}],"example":"--\n-- MAX MAX\n-- TABLES ENTRIES\nPIMTDIMS\n1 51 /\nThe above example defines that there is one PIMULTAB table with a maximum number of 51 rows.","expected_columns":2,"size_kind":"fixed","size_count":1},"PINTDIMS":{"name":"PINTDIMS","sections":["RUNSPEC"],"supported":null,"summary":"The PINTDIMS keyword defines the number of property tables used in the OPM Flow's Polymer Molecular Weight Transport option, that uses the polymer molecular weight in calculating the polymer viscosity, as well as accounting for formation damage due to the water and polymer injection, by adjusting the wellbore skin pressure. This keyword should only be used if the POLYMER and POLYMW keywords in the RUNSPEC section are also activated. The PINTDIMS keyword defines the maximum number of tables for the SKPRWAT, SKPRPOLY, and PLYMWINJ keywords, and the number of entries in the PLYVMH keyword. All the aforementioned keywords are in the PROPS section.","parameters":[{"index":1,"name":"NTSKWAT","description":"NTSKWAT is a positive integer that defines the number of SKPRWAT tables in the PROPS section, used to describe the relationship of wellbore skin pressure as a function of water throughput and water velocity, for the simulator's Polymer Molecular Weight Transport option.","units":{},"default":"1","value_type":"INT"},{"index":2,"name":"NTSKPOLY","description":"NTSKPOLY is a positive integer that defines the number of SKPRPOLY tables in the PROPS section, used to describe the relationship of wellbore skin pressure as a function of polymer throughput and polymer velocity, for the simulator's Polymer Molecular Weight Transport option.","units":{},"default":"1","value_type":"INT"},{"index":3,"name":"NTPMWINJ","description":"NTPMWINJ is a positive integer that defines the number of PLYMWINJ tables in the PROPS section, used to describe the relationship of the injected polymer molecular weight as a function of polymer throughput and polymer velocity, for the simulator's Polymer Molecular Weight Transport option.","units":{},"default":"1","value_type":"INT"},{"index":4,"name":"NPLYVMH","description":"NPLYVMH is a positive integer that defines the maximum number of entries (rows) in the PLYVMH table in the PROPS section, used to describe the relationship of the injected polymer viscosity as a function of polymer molecular weight and polymer concentration, for the simulator's Polymer Molecular Weight Transport option.","units":{},"default":"1"}],"example":"--\n-- POLYMER MOLECULAR WEIGHT TRANSPORT TABLES (OPM FLOW RUNSPEC KEYWORD)\n--\n-- NO. NO. NO. NO.\n-- NTSKWAT NTSKPOLY NTPMWINJ NPLYVMH\nPINTDIMS\n2 2 2 1 /\nThe above example declares two SKPRWAT, SKPRPOLY, and PLYMWINJ keywords in the PROPS section will be used, as well as the default value of one for the number of rows in the PLYVMH keyword.\n| Note This is an OPM Flow specific keyword that employs an alternative polymer flood model based on a Polymer Molecular Weight Transport equation, that is not available in the commercial simulator. |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":3,"size_kind":"fixed","size_count":1},"POLYMER":{"name":"POLYMER","sections":["RUNSPEC"],"supported":null,"summary":"This keyword indicates that the polymer phase is present in the model and to activate the polymer flooding model. The keyword will also invoke data input file checking to ensure that all the required polymer phase input parameters are defined in the input deck.","parameters":[],"example":"--\n-- ACTIVATE THE POLYMER PHASE IN THE MODEL\n--\nPOLYMER\nThe above example declares that the polymer phase is active in the model.","size_kind":"none","size_count":0},"POLYMW":{"name":"POLYMW","sections":["RUNSPEC"],"supported":null,"summary":"This keyword activates OPM Flow's Polymer Molecular Weight Transport option that uses the polymer molecular weight in calculating the polymer viscosity, as well as accounting for formation damage due to the water and polymer injection, by adjusting the wellbore skin pressure. This keyword should only be used if the POLYMER keyword in the RUNSPEC section is also activated. The keyword will also invoke data input file checking to ensure that all the required polymer phase input parameters are defined in the input deck.","parameters":[],"example":"--\n-- ACTIVATE THE POLYMER PHASE IN THE MODEL\n--\nPOLYMER\n--\n-- ACTIVATE THE POLYMER MOLECULAR WEIGHT TRANSPORT OPTION\n--\nPOLYMW\nThe above example declares that the polymer phase is present, and that the simulator's Polymer Molecular Weight Transport option should be used instead of the standard polymer model.\n| Note This is an OPM Flow specific keyword that employs an alternative polymer flood model based on a Polymer Molecular Weight Transport equation, that is not available in the commercial simulator. |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"none","size_count":0},"PRECSALT":{"name":"PRECSALT","sections":["RUNSPEC"],"supported":null,"summary":"This keyword activates the OPM Flow Salt Precipitation model that accounts for salt precipitating out of the water phase when the water is being vaporized into the gas phase and the dissolved salt reaches the solubility limit as the pressure in the reservoir is being depleted (see the VAPWAT keyword in the RUNSPEC section). This facility is an extension to the standard Brine model, and as such the BRINE keyword in the RUNSPEC must also be present in the input deck. In general, if the PRECSALT keyword has been activated in the input deck then the VAPWAT keyword should also be activated. The keyword should only be used if both water and gas phases are active in the model.","parameters":[],"example":"The first part of the example shows the keywords for the RUNSPEC section.\n-- ==============================================================================\n--\n-- RUNSPEC SECTION\n--\n-- ==============================================================================\nRUNSPEC\n-- ------------------------------------------------------------------------------\n-- FLUID TYPES AND TRACER OPTIONS\n-- ------------------------------------------------------------------------------\n--\n-- OIL PHASE IS PRESENT IN THE RUN\n--\nOIL\n--\n-- WATER PHASE IS PRESENT IN THE RUN\n--\nWATER\n--\n-- GAS PHASE IS PRESENT IN THE RUN\n--\nGAS\n--\n-- DISSOLVED GAS IN LIVE OIL IS PRESENT IN THE RUN\n--\nDISGAS\n--\n-- ACTIVATE STANDARD BRINE MODEL IN THE RUN\n--\nBRINE\n--\n-- ACTIVATE THE OPM FLOW SALT PRECIPITATION MODEL (OPM FLOW KEYWORD)\n--\nPRECSALT\nThe above example declares that the oil, water, gas, dissolved gas, and brine phases are present in the model, and activates the Brine (BRINE keyword) and Salt Precipitation (PRECSALT keyword) models.\nThe second part of the example shows the additional PVT fluid keywords require for the Salt Precipitation model in the PROPS section. Note that in addition to the Salt Precipitation model specific keywords, the standard DENSITY (or GRAVITY), PVDG, and PVTO keywords are required.\n-- ==============================================================================\n--\n-- PROPS SECTION\n--\n-- ==============================================================================\nPROPS\n--\n-- WATER SALT PVT TABLE\n--\nPVTWSALT\n-- REF PRES REF SALT\n-- PSIA LB/STB\n-- -------- --------\n3000.0 0.000 / REFERENCE DATA\n--\n-- SALTCONC BW CW VISC VISC\n-- LB/STB RB/STB 1/PSIA CPOISE GRAD\n-- -------- -------- ------- ------ ------\n0.0 1.0 3.0E-6 1.0 1.0E-6\n10.0 0.8 3.0E-6 1.0 1.0E-6 / SALT CONCENTRATION\n--\n-- SET SALT SOLUBILITY LIMIT FOR ALL CELLS (OPM FLOW KEYWORD)\n--\nSALTSOL\n-- MAX SALT\n-- SALTSOL DENSITY\n0.500 135.46867445023383 /\nIn addition, to the above the PERMFACT keyword may be used to account for the reduction in porosity and permeability due to salt precipitating into the pore space. Again, in addition to the Salt Precipitation model specific keywords, the standard ROCK, SGOF, and SWOF keywords are required.\n--\n-- PERMEABILITY FACTOR REDUCTION DUE TO SALT (OPM FLOW KEYWORD)\n--\nPERMFACT\n-- PORO PERM\n-- FACTOR FACTOR\n-- ------- --------\n0.0 0.000\n0.4 0.005\n0.6 0.010\n0.9 0.100\n1.0 1.000 / TABLE NO. 01\n/\nIn order to initialize the model in the SOLUTION section, apart from the standard equilibration keywords, the following Salt Precipitation model specific keywords should be included.\n-- ==============================================================================\n--\n-- SOLUTION SECTION\n--\n-- ==============================================================================\nSOLUTION\n--\n-- PRECIPITATED SALT VOLUME FRACTION VERSUS DEPTH (OPM FLOW KEYWORD)\n--\n-- DEPTH SALTPSAT\n-- ------ --------\nSALTPVD\n8300.0 0.010\n8450.0 0.010 / SALT VS DEPTH EQUIL REGN 01\n--\n-- DEPTH SALT-1 SALT-2 SALT-3\n-- SALTCON SALTCON SALTCON\n-- ------ ------- ------- -------\nSALTVD\n8300.0 0.500\n8450.0 0.500 / SALT VS DEPTH EQUIL REGN 01\nNote that OPM Flow does not support Multi-Component Brine model, thus there should only one column of salt concentrations.\nFinally, in the SCHEDULE section, one may optionally one can add the injections well's injection salt concentrations, as shown below.\n-- ==============================================================================\n--\n-- SCHEDULE SECTION\n--\n-- ==============================================================================\nSCHEDULE\n--\n-- DEFINE WATER INJECTION WELL SALT CONCENTRATIONS\n--\n-- WELL SALT-1 SALT-2 SALT-3 SALT-4\n-- NAME SALTCON SALTCON SALTCON SALTCON\n-- ------- ------- ------- --------\nWSALT\n'INJ' 0.0000 /\n/\nNormally, with this option one would also include vaporized water via the VAPWAT keyword in the RUNSPEC section, as well as the PVTGW keyword to define gas PVT properties for dry gas, or the PVTGWO keyword that declares ","size_kind":"none","size_count":0},"PSTEADY":{"name":"PSTEADY","sections":["RUNSPEC"],"supported":false,"summary":"The PSTEADY keyword activates Pseudo Steady State Flow Calculation option by advancing the simulator until it reaches a pseudo steady state flow and then sets the date to the date defined on this keyword, that is written to the RESTART file. Keyword also includes parameters defining the conditions for pseudo steady flow state.","parameters":[{"index":1,"name":"DAY","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"MONTH","description":"","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"YEAR","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"DIFF","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":5,"name":"PRESSURE_TOL","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":6,"name":"OIL_TOL","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":7,"name":"WATER_TOL","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":8,"name":"GAS_TOL","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":9,"name":"BRINE_TOL","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":10,"name":"MAX_TIME","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Time"},{"index":11,"name":"MIN_TIME","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Time"},{"index":12,"name":"PIM_AQUIFERS","description":"","units":{},"default":"NO","value_type":"STRING"}],"example":"","expected_columns":12,"size_kind":"fixed","size_count":1},"RADIAL":{"name":"RADIAL","sections":["RUNSPEC"],"supported":null,"summary":"RADIAL activates the radial grid geometry option for the model, if this keyword and the SPIDER keyword are omitted then Cartesian geometry is assumed by OPM Flow.","parameters":[],"example":"--\n-- DEFINE RADIAL GRID GEOMETRY\n--\nRADIAL\nThe example activates the radial grid geometry option.","size_kind":"none","size_count":0},"REGDIMS":{"name":"REGDIMS","sections":["RUNSPEC"],"supported":null,"summary":"The REGDIMS keyword defines the maximum number of regions for various region arrays used in the model. Note that the maximum number of FIPNUM regions can be defined both on this keyword and the TABDIMS keyword, if it set in both locations the maximum value is used. The reason for this type of inconsistency is due to the commercial simulator evolving with time as new features were added, but at the same time having to maintain backward input deck compatibility.","parameters":[{"index":1,"name":"NTFIP","description":"A positive integer defining the maximum number of regions in the FIPNUM region array. If additional sets of fluid in-place regions have been defined, as per the FIPxxxxx series of fluid in-place region keywords, then NTFIP should be set to the maximum number of regions in either the FIPNUM or FIPxxxxx associated arrays. Thus, if the maximum number of regions in the FIPNUM array is 12, and the maximum value in the FIPxxxxx series of arrays is 20, then 20 should be entered for NTFIP. Note that this parameter may also be set on the TABDIMS keyword as well. If NTFIP is set in both places, then the maximum value is used.","units":{},"default":"1","value_type":"INT"},{"index":2,"name":"NMFIPR","description":"A positive integer defining the total maximum number of fluid in-place regions. The number of FIPNUM regions are defined by NTFIP. However, if additional sets of fluid in-place regions are required, as per the FIPxxxxx series of fluid in-place region keywords, then these are to be defined here by adding the number of FIPxxxxx arrays to the value NTFIP. So for example, if NTFIP equals five and the number of distinct FIPxxxxx regions is three, then the value to enter for NMFIPR is eight.","units":{},"default":"1","value_type":"INT"},{"index":3,"name":"NRFREG","description":"A positive integer defining the maximum number of independent reservoir regions in the ISOLNUM region array.","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"MXNFLX","description":"A positive integer defining the maximum number of flux regions in the FLUXNUM region array. MXNFLX can also be defined on the TABDIMS keywords as well. If MXNFLX is defined both here and on the TABDIMS keyword then the maximum value of the two is used.","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"NUSREG","description":"A positive integer defining the maximum user defined regions in a commercial simulator’s compositional model. This parameter is included for compatibility and should be defaulted as it is not used in OPM Flow.","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"NTCREG","description":"A positive integer defining the maximum number of regions in the COALNUM region array. This parameter is included for compatibility and should be defaulted as it is not used in OPM Flow.","units":{},"default":"1","value_type":"INT"},{"index":7,"name":"NOPREG","description":"A positive integer defining the maximum number of regions in the OPERNUM region array.","units":{},"default":"0","value_type":"INT"},{"index":8,"name":"NWKDREG","description":"A positive integer defining the maximum number of real double-precision work arrays for use with the OPERATE and OPERATER keywords. This parameter is included for compatibility and should be defaulted as it is not used in OPM Flow.","units":{},"default":"0","value_type":"INT"},{"index":9,"name":"NWKIREG","description":"A positive integer defining the maximum number of integer work arrays for use with the OPERATE and OPERATER keywords. This parameter is included for compatibility and should be defaulted as it is not used in OPM Flow.","units":{},"default":"0","value_type":"INT"},{"index":10,"name":"NPLMIX","description":"A positive integer defining the maximum number of regions in the PLMIXNUM region array.","units":{},"default":"1","value_type":"INT"}],"example":"--\n-- MAX TOTAL INDEP FLUX TRACK CBM OPERN WORK WORK POLY\n-- FIPNUM REGNS REGNS REGNS REGNS REGNS REGNS REAL INTG REGNS\nREGDIMS\n9 12 1* 1* 1* 1* 1* 1* 1* 1* /\nThe above example defines the number of FIPNUM regions to be nine and the number of FIPxxx type of regions to be three (12 – 9), the rest of the region sizes are set to the default values.","expected_columns":10,"size_kind":"fixed","size_count":1},"RIVRDIMS":{"name":"RIVRDIMS","sections":["RUNSPEC"],"supported":false,"summary":"RIVRDIMS defines the river system array dimensions used with the REACHES keyword and other river keywords in the SOLUTION and SCHEDULE sections. The keyword also enables the River option.","parameters":[{"index":1,"name":"MAX_RIVERS","description":"","units":{},"default":"0","value_type":"INT"},{"index":2,"name":"MAX_REACHES","description":"","units":{},"default":"1","value_type":"INT"},{"index":3,"name":"MAX_BRANCHES","description":"","units":{},"default":"1","value_type":"INT"},{"index":4,"name":"MAX_BLOCKS","description":"","units":{},"default":"1","value_type":"INT"},{"index":5,"name":"MXTBPR","description":"","units":{},"default":"1","value_type":"INT"},{"index":6,"name":"MXDPTB","description":"","units":{},"default":"2","value_type":"INT"},{"index":7,"name":"MXTBGR","description":"","units":{},"default":"1","value_type":"INT"},{"index":8,"name":"NMDEPT","description":"","units":{},"default":"0","value_type":"INT"},{"index":9,"name":"MXDEPT","description":"","units":{},"default":"2","value_type":"INT"},{"index":10,"name":"NMMAST","description":"","units":{},"default":"0","value_type":"INT"},{"index":11,"name":"MXMAST","description":"","units":{},"default":"2","value_type":"INT"},{"index":12,"name":"NRATTA","description":"","units":{},"default":"0","value_type":"INT"},{"index":13,"name":"MXRATE","description":"","units":{},"default":"2","value_type":"INT"}],"example":"","expected_columns":13,"size_kind":"fixed","size_count":1},"ROCKCOMP":{"name":"ROCKCOMP","sections":["RUNSPEC"],"supported":true,"summary":"The ROCKCOMP keyword activates rock compaction and defines various rock compaction options for the run. By default OPM Flow models rock compaction via pore volume compressibility as entered on the ROCK keyword in the PROPS section. This keyword enables pressure dependent pore volume and transmissibility multipliers for rock compaction that are entered in the PROPS section using the ROCKTAB keyword. Currently OPM Flow only supports the default options for rock compaction.","parameters":[{"index":1,"name":"ROCKOPT","description":"A character string that defines the rock compaction option based on one of the following character strings: REVERS: Rock compaction is reversible with increasing pressure. The rock compaction multipliers should be entered via the ROCKTAB keyword in the PROPS section. This is the default value. IRREVERS: Rock compaction is irreversible, that is the rock expansion does not occur when the pressure subsequently increases. HYSTER: Invokes the hysteresis rock compaction option. BOBERG: Rock compaction hysteresis is modeled using the Boberg formulation93\n Beattie, C.I., Boberg, T.C., and McNab, G.S. “Reservoir Simulation of Cyclic Steam Stimulation in the Cold Lake Oil Sands,” paper SPE 18752, Society of Petroleum Engineers Journal, (1991) 6, No. 2, 200-206.. Beattie, C.I., Boberg, T.C., and McNab, G.S. “Reservoir Simulation of Cyclic Steam Stimulation in the Cold Lake Oil Sands,” paper SPE 18752, Society of Petroleum Engineers Journal, (1991) 6, No. 2, 200-206. REVLIMIT: Activates the reversible hysteresis rock compaction option that limits the pore volume subject to reversibility based on the minimum pressure in a grid block and the initial water saturation. This option is only intended to be used with the water induced compaction model, neither of which are currently supported by OPM Flow.. PALM-MAN: Rock compaction hysteresis is modeled using the Palmer-Mansoori94\n Palmer, I. and Mansoori, J. “How Permeability Depends on Stress and Pore Pressure in Coalbeds: A New Model,” paper SPE 52607, SPE Reservoir Evaluation & Engineering (1998) 1, No. 6, 539-544. and 95\n Clarkson, C.R., Pan, Z., Palmer, I. and Harpalani, S. \"Predicting Sorption-Induced Strain and Permeability Increase With Depletion for Coalbed-Methane Reservoirs\", SPE 114778-PA, SPE Journal (2010) 15, No. 1, 152–159.formulation for coal bed methane reservoirs, neither of which are supported by OPM Flow. Palmer, I. and Mansoori, J. “How Permeability Depends on Stress and Pore Pressure in Coalbeds: A New Model,” paper SPE 52607, SPE Reservoir Evaluation & Engineering (1998) 1, No. 6, 539-544. Clarkson, C.R., Pan, Z., Palmer, I. and Harpalani, S. \"Predicting Sorption-Induced Strain and Permeability Increase With Depletion for Coalbed-Methane Reservoirs\", SPE 114778-PA, SPE Journal (2010) 15, No. 1, 152–159. NONE: Deactivates rock compaction, unless the water induced compaction model has been invoked. Only the REVERS and IRREVERS options are supported by OPM Flow.","units":{},"default":"REVERS","value_type":"STRING"},{"index":2,"name":"NTROCC","description":"A positive integer that defines the number of rock compaction tables, that is the number of ROCKTAB tables to be used by OPM Flow.","units":{},"default":"1","value_type":"INT"},{"index":3,"name":"WATINOPT","description":"A character string that states if the water induced rock compaction option should be used (YES) or not (NO). If set to YES then either the ROCKTABW or the ROCK2D and ROCKWNOD keywords should be entered in the PROPS section.","units":{},"default":"NO","value_type":"STRING"},{"index":4,"name":"PORTXROP","description":"A character string that specifies the model to be used for when transmissibility is dependent on porosity, and should be set to either: EXP: An exponential porosity-transmissibility relationship should be used. CZ: The Carmen-Kozeny96\n J. Kozeny, \"Ueber kapillare Leitung des Wassers im Boden.\" Sitzungsber Akad. Wiss., Wien, 136(2a): 271-306, 1927., 97\n P.C. Carman, \"Fluid flow through granular beds.\" Transactions, Institution of Chemical Engineers, London, 15: 150-166, 1937.and 98\n P.C. Carman, \"Flow of gases through porous media.\" Butterworths, London, 1956porosity-transmissibility relationship should be used. J. Kozeny, \"Ueber kapillare Leitung des Wassers im Boden.\" Sitzungsber Akad. Wiss., Wien, 136(2a): 271-306, 1927. P.C. Carman, \"Fluid flow through granular beds.\" Transactions, Institution of Chemical Engineers, London, 15: 150-166, 1937. P.C. Carman, \"Flow of gases through porous media.\" Butterworths, London, 1956 This option is used in the commercial compositional simulator and is therefore ignored by OPM Flow.","units":{},"default":"1*","value_type":"STRING"},{"index":5,"name":"CARKZEXP","description":"The exponent constant in the Carmen-Kozeny porosity-transmissibility equation for when PORTXROP has been set to CZ. This option is used in the commercial compositional simulator and is therefore ignored by OPM Flow.","units":{},"default":"0.0","value_type":"DOUBLE"}],"example":"--\n-- ROCK NUMBER WAT POR-TRAN\n-- OPTN TABLES INDUCE OPTION\nROCKCOMP\nREVERS 5 NO 1* /\nThe above example defines the default values for the ROCKCOMP keyword with five rock compaction tables.","expected_columns":5,"size_kind":"fixed","size_count":1},"RPTCPL":{"name":"RPTCPL","sections":["RUNSPEC"],"supported":false,"summary":"This keyword activates the couple simulation reporting, that results in the simulator writing out various initialization data and simulation data in order for external “controlling programs” to interactively manage the simulation. There is no data required for this keyword but the keyword should be terminated by a “/”.","parameters":[],"example":"--\n-- ACTIVATE COUPLE SIMULATION REPORTING\n--\nRPTCPL\n/\nThe above example switches on couple simulation reporting; however, this has no effect in OPM Flow input decks.","size_kind":"fixed","size_count":1},"RPTHMD":{"name":"RPTHMD","sections":["RUNSPEC"],"supported":false,"summary":"This keyword, RPTHMD, defines the options and level of history match output that should be written to history match file (*.HMD), for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"ITEM1","description":"","units":{},"default":"0","value_type":"INT"},{"index":2,"name":"ITEM2","description":"","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"ITEM3","description":"","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"ITEM4","description":"","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"ITEM5","description":"","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"ITEM6","description":"","units":{},"default":"0","value_type":"INT"}],"example":"","expected_columns":6,"size_kind":"fixed","size_count":1},"RPTRUNSP":{"name":"RPTRUNSP","sections":["RUNSPEC"],"supported":false,"summary":"This keyword activates reporting of all the RUNSPEC options utilized in the run. There is no data required for this keyword.","parameters":[],"example":"--\n-- ACTIVATE RUNSPEC SECTION REPORTING\n--\nRPTRUNSP\nThe above example switches on RUNSPEC reporting; however, this has no effect in OPM Flow input decks.","size_kind":"none","size_count":0},"RSSPEC":{"name":"RSSPEC","sections":["RUNSPEC"],"supported":null,"summary":"The RSSPEC keyword activates the writing out of the RESTART index file (*.RSSPEC). The restart data (pressure, saturations etc. through time for each active cell) are written out to two files one file contains the data, *.UNRST for example, and the second file contains an index of the data (*.RSSPEC) stored in the *.UNRST file. This keyword is somewhat redundant as the RESTART index file is written out by default. See the NORSSPEC keyword in the RUNSPEC section that deactivates the writing out of the file.","parameters":[],"example":"--\n-- ACTIVATE OUTPUT OF THE RESTART INDEX FILE *.RSSPEC\n--\nRSSPEC\nThe above example switches on the writing of the restart index file (*.RSSPEC); however, this has no effect in OPM Flow input decks.","size_kind":"none","size_count":0},"RUNSPEC":{"name":"RUNSPEC","sections":["RUNSPEC"],"supported":null,"summary":"The RUNSPEC activation keyword marks the start of the RUNSPEC section that defines the key parameters for the simulator including the dimensions of the model, phases present in the model (oil, gas and water for example), number of tables for a given property and the maximum number of rows for each table, the maximum number of groups, wells and well completions, as well as various options to be invoked by OPM Flow.","parameters":[],"example":"-- ==============================================================================\n--\n-- RUNSPEC SECTION\n--\n-- ==============================================================================\nRUNSPEC\nThe above example marks the start of the RUNSPEC section in the OPM Flow data input file.","size_kind":"none","size_count":0},"SAMG":{"name":"SAMG","sections":["RUNSPEC"],"supported":false,"summary":"This keyword actives the algebraic multi-grid linear solve; note this solver is not available to the general public in the commercial simulator.","parameters":[{"index":1,"name":"EPS","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":2,"name":"REUSE","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":2,"size_kind":"fixed","size_count":1},"SATOPTS":{"name":"SATOPTS","sections":["RUNSPEC"],"supported":true,"summary":"The SATOPTS keyword activates OPM Flow’s relative permeability assignment options. The relative permeability functions are defined using the either the:","parameters":[{"index":1,"name":"DIRECT","description":"A character string that activates the directional relative permeability assignment option. If the DIRECT option is specified then directional relative permeability assignment is activated and different relative permeability functions are assigned to the x, y and z directions. In this case the KRNUMX, KRNUMY and KRNUMZ keywords are used for Cartesian grids to allocate the relative permeability tables. For Radial grids the KRNUMR, KRNUMT and KRNUMZ keywords should be used.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"IRREVERS","description":"A character string that activates the irreversible directional relative permeability assignment option. If the IRREVERS option is specified then the relative permeability assignment is set to irreversible and results in different sets of relative permeability tables being applied for flow in the xi to xi + 1 direction and the xi to the xi – 1 direction, for all directions (x, y, z). In this case the KRNUMX, KRNUMY and KRNUMZ keywords are used for Cartesian grids to allocate the relative permeability tables in the xi to xi + 1 flow directions etc. For Radial grids the KRNUMR, KRNUMT and KRNUMZ keywords should be used. For flow in the xi to xi – 1 flow directions, etc., the KRNUMX-, KRNUMY- and KRNUMZ- keywords are used for Cartesian grids and the KRNUMR-, KRNUMT- and KRNUMZ- are used for radial grids. Only the default option is supported by OPM Flow, that is irreversible permeability tables are not supported.","units":{},"default":"None"},{"index":3,"name":"HYSTER","description":"A character string that activates the hysteresis option. If the HYSTER and DIRECT options have been activated and the IRREVERS has not been invoked on the SATOPTS keyword, then different relative permeability functions are used for the x, y, and z directions and for the drainage and imbibition processes. Here the drainage relative permeability curves are allocated via the KRNUMX,KRNUMY and KRNUMZ keywords for Cartesian grids and the KRNUMR, KRNUMT and KRNUMZ keywords for radial grids. The imbibition relative permeability curves are allocated via the IMBNUMX, IMBNUMY and IMBNUMZ keywords for Cartesian grids and the IMBNUMR, IMBNUMT and IMBNUMZ keywords for radial grids. If the HYSTER, DIRECT and IRREVERS options have been activated, then different relative permeability functions are used for the x, y, and z directions, each flow direction and for the drainage and imbibition processes. In addition to the aforementioned relative permeability allocation keywords for the xi to xi + 1 flow direction etc., the xi to xi – 1 flow directions keywords, KRNUMX-, KRNUMY- and KRNUMZ- are used for Cartesian grids and the KRNUMR-, KRNUMT- and KRNUMZ- are used for radial grids. The imbibition relative permeability curves are allocated via the IMBNUMX-, IMBNUMY- and IMBNUMZ- keywords for Cartesian grids and the IMBNUMR, IMBNUMT and IMBNUMZ- keywords for radial grids.","units":{},"default":"None"},{"index":4,"name":"SURFTENS","description":"A character string that activates the capillary pressure surface tension pressure dependency option. Only the default option is supported by OPM Flow, that is capillary pressure surface tension pressure dependency option is not supported.","units":{},"default":"None"}],"example":"The first example actives the directional relative permeability assignment option only and hence the following keywords are used to allocate the relative permeability arrays for Cartesian grids: KRNUMX, KRNUMY, and KRNUMZ.\n--\n-- ACTIVATE RELATIVE PERMEABILITY ASSIGNMENT HYSTERESIS OPTIONS\n-- DIRECTTIONAL(DIRECT) IRREVERSIBLE(IRREVERS) HYSTERESIS(HYSTER)\nSATOPTS\n'DIRECT' /\nThe next example actives the directional and irreversible relative permeability assignment options, and hence the following keywords are used to allocate the relative permeability arrays for Cartesian grids: KRNUMX, KRNUMY, KRNUMZ, KRNUMX-, KRNUMY-and KRNUMZ-.\n--\n-- ACTIVATE RELATIVE PERMEABILITY ASSIGNMENT HYSTERESIS OPTIONS\n-- DIRECTTIONAL(DIRECT) IRREVERSIBLE(IRREVERS) HYSTERESIS(HYSTER)\nSATOPTS\n'DIRECT' 'IRREVERS' /\nFinally, the last example invokes the directional, irreversible and hysteresis assignment options.\n--\n-- ACTIVATE RELATIVE PERMEABILITY ASSIGNMENT HYSTERESIS OPTIONS\n-- DIRECTTIONAL(DIRECT) IRREVERSIBLE(IRREVERS) HYSTERESIS(HYSTER)\nSATOPTS\n'DIRECT' 'IRREVERS' 'HYSTER' /\nIn this case the drainage relative permeability curves are allocated by the KRNUMX, KRNUMY, KRNUMZ, KRNUMX-, KRNUMY-, KRNUMZ- keywords, and the imbibition relative permeability curves are allocated by the IMBNUMX, IMBNUMY, IMBNUMZ, IMBNUMX-, IMBNUMY-, IMBNUMZ- keywords.\nNote\nThis keyword activates how relative permeability curves are assigned in the model. The ENDSCALE keyword allows the end-point scaling also to vary with direction, flow direction and hysteresis process, resulting in a great deal of flexibility.\nWhether or not all these features should be used though is another question.\n| Option | Cartesian | Radial | | |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------|----------------------------------------------------------------|--------------------------------------------------------|----------------------------------------------------------------|\n| DIRECT Flow in all directions | KRNUMX KRNUMY KRNUMZ | KRNUMR KRNUMT KRNUMZ | | |\n| DIRECT and IRREVERS Flow in the i to i +1 directions. Flow in the i to i -1 directions. | KRNUMX, KRNUMY KRNUMZ KRNUMX- KRNUMY- KRNUMZ- | KRNUMR KRNUMT KRNUMZ KRNUMR- KRNUMT- KRNUMZ- | | |\n| DIRECT and HYSTER Flow in all directions. ","size_kind":"fixed","size_count":1,"variadic_record":true},"SAVE":{"name":"SAVE","sections":["RUNSPEC","SCHEDULE"],"supported":null,"summary":"This keyword activates output of a SAVE file for fast restarts which are read in by the LOAD keyword in the RUNSPEC section. No data is required for this keyword.","parameters":[{"index":1,"name":"FILE_TYPE","description":"","units":{},"default":"UNFORMATTED","value_type":"STRING"}],"example":"The first example requests that a SAVE file be written out in the RUNSPEC section; however, OPM Flow will not write a RESTART record if the SAVE keyword is encountered in the RUNSPEC section.\n-- ==============================================================================\n--\n-- RUNSPEC SECTION\n--\n-- ==============================================================================\nRUNSPEC\n--\n-- WRITE OUT SAVE FILE FOR FAST RESTARTS\n--\nSAVE\nThe second example shows how the keyword is used in the SCHEDULE section.\n-- ==============================================================================\n--\n-- SCHEDULE SECTION\n--\n-- ==============================================================================\nSCHEDULE\n-- ------------------------------------------------------------------------------\n-- SCHEDULE SECTION - 2020-01-01\n-- ------------------------------------------------------------------------------\nRPTSCHED\n'WELLS=2' 'WELSPECS' 'CPU=2' FIP=2' /\nDATES\n1 APR 2021 /\n/\n--\n-- WRITE OUT SAVE FILE FOR FAST RESTARTS\n--\nSAVE\nDATES\n1 JLY 2021 /\n1 OCT 2021 /\n/\nHere OPM Flow will write out a RESTART file instead of a SAVE file at April 1st, 2021.","expected_columns":1,"size_kind":"fixed","size_count":1},"SCDPDIMS":{"name":"SCDPDIMS","sections":["RUNSPEC"],"supported":false,"summary":"The SCDPDIMS keyword defines the number of tables used in the Scale Deposition option and the maximum number of entries for the various tables.","parameters":[{"index":1,"name":"NTSCDP","description":"NTSCDP is a positive integer that defines the number of SCDPTAB scale deposition tables used in the Scale Deposition option.","units":{},"default":"0","value_type":"INT"},{"index":2,"name":"NPSCDP","description":"NPSCDP is a positive integer that defines the maximum number of entries (or rows) in any one SCDPTAB scale deposition table defined in the input deck.","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"NTSCDA","description":"NTSCDA is a positive integer that defines the number of SCDATAB scale damage tables used in the Scale Deposition option.","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"NPSCDA","description":"NPSCDA is a positive integer that defines the maximum number of entries (or rows) in any one SCDATAB scale damage table defined in the input deck.","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"Not Used","description":"","units":{},"default":"1*","value_type":"INT"},{"index":6,"name":"Not Used","description":"","units":{},"default":"1*","value_type":"INT"},{"index":7,"name":"NTSCDE","description":"NTSCDE is a positive integer that defines the number of SCDETAB karst aquifer dissolution tables used in the Scale Deposition option.","units":{},"default":"0","value_type":"INT"}],"example":"--\n-- NO. MAX NO. MAX NOT NOT NO.\n-- NTSCDP NPSCDP NTSCDA NPSCDA USED USED NTSCDE\nSCDPDIMS\n5 10 4 10 1* 1* 3 /\nThe above example defines the number of SCDPTAB scale deposition tables to be five with a maximum number of rows for each table set to 10, the maximum number of SCDATAB scale damage tables to be four with a maximum number of 10 rows per table, and the maximum number of SCDETAB karst aquifer dissolution tables to be three.","expected_columns":7,"size_kind":"fixed","size_count":1},"SKIP":{"name":"SKIP","sections":["RUNSPEC","GRID","EDIT","PROPS","REGIONS","SOLUTION","SUMMARY","SCHEDULE"],"supported":null,"summary":"The SKIP keyword activates skipping of all keywords and input data until the ENDSKIP keyword is encountered. All keywords between the SKIP and ENDSKIP keywords are ignored.","parameters":[],"example":"","size_kind":"none","size_count":0},"SKIP100":{"name":"SKIP100","sections":["RUNSPEC","GRID","EDIT","PROPS","REGIONS","SOLUTION","SUMMARY","SCHEDULE"],"supported":null,"summary":"The SKIP100 keyword activates skipping of all keywords and input data by the commercial black-oil simulator until the ENDSKIP keyword is encountered. All keywords between the SKIP100 and ENDSKIP keywords are ignored by the commercial black-oil simulator. The SKIP100 keyword is ignored by the commercial compositional simulator.","parameters":[],"example":"","size_kind":"none","size_count":0},"SKIP300":{"name":"SKIP300","sections":["RUNSPEC","GRID","EDIT","PROPS","REGIONS","SOLUTION","SUMMARY","SCHEDULE"],"supported":null,"summary":"The SKIP300 keyword activates skipping of all keywords and input data by the commercial compositional simulator until the ENDSKIP keyword is encountered. All keywords between the SKIP300 and ENDSKIP keywords are ignored by the commercial compositional simulator. The SKIP300 keyword is ignored by the commercial black-oil simulator.","parameters":[],"example":"","size_kind":"none","size_count":0},"SMRYDIMS":{"name":"SMRYDIMS","sections":["RUNSPEC"],"supported":null,"summary":"The SMRYDIMS keyword defines the maximum number of summary vectors to be written out to the SUMMARY file (*.SUMMARY).","parameters":[{"index":1,"name":"NSUMMX","description":"A positive integer that defines the maximum number of summary vectors to be written out to the SUMMARY file (*.SUMMARY).","units":{},"default":"10000","value_type":"INT"}],"example":"--\n-- SET THE MAXIMUM NUMBER OF SUMMARY VECTORS THAT CAN BE WRITTEN OUT\n--\nSMRYDIMS\n10000 /\nThe above example sets maximum number of summary vectors that can be written out to the SUMMARY file to the default value of 10,000; however, this has no effect in OPM Flow input decks.","expected_columns":1,"size_kind":"fixed","size_count":1},"SOLVDIMS":{"name":"SOLVDIMS","sections":["RUNSPEC","GRID"],"supported":false,"summary":"The SOLVDIMS defines the unstructured Perpendicular Bisector (“PEBI”)101\n Heinemann, Z.E. and Brand, C.W. 1988. Gridding Techniques in Reservoir Simulation. Proc., First Intl. Forum on Reservoir Simulation, Alpbach, Austria, 339. and 102\n Heinemann, Z.E., Brand, C.W., Munka, M. et al. 1991. Modeling Reservoir Geometry With Irregular Grids. SPE Res Eng 6 (2): 225–232. SPE-18412-PA. http://dx.doi.org/10.2118/18412-PAgrid nested factorization solver dimensions. This keyword is generated by an external pre-processing program for generating simulation grids.","parameters":[],"example":"","size_kind":"array"},"SOLVENT":{"name":"SOLVENT","sections":["RUNSPEC"],"supported":null,"summary":"This keyword indicates that the solvent phase is present in the model and to activate the four component solvent model for this run. In addition to this keyword, the oil, water and gases phases should also be declared for the run using the OIL, WATER and GAS keywords. The keyword will also invoke data input file checking to ensure that all the required Solvent phase input parameters are defined in the input deck.","parameters":[],"example":"--\n-- SOLVENT PHASE IS PRESENT IN THE RUN\n--\nSOLVENT\nThe above example declares that the solvent phase is active in the model.","size_kind":"none","size_count":0},"SPIDER":{"name":"SPIDER","sections":["RUNSPEC"],"supported":null,"summary":"SPIDER activates the OPM Flow spider grid geometry option for the model, if this keyword and the RADIAL keyword are omitted then Cartesian geometry is assumed by OPM Flow. Note that is an OPM Flow specific keyword and option.","parameters":[],"example":"--\n-- DEFINE SPIDER GRID GEOMETRY (OPM FLOW RADIAL GRID KEYWORD)\n--\nSPIDER\nThe above example actives OPM Flow’s spider grid geometry option.","size_kind":"none","size_count":0},"START":{"name":"START","sections":["RUNSPEC"],"supported":null,"summary":"This keyword sets the start date for the simulation switches. If the DATES keyword is to be used during the simulation, then a start date should be entered.","parameters":[{"index":1,"name":"DAY","description":"A positive integer that defines the day of the month, the value should be greater than or equal to one and less than or equal to 31.","units":{},"default":"None","value_type":"INT"},{"index":2,"name":"MONTH","description":"Character string for the month and should be one of the following 'JAN', 'FEB', 'MAR', 'APR', 'MAY', 'JUN', 'JUL' (or 'JLY'), 'AUG', 'SEP', 'OCT', 'NOV', or 'DEC'","units":{},"default":"None","value_type":"STRING"},{"index":3,"name":"YEAR","description":"A positive four digit integer value of the start year, which must be specified fully by four digits, that is 1986.","units":{},"default":"None","value_type":"INT"},{"index":4,"name":"TIME","description":"","units":{},"default":"00:00:00.000","value_type":"STRING"}],"example":"--\n-- DEFINE THE START DATE FOR THE RUN\n--\nSTART\n01 'JAN' 2014 /\nThe above example sets the start date for the run to be January 1, 2014.\nNote\nWhenever possible it is a good idea to always set the start date to be at the beginning of the year as per the example. As like most simulators, OPM Flow reports are always stated at the number of days from the start date (and sometimes at a given date). If the start date is at the beginning of the year, then calculating the actual date is relatively straight forward and simple.\n| Note Whenever possible it is a good idea to always set the start date to be at the beginning of the year as per the example. As like most simulators, OPM Flow reports are always stated at the number of days from the start date (and sometimes at a given date). If the start date is at the beginning of the year, then calculating the actual date is relatively straight forward and simple. |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":4,"size_kind":"fixed","size_count":1},"SURFACT":{"name":"SURFACT","sections":["RUNSPEC"],"supported":false,"summary":"This keyword indicates that the surfactant phase is present in the model and to activate the surfactant flooding model. The keyword will also invoke data input file checking to ensure that all the required surfactant phase input parameters are defined in the input deck. See also the SURFACTW keyword in the RUNSPEC section that actives the surfactant phase, but with the changes to the wettability option activated as well.","parameters":[],"example":"--\n-- ACTIVATE THE SURFACTANT PHASE IN THE MODEL\n--\nSURFACT\nThe above example declares that the surfactant phase is active in the model.","size_kind":"none","size_count":0},"SURFACTW":{"name":"SURFACTW","sections":["RUNSPEC"],"supported":false,"summary":"This keyword indicates that the surfactant phase is present in the model and to activate the surfactant flooding mode with Changes to Wettability option activated as well. The keyword will also invoke data input file checking to ensure that all the required surfactant phase input parameters are defined in the input deck. See also the SURFACT keyword in the RUNSPEC section that actives the surfactant phase only, that is without the Changes to the Wettability option.","parameters":[],"example":"--\n-- ACTIVATE THE SURFACTANT PHASE WITH WETTABILITY CHANGES IN THE MODEL\n--\nSURFACTW\nThe above example declares that the surfactant phase is active in the model together with the wettability changes.","size_kind":"none","size_count":0},"TABDIMS":{"name":"TABDIMS","sections":["RUNSPEC"],"supported":null,"summary":"The TABDIMS keyword defines the maximum number of tables for a given table type dataset and the maximum number of entries for the various tables. The commercial simulator combines both the black-oil and compositional simulator variables on this keyword; however, although all the parameters are explained below only the black-oil parameters are used by OPM Flow.","parameters":[{"index":1,"name":"NTSFUN","description":"A positive integer that defines the number of relative permeability table sets defined in the input deck. The tables are allocated to different parts of the grid by the SATNUM keyword.","units":{},"default":"1","value_type":"INT"},{"index":2,"name":"NTPVT","description":"A positive integer that defines the number of fluid property table sets defined in the input deck. The tables are allocated to different parts of the grid by the PVTNUM keyword.","units":{},"default":"1","value_type":"INT"},{"index":3,"name":"NSSFUN","description":"A positive integer that defines the maximum number of saturation entries in the relative permeability tables defined in the input deck.","units":{},"default":"20","value_type":"INT"},{"index":4,"name":"NPPVT","description":"A positive integer that defines the maximum number of pressure entries in the PVT tables.","units":{},"default":"20","value_type":"INT"},{"index":5,"name":"NTFIP","description":"A positive integer defining the maximum number of regions in the FIPNUM region array. Note that this parameter may also be set on the REGDIMS keyword as well. If NTFIP is set in both places then the maximum value is used.","units":{},"default":"1","value_type":"INT"},{"index":6,"name":"NRPVT","description":"A positive integer that defines the maximum number of Rs and Rv entries in the PVT tables. If the DISGAS and VAPOIL options have not been activated then this parameter is ignored.","units":{},"default":"20","value_type":"INT"},{"index":7,"name":"NRVPVT","description":"A positive integer that defines the maximum number of Rv entries in the PVT tables for the commercial compositional simulator.","units":{},"default":"20","value_type":"INT"},{"index":8,"name":"NTENDP","description":"A positive integer that defines the maximum number of saturation end-point depth tables. The end-point depth tables are used to re-scale the saturation tables as a function of depth as oppose to being a grid block property. NTENDP may also be specified on the ENDSCALE keyword, and if specified on both here and on the ENDSCALE keyword the maximum value of the two is used.","units":{},"default":"1","value_type":"INT"},{"index":9,"name":"NMEOSR","description":"A positive integer that defines the maximum number of reservoir equations of states for the commercial compositional simulator.","units":{},"default":"1","value_type":"INT"},{"index":10,"name":"NMEOSS","description":"A positive integer that defines the maximum number of separator or surface equations of states for the commercial compositional simulator.","units":{},"default":"1","value_type":"INT"},{"index":11,"name":"MXNFLX","description":"A positive integer defining the maximum number flux regions in the FLUXNUM region array. MXNFLX can also be defined on the REGDIMS keywords as well. If MXNFLX is defined both here and on the REGDIMS keyword then the maximum value of the two is used.","units":{},"default":"10","value_type":"INT"},{"index":12,"name":"MXNTHR","description":"A positive integer that defines the maximum number of thermal regions for the commercial compositional simulator.","units":{},"default":"1","value_type":"INT"},{"index":13,"name":"NTROCC","description":"A positive integer that defines the number of rock compressibility entries enter by the ROCK keyword defined in the input deck. The ROCK data is allocated to different parts of the grid by the either the PVTNUM or ROCKNUM keywords in the REGIONS section. If NTROCC is defaulted then the PVTNUM array will be used to allocate the ROCK keyword data to the grid blocks; whereas, if a value is entered then the ROCKNUM array will be used instead. See also the ROCKOPTS keyword in the PROPS section that can be used to redefine if the PVTNUM, ROCKNUM or SATNUM arrays should be employed to allocate the ROCK keyword data.","units":{},"default":"1*","value_type":"INT"},{"index":14,"name":"MXNPMR","description":"A positive integer that defines the maximum number of pressure maintenance regions for the commercial compositional simulator.","units":{},"default":"0","value_type":"INT"},{"index":15,"name":"NTABKT","description":"A positive integer that defines the maximum number of temperature dependent K-value tables for the when the thermal option is activated in the commercial compositional simulator.","units":{},"default":"0","value_type":"INT"},{"index":16,"name":"NTALPHA","description":"A positive integer that defines the maximum number of transport coefficient tables for the commercial compositional simulator.","units":{},"default":"0","value_type":"INT"},{"index":17,"name":"NASPKA","description":"A positive integer that defines the maximum number of maximum number of entries in the ASPKDAM keyword tables for the commercial compositional simulator.","units":{},"default":"10","value_type":"INT"},{"index":18,"name":"MXRAWG","description":"A positive integer that defines the maximum number of maximum number of entries in the ASPREWG keyword tables for the commercial compositional simulator.","units":{},"default":"10","value_type":"INT"},{"index":19,"name":"MXRASO","description":"A positive integer that defines the maximum number of pressure maintenance regions for the commercial compositional simulator.","units":{},"default":"10","value_type":"INT"},{"index":20,"name":"","description":"Not Used","units":{},"default":"1*","value_type":"STRING"},{"index":21,"name":"MCASPP","description":"A positive integer that defines the maximum number of column entries in the ASPPW2D keyword tables for the commercial compositional simulator.","units":{},"default":"5","value_type":"INT"},{"index":22,"name":"MRASPP","description":"A positive integer that defines the maximum number of row entries in the ASPPW2D keyword tables for the commercial compositional simulator.","units":{},"default":"5","value_type":"INT"},{"index":23,"name":"MXRATF","description":"A positive integer that defines the maximum number of entries in the ASPWETF table for the commercial compositional simulator.","units":{},"default":"5","value_type":"INT"},{"index":24,"name":"MXNKVT","description":"A positive integer that defines the maximum number of composition dependent K-value tables for the commercial compositional simulator.","units":{},"default":"0","value_type":"INT"},{"index":25,"name":"RESVED","description":"Not Used","units":{},"default":"1*","value_type":"STRING"}],"example":"--\n-- NO. NO. MAX MAX MAX MAX E300\n-- NTSFUN NTPVT NSSFUN NPPVT NTFIP NRPVT BLANK NTEND\nTABDIMS\n15 9 40 30 1* 1* 1* 1 /\nThe above example defines number of relative permeability tables to be 15 with a maximum number of rows for each table set to 40, and the number of PVT tables to be nine with a maximum number of 30 rows per table.","expected_columns":25,"size_kind":"fixed","size_count":1},"TEMP":{"name":"TEMP","sections":["RUNSPEC"],"supported":null,"summary":"This keyword activates the temperature modeling option.","parameters":[],"example":"--\n-- ACTIVATE THE TEMPERATURE MODELING OPTION (OPM FLOW TEMPERATURE OPTION ONLY)\n--\nTEMP\nThe above example activates the temperature modeling option.","size_kind":"none","size_count":0},"THERMAL":{"name":"THERMAL","sections":["RUNSPEC"],"supported":null,"summary":"This keyword activates the thermal modeling option.","parameters":[],"example":"--\n-- ACTIVATE THE THERMAL MODELING OPTION (OPM FLOW THERMAL OPTION ONLY)\n--\nTHERMAL\nThe above example activates the thermal modeling option.\n| Section | Keyword | Function | OPM Flow | Commercial Simulator | |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------|----------|----------------------|--|\n| THERMAL MODEL | TEMP MODEL | THERMAL MODEL | | | |\n| RUNSPEC | ROCKDIMS | Thermal Rock Dimensions of Over and Underburden Rock Types | | | |\n| TEMP | Activate the Temperature Modeling Option | | | Black-Oil | |\n| THERMAL | Activate the Thermal Mo","size_kind":"none","size_count":0},"TITLE":{"name":"TITLE","sections":["RUNSPEC"],"supported":null,"summary":"The TITLE keyword defines the title for the input deck. The title text will be printed on all reports so as to act as a reference for the run.","parameters":[{"index":1,"name":"TITLE","description":"A character string that defines the title for the input deck","units":{},"default":"None","value_type":"STRING"}],"example":"--\n-- DEFINE THE TITLE FOR THE RUN\nTITLE\nSPE01-THEM01-OPM1810-R01 - OPM THERMAL OPTION RUN\nThe above example defines the title for the run to be “SPE01-THEM01-OPM1810-R01 - OPM THERMAL OPTION RUN”.\n| Note It is good practice to include the name of the input file in the tittle (without the extension) for when cross checking results from multiple cases. |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"none","variadic_record":true},"TRACERS":{"name":"TRACERS","sections":["RUNSPEC"],"supported":true,"summary":"The TRACERS keyword defines the number of tracers in the model and the various passive tracer tracking options.","parameters":[{"index":1,"name":"MXOILTR","description":"A positive integer defining the maximum number of passive oil tracers defined using the TRACER keyword.","units":{},"default":"0","value_type":"INT"},{"index":2,"name":"MXWATTR","description":"A positive integer defining the maximum number of passive water tracers defined using the TRACER keyword.","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"MXGASTR","description":"A positive integer defining the maximum number of passive gas tracers defined using the TRACER keyword.","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"MXENVTR","description":"A positive integer defining the maximum number of passive environmental tracers defined using the TRACER keyword. Environmental tracers are used with the Environment Tracer model that takes into account tracer adsorption and decay. Only the default value of zero is currently supported.","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"DIFFOPT","description":"A character string defining the numerical diffusion option for tracer tracking runs that should be set to: DIFF activates the numerical diffusion control options. NODIFF deactivates the numerical diffusion control options. Only the default value of NODIFF is supported","units":{},"default":"NODIFF","value_type":"STRING"},{"index":6,"name":"MXITRTR","description":"A positive integer defining the maximum number of non-linear iterations to be used when the tracer option is activated.","units":{},"default":"12","value_type":"INT"},{"index":7,"name":"MNITRTR","description":"A positive integer defining the minimum number of non-linear iterations to be used when the tracer option is activated.","units":{},"default":"1","value_type":"INT"},{"index":8,"name":"NONLIN","description":"A character string stating if passive tracers as should be linear (NO) or non-linear (YES). Only the default value of NO is supported.","units":{},"default":"No","value_type":"STRING"},{"index":9,"name":"LNCONFAC","description":"A real value defining the initial linear convergence factor. The default value of 1* means the parameter will not be utilized.","units":{},"default":"1*","value_type":"INT"},{"index":10,"name":"NLCONFAC","description":"A real value defining the initial non-linear convergence factor. The default value of 1* means the parameter will not be utilized.","units":{},"default":"1*","value_type":"INT"},{"index":11,"name":"CONFAC","description":"A real value defining the LNCONFAC and NLCONFAC convergence factors to be used after the initial convergence factor has been applied.","units":{},"default":"1.0","value_type":"DOUBLE"},{"index":12,"name":"NUMCONF","description":"A positive integer defining the maximum number of times CONFAC can be used.","units":{},"default":"0","value_type":"INT"}],"example":"--\n-- NO OIL NO WAT NO GAS NO ENV DIFF MAX MIN TRACER\n-- TRACERS TRACERS TRACERS TRACERS CONTL NONLIN NONLIN NONLIN\nTRACERS\n0 7 1 0 'NODIFF' 1* 1* 1* /\nThe above example defines seven tracers in the water phase and one tracer in the gas phase.","expected_columns":12,"size_kind":"fixed","size_count":1},"TRPLPORO":{"name":"TRPLPORO","sections":["RUNSPEC"],"supported":false,"summary":"The TRPLPORO keyword activates the Triple Porosity Model option that models matrix, fractures and vuggy porosity for carbonate reservoirs, and specifies the number of matrix porosity systems","parameters":[{"index":1,"name":"TRPLPORO","description":"A positive integer value that specifies the number of matrix porosity systems in the model. TRPLPORO should be set to either: TRPLPORO set equal to 2, if the vugs are only connected to the fractures, so that the porosity system is matrix and connected vugs, or, TRPLPORO set equal to 3, if the vugs are connected to the fractures and the matrix, so that the porosity system is matrix, connected vugs, and isolated vugs.","units":{},"default":"1","value_type":"INT"}],"example":"--\n-- TRPLPORO\n-- OPTION\nTRPLPORO\n3 /\nThe above example activates the Triple Porosity Model option and specifies the porosity system is matrix, connected vugs, and isolated vugs.","expected_columns":1,"size_kind":"fixed","size_count":1},"UDADIMS":{"name":"UDADIMS","sections":["RUNSPEC"],"supported":null,"summary":"This keyword defines the dimensions of the User Defined Arguments (“UDA”) used by OPM Flow that can be applied to various connection, group, and well keywords in the SCHEDULE section. UDAs are defined by the UDQ keyword that is used to specify values to be constants, SUMMARY variables, as defined in SUMMARY section, or a formula using various mathematical functions together with constants and SUMMARY variables.","parameters":[{"index":1,"name":"NMUDA","description":"NMUDA is a positive integer that defines the number of arguments in a SCHEDULE section keyword, that are replaced by numeric UDQ values.","units":{},"default":"0","value_type":"INT"},{"index":2,"name":"IGNORED","description":"Not used and should be defaulted.","units":{},"default":"1*","value_type":"INT"},{"index":3,"name":"MXUDA","description":"MXUDA is a positive integer that defines the maximum number of unique arguments in a keyword that are replaced by numeric UDA values. Note that MXUDA differs from NMUDA, for example: If only the oil rate argument of, say the WCONPROD keyword is specified by a UDA, then both NMUDA and MXUDA equal one. However, if a second WCONPROD uses a different UDA, then NMUDA equals two, but MXUDA would still be one. Finally, if the same two distinct UDAs are used separately in two lines of WCONPROD data, then both NMUDA and MXUDA must be set to two. As MXUDA’s default value is 100 then this only needs to be increased where the same UDA is used more than 100 times.","units":{},"default":"100","value_type":"INT"}],"example":"--\n-- USER DEFINED ARGUMENT DIMENSIONS\n-- NO. NOT TOTAL\n-- ARGS USED UDQ\nUDADIMS\n10 1* 10 /\nIn the above example both NMUDA and MXUDA are set equal to ten.","expected_columns":3,"size_kind":"fixed","size_count":1},"UDQDIMS":{"name":"UDQDIMS","sections":["RUNSPEC"],"supported":false,"summary":"This keyword defines the dimensions associated with the UDQ keyword used in OPM Flow to calculate various user defined values in the SCHEDULE section. The UDQ keyword defined variables can be constants, SUMMARY variables, as defined in the SUMMARY section, or a formula using various mathematical functions together with constants and SUMMARY variables.","parameters":[{"index":1,"name":"MXFUNS","description":"A positive integer that defines the maximum number of functions that can be included when defining a UDQ definition. This should also include any brackets that will be used in the UDQ definition.","units":{},"default":"16","value_type":"INT"},{"index":2,"name":"MXITEMS","description":"MXITEMS is a positive integer that defines the maximum number of ITEMS allowed in an UDQ definition.","units":{},"default":"16","value_type":"INT"},{"index":3,"name":"MXUDC","description":"MXUDC is a positive integer that defines the maximum number of user defined CONNECTION quantities allowed in an UDQ definition.","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"MXUDF","description":"MXUDF is a positive integer that defines the maximum number of user defined FIELD quantities allowed in an UDQ definition.","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"MXUDG","description":"MXUDG is a positive integer that defines the maximum number of user defined GROUP quantities allowed in an UDQ definition.","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"MXUDR","description":"MXUDR is a positive integer that defines the maximum number of user defined REGION quantities allowed in an UDQ definition.","units":{},"default":"0","value_type":"INT"},{"index":7,"name":"MXUDS","description":"MXUDS is a positive integer that defines the maximum number of user defined SEGMENT quantities allowed in an UDQ definition.","units":{},"default":"0","value_type":"INT"},{"index":8,"name":"MXUDW","description":"MXUDW is a positive integer that defines the maximum number of user defined WELL quantities allowed in an UDQ definition.","units":{},"default":"0","value_type":"INT"},{"index":9,"name":"MXUDA","description":"MXUDA is a positive integer that defines the maximum number of user defined AQUIFER quantities allowed in an UDQ definition.","units":{},"default":"0","value_type":"INT"},{"index":10,"name":"MXUDB","description":"MXUDB is a positive integer that defines the maximum number of user defined BLOCK quantities allowed in an UDQ definition.","units":{},"default":"0","value_type":"INT"},{"index":11,"name":"RSEED","description":"RSEED is a character string that determines if a new random number seed should be generated for restart runs for use in the UDQ functions RANDN, RANDU RRNDN and RRNDU. If RSEED is set to Y than a new seed will be generated and if set to the default value of N or 1* then the same seed of the “base” simulation will be employed. See also the RSEED integer variable on the UDQPARAM keyword in the RUNSPEC section to set the random number seed for the current run. This feature is not supported by OPM Flow.","units":{},"default":"N","value_type":"STRING"}],"example":"--\n-- USER DEFINED ARGUMENT DIMENSIONS FACILITY\n-- MAX MAX MAX MAX MAX MAX MAX MAX MAX MAX RAND\n-- FUNCS ITEMS CONNS FIELD GROUP REGS SEGTM WELL AQUF BLCKS OPT\nUDQDIMS\n50 25 0 50 50 0 0 0 0 0 N /\nIn this case the maximum number of functions that can be included when defining a UDQ definition is set to 50, maximum number of items allowed in an UDQ definition is 25, the maximum number of user defined field quantities allowed in an UDQ definition is 50, and the maximum number of user defined group quantities allowed in an UDQ definition is also 50. All other parameters are defaulted including the RSEED variable (the same seed of the “base” simulation will be employed).","expected_columns":11,"size_kind":"fixed","size_count":1},"UDQPARAM":{"name":"UDQPARAM","sections":["RUNSPEC"],"supported":false,"summary":"This keyword defines the dimensions of the User Defined Arguments (“UDA”) used by OPM Flow that can be applied to various connection, group, and well keywords in the SCHEDULE section. UDAs are defined by the UDQ keyword that is used to specify values to be constants, SUMMARY variables, as defined in SUMMARY section, or a formula using various mathematical functions together with constants and SUMMARY variables.","parameters":[{"index":1,"name":"RSEED","description":"RSEED is a positive integer greater than zero that sets a new random number seed for use in the UDQ functions RANDN, RANDU RRNDN and RRNDU. See also the RSEED character variable on the UDQDIMS keyword in the RUNSPEC section to default the random number seed for a restart run. This feature is not supported by OPM Flow.","units":{},"default":"1","value_type":"INT"},{"index":2,"name":"RANGE","description":"RANGE is a real positive value greater than or equal to one and less than or equal to 1.0 x 1020, that sets the absolute range for the user defined quantities. The default value of 1 x 1020 sets the range from -1 x 1020 to +1 x 1020.","units":{},"default":"1 x 1020","value_type":"DOUBLE"},{"index":3,"name":"DEFAULT","description":"DEFAULT is real value that is the default numerical value given to undefined UDQ variables and should be in the same range as RANGE.","units":{},"default":"0.0","value_type":"DOUBLE"},{"index":4,"name":"TOLUDQ","description":"TOLUDQ a real positive number greater than zero and less than one that defines the tolerance used to determine if two real values are equal. Floating-point numbers (as implemented in computers) are never exact, one cannot compare floating point numbers for exact equality. Thus, TOLUDQ defines a tolerance. For example, the default value of 1 x 10-4 means that if the difference between two real values is less than 1 x 10-4 then the values are considered equal.","units":{},"default":"1 x 10-4","value_type":"DOUBLE"}],"example":"--\n-- USER DEFINED DEFAULT VALUES\n-- SEED RANGE UNDEFINED COMPARISON\n-- INTG -AND+ VALUE TOLERANCE\nUDQPARAM\n1 1.0E20 0.0 1.0E-4 /\nThe example explicitly sets the default values for all four variables on the UDAPARAM keyword, namely the random seed to one, the range to 1 x 1020, the undefined UDQ variables to zero, and the comparison tolerance to 1.0 x 10-4.","expected_columns":4,"size_kind":"fixed","size_count":1},"UDTDIMS":{"name":"UDTDIMS","sections":["RUNSPEC"],"supported":true,"summary":"This keyword defines the dimensions of the User Defined Tables (“UDT”) used by OPM Flow that can be used as lookup tables when assigning values to User Defined Quantities (\"UDQ\") using the UDQ keyword in the SCHEDULE section. UDTs are defined by the UDT keyword in the SCHEDULE section.","parameters":[{"index":1,"name":"MXUDT","description":"MXUDT is a positive integer that defines the maximum number of User Defined Tables","units":{},"default":"0","value_type":"INT"},{"index":2,"name":"NUDT","description":"NUDT is a positive integer that defines the maximum number of rows in any given User Defined Table.","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"MXINTP","description":"MXINTP is a positive integer that defines the maximum number of interpolation points allowed in any given dimension.","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"MXDIMS","description":"MXDIMS is a positive integer that defines the maximum number of dimensions in any given User Defined Table. Only one dimensional tables are currently supported by OPM Flow.","units":{},"default":"0","value_type":"INT"}],"example":"--\n-- USER DEFINED TABLE DIMENSIONS\n--\n-- MAX MAX MAX MAX\n-- TABLES ROWS INTPOL DIMS\nUDTDIMS\n3 20 3 2 /\nIn the above example the maximum number of UDT tables is set to three and the maximum number of rows for each table is 20, the maximum number of interpolation points in any given dimension is set to three and the maximum number of dimensions is defined as two.","expected_columns":4,"size_kind":"fixed","size_count":1},"UNCODHMD":{"name":"UNCODHMD","sections":["RUNSPEC"],"supported":false,"summary":"UNCODHMD activates the history match gradient unencoded output for the history match gradient output file. Unencoded files allows external programs to read this file type.","parameters":[],"example":"--\n-- ACTIVATE HISTORY MATCH GRADIENT UNENCODED OUTPUT\n--\nUNCODHMD\nThe above example switches on the unified output file option.","size_kind":"none","size_count":0},"UNIFIN":{"name":"UNIFIN","sections":["RUNSPEC"],"supported":null,"summary":"This keyword switches on the Unified Input Files option for all input files. Similar to the commercial simulator, OPM Flow has various options for reading various input files and writing the resulting OPM Flow output files as described in Table 5.54.","parameters":[],"example":"--\n-- SWITCH ON THE UNIFIED INPUT FILES OPTION\n--\nUNIFIN\nThe above example switches on the unified input file option.\n| Process | Keyword | Description | Files |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|\n| Input | FMTIN ","size_kind":"none","size_count":0},"UNIFOUT":{"name":"UNIFOUT","sections":["RUNSPEC"],"supported":null,"summary":"This keyword switches on the Unified Output Files option for all output files. Similar to the commercial simulator, OPM Flow has various options for reading various input files and writing the resulting OPM Flow output files as described in Table 5.55.","parameters":[],"example":"--\n-- SWITCH ON THE UNIFIED OUTPUT FILES OPTION\n--\nUNIFOUT\nThe above example switches on the unified output file option.\n| Process | Keyword | Description | Files |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|\n| Input | FMTIN ","size_kind":"none","size_count":0},"UNIFOUTS":{"name":"UNIFOUTS","sections":["RUNSPEC"],"supported":false,"summary":"The UNIFOUTS keyword causes the SUMMARY file output files to be a unified file, as opposed to non-unified multiple files. A unified file is a single file containing output for each reporting time step. Here a single SUMMARY file will be generated, as opposed to one file per report time step. See also the MULTOUT keyword in the RUNSPEC section that sets both the SUMMARY and RESTART files to be non-unified multiple files, as opposed to unified files. Note also that UNIFOUTS keyword has precedence over the MULTOUT keyword for SUMMARY files.","parameters":[],"example":"--\n-- ACTIVATE THE UNIFIED OUTPUT SUMMARY FILE OPTION\n--\nUNIFOUTS\nThe above example switches on writing of unified SUMMARY output files.","size_kind":"none","size_count":0},"UNIFSAVE":{"name":"UNIFSAVE","sections":["RUNSPEC"],"supported":false,"summary":"The UNIFSAVE keyword causes the SAVE file output file to be a unified file, as opposed to non-unified multiple files. A unified file is a single file containing output for each reporting time step. Here a single SAVE file will be generated, as opposed to one file per report time step. See also the MULTOUT keyword in the RUNSPEC section that sets both the SUMMARY and RESTART files to be non-unified multiple files, as opposed to unified files.","parameters":[],"example":"--\n-- ACTIVATE THE UNIFIED OUTPUT SAVE FILE OPTION\n--\nUNIFSAVE\nThe above example switches on writing of unified SAVE output files.","size_kind":"none","size_count":0},"VAPOIL":{"name":"VAPOIL","sections":["RUNSPEC"],"supported":null,"summary":"This keyword indicates that vaporized oil (more commonly referred to as condensate) is present in wet103\n Natural gas that contains significant heavy hydrocarbons such as propane, butane and other liquid hydrocarbons is known as wet gas or rich gas. The general rule of thumb is if the gas contains less methane (typically less than 85% methane) and more ethane, and other more complex hydrocarbons, it is labeled as wet gas. Wet gas normally has GOR's less than 100,000 scf/stb or 18,000 Sm3/m3, with the condensate having a gravity greater than 50 oAPI. gas in the model and the keyword should only be used if the there is both oil and gas phases in the model. The keyword may be used for gas-water and oil-water-gas input decks that contain the oil and gas phases. The keyword will also invoke data input file checking to ensure that all the required oil and gas phase input parameters are defined in the input deck.","parameters":[],"example":"--\n-- VAPORIZED OIL IN WET GAS IS PRESENT IN THE RUN\n--\nVAPOIL\nThe above example declares that the vaporized oil, i.e. condensate, in the gas phase is active in the model.","size_kind":"none","size_count":0},"VAPWAT":{"name":"VAPWAT","sections":["RUNSPEC"],"supported":null,"summary":"This keyword indicates that vaporized water is present in the gas phase and the keyword should only be used if both water and gas phases are present in the model. VAPWAT should also be used in conjunction with the PRECSALT keyword in the RUNSPEC section in order to activate OPM Flow’s Salt Precipitation model. VAPWAT may be used for gas-water and oil-water-gas input decks that contain the oil, gas and water phases.","parameters":[],"example":"--\n-- VAPORIZED WATER IN DRY/WET GAS IS PRESENT IN THE RUN (OPM FLOW KEYWORD)\n--\nVAPWAT\nThe above example declares that the vaporized water is present in the gas phase and is active in the model.\n| Note This is an OPM Flow specific keyword for the simulator’s Water Vaporization Model that is activated by declaring that vaporized water is present in the run. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"none","size_count":0},"VE":{"name":"VE","sections":["RUNSPEC"],"supported":false,"summary":"This keyword actives the Vertical Equilibrium (“VE”) model for the global grid and optionally specifies the type of VE model. The VE model type can either be compressed for merging columns of grid blocks into a single grid block, or uncompressed for the standard VE model.","parameters":[{"index":1,"name":"MODEL_TYPE","description":"","units":{},"default":"NOCOMP","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"VFPIDIMS":{"name":"VFPIDIMS","sections":["RUNSPEC"],"supported":null,"summary":"VFPIDIMS keyword defines the maximum dimensions of the injection well Vertical Lift Performance (“VFP”) tables defined by VFPINJ keyword. The VFP tables for the producing wells are defined by the VFPPDIMS keyword.","parameters":[{"index":1,"name":"MXMFLO","description":"A positive integer that defines the maximum number of injection rate entries for the VFPINJ keyword.","units":{},"default":"0","value_type":"INT"},{"index":2,"name":"MXMTHP","description":"A positive integer that defines the maximum number of THP entries for the VFPINJ keyword.","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"MXVFPTAB","description":"A positive integer that defines the maximum number of VFPINJ tables entered through the VFPINJ keyword.","units":{},"default":"0","value_type":"INT"}],"example":"-- INJECTING VFP TABLES\n-- VFP VFP VFP\n-- MXMFLO MXMTHP NMMVFT\nVFPIDIMS\n10 10 12 /\nThe above example defines that the maximum number of injection rates and THP entries on the VFPINJ keyword is 10, and the number of VFPINJ tables is 12.","expected_columns":3,"size_kind":"fixed","size_count":1},"VFPPDIMS":{"name":"VFPPDIMS","sections":["RUNSPEC"],"supported":null,"summary":"VFPPDIMS keyword defines the maximum dimensions of the production well Vertical Lift Performance (“VFP”) tables defined by VFPPROD keyword. The VFP tables for the injection wells are defined by the VFPIDIMS keyword.","parameters":[{"index":1,"name":"MXMFLO","description":"A positive integer that defines the maximum number of production flow rate entries for the VFPPROD keyword.","units":{},"default":"0","value_type":"INT"},{"index":2,"name":"MXMTHP","description":"A positive integer that defines the maximum number of THP entries for the VFPPROD keyword.","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"MXMWFR","description":"A positive integer that defines the maximum number of water fraction entries (WOR, WCUT, GWR etc.) for the VFPPROD keyword.","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"MXMGFR","description":"A positive integer that defines the maximum number of gas fraction entries (GOR, GLR, OGR etc.) for the VFPPROD keyword.","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"MXMALQ","description":"A positive integer that defines the maximum number of artificial lift quantity entries for the VFPPROD keyword.","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"MXVFPTAB","description":"A positive integer that defines the maximum number of VFPPROD tables entered through the VFPPROD keyword.","units":{},"default":"0","value_type":"INT"}],"example":"-- PRODUCING VFP TABLES\n-- VFP VFP VFP VFP VFP VFP\n-- MXMFLO MXMTHP MXMWFR MXMGFR MXMALQ NMMVFT\nVFPPDIMS\n20 10 10 10 6 9 /\nHere the example shows that there are a maximum of 20 flow rates, 10 THP entries, 10 water and gas fraction entries, and six artificial lift entries for the nine VFPPROD VFP production tables.","expected_columns":6,"size_kind":"fixed","size_count":1},"VISAGE":{"name":"VISAGE","sections":["RUNSPEC"],"supported":false,"summary":"The VISAGE keyword activates the External Reservoir Geo-Mechanics VISAGE option. The keyword should not be used in input decks as the associated data is generated by an external program.","parameters":[],"example":"","size_kind":"none","size_count":0},"VISCD":{"name":"VISCD","sections":["RUNSPEC"],"supported":false,"summary":"The VISCD keyword activates the Dual Porosity Viscous Displacement option for dual porosity and dual permeability models, and therefore requires either the DUALPORO or DUALPERM keyword to be entered in the RUNSPEC section to activate either one of these options. The VISCD option is used to model the viscous displacement of fluids from the matrix by the fracture pressure gradient, for when the fracture system has a more moderate permeability, and flow to and from the matrix caused by the fracture pressure gradient acts as an additional production mechanism105\n Gilman, J. R. and Kazemi, H. “Improved Calculation for Viscous and Gravity Displacement in Matrix Blocks in Dual-Porosity Simulators,” paper SPE 16010 (includes a number of associated papers), Journal of Petroleum Technology (1988) 40, No. 1, 60-70.. Normally this mechanism is ignored as the pressure gradient in the fracture system is small due to the very high permeability of the fracture system. See the LX, LY and LZ keywo...","parameters":[],"example":"--\n-- ACTIVATE DUAL POROSITY VISCOUS DISPLACEMENT OPTION\n--\nVISCD\nThe above example activates the dual porosity viscous displacement option.","size_kind":"none","size_count":0},"WARN":{"name":"WARN","sections":["RUNSPEC","GRID","EDIT","PROPS","REGIONS","SOLUTION","SUMMARY","SCHEDULE"],"supported":null,"summary":"Turns on warning messages to be printed to the print file (*.PRT); note that this keyword is activated by default and can subsequently be switched off by the NOWARN activation keyword. The warning messages may be turned on and off using keywords WARN and NOWARN. OPM Flow always prints error messages.","parameters":[],"example":"","size_kind":"none","size_count":0},"WATER":{"name":"WATER","sections":["RUNSPEC"],"supported":null,"summary":"This keyword indicate that the water phase is present in the model and must be used for gas-water, oil-water, oil-water-gas input decks that contain the water phase. The keyword will also invoke data input file checking to ensure that all the required water phase input parameters are defined in the input deck.","parameters":[],"example":"--\n-- WATER PHASE IS PRESENT IN THE RUN\n--\nWATER\nThe above example declares that the water phase is active in the model.","size_kind":"none","size_count":0},"WELLDIMS":{"name":"WELLDIMS","sections":["RUNSPEC"],"supported":null,"summary":"WELLDIMS defines various well and group dimensions for the run. The commercial simulator combines both the black-oil and compositional simulator variables on this keyword; however, although all the parameters are explained below only the black-oil parameters are used by OPM Flow.","parameters":[{"index":1,"name":"MXWELS","description":"A positive integer defining the maximum number of wells for this model.","units":{},"default":"0","value_type":"INT"},{"index":2,"name":"MXCONS","description":"A positive integer defining the maximum number of grid block connections per well for this model.","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"MXGRPS","description":"A positive integer defining the maximum number of groups for this model.","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"MXGRPW","description":"A positive integer defining the maximum number of wells that can belong to a group in the model and the maximum number of child groups in a group. Note that MXGRPW sets both the maximum number of wells in a group and the maximum number of child groups in a group. The former applies to groups that contain wells and the latter applies to groups that contain other groups. See also the GRUPTREE keyword in the SCHEDULE section to define group hierarchy.","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"MXSTAGE","description":"A positive integer defining the maximum number of stages per separator for this model. This option is ignored by OPM Flow.","units":{},"default":"5","value_type":"INT"},{"index":6,"name":"MXSTRMS","description":"A positive integer defining the maximum number of well streams for this model. This option is ignored by OPM Flow.","units":{},"default":"10","value_type":"INT"},{"index":7,"name":"MXMIXS","description":"A positive integer defining the maximum number of mixtures for this model. This option is ignored by OPM Flow.","units":{},"default":"5","value_type":"INT"},{"index":8,"name":"MXSEPS","description":"A positive integer defining the maximum number of separators for this model. This option is ignored by OPM Flow.","units":{},"default":"4","value_type":"INT"},{"index":9,"name":"MXCOMPS","description":"A positive integer defining the maximum number of mixture components in a mixture for the model. This option is ignored by OPM Flow.","units":{},"default":"3","value_type":"INT"},{"index":10,"name":"MXDOCOMP","description":"A positive integer defining the maximum number of well completions that can cross a parallel run domain boundary when the PARALLEL option has been activated. This option is ignored by OPM Flow.","units":{},"default":"0","value_type":"INT"},{"index":11,"name":"MXWSLIST","description":"A positive integer defining the maximum number of well lists that a well may be concurrent belong to at one time for this model. This option is ignored by OPM Flow.","units":{},"default":"1","value_type":"INT"},{"index":12,"name":"MXWLISTS","description":"A positive integer defining the maximum number of dynamic well lists for this model. This option is ignored by OPM Flow.","units":{},"default":"1","value_type":"INT"},{"index":13,"name":"MXWSECD","description":"A positive integer defining the maximum number of secondary wells for this model. This option is ignored by OPM Flow.","units":{},"default":"10","value_type":"INT"},{"index":14,"name":"MXNGPP","description":"A positive integer defining the maximum number of row entries per completion in the generalized pseudo-pressure tables used for to calculate the blocking factor associated with condensate drop-out in gas condensate reservoirs. If the generalized pseudo-pressure option has not been activated then this is ignored. This option is ignored by OPM Flow.","units":{},"default":"201","value_type":"INT"}],"example":"--\n-- WELL WELL GRUPS GRUPS\n-- MXWELS MXCONS MXGRPS MXGRPW\nWELLDIMS\n60 110 18 40 /\nThe above example defines the maximum number of wells to be 60 with 110 completions per well, and maximum number of groups to be 18 with maximum number of wells per group of 40. All other parameters are defaulted.","expected_columns":14,"size_kind":"fixed","size_count":1},"WPOTCALC":{"name":"WPOTCALC","sections":["RUNSPEC"],"supported":false,"summary":"WPOTCALC defines how shut-in and stopped wells should have their well potentials calculated. Well potentials for wells under these conditions need to have their potentials calculated if they are in a Priority Drilling Queue via the WDRILPRI keyword in the SCHEDULE section, or the Prioritization option has been enabled by the PRIORITY keyword in the SCHEDULE section.","parameters":[{"index":1,"name":"FORCE_CALC","description":"","units":{},"default":"YES","value_type":"STRING"},{"index":2,"name":"USE_SEGMENT_VOLUMES","description":"","units":{},"default":"NO","value_type":"STRING"}],"example":"","expected_columns":2,"size_kind":"fixed","size_count":1},"WSEGDIMS":{"name":"WSEGDIMS","sections":["RUNSPEC"],"supported":null,"summary":"The WSEGSDIMS keyword defines the multi-segment well dimensions for the multi-segment well model and the keyword is obligatory if multi-segment wells are being employed in the model.","parameters":[{"index":1,"name":"MXWELS","description":"A positive integer defining the maximum number of multi-segment wells for this model.","units":{},"default":"0","value_type":"INT"},{"index":2,"name":"MXSEGS","description":"A positive integer defining the maximum number of segments per well for this model.","units":{},"default":"1","value_type":"INT"},{"index":3,"name":"MXBRAN","description":"A positive integer defining the maximum number of branches per multi-segment well, including the main branch groups for this model.","units":{},"default":"1","value_type":"INT"},{"index":4,"name":"MXLINKS","description":"A positive integer defining the maximum number of segment links per multi-segment well. The simulator does not currently support multi-segment chord links, and therefore this parameter is ignored.","units":{},"default":"0","value_type":"INT"}],"example":"--\n-- WELL WELL BRANCH SEGMENT\n-- MXWELS MXSEGS MXBRAN MXLINKS\nWSEGDIMS\n5 100 10 10 /\nThe above example defines the maximum number of multi-segment wells to be five with up to 100 segments per multi-segment well, a maximum number of 10 branches per multi-segment well, and up to 10 segment links per multi-segment well.","expected_columns":4,"size_kind":"fixed","size_count":1},"ACTNUM":{"name":"ACTNUM","sections":["GRID"],"supported":null,"summary":"The ACTNUM keyword specifies which grid blocks are either active or inactive. A grid block is automatically set to inactive if its pore volume is less than the value entered using the MINPV keyword. The ACTNUM keyword can be used to also make blocks with pore volumes greater than MINPV inactive.","parameters":[{"index":1,"name":"ACTNUM","description":"An array of integers equal to either 0 or 1 that define the activity of each cell in the model. A value of 0 indicates the cell is inactive. Grid blocks are ordered with the I index cycling fastest, followed by the J and K indices. Repeat counts may be used, for example 20*1.","units":{},"default":"1"}],"example":"The example below sets several cells to be inactive for a 4 x 5 x 2 model.\nACTNUM\n-- Layer 1\n0 0 1 1\n0 0 1 1\n1 1 1 1\n1 1 1 1\n1 1 1 1\n-- Layer 2\n1 1 1 1\n1 1 1 1\n1 1 1 1\n1 1 1 1\n0 0 0 0\n/\nAlternatively the EQUALS keyword could be employed to accomplish the same task, that is:\n-- -- ARRAY CONSTANT -- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\n'ACTNUM’ 1.0000 1* 1* 1* 1* 1* 1* / SET ACTIVE CELLS\n'ACTNUM’ 0.0000 1 2 1 2 1 1 / SET INACTIVE CELLS\n'ACTNUM’ 0.0000 1 4 5 5 2 2 / SET INACTIVE CELLS\n/","size_kind":"array"},"ADD":{"name":"ADD","sections":["GRID","EDIT","PROPS","REGIONS","SOLUTION"],"supported":true,"summary":"The ADD keyword adds a constant to a specified array or part of an array. The constant can be an integer or real value depending on the array type; however, the arrays that can be operated on are dependent on which section the ADD keyword is being applied in.","parameters":[{"index":1,"name":"ARRAY","description":"A character string of up to eight characters in length that defines the keyword identifying the property to be modified.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"CONSTANT","description":"An integer or real value to be added to the ARRAY in the same units as the ARRAY property.","units":{},"default":"0","value_type":"DOUBLE"},{"index":3,"name":"I1","description":"A positive integer that defines the lower bound of the array in the I-direction to be modified must be greater than or equal 1 and less than or equal to I2 and NX.","units":{},"default":"1","value_type":"INT"},{"index":4,"name":"I2","description":"A positive integer that defines the upper bound of the array in the I-direction to be modified must be greater than or equal to II and less than or equal to NX","units":{},"default":"NX","value_type":"INT"},{"index":5,"name":"J1","description":"A positive integer that defines the lower bound of the array in the J-direction to be modified must be greater than or equal 1 and less than or equal to J2 and NY.","units":{},"default":"1","value_type":"INT"},{"index":6,"name":"J2","description":"A positive integer that defines the upper bound of the array in the J-direction to be modified must be greater than or equal to JI and less than or equal to NY.","units":{},"default":"NY","value_type":"INT"},{"index":7,"name":"K1","description":"A positive integer that defines the lower bound of the array in the K-direction to be modified must be greater than or equal to one and less than or equal to K2 and NZ.","units":{},"default":"1","value_type":"INT"},{"index":8,"name":"K2","description":"A positive integer that defines the upper bound of the array in the K-direction to be modified must be greater than or equal to KI and less than or equal to NZ.","units":{},"default":"NZ","value_type":"INT"}],"example":"--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nADD\nPERMX 20.000 1* 1* 1* 1* 1* 1* / ADD 20 mD TO PERMX\n/\nThe above example adds 20 md to the PERMX property array throughout the model.\n| ADD Keyword and Variable Options by Section | | | | | | |\n|---------------------------------------------|---------|-------|---------|----------|---------|----------|\n| GRID | EDIT | PROPS | REGIONS | SOLUTION | SUMMARY | SCHEDULE |\n| DX | DEPTH | SWL | ENDNUM | PRESSURE | | |\n| DY | PORV | SWCR | EQLNUM | SWAT | | |\n| DZ | TRANX | SWU | FIPNUM | SGAS | | |\n| PERMX | TRANY | SGL | IMBNUM | RV | | |\n| PERMY | TRANZ | SGCR | MISCNUM | RS | | |\n| PERMZ | DIFFX | SGU | PVTNUM | TBLK | | |\n| MULTX | DIFFY | KRW | ROCKNUM | GI | | |\n| MULTY | DIFFZ | KRO | SATNUM | OILAPI | | |\n| MULTZ | TRANR | KRG | WH2NUM | SALT | | |\n| DR | TRANTHT | PCG | | GASCONC | | |\n| DTHETA | DIFFR | PCW | | SOLVCONC | | |\n| PERMR | DIFFTHT | | | SOLVFRAC | | |\n| PERMTHT | | | | SFOAM | | |\n| DZNET | | | | SPOLY | | |\n| PORO | | | | | | |\n| NTG | | | | | | |\n| FLUXNUM | | | | | | |\n| MULTNUM | | | | | | |\n| MPFANUM | | | | | | |\n| DIFFX | | | | | | |\n| DIFFY | | | | | | |\n| DIFFZ | | | | | | |\n| DIFFR | | | | | | |\n| DIFFTHT | | | | | | |","expected_columns":8,"size_kind":"list"},"ADDREG":{"name":"ADDREG","sections":["GRID","EDIT","PROPS","REGIONS","SOLUTION"],"supported":false,"summary":"The ADDREG keyword adds a constant to a specified array or part of an array based on cells with a specific region number. The region number array can be FLUXNUM, MULTNUM or OPERNUM and these arrays must be defined and be available before the ADDREG keyword is read by the simulator. The constant can be an integer or real value depending on the array type; however, the arrays that can be operated on are dependent on which section the ADDREG keyword is being applied in.","parameters":[{"index":1,"name":"ARRAY","description":"A character string of up to eight characters in length that defines the keyword identifying the array to be modified.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"CONSTANT","description":"An integer or real value to be added to the ARRAY in the same units as the ARRAY property for a given REGION.","units":{},"default":"0","value_type":"DOUBLE"},{"index":3,"name":"REGION NUMBER","description":"REGION NUMBER is a positive integer representing the region for which the CONSTANT in (2) should be applied.","units":{},"default":"None","value_type":"INT"},{"index":4,"name":"REGION ARRAY","description":"The REGION ARRAY to use for applying the CONSTANT in (2) based on the REGION NUMBER in (3). REGION ARRAY can have the following values: F for the FLUXNUM array M for the MULTNUM array O for the OPERNUM array","units":{},"default":"M","value_type":"STRING"}],"example":"--\n-- FIRST DEFINE THE PROPERTY ARRAYS AND MULTNUM ARRAYS FOR 10 X 10 X 20 MODEL\n--\n-- ARRAY CONSTANT -- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nPORO 0.2000 1* 1* 1* 1* 1* 1* / PORO TO 0.20 IN MODEL\nPERMX 100.00 1* 1* 1* 1* 1* 1* / PERMX TO 0.10 IN MODEL\nMULTNUM 1 1* 1* 1* 1* 1* 1* / MULTNUM IN MODEL\nMULTNUM 2 1* 5 1 5 6 6 / MULTNUM IN MODEL\nMULTNUM 3 1* 1* 1* 1* 10 10 / MULTNUM IN MODEL\n/\n--\n– NOW RESET PORO AND PERMX BASED ON THE MULTNUM REGION NUMBER\n--\n-- ADD A CONSTANT TO AN ARRAY BASED ON A REGION NUMBER\n--\n-- ARRAY CONSTANT REGION REGION ARRAY\n-- VALUE NUMBER M / F / O ADDREG\nPORO 0.050 1 M /\nPORO 0.100 2 M /\nPORO -0.050 3 M /\nPERMX 25.00 1 M /\nPERMX 100.0 2 M /\nPERMX -50.00 3 M /\n/\nThe example first defines the PORO and PERMX property arrays for the model and then sets the MULTNUM array to 1 for all cells in the model, after which selected areas of model are assigned various MULTNUM integer values. The ADDREG can then be invoked to add or subtract constant values from the PORO and PERMX arrays for the various MULTNUM regions.\n| ADDREG Keyword and Variable Options by Section | | | | | | |\n|------------------------------------------------|---------|-------|---------|----------|---------|----------|\n| GRID | EDIT | PROPS | REGIONS | SOLUTION | SUMMARY | SCHEDULE |\n| DX | DEPTH | SWL | ENDNUM | PRESSURE | | |\n| DY | PORV | SWCR | EQLNUM | SWAT | | |\n| DZ | TRANX | SWU | FIPNUM | SGAS | | |\n| PERMX | TRANY | SGL | IMBNUM | RV | | |\n| PERMY | TRANZ | SGCR | MISCNUM | RS | | |\n| PERMZ | DIFFX | SGU | PVTNUM | TBLK | | |\n| MULTX | DIFFY | KRW | ROCKNUM | GI | | |\n| MULTY | DIFFZ | KRO | SATNUM | OILAPI | | |\n| MULTZ | TRANR | KRG | WH2NUM | SALT | | |\n| DR | TRANTHT | PCG | | GASCONC | | |\n| DTHETA | DIFFR | PCW | | SOLVCONC | | |\n| PERMR | DIFFTHT | | | SOLVFRAC | | |\n| PERMTHT | | | | SFOAM | | |\n| DZNET | | | | SPOLY | | |\n| PORO | | | | | | |\n| NTG | | | | | | |\n| FLUXNUM | | | | | | |\n| MULTNUM | | | | | | |\n| MPFANUM | | | | | | |\n| DIFFX | | | | | | |\n| DIFFY | | | | | | |\n| DIFFZ | | | | | | |\n| DIFFR | | | | | | |\n| DIFFTHT | ","expected_columns":4,"size_kind":"list"},"ADDZCORN":{"name":"ADDZCORN","sections":["GRID"],"supported":false,"summary":"The ADDZCORN keyword adds a constant to the ZCORN array or part of the array based on cells defined in the specified input box. The constant can be real or integer and can be negative or positive.","parameters":[{"index":1,"name":"ADDED_VALUE","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":2,"name":"IX1","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"IX2","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"JY1","description":"","units":{},"default":"","value_type":"INT"},{"index":5,"name":"JY2","description":"","units":{},"default":"","value_type":"INT"},{"index":6,"name":"KZ1","description":"","units":{},"default":"","value_type":"INT"},{"index":7,"name":"KZ2","description":"","units":{},"default":"","value_type":"INT"},{"index":8,"name":"IX1A","description":"","units":{},"default":"-1","value_type":"INT"},{"index":9,"name":"IX2A","description":"","units":{},"default":"-1","value_type":"INT"},{"index":10,"name":"JY1A","description":"","units":{},"default":"-1","value_type":"INT"},{"index":11,"name":"JY2A","description":"","units":{},"default":"-1","value_type":"INT"},{"index":12,"name":"ACTION","description":"","units":{},"default":"BOTH","value_type":"STRING"}],"example":"","expected_columns":12,"size_kind":"list"},"AMALGAM":{"name":"AMALGAM","sections":["GRID"],"supported":false,"summary":"The AMALGAM keyword defines a Cartesian Local Grid Refinements (“LGR”) amalgamations, that is merging several LGRs into one amalgamated LGR.","parameters":[{"index":1,"name":"LGR_GROUPS","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","size_kind":"list","variadic_record":true},"AQUANCON":{"name":"AQUANCON","sections":["GRID","SOLUTION"],"supported":null,"summary":"The AQUANCON keyword defines how analytical aquifers are connected to the simulation grid, this includes the Carter-Tracy, Fetkovich and Constant Flux analytical aquifers, all of which are implemented in OPM Flow. Carter-Tracy analytical aquifers are characterized by the AQUCT keyword in the GRID section and Fetkovich analytical aquifers are defined by the AQUFETP keyword in the SOLUTION section. Finally, the Constant Flux aquifer is defined by the AQUFLUX keyword in SOLUTION section.","parameters":[{"index":1,"name":"AQUID","description":"AQUID is a positive integer greater than or equal to one and less than the maximum number of analytical aquifers as defined by the NANAQU variable on the AQUDIMS keyword in the RUNSPEC section, that defines the aquifer to be connected to the grid.","units":{},"default":"None","value_type":"INT"},{"index":2,"name":"I1","description":"A positive integer that defines the lower bound of the cells in the I-direction to be connected to the aquifer and must be greater than or equal to one and less than or equal to I2 and NX.","units":{},"default":"1","value_type":"INT"},{"index":3,"name":"I2","description":"A positive integer that defines the upper bound of the cells in the I-direction to be connected to the aquifer and must be greater than or equal to I1 and less than or equal to NX","units":{},"default":"NX","value_type":"INT"},{"index":4,"name":"J1","description":"A positive integer that defines the lower bound of the cells in the J-direction to be connected to the aquifer and must be greater than or equal to one and less than or equal to J2 and NY.","units":{},"default":"1","value_type":"INT"},{"index":5,"name":"J2","description":"A positive integer that defines the upper bound of the cells in the J-direction to be connected to the aquifer and must be greater than or equal to JI and less than or equal to NY.","units":{},"default":"NY","value_type":"INT"},{"index":6,"name":"K1","description":"A positive integer that defines the lower bound of the cells in the K-direction to be to be connected to the aquifer and must be greater than or equal to one and less than or equal to K2 and NZ.","units":{},"default":"1","value_type":"INT"},{"index":7,"name":"K2","description":"A positive integer that defines the upper bound of the cells in the K-direction to be connected to the aquifer and must be greater than or equal to KI and less than or equal to NZ.","units":{},"default":"NZ","value_type":"INT"},{"index":8,"name":"AQUFACE","description":"AQUFACE is a character string that sets the connection “face” of the cells declared by this record and should be set to one of the following: X+, Y+, or Z+ for the positive direction, or X-, Y- or Z- for the negative direction transmissibilities. I+, J+, or K+ for the positive direction, or I-, J- or K- for the negative direction transmissibilities.","units":{},"default":"None","value_type":"STRING"},{"index":9,"name":"AQUFLUX","description":"AQUFLUX is a positive real value that sets the fraction of the total influx between the aquifer and the defined cells declared on this keyword. If defaulted the cell face area for each cell is applied and if a value is declared then this value is applied to all cells declared by this record.","units":{"field":"ft2","metric":"m2","laboratory":"cm2"},"default":"1*","value_type":"DOUBLE","dimension":"Length*Length"},{"index":10,"name":"AQUCOEF","description":"AQUCOEF is a real positive values that scales the calculated connection between the aquifer and the cells declared on this record.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0","value_type":"DOUBLE","dimension":"1"},{"index":11,"name":"AQUOPT","description":"AQUOPT is a character string that sets the cell face connection and should be set to one of the following: YES: Aquifer connections can adjoin to active cells allowing for connections inside the reservoir grid. It is not recommended to use this option without thoroughly checking the connections in the model. NO: Aquifer connections cannot adjoin to active cells preventing connections inside the reservoir grid. This is the recommended and the default value.","units":{},"default":"NO","value_type":"STRING"}],"example":"The following example defines aquifer number one connected to the I+ face of various cells in the model.\n--\n-- ANALYTIC AQUIFER CONNECTION\n--\n-- ID ---------- BOX --------- CONNECT AQF AQF ADJOIN\n-- NUMBER I1 I2 J1 J2 K1 K2 FACE INFLX MULTI CELLS\nAQUANCON\n1 57 57 28 36 46 58 'I+' 1* 1* 'NO' /\n1 111 111 38 41 22 31 'I+' 1* 1* 'NO' /\n1 96 96 44 49 22 31 'I+' 1* 1* 'NO' /\n1 43 43 28 35 54 58 'I+' 1* 1* 'NO' /\n1 98 98 38 42 32 40 'I+' 1* 1* 'NO' /\n1 79 79 41 67 5 11 'I+' 1* 1* 'NO' /\n1 61 61 48 72 12 17 'I+' 1* 1* 'NO' /\n/\nSee the AQUCT keyword in the GRID section for a complete example on defining and connecting a Carter-Tracy aquifer to a simulation grid.\n| Note If the AQUANCON keyword has been utilized in the run deck then OPM Flow will write the AQUIFERA array to the *.INIT file in order to visualize the aquifer connections in OPM ResInsight. This is accomplished by setting the AQUIFERA value to 2^(AQUID-1) for cells connected to aquifer AQUID. If a cell is connected to multiple analytical aquifers then AQUIFERA is summed for all aquifers connected to a cell. Note that connecting cells to multiple aquifers is best avoided. |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":11,"size_kind":"list"},"AQUCON":{"name":"AQUCON","sections":["GRID"],"supported":null,"summary":"AQUCON keyword defines how numerical aquifers are connected to the simulation grid and these type of aquifers are characterized by the AQUNUM keyword in the GRID section. Analytical aquifers are connected to the simulation grid by the AQUANCON keyword in the GRID section, this includes the Carter-Tracy and Fetkovich analytical aquifers, both of which are implemented in OPM Flow. Both aquifer types dimensions are declared by the AQUDIMS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"AQUID","description":"AQUID is a positive integer greater than or equal to one and less than or equal to the maximum number of numerical aquifers as defined by the MXNAQN variable on the AQUDIMS keyword in the RUNSPEC section, that defines the aquifer to be connected to the grid.","units":{},"default":"None","value_type":"INT"},{"index":2,"name":"I1","description":"A positive integer that defines the lower bound of the cells in the I-direction to be connected to the aquifer and must be greater than or equal to one and less than or equal to I2 and NX.","units":{},"default":"1","value_type":"INT"},{"index":3,"name":"I2","description":"A positive integer that defines the upper bound of the cells in the I-direction to be connected to the aquifer and must be greater than or equal to I1 and less than or equal to NX","units":{},"default":"NX","value_type":"INT"},{"index":4,"name":"J1","description":"A positive integer that defines the lower bound of the cells in the J-direction to be connected to the aquifer and must be greater than or equal to one and less than or equal to J2 and NY.","units":{},"default":"1","value_type":"INT"},{"index":5,"name":"J2","description":"A positive integer that defines the upper bound of the cells in the J-direction to be connected to the aquifer and must be greater than or equal to JI and less than or equal to NY.","units":{},"default":"NY","value_type":"INT"},{"index":6,"name":"K1","description":"A positive integer that defines the lower bound of the cells in the K-direction to be to be connected to the aquifer and must be greater than or equal to one and less than or equal to K2 and NZ.","units":{},"default":"1","value_type":"INT"},{"index":7,"name":"K2","description":"A positive integer that defines the upper bound of the cells in the K-direction to be connected to the aquifer and must be greater than or equal to KI and less than or equal to NZ.","units":{},"default":"NZ","value_type":"INT"},{"index":8,"name":"AQUFACE","description":"AQUFACE is a character string that sets the connection “face” of the cells declared by this record and should be set to one of the following: X+, Y+, or Z+ for the positive direction, or X-, Y- or Z- for the negative direction transmissibilities. I+, J+, or K+ for the positive direction, or I-, J- or K- for the negative direction transmissibilities.","units":{},"default":"None","value_type":"STRING"},{"index":9,"name":"AQUMULT","description":"AQUMULT is a positive real number greater than or equal to zero that scales the OPM Flow calculated transmissibility between the AQUID aquifer and the grid cell connections defined by this record. The default value of one sets the transmissibility between the aquifer and grid cells to the OPM Flow calculated value.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0","value_type":"DOUBLE"},{"index":10,"name":"AQUOPT1","description":"AQUOPT1 is a defined integer value set to either zero or one, that defines the area to be used in calculating the connection transmissibility between the aquifer and the grid cells: A value of zero means the cross-sectional defined on the AQUNUM keyword will be used, whereas, A value of one means the cross-sectional defined by the grid cell connections defined by this record will be used.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0","value_type":"INT"},{"index":11,"name":"AQUOPT2","description":"AQUOPT2 is a character string that sets the cell face connection and should be set to one of the following: YES: Aquifer connections can adjoin to active cells allowing for connections inside the reservoir grid. It is not recommended to use this option without thoroughly checking the connections in the model. NO: Aquifer connections cannot adjoin to active cells preventing connections inside the reservoir grid. This is the recommended and the default value.","units":{},"default":"NO","value_type":"STRING"},{"index":12,"name":"VEOPT1","description":"Vertical Equilibrium Option Number 1– Not Used","units":{},"default":"1","value_type":"DOUBLE"},{"index":13,"name":"VEOPT2","description":"Vertical Equilibrium Option Number 2– Not Used","units":{},"default":"1","value_type":"DOUBLE"}],"example":"The following example defines numerical aquifer number one connected to the I+ face of various cells in the model.\n--\n-- NUMERICAL AQUIFER CONNECTIONS\n--\n-- ID ---------- BOX --------- CONNECT TRANS TRANS ADJOIN\n-- NUMBER I1 I2 J1 J2 K1 K2 FACE MULT OPTN CELLS\nAQUCON\n1 57 57 28 36 46 58 'I+' 1* 1* 'NO' /\n1 111 111 38 41 22 31 'I+' 1* 1* 'NO' /\n1 96 96 44 49 22 31 'I+' 1* 1* 'NO' /\n1 43 43 28 35 54 58 'I+' 1* 1* 'NO' /\n1 98 98 38 42 32 40 'I+' 1* 1* 'NO' /\n1 79 79 41 67 5 11 'I+' 1* 1* 'NO' /\n1 61 61 48 72 12 17 'I+' 1* 1* 'NO' /\n/\nSee the AQUNUM keyword in the GRID section for a complete example on defining and connecting a numerical aquifer to a simulation grid.\n| Note If the AQUCON keyword has been utilized in the run deck then OPM Flow will write the AQUIFERN array to the *.INIT file in order to visualize the aquifer connections in OPM ResInsight. This is accomplished by setting the AQUIFERN value to 2^(AQUID-1) for cells connected to aquifer AQUID. If a cell is connected to multiple numerical aquifers then AQUIFERN is summed for all aquifers connected to a cell. Note that connecting cells to multiple aquifers is best avoided. Finally, for cells representing the numerical aquifers themselves, AQUIFERN is set to minus AQUID. |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":13,"size_kind":"list"},"AQUCT":{"name":"AQUCT","sections":["GRID","PROPS","SOLUTION","SCHEDULE"],"supported":null,"summary":"The AQUCT keyword defines Carter-Tracy112\n Carter, R. D. and Tracy, G. W. “An Improved Method for Calculating Water Influx,” Transactions of AIME (1960) 219, 215-417. 113\n Van Everdingen, A. & Hurst, W.,.The Application of the Laplace Transformation to Flow Problems in Reservoirs. Petroleum Transactions, AIME (December, 1949).analytical aquifers, the properties of the aquifer, including the Carter-Tracy aquifer influence function associated with the aquifer, defined by the AQUTAB keyword in the PROPS section.","parameters":[{"index":1,"name":"AQUID","description":"A positive integer greater than or equal to one and less than or equal to NANAQU on the AQUDIMS keyword in the RUNSPEC section, that defines the Carter-Tracy aquifer number.","units":{},"default":"1","value_type":"INT"},{"index":2,"name":"DATUM","description":"DATUM is a single positive value that defines the Carter-Tracy reference datum depth for PRESS.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":"Length"},{"index":3,"name":"PRESS","description":"PRESS is a single positive value that defines the aquifer pressure at DATUM. If PRESS is defaulted then the simulator will set the aquifer’s initial reservoir pressure to be in equilibrium with the cells the aquifer is contacted to.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1*","value_type":"DOUBLE","dimension":"Pressure"},{"index":4,"name":"PERM","description":"PERM is a real positive number that assigns the permeability to the aquifer.","units":{"field":"mD","metric":"mD","laboratory":"mD"},"default":"None","value_type":"DOUBLE","dimension":"Permeability"},{"index":5,"name":"PORO","description":"PORO is a real positive number greater than zero and less than or equal to one that assigns the porosity to the aquifer.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":"1"},{"index":6,"name":"RCOMP","description":"RCOMP is a real number defining the total (rock and water) compressibility (Ct) at the DATUM pressure.","units":{"field":"1/psia","metric":"1/barsa","laboratory":"1/atma"},"default":"None","value_type":"DOUBLE","dimension":"1/Pressure"},{"index":7,"name":"RE","description":"RE is a real positive number that defines the Carter-Tracy aquifer external radius.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":"Length"},{"index":8,"name":"DZ","description":"DZ is a real positive number that defines the Carter-Tracy aquifer average net thickness.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":"Length"},{"index":9,"name":"ANGLE","description":"ANGLE is a real positive number that defines the angle of influence, that is the angular connection between the aquifer and the hydrocarbon reservoir. A value of 360o degrees, the default value, indicates that the aquifer completely surrounds the hydrocarbon reservoir.","units":{"field":"degrees","metric":"degrees","laboratory":"degrees"},"default":"360.0","value_type":"DOUBLE","dimension":"1"},{"index":10,"name":"PVTNUM","description":"PVTNUM is positive integer greater than zero and less than the NTPVT variable on the TABDIMS keyword in the RUNSPEC section, that defines the PVTW table allocated to the Carter-Tracy aquifer.","units":{},"default":"1","value_type":"INT"},{"index":11,"name":"AQUTAB","description":"AQUTAB is positive integer greater than zero and less than the NIFTBL variable as declared on the AQUDIMS keyword in the RUNSPEC section, that defines the AQUTAB table allocated to this Carter-Tracy aquifer. The default value of one sets the internal infinite acting Carter-Tracy aquifer influence table not the first table in the AQUTAB keyword in the PROPS section The first table in the AQUTAB keyword is considered to be table number two. The internal table, AQUTAB equal to one, is based on the Radial Flow, Constant Pressure and Constant Terminal Rate Cases for Infinite Reservoirs (Table I) in Van Everdingen and Hurst's 114\n Van Everdingen, A. & Hurst, W.,.The Application of the Laplace Transformation to Flow Problems in Reservoirs. Petroleum Transactions, AIME (December, 1949).paper. Van Everdingen, A. & Hurst, W.,.The Application of the Laplace Transformation to Flow Problems in Reservoirs. Petroleum Transactions, AIME (December, 1949).","units":{},"default":"1","value_type":"INT"},{"index":12,"name":"SALTCON","description":"SALTCON is a real positive number that defines the initial salt concentration in the aquifer, for when with simulator's Brine Model has been activated via the BRINE keyword in the RUNSPEC section. This variable is ignored by OPM Flow.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"0.0","value_type":"DOUBLE","dimension":"Concentration"},{"index":13,"name":"TEMP","description":"TEMP is a real positive number that defines the initial temperature of the aquifer at DATUM for use with OPM Flow's thermal option. The THERMAL keyword in the RUNSPEC section must be activated to use this option.","units":{"field":"oF","metric":"oC","laboratory":"oC"},"default":"1*","value_type":"DOUBLE","dimension":"Temperature"}],"example":"Given the following grid and aquifer dimensions in the RUNSPEC section:\n--\n-- MAX MAX MAX\n-- NDIVIX NDIVIY NDIVIZ\nDIMENS\n20 1 5 /\n-- AQF AQF AQF AQF AQF AQF AQF AQF\n-- MXAQN MXNAQC NIFTBL NRIFTB NANAQU NCAMAX MXNALI MXAAQL\nAQUDIMS\n1* 1* 5 100 1 1* 1* 1* /\nAnd the AQUTAB keyword in the PROPS section\n--\n-- CARTER-TRACY AQUIFER INFLUENCE TABLES\n-- (STARTS FROM TABLE NO. 2, AS DEFAULT IS TABLE NO. 1)\n--\nAQUTAB\n-- DIMLESS DIMLESS\n-- TIME PRESSURE\n-- ------- ---------\n0.01 0.112\n0.05 0.229\n0.10 0.315\n0.15 0.376\n0.20 0.424\n0.22 0.443\n0.24 0.459\n0.26 0.476\n0.28 0.492\n0.30 0.507\n0.32 0.522\n0.34 0.536\n0.36 0.551\n0.38 0.565\n0.40 0.579\n0.42 0.593\n0.44 0.607\n0.46 0.621\n0.48 0.634\n0.50 0.648\n0.60 0.715\n0.70 0.782\n0.80 0.849\n0.90 0.915\n1.00 0.982\n2.00 1.649\n3.00 2.316\n5.00 3.649\n10.00 6.982\n20.00 13.649\n30.00 20.316\n50.00 33.649\n100.00 66.982\n200.00 133.649\n300.00 200.316\n500.00 333.649\n1000.00 666.982 /\nThe Carter-Tracy aquifer is defined in the GRID or SOLUTION sections as:\n-- ==============================================================================\n--\n-- SOLUTION SECTION\n--\n-- ==============================================================================\nSOLUTION\n--\n-- CARTER-TRACY AQUIFER DESCRIPTION\n--\n-- ID DATUM AQF AQF AQF AQF AQF AQF INFL PVT AQU\n-- NUM DEPTH PRESS PERM PORO RCOMP RE DZ ANGLE NUM TAB\n--\nAQUCT\n1 2000.0 269 100.0 0.30 3.0e-5 330 10.0 360.0 1 2 /\n/\nAnd the connection of the aquifer is set in the GRID or SOLUTION sections as:\n--\n-- ANALYTIC AQUIFER CONNECTION\n--\n-- ID ---------- BOX --------- CONNECT AQF AQF ADJOIN\n-- NUMBER I1 I2 J1 J2 K1 K2 FACE INFLX MULTI CELLS\nAQUANCON\n1 1 1 1 1 1 1 J- 1.0 1.0 'NO' /\n/\nHere one Carter-Tracy aquifer is connected to a single cell (1, 1, 1) at the J- face (or X- face) of the cell.\n| Note OPM Flow includes the infinite acting Carter-Tracy aquifer influence table as a default for table number one; thus data entered on AQUTAB keyword starts from table number two. |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":13,"size_kind":"list"},"AQUNNC":{"name":"AQUNNC","sections":["GRID"],"supported":false,"summary":"The AQUNNC keyword defines Numerical Aquifer Non-Neighbor Connections.","parameters":[{"index":1,"name":"AQUIFER_ID","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"IX","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"IY","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"IZ","description":"","units":{},"default":"","value_type":"INT"},{"index":5,"name":"JX","description":"","units":{},"default":"","value_type":"INT"},{"index":6,"name":"JY","description":"","units":{},"default":"","value_type":"INT"},{"index":7,"name":"JZ","description":"","units":{},"default":"","value_type":"INT"},{"index":8,"name":"TRAN","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Transmissibility"},{"index":9,"name":"IST1","description":"","units":{},"default":"","value_type":"INT"},{"index":10,"name":"IST2","description":"","units":{},"default":"","value_type":"INT"},{"index":11,"name":"IPT1","description":"","units":{},"default":"","value_type":"INT"},{"index":12,"name":"IPT2","description":"","units":{},"default":"","value_type":"INT"},{"index":13,"name":"ZF1","description":"","units":{},"default":"","value_type":"STRING"},{"index":14,"name":"ZF2","description":"","units":{},"default":"","value_type":"STRING"},{"index":15,"name":"DIFF","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"}],"example":"","expected_columns":15,"size_kind":"list"},"AQUNUM":{"name":"AQUNUM","sections":["GRID"],"supported":null,"summary":"The AQUNUM keyword defines the properties of numerical aquifers, including which grid blocks in the model should be utilized as part of the numerical aquifer. Each row entry in the AQUNUM keyword defines one numerical aquifer. Note that a numerical aquifer may consists of more than one grid cell, in order to better describe the water influx from the aquifer to the grid.","parameters":[{"index":1,"name":"AQUID","description":"AQUID is a positive integer greater than or equal to one and less than or equal to the maximum number of numerical aquifers as defined by the MXNAQN variable on the AQUDIMS keyword in the RUNSPEC section, that defines the aquifer to be connected to the grid.","units":{},"default":"None","value_type":"INT"},{"index":2,"name":"I","description":"A positive integer that defines the cell in the I-direction that represents the AQUID aquifer, and which must be greater than or equal to one and less than or equal to NX.","units":{},"default":"None","value_type":"INT"},{"index":3,"name":"J","description":"A positive integer that defines the cell in the J-direction that represents the AQUID aquifer, and which must be greater than or equal to one and less than or equal to NY.","units":{},"default":"None","value_type":"INT"},{"index":4,"name":"K","description":"A positive integer that defines the cell in the K-direction that represents the AQUID aquifer, and which must be greater than or equal to one and less than or equal to NZ.","units":{},"default":"None","value_type":"INT"},{"index":5,"name":"AREA","description":"AREA is a real positive value that defines the cross-sectional area of the aquifer used in calculating the aquifer connection transmissibility. The actual transmissibility between the numerical aquifer and the connected grid cell is the harmonic average of the aquifer connection transmissibility and the calculated connected cell transmissibility. The value entered for AREA does not effect the visualization of the cell in OPM ResInsight, as it is only used in calculating the transmissibility. Note that the AQUOPT1 variable on the AQUCON keyword in the GRID section allows one to use the value entered for AREA or to use the grid cell cross-sectional area instead for the transmissibility calculation.","units":{"field":"ft2","metric":"m2","laboratory":"cm2"},"default":"None","value_type":"DOUBLE","dimension":"Length*Length"},{"index":6,"name":"LENGTH","description":"LENGTH is a real positive value that defines the length of the numerical aquifer. Similar to the AREA variable, LENGTH is not constrained by the original host cell size and the value entered does not effect the visualization of the cell in OPM ResInsight.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":"Length"},{"index":7,"name":"PORO","description":"PORO is a real positive number greater than zero and less than or equal to one that assigns the porosity to the numerical aquifer.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":"1"},{"index":8,"name":"PERM","description":"PERM is a real positive number that assigns the permeability to the numerical aquifer.","units":{"field":"mD","metric":"mD","laboratory":"mD"},"default":"None","value_type":"DOUBLE","dimension":"Permeability"},{"index":9,"name":"DATUM","description":"DATUM is a real positive number that sets the reference datum depth of the numerical aquifer. Similar to the AREA variable, DATUM is not constrained by the original host cell depth and the value entered does not effect the visualization of the cell in OPM ResInsight. If defaulted then the depth of cell (I, J, K) will be used","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"Cell Depth","value_type":"DOUBLE","dimension":"Length"},{"index":10,"name":"PRESS","description":"PRESS is a single positive value that defines the numerical aquifer pressure at DATUM. If PRESS is defaulted then the simulator will set the aquifer’s initial reservoir pressure to be in equilibrium with the cells the aquifer is contacted to. This is the preferred manner to initialize the numerical aquifer.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1*","value_type":"DOUBLE","dimension":"Pressure"},{"index":11,"name":"PVTNUM","description":"PVTNUM is positive integer greater than zero and less than the NTPVT variable on the TABDIMS keyword in the RUNSPEC section, that defines the PVTW table allocated to the numerical aquifer. If defaulted then the PVT tables allocated to cell (I, J, K) will be used.","units":{},"default":"Cell PVTNUM","value_type":"INT"},{"index":12,"name":"SATNUM","description":"SATNUM is positive integer greater than zero and less than the NTSFUN variable on the TABDIMS keyword in the RUNSPEC section, that defines the saturation tables allocated to the numerical aquifer. If defaulted then the saturation tables allocated to cell (I, J, K) will be used.","units":{},"default":"Cell SATNUM","value_type":"INT"}],"example":"Given the following grid and aquifer dimensions in the RUNSPEC section:\n--\n-- MAX MAX MAX\n-- NDIVIX NDIVIY NDIVIZ\nDIMENS\n96 58 28 /\n-- AQF AQF AQF AQF AQF AQF AQF AQF\n-- MXAQN MXNAQC NIFTBL NRIFTB NANAQU NCAMAX MXNALI MXAAQL\nAQUDIMS\n3 3 1* 1* 1* 1* 1* 1* /\nThe following numerical aquifer definition:\n--\n-- NUMERICAL AQUIFER DESCRIPTION\n--\n-- AQUID - LOCATION - AQF AQF AQF AQF AQF AQF PVT SATNUM\n-- NUMBER I J K AREA LENGTH PORO PERM DATUM PRES TAB TAB\n--\nAQUNUM\n1 1 3 28 5.20E03 2.0E3 0.05 0.3 1* 1* 1* 1* /\n1 1 2 28 5.20E06 2.0E6 0.05 0.3 1* 1* 1* 1* /\n1 1 1 28 5.20E09 2.0E9 0.05 0.3 1* 1* 1* 1* /\n/\ndefines one numerical aquifer consisting of three cells. The connection to the grid cells would take the form of:\n--\n-- NUMERICAL AQUIFER CONNECTIONS\n--\n-- ID ---------- BOX --------- CONNECT TRANS TRANS ADJOIN\n-- NUMBER I1 I2 J1 J2 K1 K2 FACE MULT OPTN CELLS\nAQUCON\n1 1 1 4 58 28 28 'K+' 1.3 1* 1* /\n1 2 96 1 58 28 28 'K+' 1.3 1* 1* /\n/\nthat creates a basal aquifer115\n Basal Aquifer: An aquifer located at the bottom of a geologic unit..\nBasal Aquifer: An aquifer located at the bottom of a geologic unit.\n| Note If the AQUCON keyword has been utilized in the run deck then OPM Flow will write the AQUIFERN array to the *.INIT file in order to visualize the aquifer connections in OPM ResInsight. This is accomplished by setting the AQUIFERN value to 2^(AQUID-1) for cells connected to aquifer AQUID. If a cell is connected to multiple numerical aquifers then AQUIFERN is summed for all aquifers connected to a cell. Note that connecting cells to multiple aquifers is best avoided. Finally for cells representing the numerical aquifers themselves, AQUIFERN is set to minus AQUID. |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":12,"size_kind":"list"},"AUTOCOAR":{"name":"AUTOCOAR","sections":["GRID"],"supported":false,"summary":"The AUTOCOAR keyword defines an area in the global grid that should be coarsen for when the AUTOREF keyword has been declared in the RUNSPEC section.","parameters":[{"index":1,"name":"I1","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"I2","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"J1","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"J2","description":"","units":{},"default":"","value_type":"INT"},{"index":5,"name":"K1","description":"","units":{},"default":"","value_type":"INT"},{"index":6,"name":"K2","description":"","units":{},"default":"","value_type":"INT"},{"index":7,"name":"NX","description":"","units":{},"default":"","value_type":"INT"},{"index":8,"name":"NY","description":"","units":{},"default":"","value_type":"INT"},{"index":9,"name":"NZ","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":9,"size_kind":"list"},"BCCON":{"name":"BCCON","sections":["GRID"],"supported":true,"summary":"The BCCON keyword defines the grid connections for the boundary conditions.","parameters":[{"index":1,"name":"INDEX","description":"A positive integer that identifies the boundary condition.","units":{},"default":"None","value_type":"INT"},{"index":2,"name":"I1","description":"A positive integer that defines the lower bound of the grid in the I-direction for which the boundary conditions are to be applied, must be greater than or equal 1 and less than or equal to I2 and NX.","units":{},"default":"1","value_type":"INT"},{"index":2,"name":"I2","description":"A positive integer that defines the upper bound of the grid in the I-direction for which the boundary conditions are to be applied, must be greater than or equal to II and less than or equal to NX","units":{},"default":"NX","value_type":"INT"},{"index":3,"name":"J1","description":"A positive integer that defines the lower bound of the grid in the J-direction for which the boundary conditions are to be applied, must be greater than or equal 1 and less than or equal to J2 and NY.","units":{},"default":"1","value_type":"INT"},{"index":4,"name":"J2","description":"A positive integer that defines the upper bound of the grid in the J-direction for which the boundary conditions are to be applied, must be greater than or equal to JI and less than or equal to NY.","units":{},"default":"NY","value_type":"INT"},{"index":5,"name":"K1","description":"A positive integer that defines the lower bound of the grid in the K-direction for which the boundary conditions are to be applied, must be greater than or equal to one and less than or equal to K2 and NZ.","units":{},"default":"1","value_type":"INT"},{"index":6,"name":"K2","description":"A positive integer that defines the upper bound of the grid in the K-direction for which the boundary conditions are to be applied, must be greater than or equal to KI and less than or equal to NZ.","units":{},"default":"NZ","value_type":"INT"},{"index":7,"name":"DIRECT","description":"A character string that defines the direction to apply the boundary conditions, and should be set to one of the following X, Y, or Z for the positive direction, or X-, Y- or Z- for the negative direction.","units":{},"default":"None","value_type":"INT"},{"index":8,"name":"DIRECTION","description":"","units":{},"default":"","value_type":"STRING"}],"example":"The first example shows how to set a constant pressure boundary using TYPE equal to FREE:\n--\n-- DEFINE BOUNDARY CONDITIONS CONNECTION (OPM FLOW GRID KEYWORD)\n--\n--INDEX ---------- BOX --------- BC\n-- I1 I2 J1 J2 K1 K2 DIRC\nBCCON\n1 1 1 1 1* 1 1* X- /\n2 1 1* 1 1 1 1* Y /\n/\n--\n-- DEFINE BOUNDARY CONDITIONS PROPERTIES (OPM FLOW SCHEDULE KEYWORD)\n--\n--INDEX BC BC BC BC BC\n-- TYPE PHASE RATE PRESS TEMP\nBCPROP\n1 FREE 1* 1* 1* 1* /\n2 FREE /\n/\nWith this option it is only necessary to define the boundary cells and all the other parameters (COMPONENT, RATE, PRESS, and TEMP) can be defaulted, as they are ignored when TYPE equals FREE.\nThe next example is based on NX, NY and NZ equal to 20, 1, 10 respectively, on the DIMENS keyword in the RUNSPEC section, and shows how different boundary types can be assigned to different parts of the model.\n--\n-- DEFINE BOUNDARY CONDITIONS CONNECTION (OPM FLOW GRID KEYWORD)\n--\n--INDEX ---------- BOX --------- BC\n-- I1 I2 J1 J2 K1 K2 DIRC\nBCCON\n1 1 1 1 1 1 10 X- /\n2 20 20 1 1 1 10 X /\n/\n--\n-- DEFINE BOUNDARY CONDITIONS PROPERTIES (OPM FLOW SCHEDULE KEYWORD)\n--\n--INDEX BC BC BC BC BC\n-- TYPE PHASE RATE PRESS TEMP\nBCPROP\n1 DIRICHLET GAS 1* 256.0 100.0 /\n2 FREE 4* /\n/\nThe last example shows how the DIRICHLET boundary condition option may be used:\n--\n-- DEFINE BOUNDARY CONDITIONS CONNECTION (OPM FLOW GRID KEYWORD)\n--\n--INDEX ---------- BOX --------- BC\n-- I1 I2 J1 J2 K1 K2 DIRC\nBCCON\n1 1 1 1 1* 1 1* X- /\n2 1 1* 1 1 1 1* Y /\n/\n--\n-- DEFINE BOUNDARY CONDITIONS PROPERTIES (OPM FLOW SCHEDULE KEYWORD)\n--\n--INDEX BC BC BC BC BC\n-- TYPE PHASE RATE PRESS TEMP\nBCPROP\n1 DIRICHLET WAT 1* 256.0 100.0 /\n2 DIRICHLET WAT 1* 1* 100.0 /\n/\nHere, the first line sets both the pressure and temperature at the boundary, and the second line defaults the pressure entry, so that the simulator calculated initial boundary pressure will be used.\n| Note This is an OPM Flow specific keyword and will therefore cause an error in the commercial simulator. |\n|----------------------------------------------------------------------------------------------------------|","expected_columns":8,"size_kind":"list"},"BOUNDARY":{"name":"BOUNDARY","sections":["GRID","EDIT","REGIONS","SOLUTION","SCHEDULE"],"supported":false,"summary":"The BOUNDARY keyword defines a rectangular grid for printing various arrays to the output print file (*.PRT); thus, avoiding printing all the elements in the selected array.","parameters":[{"index":1,"name":"IX1","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"IX2","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"JY1","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"JY2","description":"","units":{},"default":"","value_type":"INT"},{"index":5,"name":"KZ1","description":"","units":{},"default":"","value_type":"INT"},{"index":6,"name":"KZ2","description":"","units":{},"default":"","value_type":"INT"},{"index":7,"name":"ORIENTATION_INDEX","description":"","units":{},"default":"1","value_type":"INT"},{"index":8,"name":"DUAL_PORO_FLAG","description":"","units":{},"default":"BOTH","value_type":"STRING"}],"example":"","expected_columns":8,"size_kind":"fixed","size_count":1},"BOX":{"name":"BOX","sections":["GRID","EDIT","PROPS","REGIONS","SOLUTION","SCHEDULE"],"supported":null,"summary":"BOX defines a range of grid blocks for which subsequent data is assigned for all the cells in the defined BOX. Values are set for cells within the defined box grid using natural reading order, initially along the I-direction then J-direction and finally the K-direction. If fewer values are assigned than exist within the defined block space, then subsequent values are set starting from the next block that was not previously assigned for that property. This is the same behavior as applies to setting grid properties for an unboxed grid.","parameters":[{"index":1,"name":"I1","description":"A positive integer that defines the lower bound of the array in the I-direction to be modified must be greater than or equal 1 and less than or equal to I2 and NX.","units":{},"default":"1","value_type":"INT"},{"index":2,"name":"I2","description":"A positive integer that defines the upper bound of the array in the I-direction to be modified must be greater than or equal to II and less than or equal to NX","units":{},"default":"NX","value_type":"INT"},{"index":3,"name":"J1","description":"A positive integer that defines the lower bound of the array in the J-direction to be modified must be greater than or equal 1 and less than or equal to J2 and NY.","units":{},"default":"1","value_type":"INT"},{"index":4,"name":"J2","description":"A positive integer that defines the upper bound of the array in the J-direction to be modified must be greater than or equal to JI and less than or equal to NY.","units":{},"default":"NY","value_type":"INT"},{"index":5,"name":"K1","description":"A positive integer that defines the lower bound of the array in the K-direction to be modified must be greater than or equal to one and less than or equal to K2 and NZ.","units":{},"default":"1","value_type":"INT"},{"index":6,"name":"K2","description":"A positive integer that defines the upper bound of the array in the K-direction to be modified must be greater than or equal to KI and less than or equal to NZ.","units":{},"default":"NZ","value_type":"INT"}],"example":"--\n-- DEFINE A BOX GRID FOR THE BOTTOM LAYER OF A 100 X 100 X 20 MODEL\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1* 1* 1* 1* 20 20 / SELECT THE BOTTOM LAYER\n--\n-- DEFINE THE POROSITY AND OTHER PROPERTIES ON THE BOX GRID\n--\nPORO\n10000*0.300 /\nPERMX\n5000*100.0 5000*75.0 /\nNTG\n10000*0.500 /\n--\n-- RESET THE INPUT BOX TO BE THE FULL MODEL\n--\nENDBOX\nThe above example set the BOX grid to be the last layer in the model which means that 100 x 100, that is 10,000 values need to entered for each property.\nAlternatively, one could use the EQUALS keyword to accomplish the same thing.\n-- -- ARRAY CONSTANT -- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\n'PORO’ 0.3000 1* 1* 1* 1* 20 20 / PORO TO 0.30 IN LAYER 20\n'PERMX' 100.00 1* 1* 1 50 20 20 / PERMX TO 100. IN LAYER 20\n'PERMX' 75.00 1* 1* 51 100 20 20 / PERMX TO 75.0 IN LAYER 20\n'NTG’ 0.5000 1* 1* 1* 1* 20 20 / NTG TO 0.50 IN LAYER 20\n/\nNote\nIt is good practice to always use the ENDBOX keyword to reset the input back to the full grid when all the modifications for a sub-grid have been completed.\n| Note It is good practice to always use the ENDBOX keyword to reset the input back to the full grid when all the modifications for a sub-grid have been completed. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":6,"size_kind":"fixed","size_count":1},"BTOBALFA":{"name":"BTOBALFA","sections":["GRID"],"supported":false,"summary":"The BTOBALFA keyword defines a dual porosity matrix to fracture multiplier that is applied to all cells, for when the Dual Porosity model has been activated by either the DUALPORO or the DUALPERM keywords in the RUNSPEC section.","parameters":[{"index":1,"name":"VALUE","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"BTOBALFV":{"name":"BTOBALFV","sections":["GRID"],"supported":false,"summary":"The BTOBALFV keyword defines a dual porosity matrix to fracture multiplier that is applied to individual cells, for when the Dual Porosity model has been invoked by either the DUALPORO or the DUALPERM keywords in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"CARFIN":{"name":"CARFIN","sections":["GRID"],"supported":false,"summary":"CARFIN defines a Cartesian Local Grid Refinement (“LGR”) in a cell or a group of cells in the host grid, for when LGRs have been activated for the input deck using the LGR keyword in the RUNSPEC section. The keyword marks the start of an LGR description section and all subsequent keywords between the CARFIN and ENDFIN keywords are deemed to be associated with the current LGR and not the host grid.","parameters":[{"index":1,"name":"LGRNAME","description":"A character string of up to eight characters in length that defines the LGR name for which the LGR is being being defined.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"I1","description":"A positive integer that defines the lower index of the global or host grid in the I-direction to be refined; must be greater than or equal 1 and less than or equal to I2 and NX on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":3,"name":"I2","description":"A positive integer that defines the upper index of the global or host grid in the I-direction to be refined; must be greater than or equal 1 and II, and less than or equal to NX on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":4,"name":"J1","description":"A positive integer that defines the lower index of the global or host grid in the J-direction to be refined; must be greater than or equal 1 and less than or equal to J2 and NY on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":5,"name":"J2","description":"A positive integer that defines the upper index of the global or host grid in the J-direction to be refined; must be greater than or equal 1 and JI, and less than or equal to NY on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":6,"name":"K1","description":"A positive integer that defines the lower index of the global or host grid in the K-direction to be refined; must be greater than or equal 1 and less than or equal to K2 and NZ on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":7,"name":"K2","description":"A positive integer that defines the upper index of the global or host grid in the K-direction to be refined; must be greater than or equal 1 and KI, and less than or equal to NZ on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":8,"name":"NX","description":"A positive integer value that defines the number of LGR grid blocks in the x direction for Cartesian grids or the number of grid blocks in the r direction for radial grids","units":{},"default":"None","value_type":"INT"},{"index":9,"name":"NY","description":"A positive integer value that defines the number of LGR grid blocks in the y direction for Cartesian grids or the number of grid blocks in the theta direction for radial grids.","units":{},"default":"None","value_type":"INT"},{"index":10,"name":"NZ","description":"A positive integer value that defines the number of LGR grid blocks in the z direction for both Cartesian and radial grids.","units":{},"default":"None","value_type":"INT"},{"index":11,"name":"MXWELS","description":"A positive integer defining the maximum number of wells contained in this LGR.","units":{},"default":"None","value_type":"INT"},{"index":12,"name":"HOSTNAME","description":"A character string of up to eight characters in length that defines the host grid name for nested refinements. The default value of “GLOBAL” sets the host name to the global grid, that is for a conventional LGR. A nested refinement is when the HOSTNAME is a previously declared LGR for which the current LGR is specifying a further LGR refinement.","units":{},"default":"GLOBAL","value_type":"STRING"}],"example":"The example below defines an LGR in the global grid, named LGR-OP01 with a maximum of one well allowed in the LGR.\n--\n-- CARFIN LGR GRID COMMANDS\n--\n-- LGR ----- HOST GRID ------ -- CARFIN GRID -- MAX HOST\n-- NAME I1 I2 J1 J2 K1 K2 NX NY NZ WELLS NAME\nCARFIN\nLGR-OP01 24 24 87 87 1 50 3 3 50 1 GLOBAL /\nENDFIN\nHere the one global cell in the areal plane (24, 87) is divided into three LGR cells in the x-direction and three cells in the y-direction. Since no other property data is given, then the LGR cells take their properties from the host grid, that is the global grid.","expected_columns":12,"size_kind":"fixed","size_count":1},"COALNUM":{"name":"COALNUM","sections":["GRID"],"supported":false,"summary":"The COALNUM keyword defines the coal region numbers for each grid block used with the Coal Bed Methane option (“CBM”). OPM Flow does not have a CBM option; however, the keyword is documented here for completeness.","parameters":[{"index":1,"name":"COALNUM","description":"COALNUM defines an array of positive integers assigning a grid cell to a particular coal region. The maximum number of COALNUM regions is set by the NTCREG variable on REGDIMS keywords in the RUNSPEC section.","units":{},"default":"1"}],"example":"The example below sets three COALNUM regions for a 4 x 5 x 2 model.\n--\n-- DEFINE COALNUM REGIONS FOR ALL CELLS\n--\nCOALNUM\n2 2 1 1 2 2 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n3 3 1 1 3 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n/\nThe above will no effect in an OPM Flow input deck.","size_kind":"array"},"COARSEN":{"name":"COARSEN","sections":["GRID"],"supported":false,"summary":"The COARSEN keyword defines how a set of cells should be coarsened for when the Local Grid Refinement (“LGR”) option has been activated by LGR keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"I1","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"I2","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"J1","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"J2","description":"","units":{},"default":"","value_type":"INT"},{"index":5,"name":"K1","description":"","units":{},"default":"","value_type":"INT"},{"index":6,"name":"K2","description":"","units":{},"default":"","value_type":"INT"},{"index":7,"name":"NX","description":"","units":{},"default":"","value_type":"INT"},{"index":8,"name":"NY","description":"","units":{},"default":"","value_type":"INT"},{"index":9,"name":"NZ","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":9,"size_kind":"fixed","size_count":1},"COLLAPSE":{"name":"COLLAPSE","sections":["GRID"],"supported":false,"summary":"The COLLAPSE keyword defines the which cells can be collapsed in a collapsed Vertical Equilibrium (“VE”) run when the VE option has been invoked via the VE keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"VALUE","description":"","units":{},"default":"1","value_type":"INT"}],"example":"","expected_columns":1,"size_kind":"list"},"COORD":{"name":"COORD","sections":["GRID"],"supported":null,"summary":"COORD defines a set of coordinate lines or pillars for a reservoir grid via an array. A total of 6 x (NX+1) x (NY+1) values must be specified for each coordinate data set (or reservoir). For multiple reservoirs, where NUMRES is greater than one, there must be 6 x (NX+1) x (NY+1) x NUMRES values. In OPM Flow NUMRES can only be set to one.","parameters":[{"index":1,"name":"X1-Column","description":"Top X coordinate","units":{},"default":"None"},{"index":2,"name":"Y1-Column","description":"Top Y coordinate","units":{},"default":""},{"index":3,"name":"Z1-Column","description":"Top Z coordinate","units":{},"default":""},{"index":4,"name":"X2-Column","description":"Base X coordinate","units":{},"default":""},{"index":5,"name":"Y2-Column","description":"Base Y coordinate","units":{},"default":""},{"index":6,"name":"Z2-Column","description":"Base Z coordinate","units":{},"default":""}],"example":"--\n-- SPECIFY VERTICAL COORDINATE LINES FOR A REGULAR 3 x 2 GRID\n-- (DX = 100 and DY = 200)\n--\n-- X1 Y1 Z1 X2 Y2 Z2\n-- --- --- ---- --- --- ----\nCOORD\n0 0 1000 0 0 5000\n100 0 1000 100 0 5000\n200 0 1000 200 0 5000\n300 0 1000 300 0 5000\n0 200 1000 0 200 5000\n100 200 1000 100 200 5000\n200 200 1000 200 200 5000\n300 200 1000 300 200 5000\n0 400 1000 0 400 5000\n100 400 1000 100 400 5000\n200 400 1000 200 400 5000\n300 400 1000 300 400 5000\n/\nThe above example defines vertical coordinate lines for a regular 3 by 2 grid with DX equal to 100 and DY equal to 200.","size_kind":"array"},"COORDSYS":{"name":"COORDSYS","sections":["GRID"],"supported":false,"summary":"This keyword sets various options for when multiple grid systems are being used, as declared by the NUMRES keyword in the RUNSPEC section. OPM Flow does not support multiple grid systems. The keyword is also used to stipulate for radial grids if the completion of the circle in the THETA direction should be implemented using non-neighbor connections.","parameters":[{"index":1,"name":"K1","description":"A positive integer that defines the lower bound of the array in the K-direction for the given grid system.","units":{},"default":"None","value_type":"INT"},{"index":2,"name":"K2","description":"A positive integer that defines the upper bound of the array in the K-direction for the given grid system.","units":{},"default":"None","value_type":"INT"},{"index":3,"name":"COMPLETE","description":"COMPLETE is a defined character string that determines for radial grids if the circle should be completed in THETA direction, and should be set to COMP to complete the circle, or INCOMP for not completing the circle.","units":{},"default":"INCOMP","value_type":"STRING"},{"index":4,"name":"CONNECT","description":"A defined character string that declares how the reservoir below should be connected to the given reservoir, and should be set to JOIN to connect the two reservoirs by calculating the inter-reservoir transmissibilities, or SEPARATE to isolate the reservoirs.","units":{},"default":"SEPARATE","value_type":"STRING"},{"index":5,"name":"R1","description":"R1 is a positive integer defining the lower reservoir unit that is is connected to the given reservoir unit.","units":{},"default":"Current Reservoir Record","value_type":"INT"},{"index":6,"name":"R2","description":"R2 is a positive integer defining the upper reservoir unit that is is connected to the given reservoir unit.","units":{},"default":"","value_type":"INT"}],"example":"--\n-- DEFINE COORDINATE GRID OPTIONS\n--\n-- K1 K2 COMP CONNECT LOWER UPPER\n-- Layer Layer CIRCLE RES RES RES\nCOORDSYS\n1 1 COMP /\n/\nThe above example connects the circle in the THETA direction for the RADIAL model, for when the number of grids have been set to one via the NUMRES keyword in the SCHEDULE section.","expected_columns":6,"size_kind":"fixed"},"COPY":{"name":"COPY","sections":["GRID","EDIT","PROPS","REGIONS","SOLUTION"],"supported":false,"summary":"The COPY keyword copies an array (or part of an array) to another array or part of an array. The arrays can be integer or real valued; however, the arrays that can be operated on are dependent on which section the COPY keyword is being applied in.","parameters":[{"index":1,"name":"ARRAY-1","description":"A character string of up to eight characters in length that defines the keyword identifying the array to be copied from.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"ARRAY-2","description":"A character string of up to eight characters in length that defines the keyword identifying the array to be copied to.","units":{},"default":"None","value_type":"STRING"},{"index":3,"name":"I1","description":"A positive integer that defines the lower bound of the array in the I-direction to be modified must be greater than or equal 1 and less than or equal to I2 and NX.","units":{},"default":"1","value_type":"INT"},{"index":4,"name":"I2","description":"A positive integer that defines the upper bound of the array in the I-direction to be modified must be greater than or equal to II and less than or equal to NX","units":{},"default":"NX","value_type":"INT"},{"index":5,"name":"J1","description":"A positive integer that defines the lower bound of the array in the J-direction to be modified must be greater than or equal 1 and less than or equal to J2 and NY.","units":{},"default":"1","value_type":"INT"},{"index":6,"name":"J2","description":"A positive integer that defines the upper bound of the array in the J-direction to be modified must be greater than or equal to JI and less than or equal to NY.","units":{},"default":"NY","value_type":"INT"},{"index":7,"name":"K1","description":"A positive integer that defines the lower bound of the array in the K-direction to be modified must be greater than or equal to one and less than or equal to K2 and NZ.","units":{},"default":"1","value_type":"INT"},{"index":8,"name":"K2","description":"A positive integer that defines the upper bound of the array in the K-direction to be modified must be greater than or equal to KI and less than or equal to NZ.","units":{},"default":"NZ","value_type":"INT"}],"example":"--\n-- SOURCE DESTIN. ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nCOPY\nPERMX PERMY 1* 1* 1* 1* 1* 1* / CREATE PERMY\nPERMX PERMZ 1* 1* 1* 1* 1* 1* / CREATE PERMZ\n/\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nMULTIPLY\nPERMZ 0.50000 1* 1* 1* 1* 1* 1* / PERMZ * 0.5\n/\nThe above example copies PERMX array to the PERMY and PERMZ arrays in the GRID section for all grid blocks in the model. The PERMZ array is then multiplied by 0.5 for all grid blocks in the model.\n| COPY Keyword and Variable Options by Section | | | | | | |\n|----------------------------------------------|---------|-------|---------|----------|---------|----------|\n| GRID | EDIT | PROPS | REGIONS | SOLUTION | SUMMARY | SCHEDULE |\n| DX | DEPTH | SWL | ENDNUM | PRESSURE | | |\n| DY | PORV | SWCR | EQLNUM | SWAT | | |\n| DZ | TRANX | SWU | FIPNUM | SGAS | | |\n| PERMX | TRANY | SGL | IMBNUM | RV | | |\n| PERMY | TRANZ | SGCR | MISCNUM | RS | | |\n| PERMZ | DIFFX | SGU | PVTNUM | TBLK | | |\n| MULTX | DIFFY | KRW | ROCKNUM | GI | | |\n| MULTY | DIFFZ | KRO | SATNUM | OILAPI | | |\n| MULTZ | TRANR | KRG | WH2NUM | SALT | | |\n| DR | TRANTHT | PCG | | GASCONC | | |\n| DTHETA | DIFFR | PCW | | SOLVCONC | | |\n| PERMR | DIFFTHT | | | SOLVFRAC | | |\n| PERMTHT | | | | SFOAM | | |\n| DZNET | | | | SPOLY | | |\n| PORO | | | | | | |\n| NTG | | | | | | |\n| FLUXNUM | | | | | | |\n| MULTNUM | | | | | | |\n| MPFANUM | | | | | | |\n| DIFFX | | | | | | |\n| DIFFY | | | | | | |\n| DIFFZ | | | | | | |\n| DIFFR | | | | | | |\n| DIFFTHT | | | | | | |","expected_columns":8,"size_kind":"list"},"COPYBOX":{"name":"COPYBOX","sections":["GRID","PROPS","REGIONS"],"supported":false,"summary":"The COPYBOX keyword copies an array (or part of an array) to another part of the same array. The array can be real or integer depending on the array type; however, the array that can be operated on is dependent on which section the COPYBOX keyword is being used.","parameters":[{"index":1,"name":"ARRAY-1","description":"The name of the array to be copied This is the keyword name identifying the property and is up to eight characters in length and enclosed in quotes.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"I1","description":"A positive integer that defines the SOURCE lower bound of the array in the I-direction to be modified must be greater than or equal 1 and less than or equal to I2 and NX.","units":{},"default":"1","value_type":"INT"},{"index":3,"name":"I2","description":"A positive integer that defines the SOURCE upper bound of the array in the I-direction to be modified must be greater than or equal to II and less than or equal to NX","units":{},"default":"NX","value_type":"INT"},{"index":4,"name":"J1","description":"A positive integer that defines the SOURCE lower bound of the array in the J-direction to be modified must be greater than or equal 1 and less than or equal to J2 and NY.","units":{},"default":"1","value_type":"INT"},{"index":5,"name":"J2","description":"A positive integer that defines the SOURCE upper bound of the array in the J-direction to be modified must be greater than or equal to JI and less than or equal to NY.","units":{},"default":"NY","value_type":"INT"},{"index":6,"name":"K1","description":"A positive integer that defines the SOURCE lower bound of the array in the K-direction to be modified must be greater than or equal to one and less than or equal to K2 and NZ.","units":{},"default":"1","value_type":"INT"},{"index":7,"name":"K2","description":"A positive integer that defines the SOURCE upper bound of the array in the K-direction to be modified must be greater than or equal to KI and less than or equal to NZ.","units":{},"default":"NZ","value_type":"INT"},{"index":8,"name":"I3","description":"A positive integer that defines the DESTINATION lower bound of the array in the I-direction to be modified must be greater than or equal 1 and less than or equal to I2 and NX.","units":{},"default":"1","value_type":"INT"},{"index":9,"name":"I4","description":"A positive integer that defines the DESTINATION upper bound of the array in the I-direction to be modified must be greater than or equal to II and less than or equal to NX","units":{},"default":"NX","value_type":"INT"},{"index":10,"name":"J3","description":"A positive integer that defines the DESTINATION lower bound of the array in the J-direction to be modified must be greater than or equal 1 and less than or equal to J2 and NY.","units":{},"default":"1","value_type":"INT"},{"index":11,"name":"J4","description":"A positive integer that defines the DESTINATION upper bound of the array in the J-direction to be modified must be greater than or equal to JI and less than or equal to NY.","units":{},"default":"NY","value_type":"INT"},{"index":12,"name":"K3","description":"A positive integer that defines the DESTINATION lower bound of the array in the K-direction to be modified must be greater than or equal to one and less than or equal to K2 and NZ.","units":{},"default":"1","value_type":"INT"},{"index":13,"name":"K4","description":"A positive integer that defines the DESTINATION upper bound of the array in the K-direction to be modified must be greater than or equal to KI and less than or equal to NZ.","units":{},"default":"NZ","value_type":"INT"}],"example":"--\n-- SOURCE ------ SOURCE BOX ------ ---- DESTINATION BOX ----\n-- ARRAY I1 I2 J1 J2 K1 K2 I1 I2 J1 J2 K1 K2\nCOPYBOX\nPORO 1* 1* 1* 1* 12 14 1* 1* 1* 1* 15 17 / PORO\nPERMX 1* 1* 1* 1* 12 14 1* 1* 1* 1* 15 17 / PERMX\n/\nThe above example copies all the PORO and PERMX values in layers 12 to 14 to layers 15 and 17.\n| COPYBOX Keyword and Variable Options by Section | | | | | | |\n|-------------------------------------------------|------|-------|---------|----------|---------|----------|\n| GRID | EDIT | PROPS | REGIONS | SOLUTION | SUMMARY | SCHEDULE |\n| DX | | SWL | ENDNUM | | | |\n| DY | | SWCR | EQLNUM | | | |\n| DZ | | SWU | FIPNUM | | | |\n| PERMX | | SGL | IMBNUM | | | |\n| PERMY | | SGCR | MISCNUM | | | |\n| PERMZ | | SGU | PVTNUM | | | |\n| MULTX | | KRW | ROCKNUM | | | |\n| MULTY | | KRO | SATNUM | | | |\n| MULTZ | | KRG | WH2NUM | | | |\n| DR | | PCG | | | | |\n| DTHETA | | PCW | | | | |\n| PERMR | | | | | | |\n| PERMTHT | | | | | | |\n| DZNET | | | | | | |\n| PORO | | | | | | |\n| NTG | | | | | | |\n| FLUXNUM | | | | | | |\n| MULTNUM | | | | | | |\n| MPFANUM | | | | | | |\n| DIFFX | | | | | | |\n| DIFFY | | | | | | |\n| DIFFZ | | | | | | |\n| DIFFR | | | | | | |\n| DIFFTHT | | | | | | |","expected_columns":13,"size_kind":"list"},"COPYREG":{"name":"COPYREG","sections":["GRID","EDIT","PROPS","REGIONS","SOLUTION"],"supported":false,"summary":"The COPYREG keyword copies a specified array or part of an array based on cells with a specific region number to another array. The region number array can be FLUXNUM, MULTNUM or OPERNUM and these arrays must be defined and be available before the COPYREG keyword is read by the simulator. The property arrays can be real or integer valued depending on the property array type; however, the property arrays that can be operated on are dependent on which section the COPYREG keyword is being applied in.","parameters":[{"index":1,"name":"ARRAY-1","description":"A character string of up to eight characters in length that defines the keyword identifying the array to be copied from.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"ARRAY-2","description":"A character string of up to eight characters in length that defines the keyword identifying the array to be copied to.","units":{},"default":"None","value_type":"STRING"},{"index":3,"name":"REGION NUMBER","description":"Integer REGION NUMBER is the region for which the array data in (1) should be copied to array data in (2).","units":{},"default":"None","value_type":"INT"},{"index":4,"name":"REGION ARRAY","description":"The REGION ARRAY to use for selecting the REGION NUMBER in (3) for selecting the data to be copied. REGION ARRAY can have the following values: F for the FLUXNUM array M for the MULTNUM array O for the OPERNUM array","units":{},"default":"M","value_type":"STRING"}],"example":"--\n-- COPY AN ARRAY TO ANOTHER ARRAY BASED ON A REGION NUMBER\n--\n-- ARRAY ARRAY REGION REGION ARRAY\n-- FROM TO NUMBER M / F / O\nCOPYREG\nPERMX PERMY 1 M / COPY PERMX TO PERMY\nPERMX PERMZ 1 M / COPY PERMX TO PERMZ\n/\n--\n-- NOW RESET PERMZ BASED ON THE MULTNUM REGION NUMBER\n--\n--\n-- MULTIPLY AN ARRAY BY A CONSTANT BASED ON A REGION NUMBER\n--\n-- ARRAY CONSTANT REGION REGION ARRAY\n-- VALUE NUMBER M / F / O\nMULTIREG\nPERMX 0.95 1 M /\n/\nThe above example first copies the PERMX property array for region number one to the PERMY and PERMZ property arrays for region one using the MULTNUM array to define the region numbers. After which PERMZ property array for region one is multiplied by 0.5 using the MULTIREG keyword.\n| COPYREG Keyword and Variable Options by Section | | | | | | |\n|-------------------------------------------------|---------|-------|---------|----------|---------|----------|\n| GRID | EDIT | PROPS | REGIONS | SOLUTION | SUMMARY | SCHEDULE |\n| DX | DEPTH | SWL | ENDNUM | PRESSURE | | |\n| DY | PORV | SWCR | EQLNUM | SWAT | | |\n| DZ | TRANX | SWU | FIPNUM | SGAS | | |\n| PERMX | TRANY | SGL | IMBNUM | RV | | |\n| PERMY | TRANZ | SGCR | MISCNUM | RS | | |\n| PERMZ | DIFFX | SGU | PVTNUM | TBLK | | |\n| MULTX | DIFFY | KRW | ROCKNUM | GI | | |\n| MULTY | DIFFZ | KRO | SATNUM | OILAPI | | |\n| MULTZ | TRANR | KRG | WH2NUM | SALT | | |\n| DR | TRANTHT | PCG | | GASCONC | | |\n| DTHETA | DIFFR | PCW | | SOLVCONC | | |\n| PERMR | DIFFTHT | | | SOLVFRAC | | |\n| PERMTHT | | | | SFOAM | | |\n| DZNET | | | | SPOLY | | |\n| PORO | | | | | | |\n| NTG | | | | | | |\n| FLUXNUM | | | | | | |\n| MULTNUM | | | | | | |\n| MPFANUM | | | | | | |\n| DIFFX | | | | | | |\n| DIFFY | | | | | | |\n| DIFFZ | | | | | | |\n| DIFFR | | | | | | |\n| DIFFTHT | | | | | | |","expected_columns":4,"size_kind":"list"},"CRITPERM":{"name":"CRITPERM","sections":["GRID"],"supported":false,"summary":"The CRITPERM keyword is used to define the minimum permeability for Vertical Equilibrium(“VE”) grid cell compression, for when the Vertical Equilibrium formulation has been activated by the VE keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"VALUE","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Permeability"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"DIFFMR-":{"name":"DIFFMR-","sections":["GRID"],"supported":false,"summary":"The DIFFMR- keyword defines the negative radial direction diffusivity multipliers for cells in the current input box for when the Diffusivity option has been activated by the DIFFUSE keyword in the RUNSPEC section.","parameters":[],"example":""},"DIFFMR":{"name":"DIFFMR","sections":["GRID"],"supported":false,"summary":"The DIFFMR keyword defines the radial direction diffusivity multipliers for cells in the current input box for when the Diffusivity option has been activated by the DIFFUSE keyword in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"DIFFMTH-":{"name":"DIFFMTH-","sections":["GRID"],"supported":false,"summary":"The DIFFMR- keyword defines the negative theta direction diffusivity multipliers for cells in the current input box for when the Diffusivity option has been activated by the DIFFUSE keyword in the RUNSPEC section.","parameters":[],"example":""},"DIFFMTHT":{"name":"DIFFMTHT","sections":["GRID"],"supported":false,"summary":"The DIFFMTHT keyword defines the theta direction diffusivity multipliers for cells in the current input box for when the Diffusivity option has been activated by the DIFFUSE keyword in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"DIFFMX-":{"name":"DIFFMX-","sections":["GRID"],"supported":false,"summary":"The DIFFMX- keyword defines the negative x-direction diffusivity multipliers for cells in the current input box for when the Diffusivity option has been activated by the DIFFUSE keyword in the RUNSPEC section.","parameters":[],"example":""},"DIFFMX":{"name":"DIFFMX","sections":["GRID"],"supported":false,"summary":"The DIFFMX keyword defines the x-direction diffusivity multipliers for cells in the current input box for when the Diffusivity option has been activated by the DIFFUSE keyword in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"DIFFMY-":{"name":"DIFFMY-","sections":["GRID"],"supported":false,"summary":"The DIFFMY- keyword defines the negative y-direction diffusivity multipliers for cells in the current input box for when the Diffusivity option has been activated by the DIFFUSE keyword in the RUNSPEC section.","parameters":[],"example":""},"DIFFMY":{"name":"DIFFMY","sections":["GRID"],"supported":false,"summary":"The DIFFMY keyword defines the y-direction diffusivity multipliers for cells in the current input box for when the Diffusivity option has been activated by the DIFFUSE keyword in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"DIFFMZ-":{"name":"DIFFMZ-","sections":["GRID"],"supported":false,"summary":"The DIFFMZ- keyword defines the negative z-direction diffusivity multipliers for cells in the current input box for when the Diffusivity option has been activated by the DIFFUSE keyword in the RUNSPEC section.","parameters":[],"example":""},"DIFFMZ":{"name":"DIFFMZ","sections":["GRID"],"supported":false,"summary":"The DIFFMZ keyword defines the z-direction diffusivity multipliers for cells in the current input box for when the Diffusivity option has been activated by the DIFFUSE keyword in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"DISPERC":{"name":"DISPERC","sections":["GRID"],"supported":null,"summary":"The DISPERC keyword defines the mechanical dispersivity for all cells in the model via an array.","parameters":[{"index":1,"name":"DISPERC","description":"DISPERC is an array of real positive values that defines the mechanical dispersivity for each cell in the model. Repeat counts may be used, for example 20*1.0.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None"}],"example":"The example sets the mechanical dispersivity for all cells in the model to 1.0.\n--\n-- SET MECHANICAL DISPERSIVITY FOR ALL CELLS (OPM FLOW KEYWORD)\n--\nDISPERC\n1000*1.0 /\n| Note The option has been tested in combination with the CO2STORE, H2STORE, BIOFILM, or MICP keywords, but not for the general case at this point. |\n|---------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"array"},"DOMAINS":{"name":"DOMAINS","sections":["GRID"],"supported":false,"summary":"The DOMAINS keyword defines the parallel domain properties for when parallel processing has been invoked by the PARALLEL keyword in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"DPGRID":{"name":"DPGRID","sections":["GRID"],"supported":false,"summary":"The DPGRID keyword activates the matrix cell to fracture cell option for dual porosity runs for when a Dual Porosity model has been activated by either the DUALPORO or DUALPERM keywords in the RUNSPEC section. The keyword allows for only the matrix grid data to be entered and the missing fracture cells are set to the inputted matrix cells.","parameters":[],"example":"","size_kind":"none","size_count":0},"DPNUM":{"name":"DPNUM","sections":["GRID"],"supported":false,"summary":"In dual porosity runs only, that is not dual permeability runs, the DPNUM keyword defines which wells should be treated as single porosity cells and which cells should be treated as dual porosity cells, for when the Dual Porosity model has been activated by the DUALPORO keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"VALUE","description":"","units":{},"default":"","value_type":"INT"}],"example":"","size_kind":"fixed","size_count":1,"variadic_record":true},"DR":{"name":"DR","sections":["GRID"],"supported":false,"summary":"DR defines the size of all grid blocks in the R direction via an array for each cell in the model. The RADIAL or SPIDER keyword in the RUNSPEC section should be activated to indicate that radial or spider geometry is being used.","parameters":[{"index":1,"name":"DR","description":"DR is an array of real numbers describing the cell size in the R direction for each cell in the model in a radial grid. Repeat counts may be used, for example 10*100.0.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None"}],"example":"Given the dimensions of the grid in the RUNSPEC section to be 10,1, 8 for NX, NY and NZ respectively, we first define the inner radius of the radial model,\n--\n-- INNER RADIUS OF FIRST GRID BLOCK IN THE RADIAL DIRECTION\n--\nINRAD\n0.25\n/\nand then DR should be defined as:\n--\n-- DEFINE GRID BLOCK R DIRECTION CELL SIZE\n--\nDR\n1.75 2.32 5.01 10.84 23.39 50.55 109.21 235.92 509.68 1101.0\n1.75 2.32 5.01 10.84 23.39 50.55 109.21 235.92 509.68 1101.0\n1.75 2.32 5.01 10.84 23.39 50.55 109.21 235.92 509.68 1101.0\n1.75 2.32 5.01 10.84 23.39 50.55 109.21 235.92 509.68 1101.0\n1.75 2.32 5.01 10.84 23.39 50.55 109.21 235.92 509.68 1101.0\n1.75 2.32 5.01 10.84 23.39 50.55 109.21 235.92 509.68 1101.0\n1.75 2.32 5.01 10.84 23.39 50.55 109.21 235.92 509.68 1101.0\n1.75 2.32 5.01 10.84 23.39 50.55 109.21 235.92 509.68 1101.0\n/\nThe above example defines the size of the cells in the R direction based on 80 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.\nNote that since the first layer (K=1) must be defined and subsequent layers default to the layer above then:\n--\n-- INNER RADIUS OF FIRST GRID BLOCK IN THE RADIAL DIRECTION\n--\nINRAD\n0.25\n/\n--\n-- DEFINE GRID BLOCK R DIRECTION CELL SIZE\n--\nDR\n1.75 2.32 5.01 10.84 23.39 50.55 109.21 235.92 509.68 1101.0\n/\nis equivalent to previous example.","size_kind":"array"},"DRV":{"name":"DRV","sections":["GRID"],"supported":false,"summary":"DRV defines the size of grid blocks in the R direction via a vector as opposed to defining the property for each cell for a Radial or Spider Grid. The RADIAL or SPIDER keyword in the RUNSPEC section should be activated to indicate that radial or spider geometry is being used.","parameters":[{"index":1,"name":"DRV","description":"DRV is a vector of real numbers describing the cell size for the grid blocks in the R direction in a radial grid. Repeat counts may be used, for example 10*100.0.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None"}],"example":"--\n-- INNER RADIUS OF FIRST GRID BLOCK IN THE RADIAL DIRECTION\n--\nINRAD\n0.25\n/\n--\n-- DEFINE GRID BLOCK SIZES IN THE R DIRECTION\n--\nDRV\n1.75 2.32 5.01 10.84 23.39 50.55 109.21 235.92 509.68 1101.08 /\nThe above example defines the size of the cells in the R direction based on NX equals 10 on the DIMENS keyword in the RUNSPEC section. Note the INRAD keyword to define the inner radius of the radial grid.","size_kind":"array"},"DTHETA":{"name":"DTHETA","sections":["GRID"],"supported":false,"summary":"DTHETA defines the size of all grid blocks in the Theta direction via an array for each cell in model. The RADIAL or SPIDER keyword in the RUNSPEC section should be activated to indicate that radial or spider geometry is being used.","parameters":[{"index":1,"name":"DTHETA","description":"DTHETA is an array of real numbers describing the cell size in the THETA direction in radial grids for each cell in the model. Repeat counts may be used, for example 10*25.0","units":{"field":"degrees","metric":"degrees","laboratory":"degrees"},"default":"None"}],"example":"Given the dimensions of the grid in the RUNSPEC section to be 10, 6, 1 for NX, NY and NZ respectively, then DTHETA should be defined as:\n--\n-- DEFINE GRID BLOCK SIZES IN THE THETA DIRECTION\n--\nDTHETA\n10*60.0\n10*60.0\n10*60.0\n10*60.0\n10*60.0\n10*60.0\n/\nThe above example defines the size of the cells in the R direction based on 60 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"DTHETAV":{"name":"DTHETAV","sections":["GRID"],"supported":null,"summary":"DTHETAV defines the size of grid blocks in the THETA direction via a vector as opposed to defining the property for each cell for a Radial Grid. The RADIAL or SPIDER keyword in the RUNSPEC should be activated to indicate that radial geometry is being used.","parameters":[{"index":1,"name":"DTHETAV","description":"DTHETAV is a vector of real numbers describing the cell size for the grid blocks in the THETA direction in a radial grid. Repeat counts may be used, for example 10*100.0.","units":{"field":"degrees","metric":"degrees","laboratory":"degrees"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK SIZES IN THE THETA DIRECTION (BASED ON NY = 6)\n--\nDTHETAV\n60.0 60.0 60.0 60.0 60.0 60.0 /\nThe above example defines the size of the cells in the THETA direction based on NY equals six in the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"DUMPFLUX":{"name":"DUMPFLUX","sections":["GRID"],"supported":null,"summary":"This keyword activates the writing out of a full field (the full grid) FLUX file for later processing in a Flux Boundary run. The Flux Boundary feature allows for the segmentation of the full grid into flux boundary areas which allow for a sub-area of the grid to be run and at the same time model the flux across the boundary derived from the main grid. The object of this feature is to be able to investigate the performance of various areas of the model without having to run the full field, thus improving computational efficiency and run times, but still obtain “reasonable” results due to the incorporation of the fluxes across the boundary.","parameters":[],"example":"--\n-- ACTIVATE WRITING OUT OF A FLUX FILE\n--\nDUMPFLUX /\nThe above example switches on the writing of the FLUX output file; the keyword has no effect and is ignored by the simulator.","size_kind":"none","size_count":0},"DX":{"name":"DX","sections":["GRID"],"supported":null,"summary":"DX defines the size of all grid blocks in the X direction via an array for each cell in a Cartesian Regular Grid model.","parameters":[{"index":1,"name":"DX","description":"DX is an array of real numbers describing the cell size in the X direction for each cell in the model. Repeat counts may be used, for example 10*100.0.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK X DIRECTION CELL SIZE (BASED ON NX x NY x NZ = 300)\n--\nDX\n300*1000 /\nThe above example defines the size of the cells in the X direction based on 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"DXV":{"name":"DXV","sections":["GRID"],"supported":null,"summary":"DXV defines the size of grid blocks in the X direction via a vector as opposed to defining the X direction cell size for each cell for a Cartesian Regular Grid.","parameters":[{"index":1,"name":"DXV","description":"DXV is a vector of real numbers describing the cell size for the grid blocks in the X direction. Repeat counts may be used, for example 10*100.0.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK X DIRECTION CELL SIZE (BASED ON NX = 5)\n--\nDXV\n5*100 /\nThe above example defines the size of the cells in the X direction based on NX equals 5 on the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"DY":{"name":"DY","sections":["GRID"],"supported":null,"summary":"DY defines the size of all grid blocks in the Y direction via an array for each cell in a Cartesian Regular Grid model.","parameters":[{"index":1,"name":"DY","description":"DY is an array of real numbers describing the cell size in the Y direction for each cell in the model. Repeat counts may be used, for example 10*100.0.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK Y DIRECTION CELL SIZE (BASED ON NX x NY x NZ = 300)\n--\nDY\n300*1000 /\nThe above example defines the size of the cells in the Y direction based on 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"DYV":{"name":"DYV","sections":["GRID"],"supported":null,"summary":"DYV defines the size of grid blocks in the Y direction via a vector as opposed to defining the Y direction cell size for each cell for a Cartesian Regular Grid.","parameters":[{"index":1,"name":"DYV","description":"DYV is a vector of real numbers describing the cell size for the grid blocks in the Y direction. Repeat counts may be used, for example 10*100.0.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK Y DIRECTION CELL SIZE (BASED ON NY = 5)\n--\nDYV\n5*100 /\nThe above example defines the size of the cells in the Y direction based on NY equals 5 on the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"DZ":{"name":"DZ","sections":["GRID"],"supported":null,"summary":"DZ defines the size of all grid blocks in the Z direction via an array for each cell in a Cartesian Regular Grid model.","parameters":[{"index":1,"name":"DZ","description":"DZ is an array of real numbers describing the cell size in the Z direction for each cell in the model. Repeat counts may be used, for example 10*100.0.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK Z DIRECTION CELL SIZE (BASED ON NX x NY x NZ = 300)\n--\nDZ\n100*20.0 100*30.0 100*50.0 /\nThe above example defines the size of the cells in the Z direction based on 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"DZMATRIX":{"name":"DZMATRIX","sections":["GRID"],"supported":false,"summary":"The DZMATRIX keyword defines the matrix block height for the gravity drainage model by grid block for when the Dual Permeability or Dual Porosity models are activated by the DUALPERM and DUALPORO keywords and the Gravity Drainage option is invoked via the GRAVDR and GRAVDRM keywords. All keywords are in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"DZMTRX":{"name":"DZMTRX","sections":["GRID"],"supported":false,"summary":"The DZMTRX keyword defines a constant matrix block height for the gravity drainage model for the entire grid for when the Dual Permeability or Dual Porosity models are activated by the DUALPERM and DUALPORO keywords and the Gravity Drainage option is invoked via the GRAVDR and GRAVDRM keywords. All keywords are in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"DZMTRXV":{"name":"DZMTRXV","sections":["GRID"],"supported":false,"summary":"The DZMATRIX keyword defines the matrix block height for the gravity drainage model by grid block for when the Dual Permeability or Dual Porosity models are activated by the DUALPERM and DUALPORO keywords and the Gravity Drainage option is invoked via the GRAVDR and GRAVDRM keywords. All keywords are in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"DZNET":{"name":"DZNET","sections":["GRID"],"supported":null,"summary":"DZNET defines the net thickness of all grid blocks in the Z direction via an array for each cell in a Cartesian Regular Grid model.","parameters":[{"index":1,"name":"DZNET","description":"DZNET is an array of real numbers describing the net thickness in the Z direction for each cell in the model. Repeat counts may be used, for example 10*100.0. If the value for a grid block is not defined then the grid block size (DZ) is assigned to the missing values.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"DZ"}],"example":"--\n-- DEFINE GRID BLOCK Z DIRECTION NET THICKNESS(BASED ON NX x NY x NZ = 300)\n--\nDZNET\n100*15.0 100*25.0 00*45.0 /\nThe above example defines the net thickness of the cells in the Z direction based on 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"DZV":{"name":"DZV","sections":["GRID"],"supported":null,"summary":"DZV defines the size of grid blocks in the Z direction via a vector as opposed to defining the thickness property for each cell. The keyword is used for both Cartesian Regular Grids and Radial Grids.","parameters":[{"index":1,"name":"DZV","description":"DZV is a vector of real numbers describing the cell size for the grid blocks in the Z direction. Repeat counts may be used, for example 10*20.0.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK SIZES IN THE Z DIRECTION (BASED ON NZ = 20)\n--\nDZV\n3.0 5.0 3.0 2.0 5.0 15*3.0 /\nThe above example defines the size of the cells in the Z direction based on NZ equals 20 on the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"ENDBOX":{"name":"ENDBOX","sections":["GRID","EDIT","PROPS","REGIONS","SOLUTION","SCHEDULE"],"supported":null,"summary":"This keyword marks the end of a previously defined BOX sub-grid as defined by a previously entered BOX keyword. The keyword resets the input grid to be the full grid as defined by the NX, NY, and NZ variables on the DIMENS keyword in the RUNSPEC section.","parameters":[],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n10 10 1 6 1 1 / DEFINE BOX AREA\n--\n--\n-- DEFINE GRID BLOCK PERMZ DATA FOR THE INPUT BOX\n--\nPERMZ\n6*0.01 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe above example defines a subset of the grid and sets the cells PERMZ values to 0.01 for that area. After which the ENDBOX keyword resets the input to be the full grid.\nNote\nIt is good practice to always use the ENDBOX keyword to reset the input back to the full grid when all the modifications for a sub-grid have been completed.\n| Note It is good practice to always use the ENDBOX keyword to reset the input back to the full grid when all the modifications for a sub-grid have been completed. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"none","size_count":0},"ENDFIN":{"name":"ENDFIN","sections":["GRID","EDIT","PROPS","REGIONS","SOLUTION","SCHEDULE"],"supported":false,"summary":"The ENDFIN keyword defines the end of a Cartesian or radial local grid refinement (“LGR”) definition and a LGR property definition data set. In the GRID section the CARFIN, RADFIN, and RADFIN4 keywords defines the start of an LGR description section, whereas the REFINE keyword in the EDIT, PROPS, REGIONS, SOLUTION and SCHEDULE section defines the start. The REFINE keyword can also be used in the GRID section provided the LGR has been previously specified by the CARFIN, RADFIN, or RADFIN4 keywords.","parameters":[],"example":"The example below is based on using the CARFIN keyword in the GRID section to define an LGR in the global grid, named LGR-OP01 with a maximum of one well allowed in the LGR.\n--\n-- CARFIN LGR GRID COMMANDS\n--\n-- LGR ----- FINE GRID ------ -- CARFIN GRID -- MAX HOST\n-- NAME I1 I2 J1 J2 K1 K2 NX NY NZ WELLS NAME\nCARFIN\nLGR-OP01 24 24 87 87 1 50 3 3 50 1 GLOBAL /\nENDFIN\nHere the one global cell in the areal plane (24, 87) is divided into three LGR cells in the x-direction and three cells in the y-direction. Since no other property data is given, then the LGR cells take their properties from the host grid, that is the global grid.","size_kind":"none","size_count":0},"EQLZCORN":{"name":"EQLZCORN","sections":["GRID"],"supported":false,"summary":"The EQLZCORN keyword modifies the depth of a corner point of a grid block on the pillars defining the reservoir grid. The keyword can be only used be used with Irregular Corner-Point Grids.","parameters":[{"index":1,"name":"VALUE_ZCORN_ARRAY","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":2,"name":"IX1","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"IX2","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"JY1","description":"","units":{},"default":"","value_type":"INT"},{"index":5,"name":"JY2","description":"","units":{},"default":"","value_type":"INT"},{"index":6,"name":"KZ1","description":"","units":{},"default":"","value_type":"INT"},{"index":7,"name":"KZ2","description":"","units":{},"default":"","value_type":"INT"},{"index":8,"name":"IX1A","description":"","units":{},"default":"","value_type":"INT"},{"index":9,"name":"IX2A","description":"","units":{},"default":"","value_type":"INT"},{"index":10,"name":"JY1A","description":"","units":{},"default":"","value_type":"INT"},{"index":11,"name":"JY2A","description":"","units":{},"default":"","value_type":"INT"},{"index":12,"name":"ACTION_REQ","description":"","units":{},"default":"TOP","value_type":"STRING"}],"example":"","expected_columns":12,"size_kind":"list"},"EQUALREG":{"name":"EQUALREG","sections":["GRID","EDIT","PROPS","REGIONS","SOLUTION"],"supported":false,"summary":"The EQUALREG keyword sets a specified array to a constant for cells with a specific region number. The region number array can be FLUXNUM, MULTNUM or OPERNUM and these arrays must be defined and be available before the EQUALREG keyword is read by the simulator. The constant can be an integer or real value depending on the array type; however, the arrays that can be operated on are dependent on which section the EQUALREG keyword is being applied in.","parameters":[{"index":1,"name":"ARRAY","description":"A character string of up to eight characters in length that defines the keyword identifying the array to be modified.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"CONSTANT","description":"An integer or real value to be assigned to the ARRAY in the same units as the ARRAY property for a given REGION","units":{},"default":"0","value_type":"DOUBLE"},{"index":3,"name":"REGION NUMBER","description":"REGION NUMBER is a positive integer representing the region for which the CONSTANT in (2) should be applied","units":{},"default":"None","value_type":"INT"},{"index":4,"name":"REGION ARRAY","description":"The REGION ARRAY to use for applying the CONSTANT in (2) based on the REGION NUMBER in (3). REGION ARRAY can have the following values: F for the FLUXNUM array M for the MULTNUM array O for the OPERNUM array","units":{},"default":"M","value_type":"STRING"}],"example":"-- FIRST DEFINE MULTNUM ARRAYS FOR 10 X 10 X 20 MODEL\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nMULTNUM 1 1* 1* 1* 1* 1* 1* / MULTNUM IN MODEL\nMULTNUM 2 1* 1* 1* 1* 6 6 / MULTNUM IN MODEL\nMULTNUM 3 1* 1* 1* 1* 10 10 / MULTNUM IN MODEL\n/\n-- NOW SET PORO AND PERMX BASED ON THE MULTNUM REGION NUMBER\n--\n-- SETS A CONSTANT TO AN ARRAY BASED ON A REGION NUMBER\n--\n-- ARRAY CONSTANT REGION REGION ARRAY\n-- VALUE NUMBER M / F / O EQUALREG\nPORO 0.200 1 M /\nPORO 0.150 2 M /\nPORO 0.120 3 M /\nPERMX 100.00 1 M /\nPERMX 75.00 2 M /\nPERMX 50.00 3 M /\n/\nThe example first defines the MULTNUM array to 1 for all cells in the model, after which selected areas of model are assigned various MULTNUM integer values. The EQUALREG can then be invoked to set constant values for the PORO and PERMX arrays for the various MULTNUM regions.\n| EQUALREG Keyword and Variable Options by Section | | | | | | |\n|--------------------------------------------------|---------|-------|---------|----------|---------|----------|\n| GRID | EDIT | PROPS | REGIONS | SOLUTION | SUMMARY | SCHEDULE |\n| DX | DEPTH | SWL | ENDNUM | PRESSURE | | |\n| DY | PORV | SWCR | EQLNUM | SWAT | | |\n| DZ | TRANX | SWU | FIPNUM | SGAS | | |\n| PERMX | TRANY | SGL | IMBNUM | RV | | |\n| PERMY | TRANZ | SGCR | MISCNUM | RS | | |\n| PERMZ | DIFFX | SGU | PVTNUM | TBLK | | |\n| MULTX | DIFFY | KRW | ROCKNUM | GI | | |\n| MULTY | DIFFZ | KRO | SATNUM | OILAPI | | |\n| MULTZ | TRANR | KRG | WH2NUM | SALT | | |\n| DR | TRANTHT | PCG | | GASCONC | | |\n| DTHETA | DIFFR | PCW | | SOLVCONC | | |\n| PERMR | DIFFTHT | | | SOLVFRAC | | |\n| PERMTHT | | | | SFOAM | | |\n| DZNET | | | | SPOLY | | |\n| PORO | | | | | | |\n| NTG | | | | | | |\n| FLUXNUM | | | | | | |\n| MULTNUM | | | | | | |\n| MPFANUM | | | | | | |\n| DIFFX | | | | | | |\n| DIFFY | | | | | | |\n| DIFFZ | | | | | | |\n| DIFFR | | | | | | |\n| DIFFTHT | | | | | | |","expected_columns":4,"size_kind":"list"},"EQUALS":{"name":"EQUALS","sections":["GRID","EDIT","PROPS","REGIONS","SOLUTION"],"supported":false,"summary":"The EQUALS keyword sets a specified array or part of an array to a constant. The constant can be an integer or real value depending on the array type; however, the arrays that can be operated on are dependent on which section the EQUALS keyword is being applied in.","parameters":[{"index":1,"name":"ARRAY","description":"A character string of up to eight characters in length that defines the keyword identifying the property to be modified.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"CONSTANT","description":"An integer or real value that the ARRAY will be set to in the same units as the ARRAY property.","units":{},"default":"None","value_type":"DOUBLE"},{"index":3,"name":"I1","description":"A positive integer that defines the lower bound of the array in the I-direction to be modified must be greater than or equal to one and less than or equal to I2 and NX.","units":{},"default":"1","value_type":"INT"},{"index":4,"name":"I2","description":"A positive integer that defines the upper bound of the array in the I-direction to be modified must be greater than or equal to II and less than or equal to NX","units":{},"default":"NX","value_type":"INT"},{"index":5,"name":"J1","description":"A positive integer that defines the lower bound of the array in the J-direction to be modified must be greater than or equal to one and less than or equal to J2 and NY.","units":{},"default":"1","value_type":"INT"},{"index":6,"name":"J2","description":"A positive integer that defines the upper bound of the array in the J-direction to be modified must be greater than or equal to JI and less than or equal to NY.","units":{},"default":"NY","value_type":"INT"},{"index":7,"name":"K1","description":"A positive integer that defines the lower bound of the array in the K-direction to be modified must be greater than or equal to one and less than or equal to K2 and NZ.","units":{},"default":"1","value_type":"INT"},{"index":8,"name":"K2","description":"A positive integer that defines the upper bound of the array in the K-direction to be modified must be greater than or equal to KI and less than or equal to NZ.","units":{},"default":"NZ","value_type":"INT"}],"example":"The first example resets the PERMX, PERMY and PERMZ, arrays to 0.10, 0.10, and 0.01 for all cells in layer five, respectively.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n- I1 I2 J1 J2 K1 K2\nEQUALS\nPERMX 0.1000 1* 1* 1* 1* 5 5 / PERMX TO 0.10 IN LAYER 5\nPERMY 0.1000 1* 1* 1* 1* 5 5 / PERMY TO 0.10 IN LAYER 5\nPERMZ 0.0100 1* 1* 1* 1* 5 5 / PERMZ TO 0.01 IN LAYER 5\n/\nThe second example illustrates how to correctly setup a Cartesian Regular Grid in OPM Flow, given the DIMENS keyword in the RUNSPEC section is set to:\n--\n-- MAX MAX MAX\n-- NDIVIX NDIVIY NDIVIZ\nDIMENS\n10 10 3 /\nand the following keywords in the GRID section:\n--\n-- ACTIVATE IRREGULAR CORNER-POINT GRID TRANSMISSIBILITIES\n--\nOLDTRAN\n--\n-- DEFINE GRID BLOCK X DIRECTION CELL SIZE (BASED ON NX = 5)\n--\nDX\n300*1000 /\n--\n-- DEFINE GRID BLOCK Y DIRECTION CELL SIZE (BASED ON NY = 5)\n--\nDY\n300*1000 /\n--\n-- DEFINE GRID BLOCK SIZES IN THE Z DIRECTION\n--\nDZ\n100*20 100*30 100*50 /\n--\n-- DEFINE GRID BLOCK TOPS FOR THE TOP LAYER\n--\nTOPS\n100*8325 /\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nPERMX 500.000 1* 1* 1* 1* 1 1 / Layer #01 Properties\nPERMY 500.000 /\nPERMZ 20.000 /\nPORO 0.300 /\nNTG 1.000 /\nPERMX 50.000 1* 1* 1* 1* 2 2 / Layer #02 Properties\nPERMY 50.000 /\nPERMZ 50.000 /\nPORO 0.300 /\nNTG 1.000 /\nPERMX 200.000 1* 1* 1* 1* 3 3 / Layer #03 Properties\nPERMY 200.000 /\nPERMZ 200.000 /\nPORO 0.300 /\nNTG 1.000 /\n/\nNotice that the DX, DY, DZ and TOPS keywords are defined separately, that is they are not included in the EQUALS keyword.\n| EQUALS Keyword and Variable Options by Section | | | | | | |\n|------------------------------------------------|---------|-------|---------|----------|---------|----------|\n| GRID | EDIT | PROPS | REGIONS | SOLUTION | SUMMARY | SCHEDULE |\n| DX | DEPTH | SWL | ENDNUM | PRESSURE | | |\n| DY | PORV | SWCR | EQLNUM | SWAT | | |\n| DZ | TRANX | SWU | FIPNUM | SGAS | | |\n| PERMX | TRANY | SGL | IMBNUM | RV | | |\n| PERMY | TRANZ | SGCR | MISCNUM | RS | | |\n| PERMZ | DIFFX | SGU | PVTNUM | TBLK | | |\n| MULTX | DIFFY | KRW | ROCKNUM | GI | | |\n| MULTY | DIFFZ | KRO | SATNUM | OILAPI | | |\n| MULTZ | TRANR | KRG | WH2NUM | SALT | | |\n| DR | TRANTHT | PCG | | GASCONC | | |\n| DTHETA | DIFFR | PCW | | SOLVCONC | | |\n| PERMR | DIFFTHT | | | SOLVFRAC | | |\n| PERMTHT | | | | SFOAM | | |\n| DZNET | | | | SPOLY | | |\n| PORO | | | | | | |\n| NTG | | | | | | |\n| FLUXNUM | | | | | | |\n| MULTNUM | | | | | | |\n| MPFANUM | | | | | | |\n| DIFFX ","expected_columns":8,"size_kind":"list"},"EXTFIN":{"name":"EXTFIN","sections":["GRID"],"supported":false,"summary":"The EXTFIN keyword defines an external Unstructured Local Grid Refinement (“LGR”) in a cell or a group of cells in the global grid, and for when LGRs have been activated for the model using the LGR keyword in the RUNSPEC section. Note the global grid can be either structured, see the EXTREPGL keyword in the GRID section for global structure grids, or unstructured, see the EXTHOST keyword in the GRID section for unstructured global grids.","parameters":[{"index":1,"name":"LOCAL_GRID_REF","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"NX","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"NY","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"NZ","description":"","units":{},"default":"","value_type":"INT"},{"index":5,"name":"NREPG","description":"","units":{},"default":"","value_type":"INT"},{"index":6,"name":"NHALO","description":"","units":{},"default":"","value_type":"INT"},{"index":7,"name":"NFLOG","description":"","units":{},"default":"","value_type":"INT"},{"index":8,"name":"NUMINT","description":"","units":{},"default":"","value_type":"INT"},{"index":9,"name":"NUMCON","description":"","units":{},"default":"","value_type":"INT"},{"index":10,"name":"NWMAX","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":10,"size_kind":"fixed","size_count":1},"EXTHOST":{"name":"EXTHOST","sections":["GRID"],"supported":false,"summary":"The EXTHOST keyword defines the host global grid blocks for an external Local Grid Refinement (“LGR”) for when LGRs have been activated for the model using the LGR keyword in the RUNSPEC section, and the global grid is an unstructured grid.","parameters":[],"example":"","size_kind":"array"},"EXTREPGL":{"name":"EXTREPGL","sections":["GRID"],"supported":false,"summary":"The EXTREPGL keyword defines the host global grid blocks for an external Unstructured Local Grid Refinement (“LGR”) for when LGRs have been activated for the model using the LGR keyword in the RUNSPEC section, and the global grid is a structured grid.","parameters":[],"example":"","size_kind":"array"},"FAULTS":{"name":"FAULTS","sections":["GRID"],"supported":null,"summary":"The FAULTS keyword defines the faults in the grid geometry and the keyword is normally exported with the grid geometry COORD and ZCORN data sets from static earth modeling software. Note that the FAULTS keyword is not required to describe the structural geometry as this is already accounted for in the COORD and ZCORN data sets, but instead lists the fault traces with respect to the grid. Once the fault traces have been defined with the FAULTS keyword then the fault transmissibilities can be modified by the MULTFLT keyword. Note that without the FAULTS keyword one would still get proper cross-fault transmissibilities but they would not be modifiable using MULTFLT keyword.","parameters":[{"index":1,"name":"FLTNAME","description":"FLTNAME is a character string enclosed in quotes with a maximum length of eight characters, that defines the name of the fault.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"I1","description":"The lower bound of the fault’s I-direction range must be greater than or equal to one and less than or equal to I2 and NX.","units":{},"default":"None","value_type":"INT"},{"index":3,"name":"I2","description":"The upper bound of the fault’s I-direction range must be greater than or equal to II and less than or equal to NX","units":{},"default":"None","value_type":"INT"},{"index":4,"name":"J1","description":"The lower bound of the fault’s J-direction range must be greater than or equal to one and less than or equal to J2 and NY.","units":{},"default":"None","value_type":"INT"},{"index":5,"name":"J2","description":"The upper bound of the fault’s J-direction range must be greater than or equal to JI and less than or equal to NY.","units":{},"default":"None","value_type":"INT"},{"index":6,"name":"K1","description":"The lower bound of the fault’s K-direction range must be greater than or equal to one and less than or equal to K2 and NZ.","units":{},"default":"None","value_type":"INT"},{"index":7,"name":"K2","description":"The upper bound of the fault’s K-direction range must be greater than or equal to KI and less than or equal to NZ.","units":{},"default":"None","value_type":"INT"},{"index":8,"name":"FLTFACE","description":"Unknown Author\n 2017-06-27T13:59:19\n I am not able to review this properly, as I am not familiar enough with what is supposed to happen. I do not know if we support X-, Y-, Z- transmissibilities.\n FLTFACE is a character string enclosed in quotes with a maximum length of two characters, that classifies the fault face. I am not able to review this properly, as I am not familiar enough with what is supposed to happen. I do not know if we support X-, Y-, Z- transmissibilities. If TRANSMULT on the GRIDOPTS keyword in the RUNSPEC section is set to NO then FLTFACE can have values of X, Y, or Z. Alternatively, if TRANSMULT on the GRIDOPTS keyword in the RUNSPEC section is set to YES then FLTFACE can have values of X, Y, or Z for the positive direction, or X-, Y- or Z- for the negative direction transmissibilities.","units":{},"default":"None","value_type":"STRING"}],"example":"The example below defines two fault traces, the first being the ‘M_WEST’ fault and the second the ‘BC’ fault trace.\n--\n-- DEFINE FAULTS IN THE GRID GEOMETRY\n--\n-- FAULT ------------ FAULT TRACE -------------\n-- NAME I1 I2 J1 J2 K1 K2 FACE\nFAULTS\n'M_WEST' 5 5 3 3 1 22 'X' /\n'M_WEST' 5 5 4 4 1 22 'X' /\n'M_WEST' 5 5 5 5 1 22 'X' /\n'M_WEST' 5 5 6 6 1 22 'X' /\n'M_WEST' 5 5 7 7 1 22 'X' /\n'M_WEST' 5 5 8 8 1 22 'X' /\n'M_WEST' 5 5 9 9 1 22 'X' /\n'M_WEST' 5 5 10 10 1 22 'X' /\n'M_WEST' 5 5 11 11 1 22 'X' /\n……………………………………………..\n'BC' 43 43 8 8 1 22 'Y' /\n'BC' 42 42 9 9 1 22 'X' /\n'BC' 44 44 8 8 1 22 'Y' /\n'BC' 45 45 8 8 1 22 'Y' /\n'BC' 46 46 8 8 1 22 'Y' /\n'BC' 31 31 9 9 1 22 'Y' /\n'BC' 30 30 10 10 1 22 'X' /\n'BC' 32 32 9 9 1 22 'Y' /\n'BC' 33 33 9 9 1 22 'Y' /\n'BC' 34 34 9 9 1 22 'Y' /\n'BC' 35 35 9 9 1 22 'Y' /\n'BC' 36 36 9 9 1 22 'Y' /\n'BC' 37 37 9 9 1 22 'Y' /\n'BC' 38 38 9 9 1 22 'Y' /\n'BC' 39 39 9 9 1 22 'Y' /\n'BC' 40 40 9 9 1 22 'Y' /\n……………………………………………..\n/","expected_columns":8,"size_kind":"list"},"FILEUNIT":{"name":"FILEUNIT","sections":["GRID","EDIT","PROPS","REGIONS","SOLUTION","SCHEDULE"],"supported":null,"summary":"The FILEUNIT keyword defines the units of the data set, and is used to verify that the units in the input deck and any associated include files are consistent. The keyword does not provide for the conversion between different sets of units.","parameters":[{"index":1,"name":"FILEUNIT","description":"A character string that defines the units of the data set, and should be set to: FIELD for field units, METRIC for metric units, or LAB for laboratory units","units":{},"default":"None","value_type":"STRING"}],"example":"--\n-- ACTIVATE UNIT CONSISTENCY CHECKING\n--\nFILEUNIT\nFIELD /\nThe above example defines the data set units to be FIELD units.","expected_columns":1,"size_kind":"fixed","size_count":1},"FLUXNUM":{"name":"FLUXNUM","sections":["GRID"],"supported":null,"summary":"The FLUXNUM keyword defines the flux region numbers for each grid block, as such there must be one entry for each cell in the model. The array is used with the Flux Boundary option to define the various flux regions; however, the Flux Boundary option has not been implemented in OPM Flow. In addition, the array can be used with the EQUALREG, ADDREG, COPYREG, MULTIREG, MULTREGP and MULTREGT keywords in calculating various grid properties in the GRID section. This facility has been implemented in OPM Flow.","parameters":[{"index":1,"name":"FLUXNUM","description":"FLUXNUM defines an array of positive integers assigning a grid cell to a particular flux region. The maximum number of flux regions is set by the MXNFLX variable on the REGDIMS keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"The example below sets three FLUXNUM regions for a 4 x 5 x 2 model.\n--\n-- DEFINE FLUXNUM REGIONS FOR ALL CELLS\n--\nFLUXNUM\n2 2 1 1 2 2 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n3 3 1 1 3 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n/\nAlternatively the EQUALS keyword could be employed to accomplish the same task, that is:\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nFLUXNUM 1 1* 1* 1* 1* 1* 1* / SET REGION 1\nFLUXNUM 2 1 2 1 2 1 1 / SET REGION 2\nFLUXNUM 3 1 2 1 2 2 2 / SET REGION 3\n/","size_kind":"array"},"FLUXREG":{"name":"FLUXREG","sections":["GRID"],"supported":false,"summary":"The FLUXREG is used in conjunction with the USEFLUX keyword in runs with have multiple flux regions, to reduce the number of flux regions, that is the keyword specifies which flux regions are active and which are not in the current run.","parameters":[],"example":"","size_kind":"array"},"FLUXTYPE":{"name":"FLUXTYPE","sections":["GRID"],"supported":false,"summary":"The FLUXTYPE keyword defines the type of flux boundary to be used in the run.","parameters":[{"index":1,"name":"BC_TYPE","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"GDFILE":{"name":"GDFILE","sections":["GRID"],"supported":null,"summary":"The GDFILE keyword loads a GRID file that contains the structural data for the grid as a set of topological cuboidal cells, and EGRID files that contain structural and property data. Note OPM Flow only supports reading in EGRID files at this time.","parameters":[{"index":1,"name":"GRIDFILE","description":"A character string enclosed in quotes that defines the GRID or EGRID file to be read in and be processed by OPM Flow. Again, OPM Flow only supports reading in EGRID files.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"FMTOPT","description":"A defined character string that defines the format of the GRID or EGRID file to be read and should be set to one of the following: FORMATTED: If the file is formatted as ASCII i.e. a text file, as oppose to a binary file. The option can be abbreviated to just the letter F. UNFORMATTED: If the file is in binary format, note this option can be abbreviated to just the letter U. If the variable FMTOPT is omitted then the default is for binary file input for the commercial simulator; whereas, OPM Flow derives FMTOPT from the file extension (*.EGRID or *.FEGRID), making FMTOPT superfluous.","units":{},"default":"U","value_type":"STRING"}],"example":"The first example shown below loads the NOR-OPM-A00-GRID.EGRID file in binary format from the same directory as the data file.\n--\n-- LOAD A GRID FILE\n--\nGDFILE\n'NOR-OPM-A00-GRID.EGRID' /\nThe next example loads the same EGRID file one directory above from where the data file is located.\n--\n-- LOAD a GRID FILE\n--\nGDFILE\n'../NOR-OPM-A00-GRID.EGRID' /","expected_columns":2,"size_kind":"fixed","size_count":1},"GDORIENT":{"name":"GDORIENT","sections":["GRID"],"supported":false,"summary":"This keyword defines the grid orientation parameters for post-processing applications.","parameters":[{"index":1,"name":"I","description":"","units":{},"default":"INC","value_type":"STRING"},{"index":2,"name":"J","description":"","units":{},"default":"INC","value_type":"STRING"},{"index":3,"name":"K","description":"","units":{},"default":"INC","value_type":"STRING"},{"index":4,"name":"Z","description":"","units":{},"default":"DOWN","value_type":"STRING"},{"index":5,"name":"HAND","description":"","units":{},"default":"RIGHT","value_type":"STRING"}],"example":"","expected_columns":5,"size_kind":"fixed","size_count":1},"GETDATA":{"name":"GETDATA","sections":["GRID","EDIT","PROPS","REGIONS","SOLUTION"],"supported":false,"summary":"The GETDATA keyword loads a data array from a previously generated INIT or RESTART file and assigns the loaded array to either same array in the run or another property array.","parameters":[{"index":1,"name":"FILENAME","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"FORMATTED","description":"","units":{},"default":"UNFORMATTED","value_type":"STRING"},{"index":3,"name":"ZNAME","description":"","units":{},"default":"","value_type":"STRING"},{"index":4,"name":"ZALT","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":4,"size_kind":"fixed","size_count":1},"GRID":{"name":"GRID","sections":["GRID"],"supported":null,"summary":"The GRID activation keyword marks the end of the RUNSPEC section and the start of the GRID section that defines the key grid property data for the simulator including the grid structure, porosity, permeability and other relevant grid property data.","parameters":[],"example":"-- ==============================================================================\n--\n-- GRID SECTION\n--\n-- ==============================================================================\nGRID\nThe above example marks the end of the RUNSPEC section and the start of the GRID section in the OPM Flow data input file.","size_kind":"none","size_count":0},"GRIDFILE":{"name":"GRIDFILE","sections":["GRID"],"supported":true,"summary":"This keyword controls the output of a standard GRID or extended GRID file, as well as the extensible EGRID file for post-processing applications. The extended and extensible GRID formats are comparable; however, the extensible GRID format is more compact and is the only format supported by OPM Flow.","parameters":[{"index":1,"name":"NGRID","description":"A positive integer that controls the output of the GRID geometry file: - for no GRID file to be written out. - for the standard GRID file to be written out. - for the extended GRID file to be written out. Only the default value of zero is supported.","units":{},"default":"0","value_type":"INT"},{"index":2,"name":"NEGRID","description":"A positive integer that controls the output of the EGRID geometry file: - for no extensible GRID file to be written out. - for the extensible GRID file to be written out. Only the default value of one is supported.","units":{},"default":"1","value_type":"INT"}],"example":"--\n-- GRID FILE OUTPUT OPTIONS\n-- GRID EGRID\n-- OPTN OPTN\nGRIDFILE\n0 1 /\nThe above example defines that no GRID file will be written out and that the extensible GRID (that is the EGRID geometry format) file will be produced. This is the only configuration that OPM Flow supports","expected_columns":2,"size_kind":"fixed","size_count":1},"GRIDUNIT":{"name":"GRIDUNIT","sections":["GRID"],"supported":null,"summary":"The GRIDUNIT keyword defines the units of the grid data. It is usually output by pre-processing software when exporting the grid geometry. The data is not used by OPM Flow intrinsically, but is merely written to the output EGRID file, as specified by the GRIDFILE keyword, for the use of post-processing software like OPM ResInsight.","parameters":[{"index":1,"name":"GRIDUNIT","description":"A character string that defines the units of the coordinates stated on the MAPAXES keyword, and should be set to: FEET for field units, METRES for metric units, or CM for laboratory units.","units":{},"default":"METRES","value_type":"STRING"},{"index":2,"name":"MAPOPT","description":"A character string that defines if the grid data are measured relative to the map, or relative to the origin as stated on the MAPAXES keyword. MAPOPT should either be left blank (the default) indicating the origin is relative to the origin on the MAPAXES keyword, or set equal to MAP measured relative to the map.","units":{},"default":"1*","value_type":"STRING"}],"example":"--\n-- SET THE GRID UNITS FOR THE GRID\n--\nGRIDUNIT\nMETRES /\nThe above example defines that the GRID units to be metric.","expected_columns":2,"size_kind":"fixed","size_count":1},"HALFTRAN":{"name":"HALFTRAN","sections":["GRID"],"supported":false,"summary":"The HALFTRAN keyword activates the half block transmissibility calculation option.","parameters":[],"example":"","size_kind":"none","size_count":0},"HEATCR":{"name":"HEATCR","sections":["GRID"],"supported":null,"summary":"The HEATCR keyword defines the reservoir rock volumetric heat capacity for all cells for when OPM Flow’s thermal calculation is activated by the THERMAL keywords in the RUNSPEC section.","parameters":[{"index":1,"name":"HEATCR","description":"HEATCR is an array of real positive numbers that define reservoir rock volumetric heat capacity of a grid block. Repeat counts may be used, for example 3000*25.0","units":{"field":"Btu/ft3/°R","metric":"kJ/m3/K","laboratory":"J/cm3/K"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK RESERVOIR ROCK HEAT CAPACITY\n-- FOR ALL CELLS (BASED ON NX x NY x NZ = 300)\n-- KEYWORD IS INCOMPATIBLE WITH THE SPECROCK KEYWORD\n-- (OPM FLOW THERMAL OPTION ONLY)\n--\nHEATCR\n300*32.0 /\nThe above example defines the reservoir rock volumetric heat capacity of 32.0 for each cell in the 300 grid block model.","size_kind":"array"},"HEATCRT":{"name":"HEATCRT","sections":["GRID"],"supported":null,"summary":"The HEATCRT keyword defines the reservoir rock volumetric heat capacity temperature dependence for all cells for when OPM Flow’s thermal calculation is activated by the THERMAL keywords in the RUNSPEC section.","parameters":[{"index":1,"name":"HEATCRT","description":"HEATCRT is an array of real positive numbers that define reservoir rock volumetric heat capacity temperature dependence of a grid block. Repeat counts may be used, for example 3000*0.05","units":{"field":"Btu/ft3/°R2","metric":"kJ/m3/K2","laboratory":"J/cm3/K2"},"default":"None"}],"example":"--\n-- DEFINE RESERVOIR ROCK HEAT CAPACITY TEMPERATURE DEPENDENCE\n-- FOR ALL CELLS (BASED ON NX x NY x NZ = 300)\n-- KEYWORD IS INCOMPATIBLE WITH THE SPECROCK KEYWORD\n-- (OPM FLOW THERMAL OPTION ONLY)\n--\nHEATCRT\n300*0.05 /\nThe above example defines the reservoir rock volumetric heat capacity temperature dependence of 0.05 for each cell in the 300 grid block model.\n| [\"Heat Capacity of Rock \"=\"HEATCR\" LEFT(Temp ~-~Temp sub{ref} right)~+~{\"HEATCRT\"left(Temp ~-~Temp sub{ref} right) sup{2}} over { 2}] | (6.3) |\n|---------------------------------------------------------------------------------------------------------------------------------------|-------|","size_kind":"array"},"HMAQUNUM":{"name":"HMAQUNUM","sections":["GRID"],"supported":false,"summary":"The HMAQUNUM keyword defines the history match numerical aquifer gradient parameters for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section, and numerical aquifers have been specified in the model via the AQUNUM keyword and connected to the grid using AQUCON keyword. All keywords are in the GRID section.","parameters":[{"index":1,"name":"AQUIFER_ID","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"DERIVATIES_RESP_PORE_VOL_MULT","description":"","units":{},"default":"NO","value_type":"STRING"},{"index":3,"name":"DERIVATIES_RESP_AQUIFER_PERM_MULT","description":"","units":{},"default":"","value_type":"STRING"},{"index":4,"name":"DERIVATIES_RESP_AQUIFER_GRID_CON_TRANS","description":"","units":{},"default":"NO","value_type":"STRING"}],"example":"","expected_columns":4,"size_kind":"list"},"HMFAULTS":{"name":"HMFAULTS","sections":["GRID"],"supported":false,"summary":"The HMFAULTS keyword defines the history match faults gradient parameters for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section, and for when the FAULTS keyword in the GRID section has been used to define faults in the model.","parameters":[{"index":1,"name":"FAULT_SEGMENT","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"list"},"HMMLAQUN":{"name":"HMMLAQUN","sections":["GRID"],"supported":false,"summary":"The HMMLAQUN keyword defines the history match numerical aquifer gradient multipliers for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section, and numerical aquifers have been specified in the model via the AQUNUM keyword and connected to the grid using the AQUCON keyword. All keywords are in the GRID section.","parameters":[{"index":1,"name":"AQUIFER_ID","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"AQUIFER_PORE_VOL_MULT","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"AQUIFER_PORE_PERM_MULT","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"},{"index":4,"name":"AQUIFER_GRID_CONN_MULT","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"}],"example":"","expected_columns":4,"size_kind":"list"},"HMMLT":{"name":"HMMLT","sections":["GRID"],"supported":false,"summary":"The HMMLT series of keywords defines the history match gradient cumulative permeability multipliers, for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section. The keyword consists of the first five characters of “HMMLT” followed by a two or three character string shown in Table 6.45, that determines the permeability direction, for example, HMMLTPX.","parameters":[],"example":"| Mnemonic | Cartesian Grid | Radial Grid | | |\n|--------------|----------------|--------------|----------------|---------|\n| Grid Keyword | HMMULT Keyword | Grid Keyword | HMMULT Keyword | |\n| PX/PR | PERMX | HMMLTPX | PERMR | HMMLTPR |\n| PXY | PERMXY | HMMLTPXY | | |\n| PY/THT | PERMY | hMMLTPY | PERMTHT | HMMLTTH |\n| PZ | PERMZ | HMMLTPZ | PERMZ | HMMLTPZ |"},"HMMMREGT":{"name":"HMMMREGT","sections":["GRID"],"supported":false,"summary":"The HMMMREGT keyword multiplies the transmissibility between two regions by a constant, for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section. The constant should be a real number. Unlike the MULTREGT keyword in the GRID section, the HMMMREGT keyword modifications are cumulative.","parameters":[],"example":""},"HMMULRGT":{"name":"HMMULRGT","sections":["GRID"],"supported":false,"summary":"HMMULRGT defines the transmissibility between two regions gradient parameters, for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section.","parameters":[],"example":""},"HMMULTFT":{"name":"HMMULTFT","sections":["GRID"],"supported":false,"summary":"HMMULTFT defines the history match fault transmissibility gradient cumulative multipliers to be applied to the fault transmissibilities for faults declared by the FAULT keyword in the GRID section, for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section. The keyword allows for the re-scaling of the existing fault transmissibilities calculated by OPM Flow, or if the MULTFLT keyword has been entered, then HMMULTFT is applied to the existing MULTFLT multipliers.","parameters":[{"index":1,"name":"FAULT","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"TRANS_MULT","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"DIFF_MULT","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"}],"example":"","expected_columns":3,"size_kind":"list"},"HMMULTSG":{"name":"HMMULTSG","sections":["GRID"],"supported":false,"summary":"HMMULTSG defines the history match dual porosity sigma parameter gradient cumulative multipliers applied to the dual porosity sigma value declared by the SIGMAV and SIGMAGDV keywords in the PROPS section, for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section. In addition to the HMDIMS keyword, either the DUALPERM keyword that activates the Dual Permeability option, or the DUALPORO keyword that activates the Dual Porosity option for the run, must be declared in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"HRFIN":{"name":"HRFIN","sections":["GRID"],"supported":false,"summary":"HRFIN116\n Radial grids are not currently implemented in this version of OPM Flow, but is expected to be incorporated in a future release. defines the ratio of grid blocks for the DRV keyword in the r-direction via a vector within a Local Grid Refinement (“LGR”) as opposed to defining the size for each cell for a Radial LGR Grid. The LGR keyword in the RUNSPEC section should be activated to indicate an LGR is being used, and the keyword HRFIN should be placed in between the RADIN (or RAFDIN4) and ENDFIN keywords in the GRID section. The DRV keyword in the GRID section defines the radial grid size in terms of the length, that is feet for field units, this keyword defines the length as the ratio of the previous cell size, staring with the inner radius (INRAD).","parameters":[{"index":1,"name":"HRFIN","description":"HRFIN is a vector of real numbers describing the ratio of cell size for the grid blocks in the r-direction in a radial LGR for the DRV keyword. Repeat counts may be used, for example 2*1.5.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- INNER RADIUS OF FIRST GRID BLOCK IN THE RADIAL DIRECTION\n--\nINRAD 0.25 /\n--\n-- DEFINE GRID BLOCK DRV RATIOS IN THE R DIRECTION\n--\nHRFIN\n1.50 2.00 3.00 5.00 7.00 10.00 /\nThe above example defines the size of the cells in the R direction based on NR equals 7, resulting in NR-1 values on the RADFIN keyword in the GRID section. Note the INRAD keyword to define the inner radius of the radial grid.","size_kind":"array"},"HXFIN":{"name":"HXFIN","sections":["GRID"],"supported":false,"summary":"HXFIN defines the split ratio of grid blocks for the DXV keyword in the x-direction via a vector within a Local Grid Refinement (“LGR”) as opposed to defining the size for each cell for a Cartesian LGR Grid. The LGR keyword in the RUNSPEC section should be activated to indicate an LGR is being used, and the keyword HXFIN should be placed in between the CARFIN and ENDFIN keywords in the GRID section. The DXV keyword in the GRID section defines the grid size in terms of the length, that is feet for field units, this keyword defines the length as the ratio of the coarse cells.","parameters":[{"index":1,"name":"HXFIN","description":"HXFIN is a vector of real numbers describing the ratio of cell size for the grid blocks in the x-direction in a Cartesian LGR grid. Repeat counts may be used, for example 2*2.0.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- CARFIN LGR GRID COMMANDS\n--\n-- LGR ----- HOST GRID ------ -- CARFIN GRID -- MAX HOST\n-- NAME I1 I2 J1 J2 K1 K2 NX NY NZ WELLS NAME\nCARFIN\nLGR-OP01 24 25 86 87 1 50 5 3 50 1 GLOBAL /\n--\n-- DEFINE LGR GRID BLOCK IN THE X-DIRECTION\nNXFIN\n3 2 /\n--\n-- DEFINE GRID BLOCK LGR RATIOS IN THE X-DIRECTION\n--\nHXFIN\n1.00 2.00 3.00 2.00 1.00 /\nENDFIN\nThe above example defines the size of the cells in the x-direction based on NX equals five on the CARFIN keyword in the GRID section.","size_kind":"array"},"HYFIN":{"name":"HYFIN","sections":["GRID"],"supported":false,"summary":"HYFIN defines the split ratio of grid blocks for the DYV keyword in the y-direction via a vector within a Local Grid Refinement (“LGR”) as opposed to defining the size for each cell for a Cartesian LGR Grid. The LGR keyword in the RUNSPEC section should be activated to indicate an LGR is being used, and the keyword HYFIN should be placed in between the CARFIN and ENDFIN keywords in the GRID section. The DYV keyword in the GRID section defines the grid size in terms of the length, that is feet for field units, this keyword defines the length as the ratio of the coarse cells.","parameters":[{"index":1,"name":"HYFIN","description":"HYFIN is a vector of real numbers describing the ratio of cell size for the grid blocks in the y-direction in a Cartesian LGR grid. Repeat counts may be used, for example 2*2.0.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- CARFIN LGR GRID COMMANDS\n--\n-- LGR ----- HOST GRID ------ -- CARFIN GRID -- MAX HOST\n-- NAME I1 I2 J1 J2 K1 K2 NX NY NZ WELLS NAME\nCARFIN\nLGR-OP01 24 25 86 87 1 50 3 5 50 1 GLOBAL /\n--\n-- DEFINE LGR GRID BLOCK IN THE Y-DIRECTION\nNYFIN\n3 2 /\n--\n-- DEFINE GRID BLOCK LGR RATIOS IN THE Y-DIRECTION\n--\nHYFIN\n1.00 2.00 3.00 2.00 1.00 /\nENDFIN\nThe above example defines the size of the cells in the y-direction based on NY equals five on the CARFIN keyword in the GRID section.","size_kind":"array"},"HZFIN":{"name":"HZFIN","sections":["GRID"],"supported":false,"summary":"HZFIN defines the split ratio of grid blocks for the DZV keyword in the z-direction via a vector within a Local Grid Refinement (“LGR”) as opposed to defining the size for each cell for a Cartesian LGR Grid. The LGR keyword in the RUNSPEC section should be activated to indicate an LGR is being used, and the keyword HYFIN should be placed in between the CARFIN and ENDFIN keywords in the GRID section. The DZV keyword in the GRID section defines the grid size in terms of the length, that is feet for field units, this keyword defines the length as the ratio of the coarse cells.","parameters":[{"index":1,"name":"HYZIN","description":"HZFIN is a vector of real numbers describing the ratio of cell size for the grid blocks in the z-direction in a Cartesian LGR grid. Repeat counts may be used, for example 2*2.0.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- CARFIN LGR GRID COMMANDS\n--\n-- LGR ----- HOST GRID ------ -- CARFIN GRID -- MAX HOST\n-- NAME I1 I2 J1 J2 K1 K2 NX NY NZ WELLS NAME\nCARFIN\nLGR-OP01 24 25 86 87 1 50 5 3 100 1 GLOBAL /\n--\n-- DEFINE LGR GRID BLOCK IN THE Z-DIRECTION\nNZFIN\n50*2 /\n--\n-- DEFINE GRID BLOCK LGR RATIOS IN THE Z-DIRECTION\n--\nHZFIN\n50*2.0 /\nENDFIN\nThe above example defines the size of the cells in the z-direction based on NZ equals 100 on the CARFIN keyword in the GRID section.","size_kind":"array"},"IHOST":{"name":"IHOST","sections":["GRID"],"supported":false,"summary":"The IHIST keyword assigns Local Grid Refinements (“LGR”) to a parallel process number, for when the PARALLEL keyword has been invoked in the RUNSPEC section.","parameters":[{"index":1,"name":"LGR","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"PROCESS","description":"","units":{},"default":"0","value_type":"INT"}],"example":"","expected_columns":2,"size_kind":"list"},"IMPORT":{"name":"IMPORT","sections":["GRID","EDIT","PROPS","REGIONS","SOLUTION"],"supported":null,"summary":"The IMPORT keyword informs the simulator to import data from the specified IMPORT file. When the end of the IMPORT file is reached, input data is read from the next keyword in the current file. Normally IMPORT files are generated by grid pre-processing software and the keyword allows for both formatted and unformatted (binary) files to be loaded. The keyword can be used to import any valid grid arrays within a section, for example the EQLNUM array in the REGIONS section","parameters":[{"index":1,"name":"FILENAME","description":"A character string enclosed in quotes that defines a file to be imported and to be processed by OPM Flow.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"FMTOPT","description":"A defined character string that defines the format of the file to be imported and should be set to one of the following: FORMATTED: If the file is formatted as ASCII i.e. a text file, as oppose to a binary file. The option can be abbreviated to just the letter F. UNFORMATTED: If the file is in binary format, note this option can be abbreviated to just the letter U. If the variable FMTOPT is omitted then the default is for binary file input.","units":{},"default":"U","value_type":"STRING"}],"example":"The first example shown below loads the grid file from the same directory as the data file.\n--\n-- LOAD A IMPORT FILE\n--\nIMPORT\n'NOR-OPM-A00-GRID.EGRID' /\nThe next example loads the same file one directory above from where the data file is located.\n--\n-- LOAD A IMPORT FILE\n--\nIMPORT\n'../NOR-OPM-A00-GRID.EGRID' /\nThe final example loads the same file from a separate include subdirectory in the parent directory of the data file.\n--\n-- LOAD A IMPORT FILE\n--\nIMPORT\n'../INCLUDE/NOR-OPM-A00-GRID.EGRID' /","expected_columns":2,"size_kind":"fixed","size_count":1},"INIT":{"name":"INIT","sections":["GRID"],"supported":null,"summary":"This keyword switches on the writing of the INIT file that contains the static data specified in the GRID, PROPS and REGIONS sections. For example, the PORO, PERM and NTG arrays from the GRID section. The data is used in post-processing software, for example OPM ResInsight, to visualize the static grid properties.","parameters":[],"example":"--\n-- ACTIVATE WRITING THE INIT FILE FOR POST-PROCESSING\nINIT\nThe above example switches on the writing of the INIT file for post-processing in ResInsight.","size_kind":"none","size_count":0},"INRAD":{"name":"INRAD","sections":["GRID"],"supported":null,"summary":"INRAD defines the inner radius of the reservoir model for a radial grid geometry. The RADIAL or SPIDER keyword in the RUNSPEC should be activated to indicate that radial geometry is being used.","parameters":[{"index":1,"name":"INRAD","description":"A single real positive number defining the inner radius of a radial grid.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":"Length"}],"example":"--\n-- INNER RADIUS OF FIRST GRID BLOCK IN THE RADIAL DIRECTION\n--\nINRAD\n0.25 /\nThe above example defines the inner radius of a radial grid to be 0.25 feet.","expected_columns":1,"size_kind":"fixed","size_count":1},"IONROCK":{"name":"IONROCK","sections":["GRID"],"supported":false,"summary":"The IONROCK keyword defines the ion exchange capacity for all the cells in the model, for when the brine phase has been activated by the BRINE keyword and the Multi-Component Brine model, that allows for the water phase to have multiple water salinities, has been activated by the ECLMC keyword. Both keywords are in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"ISOLNUM":{"name":"ISOLNUM","sections":["GRID"],"supported":false,"summary":"The ISOLNUM keyword defines areas of the grid that consists of isolated reservoirs where the only form of communication between the reservoirs is via wellbore connections This enables the reservoir flow equations to be solved independently for greater computational efficiency.","parameters":[{"index":1,"name":"ISOLNUM","description":"ISOLNUM defines an array of positive integers assigning a grid cell to a particular isolated reservoir region. The maximum number of ISOLNUM regions is set by the NRFREG variable on the REGDIMS keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"The example below defines three separate independent reservoirs; the first reservoir covers the whole grid and layers 1 to 50, reservoir two cover the whole grid and layers 52 to 150, and finally the third reservoir again covers the whole grid but with layers 152 to 300. The layers 51 and 151 are shale layers made inactive by setting ISOLNUM to zero.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nISOLNUM 1 1* 1* 1* 1* 1 50 / DEFINED RESERVOIR 1\nISOLNUM 0 1* 1* 1* 1* 51 51 / DEFINED A SHALE\nISOLNUM 2 1* 1* 1* 1* 52 150 / DEFINED RESERVOIR 2\nISOLNUM 0 1* 1* 1* 1* 151 151 / DEFINED A SHALE\nISOLNUM 3 1* 1* 1* 1* 152 300 / DEFINED RESERVOIR 3\n/\nNote the above example has no effect as the keyword is ignored by the simulator.","size_kind":"array"},"JFUNC":{"name":"JFUNC","sections":["GRID"],"supported":null,"summary":"The JFUNC keyword activates the Leverett-J-Function117\n Leverett, M. C.; “Capillary Behaviour in Porous Solids”, Trans. AIME (1941) 142, 152-168. option which is a commonly used technique to normalize capillary pressure based on laboratory measured core plugs porosity and permeability values and the resulting capillary pressure data. The keyword performs the calculation based on the parameters on the this keyword combined with a cells porosity and permeability to perform the scaling globally.","parameters":[{"index":1,"name":"JFOPT","description":"A character string that defines which capillary data sets the J-Function option should be applied to, based on the following options: WATER: apply the J-Function option to the water-oil capillary pressure data only. GAS: apply the J-Function option to the gas-oil capillary pressure data only. BOTH: apply the J-Function option to the water-oil and the gas-oil capillary pressure data.","units":{},"default":"BOTH","value_type":"STRING","options":["WATER","GAS","BOTH"]},{"index":2,"name":"OWSTEN","description":"A positive real number that defines oil-water surface tension used to de-normalized J-Function data entered in the PROPS section.","units":{"field":"dynes/cm","metric":"dynes/cm","laboratory":"dynes/cm"},"default":"None","value_type":"DOUBLE","dimension":"SurfaceTension"},{"index":3,"name":"OGSTEN","description":"A positive real number that defines oil-gas surface tension used to de-normalized J-Function data entered in the PROPS section.","units":{"field":"dynes/cm","metric":"dynes/cm","laboratory":"dynes/cm"},"default":"None","value_type":"DOUBLE","dimension":"SurfaceTension"},{"index":4,"name":"ALPHA","description":"A positive real value that defines an alternative power value for the porosity term in the J-Function equation, that is instead of [sqrt{k over %varphi}]use use [{k sup 0.5} over {%varphi sup %alpha}]instead in the transformation.instead in the transformation.","units":{},"default":"0.5","value_type":"DOUBLE"},{"index":5,"name":"BETA","description":"A positive real number that defines an alternative power value for the permeability term in the J-Function equation, that is instead of [sqrt{k over %varphi}]use use [{k sup %beta} over {%varphi sup 0.5}]instead in the transformation.instead in the transformation.","units":{},"default":"0.5","value_type":"DOUBLE"},{"index":6,"name":"PERM","description":"PERM is a character string that sets the permeability array to be used in the transform, based on the following options: X: use the PERMX array. XY: use the average of the PERMX and PERMY arrays. Y: use the PERMY array. Z: use the PERMZ array. U: use the PERMJFUN array","units":{},"default":"XY","value_type":"STRING"}],"example":"--\n-- DEFINE LEVERETT J-FUNCTION PARAMETERS\n-- JFUN OILWAT GASOIL PORO PERM PERM\n-- OPTN SDENS SDEN ALPHA BETA OPTN\nJFUNC\nWATER 22.5 1* 0.5 0.5 XY /\nThe above example results in the oil-water capillary pressure data entered on the SWFN keyword in the PROPS section being treated as J-Functions, and that the J-Function should be de-normalized using an oil-water surface density of 22.5 dynes/cm, using the default power values and the average of the PERMX and PERMY values for each grid block.\n| [J ` ` (S SUB{w})~=~ {P SUB{c,res} (S SUB{w}) ~ {SQRT {k OVER φ} }}\n OVER {σ }] | (6.4) |\n|-----------------------------------------------------------------------------------------------------------|-------|\n| [J ` ` (S SUB{w})~=~ {P SUB{c,res} (S SUB{w}) ~ {SQRT {k OVER φ} }}\n OVER {σ`` cos ` ` Θ}] | (6.5) |\n|----------------------------------------------------------------------------------------------------------------------|-------|\n| [J ` ` (S SUB{w})~=~ {P SUB{c,res} (S SUB{w}) ~ {SQRT {k OVER φ} }}] | (6.6) |\n|-----------------------------------------------------------------------|-------|\n| [J ` ` (S SUB{w})~=~ {P SUB{c,res} (S SUB{w}) ~ left( {k sup %beta} OVER {φ sup %alpha} right) }\n OVER {σ }] | (6.7) |\n|---------------------------------------------------------------------------------------------------------------------------------------|-------|\n| Note If either the JFUNC or JFUNCR keywords are used to activate J-Function scaling then the ENDSCALE keyword in the RUNSPEC section must also be present in the input deck, in order for the dimensionless J-function values entered on the SWFN, SGFN or the SWOF, SGOF, SLGOF keywords to be re-scaled to capillary pressure data. Note if the ENDSCALE keyword is absent, then like the commercial simulator, J-Function scaling is not performed, and the values entered on the SWFN, SGFN or the SWOF, SGOF, SLGOF keywords are used as entered. |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":6,"size_kind":"fixed","size_count":1},"JFUNCR":{"name":"JFUNCR","sections":["GRID"],"supported":false,"summary":"JFUNCR keyword activates Leverett-J-Function119\n Leverett, M. C.; “Capillary Behaviour in Porous Solids”, Trans. AIME (1941) 142, 152-168. Saturation Table option which is a commonly used technique to normalize capillary pressure base on laboratory measured core plugs porosity and permeability values and the resulting capillary pressure data. This keyword is an extension of the JFUNC keyword in the GRID section that uses the parameters on the JFUNC keyword combined with a cell’s porosity and permeability to perform the scaling globally. In comparison, the JFUNCR allows for the J-Function parameters to be declared per saturation table number, resulting in greater flexibility.","parameters":[{"index":1,"name":"JFOPT","description":"A character string that defines which capillary data sets the J-Function option should be applied to, based on the following options: WATER: apply the J-Function option to the water-oil capillary pressure data only. GAS: apply the J-Function option to the gas-oil capillary pressure data only. BOTH: apply the J-Function option to the water-oil and the gas-oil capillary pressure data.","units":{},"default":"BOTH","value_type":"STRING","options":["WATER","GAS","BOTH"]},{"index":2,"name":"OWSTEN","description":"A positive real number that defines oil-water surface tension used to de-normalized J-Function data entered in the PROPS section.","units":{"field":"dynes/cm","metric":"dynes/cm","laboratory":"dynes/cm"},"default":"None","value_type":"DOUBLE"},{"index":3,"name":"OGSTEN","description":"A positive real number that defines oil-gas surface tension used to de-normalized J-Function data entered in the PROPS section.","units":{"field":"dynes/cm","metric":"dynes/cm","laboratory":"dynes/cm"},"default":"None","value_type":"DOUBLE"},{"index":4,"name":"ALPHA","description":"A positive real value that defines an alternative power value for the porosity term in the J-Function equation, that is instead of[sqrt{k over %varphi}] use use [{k sup 0.5} over {%varphi sup %alpha}]instead in the transformation.instead in the transformation.","units":{},"default":"0.5","value_type":"DOUBLE","dimension":"1"},{"index":5,"name":"BETA","description":"A positive real number that defines an alternative power value for the permeability term in the J-Function equation, that is instead of [sqrt{k over %varphi}]use use [{k sup %beta} over {%varphi sup 0.5}]instead in the transformation.instead in the transformation.","units":{},"default":"0.5","value_type":"DOUBLE","dimension":"1"},{"index":6,"name":"PERM","description":"PERM is a character string that sets the permeability array to be used in the transform, based on the following options: X: use the PERMX array. XY: use the average of the PERMX and PERMY arrays. Y: use the PERMY array. Z: use the PERMZ array. U: use the PERMJFUN array","units":{},"default":"XY","value_type":"STRING"}],"example":"The example below assumes NTSFUN is equal to five on the TABDIMS keyword in the RUNSPEC section.\n--\n-- DEFINE LEVERETT J-FUNCTION PARAMETERS BY SATURATION TABLES\n-- JFUN OILWAT GASOIL PORO PERM PERM\n-- OPTN SDENS SDEN ALPHA BETA OPTN\nJFUNCR\nWATER 22.5 1* 0.5 0.5 XY /\nWATER 22.5 1* 0.5 0.5 XY /\nWATER 22.5 1* 0.5 0.5 XY /\nWATER 22.5 1* 0.5 0.5 XY /\nWATER 22.5 1* 0.5 0.5 XY /\nHere the oil-water capillary pressure data entered on the SWFN keyword in the PROPS section are treated as J-Functions, and that the J-Function should be de-normalized using an oil-water surface density of 22.5 dynes/cm, using the default power values and the average of the PERMX and PERMY values for each grid block, for all five tables. Note that since all the JFUNCR parameters are the same for all saturation tables then the JFUNC keyword could be used instead in this instance.\n| [J ` ` (S SUB{w})~=~ {P SUB{c,res} (S SUB{w}) ~ {SQRT {k OVER φ} }}\n OVER {σ }] | (6.8) |\n|-----------------------------------------------------------------------------------------------------------|-------|\n| [J ` ` (S SUB{w})~=~ {P SUB{c,res} (S SUB{w}) ~ {SQRT {k OVER φ} }}\n OVER {σ`` cos ` ` Θ}] | (6.9) |\n|----------------------------------------------------------------------------------------------------------------------|-------|\n| [J ` ` (S SUB{w})~=~ {P SUB{c,res} (S SUB{w}) ~ {SQRT {k OVER φ} }}] | (6.10) |\n|-----------------------------------------------------------------------|--------|\n| [J ` ` (S SUB{w})~=~ {P SUB{c,res} (S SUB{w}) ~ left( {k sup %beta} OVER {φ sup %alpha} right) }\n OVER {σ }] | (6.11) |\n|---------------------------------------------------------------------------------------------------------------------------------------|--------|\n| Note If either the JFUNC or JFUNCR keywords are used to activate J-Function scaling then the ENDSCALE keyword in the RUNSPEC section must also be present in the input deck, in order for the dimensionless J-function values entered on the SWFN, SGFN or the SWOF, SGOF, SLGOF keywords to be re-scaled to capillary pressure data. Note if the ENDSCALE keyword is absent, then like the commercial simulator, J-Function scaling is not performed, and the values entered on the SWFN, SGFN or the SWOF, SGOF, SLGOF keywords are used as entered. |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":6,"size_kind":"fixed"},"LINKPERM":{"name":"LINKPERM","sections":["GRID"],"supported":false,"summary":"The LINKPERM keyword assigns the grid cell permeabilities entered via the PERMX, PERMY and PERMZ keywords to a cell face (I±, J±, or K±) and results in the simulator using these values directly in the calculating the transmissibility between grid blocks. This is different to the conventional way of entering permeability data that consists of entering the cell centered permeability and the simulator calculating a weighted average transmissibility based on the cell centered permeability of the up-stream and down-stream grid blocks.","parameters":[],"example":"","size_kind":"array"},"LTOSIGMA":{"name":"LTOSIGMA","sections":["GRID"],"supported":false,"summary":"The LTOSIGMA keyword defines parameters to calculate the sigma factor in conjunction with the data entered via the LX, LY and LZ keywords in the GRID section, for when the VISCD keyword has been used in the RUNSPEC section to activate the Dual Porosity Viscous Displacement option. In addition, either the DUALPORO or DUALPERM keyword should be entered in the RUNSPEC section to activate the dual porosity or dual permeability models.","parameters":[{"index":1,"name":"FX","description":"","units":{},"default":"4","value_type":"DOUBLE","dimension":"1"},{"index":2,"name":"FY","description":"","units":{},"default":"4","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"FZ","description":"","units":{},"default":"4","value_type":"DOUBLE","dimension":"1"},{"index":4,"name":"FGD","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"1"},{"index":5,"name":"OPTION","description":"","units":{},"default":"XONLY","value_type":"STRING"}],"example":"","expected_columns":5,"size_kind":"fixed","size_count":1},"LX":{"name":"LX","sections":["GRID"],"supported":false,"summary":"The LX keyword defines the size of “representative” matrix grid blocks in the X direction via an array in dual porosity and dual permeability runs, for when the VISCD keyword has been used in the RUNSPEC section to activate the dual porosity viscous displacement option. In addition, either the DUALPORO or DUALPERM keyword should be entered in the RUNSPEC section to activate the dual porosity or dual permeability models. The VISCD option is used to model the viscous displacement of fluids from the matrix by the fracture pressure gradient, for when the fracture system has a more moderate permeability, and flow to and from the matrix caused by the fracture pressure gradient acts as an additional production mechanism.","parameters":[{"index":1,"name":"LX","description":"LX is an array of real numbers describing the “representative” cell size in the X direction for each cell in the model. Repeat counts may be used, for example 10*100.0.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"0"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n10 10 1 6 1 1 / DEFINE BOX AREA\n--\n-- DEFINE DUAL POROSITY VISCOUS DISPLACEMENT X DIRECTION MATRIX SIZE\n--\nLX\n6*10.0 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe above example defines a subset of the grid and the size of the “representative” matrix cells in the X direction to 10.0 ft.; after which the ENDBOX keyword resets the input to be the full grid.","size_kind":"array"},"LXFIN":{"name":"LXFIN","sections":["GRID"],"supported":false,"summary":"The LXFIN keyword defines the parameters for automatically generating a Local Grid Refinement (“LGR”) grid in the X direction based on logarithmic block spacing, for when the LGR option has been activated by the LGR keyword in the RUNSPEC section. LXFIN should be placed in between the CARFIN and ENDFIN keywords in the GRID section.","parameters":[{"index":1,"name":"CELL_THICKNESS","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":2,"name":"SIZE_OPTION","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":2,"size_kind":"fixed","size_count":1},"LY":{"name":"LY","sections":["GRID"],"supported":false,"summary":"The LY keyword defines the size of “representative” matrix grid blocks in the Y direction via an array in dual porosity and dual permeability runs, for when the VISCD keyword has been used in the RUNSPEC section to activate the dual porosity viscous displacement option. In addition, either the DUALPORO or DUALPERM keyword should be entered in the RUNSPEC section to activate the dual porosity or dual permeability models. The VISCD option is used to model the viscous displacement of fluids from the matrix by the fracture pressure gradient, for when the fracture system has a more moderate permeability, and flow to and from the matrix caused by the fracture pressure gradient acts as an additional production mechanism.","parameters":[{"index":1,"name":"LY","description":"LY is an array of real numbers describing the “representative” cell size in the Y direction for each cell in the model. Repeat counts may be used, for example 10*100.0.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"0"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n10 10 1 6 1 1 / DEFINE BOX AREA\n--\n-- DEFINE DUAL POROSITY VISCOUS DISPLACEMENT Y DIRECTION MATRIX SIZE\n--\nLY\n6*15.0 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe above example defines a subset of the grid and the size of the “representative” matrix cells in the Y direction to 15.0 ft.; after which the ENDBOX keyword resets the input to be the full grid.","size_kind":"array"},"LYFIN":{"name":"LYFIN","sections":["GRID"],"supported":false,"summary":"The LYFIN keyword defines the parameters for automatically generating a Local Grid Refinement (“LGR”) grid in the Y direction based on logarithmic block spacing, for when the LGR option has been activated by the LGR keyword in the RUNSPEC section. LYFIN should be placed in between the CARFIN and ENDFIN keywords in the GRID section.","parameters":[{"index":1,"name":"CELL_THICKNESS","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":2,"name":"SIZE_OPTION","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":2,"size_kind":"fixed","size_count":1},"LZ":{"name":"LZ","sections":["GRID"],"supported":false,"summary":"The LZ keyword defines the size of “representative” matrix grid blocks in the Z direction via an array in dual porosity and dual permeability runs, for when the VISCD keyword has been used in the RUNSPEC section to activate the dual porosity viscous displacement option. In addition, either the DUALPORO or DUALPERM keyword should be entered in the RUNSPEC section to activate the dual porosity or dual permeability models. The VISCD option is used to model the viscous displacement of fluids from the matrix by the fracture pressure gradient, for when the fracture system has a more moderate permeability, and flow to and from the matrix caused by the fracture pressure gradient acts as an additional production mechanism.","parameters":[{"index":1,"name":"LZ","description":"LZ is an array of real numbers describing the “representative” cell size in the Z direction for each cell in the model. Repeat counts may be used, for example 10*100.0.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"0"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n10 10 1 6 1 1 / DEFINE BOX AREA\n--\n-- DEFINE DUAL POROSITY VISCOUS DISPLACEMENT Z DIRECTION MATRIX SIZE\n--\nLZ\n6*3.0 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe example defines a subset of the grid and the size of the “representative” matrix cells in the Y direction to 15.0 ft.; after which the ENDBOX keyword resets the input to be the full grid.","size_kind":"array"},"LZFIN":{"name":"LZFIN","sections":["GRID"],"supported":false,"summary":"The LZFIN keyword defines the parameters for automatically generating a Local Grid Refinement (“LGR”) grid in the Z direction based on logarithmic block spacing, for when the LGR option has been activated by the LGR keyword in the RUNSPEC section. LZFIN should be placed in between the CARFIN and ENDFIN keywords in the GRID section.","parameters":[{"index":1,"name":"CELL_THICKNESS","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":2,"name":"SIZE_OPTION","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":2,"size_kind":"fixed","size_count":1},"MAPAXES":{"name":"MAPAXES","sections":["GRID"],"supported":null,"summary":"MAPAXES specifies the origin of the map used to create the grid. It is usually output by pre-processing software when exporting the grid geometry. The data is not used by OPM Flow intrinsically, but is merely written to the output EGRID file, as specified by the GRIDFILE keyword, for the use of post-processing software like OPM ResInsight.","parameters":[{"index":1,"name":"X1","description":"X1 is a real number that defines the x co-ordinate of a point on the y-axis.","units":{},"default":"None"},{"index":2,"name":"Y1","description":"Y1 is a real number that defines the y co-ordinate of a point on the y-axis.","units":{},"default":"None"},{"index":3,"name":"X2","description":"X2 is a real number that defines the x co-ordinate of the origin.","units":{},"default":"None"},{"index":4,"name":"Y2","description":"Y2 is a real number that defines the y co-ordinate of the origin.","units":{},"default":"None"},{"index":5,"name":"X3","description":"X3 is a real number that defines the x co-ordinate of a point on the x-axis.","units":{},"default":"None"},{"index":6,"name":"Y3","description":"Y3 is a real number that defines the y co-ordinate of a point on the x-axis.","units":{},"default":"None"}],"example":"--\n-- ---------------- MAPAXES -----------------\n-- X1 Y1 X2 Y2 X3 Y3\nMAPAXES\n0.0 100.0 0.0 0.0 100.0 0.0 /\nThe above example defines the map axes to be exported to the grid file for use by post-processing software."},"MAPUNITS":{"name":"MAPUNITS","sections":["GRID"],"supported":false,"summary":"The MAPUNITS keyword defines the units of the coordinates stated on the MAPAXES keyword. It is usually output by pre-processing software when exporting the grid geometry. The data is not used by OPM Flow intrinsically, but is merely written to the output EGRID file, as specified by the GRIDFILE keyword, for the use of post-processing software like OPM ResInsight.","parameters":[{"index":1,"name":"MAPUNITS","description":"A character string that defines the units of the coordinates stated on the MAPAXES keyword, and should be set to: FEET for field units METRES for metric units, or CM for laboratory units","units":{},"default":"METRES","value_type":"STRING"}],"example":"--\n-- SET THE MAP UNITS FOR THE MAPAXES KEYWORD\nMAPUNITS\nMETRES /\nThe above example specifies the units on the MAPAXES to be the default METRES.","expected_columns":1,"size_kind":"fixed","size_count":1},"MAXVALUE":{"name":"MAXVALUE","sections":["GRID","EDIT","PROPS"],"supported":false,"summary":"The MAXVALUE keyword sets a maximum value for the specified array or part of an array. The constant can be an integer or real value depending on the array type; however, the arrays that can be operated on are dependent on which section the MAXVALUE keyword is being applied in.","parameters":[{"index":1,"name":"ARRAY","description":"A character string of up to eight characters in length that defines the keyword identifying the array to be modified.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"CONSTANT","description":"CONSTANT is a positive integer or positive real value that an ARRAY element will be reset to if an element in the defined input BOX, as defined by items (3) to (8), is greater than CONSTANT. CONSTANT has in the same units as the ARRAY property.","units":{},"default":"None","value_type":"DOUBLE"},{"index":3,"name":"I1","description":"The lower bound of the array in the I-direction to be modified must be greater than or equal to one and less than or equal to I2 and NX.","units":{},"default":"1","value_type":"INT"},{"index":4,"name":"I2","description":"The upper bound of the array in the I-direction to be modified must be greater than or equal to I1 and less than or equal to NX","units":{},"default":"NX","value_type":"INT"},{"index":5,"name":"J1","description":"The lower bound of the array in the J-direction to be modified must be greater than or equal to one and less than or equal to J2 and NY.","units":{},"default":"1","value_type":"INT"},{"index":6,"name":"J2","description":"The upper bound of the array in the J-direction to be modified must be greater than or equal to J1 and less than or equal to NY.","units":{},"default":"NY","value_type":"INT"},{"index":7,"name":"K1","description":"The lower bound of the array in the K-direction to be modified must be greater than or equal to one and less than or equal to K2 and NZ.","units":{},"default":"1","value_type":"INT"},{"index":8,"name":"K2","description":"The upper bound of the array in the K-direction to be modified must be greater than or equal to K1 and less than or equal to NZ.","units":{},"default":"NZ","value_type":"INT"}],"example":"--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nMAXVALUE\nPERMX 1.0E2 1* 1* 1* 1* 1* 1* / MAX VALUE FOR PERMX\nPERMY 1.0E2 1* 1* 1* 1* 1* 1* / MAX VALUE FOR PERMY\nPERMZ 1.0E1 1* 1* 1* 1* 1* 1* / MAX VALUE FOR PERMZ\n/\nThe above example resets the maximum values for the PERMX, PERMY and PERMZ, arrays to 100.0, 100.0 and 10.0, respectively, for all cells.\n| MAXVALUE Keyword and Variable Options by Section | | | | | | |\n|--------------------------------------------------|---------|-------|---------|----------|---------|----------|\n| GRID | EDIT | PROPS | REGIONS | SOLUTION | SUMMARY | SCHEDULE |\n| DX | DEPTH | SWL | | | | |\n| DY | PORV | SWCR | | | | |\n| DZ | TRANX | SWU | | | | |\n| PERMX | TRANY | SGL | | | | |\n| PERMY | TRANZ | SGCR | | | | |\n| PERMZ | DIFFX | SGU | | | | |\n| MULTX | DIFFY | KRW | | | | |\n| MULTY | DIFFZ | KRO | | | | |\n| MULTZ | TRANR | KRG | | | | |\n| DR | TRANTHT | PCG | | | | |\n| DTHETA | DIFFR | PCW | | | | |\n| PERMR | DIFFTHT | | | | | |\n| PERMTHT | | | | | | |\n| DZNET | | | | | | |\n| PORO | | | | | | |\n| NTG | | | | | | |\n| FLUXNUM | | | | | | |\n| MULTNUM | | | | | | |\n| MPFANUM | | | | | | |\n| DIFFX | | | | | | |\n| DIFFY | | | | | | |\n| DIFFZ | | | | | | |\n| DIFFR | | | | | | |\n| DIFFTHT | | | | | | |","expected_columns":8,"size_kind":"list"},"MINNNCT":{"name":"MINNNCT","sections":["GRID"],"supported":false,"summary":"The MINNNCT keyword defines a minimum non-neighbor connection transmissibility below which the non-neighbor connection is deleted. The keyword allows for three minimum values, one for the transmissibility, one for the diffusivity and one for the thermal transmissibility. If the keyword is absent from the input deck then no minimum cut-off is applied.","parameters":[{"index":1,"name":"CUTOFF_TRANSMISSIBILITY","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Transmissibility"},{"index":2,"name":"DIFFUSIVITY","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Length"},{"index":3,"name":"CUTOFF_THERMAL_TRANSMISSIBILITY","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Energy/AbsoluteTemperature*Time"}],"example":"","expected_columns":3,"size_kind":"fixed","size_count":1},"MINPORV":{"name":"MINPORV","sections":["GRID"],"supported":null,"summary":"MINPORV defines a minimum threshold pore volume that makes all grid blocks whose pore volume is below this value inactive in the model (inactive cells are not used in OPM Flow calculations). Note this keyword is different to the MINPVV keyword in the GRID section, that sets a minimum threshold pore volume for individual cells in the model.","parameters":[{"index":1,"name":"MINPORV","description":"MINPORV is a real positive number that defines the minimum pore volume for a cell to be active in the model.","units":{"field":"rb 1.0e-6","metric":"rm3 1.0e-6","laboratory":"rcc 1.0e-6"},"default":"Defined","value_type":"DOUBLE","dimension":"ReservoirVolume"}],"example":"--\n-- MINIMUM PORE VOLUME FOR ACTIVE CELLS\n--\nMINPORV\n500.0 /\nThe above example defines 500 rb (or m3) as the minimum pore volume for a cell to be active in the model.","expected_columns":1,"size_kind":"fixed","size_count":1},"MINPV":{"name":"MINPV","sections":["GRID"],"supported":null,"summary":"MINPV defines a minimum threshold pore volume that makes all grid blocks whose pore volume is below this value inactive in the model (inactive cells are not used in OPM Flow calculations). Note this keyword is different to the MINPVV keyword in the GRID section, that sets a minimum threshold pore volume for individual cells in the model.","parameters":[{"index":1,"name":"MINPV","description":"MINPV is a real positive number that defines the minimum pore volume for a cell to be active in the model.","units":{"field":"rb 1.0e-6","metric":"rm3 1.0e-6","laboratory":"rcc 1.0e-6"},"default":"Defined","value_type":"DOUBLE","dimension":"ReservoirVolume"}],"example":"--\n-- MINIMUM PORE VOLUME FOR ACTIVE CELLS\n--\nMINPV\n500.0 /\nThe above example defines 500 rb (or m3) as the minimum pore volume for a cell to be active in the model.","expected_columns":1,"size_kind":"fixed","size_count":1},"MINPVV":{"name":"MINPVV","sections":["GRID"],"supported":null,"summary":"MINPVV is an array that defines the minimum threshold pore volume for each cell, that makes grid blocks whose pore volume is below this value inactive in the model (inactive cells are not used in OPM Flow calculations).","parameters":[{"index":1,"name":"MINPVV","description":"MINPVV is an array of real positive numbers that defines the minimum pore volumes for each cell in the model in order for the cells to be active.","units":{"field":"rb 1.0e-6","metric":"rm3 1.0e-6","laboratory":"rcc 1.0e-6"},"default":"Defined"}],"example":"The example below shows how to define 500 rb (or m3) as the minimum pore volume for all cells in layer 19 to be active in the model, and 750 rb (or m3) as the minimum pore volume for all cells in layer 20, by using the BOX keyword to set the portion of the grid of interest.\n--\n-- DEFINE A BOX GRID FOR THE BOTTOM TWO LAYERS OF A 100 X 100 X 20 MODEL\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1* 1* 1* 1* 19 20 / SELECT THE BOTTOM LAYERS\n--\n-- MINIMUM PORE VOLUME FOR INDIVIDUAL CELLS TO BE ACTIVE\n--\nMINPVV\n10000*500.0 10000*750.0 /\n--\n-- RESET THE INPUT BOX TO BE THE FULL MODEL\n--\nENDBOX\nAlthough this will work in the commercial simulators, it does not currently work in OPM Flow, that is one cannot use the MINPVV keyword in conjunction with the BOX keyword, as shown in the aforementioned example.\nInstead one can use:\n--\n-- MINIMUM PORE VOLUME FOR INDIVIDUAL CELLS TO BE ACTIVE\n--\nMINPVV\n10000* 10000* 10000* 10000* 10000*\n10000* 10000* 10000* 10000* 10000*\n10000* 10000* 10000* 10000* 10000*\n10000* 10000* 10000*\n10000*500.0 10000*750.0 /\nTo accomplish the same thing, where the 10000* instructs the simulator to use the default value of 1.0 x 10-6 for 10,000 cells, which in this case is one layer.","size_kind":"array"},"MINVALUE":{"name":"MINVALUE","sections":["GRID","EDIT","PROPS"],"supported":false,"summary":"The MINVALUE keyword sets a minimum value for the specified array or part of an array. The constant can be an integer or real value depending on the array type; however, the arrays that can be operated on are dependent on which section the MINVALUE keyword is being applied in.","parameters":[{"index":1,"name":"ARRAY","description":"A character string of up to eight characters in length that defines the keyword identifying the array to be modified.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"CONSTANT","description":"CONSTANT is a positive integer or positive real value that an ARRAY element will be reset to if an element in the defined input BOX, as defined by items (3) to (8), is less than CONSTANT. CONSTANT has in the same units as the ARRAY property.","units":{},"default":"None","value_type":"DOUBLE"},{"index":3,"name":"I1","description":"A positive integer that defines the lower bound of the array in the I-direction to be modified must be greater than or equal to one and less than or equal to I2 and NX.","units":{},"default":"1","value_type":"INT"},{"index":4,"name":"I2","description":"A positive integer that defines the upper bound of the array in the I-direction to be modified must be greater than or equal to I1 and less than or equal to NX","units":{},"default":"NX","value_type":"INT"},{"index":5,"name":"J1","description":"A positive integer that defines the lower bound of the array in the J-direction to be modified must be greater than or equal to one and less than or equal to J2 and NY.","units":{},"default":"1","value_type":"INT"},{"index":6,"name":"J2","description":"A positive integer that defines the upper bound of the array in the J-direction to be modified must be greater than or equal to J1 and less than or equal to NY.","units":{},"default":"NY","value_type":"INT"},{"index":7,"name":"K1","description":"A positive integer that defines the lower bound of the array in the K-direction to be modified must be greater than or equal to one and less than or equal to K2 and NZ.","units":{},"default":"1","value_type":"INT"},{"index":8,"name":"K2","description":"A positive integer that defines the upper bound of the array in the K-direction to be modified must be greater than or equal to K1 and less than or equal to NZ.","units":{},"default":"NZ","value_type":"INT"}],"example":"--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nMINVALUE\nPERMX 1.0E0 1* 1* 1* 1* 1* 1* / MINIMUM PERMX\nPERMY 1.0E0 1* 1* 1* 1* 1* 1* / MINIMUM PERMY\nPERMZ 1.0E-1 1* 1* 1* 1* 1* 1* / MINIMUM PERMZ\n/\nThe above example resets the minimum values for the PERMX, PERMY and PERMZ, arrays to 1.0, 1.0 and 0.1, respectively, for all cells.\n| EQUALS Keyword and Variable Options by Section | | | | | | |\n|------------------------------------------------|---------|-------|---------|----------|---------|----------|\n| GRID | EDIT | PROPS | REGIONS | SOLUTION | SUMMARY | SCHEDULE |\n| DX | DEPTH | SWL | | | | |\n| DY | PORV | SWCR | | | | |\n| DZ | TRANX | SWU | | | | |\n| PERMX | TRANY | SGL | | | | |\n| PERMY | TRANZ | SGCR | | | | |\n| PERMZ | DIFFX | SGU | | | | |\n| MULTX | DIFFY | KRW | | | | |\n| MULTY | DIFFZ | KRO | | | | |\n| MULTZ | TRANR | KRG | | | | |\n| DR | TRANTHT | PCG | | | | |\n| DTHETA | DIFFR | PCW | | | | |\n| PERMR | DIFFTHT | | | | | |\n| PERMTHT | | | | | | |\n| DZNET | | | | | | |\n| PORO | | | | | | |\n| NTG | | | | | | |\n| FLUXNUM | | | | | | |\n| MULTNUM | | | | | | |\n| MPFANUM | | | | | | |\n| DIFFX | | | | | | |\n| DIFFY | | | | | | |\n| DIFFZ | | | | | | |\n| DIFFR | | | | | | |\n| DIFFTHT | | | | | | |","expected_columns":8,"size_kind":"list"},"MPFANUM":{"name":"MPFANUM","sections":["GRID"],"supported":false,"summary":"The MPFANUM keyword defines regions in the model where the multi-point flux discretization should be applied.","parameters":[],"example":"","size_kind":"array"},"MPFNNC":{"name":"MPFNNC","sections":["GRID"],"supported":false,"summary":"The MPFNNC keyword defines multi-point flux non-neighbor connections explicitly.","parameters":[],"example":"","size_kind":"none","size_count":0},"MULTFLT":{"name":"MULTFLT","sections":["GRID","EDIT","SCHEDULE"],"supported":null,"summary":"MULTFLT enables the transmissibilities across defined faults, as declared by the FAULTS keyword, to be modified. They keyword allows for the re-scaling of the existing fault transmissibilities calculated by OPM Flow, for example setting a fault to be completely sealing by setting the multiplier to zero.","parameters":[{"index":1,"name":"FLTNAME","description":"FLTNAME is a character string enclosed in quotes with a maximum length of eight characters, that defines the name of the fault that FLTMULT will be applied to. FLTNAME must have previously been defined using the FAULTS keyword in GRID section","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"FLT-TRS","description":"A positive real number that sets the transmissible multiplier to be applied to the FLTNAME transmissibilities positive real number that sets the transmissible multiplier to be applied to the FLTNAME transmissibilities.","units":{},"default":"1.0","value_type":"DOUBLE"},{"index":3,"name":"FLT-DIF","description":"A positive real number that sets the diffusivity multiplier to be applied to the FLTNAME diffusivities. This option should only be used if the Diffusion option has been made activate by the DIFFUSE keyword in the RUNSPEC section. OPM Flow does not support this Diffusion option.","units":{},"default":"1.0"}],"example":"--\n-- MODIFY THE TRANSMISSIBILITES ACROSS DEFINED FAULTS\n--\n-- FAULT TRANS DIFUSS\n-- NAME MULTIPLIER MULTIPLIER\nMULTFLT\n'FAULT01' 0.0 / FAULT MULTIPLIERS\n'FAULT02' 0.0 / FAULT MULTIPLIERS\n'FAULT03' 0.0 / FAULT MULTIPLIERS\n/\nThe above example sets the fault transmissibility multiplier for defined faults named FAULT01, FAULT02, and FAULT03 to zero making the faults sealing in the model.","expected_columns":2,"size_kind":"list"},"MULTIPLY":{"name":"MULTIPLY","sections":["GRID","EDIT","PROPS","REGIONS","SOLUTION"],"supported":false,"summary":"The MULTIPLY keyword multiplies a specified array or part of an array by a constant. The constant can be an integer or real value depending on the array type; however, the arrays that can be operated on are dependent on which section the MULTIPLY keyword is being applied in.","parameters":[{"index":1,"name":"ARRAY","description":"A character string of up to eight characters in length that defines the keyword identifying the property to be modified.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"CONSTANT","description":"An integer or real value to multiply the ARRAY by in the same units as the ARRAY property.","units":{},"default":"None","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"I1","description":"A positive integer that defines the lower bound of the array in the I-direction to be modified must be greater than or equal to one and less than or equal to I2 and NX.","units":{},"default":"1","value_type":"INT"},{"index":4,"name":"I2","description":"A positive integer that defines the upper bound of the array in the I-direction to be modified must be greater than or equal to II and less than or equal to NX","units":{},"default":"NX","value_type":"INT"},{"index":5,"name":"J1","description":"A positive integer that defines the lower bound of the array in the J-direction to be modified must be greater than or equal to one and less than or equal to J2 and NY.","units":{},"default":"1","value_type":"INT"},{"index":6,"name":"J2","description":"A positive integer that defines the upper bound of the array in the J-direction to be modified must be greater than or equal to JI and less than or equal to NY.","units":{},"default":"NY","value_type":"INT"},{"index":7,"name":"K1","description":"A positive integer that defines the lower bound of the array in the K-direction to be modified must be greater than or equal to one and less than or equal to K2 and NZ.","units":{},"default":"1","value_type":"INT"},{"index":8,"name":"K2","description":"A positive integer that defines the upper bound of the array in the K-direction to be modified must be greater than or equal to KI and less than or equal to NZ.","units":{},"default":"NZ","value_type":"INT"}],"example":"--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nMULTIPLY\nPERMZ 0.50000 1* 1* 1* 1* 1* 1* / PERMZ * 0.5\n/\nThe above example multiples the PERMZ property array by 0.5 throughout the model.\n| MULTIPLY Keyword and Variable Options by Section | | | | | | |\n|--------------------------------------------------|---------|-------|---------|----------|---------|----------|\n| GRID | EDIT | PROPS | REGIONS | SOLUTION | SUMMARY | SCHEDULE |\n| DX | DEPTH | SWL | ENDNUM | PRESSURE | | |\n| DY | PORV | SWCR | EQLNUM | SWAT | | |\n| DZ | TRANX | SWU | FIPNUM | SGAS | | |\n| PERMX | TRANY | SGL | IMBNUM | RV | | |\n| PERMY | TRANZ | SGCR | MISCNUM | RS | | |\n| PERMZ | DIFFX | SGU | PVTNUM | TBLK | | |\n| MULTX | DIFFY | KRW | ROCKNUM | GI | | |\n| MULTY | DIFFZ | KRO | SATNUM | OILAPI | | |\n| MULTZ | TRANR | KRG | WH2NUM | SALT | | |\n| DR | TRANTHT | PCG | | GASCONC | | |\n| DTHETA | DIFFR | PCW | | SOLVCONC | | |\n| PERMR | DIFFTHT | | | SOLVFRAC | | |\n| PERMTHT | | | | SFOAM | | |\n| DZNET | | | | SPOLY | | |\n| PORO | | | | | | |\n| NTG | | | | | | |\n| FLUXNUM | | | | | | |\n| MULTNUM | | | | | | |\n| MPFANUM | | | | | | |\n| DIFFX | | | | | | |\n| DIFFY | | | | | | |\n| DIFFZ | | | | | | |\n| DIFFR | | | | | | |\n| DIFFTHT | | | | | | |","expected_columns":8,"size_kind":"list"},"MULTIREG":{"name":"MULTIREG","sections":["GRID","EDIT","PROPS","REGIONS","SOLUTION"],"supported":false,"summary":"The MULTIREG keyword multiplies an array or part of an array by a constant for cells with a specific region number. The region number array can be FLUXNUM, MULTNUM or OPERNUM and these arrays must be defined and be available before the MULTIREG keyword is read by the simulator. The constant can be an integer or real value depending on the array type; however, the arrays that can be operated on are dependent on which section the MULTIREG keyword is being applied in.","parameters":[{"index":1,"name":"ARRAY","description":"A character string of up to eight characters in length that defines the keyword identifying the array to be modified.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"CONSTANT","description":"An integer or real value to multiply the ARRAY by in the same units as the ARRAY property for a given REGION.","units":{},"default":"0","value_type":"DOUBLE"},{"index":3,"name":"REGION NUMBER","description":"REGION NUMBER is a positive integer representing the region for which the CONSTANT in (2) should be applied.","units":{},"default":"None","value_type":"INT"},{"index":4,"name":"REGION ARRAY","description":"The REGION ARRAY to use for applying the CONSTANT in (2) based on the REGION NUMBER in (3). REGION ARRAY can have the following values: F for the FLUXNUM array M for the MULTNUM array O for the OPERNUM array","units":{},"default":"M","value_type":"STRING"}],"example":"--\n-- FIRST DEFINE THE PROPERTY ARRAYS AND MULTNUM ARRAYS FOR 10 X 10 X 20 MODEL\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nPORO 0.2000 1* 1* 1* 1* 1* 1* / PORO TO 0.20 IN MODEL\nPERMX 100.00 1* 1* 1* 1* 1* 1* / PERMX TO 0.10 IN MODEL\nMULTNUM 1 1* 1* 1* 1* 1* 1* / MULTNUM IN MODEL\nMULTNUM 2 1* 5 1 5 6 6 / MULTNUM IN MODEL\nMULTNUM 3 1* 1* 1* 1* 10 10 / MULTNUM IN MODEL\n/\n--\n-- NOW RESET PORO AND PERMX BASED ON THE MULTNUM REGION NUMBER\n--\n-- MULTIPLY AN ARRAY BY A CONSTANT BASED ON A REGION NUMBER\n--\n-- ARRAY CONSTANT REGION REGION ARRAY\n-- VALUE NUMBER M / F / O\nMULTIREG\nPORO 1.050 1 M /\nPORO 1.100 2 M /\nPORO 0.950 3 M /\nPERMX 1.25 1 M /\nPERMX 1.30 2 M /\nPERMX 0.90 3 M /\n/\nThe example first defines the PORO and PERMX property arrays for the model and then sets the MULTNUM array to 1 for all cells in the model, after which selected areas of model are assigned various MULTNUM integer values. The MULTIREG can then be invoked to multiply the PORO and PERMX arrays by a constant for the various MULTNUM regions.\n| MULTREG Keyword and Variable Options by Section | | | | | | |\n|-------------------------------------------------|---------|-------|---------|----------|---------|----------|\n| GRID | EDIT | PROPS | REGIONS | SOLUTION | SUMMARY | SCHEDULE |\n| DX | DEPTH | SWL | ENDNUM | PRESSURE | | |\n| DY | PORV | SWCR | EQLNUM | SWAT | | |\n| DZ | TRANX | SWU | FIPNUM | SGAS | | |\n| PERMX | TRANY | SGL | IMBNUM | RV | | |\n| PERMY | TRANZ | SGCR | MISCNUM | RS | | |\n| PERMZ | DIFFX | SGU | PVTNUM | TBLK | | |\n| MULTX | DIFFY | KRW | ROCKNUM | GI | | |\n| MULTY | DIFFZ | KRO | SATNUM | OILAPI | | |\n| MULTZ | TRANR | KRG | WH2NUM | SALT | | |\n| DR | TRANTHT | PCG | | GASCONC | | |\n| DTHETA | DIFFR | PCW | | SOLVCONC | | |\n| PERMR | DIFFTHT | | | SOLVFRAC | | |\n| PERMTHT | | | | SFOAM | | |\n| DZNET | | | | SPOLY | | |\n| PORO | | | | | | |\n| NTG | | | | | | |\n| FLUXNUM | | | | | | |\n| MULTNUM | | | | | | |\n| MPFANUM | | | | | | |\n| DIFFX | | | | | | |\n| DIFFY | | | | | | |\n| DIFFZ | | | | | | |\n| DIFFR | | | | | | |\n| DIFFTHT ","expected_columns":4,"size_kind":"list"},"MULTNUM":{"name":"MULTNUM","sections":["GRID"],"supported":null,"summary":"The MULTNUM keyword defines the inter-region transmissibility region numbers for each grid block, as such there must be one entry for each cell in the model. The array can be used with the EQUALREG, ADDREG, COPYREG, MULTIREG, MULTREGP and MULTREGT keywords in calculating various grid properties in the GRID section.","parameters":[{"index":1,"name":"MULTNUM","description":"MULTNUM defines an array of positive integers assigning a grid cell to a particular inter-region transmissibility region. The maximum number of MULTNUM regions is set by the NRMULT variable on the GRIDOPTS keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"The example below sets three MULTNUM regions for a 4 x 5 x 2 model.\n--\n-- DEFINE MULTNUM REGIONS FOR ALL CELLS\n--\nMULTNUM\n2 2 1 1 2 2 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n3 3 1 1 3 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n/\nAlternatively the EQUALS keyword could be employed to accomplish the same task, that is:\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nMULTNUM 1 1* 1* 1* 1* 1* 1* / SET REGION 1\nMULTNUM 2 1 2 1 2 1 1 / SET REGION 2\nMULTNUM 3 1 2 1 2 2 2 / SET REGION 3\n/\nOne can then increase PERMX by 25% in region three only.\n--\n-- MULTIPLY AN ARRAY BY A CONSTANT BASED ON A REGION NUMBER\n--\n-- ARRAY CONSTANT REGION REGION ARRAY\n-- VALUE NUMBER M / F / O\nMULTIREG\nPERMX 1.25 3 M /\n/","size_kind":"array"},"MULTPV":{"name":"MULTPV","sections":["GRID","EDIT"],"supported":null,"summary":"MULTPV multiples the pore volumes of a cell by a real positive constant for all the cells in the model via an array. An alternative to defining the complete array is to use the BOX keyword to define an area of the grid and then use the MULTPV keyword to set the multipliers just for the area defined by the BOX keyword (see the example).","parameters":[{"index":1,"name":"MULTPV","description":"MULTPV is an array of real positive numbers assigning the pore volume multipliers for each cell in the model. Repeat counts may be used, for example 20*100.0.","units":{},"default":"1.0"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n10 10 1 6 1 3 / DEFINE BOX AREA\n--\n-- SET PORE VOLUME MULTIPLIERS\n--\nMULTPV\n18*0.0500 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe above example defines a 0.05 scaling multiplier for the 18 cells defined by the preceding BOX statement. The ENDBOX keyword resets the input box to the full grid.","size_kind":"array"},"MULTR-":{"name":"MULTR-","sections":["GRID","EDIT","SCHEDULE"],"supported":null,"summary":"MULTR- multiples the transmissibility between two cell faces in the -R direction for all the cells in the model via an array, that is the keyword sets the transmissibility multiplier of block (I, J, K) between the cells (I-1, J, K) and (I, J, K). An alternative to defining the complete array is to use the BOX keyword to define an area of the grid and then use the MULTR- keyword to set the multipliers just for the area defined by the BOX keyword (see the example).","parameters":[{"index":1,"name":"MULTR-","description":"MULTR- is an array of real positive numbers assigning the transmissibility multipliers in the -R direction to each cell face in the model. Repeat counts may be used, for example 20*100.0.","units":{},"default":"1.0"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n10 10 1 6 1 1 / DEFINE BOX AREA\n--\n-- SET MULTR- TRANSMISSIBILITY MULTIPLIERS\n--\nMULTR-\n6*0.500 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe above example defines a 0.5 scaling multiplier for the six cells defined by the preceding BOX statement. The ENDBOX keyword resets the input box to the full grid."},"MULTR":{"name":"MULTR","sections":["GRID","EDIT","SCHEDULE"],"supported":null,"summary":"MULTR multiples the transmissibility between two cell faces in the +R direction for all the cells in the model via an array, that is the keyword sets the transmissibility multiplier of block (I, J, K) between the cells (I, J, K) and (I+I, J, K). An alternative to defining the complete array is to use the BOX keyword to define an area of the grid and then use the MULTR keyword to set the multipliers just for the area defined by the BOX keyword (see the example).","parameters":[{"index":1,"name":"MULTR+","description":"MULTR+ is an array of real positive numbers assigning the transmissibility multipliers in the +R direction to each cell face in the model. Repeat counts may be used, for example 20*100.0.","units":{},"default":"1.0"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n10 10 1 6 1 3 / DEFINE BOX AREA\n--\n-- SET MULTR+ TRANSMISSIBILITY MULTIPLIERS\n--\nMULTR\n18*0.300 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe above example defines a 0.3 scaling multiplier for the 18 cells defined by the preceding BOX statement. The ENDBOX keyword resets the input box to the full grid."},"MULTREGD":{"name":"MULTREGD","sections":["GRID","EDIT"],"supported":false,"summary":"The MULTREGD keyword multiplies the diffusivity between two regions by a constant. The region number array can be FLUXNUM, MULTNUM or OPERNUM and these arrays must be defined and be available before the MULTREGD keyword is read by the simulator. The constant should be a real number.","parameters":[{"index":1,"name":"REGION1","description":"A positive integer value that defines the from REGION number for which the CONSTANT in (3) should be applied.","units":{},"default":"None","value_type":"INT"},{"index":2,"name":"REGION2","description":"A positive integer value that defines the to REGION number for which the CONSTANT in (3) should be applied.","units":{},"default":"None","value_type":"INT"},{"index":3,"name":"CONSTANT","description":"A real value to multiply the diffusivity between REGION1 and REGION2.","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"},{"index":4,"name":"DIR","description":"A character string that defines the direction to apply the diffusivity multiplier between the two regions, should be set to one of the following X, Y, Z, XY, XZ, YZ, or XYZ.","units":{},"default":"XYZ","value_type":"STRING"},{"index":5,"name":"TYPE","description":"A character string that defines the type of connections the diffusivity multiplier should be applied to, should be one of the following: NNC – Only apply the diffusivity multiplier between REGION1 and REGION2 to non-neighbor connections. NONNC – Do not apply the diffusivity multiplier between REGION1 and REGION2 to non-neighbor connections. ALL - Apply the diffusivity multiplier between REGION1 and REGION2 to all connections.","units":{},"default":"ALL","value_type":"STRING"},{"index":6,"name":"REGION ARRAY","description":"The REGION ARRAY to use for applying the CONSTANT in (3) based on the regions REGION1 and REGION2 in (1 and 2). REGION ARRAY can have the following values: F for the FLUXNUM array M for the MULTNUM array O for the OPERNUM array","units":{},"default":"M","value_type":"STRING"}],"example":"--\n-- MULTIPLY DIFFUSIVITIES BETWEEN RESERVOIRS\n--\n-- REGION REGION DIFFS DIREC NNC REGION ARRAY\n-- FROM TO MULT OPT OPTS M / F / O\nMULTREGD\n1* 1* 1.05 1* 'ALL' M / ALL REGIONS\n/\nThe above example multiplies the diffusivities between all the MULTNUM regions by 1.05 in all directions and for all connections types.","expected_columns":6,"size_kind":"list"},"MULTREGH":{"name":"MULTREGH","sections":["GRID","EDIT"],"supported":false,"summary":"The MULTREGH keyword multiplies the thermal conductivity between two regions by a constant. The region number array can be FLUXNUM, MULTNUM or OPERNUM and these arrays must be defined and be available before the MULTREGT keyword is read by the simulator. The constant should be a real number.","parameters":[{"index":1,"name":"REGION1","description":"A positive integer value that defines the from REGION number for which the CONSTANT in (3) should be applied.","units":{},"default":"None","value_type":"INT"},{"index":2,"name":"REGION2","description":"A positive integer value that defines the to REGION number for which the CONSTANT in (3) should be applied.","units":{},"default":"None","value_type":"INT"},{"index":3,"name":"CONSTANT","description":"A real value to multiply the thermal conductivity between REGION1 and REGION2.","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"},{"index":4,"name":"DIR","description":"A character string that defines the direction to apply the thermal conductivity multiplier between the two regions, should be set to one of the following X, Y, Z, XY, XZ, YZ, or XYZ.","units":{},"default":"XYZ","value_type":"STRING"},{"index":5,"name":"TYPE","description":"A character string that defines the type of connections the thermal conductivity multiplier should be applied to, should be one of the following: NNC – Only apply the thermal conductivity multiplier between REGION1 and REGION2 to non-neighbor connections. NONNC – Do not apply the thermal conductivity multiplier between REGION1 and REGION2 to non-neighbor connections. ALL - Apply the thermal conductivity multiplier between REGION1 and REGION2 to all connections.","units":{},"default":"ALL","value_type":"STRING"},{"index":6,"name":"REGION ARRAY","description":"The REGION ARRAY to use for applying the CONSTANT in (3) based on the regions REGION1 and REGION2 in (1 and 2). REGION ARRAY can have the following values: F for the FLUXNUM array. M for the MULTNUM array. O for the OPERNUM array.","units":{},"default":"M","value_type":"STRING"}],"example":"--\n-- MULTIPLY THERMAL CONDUCTIVITIES BETWEEN RESERVOIRS\n--\n-- REGION REGION CONDS DIREC NNC REGION ARRAY\n-- FROM TO MULT OPT OPTS M / F / O\nMULTREGH\n1* 1* 1.05 1* 'ALL' M / ALL REGIONS\n/\nThe above example multiplies the thermal conductivities between all the MULTNUM regions by 1.05 in all directions and for all connections types.","expected_columns":6,"size_kind":"list"},"MULTREGP":{"name":"MULTREGP","sections":["GRID","EDIT"],"supported":null,"summary":"The MULTREGP keyword multiplies the pore volume of a cell by a constant for all cells with a specific region number. The region number array can be FLUXNUM, MULTNUM or OPERNUM and these arrays must be defined and be available before the MULTREGP keyword is read by the simulator. The constant should be a real number.","parameters":[{"index":1,"name":"REGION","description":"REGION is a positive integer representing the region for which the CONSTANT in (2) should be applied.","units":{},"default":"None","value_type":"INT"},{"index":2,"name":"CONSTANT","description":"A real value to multiply the pore volume by for a given REGION.","units":{},"default":"1","value_type":"DOUBLE"},{"index":3,"name":"REGION ARRAY","description":"The REGION ARRAY to use for applying the CONSTANT in (2) based on the REGION in (1). ARRAY can have the following values: F for the FLUXNUM array. M for the MULTNUM array. O for the OPERNUM array.","units":{},"default":"M","value_type":"STRING"}],"example":"--\n-- RESET PORE VOLUME FOR DIFFERENT REGIONS\n--\n-- REGION PORV REGION ARRAY\n-- NUMBER MULT M / F / O\nMULTREGP\n1 1.0456573 M / Fault Block 1\n2 0 M / Fault Block 2\n3 0.9756715 M / Fault Block 3\n4 0 M / Inactive Blocks\n/\nThe above example re-scales the pore volumes for MULTNUM regions one and three and makes regions two and four inactive by setting their pore volumes to zero.","expected_columns":3,"size_kind":"list"},"MULTREGT":{"name":"MULTREGT","sections":["GRID","EDIT","SCHEDULE"],"supported":null,"summary":"The MULTREGT keyword multiplies the transmissibility between two regions by a constant. The region number array can be FLUXNUM, MULTNUM or OPERNUM and these arrays must be defined and be available before the MULTREGT keyword is read by the simulator. The constant should be a real number.","parameters":[{"index":1,"name":"REGION1","description":"A positive integer value that defines the from REGION number for which the CONSTANT in (3) should be applied.","units":{},"default":"None","value_type":"INT"},{"index":2,"name":"REGION2","description":"A positive integer value that defines the to REGION number for which the CONSTANT in (3) should be applied.","units":{},"default":"None","value_type":"INT"},{"index":3,"name":"CONSTANT","description":"A real positive value to multiply the transmissibility between REGION1 and REGION2.","units":{},"default":"1","value_type":"DOUBLE"},{"index":4,"name":"DIR","description":"A character string that defines the direction to apply the transmissibility multiplier between the two regions, should be set to one of the following X, Y, Z, XY, XZ, YZ, or XYZ.","units":{},"default":"XYZ","value_type":"STRING"},{"index":5,"name":"TYPE","description":"A character string that defines the type of connections the transmissibility multiplier should be applied to, should be one of the following: NNC – Only apply the transmissibility multiplier between REGION1 and REGION2 to non-neighbor connections. NONNC – Do not apply the transmissibility multiplier between REGION1 and REGION2 to non-neighbor connections. ALL – Apply the transmissibility multiplier between REGION1 and REGION2 to all connections.","units":{},"default":"ALL","value_type":"STRING"},{"index":6,"name":"REGION ARRAY","description":"A single character that defines the REGION ARRAY that is used to specify the regions identified by REGION1 and REGION2. REGION ARRAY can have the following values: F for the FLUXNUM array M for the MULTNUM array O for the OPERNUM array","units":{},"default":"M","value_type":"STRING"}],"example":"--\n-- SET TRANSMISSIBILITES ACROSS DIFFERENT RESERVOIRS TO ZERO\n--\n-- REGION REGION TRANS DIREC NNC REGION ARRAY\n-- FROM TO MULT OPT OPTS M / F / O\nMULTREGT\n1* 1* 0.0 1* 'ALL' M / ALL REGIONS SEALED\n/\nThe above example isolates all regions from one another by setting the transmissibility for the MULTNUM regions to zero in all directions and for all connections types.\n| Note Note if the MULTREGT keyword is used in the EDIT section, OPM Flow will always apply the changes irrespective, of if the TRANX, TRANY and TRANZ transmissibility arrays have been entered or not in the EDIT section. This behavior is different to the commercial simulator that only applies the keyword if the transmissibility arrays have been entered in the EDIT section. |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":6,"size_kind":"list"},"MULTTHT-":{"name":"MULTTHT-","sections":["GRID","EDIT","SCHEDULE"],"supported":null,"summary":"MULTTHT- multiples the transmissibility between two cell faces in the -Theta direction for all the cells in the model via an array, that is the keyword sets the transmissibility multiplier of block (I, J, K) between the cells (I, J-1, K) and (I, J, K). An alternative to defining the complete array is to use the BOX keyword to define an area of the grid and then use the MULTTHT- keyword to set the multipliers just for the area defined by the BOX keyword (see the example).","parameters":[{"index":1,"name":"MULTTHT-","description":"MULTTHT- is an array of real positive numbers assigning the transmissibility multipliers in the -Theta direction to each cell face in the model. Repeat counts may be used, for example 20*100.0.","units":{},"default":"1.0"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n10 10 1 6 1 1 / DEFINE BOX AREA\n--\n-- SET MULTTHT- TRANSMISSIBILITY MULTIPLIERS\n--\nMULTTHT-\n6*0.500 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe above example defines a 0.5 scaling multiplier for the six cells defined by the preceding BOX statement. The ENDBOX keyword resets the input box to the full grid."},"MULTTHT":{"name":"MULTTHT","sections":["GRID","EDIT","SCHEDULE"],"supported":null,"summary":"MULTTHT multiples the transmissibility between two cell faces in the +Theta direction for all the cells in the model via an array, that is the keyword sets the transmissibility multiplier of block (I, J, K) between the cells (I, J, K) and (I, J+1, K). An alternative to defining the complete array is to use the BOX keyword to define an area of the grid and then use the MULTTHT keyword to set the multipliers just for the area defined by the BOX keyword (see the example).","parameters":[{"index":1,"name":"MULTTHT+","description":"MULTTHT+ is an array of real positive numbers assigning the transmissibility multipliers in the +Theta direction to each cell face in the model. Repeat counts may be used, for example 20*100.0.","units":{},"default":"1.0"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n10 10 1 6 1 3 / DEFINE BOX AREA\n--\n-- SET MULTTHT+ TRANSMISSIBILITY MULTIPLIERS\n--\nMULTTHT\n18*0.300 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe above example defines a 0.3 scaling multiplier for the 18 cells defined by the preceding BOX statement. The ENDBOX keyword resets the input box to the full grid."},"MULTX-":{"name":"MULTX-","sections":["GRID","EDIT","SCHEDULE"],"supported":null,"summary":"MULTX- multiples the transmissibility between two cell faces in the -X direction for all the cells in the model via an array, that is the keyword sets the transmissibility multiplier of block (I, J, K) between the cells (I-1, J, K) and (I, J, K). An alternative to defining the complete array is to use the BOX keyword to define an area of the grid and then use the MULTX- keyword to set the multipliers just for the area defined by the BOX keyword (see the example).","parameters":[{"index":1,"name":"MULTX-","description":"MULTX- is an array of real positive numbers assigning the transmissibility multipliers in the -X direction to each cell face in the model. Repeat counts may be used, for example 20*100.0.","units":{},"default":"1.0"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n10 10 1 6 1 1 / DEFINE BOX AREA\n--\n-- SET MULTX- TRANSMISSIBILITY MULTIPLIERS\n--\nMULTX-\n6*0.500 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe above example defines a 0.5 scaling multiplier for the six cells defined by the preceding BOX statement. The ENDBOX keyword resets the input box to the full grid."},"MULTX":{"name":"MULTX","sections":["GRID","EDIT","SCHEDULE"],"supported":null,"summary":"MULTX multiples the transmissibility between two cell faces in the +X direction for all the cells in the model via an array, that is the keyword sets the transmissibility multiplier of block (I, J, K) between the cells (I, J, K) and (I+I, J, K).","parameters":[{"index":1,"name":"MULTX+","description":"MULTX+ is an array of real positive numbers assigning the transmissibility multipliers in the +X direction to each cell face in the model. Repeat counts may be used, for example 20*100.0.","units":{},"default":"1.0"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n10 10 1 6 1 3 / DEFINE BOX AREA\n--\n-- SET MULTX+ TRANSMISSIBILITY MULTIPLIERS\n--\nMULTX\n18*0.300 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe above example defines a 0.3 scaling multiplier for the 18 cells defined by the preceding BOX statement. The ENDBOX keyword resets the input box to the full grid."},"MULTY-":{"name":"MULTY-","sections":["GRID","EDIT","SCHEDULE"],"supported":null,"summary":"MULTY- multiples the transmissibility between two cell faces in the -Y direction for all the cells in the model via an array, that is the keyword sets the transmissibility multiplier of block (I, J, K) between the cells (I, J-1, K) and (I, J, K). An alternative to defining the complete array is to use the BOX keyword to define an area of the grid and then use the MULTY- keyword to set the multipliers just for the area defined by the BOX keyword (see the example).","parameters":[{"index":1,"name":"MULTY-","description":"MULTY- is an array of real positive numbers assigning the transmissibility multipliers in the -Y direction to each cell face in the model. Repeat counts may be used, for example 20*100.0.","units":{},"default":"1.0"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n10 10 1 6 1 1 / DEFINE BOX AREA\n--\n-- SET MULTY- TRANSMISSIBILITY MULTIPLIERS\n--\nMULTY-\n6*0.500 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe above example defines a 0.5 scaling multiplier for the six cells defined by the preceding BOX statement. The ENDBOX keyword resets the input box to the full grid."},"MULTY":{"name":"MULTY","sections":["GRID","EDIT","SCHEDULE"],"supported":null,"summary":"MULTY multiples the transmissibility between two cell faces in the +Y direction for all the cells in the model via an array, that is the keyword sets the transmissibility multiplier of block (I, J, K) between the cells (I, J, K) and (I, J+1, K).","parameters":[{"index":1,"name":"MULTY+","description":"MULTY+ is an array of real positive numbers assigning the transmissibility multipliers in the +Y direction to each cell face in the model. Repeat counts may be used, for example 20*100.0.","units":{},"default":"1.0"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n10 10 1 6 1 3 / DEFINE BOX AREA\n--\n-- SET MULTY+ TRANSMISSIBILITY MULTIPLIERS\n--\nMULTY\n18*0.300 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe above example defines a 0.3 scaling multiplier for the 18 cells defined by the preceding BOX statement. The ENDBOX keyword resets the input box to the full grid."},"MULTZ-":{"name":"MULTZ-","sections":["GRID","EDIT","SCHEDULE"],"supported":null,"summary":"MULTZ- multiples the transmissibility between two cell faces in the -Z direction for all the cells in the model via an array, that is the keyword sets the transmissibility multiplier of block (I, J, K) between the cells (1, J, K-1) and (I, J, K). An alternative to defining the complete array is to use the BOX keyword to define an area of the grid and then use the MULTZ- keyword to set the multipliers just for the area defined by the BOX keyword (see the example).","parameters":[{"index":1,"name":"MULTZ-","description":"MULTZ- is an array of real positive numbers assigning the transmissibility multipliers in the -X direction to each cell face in the model. Repeat counts may be used, for example 20*100.0.","units":{},"default":"1.0"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n10 10 1 6 1 1 / DEFINE BOX AREA\n--\n-- SET MULTZ- TRANSMISSIBILITY MULTIPLIERS\n--\nMULTZ-\n6*0.500 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe above example defines a 0.5 scaling multiplier for the six cells defined by the preceding BOX statement. The ENDBOX keyword resets the input box to the full grid."},"MULTZ":{"name":"MULTZ","sections":["GRID","EDIT","SCHEDULE"],"supported":null,"summary":"MULTZ multiples the transmissibility between two cell faces in the +Z direction for all the cells in the model via an array, that is the keyword sets the transmissibility multiplier of block (I, J, K) between the cells (I, J, K) and (I, J, K+1).","parameters":[{"index":1,"name":"MULTZ+","description":"MULTZ+ is an array of real positive numbers assigning the transmissibility multipliers in the +Z direction to each cell face in the model. Repeat counts may be used, for example 20*100.0.","units":{},"default":"1.0"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n10 10 1 18 1 1 / DEFINE BOX AREA\n--\n-- SET MULTZ+ TRANSMISSIBILITY MULTIPLIERS\n--\nMULTZ\n18*0.300 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe above example defines a 0.3 scaling multiplier for the 18 cells defined by the preceding BOX statement. The ENDBOX keyword resets the input box to the full grid."},"NEWTRAN":{"name":"NEWTRAN","sections":["GRID"],"supported":null,"summary":"This keyword switches on Irregular Corner-Point Grid geometry transmissibility calculation, which is the default option for this type of grid. Grids defined with the COORD and ZCORN keywords will always invoke this option by default.","parameters":[],"example":"--\n-- ACTIVATE IRREGULAR CORNER-POINT GRID TRANSMISSIBILITIES\n--\nNEWTRAN\nThe above example manually activates Irregular Corner-Point Grid transmissibility calculations.","size_kind":"none","size_count":0},"NINENUM":{"name":"NINENUM","sections":["GRID"],"supported":false,"summary":"The NINENUM keyword defines areas in the grid that should use the Nine-Point Discretization formulation by setting a grid block’s NINENUM value to one, or zero for the conventional standard five-point discretization formulation, for when the Nine-Point Discretization formulation has been activated by the NINEPOIN keyword in the RUNSPEC section. There should be a NINENUM value for each grid block in the model. Note that if the if the NINEPOIN keyword in the RUNSPEC section has been invoked and the NINENUM keyword has not been used in the input deck, then all the grid will use the nine-point scheme.","parameters":[{"index":1,"name":"NINENUM","description":"NINENUM defines an integer array of zeros and ones assigning a grid cell to a particular discretization region, a value of zero for five-point or a value of one for nine-point discretization. Note that the default value of one implies a cell is included in the Nine-Point Discretization region; thus, if a cell is to use the conventional standard five-point finite difference discretization formulation, then NINENUM must be explicitly set to zero.","units":{},"default":"1"}],"example":"The example below sets a portion of the model to us the Nine-Point Discretization formulation.\n--\n-- DEFINE NINE-POINT DISCRETIZATION REGION FOR ALL CELLS\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nNINENUM’ 0 1* 1* 1* 1* 1* 1* / FIVE-POINT\nNINENUM’ 1 1* 1* 1* 1* 1 5 / NINE-POINT\n/\nHere the first line sets all the grid to us the five-point discretization formulation, all values set to zero, and then the second line sets all the cells in the layers one to five to use the nine-point discretization formulation.","size_kind":"array"},"NMATOPTS":{"name":"NMATOPTS","sections":["GRID"],"supported":false,"summary":"The NMATOPTS keyword defines the Discretized Matrix Dual Porosity parameters for when the Discretized Matrix Dual Porosity option has been activated by NMATRIX keyword in the RUNSPEC section. The option allows the matrix grid blocks to be subdivided into smaller cells for more accurate flow calculations, in particular the modeling of transient flow within the matrix grid blocks.","parameters":[{"index":1,"name":"GEOMETRY","description":"","units":{},"default":"LINEAR","value_type":"STRING"},{"index":2,"name":"FRACTION_PORE_VOL","description":"","units":{},"default":"0.1","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"METHOD","description":"","units":{},"default":"FPORV","value_type":"STRING"}],"example":"","expected_columns":3,"size_kind":"fixed","size_count":1},"NNC":{"name":"NNC","sections":["GRID"],"supported":null,"summary":"NNC enables Non-Neighbor Connections (“NNC”) to be manually defined. This keyword is normally generated by static modeling software as opposed to be manually entered in the OPM Flow input deck due to the verbosity and complexity of calculating the required parameters for this keyword.","parameters":[{"index":1,"name":"I1","description":"A positive integer that defines the first grid block in the I-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NX on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":2,"name":"J1","description":"A positive integer that defines the first grid block in the J-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NY on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":3,"name":"K1","description":"A positive integer that defines the first grid block in the K-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NZ on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":4,"name":"I2","description":"A positive integer that defines the second grid block in the I-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NX on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":5,"name":"J2","description":"A positive integer that defines the second grid block in the J-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NY on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":6,"name":"K2","description":"A positive integer that defines the second grid block in the K-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NZ on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":7,"name":"TRANSNNC","description":"TRANSNNC is a positive real number greater than or equal to zero that defines the transmissibility between the first grid block (I1, J1, K1) and the second grid block (I2, J2, K2). The default value of zero sets the transmissibility between the two cells to zero.","units":{"field":"cP.rb/day/psia","metric":"cP.rm3/day/bars","laboratory":"cP.rcc/hr/atm"},"default":"0.0","value_type":"DOUBLE","dimension":"Transmissibility"},{"index":8,"name":"ISATNUM1","description":"ISATNUM1 is a positive integer defining which saturation table number (relative permeability table) to be used for flow from the first grid block to the second grid block. The default value of zero means the existing saturation table allocated to the upstream cell (I1,J1,K1).","units":{},"default":"0","value_type":"INT"},{"index":9,"name":"ISATNUM2","description":"ISATNUM2 is a positive integer defining which saturation table number (relative permeability table) to be used for flow from the second grid block to the first grid block. The default value of zero means the existing saturation table allocated to the downstream cell (I2,J2,K2).","units":{},"default":"0","value_type":"INT"},{"index":10,"name":"IPRSNUM1","description":"IPRSNUM1 is a positive integer defining which pressure table number (PVT table) to be used for flow from the first grid block to the second grid block. The default value of zero means the existing PVT table allocated to the upstream cell (I1,J1,K1).","units":{},"default":"0","value_type":"INT"},{"index":11,"name":"IPRSNUM2","description":"IPRSNUM2 is a positive integer defining which pressure table number (PVT table) to be used for flow from the second grid block to the first grid block. The default value of zero means the existing PVT table allocated to the downstream cell (I2,J2,K2).","units":{},"default":"0","value_type":"INT"},{"index":12,"name":"FACE1","description":"FACE1 is a character string that defines the face associated with flow from the first grid block to the second grid block, where FACE1 can have values of: X+, X-, Y+, Y-, Z+, or Z-.","units":{},"default":"None","value_type":"STRING"},{"index":13,"name":"FACE2","description":"FACE2 is a character string that defines the face associated with flow from the second grid block to the first grid block, where FACE2 can have values of: X+, X-, Y+, Y-, Z+, or Z-.","units":{},"default":"None","value_type":"STRING"},{"index":14,"name":"DIFFNNC","description":"DIFFNNC is a positive real number that defines the diffusivity between the first grid block (I1, J1, K1) and the second grid block (I2, J2, K2).","units":{"field":"feet","metric":"meters","laboratory":"cm"},"default":"0.0","value_type":"DOUBLE"},{"index":15,"name":"DISPNNC","description":"DISPNNC s a positive real number that defines the dispersion coefficient [1 over ( Area x Porosity)]between the first grid block (I1, J1, K1) and the second grid block (I2, J2, K2), used with the between the first grid block (I1, J1, K1) and the second grid block (I2, J2, K2), used with the DISPERSE option.","units":{"field":"ft-2","metric":"m-2","laboratory":"cm-2"},"default":"0.0","value_type":"DOUBLE","dimension":"ContextDependent"},{"index":16,"name":"AREANNC","description":"AREANNC is a positive real number that defines the area associated with the connection between the first grid block (I1, J1, K1) and the second grid block (I2, J2, K2).","units":{"field":"ft2","metric":"m2","laboratory":"cm2"},"default":"None","value_type":"DOUBLE","dimension":"Length*Length"},{"index":17,"name":"PERMNNC","description":"AREANNC is a positive real number that defines the permeability associated with the connection between the first grid block (I1, J1, K1) and the second grid block (I2, J2, K2). This used by the non-Darcy option.","units":{"field":"mD","metric":"mD","laboratory":"mD"},"default":"None","value_type":"DOUBLE","dimension":"Permeability"}],"example":"--\n-- MANUALLY DEFINE NON-NEIGHBOR CONNECTIONS\n--\n-- ------------ BOX ----------- -- TRANSNNC --\n-- I1 J1 K1 I2 J2 K2\nNNC\n1 1 1 1 1 2 0.2500 / SET NNC FOR FAULT\n1 1 2 1 1 3 0.2500 / SET NNC FOR FAULT\n1 1 3 1 1 4 0.2500 / SET NNC FOR FAULT\n/\nThe above example defines the transmissibility between cells (1, 1, 1) and (1, 1, 2), (1, 1, 2) and (1, 1, 3) and finally between (1, 1, 3) and (1, 1, 4) to be 0.2500.","expected_columns":17,"size_kind":"list"},"NOGGF":{"name":"NOGGF","sections":["GRID"],"supported":false,"summary":"This keyword deactivates the output of a standard GRID or extended GRID file, as well as the extensible EGRID file for post-processing applications.","parameters":[],"example":"--\n-- DEACTIVATE GRID GEOMETRY OUTPUT\n--\nNOGGF\nThe above example switches off the default behavior of writing out the grid geometry files.","size_kind":"none","size_count":0},"NTG":{"name":"NTG","sections":["GRID"],"supported":null,"summary":"NTG defines the Net-to-Gross Ratio (“NTG”) for all the cells in the model via an array. The keyword can be used with all grid types.","parameters":[{"index":1,"name":"NTG","description":"NTG is an array of real numbers greater than or equal to zero and less than or equal to one, that are assigned the net-to-gross ratio values for each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 200*0.850.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK NTG DATA FOR ALL CELLS (BASED ON NX x NY x NZ = 300)\n--\nNTG\n100*1.000 100*0.850 100*0.500 /\nThe above example defines a constant NTG of 1.00 for the first 100 cells, then 0.85 for the second 100 hundred cells, and finally 0.500 for the last 100 cell, for the 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"NXFIN":{"name":"NXFIN","sections":["GRID"],"supported":false,"summary":"NXFIN defines the number of Local Grid Refinement (“LGR”) cells within a global or host cell in the x-direction via a vector, as opposed to defining the size for each cell for a Cartesian LGR Grid. The LGR keyword in the RUNSPEC section should be activated to indicate an LGR is being used, and the keyword NXFIN should be placed in between the CARFIN and ENDFIN keywords in the GRID section.","parameters":[{"index":1,"name":"NXFIN","description":"NXFIN is a vector of integer numbers describing the number of LGR cells within each defined global or host grid block in the x-direction in a Cartesian LGR grid. Repeat counts may be used, for example 2*2.0.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- CARFIN LGR GRID COMMANDS\n--\n-- LGR ----- HOST GRID ------ -- CARFIN GRID -- MAX HOST\n-- NAME I1 I2 J1 J2 K1 K2 NX NY NZ WELLS NAME\nCARFIN\nLGR-OP01 24 25 87 87 1 50 8 1 50 1 GLOBAL /\n--\n-- DEFINE LGR GRID BLOCKS IN THE X-DIRECTION\n--\nNXFIN\n4 4 /\nENDFIN\nThe above example splits the global cells (24-25,87, 1-50) into four and four LGR grid blocks in the x-direction, and since the HXFIN keyword has not been supplied, then the host cells will split into equal proportions.","size_kind":"array"},"NYFIN":{"name":"NYFIN","sections":["GRID"],"supported":false,"summary":"NYFIN defines the number of Local Grid Refinement (“LGR”) cells within a global or host cell in the x-direction via a vector, as opposed to defining the size for each cell for a Cartesian LGR Grid. The LGR keyword in the RUNSPEC section should be activated to indicate an LGR is being used, and the keyword NYFIN should be placed in between the CARFIN and ENDFIN keywords in the GRID section.","parameters":[{"index":1,"name":"NYFIN","description":"NYFIN is a vector of integer numbers describing the number of LGR cells within each defined global or host grid block in the y-direction in a Cartesian LGR grid. Repeat counts may be used, for example 2*2.0.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- CARFIN LGR GRID COMMANDS\n--\n-- LGR ----- HOST GRID ------ -- CARFIN GRID -- MAX HOST\n-- NAME I1 I2 J1 J2 K1 K2 NX NY NZ WELLS NAME\nCARFIN\nLGR-OP01 24 24 86 87 1 50 1 8 50 1 GLOBAL /\n--\n-- DEFINE LGR GRID BLOCKS IN THE Y-DIRECTION\n--\nNYFIN\n4 4 /\nENDFIN\nThe above example splits the global cells (24, 86-87,1-50) into four and four LGR grid blocks in the y-direction and since the HYFIN keyword has not been supplied, then the host cells will split into equal proportions.","size_kind":"array"},"NZFIN":{"name":"NZFIN","sections":["GRID"],"supported":false,"summary":"NZFIN defines the number of Local Grid Refinement (“LGR”) cells within a global or host cell in the z-direction via a vector, as opposed to defining the size for each cell for a Cartesian LGR Grid. The LGR keyword in the RUNSPEC section should be activated to indicate an LGR is being used, and the keyword NXFIN should be placed in between the CARFIN and ENDFIN keywords in the GRID section.","parameters":[{"index":1,"name":"NZFIN","description":"NZFIN is a vector of integer numbers describing the number of LGR cells within each defined global or host grid block in the x-direction in a Cartesian LGR grid. Repeat counts may be used, for example 2*2.0.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- CARFIN LGR GRID COMMANDS\n--\n-- LGR ----- HOST GRID ------ -- CARFIN GRID -- MAX HOST\n-- NAME I1 I2 J1 J2 K1 K2 NX NY NZ WELLS NAME\nCARFIN\nLGR-OP01 24 24 86 86 1 50 8 1 100 1 GLOBAL /\n--\n-- DEFINE LGR GRID BLOCKS IN THE Z-DIRECTION\n--\nNZFIN\n50*2 /\nENDFIN\nThe above example splits the global cells (24, 86, 1-50) into two LGR grid blocks per host cell in the z-direction, and since the HZFIN keyword has not been supplied, then the host cells will split into equal proportions.","size_kind":"array"},"OLDTRAN":{"name":"OLDTRAN","sections":["GRID"],"supported":null,"summary":"This keyword switches on Cartesian Regular Grids geometry transmissibility calculation (or block centered transmissibility calculations), which is the default option for this type of grid. Grids defined by the DX, DY, and DZ series of keywords will always invoke this option by default.","parameters":[],"example":"--\n-- ACTIVATE CARTESIAN REGULAR GRID TRANSMISSIBILITIES\n--\nOLDTRAN\nThe above example manually activates Cartesian Regular Grid transmissibility calculations.","size_kind":"none","size_count":0},"OLDTRANR":{"name":"OLDTRANR","sections":["GRID"],"supported":null,"summary":"This keyword switches on Radial Regular Grids geometry transmissibility calculation (or block centered transmissibility calculations), which is the default option for this type of grid. Grids defined by the DR, DTHETA, and DZ series of keywords will always invoke this option by default.","parameters":[],"example":"--\n-- ACTIVATE RADIAL REGULAR GRID TRANSMISSIBILITIES\n--\nOLDTRANR\nThe above example manually activates Radial Regular Grid transmissibility calculations.","size_kind":"none","size_count":0},"OPERATE":{"name":"OPERATE","sections":["GRID","EDIT","PROPS","REGIONS","SOLUTION"],"supported":false,"summary":"The OPERATE keyword performs a mathematical operation on a specified array or part of an array, optionally using another specified array as input to the operation. The keyword allows for various mathematical functions and their associated variables to be defined and applied to the specified array. Input constants can be integer or real valued depending on the array type; however, the arrays that can be operated on are dependent on which section the OPERATE keyword is being applied in.","parameters":[{"index":1,"name":"Y","description":"A character string of up to eight characters in length that defines the keyword identifying the array to be modified.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"I1","description":"A positive integer that defines the lower bound of the array in the I-direction to be modified must be greater than or equal to one and less than or equal to I2 and NX.","units":{},"default":"1","value_type":"INT"},{"index":3,"name":"I2","description":"A positive integer that defines the upper bound of the array in the I-direction to be modified must be greater than or equal to I1 and less than or equal to NX","units":{},"default":"NX","value_type":"INT"},{"index":4,"name":"J1","description":"A positive integer that defines the lower bound of the array in the J-direction to be modified must be greater than or equal to one and less than or equal to J2 and NY.","units":{},"default":"1","value_type":"INT"},{"index":5,"name":"J2","description":"A positive integer that defines the upper bound of the array in the J-direction to be modified must be greater than or equal to J1 and less than or equal to NY.","units":{},"default":"NY","value_type":"INT"},{"index":6,"name":"K1","description":"A positive integer that defines the lower bound of the array in the K-direction to be modified must be greater than or equal to one and less than or equal to K2 and NZ.","units":{},"default":"1","value_type":"INT"},{"index":7,"name":"K2","description":"A positive integer that defines the upper bound of the array in the K-direction to be modified must be greater than or equal to K1 and less than or equal to NZ.","units":{},"default":"NZ","value_type":"INT"},{"index":8,"name":"EQUATION","description":"A defined character string of up to eight characters that defines the mathematical function to be applied, using the X array and the ALPHA and BETA constants declared on this keyword. EQUATION should be set to one of the following character strings:","units":{},"default":"None","value_type":"STRING"},{"index":9,"name":"X","description":"A character string of up to eight characters in length that defines the keyword identifying the array to be used as an input parameter.","units":{},"default":"None","value_type":"STRING"},{"index":10,"name":"ALPHA","description":"An integer or real value that is the α variable in the EQUATION function.","units":{},"default":"None","value_type":"DOUBLE"},{"index":11,"name":"BETA","description":"An integer or real value that is the β variable in the EQUATION function.","units":{},"default":"None","value_type":"DOUBLE"}],"example":"The first example uses the MULTP function combined with the Net-to-Gross (NTG) array to re-scale the MULTX, MULTY and MULTZ arrays to reduce the transmissibility in three separate reservoirs based on the reservoir quality (NTG).\n--\n-- MATHEMATICAL OPERATIONS ON ARRAYS BY CELL\n--\n-- OUTPUT ---------- BOX --------- OPERATION INPUT ALPHA BETA\n-- ARRAY I1 I2 J1 J2 K1 K2 --------- ARRAY ----- ----\nOPERATE\nMULTX 1* 1* 1* 1* 1 32 ‘MULTP’ NTG 1.00 0.75 / RES1\nMULTY 1* 1* 1* 1* 1 32 ‘MULTP’ NTG 1.00 0.75 / RES1\nMULTZ 1* 1* 1* 1* 1 32 ‘MULTP’ NTG 1.00 0.75 / RES1\nMULTX 1* 1* 1* 1* 34 64 ‘MULTP’ NTG 1.00 0.85 / RES2\nMULTY 1* 1* 1* 1* 34 64 ‘MULTP’ NTG 1.00 0.85 / RES2\nMULTZ 1* 1* 1* 1* 34 64 ‘MULTP’ NTG 1.00 0.85 / RES2\nMULTX 1* 1* 1* 1* 67 96 ‘MULTP’ NTG 1.00 0.50 / RES3\nMULTY 1* 1* 1* 1* 67 96 ‘MULTP’ NTG 1.00 0.50 / RES3\nMULTZ 1* 1* 1* 1* 67 96 ‘MULTP’ NTG 1.00 0.50 / RES3\n/\nThe next example shows how to set the maximum gas saturation (SGU) based on the minimum (lowest) water saturation (SWL) when using the End-Point Scaling option.\n--\n-- MATHEMATICAL OPERATIONS ON ARRAYS\n--\n-- OUTPUT ---------- BOX --------- OPERATION INPUT ALPHA BETA\n-- ARRAY I1 I2 J1 J2 K1 K2 --------- ARRAY ----- ----\nOPERATE\nSGU 1* 1* 1* 1* 1* 1* 'MULTA' SWL -1.0 1.0 /\n/\nThe above example sets the maximum gas saturation to be one minus the minimum water saturation.\n| OPERATE Keyword and Variable Options by Section | | | | | | |\n|-------------------------------------------------|---------|-------|---------|----------|---------|----------|\n| GRID | EDIT | PROPS | REGIONS | SOLUTION | SUMMARY | SCHEDULE |\n| DX | DEPTH | SWL | ENDNUM | PRESSURE | | |\n| DY | PORV | SWCR | EQLNUM | SWAT | | |\n| DZ | TRANX | SWU | FIPNUM | SGAS | | |\n| PERMX | TRANY | SGL | IMBNUM | RV | | |\n| PERMY | TRANZ | SGCR | MISCNUM | RS | | |\n| PERMZ | DIFFX | SGU | PVTNUM | TBLK | | |\n| MULTX | DIFFY | KRW | ROCKNUM | GI | | |\n| MULTY | DIFFZ | KRO | SATNUM | OILAPI | | |\n| MULTZ | TRANR | KRG | WH2NUM | SALT | | |\n| DR | TRANTHT | PCG | | GASCONC | | |\n| DTHETA | DIFFR | PCW | | SOLVCONC | | |\n| PERMR | DIFFTHT | | | SOLVFRAC | | |\n| PERMTHT | | | | SFOAM | | |\n| DZNET | | | | SPOLY | | |\n| PORO | | | | | | |\n| NTG | | | | | | |\n| FLUXNUM | | | | | | |\n| MULTNUM | | | | | | |\n| MPFANUM | | | | | | |\n| DIFFX | | | | | | |\n| DIFFY | | | ","expected_columns":11,"size_kind":"list"},"OPERATER":{"name":"OPERATER","sections":["GRID","EDIT","PROPS","REGIONS","SOLUTION"],"supported":true,"summary":"The OPERATER keyword is similar to the OPERATE keyword, except it applies the mathematical operation on specific regions, whereas, OPERATE applies the operations on a cell by cell basis. Here the OPERATER keyword performs a mathematical operation on a specified property array, optionally using another property array as input to the function. The keyword allows for various mathematical functions and their associated variables to be defined and applied to the specified region data. Input constants can be integer or real valued depending on the array type; however, the arrays that can be operated on are dependent on which section the OPERATER keyword is being applied in.","parameters":[{"index":1,"name":"Y","description":"A character string of up to eight characters in length that defines the keyword identifying the array to be modified.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"REGION","description":"REGION is a positive integer representing the region for which the EQUATION should be applied. The default is to use the region number from the OPERNUM keyword; however this can be reset to another region array via the ARRAY item on this keyword, provided the array exists at the time the keyword is declared in the input deck. Note also the OPERNUM keyword must precede the use of the OPERATER keyword.","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"EQUATION","description":"A defined character string of up to eight characters that defines the mathematical function to be applied, using the X array and the ALPHA and BETA constants declared on this keyword. EQUATION should be set to one of the following character strings:","units":{},"default":"None","value_type":"STRING"},{"index":4,"name":"X","description":"A character string of up to eight characters in length that defines the keyword identifying the array to be used as an input parameter.","units":{},"default":"None","value_type":"STRING"},{"index":5,"name":"ALPHA","description":"An integer or real value that is the α variable in the EQUATION function.","units":{},"default":"None","value_type":"DOUBLE"},{"index":6,"name":"BETA","description":"An integer or real value that is the β variable in the EQUATION function.","units":{},"default":"None","value_type":"DOUBLE"},{"index":7,"name":"ARRAY","description":"The name of the array for which the REGION variable references. This can be any standard region array as declared in the REGION section (FIPNUM, PVTNUM, etc.), provided the array exists at the time the OPERATER keyword is invoked. In addition, the MULTNUM, FLUXNUM and OPERNUM may be used. Only the default value of OPERNUM is supported by OPM Flow.","units":{},"default":"OPERNUM","value_type":"STRING"}],"example":"The first example uses the MULTP function combined with the Net-to-Gross (NTG) array to re-scale the MULTX, MULTY and MULTZ arrays to reduce the transmissibility in three separate reservoirs based on the reservoir quality (NTG). This keyword sequence should be in the GRID section.\n--\n-- MATHEMATICAL OPERATIONS ON ARRAYS BY REGION\n--\n-- OUTPUT REGN OPERATION SOURCE ALPHA BETA REGN\n-- ARRAY NUM TYPE ARRAY CONST CONST ARRAY\nOPERATER\nMULTX 1 'MULTP' NTG 1.00 0.75 / RES1\nMULTY 1 'MULTP' NTG 1.00 0.75 / RES1\nMULTZ 1 'MULTP' NTG 1.00 0.75 / RES1\nMULTX 2 'MULTP' NTG 1.00 0.85 / RES2\nMULTY 2 'MULTP' NTG 1.00 0.85 / RES2\nMULTZ 2 'MULTP' NTG 1.00 0.85 / RES2\nMULTX 3 'MULTP' NTG 1.00 0.50 / RES3\nMULTY 3 'MULTP' NTG 1.00 0.50 / RES3\nMULTZ 3 'MULTP' NTG 1.00 0.50 / RES3\n/\nNotice that the ARRAY variable has been defaulted, resulting in OPERNUM being the regional array for the REGION variable.\nThe next example shows how to set the maximum gas saturation (SGU) based on the minimum (lowest) water saturation (SWL) when using the End-Point Scaling option, in the PROPS section.\n--\n-- MATHEMATICAL OPERATIONS ON ARRAYS\n--\n-- OUTPUT REGN OPERATION SOURCE ALPHA BETA REGN\n-- ARRAY NUM TYPE ARRAY CONST CONST ARRAY\nOPERATER\nSGU 1 'MULTA' SWL -1.0 1.0 /\nSGU 2 'MULTA' SWL -1.0 1.0 /\nSGU 3 'MULTA' SWL -1.0 1.0 /\n/\nThe above example sets the maximum gas saturation to be one minus the minimum water saturation for regions one to three.\nThe final example shows how to reset the FIPNUM array when the exported array from the earth model does not correspond to the simulator’s desired numbering scheme.\n--\n-- MATHEMATICAL OPERATIONS ON ARRAYS BY REGION\n--\n-- RESET FIPNUM BASED ON MULTNUM AND OPERNUM\n--\n-- DESTIN REGN OPERATION SOURCE ALPHA BETA INPUT SEGNUM EQUIL\n-- ARRAY NUM TYPE ARRAY CONST CONST ARRAY NUMBER NUMBER\nOPERATER\nFIPNUM 26 'MULTA' 'MULTNUM' 0.00 1 / 26 1\nFIPNUM 44 'MULTA' 'MULTNUM' 0.00 2 / 44 2\nFIPNUM 62 'MULTA' 'MULTNUM' 0.00 3 / 62 3\nFIPNUM 98 'MULTA' 'MULTNUM' 0.00 4 / 98 4\nFIPNUM 116 'MULTA' 'MULTNUM' 0.00 5 / 116 5\nFIPNUM 134 'MULTA' 'MULTNUM' 0.00 6 / 134 6\nFIPNUM 46 'MULTA' 'MULTNUM' 0.00 7 / 46 7\nFIPNUM 64 'MULTA' 'MULTNUM' 0.00 8 / 64 8\nFIPNUM 82 'MULTA' 'MULTNUM' 0.00 9 / 82 9\nFIPNUM 226 'MULTA' 'MULTNUM' 0.00 10 / 226 10\nFIPNUM 262 'MULTA' 'MULTNUM' 0.00 11 / 262 11\nFIPNUM 280 'MULTA' 'MULTNUM' 0.00 12 / 280 12\nFIPNUM 298 'MULTA' 'MULTNUM' 0.00 13 / 298 13\nFIPNUM 33 'MULTA' 'MULTNUM' 0.00 14 / 33 14\nFIPNUM 51 'MULTA' 'MULTNUM' 0.00 15 / 51 15\nFIPNUM 105 'MULTA' 'MULTNUM' 0.00 16 / 105 16\nFIPNUM 159 'MULTA' 'MULTNUM' 0.00 17 / 159 17\nFIPNUM 195 'MULTA' 'MULTNUM' 0.00 18 / 195 18\nFIPNUM 267 'MULTA' 'MULTNUM' 0.00 19 / 267 19\nFIPNUM 303 'MULTA' 'MULTNUM' 0.00 20 / 303 20\nFIPNUM 321 'MULTA' 'MULTNUM' 0.00 21 / 321 21\nFIPNUM 339 'MULTA' 'MULTNUM' 0.00 22 / 339 22\nFIPNUM 54 'MULTA' 'MULTNUM' 0.00 23 / 54 23\nFIPNUM 72 'MULTA' 'MULTNUM' 0.00 24 / 72 24\nFIPNUM 108 'MULTA' 'MULTNUM' 0.00 25 / 108 25\nFIPNUM 144 'MULTA' 'MULTNUM' 0.00 26 / 144 26\nFIPNUM 270 'MULTA' 'MULTNUM' 0.00 27 / 270 27\n/\nNote that operation can only be done in the REGION section as FIPNUM is only available for use in this section and that the ARRAY variable has been defaulted, resulting in OPERNUM being the regional array for the REGION variable.\n| OPERATER Keyword and Variable Options by Section | | | | | | |\n|--------------------------------------------------|---------|-------|---------|----------|---------|----------|\n| GRID | EDIT | PROPS | REGIONS | SOLUTION | SUMMARY | SCHEDULE |\n| DX | DEPTH | SWL | ENDNUM | PRESSURE | | |\n| DY | PORV | SWCR | EQLNUM | SWAT | | |\n| DZ | TRANX | SWU | FIPNUM | SGAS | | |\n| PERMX | TRANY | SGL |","expected_columns":7,"size_kind":"list"},"OPERNUM":{"name":"OPERNUM","sections":["GRID","REGIONS"],"supported":null,"summary":"This keyword defines the OPERATER region numbers for each grid block. The OPERNUM keyword defines the region numbers for each grid block, as such there must be one entry for each cell in the model. The array can also be used with the EQUALREG, ADDREG, COPYREG, MULTIREG, MULTREGP and MULTREGT keywords, as well as the OPERATER keyword in calculating various grid properties in the GRID and REGION section.","parameters":[{"index":1,"name":"OPERNUM","description":"OPERNUM defines an array of positive integers greater than or equal to one that assigns a grid cell to a particular OPERNUM region. The maximum number of OPERNUM regions is set by the NOPREG variable on the REGDIMS keyword in the RUNSPEC section. Note that the default value of zero implies that the calculations requested by the OPERATER keyword will not be performed.","units":{},"default":"0"}],"example":"The example below sets three OPERNUM regions for a 4 x 5 x 2 model.\n--\n-- DEFINE OPERNUM REGIONS FOR ALL CELLS\n--\nOPERNUM\n2 2 1 1 2 2 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n3 3 1 1 3 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n/\nAlternatively the EQUALS keyword could be employed to accomplish the same task, that is:\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nOPERNUM 1 1* 1* 1* 1* 1* 1* / SET REGION 1\nOPERNUM 2 1 2 1 2 1 1 / SET REGION 2\nOPERNUM 3 1 2 1 2 2 2 / SET REGION 3\n/\nOne can then increase PERMX by 25% in region three only.\n--\n-- MULTIPLY AN ARRAY BY A CONSTANT BASED ON A REGION NUMBER\n--\n-- ARRAY CONSTANT REGION REGION ARRAY\n-- VALUE NUMBER M / F / O\nMULTIREG\nPERMX 1.25 3 O /\n/","size_kind":"array"},"OUTRAD":{"name":"OUTRAD","sections":["GRID"],"supported":false,"summary":"OUTRAD defines the OUTER radius of the reservoir model for a radial or spider grid geometry. The RADIAL or SPIDER keyword in the RUNSPEC should be activated to indicate that radial or spider geometry is being used.","parameters":[{"index":1,"name":"OUTRAD","description":"A single real positive number greater than INRAD defining the outer radius of a radial grid.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":"Length"}],"example":"--\n-- INNER RADIUS OF FIRST GRID BLOCK IN THE RADIAL DIRECTION\n--\nINRAD\n0.25 /\n--\n-- OUTER RADIUS OF FIRST GRID BLOCK IN THE RADIAL DIRECTION\n--\nOUTRAD\n2050.0 /\nThe above example defines the inner radius to be 0.25 and the outer radius to be 2,050 feet. Note that the outer radius includes the inner radius.\n| [{R sub{i}} over {R sub{i-1}} ``=``left( OUTRAD over {R sub{i sub{j}-1}}right)` sup{1 over {left(NX`-`i sub{j}``+``1 right)}}] | (6.12) |\n|--------------------------------------------------------------------------------------------------------------------------------|--------|\n| [R sub{i}``=``left(R sub{i sub{j}-1} right) left( OUTRAD over {R sub{i sub{j}-1}} right)` sup{left(i`-`i sub{j}`+1` right) over {left(NX`-`i sub{j}``+``1 right)}}] | (6.13) |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|\n| [DR sub{ i}~=~R sub{i}``-``R sub{i`-`1}] | (6.14) |\n|------------------------------------------|--------|\n| OUTRAD Radial Grid Example | | | |\n|----------------------------|----------|----------|-------|\n| INRAD | 0.25 | | |\n| OUTRAD | 2050.0 | | |\n| NX | 10 | | |\n| NX | Ri | DR | Ratio |\n| 0 | 0.250 | 0.250 | |\n| 1 | 0.616 | 0.366 | 1.463 |\n| 2 | 1.516 | 0.900 | 2.463 |\n| 3 | 3.733 | 2.217 | 2.463 |\n| 4 | 9.193 | 5.460 | 2.463 |\n| 5 | 22.638 | 13.445 | 2.463 |\n| 6 | 55.748 | 33.109 | 2.463 |\n| 7 | 137.281 | 81.533 | 2.463 |\n| 8 | 338.058 | 200.777 | 2.463 |\n| 9 | 832.477 | 494.420 | 2.463 |\n| 10 | 2050.000 | 1217.523 | 2.463 |\n| Total | | 2050.000 | |","expected_columns":1,"size_kind":"fixed","size_count":1},"PARAOPTS":{"name":"PARAOPTS","sections":["GRID"],"supported":false,"summary":"The PARAOPTS keyword defines various options for parallel runs, for when the Parallel option has been invoked by the PARALLEL keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"METHOD","description":"","units":{},"default":"TREE","value_type":"STRING"},{"index":2,"name":"SET_PRINT","description":"","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"SIZE","description":"","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"NUM_BUFFERS","description":"","units":{},"default":"2","value_type":"INT"},{"index":5,"name":"VALUE_MEM","description":"","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"VALUE_COARSE","description":"","units":{},"default":"0","value_type":"INT"},{"index":7,"name":"VALUE_NNC","description":"","units":{},"default":"0","value_type":"INT"},{"index":8,"name":"VALUE_PRT_FILE","description":"","units":{},"default":"1","value_type":"INT"},{"index":9,"name":"RESERVED","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":9,"size_kind":"fixed","size_count":1},"PEBI":{"name":"PEBI","sections":["GRID"],"supported":false,"summary":"PEBI activates the unstructured Perpendicular Bisector (“PEBI”)121\n Heinemann, Z.E. and Brand, C.W. 1988. Gridding Techniques in Reservoir Simulation. Proc., First Intl. Forum on Reservoir Simulation, Alpbach, Austria, 339. and 122\n Heinemann, Z.E., Brand, C.W., Munka, M. et al. 1991. Modeling Reservoir Geometry With Irregular Grids. SPE Res Eng 6 (2): 225–232. SPE-18412-PA. http://dx.doi.org/10.2118/18412-PAloading of grid data generated by an external pre-processing program for generating simulation grids.","parameters":[{"index":1,"name":"OPTION1","description":"A defined character string that activates or deactivates the checking of negative transmissibility values. OPTION1 should be set to YES to check for negative values, or NO switches off this option.","units":{},"default":"NO","value_type":"STRING"},{"index":2,"name":"OPTION2","description":"A defined character string that activates or deactivates the calculation of pore volumes and transmissibilities. OPTION2 should be set to YES if the pore volumes and transmissibilities are provided, or NO for the values to calculated by the simulator.","units":{},"default":"NO","value_type":"STRING"}],"example":"–-\n-- OPTION1 OPTION2\n-- CHECK CALCULATE\nPEBI\nNO YES /\nThe above example switches off the negative transmissibility check and requests that the simulator calculates pore volumes and transmissibilities as they are not provided by the input data.","expected_columns":2,"size_kind":"fixed","size_count":1},"PERMAVE":{"name":"PERMAVE","sections":["GRID"],"supported":false,"summary":"The PERMAVE keyword defines the three directional exponent coefficients used to average the grid block permeabilities between two neighboring cells when calculating the transmissibility between the two blocks. The keyword can be used to change from the default weighted harmonic averaging (coefficient set equal to -1), to geometric (coefficient equal to zero), or to arithmetic averaging (coefficient equal to 1). The three coefficients represent the averaging in the x-, y- and z-directions.","parameters":[{"index":1,"name":"EXPO_0","description":"","units":{},"default":"-1","value_type":"INT"},{"index":2,"name":"EXPO_1","description":"","units":{},"default":"-1","value_type":"INT"},{"index":3,"name":"EXPO_2","description":"","units":{},"default":"-1","value_type":"INT"}],"example":"","expected_columns":3,"size_kind":"fixed","size_count":1},"PERMJFUN":{"name":"PERMJFUN","sections":["GRID"],"supported":false,"summary":"PERMJFUN defines the permeability to be used in de-normalizing the Leverett J-Functions123\n Leverett, M. C.; “Capillary Behaviour in Porous Solids”, Trans. AIME (1941) 142, 152-168. for when the PERM variable on the JFUNC or the JFUNCR keyword in the GRID section has been set to “U”, as oppose to using PERMX, PERMY, PERMZ arrays etc.","parameters":[{"index":1,"name":"PERMJFUN","description":"PERMJFUN is an array of real positive numbers assigning the permeability to be used in de-normalizing the Leverett J-Function to each cell in the model. Repeat counts may be used, for example 20*100.0.","units":{"field":"mD","metric":"mD","laboratory":"mD"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK PERMJFUN FOR ALL CELLS (BASED ON NX x NY x NZ = 300)\n--\nPERMJFUN\n100*500.0 100*50.0 100*200.0 /\nThe above example defines the PERMJFUN to be 500.0, 50.0, and 200.0 for the first, second and third layers in the model for all 300 cells, as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"PERMR":{"name":"PERMR","sections":["GRID"],"supported":null,"summary":"PERMR sets the permeability for each cell in the R direction in a radial geometry grid. The RADIAL or SPIDER keywords in the RUNSPEC should be activated to indicate that radial or spider geometry is being used.","parameters":[{"index":1,"name":"PERMR","description":"PERMR is an array of real positive numbers assigning the permeability in the R direction to each cell in the model. This equivalent to PERMX in a Cartesian grid. Repeat counts may be used, for example 20*100.0.","units":{"field":"mD","metric":"mD","laboratory":"mD"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK PERMR DATA FOR ALL CELLS (BASED ON NR x NY x NZ = 300)\n--\nPERMR\n100*500.0 100*50.0 100*200.0 /\nThe above example defines the PERMR to be 500.0, 50.0, and 200.0 for the first, second and third layers in the model for all 300 cells, as defined by the DIMENS keyword (10, 10, 3) in the RUNSPEC section.","size_kind":"array"},"PERMTHT":{"name":"PERMTHT","sections":["GRID"],"supported":null,"summary":"PERMTHT sets the permeability for each cell in the THETA direction in a radial geometry grid. The RADIAL or SPIDER keyword in the RUNSPEC should be activated to indicate that radial or spider geometry is being used.","parameters":[{"index":1,"name":"PERMTHT","description":"PERMTHT is an array of real positive numbers assigning the permeability in the THETA direction to each cell in the model. This equivalent to PERMY in a Cartesian grid. Repeat counts may be used, for example 20*100.0.","units":{"field":"mD","metric":"mD","laboratory":"mD"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK PERMTHT DATA FOR ALL CELLS (NX x NY x NZ = 300)\n--\nPERMTHT\n100*500.0 100*50.0 100*200.0 /\nThe above example defines the PERMTHT to be 500.0, 50.0, and 200.0 for the first, second and third layers in the model for all 300 cells, as defined by the DIMENS keyword (10, 10, 3) in the RUNSPEC section.","size_kind":"array"},"PERMX":{"name":"PERMX","sections":["GRID"],"supported":null,"summary":"PERMX defines the permeability in the X direction for all the cells in the model via an array. The keyword can be used for all grid types, except for the Radial Grid geometry.","parameters":[{"index":1,"name":"PERMX","description":"PERMX is an array of real positive numbers assigning the permeability in the X direction to each cell in the model. Repeat counts may be used, for example 20*100.0.","units":{"field":"mD","metric":"mD","laboratory":"mD"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK PERMX DATA FOR ALL CELLS (BASED ON NX x NY x NZ = 300)\n--\nPERMX\n100*500.0 100*50.0 100*200.0 /\nThe above example defines the PERMX to be 500.0, 50.0, and 200.0 for the first, second and third layers in the model for all 300 cells, as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"PERMY":{"name":"PERMY","sections":["GRID"],"supported":null,"summary":"PERMY defines the permeability in the Y direction for all the cells in the model via an array. The keyword can be used for all grid types, except for the Radial Grid geometry.","parameters":[{"index":1,"name":"PERMY","description":"PERMY is an array of real positive numbers assigning the permeability in the Y direction to each cell in the model. Repeat counts may be used, for example 20*100.0.","units":{"field":"mD","metric":"mD","laboratory":"mD"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK PERMY DATA FOR ALL CELLS (BASED ON NX x NY x NZ = 300)\n--\nPERMY\n100*500.0 100*50.0 100*200.0 /\nThe above example defines the PERMY to be 500.0, 50.0, and 200.0 for the first, second and third layers in the model for all 300 cells, as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"PERMZ":{"name":"PERMZ","sections":["GRID"],"supported":null,"summary":"PERMZ defines the permeability in the Z direction for all the cells in the model via an array. The keyword can be used for all grid types, except for the Radial Grid geometry.","parameters":[{"index":1,"name":"PERMZ","description":"PERMZ is an array of real positive numbers assigning the permeability in the Z direction to each cell in the model. Repeat counts may be used, for example 200*50.0.","units":{"field":"mD","metric":"mD","laboratory":"mD"},"default":"None"}],"example":"The example below defines the PERMZ to be 50.0, 5.0, and 20.0 for the first, second and third layers in the model for all 300 cells, as defined by the DIMENS keyword in the RUNSPEC section.\n--\n-- DEFINE GRID BLOCK PERMZ DATA FOR ALL CELLS (BASED ON NX x NY x NZ = 300)\n--\nPERMZ\n100*50.0 100*5.0 100*20.0 /\nThe next example sets PERMX to be 500.0, 50.0, and 200.0 for the first, second and third layers in the model for all 300 cells, as defined by the DIMENS keyword in the RUNSPEC section. It then copies the PERMX values to the PERMY and PERMZ arrays, and finally multiplies PERMZ by 0.1 times to get the final values for PERMZ.\n--\n-- DEFINE GRID BLOCK PERMX DATA FOR ALL CELLS\n--\nPERMX\n100*500.0 100*50.0 100*200.0 /\n--\n-- SOURCE DESTIN. ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nCOPY\nPERMX PERMY 1* 1* 1* 1* 1* 1* / CREATE PERMY\nPERMX PERMZ 1* 1* 1* 1* 1* 1* / CREATE PERMZ\n/\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nMULTIPLY\nPERMZ 0.10000 1* 1* 1* 1* 1* 1* / PERMZ * 0.1\n/\nThe above sequence of keywords is quite common in input decks, that is copying the PERMX data to the PERMY and PERMZ arrays and then adjusting the PERMY and PERMZ arrays as required using the MULTIPLY keyword.\n| Note Although PERMX and PERMY are commonly set to be equal, PERMZ is typically not equal to either PERMX or PERMY. Normally PERMZ is set as a fraction of PERMX with typical values ranging from 0.1 to 0.5 times PERMX. |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"array"},"PETGRID":{"name":"PETGRID","sections":["GRID"],"supported":false,"summary":"The PETGRID keyword instructs the simulator to load a Generic Simulation Grid (*.GSG) file that contains grid geometry data.","parameters":[{"index":1,"name":"FILE_NAME","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"PINCH":{"name":"PINCH","sections":["GRID"],"supported":null,"summary":"The PINCH keyword defines the parameters used to control the generation of Non-Neighbor Connections (“NNCs”) in the vertical (K) direction due to layers pinching out. This keyword is applied to all layers in the model as opposed to the PINCHREG keyword that offers more flexibility by applying the pinch-out controls to various regions in the model defined by the PINCHNUM keyword.","parameters":[{"index":1,"name":"PINCHTHK","description":"A real number defining the pinch-out threshold thickness for any cell. NNCs are generated across inactive cells having a vertical thickness less than PINCHTHK.","units":{"field":"ft. 0.001","metric":"m 0.001","laboratory":"cm 0.001"},"default":"Defined","value_type":"DOUBLE","dimension":"Length"},{"index":2,"name":"PINCHOPT","description":"A character string controlling the generation of pinch-outs when the MINPV keyword has been used to deactivate cells with small pore volumes. PINCHOPT can either be set to: GAP to allow the generation of NNCs across cells that have been made inactive with the MINPV keyword when the thickness is greater than PINCHTHK threshold. NOGAP to enforce the strict adherence to the PINCHTHK threshold whether or not cells have been made inactive due to the MINPV keyword.","units":{},"default":"GAP","value_type":"STRING"},{"index":3,"name":"PINCHGAP","description":"A real number defining the maximum “empty” thickness allowed between grid blocks in adjacent grid layers for a non-zero transmissibility to exist between them.","units":{"field":"ft. 1.0E20","metric":"m 1.0E20","laboratory":"cm 1.0E20"},"default":"Defined","value_type":"DOUBLE","dimension":"Length"},{"index":4,"name":"PINCHCAL","description":"A character string controlling the calculation of the pinch-out transmissibilities. PINCHCAL can either be set to: TOPBOT results in the pinch-out transmissibility being calculated from the half-cell Z-direction transmissibilities of the active cells on either side of the pinched-out layers. ALL results in the pinch-out transmissibility being calculated from the Z-direction transmissibilities harmonic average of all the cells between the active cells on either side of the pinched-out layers.","units":{},"default":"TOPBOT","value_type":"STRING"},{"index":5,"name":"PINCHMUL","description":"A character string controlling the calculation of the pinch-out transmissibilities when adjustments have been made by the MULTZ keyword. PINCHMUL can either be set to: TOP results in the pinch-out transmissibility being calculated from the active cell at the top of the pinch-out. ALL results in the pinch-out transmissibility being calculated from the minimum value of the MULTZ of the active cell at the top of the pinch-out and all the inactive cells in the pinch-out vertical column. Note if PINCHCAL has been set equal to ALL then PINCHMUL is reset to TOP, irrespective of the entered value for PINCHMUL.","units":{},"default":"TOP","value_type":"STRING"}],"example":"The first example below will create NNCs between the cells above and below any cell having vertical thickness less than 0.01 in either feet or metres.\n--\n-- SET PINCH-OUT PARAMETERS FOR CALCULATING PINCH-OUT PROPERTIES\n--\nPINCH\n-- THRESHOLD GAP EMPTY TRANS MULTZ\n-- THICKNESS NO GAP GAP CALC CALC\n0.01 1* 1* 1* 1* /\nFor the second example, the MINPV keyword is used to set the minimum pore volume to 500 m3 (metric units) and then the PINCH keyword is invoked with PINCHGAP set equal to GAP, as follows:\n--\n-- MINIMUM PORE VOLUME FOR ACTIVE CELLS\n--\nMINPV\n500.0 /\n--\n-- SET PINCH-OUT CRITERIA FOR THE MODEL\n--\nPINCH\n-- THRESHOLD GAP EMPTY TRANS MULTZ\n-- THICKNESS NO GAP GAP CALC CALC\n0.1 GAP 1* 1* 1* /\nIn the above example the MINPV keyword will deactivate all cells with pore volumes less than 500 m3. These deactivated cells are inactive in the model and therefore are not included in the flow calculations; however, by default they will result in no-flow barriers but may not be thin enough for PINCH to create NNCs across them. By setting PINCHGAP equal to GAP on the PINCH keyword (the default setting), then OPM Flow generates NNCs across the cells that have been deactivated by the MINPV keyword. However, in this case there may be grid blocks in the model with a pore volume greater than MINPV but a thickness less than the pinch-out threshold. These cells will not be deactivated by the PINCH keyword.","expected_columns":5,"size_kind":"fixed","size_count":1},"PINCHNUM":{"name":"PINCHNUM","sections":["GRID"],"supported":false,"summary":"The PINCHNUM keyword defines the pinch-out region numbers for each grid block, as such there must be one entry for each cell in the model. The array is used with the PINCHREG keyword to set the pinch-out options and threshold thickness for each region.","parameters":[{"index":1,"name":"PINCHNUM","description":"PINCHNUM defines an array of positive integers assigning a grid cell to a particular PINCHNUM region. The maximum number of PINCHNUM regions is set by the NRPINC variable on the GRIDOPTS keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"The example below sets defines three PINCHNUM regions for various layers in a model based on the model’s layering.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nMULTNUM 1 1* 1* 1* 1* 1* 1* / SET REGION 1\nMULTNUM 2 1 2 1 2 10 50 / SET REGION 2\nMULTNUM 3 1 2 1 2 51 100 / SET REGION 3\n/\nOne can then set the pinch-out criteria for each region.\n--\n-- SET PINCH-OUT CRITERA VIA THE PINCHNUM REGION\n--\nPINCHREG\n-- THRESHOLD GAP EMPTY TRANS\n-- THICKNESS NO GAP GAP CALC\n0.1 1* 1* 1* / PINCHNUM 01\n1.0 1* 10 1* / PINCHNUM 02\n1.0 NOGAP 20 1* / PINCHNUM 03\nThe above example sets the default pinch-out criteria for grid blocks defined as region one via the PINCHNUM array and different criteria for regions two and three.","size_kind":"array"},"PINCHOUT":{"name":"PINCHOUT","sections":["GRID"],"supported":false,"summary":"The PINCHOUT keyword activates the generation of Non-Neighbor Connections (“NNCs”) in the vertical (K) direction due to layers pinching out, using a constant threshold thickness of 0.001 for all unit systems. See also the PINCH keyword in the GRID section that allows for specifying the threshold thickness and other parameters on a layer basis, and the PINCHREG keyword that applies the pinch-out controls to various regions in the model defined by the PINCHNUM keyword.","parameters":[],"example":"The example will create NNCs between the cells above and below any cell having vertical thickness less than 0.001 in either feet or metres.\n--\n-- SET PINCH-OUT CRITERA WITH CONSTANT THRESHOLD THICKNESS OF 0.001\n--\nPINCHOUT","size_kind":"none","size_count":0},"PINCHREG":{"name":"PINCHREG","sections":["GRID"],"supported":null,"summary":"The PINCHREG keyword defines the parameters used to control the generation of Non-Neighbor Connections (“NNCs”) in the vertical (K) direction due to layers pinching out in combination with the PINCHNUM keyword. This allows different regions in the model to use different criteria in controlling the how pinch-outs are generated. The keyword should contain NRPINC records defining the criteria for each pinch-out region defined with the PINCHNUM keyword. NRPINC is the maximum number of PINCHNUM regions defined via the GRIDOPTS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"PINCHTHK","description":"A real number defining the pinch-out threshold thickness for any cell. NNCs are generated across inactive cells having a vertical thickness less than PINCHTHK.","units":{"field":"ft. 0.001","metric":"m 0.001","laboratory":"cm 0.001"},"default":"Defined","value_type":"DOUBLE","dimension":"Length"},{"index":2,"name":"PINCHOPT","description":"A character string controlling the generation of pinch-outs when the MINPV keyword has been used to deactivate cells with small pore volumes. PINCHOPT can either be set to: GAP to allow the generation of NNCs across cells that have been made inactive with the MINPV keyword when the thickness is greater than PINCHTHK threshold. NOGAP to enforce the strict adherence to the PINCHTHK threshold whether or not cells have been made inactive due to the MINPV keyword.","units":{},"default":"GAP","value_type":"STRING"},{"index":3,"name":"PINCHGAP","description":"A real number defining the maximum “empty” thickness allowed between grid blocks in adjacent grid layers for a non-zero transmissibility to exist between them.","units":{"field":"ft. 1.0E20","metric":"m 1.0E20","laboratory":"cm 1.0E20"},"default":"Defined","value_type":"DOUBLE","dimension":"Length"},{"index":4,"name":"PINCHCAL","description":"A character string controlling the calculation of the pinch-out transmissibilities. PINCHCAL can either be set to: TOPBOT results in the pinch-out transmissibility being calculated from the half-cell Z-direction transmissibilities of the active cells on either side of the pinched-out layers. ALL results in the pinch-out transmissibility being calculated from the Z-direction transmissibilities harmonic average of all the cells between the active cells on either side of the pinched-out layers.","units":{},"default":"TOPBOT","value_type":"STRING"},{"index":5,"name":"PINCHMUL","description":"A character string controlling the calculation of the pinch-out transmissibilities when adjustments have been made by the MULTZ keyword. PINCHMUL can either be set to: TOP results in the pinch-out transmissibility being calculated from the active cell at the top of the pinch-out. ALL results in the pinch-out transmissibility being calculated from the minimum value of the MULTZ of the active cell at the top of the pinch-out and all the inactive cells in the pinch-out vertical column. Note if PINCHCAL has been set equal to ALL then PINCHMUL is reset to TOP, irrespective of the entered value for PINCHMUL.","units":{},"default":"TOP","value_type":"STRING"}],"example":"--\n-- SET PINCH-OUT CRITERA VIA THE PINCHNUM REGION\n--\nPINCHREG\n-- THRESHOLD GAP EMPTY TRANS\n-- THICKNESS NO GAP GAP CALC\n0.1 1* 1* 1* / PINCHNUM 01\n1.0 1* 10 1* / PINCHNUM 02\n1.0 NOGAP 20 1* / PINCHNUM 03\nThe above example sets the default pinch-out criteria for grid blocks defined as region one via the PINCHNUM array and different values for regions two and three.","expected_columns":5,"size_kind":"list"},"PINCHXY":{"name":"PINCHXY","sections":["GRID"],"supported":false,"summary":"The PINCHXY keyword defines the x-direction and y-direction threshold thickness used to control the generation of Non-Neighbor Connections (“NNCs”) in the x- and y- directions for missing cells in the areal plane.","parameters":[{"index":1,"name":"PINCHTHX","description":"A real number defining the pinch-out threshold width for any cell in the x-direction. NNCs are generated across inactive cells having a width less than PINCHTHX in the x-direction.","units":{"field":"ft. 0.001","metric":"m 0.001","laboratory":"cm 0.001"},"default":"Defined","value_type":"DOUBLE","dimension":"Length"},{"index":2,"name":"PINCHTHY","description":"A real number defining the pinch-out threshold width for any cell in the y-direction. NNCs are generated across inactive cells having a width less than PINCHTHY in the y-direction.","units":{"field":"ft. 0.001","metric":"m 0.001","laboratory":"cm 0.001"},"default":"Defined","value_type":"DOUBLE","dimension":"Length"}],"example":"The example below will create NNCs between the cells in the areal plane having cell widths less than 0.01 in either feet or metres in both the x- and y-directions.\n--\n-- SET PINCH-OUT PARAMETERS FOR AREAL PLANE\n--\nPINCHXY\n-- X-DIRC Y-DIRC\n-- THRESHOLD THRESHOLD\n--\n0.01 0.01 /","expected_columns":2,"size_kind":"fixed","size_count":1},"PORO":{"name":"PORO","sections":["GRID"],"supported":null,"summary":"PORO defines the porosity for all the cells in the model via an array. The keyword can be used with all grid types.","parameters":[{"index":1,"name":"PORO","description":"PORO is an array of real positive numbers that are greater than or equal to zero and less than or equal to one that are the porosity values for each cell in the model. Repeat counts may be used, for example 3000*0.15","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK POROSITY DATA FOR ALL CELLS (BASED ON NX x NY x NZ = 300)\n--\nPORO\n300*0.300 /\nThe above example defines a constant porosity of 0.300 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"PYEND":{"name":"PYEND","sections":["GRID","EDIT","PROPS","REGIONS","SOLUTION","SUMMARY","SCHEDULE"],"supported":null,"summary":"The PYINPUT and PYEND keywords are a part of OPM Flow’s Python scripting facility that processes standard Python commands that can be used to manipulate and define the simulators input parameters during processing of the input deck. The main purpose of the facility is to script the construction of the various keywords.","parameters":[],"example":"The example shows how to construct the DX variable in the GRID section and to add the resulting DX array as part of the input deck.\n--\n-- START OF PYINPUT SECTION\n--\nPYINPUT\n#\n# Import Numpy Model\n#\nimport numpy as np\n#\n# Define DX and Get the Input Decks Unit Systems\n#\ndx = np.array([100.0, 100.0, 100.0, 100.0])\nactive_unit_system = context.deck.active_unit_system()\ndefault_unit_system = context.deck.default_unit_system()\n#\n# Set DX in the Input Deck\n#\nkw = context.DeckKeyword( context.parser['DX'], dx, active_unit_system,\ndefault_unit_system )\ncontext.deck.add(kw)\nPYEND\nThe active Parser objects are accessible as context.parser and the active Deck object is available as context.deck.\n| Note This is an OPM Flow specific keyword for the simulator’s scripting facility using the standard Python interpreter, as such it gives more flexibility than the commercial simulator’s data editing keywords (ADD, EQUAL, MULTIPLY, etc.), although OPM Flow also supports these keywords as well. The PYINPUT facility should be considered experimental as details of the OPM Flow - Python interface might change for future releases. In particular, the current implementation is quite minimal; however, future releases are expected to add more entry points in the simulator’s deck class which can be used to manipulate the input deck as the data is loaded. As a user you are encouraged to come with wishes in this regard. The PYINPUT facility is very powerful and allows for any piece of Python code to be included and run, including potentially malicious code. The important point is to scrutinize the Python code in between PYINPUT and PYEND in a deck you receive from other parties. |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|"},"PYINPUT":{"name":"PYINPUT","sections":["RUNSPEC","GRID","EDIT","PROPS","REGIONS","SOLUTION","SUMMARY","SCHEDULE"],"supported":null,"summary":"The PYINPUT and PYEND keywords are a part of OPM Flow’s Python scripting facility that processes standard Python commands that can be used to manipulate and define the simulators input parameters during processing of the input deck. The main purpose of the facility is to script the construction of the various keywords used by the simulator.","parameters":[{"index":"1-1","name":"PYTHON","description":"A series of standard Python commands with one line per command. The active Parser objects are accessible as context.parser and the active Deck object is available as context.deck.","units":{},"default":""}],"example":"The example shows how to construct the DX variable in the GRID section and to add the resulting DX array as part of the input deck.\n--\n-- START OF PYINPUT SECTION\n--\nPYINPUT\n#\n# Import Numpy Model\n#\nimport numpy as np\n#\n# Define DX and Get the Input Decks Unit Systems\n#\ndx = np.array([100.0, 100.0, 100.0, 100.0])\nactive_unit_system = context.deck.active_unit_system()\ndefault_unit_system = context.deck.default_unit_system()\n#\n# Set DX in the Input Deck\n#\nkw = context.DeckKeyword( context.parser['DX'], dx, active_unit_system,\ndefault_unit_system )\ncontext.deck.add(kw)\nPYEND\nThe active Parser objects is accessible as context.parser and the active Deck object is available as context.deck.\n| Note This is an OPM Flow specific keyword for the simulator’s scripting facility using the standard Python interpreter, as such it gives more flexibility than the commercial simulator’s data editing keywords (ADD, EQUALS, MULTIPLY, etc.), although OPM Flow also supports these keywords as well. The PYINPUT facility should be considered experimental as details of the OPM Flow - Python interface might change for future releases. In particular, the current implementation is quite minimal; however, future releases are expected to add more entry points in the simulator’s deck class which can be used to manipulate the input deck as the data is loaded. As a user you are encouraged to come with wishes in this regard. The PYINPUT facility is very powerful and allows for any piece of Python code to be included and run, including potentially malicious code. The important point is to scrutinize the Python code in between PYINPUT and PYEND in a deck you receive from other parties. |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"none","size_count":0},"QMOBIL":{"name":"QMOBIL","sections":["GRID"],"supported":false,"summary":"The QMOBIL keyword activates or deactivates the end-point mobility correction for Local Grid Refinements (“LGR”), for when LGRs have been activated for the input deck using the LGR keyword in the RUNSPEC section. QMOBIL should be placed in between the LGR definition keywords CARFIN, or RADIN (or RAFDIN4) and the ENDFIN keyword in the GRID section.","parameters":[{"index":1,"name":"MOBILE_END_POINT_CORRECTION","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"RADFIN":{"name":"RADFIN","sections":["GRID"],"supported":false,"summary":"This keyword defines a radial local grid refinement using one columns Local grid refinement is currently not supported by OPM Flow.","parameters":[{"index":1,"name":"NAME","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"I","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"J","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"K1","description":"","units":{},"default":"","value_type":"INT"},{"index":5,"name":"K2","description":"","units":{},"default":"","value_type":"INT"},{"index":6,"name":"NR","description":"","units":{},"default":"","value_type":"INT"},{"index":7,"name":"NTHETA","description":"","units":{},"default":"","value_type":"INT"},{"index":8,"name":"NZ","description":"","units":{},"default":"","value_type":"INT"},{"index":9,"name":"NWMAX","description":"","units":{},"default":"1","value_type":"INT"},{"index":10,"name":"INNER_RADIUS","description":"Default value is 0.5 ft (= 6 in)","units":{},"default":"0.1524","value_type":"DOUBLE","dimension":"Length"},{"index":11,"name":"OUTER_RADIUS","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":12,"name":"MINIMUM_RADIUS_REFINEMENT","description":"Default value is 5 ft","units":{},"default":"1.524","value_type":"DOUBLE","dimension":"Length"},{"index":13,"name":"PARENT_LGR","description":"","units":{},"default":"GLOBAL","value_type":"STRING"}],"example":"","expected_columns":13,"size_kind":"fixed","size_count":1},"RADFIN4":{"name":"RADFIN4","sections":["SPECIAL","GRID"],"supported":false,"summary":"This keyword defines a radial local grid refinement using four columns. Local grid refinement is currently not supported by OPM Flow.","parameters":[{"index":1,"name":"NAME","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"I1","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"I2","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"J1","description":"","units":{},"default":"","value_type":"INT"},{"index":5,"name":"J2","description":"","units":{},"default":"","value_type":"INT"},{"index":6,"name":"K1","description":"","units":{},"default":"","value_type":"INT"},{"index":7,"name":"K2","description":"","units":{},"default":"","value_type":"INT"},{"index":8,"name":"NR","description":"","units":{},"default":"","value_type":"INT"},{"index":9,"name":"NTHETA","description":"","units":{},"default":"","value_type":"INT"},{"index":10,"name":"NZ","description":"","units":{},"default":"","value_type":"INT"},{"index":11,"name":"NWMAX","description":"","units":{},"default":"1","value_type":"INT"}],"example":"","expected_columns":11,"size_kind":"fixed","size_count":1},"REFINE":{"name":"REFINE","sections":["GRID","EDIT","PROPS","REGIONS","SOLUTION","SCHEDULE"],"supported":false,"summary":"The REFINE keyword defines the start of a Cartesian or radial Local Grid Refinement (“LGR”) definition that sets the properties of the selected LGR. The keyword is then followed by the property keywords associated with the section where the keyword is being invoked. For example, if the REFINE keyword is used in the GRID section then most of the keywords in that section can be used to set the grid properties for the LGR.","parameters":[{"index":1,"name":"LGR","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"RESVNUM":{"name":"RESVNUM","sections":["GRID"],"supported":true,"summary":"The RESVNUM keyword is used to define the start of a reservoir coordinate data set and stipulates the reservoir number for the data set. The keyword is used in conjunction with the COORD keyword in the GRID section, that specifies a set of coordinate lines or pillars for a reservoir grid via an array. Note that the COORD keyword should immediately follow the RESVNUM keyword.","parameters":[{"index":1,"name":"RESVNUM","description":"A positive integer values that defines the reservoir coordinate data set, or the independent reservoir, for which the subsequent COORD data is to be associated with. RESVNUM should be less than or equal to NUMRES on the NUMRES keyword in the RUNSPEC section. OPM Flow currently only accepts a single data set, that is the default value of one.","units":{},"default":"1","value_type":"INT"}],"example":"--\n-- NUMRES\n-- NUMBER\nRESVNUM\n1 /\n--\n-- SPECIFY VERTICAL COORDINATE LINES FOR A REGULAR 3 x 2 GRID\n--(DX = 100 and DY = 200)\n--\n-- X1 Y1 Z1 X2 Y2 Z2\n-- --- --- ---- --- --- ----\nCOORD\n0 0 1000 0 0 5000\n100 0 1000 100 0 5000\n200 0 1000 200 0 5000\n300 0 1000 300 0 5000\n0 200 1000 0 200 5000\n100 200 1000 100 200 5000\n200 200 1000 200 200 5000\n300 200 1000 300 200 5000\n0 400 1000 0 400 5000\n100 400 1000 100 400 5000\n200 400 1000 200 400 5000\n300 400 1000 300 400 5000\n/\n--\n-- NUMRES\n-- NUMBER\nRESVNUM\n2 /\n--\n-- SPECIFY VERTICAL COORDINATE LINES FOR A REGULAR 3 x 2 GRID\n--(DX = 100 and DY = 200)\n--\n-- X1 Y1 Z1 X2 Y2 Z2\n-- --- --- ---- --- --- ----\nCOORD\n0 0 1000 0 0 5000\n100 0 1000 100 0 5000\n200 0 1000 200 0 5000\n300 0 1000 300 0 5000\n0 200 1000 0 200 5000\n100 200 1000 100 200 5000\n200 200 1000 200 200 5000\n300 200 1000 300 200 5000\n0 400 1000 0 400 5000\n100 400 1000 100 400 5000\n200 400 1000 200 400 5000\n300 400 1000 300 400 5000\n/","expected_columns":1,"size_kind":"fixed","size_count":1},"ROCKFRAC":{"name":"ROCKFRAC","sections":["GRID"],"supported":false,"summary":"ROCKFRAC defines the rock volume to bulk volume fraction for all the cells, The keyword can be used with all grid types. Rock volume of a grid block is calculated by multiply a cell’s bulk volume by it’s ROCKFRAC volume. A cell’s rock volume is used in the Coal option to calculate the adsorbed gas in the rock (coal), as well as the Thermal and Temp options to calculate the energy is stored in the rock.","parameters":[{"index":1,"name":"ROCKFRAC","description":"ROCKFRAC is an array of real numbers greater than or equal to zero and less than or equal to one, that are assigned the rock volume to bulk volume fraction values for each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 200*0.850.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- DEFINE GRID ROCKFRAC DATA FOR ALL CELLS (BASED ON NX x NY x NZ = 300)\n--\nROCKFRAC\n100*1.000 100*0.850 100*0.500 /\nThe above example defines a constant ROCKFRAC of 1.00 for the first 100 cells, then 0.85 for the second 100 hundred cells, and finally 0.500 for the last 100 cell, for the 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"RPTGRID":{"name":"RPTGRID","sections":["GRID"],"supported":false,"summary":"This keyword defines the data in the GRID section that is to be printed to the output print file in human readable format. The keyword has two distinct forms, the first of which consists of the keyword followed by a series of integers on the next line indicating the data to be printed (see the first example). This is the original formal in the commercial simulator and was subsequently superseded by the second format. The second format consists of the keyword followed by a series of character strings that indicate the data to be printed. In most cases the character string is the keyword used to load the data in the OPM Flow input deck, for example PORO for the porosity array. Its is anticipated that OPM Flow will eventually support the functionality of the second format only, the first format although recognized will be completely ignored.","parameters":[{"index":1,"name":"ALLNCC","description":"Print all the non-neighbor connections.","units":{},"default":"N/A","value_type":"STRING"},{"index":2,"name":"COORD","description":"Print the coordinate lines.","units":{},"default":"N/A"},{"index":3,"name":"COORDYS","description":"Print the coordinate systems.","units":{},"default":"N/A"},{"index":4,"name":"DEPTH","description":"Print grid cells center depths.","units":{},"default":"N/A"}],"example":"The first example shows the original format of this keyword; although the keyword and format are recognized by OPM Flow, the format is ignored and is unlikely to be implemented in in the simulator.\n--\n-- DEFINE GRID SECTION REPORT OPTION (ORIGINAL FORMAT)\n–\nRPTGRID\n1 2*0 1 3*1 /\nThe next example shows the second format of the keyword which may be supported in a future release of OPM Flow.\n-- DEFINE GRID SECTION REPORT OPTIONS\n--\nRPTGRID\nDX DY DZ DEPTH PORO PERMX /\n| Note This keyword has the potential to produce very large print files that some text editors may have difficulty loading, coupled with the fact that reviewing the data in this format is very cumbersome. A more efficient solution is to load the *.INIT file into OPM ResInsight to view the data graphically, this also has the benefit of being able to filter the grid based on I, J, K ranges and grid properties. |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"fixed","size_count":1,"variadic_record":true},"RPTGRIDL":{"name":"RPTGRIDL","sections":["GRID"],"supported":false,"summary":"This keyword defines the data in the GRID section that is to be printed to the output print file in human readable format for Local Grid Refinements (“LGRs”), for when LGRs have been activated for the input deck using the LGR keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"ALLNCC","description":"Print all the non-neighbor connections.","units":{},"default":"N/A","value_type":"STRING"},{"index":2,"name":"COORD","description":"Print the coordinate lines.","units":{},"default":"N/A"},{"index":3,"name":"COORDYS","description":"Print the coordinate systems.","units":{},"default":"N/A"},{"index":4,"name":"DEPTH","description":"Print grid cells center depths.","units":{},"default":"N/A"},{"index":24,"name":"ALLNNC","description":"ALLNNC is a defined positive integer that specifies the type of Non-Neighbor Connections (“NNC”) to be printed, and should be set to one of the follow: To print the NNCs within the LGRs, and the connections between the local and host cells to the print file (*.PRT). To print the NNCs within the LGRs, and the connections between the local and host cells to the print (*.PRT) and debug files (*.DBG). Same as (2) but the data in the debug file (*.DBG) is written out in an alternative format.","units":{},"default":"N/A"},{"index":57,"name":"EXTHOST","description":"EXTHOSTS outputs host cells for Perpendicular Bisector (“PEBI”)124\n Heinemann, Z.E. and Brand, C.W. 1988. Gridding Techniques in Reservoir Simulation. Proc., First Intl. Forum on Reservoir Simulation, Alpbach, Austria, 339. and 125\n Heinemann, Z.E., Brand, C.W., Munka, M. et al. 1991. Modeling Reservoir Geometry With Irregular Grids. SPE Res Eng 6 (2): 225–232. SPE-18412-PA. http://dx.doi.org/10.2118/18412-PALGRs. Heinemann, Z.E. and Brand, C.W. 1988. Gridding Techniques in Reservoir Simulation. Proc., First Intl. Forum on Reservoir Simulation, Alpbach, Austria, 339. Heinemann, Z.E., Brand, C.W., Munka, M. et al. 1991. Modeling Reservoir Geometry With Irregular Grids. SPE Res Eng 6 (2): 225–232. SPE-18412-PA. http://dx.doi.org/10.2118/18412-PA","units":{},"default":""}],"example":"The first example shows the original format of this keyword; although the keyword and format are recognized by OPM Flow, the format is ignored and is unlikely to be implemented in in the simulator.\n--\n-- DEFINE LGR GRID SECTION REPORT OPTION (ORIGINAL FORMAT)\n–\nRPTGRIDL\n1 2*0 1 3*1 /\nThe next example shows the second format of the keyword which may be supported in a future release of OPM Flow.\n-- DEFINE LGR GRID SECTION REPORT OPTIONS\n--\nRPTGRIDL\nDX DY DZ DEPTH PORO PERMX /\n| Note This keyword has the potential to produce very large print files that some text editors may have difficulty loading, coupled with the fact that reviewing the data in this format is very cumbersome. A more efficient solution is to load the *.INIT file into OPM ResInsight to view the data graphically, this also has the benefit of being able to filter the grid based on I, J, K ranges and grid properties. |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"fixed","size_count":1,"variadic_record":true},"RPTINIT":{"name":"RPTINIT","sections":["GRID"],"supported":false,"summary":"This keyword defines the data in the GRID and EDIT sections that is to be written out to the INIT file (*.INIT or *.FINIT). The format consists of the keyword followed by a series of character strings that indicate the data to be written. In most cases the character string is the keyword used to load the data into the OPM Flow input deck, for example PORO for the porosity array in the GRID section. In addition, values either read or calculated by the simulator in the EDIT section can also be written to the INIT file. Again the keyword or property name is used as the mnemonic for the character string, for example the PORV, TRANX keywords etc. If the RPTINIT keyword is not used in the input deck then a default set of data array are written to the file, in this case the actual data written is dependent on the model’s configuration and the options being used.","parameters":[{"index":1,"name":"MNEMONICS_LIST","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","size_kind":"fixed","size_count":1,"variadic_record":true},"RPTISOL":{"name":"RPTISOL","sections":["GRID"],"supported":false,"summary":"The RPTISOL keyword activates the isolated reservoir report that generates an array of isolated region numbers that is printed in the debug file (*.DBG). The main purpose of this facility is to use the generated array as input to the ISOLNUM keyword in the GRID section in conjunction with the Independent Reservoir Regions option. If the model can be divided into isolated reservoirs then the individual reservoirs may be solved independently, resulting in increased computational efficient, compared with solving the model as a whole.","parameters":[],"example":"--\n-- ACTIVATE ISOLATED RESERVOIR NUMBER REPORTING\n--\nRPTISOL\nThe above example activates the isolated reservoir report that generates an array of isolated region numbers to the debug file (*.DBG).","size_kind":"none","size_count":0},"SIGMA":{"name":"SIGMA","sections":["GRID"],"supported":false,"summary":"The SIGMA keyword defines the dual porosity matrix to fracture transmissibility multiplier, sigma, that is applied to all cells, for when the Dual Porosity model has been activated by either the DUALPORO or the DUALPERM keywords in the RUNSPEC section. Sigma (σ) takes into account the matrix-fracture interface area per unit volume and was defined by Kazemi et al126\n Kazemi, H., Merrill JR., L. S., Porterfield, K. L., and Zeman, P. R. “Numerical Simulation of Water-Oil Flow in Naturally Fractured Reservoirs,” paper SPE 5719, Society of Petroleum Engineers Journal (1976) 16, No. 6, 317-326. to be:","parameters":[{"index":1,"name":"COUPLING","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1/Length*Length"}],"example":"| [%sigma `=` 4left(1 over {l sub x} sup 2` + 1 over {l sub y} sup 2`+ 1 over {l sub z} sup 2` right)] | (6.15) |\n|------------------------------------------------------------------------------------------------------|--------|","expected_columns":1,"size_kind":"fixed","size_count":1},"SIGMAGD":{"name":"SIGMAGD","sections":["GRID"],"supported":false,"summary":"The SIGMAGD keyword defines the dual porosity matrix to fracture transmissibility multiplier, sigma, that is applied to all cells, for when the Dual Porosity model has been activated by either the DUALPORO or the DUALPERM keywords in the RUNSPEC section. In addition, the GRAVDR keyword in the RUNSPEC section should be used to enable the Gravity Drainage model for the run. Sigma (σ) takes into account the matrix-fracture interface area per unit volume and was defined by Kazemi et al127\n Kazemi, H., Merrill JR., L. S., Porterfield, K. L., and Zeman, P. R. “Numerical Simulation of Water-Oil Flow in Naturally Fractured Reservoirs,” paper SPE 5719, Society of Petroleum Engineers Journal (1976) 16, No. 6, 317-326. to be:","parameters":[{"index":1,"name":"COUPLING","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1/Length*Length"}],"example":"| [%sigma `=` 4left(1 over {l sub x} sup 2` + 1 over {l sub y} sup 2`+ 1 over {l sub z} sup 2` right)] | (6.16) |\n|------------------------------------------------------------------------------------------------------|--------|","expected_columns":1,"size_kind":"list"},"SIGMAGDV":{"name":"SIGMAGDV","sections":["GRID"],"supported":false,"summary":"The SIGMAGD keyword defines the dual porosity matrix to fracture transmissibility multiplier, sigma, that is applied to individual cells, for when the Dual Porosity model has been activated by either the DUALPORO or the DUALPERM keywords in the RUNSPEC section. In addition, the GRAVDR keyword in the RUNSPEC section should be used to enable the Gravity Drainage model for the run. Sigma (σ) takes into account the matrix-fracture interface area per unit volume and was defined by Kazemi et al128\n Kazemi, H., Merrill JR., L. S., Porterfield, K. L., and Zeman, P. R. “Numerical Simulation of Water-Oil Flow in Naturally Fractured Reservoirs,” paper SPE 5719, Society of Petroleum Engineers Journal (1976) 16, No. 6, 317-326. to be:","parameters":[],"example":"| [%sigma `=` 4left(1 over {l sub x} sup 2` + 1 over {l sub y} sup 2`+ 1 over {l sub z} sup 2` right)] | (6.17) |\n|------------------------------------------------------------------------------------------------------|--------|","size_kind":"array"},"SIGMAV":{"name":"SIGMAV","sections":["GRID"],"supported":false,"summary":"The SIGMAV keyword defines a dual porosity matrix to fracture multiplier, sigma, that is applied to individual cells, for when the Dual Porosity model has been invoked by either the DUALPORO or the DUALPERM keywords in the RUNSPEC section. Sigma (σ) takes into account the matrix-fracture interface area per unit volume and was defined by Kazemi et al129\n Kazemi, H., Merrill JR., L. S., Porterfield, K. L., and Zeman, P. R. “Numerical Simulation of Water-Oil Flow in Naturally Fractured Reservoirs,” paper SPE 5719, Society of Petroleum Engineers Journal (1976) 16, No. 6, 317-326. to be:","parameters":[],"example":"| [%sigma `=` 4left(1 over {l sub x} sup 2` + 1 over {l sub y} sup 2`+ 1 over {l sub z} sup 2` right)] | (6.18) |\n|------------------------------------------------------------------------------------------------------|--------|","size_kind":"array"},"SMULTX":{"name":"SMULTX","sections":["GRID"],"supported":false,"summary":"SMULTX multiples the transmissibility between two cell faces in the +X direction between cells in a host base grid and the connecting auto-refined grid cells, via an array, that is the keyword sets the transmissibility multiplier of block (Ihost, Jhost, Khost) in the host base grid, multiplies the transmissibility all the cells (Iauto, Jauto, Kauto) and (I+Iauto, Jauto, Kauto) in the auto-refinement grid. The Auto Refinement option must be enabled to use this keyword via the AUTOREF keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"SMULTX+","description":"SMULTX+ is an array of real positive numbers assigning the transmissibility multipliers in the +X direction to each cell face in the model. Repeat counts may be used, for example 20*100.0.","units":{},"default":"1.0"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n10 10 1 6 1 3 / DEFINE BOX AREA\n--\n-- SET SMULTX+ TRANSMISSIBILITY MULTIPLIERS\n--\nSMULTX\n18*0.300 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe above example defines a 0.3 scaling multiplier for the 18 cells defined by the preceding BOX statement. The ENDBOX keyword resets the input box to the full grid.","size_kind":"array"},"SMULTY":{"name":"SMULTY","sections":["GRID"],"supported":false,"summary":"SMULTY multiples the transmissibility between two cell faces in the +Y direction between cells in a host base grid and the connecting auto-refined grid cells, via an array, that is the keyword sets the transmissibility multiplier of block (Ihost, Jhost, Khost) in the host base grid, multiplies the transmissibility all the cells (Iauto, Jauto, Kauto) and (Iauto, J+1auto, Kauto) in the auto-refinement grid. The Auto Refinement option must be enabled to use this keyword via the AUTOREF keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"SMULTY+","description":"SMULTY+ is an array of real positive numbers assigning the transmissibility multipliers in the +X direction to each cell face in the model. Repeat counts may be used, for example 20*100.0.","units":{},"default":"1.0"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n10 10 1 6 1 3 / DEFINE BOX AREA\n--\n-- SET SMULTY+ TRANSMISSIBILITY MULTIPLIERS\n--\nSMULTY\n18*0.300 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe above example defines a 0.3 scaling multiplier for the 18 cells defined by the preceding BOX statement. The ENDBOX keyword resets the input box to the full grid.","size_kind":"array"},"SMULTZ":{"name":"SMULTZ","sections":["GRID"],"supported":false,"summary":"SMULTZ multiples the transmissibility between two cell faces in the +Z direction between cells in a host base grid and the connecting auto-refined grid cells, via an array, that is the keyword sets the transmissibility multiplier of block (Ihost, Jhost, Khost) in the host base grid, multiplies the transmissibility all the cells (Iauto, Jauto, Kauto) and (Iauto, Jauto, K+1auto) in the auto-refinement grid. The Auto Refinement option must be enabled to use this keyword via the AUTOREF keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"SMULTZ+","description":"SMULTZ+ is an array of real positive numbers assigning the transmissibility multipliers in the +X direction to each cell face in the model. Repeat counts may be used, for example 20*100.0.","units":{},"default":"1.0"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n10 10 1 6 1 3 / DEFINE BOX AREA\n--\n-- SET SMULTZ+ TRANSMISSIBILITY MULTIPLIERS\n--\nSMULTZ\n18*0.300 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe above example defines a 0.3 scaling multiplier for the 18 cells defined by the preceding BOX statement. The ENDBOX keyword resets the input box to the full grid.","size_kind":"array"},"SOLVDIRS":{"name":"SOLVDIRS","sections":["GRID"],"supported":false,"summary":"The SOLVDIRS keyword defines the linear solver principal directions, which should be set to XY, XZ, YX, YZ, ZX, or ZY. The default direction is based on the direction of the highest transmissibility and SOLVDIRS allows for over writing the default direction for when linear convergence of the equations are problematic.","parameters":[{"index":1,"name":"DIRECTION","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"SOLVNUM":{"name":"SOLVNUM","sections":["GRID"],"supported":false,"summary":"The SOLVNUM defines the unstructured Perpendicular Bisector (“PEBI”)130\n Heinemann, Z.E. and Brand, C.W. 1988. Gridding Techniques in Reservoir Simulation. Proc., First Intl. Forum on Reservoir Simulation, Alpbach, Austria, 339. and 131\n Heinemann, Z.E., Brand, C.W., Munka, M. et al. 1991. Modeling Reservoir Geometry With Irregular Grids. SPE Res Eng 6 (2): 225–232. SPE-18412-PA. http://dx.doi.org/10.2118/18412-PAgrid correspondence to the nested factorization solver order, for when the grid has been entered as a PEBI list. This keyword is generated by an external pre-processing program for generating simulation grids.","parameters":[],"example":"","size_kind":"array"},"SPECGRID":{"name":"SPECGRID","sections":["GRID"],"supported":true,"summary":"SPECGRID defines the dimensions of corner-point and radial grids in the x, y, and z directions as well as the number of reservoirs, where each reservoir has its own set of corner-point geometry data.","parameters":[{"index":1,"name":"NDIVIX","description":"A positive integer value that defines the number of cells in the X or R direction","units":{},"default":"1","value_type":"INT"},{"index":2,"name":"NDIVIY","description":"A positive integer value that defines the number of cells in the Y or THETA direction","units":{},"default":"1","value_type":"INT"},{"index":3,"name":"NDIVZ","description":"A positive integer value that defines the number of cells in the Z direction","units":{},"default":"1","value_type":"INT"},{"index":4,"name":"NUMRES","description":"A positive integer values that defines number of coordinate data sets, or independent reservoirs in the model. OPM Flow currently only accepts a single data set, that is the default value of one.","units":{},"default":"1","value_type":"INT"},{"index":5,"name":"TYPE","description":"A character string set to either T of F that defines the type of grid to be defined by subsequent keywords: T = Radial grid with radial coordinates F = Cartesian grid Only the default option F is supported by OPM Flow.","units":{},"default":"F","value_type":"STRING"}],"example":"--\n-- MAX MAX MAX MAX GRID\n-- NDIVIX NDIVIY NDIVIZ NUMRES TYPE\nSPECGRID\n46 112 22 1 F /\nThe above example defines a 46 x 112 x 22 grid with one set of irregular corner-point data.","expected_columns":5,"size_kind":"fixed","size_count":1},"THCGAS":{"name":"THCGAS","sections":["GRID"],"supported":false,"summary":"The THCGAS keyword defines the gas phase thermal conductivity for when the thermal calculation is activated by the THERMAL keyword in the RUNSPEC section, and should be used in conjunction with THCROCK keyword in the GRID section.","parameters":[{"index":1,"name":"THCGAS","description":"THCGAS is an array of real positive numbers that define the thermal conductivity of the gas phase in each grid block. Repeat counts may be used, for example 3000*20.0","units":{"field":"Btu/ft/day/°R","metric":"kJ/m/day/K","laboratory":"J/cm/hr/K"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK GAS PHASE THERMAL CONDUCTIVITY\n– FOR ALL CELLS (BASED ON NX x NY x NZ = 300)\n--\nTHCGAS\n300*20.0 /\nThe above example defines the gas phase thermal conductivity of 20.0 for each cell in the 300 grid block model as defined by the DIMENS keyword in the RUNSPEC section.\n| [\"Average Thermal Conductivity\"= {PORO times left( THCOIL + THCGAS+THCWATER+THCSOLID right )} over {\" NUMBER OF PHASES IN THE MODEL\"} times\nLEFT(1 - PORO RIGHT ) times THCROCK] | (6.19) |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|","size_kind":"array"},"THCOIL":{"name":"THCOIL","sections":["GRID"],"supported":false,"summary":"The THCOIL keyword defines the oil phase thermal conductivity for when the thermal calculation is activated by the THERMAL keyword in the RUNSPEC section, and should be used in conjunction with THCROCK keyword in the GRID section.","parameters":[{"index":1,"name":"THCOIL","description":"THCOIL is an array of real positive numbers that define the thermal conductivity of the oil phase in each grid block. Repeat counts may be used, for example 3000*20.0","units":{"field":"Btu/ft/day/°R","metric":"kJ/m/day/K","laboratory":"J/cm/hr/K"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK OIL PHASE THERMAL CONDUCTIVITY\n– FOR ALL CELLS (BASED ON NX x NY x NZ = 300)\n--\nTHCOIL\n300*20.0 /\nThe above example defines the oil phase thermal conductivity of 20.0 for each cell in the 300 grid block model, as defined by the DIMENS keyword in the RUNSPEC section.\n| [\"Average Thermal Conductivity\"= PORO times left( THCOIL + THCGAS+THCWATER+THCSOLID right ) over \" NUMBER OF PHASES IN THE MODEL\" times\nLEFT(1 -\" PORO\" RIGHT ) times \"THCROCK\"] | (6.20) |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|","size_kind":"array"},"THCONR":{"name":"THCONR","sections":["GRID"],"supported":null,"summary":"The THCONR keyword defines the reservoir rock plus fluid thermal conductivity for all cells for when the thermal calculation is activated by the THERMAL keywords in the RUNSPEC section.","parameters":[{"index":1,"name":"THCONR","description":"THCONR is an array of real positive numbers that define the combined rock and fluid conductivity of a grid block. Repeat counts may be used, for example 3000*25.0","units":{"field":"Btu/ft/day/°R","metric":"kJ/m/day/K","laboratory":"J/cm/hr/K"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK ROCK-FLUID THERMAL CONDUCTIVITY\n– FOR ALL CELLS (BASED ON NX x NY x NZ = 300)\n--\nTHCONR\n300*25.0 /\nThe above example defines the combined rock and fluid thermal conductivity of 25.0 for each cell in the 300 grid block model, as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"THCONSF":{"name":"THCONSF","sections":["GRID"],"supported":false,"summary":"The THCONSF keyword defines a gas saturation dependent scaling factor to the fluid and reservoir rock thermal conductivities entered via the THCONR keyword in the GRID section, for when the thermal calculation is activated by the THERMAL keyword in the RUNSPEC.","parameters":[{"index":1,"name":"THCONSF","description":"THCONSF is an array of real positive numbers, greater than zero and less than or equal to one, that define the gas saturation dependent scaling factor that is applied to the THCONR data, entered via the THCONR keyword, to adjust the thermal conductivity of the reservoir cells in each grid block. Repeat counts may be used, for example 3000*0.15","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- DEFINE GRID SGAS DEPENDENT SCALING FACTOR FOR THE THCONR ARRAY -- FOR ALL CELLS (BASED ON NX x NY x NZ = 300)\n-- (OPM FLOW THERMAL OPTION ONLY)\n--\nTHCONSF\n300*0.12 /\nThe above example defines the gas saturation thermal conductivity scaling factor to be applied to the THCONR to be 0.12 for all 300 cells in the model, as defined by the DIMENS keyword in the RUNSPEC section.\n| [%OMEGA sub{ i,j,k}`` =`` left(1 - \"THCONSF x Gas Saturation\" right ) sub{ i,j,k}] | (6.21) |\n|------------------------------------------------------------------------------------|--------|","size_kind":"array"},"THCROCK":{"name":"THCROCK","sections":["GRID"],"supported":false,"summary":"The THCROCK keyword defines the reservoir rock thermal conductivity for when the thermal calculation is activated by the THERMAL keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"THCROCK","description":"THCROCK is an array of real positive numbers that define the thermal conductivity of the reservoir rock in each grid block. Repeat counts may be used, for example 3000*20.0","units":{"field":"Btu/ft/day/°R","metric":"kJ/m/day/K","laboratory":"J/cm/hr/K"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK RESERVOIR ROCK THERMAL CONDUCTIVITY\n– FOR ALL CELLS (BASED ON NX x NY x NZ = 300)\n--\nTHCROCK\n300*20.0 /\nThe above example defines the reservoir rock thermal conductivity of 20.0 for each cell in the 300 grid block model, as defined by the DIMENS keyword in the RUNSPEC section.\n| [\"Average Thermal Conductivity\"= PORO times left( THCOIL + THCGAS+THCWATER+THCSOLID right ) over \" NUMBER OF PHASES IN THE MODEL\" times\nLEFT(1 - PORO RIGHT ) times THCROCK] | (6.22) |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|","size_kind":"array"},"THCWATER":{"name":"THCWATER","sections":["GRID"],"supported":false,"summary":"The THCWATER keyword defines the water phase thermal conductivity for when the thermal calculation is activated by the THERMAL keyword in the RUNSPEC section, and should be used in conjunction with THCROCK keyword in the GRID section.","parameters":[{"index":1,"name":"THCWATER","description":"THCWATER is an array of real positive numbers that define the thermal conductivity of the water phase in each grid block. Repeat counts may be used, for example 3000*20.0","units":{"field":"Btu/ft/day/°R","metric":"kJ/m/day/K","laboratory":"J/cm/hr/K"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK WATER PHASE THERMAL CONDUCTIVITY\n– FOR ALL CELLS (BASED ON NX x NY x NZ = 300)\n--\nTHCWATER\n300*2O.0 /\nThe above example defines the water phase thermal conductivity of 20.0 for each cell in the 300 grid block model, as defined by the DIMENS keyword in the RUNSPEC section.\n| [\"Average Thermal Conductivity\"= PORO times left( THCOIL + THCGAS+THCWATER+THCSOLID right ) over \" NUMBER OF PHASES IN THE MODEL\" times\nLEFT(1 - PORO RIGHT ) times THCROCK] | (6.23) |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|","size_kind":"array"},"THPRESFT":{"name":"THPRESFT","sections":["GRID"],"supported":null,"summary":"The THPRESFT keyword defines a fault threshold pressures that prevents fluid flow from occurring across the fault plane until the threshold pressure is exceeded, for when the threshold pressure option has been activated via the THRPRES variable on the EQLOPTS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"FLTNAME","description":"FLTNAME is a character string enclosed in quotes with a maximum length of eight characters, that defines the name of the fault. FLTNAME must have been previously defined using the FAULTS keyword in the GROD section, otherwise an error will occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"PRESS","description":"PRESS is a single positive real value that defines the threshold pressure for the fault (FLTNAME). If PRESS is defaulted then the simulator will set the threshold pressure to zero, that is the fault is open to flow along the fault plane.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"0","value_type":"DOUBLE","dimension":"Pressure"}],"example":"The example below defines two fault traces, ‘M_WEST’ and ‘BC’ fault having threshold pressures of 1000.0 and 2000 psis respectively.\n--\n-- DEFINE FAULTS IN THE GRID GEOMETRY\n--\n-- FAULT ------------ FAULT TRACE -------------\n-- NAME I1 I2 J1 J2 K1 K2 FACE\nFAULTS\n'M_WEST' 5 5 3 3 1 22 'X' /\n'M_WEST' 5 5 4 4 1 22 'X' /\n'M_WEST' 5 5 5 5 1 22 'X' /\n……………………………………………..\n'BC' 43 43 8 8 1 22 'Y' /\n'BC' 42 42 9 9 1 22 'X' /\n'BC' 44 44 8 8 1 22 'Y' /\n……………………………………………..\n/\n--\n-- DEFINE FAULT THRESHOLD PRESSURES\n--\n-- FAULT THRESHOLD\n-- NAME PRESSURE\nTHPRESFT\n'M_WEST' 1000.0 /\n'BC' 1200.0 /\n/","expected_columns":2,"size_kind":"list"},"TOPS":{"name":"TOPS","sections":["GRID"],"supported":null,"summary":"TOPS defines the depth of the top face of each cell in the model.","parameters":[{"index":1,"name":"TOPS","description":"TOPS is an array of real numbers defining the depth at the top face of each cell in the model. One can either just enter the TOPS for the first layer only based on NX x NY entries and OPM Flow will calculate the remaining TOPS based on either DZ or DZV. Alternatively NX x NY x NZ TOPS may be entered for each cell in the model. See the DIMENS keyword in the RUNSPEC section for the definition of NX, NY and NZ. Repeat counts may be used, for example 10*5201.0.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None"}],"example":"The example below defines the TOPS of the cells for each cell for NX = 5, NY = 5 and NZ = 3 model, as well as the X and Y direction cells sizes.\n--\n-- DEFINE GRID BLOCK TOPS FOR THE TOP LAYER (NX=5, NY=5, and NZ=3)\n--\nTOPS\n25*3100 25*3105 25*3110 / --\n-- DEFINE GRID BLOCK X DIRECTION CELL SIZE (BASED ON NX = 5)\n--\nDXV\n5*100 / --\n-- DEFINE GRID BLOCK X DIRECTION CELL SIZE (BASED ON NY = 5)\n--\nDYV\n5*100 /\nA second example is shown on the following page.\nThis example defines the same grid as before but with the TOPS keyword only defining the top layer and DZV keyword defining the cells thickness.\n--\n-- DEFINE GRID BLOCK TOPS FOR THE TOP LAYER (NX = 5, NY = 5, NZ = 3)\n--\nTOPS\n25*3100 /\n--\n-- DEFINE GRID BLOCK Z DIRECTION CELL SIZE (BASED ON NZ = 3)\n--\nDZV\n3*5.0 /\n--\n-- DEFINE GRID BLOCK X DIRECTION CELL SIZE (BASED ON NX = 5)\n--\nDXV\n5*100 / --\n-- DEFINE GRID BLOCK Y DIRECTION CELL SIZE (BASED ON NY = 5)\n--\nDYV\n5*100 /","size_kind":"array"},"TRANGL":{"name":"TRANGL","sections":["GRID"],"supported":false,"summary":"TRANGL enables Non-Neighbor Connections (“NNC”) between the global cells and the Local Grid Refinement (“LGR”) cells to be manually specified, as oppose to the simulator calculating the transmissibilities. The LGR keyword in the RUNSPEC section should be utilized to define the presence of LGRs in the model and to define various LGR dimension parameters.","parameters":[{"index":1,"name":"I1","description":"A positive integer that defines the LGR grid block in the I-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NX on the CARFIN keyword in the GRID section.","units":{},"default":"None","value_type":"INT"},{"index":2,"name":"J1","description":"A positive integer that defines the LGR grid block in the J-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NY on the CARFIN keyword in the GRID section.","units":{},"default":"None","value_type":"INT"},{"index":3,"name":"K1","description":"A positive integer that defines the LGR grid block in the K-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NZ on the CARFIN keyword in the GRID section.","units":{},"default":"None","value_type":"INT"},{"index":4,"name":"I2","description":"A positive integer that defines the GLOBAL grid block in the I-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NX on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":5,"name":"J2","description":"A positive integer that defines the GLOBAL grid block in the J-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NY on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":6,"name":"K2","description":"A positive integer that defines the GLOBAL grid block in the K-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NZ on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":7,"name":"TRANSNNC","description":"TRANSNNC is a positive real number greater than or equal to zero that defines the transmissibility between the GLOBAL grid block (I1, J1, K1) and the LGR grid block (I2, J2, K2). The default value of zero sets the transmissibility between the two cells to zero.","units":{"field":"cP.rb/day/psia","metric":"cP.rm3/day/bars","laboratory":"cP.rcc/hr/atm"},"default":"0.0","value_type":"DOUBLE","dimension":"Transmissibility"}],"example":"--\n-- MANUALLY DEFINE LGR-GLOBAL GRID NON-NEIGHBOR CONNECTIONS\n--\n-- ----LGR----- ---GLOBAL---- -- TRANSNCC --\n-- I1 J1 K1 I2 J2 K2\nTRANGL\n1 1 1 1 1 2 0.2500 /\n1 1 2 1 1 3 0.2500 /\n1 1 3 1 1 4 0.2500 /\n/\nThe above example defines the transmissibility between LGR cell (1, 1, 1) and global cell (1, 1, 2), LGR cell (1, 1, 2) and global cell (1, 1, 3) and finally between LGR cell (1, 1, 3) and global cell (1, 1, 4) to be 0.2500.","expected_columns":7,"size_kind":"list"},"USEFLUX":{"name":"USEFLUX","sections":["GRID"],"supported":false,"summary":"The USEFLUX keyword activates the Flux Boundary model and defines the name of the FLUX file. Only grid blocks that have been declared by the FLUXREG keyword in the GRID section to be in an active flux region, are active for the run.","parameters":[],"example":"","size_kind":"none","size_count":0},"USENOFLO":{"name":"USENOFLO","sections":["GRID"],"supported":false,"summary":"The USENOFLUX keyword activates the Flux Boundary model without a FLUX file. The USEFLUX keyword should still be in the input deck, but in this case the FLUX filename is ignored. The option is useful when the no-flow boundary condition is a reasonable assumption and avoids the pre-cursor run used to generate the FLUX file via the DUMPFLUX keyword in the GRID section. Only grid blocks that have been declared by the FLUXREG keyword in the GRID section to be in an active flux region, are active for the run.","parameters":[],"example":"--\n-- ACTIVATE FLUX BOUNDARY MODEL WITHOUT A FLUX FILE\n--\nUSEFLUX\n/\nUSENOFLO\nThe above example activates the Flux Boundary model without a FLUX file.","size_kind":"none","size_count":0},"VEDEBUG":{"name":"VEDEBUG","sections":["GRID"],"supported":false,"summary":"This keyword defines the debug Vertical Equilibrium (“VE”) data to be written to the debug file (*.DBG), for when the VE model has been activated by the VE keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"I1","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"I2","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"J1","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"J2","description":"","units":{},"default":"","value_type":"INT"},{"index":5,"name":"K1","description":"","units":{},"default":"","value_type":"INT"},{"index":6,"name":"K2","description":"","units":{},"default":"","value_type":"INT"},{"index":7,"name":"DEBUG_LEVEL","description":"","units":{},"default":"0","value_type":"INT"},{"index":8,"name":"LGR","description":"","units":{},"default":" ","value_type":"STRING"}],"example":"","expected_columns":8,"size_kind":"fixed","size_count":1},"VEFIN":{"name":"VEFIN","sections":["GRID"],"supported":false,"summary":"If the VE keyword in the RUNSPEC section has been used to activate the Vertical Equilibrium (“VE”) model for the global grid, then the VEFIN keyword may used to set various options for the Local Grid Refinements (“LGR”). The LGR keyword in the RUNSPEC section should be activated to indicate the presence of LGRs and the keyword VEFIN should be placed in between the CARFIN and ENDFIN keywords in the GRID section.","parameters":[{"index":1,"name":"VE","description":"","units":{},"default":"NO","value_type":"STRING"},{"index":2,"name":"NVEPT","description":"","units":{},"default":"0","value_type":"INT"}],"example":"","expected_columns":2,"size_kind":"fixed","size_count":1},"ZCORN":{"name":"ZCORN","sections":["GRID"],"supported":null,"summary":"ZCORN defines the depth of each corner point of a grid block on the pillars defining the reservoir grid. A total of 8 x NX x NY x NZ values are needed to fully define all the depths in the model. The depths specifying the top of the first layer are entered first with one point for each pillar for each grid block. The points are entered with the X axis cycling fastest. Next come the depths of the bottom of the first layer. The top of layer two follows etc.","parameters":[{"index":1,"name":"ZCORN","description":"An array of depths with 8 depths for each cell, for a total of 8 x Nx x NY x NZ entries","units":{"field":"feet","metric":"metres","laboratory":"cm"},"default":"None"}],"example":"--\n-- SPECIFY CORNER-POINT DEPTHS FOR A 3 x 2 x 2 GRID,\n-- WITH CONSTANT SLOPE IN THE X AND Y DIRECTIONS\n-- SUCH THAT ALL CORNER POINTS OF NEIGHBOURING BLOCKS ALIGN\nZCORN\n--\n-- top of layer 1\n--\n1450 1500 1500 1550 1550 1600\n1500 1550 1550 1600 1600 1650\n1500 1550 1550 1600 1600 1650\n1550 1600 1600 1650 1650 1700\n--\n-- bottom of layer 1\n--\n1460 1510 1510 1560 1560 1610\n1510 1560 1560 1610 1610 1660\n1510 1560 1560 1610 1610 1660\n1560 1610 1610 1660 1660 1710\n--\n-- top of layer 2\n--\n1460 1510 1510 1560 1560 1610\n1510 1560 1560 1610 1610 1660\n1510 1560 1560 1610 1610 1660\n1560 1610 1610 1660 1660 1710\n--\n-- bottom of layer 2\n--\n1470 1520 1520 1570 1570 1620\n1520 1570 1570 1620 1620 1670\n1520 1570 1570 1620 1620 1670\n1570 1620 1620 1670 1670 1720\n/\nThe above example defines depths of the vertical coordinate lines for a regular 3 by 2 by 2 grid with a constant slope in the x and y directions such that all the corner points of neighboring blocks are aligned.","size_kind":"array"},"DEPTH":{"name":"DEPTH","sections":["EDIT"],"supported":null,"summary":"The DEPTH keywords modifies the depth at the center of selected cells in the model. The cells DEPTH are calculated by OPM Flow at the end of the GRID section and this keyword allows the user to adjust the calculated depths in the EDIT section. The area to be modified can be defined via the various grid selection keywords, ADD, BOX, EQUALS, etc., and areas that are not selected remain unchanged.","parameters":[{"index":1,"name":"DEPTH","description":"DEPTH is an array of real numbers defining the depth at the center of each cell in the model. Only the values in the currently defined input BOX needed be entered. Repeat counts may be used, for example 30*5201.0.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None"}],"example":"The example below modifies the DEPTH of the cells for a selection of 10 cells from an NX = 10, NY = 11 and NZ = 20 model.\n--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1 10 11 11 20 20 / SET BOX AREA TO BE MODIFIED\n/\n--\n-- SET GRID BLOCK CENTER DEPTH FOR THE GRID BLOCKS\n--\nDEPTH 10*3500.0 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nAlternatively the EQUALS keyword can be used to perform the same edit.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nDEPTH 3500.0 1 10 11 11 20 20 / RESET DEPTH\n/","size_kind":"array"},"DIFFR":{"name":"DIFFR","sections":["EDIT"],"supported":false,"summary":"The DIFFR keyword defines the radial direction diffusivity values for cells in the current input box for when the Diffusivity option has been activated by the DIFFUSE keyword in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"DIFFTHT":{"name":"DIFFTHT","sections":["EDIT"],"supported":false,"summary":"The DIFFTHT keyword defines the theta direction diffusivity values for cells in the current input box for when the Diffusivity option has been activated by the DIFFUSE keyword in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"DIFFX":{"name":"DIFFX","sections":["EDIT"],"supported":false,"summary":"The DIFFX keyword defines the x-direction diffusivity values for cells in the current input box for when the Diffusivity option has been activated by the DIFFUSE keyword in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"DIFFY":{"name":"DIFFY","sections":["EDIT"],"supported":false,"summary":"The DIFFY keyword defines they y-direction diffusivity values for cells in the current input box for when the Diffusivity option has been activated by the DIFFUSE keyword in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"DIFFZ":{"name":"DIFFZ","sections":["EDIT"],"supported":false,"summary":"The DIFFZ keyword defines the z-direction diffusivity values for cells in the current input box for when the Diffusivity option has been activated by the DIFFUSE keyword in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"EDIT":{"name":"EDIT","sections":["EDIT"],"supported":null,"summary":"The EDIT activation keyword marks the end of the GRID section and the start of the EDIT section that enables modifications to the OPM Flow calculated properties derived from the data entered in the GRID section, for example grid block pore volumes via the PORV array and the transmissibilities via the TRANX, TRANY and TRANZ family of keywords.","parameters":[],"example":"-- ==============================================================================\n--\n-- EDIT SECTION\n--\n-- ==============================================================================\nEDIT\nThe above example marks the end of the GRID section and the start of the EDIT section in the OPM Flow data input file.","size_kind":"none","size_count":0},"EDITNNC":{"name":"EDITNNC","sections":["EDIT"],"supported":false,"summary":"EDITNNC enables Non-Neighbor Connections (“NNC”), entered via the NNC keyword or calculated by the simulator, to be multiplied (re-scaled) by a constant. For example, if the existing transmissibility between non-neighbor connections is Told and the multiplier is C, then the resulting transmissibility, Tnew, will be [T sub{new}~= C ``x ``T sub{old}]. . Only previously defined NNC’s entered via the NNC keyword or calculated by the simulator can be edited, otherwise a warning message will be printed.","parameters":[{"index":1,"name":"I1","description":"A positive integer that defines the first grid block in the I-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NX on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":2,"name":"J1","description":"A positive integer that defines the first grid block in the J-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NY on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":3,"name":"K1","description":"A positive integer that defines the first grid block in the K-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NZ on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":4,"name":"I2","description":"A positive integer that defines the second grid block in the I-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NX on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":5,"name":"J2","description":"A positive integer that defines the second grid block in the J-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NY on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":6,"name":"K2","description":"A positive integer that defines the second grid block in the K-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NZ on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":7,"name":"TRANSMUL","description":"TRANSMUL is a positive real number greater than or equal to zero that defines a constant that scales the transmissibility between the first grid block (I1, J1, K1) and the second grid block (I2, J2, K2). The default value of one means no scaling will be applied.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1","value_type":"DOUBLE"},{"index":8,"name":"ISATNUM1","description":"The default value of zero means the existing saturation table allocated to the upstream cell (I1,J1,K1).","units":{},"default":"0","value_type":"INT"},{"index":9,"name":"ISATNUM2","description":"ISATNUM2 is a positive integer defining which saturation table number (relative permeability table) to be used for flow from the second grid block to the first grid block. The default value of zero means the existing saturation table allocated to the downstream cell (I2,J2,K2).","units":{},"default":"0","value_type":"INT"},{"index":10,"name":"IPRSNUM1","description":"IPRSNUM1 is a positive integer defining which pressure table number (PVT table) to be used for flow from the first grid block to the second grid block. The default value of zero means the existing PVT table allocated to the upstream cell (I1,J1,K1).","units":{},"default":"0","value_type":"INT"},{"index":11,"name":"IPRSNUM2","description":"IPRSNUM2 is a positive integer defining which pressure table number (PVT table) to be used for flow from the second grid block to the first grid block. The default value of zero means the existing PVT table allocated to the downstream cell (I2,J2,K2).","units":{},"default":"0","value_type":"INT"},{"index":12,"name":"FACE1","description":"FACE1 is a character string that defines the face associated with flow from the first grid block to the second grid block, where FACE1 can have values of: X+, X-, Y+, Y-, Z+, or Z-. FACE1 is used with the commercial simulator’s Vertical Equilibrium option which is not supported by OPM Flow.","units":{},"default":"None","value_type":"STRING"},{"index":13,"name":"FACE2","description":"FACE2 is a character string that defines the face associated with flow from the second grid block to the first grid block, where FACE2 can have values of: X+, X-, Y+, Y-, Z+, or Z-. FACE2 is used with the commercial simulator’s Vertical Equilibrium option which is not supported by OPM Flow.","units":{},"default":"None","value_type":"STRING"},{"index":14,"name":"DIFFNNC","description":"DIFFNNC is a positive real number greater than or equal to zero that scales the diffusivity between the first grid block (I1, J1, K1) and the second grid block (I2, J2, K2).","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.0","value_type":"DOUBLE"}],"example":"--\n-- MANUALLY RESCALE NON-NEIGHBOR CONNECTIONS\n--\n-- ------------ BOX ----------- -- TRANSMUL --\n-- I1 J1 K1 I2 J2 K2\nEDITNCC\n1 1 1 1 1 2 0.2000 / SET NNC FOR FAULT\n1 1 2 1 1 3 0.2000 / SET NNC FOR FAULT\n1 1 3 1 1 4 0.2000 / SET NNC FOR FAULT\n/\nThe above example multiplies the transmissibility between cells (1, 1, 1) and (1, 1, 2), (1, 1, 2) and (1, 1, 3) and finally between (1, 1, 3) and (1, 1, 4) by 0.200.","expected_columns":14,"size_kind":"list"},"EDITNNCR":{"name":"EDITNNCR","sections":["EDIT"],"supported":null,"summary":"EDITNNCR enables Non-Neighbor Connections (“NNC”), entered via the NNC keyword or calculated by the simulator, to be reset to a user defined value. Only previously defined NNC’s entered via the NNC keyword or calculated by the simulator can be edited, otherwise a warning message will be printed. See also the EDITNNC keyword in the EDIT section that scales an existing NNC.","parameters":[{"index":1,"name":"I1","description":"A positive integer that defines the first grid block in the I-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NX on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":2,"name":"J1","description":"A positive integer that defines the first grid block in the J-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NY on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":3,"name":"K1","description":"A positive integer that defines the first grid block in the K-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NZ on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":4,"name":"I2","description":"A positive integer that defines the second grid block in the I-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NX on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":5,"name":"J2","description":"A positive integer that defines the second grid block in the J-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NY on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":6,"name":"K2","description":"A positive integer that defines the second grid block in the K-direction in a non-neighbor connection, must be greater than or equal to one and less than or equal to NZ on the DIMENS keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":7,"name":"TRANSNNC","description":"TRANSNNC is a positive real number greater than or equal to zero that defines the transmissibility between the first grid block (I1, J1, K1) and the second grid block (I2, J2, K2). This value cannot be defaulted and must be defined.","units":{"field":"cP.rb/day/psia","metric":"cP.rm3/day/bars","laboratory":"cP.rcc/hr/atm"},"default":"None","value_type":"DOUBLE","dimension":"Transmissibility"},{"index":8,"name":"ISATNUM1","description":"ISATNUM1 is a positive integer defining which saturation table number (relative permeability table) to be used for flow from the first grid block to the second grid block. The default value of zero means the existing saturation table allocated to the upstream cell (I1,J1,K1).","units":{},"default":"0","value_type":"INT"},{"index":9,"name":"ISATNUM2","description":"ISATNUM2 is a positive integer defining which saturation table number (relative permeability table) to be used for flow from the second grid block to the first grid block. The default value of zero means the existing saturation table allocated to the downstream cell (I2,J2,K2).","units":{},"default":"0","value_type":"INT"},{"index":10,"name":"IPRSNUM1","description":"IPRSNUM1 is a positive integer defining which pressure table number (PVT table) to be used for flow from the first grid block to the second grid block. The default value of zero means the existing PVT table allocated to the upstream cell (I1,J1,K1).","units":{},"default":"0","value_type":"INT"},{"index":11,"name":"IPRSNUM2","description":"IPRSNUM2 is a positive integer defining which pressure table number (PVT table) to be used for flow from the second grid block to the first grid block. The default value of zero means the existing PVT table allocated to the downstream cell (I2,J2,K2).","units":{},"default":"0","value_type":"INT"},{"index":12,"name":"FACE1","description":"FACE1 is a character string that defines the face associated with flow from the first grid block to the second grid block, where FACE1 can have vales of: X+, X-, Y+, Y-, Z+, or Z-.","units":{},"default":"None","value_type":"STRING"},{"index":13,"name":"FACE2","description":"FACE2 is a character string that defines the face associated with flow from the second grid block to the first grid block, where FACE2 can have vales of: X+, X-, Y+, Y-, Z+, or Z-.","units":{},"default":"None","value_type":"STRING"},{"index":14,"name":"DIFFNNC","description":"DIFFNNC is a positive real number greater than or equal to zero that scales the diffusivity between the first grid block (I1, J1, K1) and the second grid block (I2, J2, K2). The default value is the value calculated in the GRID section.","units":{"field":"feet","metric":"meters","laboratory":"cm"},"default":"1*","value_type":"DOUBLE","dimension":"Length"}],"example":"--\n-- MANUALLY RESET NON-NEIGHBOR CONNECTIONS\n--\n-- ------------ BOX ----------- -- TRANSNNC --\n-- I1 J1 K1 I2 J2 K2\nEDITNCCR\n1 1 1 1 1 2 0.2500 / RESET NNC TRANS FOR FAULT\n1 1 2 1 1 3 0.2500 / RESET NNC TRANS FAULT\n1 1 3 1 1 4 0.2500 / RESET NNC TRANS FAULT\n/\nThe above example res-sets the transmissibility between cells (1, 1, 1) and (1, 1, 2), (1, 1, 2) and (1, 1, 3) and (1, 1, 3) and (1, 1, 4) to be 0.2500.","expected_columns":14,"size_kind":"list"},"HMMULT":{"name":"HMMULT","sections":["EDIT"],"supported":false,"summary":"The HMMULT series of keywords defines the history match gradient cumulative permeability multipliers, for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section. The keyword consists of the first six characters of “HMMULT” followed by a one or two character string shown in Table 7.5, that determines the transmissibility direction, for example, HMMULTX.","parameters":[],"example":"| Mnemonic | Cartesian Grid | Radial Grid | | |\n|--------------|----------------|--------------|----------------|----------|\n| Grid Keyword | HMMULT Keyword | Grid Keyword | HMMULT Keyword | |\n| X/R | MULTX | HMMULTX | MULTR | HMMULTR |\n| XY | | HMMULTXY | | |\n| Y/HT | MULTY | hMMULTY | MULTTHT | HMMULTTH |\n| z | MULTZ | HMMULTZ | MULTZ | HMMULTZ |\n| PV | MULTPV | HMMULTPV | MULTPV | HMMULTPV |"},"PORV":{"name":"PORV","sections":["EDIT"],"supported":null,"summary":"PORV defines the pore volumes for all the cells in the model via an array. The keyword can be used for all grid types, except for the Radial Grid geometry. The keyword effectively overwrites previously entered and calculated data. The area to be modified can be defined via the various grid selection keywords, ADD, BOX, EQUALS, etc., and areas that are not selected remain unchanged.","parameters":[{"index":1,"name":"PORV","description":"PORV is an array of real positive numbers assigning a pore volume to each cell in the model. Only the values in the currently defined input BOX needed be entered. Repeat counts may be used, for example 20*100.0.","units":{"field":"rb","metric":"rm3","laboratory":"rcc"},"default":"None"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1* 100 1* 100 20 20 / DEFINE BOX AREA\n--\n-- SET PORV FOR THE GRID BLOCKS\n--\nPORV\n1000*0.00 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nHere the BOX statement is used to define the input grid for the PORV keyword, which overwrites the pore volume previously calculated with pore volume values of zero, resulting in a no-flow boundary in that part of the field between layers 19 and 21, since layer 20 is deactivated. The ENDBOX keyword resets the input box to the full grid.","size_kind":"array"},"TRANR":{"name":"TRANR","sections":["EDIT"],"supported":false,"summary":"TRANR defines the transmissibility in the +R direction for all the cells in the model via an array. The keyword can only be used with Radial Grid geometry grids. The keyword effectively overwrites previously entered and calculated data. The transmissibility overwritten is the +R face transmissibility of each grid block, that is for cell (I, J, K) the transmissibility between cells (I, J, K) and (I+1, J, K).","parameters":[{"index":1,"name":"TRANR","description":"TRANR is an array of real positive numbers assigning the transmissibility in the R direction to each cell in the model. Repeat counts may be used, for example 20*100.0.","units":{"field":"cP.rb/day/psia","metric":"cP.rm3/day/bars","laboratory":"cP.rcc/hr/atm"},"default":"None"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1 1 10 10 1 120 / DEFINE BOX AREA\n--\n-- SET TRANR+ TRANSMISSIBILITY\n--\nTRANR\n120*0.00 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nHere the BOX statement is used to define the input grid for the TRANR keyword, which overwrites the transmissibility previously calculated with transmissibility values of zero, resulting in a no-flow boundary in that part of the grid. The ENDBOX keyword resets the input box to the full grid.","size_kind":"array"},"TRANTHT":{"name":"TRANTHT","sections":["EDIT"],"supported":false,"summary":"TRANTHT defines the transmissibility in the +Theta direction for all the cells in the model via an array. The keyword can only be used with Radial Grid geometry grids. The keyword effectively overwrites previously entered and calculated data. The transmissibility overwritten is the +Theta face transmissibility of each grid block, that is for cell (I, J, K) the transmissibility between cells (I, J, K) and (I, J+1, K).","parameters":[{"index":1,"name":"TRANTHT","description":"TRANTHT is an array of real positive numbers assigning the transmissibility in the +Theta direction to each cell in the model. Repeat counts may be used, for example 20*100.0.","units":{"field":"cP.rb/day/psia","metric":"cP.rm3/day/bars","laboratory":"cP.rcc/hr/atm"},"default":"None"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n10 10 1 6 1 3 / DEFINE BOX AREA\n--\n-- SET TRANTHT TRANSMISSIBILITY\n--\nTRANTHT\n18*0.00 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nHere the BOX statement is used to define the input grid for the TRANTHT keyword, which overwrites the transmissibility previously calculated with transmissibility values of zero, resulting in a no-flow boundary in that part of the grid. The ENDBOX keyword resets the input box to the full grid.","size_kind":"array"},"TRANX":{"name":"TRANX","sections":["EDIT"],"supported":null,"summary":"TRANX defines the transmissibility in the X direction for all the cells in the model via an array. The keyword can be used for all grid types, except for the Radial Grid geometry. The keyword effectively overwrites previously entered and calculated data. The transmissibility overwritten is the +X face transmissibility of each grid block, that is for cell (I, J, K) the transmissibility between cells (I, J, K) and (I+1, J, K).","parameters":[{"index":1,"name":"TRANX","description":"TRANX is an array of real positive numbers assigning the transmissibility in the X direction to each cell in the model. Repeat counts may be used, for example 20*100.0.","units":{"field":"cP.rb/day/psia","metric":"cP.rm3/day/bars","laboratory":"cP.rcc/hr/atm"},"default":"None"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1 1 10 10 1 120 / DEFINE BOX AREA\n--\n-- SET TRANX+ TRANSMISSIBILITY\n--\nTRANX\n120*0.00 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nHere the BOX statement is used to define the input grid for the TRANX keyword, which overwrites the transmissibility previously calculated with transmissibility values of zero, resulting in a no-flow boundary in that part of the field. The ENDBOX keyword resets the input box to the full grid.","size_kind":"array"},"TRANY":{"name":"TRANY","sections":["EDIT"],"supported":null,"summary":"TRANY defines the transmissibility in the Y direction for all the cells in the model via an array. The keyword can be used for all grid types, except for the Radial Grid geometry. The keyword effectively overwrites previously entered and calculated data. The transmissibility overwritten is the +Y face transmissibility of each grid block, that is for cell (I, J, K) the transmissibility between cells (I, J, K) and (I, J+1, K).","parameters":[{"index":1,"name":"TRANY","description":"TRANY is an array of real positive numbers assigning the transmissibility in the Y direction to each cell in the model. Repeat counts may be used, for example 20*100.0.","units":{"field":"cP.rb/day/psia","metric":"cP.rm3/day/bars","laboratory":"cP.rcc/hr/atm"},"default":"None"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1 1 10 10 1 120 / DEFINE BOX AREA\n--\n-- SET TRANY+ TRANSMISSIBILITY\n--\nTRANY\n120*0.00 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nHere the BOX statement is used to define the input grid for the TRANY keyword, which overwrites the transmissibility previously calculated with transmissibility values of zero, resulting in a no-flow boundary in that part of the field. The ENDBOX keyword resets the input box to the full grid.","size_kind":"array"},"TRANZ":{"name":"TRANZ","sections":["EDIT"],"supported":null,"summary":"TRANX defines the transmissibility in the z direction for all the cells in the model via an array. The keyword can be used for all grid types, except for the Radial Grid geometry. The keyword effectively overwrites previously entered and calculated data. The transmissibility overwritten is the +Z face transmissibility of each grid block, that is for cell (I, J, K) the transmissibility between cells (I, J, K) and (I, J, K+1).","parameters":[{"index":1,"name":"TRANZ","description":"TRANZ is an array of real positive numbers assigning the transmissibility in the Z direction to each cell in the model. Repeat counts may be used, for example 20*100.0.","units":{"field":"cP.rb/day/psia","metric":"cP.rm3/day/bars","laboratory":"cP.rcc/hr/atm"},"default":"None"}],"example":"--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1* 100 1* 100 20 20 / DEFINE BOX AREA\n--\n-- SET TRANZ+ TRANSMISSIBILITY\n--\nTRANZ\n1000*0.00 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nHere the BOX statement is used to define the input grid for the TRANZ keyword, which overwrites the transmissibility previously calculated with transmissibility values of zero, resulting in a no-flow boundary in that part of the field between layers 20 and 21. The ENDBOX keyword resets the input box to the full grid.","size_kind":"array"},"ACF":{"name":"ACF","sections":["PROPS"],"supported":false,"summary":"The ACF keyword defines the acentric factors for each of the compositional components active in the model and for each equation of state. The keyword should only be used if the compositional mode has been requested using the COMPS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"ACF","description":"A series of real numbers that define the acentric factors for each of the compositional components active in the model.","units":{},"default":"None","value_type":"DOUBLE","dimension":"1"}],"example":"The following example defines the acentric factors for each component in a single three-component equation of state model.\n--\n-- Acentric Factors\n--\nACF\n0.0108 0.2273 0.3434 /\nThe following example defines the acentric factors for each component in two three-component equation of state models.\n--\n-- Acentric Factors\n--\nACF\n0.0108 0.2273 0.3434 /\n0.0110 0.2281 0.3428 /","size_kind":"fixed","variadic_record":true},"ACTCO2S":{"name":"ACTCO2S","sections":["PROPS"],"supported":null,"summary":"The keyword ACTCO2S specifies the activity model for salting-out effects when calculating mutual solubility in the CO2 storage module which is activated by the CO2STORE keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"ACTMODEL","description":"A positive integer value selecting the activity model for the salting-out effect. The choices are: The Rumpf et al.1\n Rumpf, B.,Nicolaisen, H., Ocal, C., and Maurer, G., 1994. Solubility of carbon dioxide in aqueous solutions of sodium chloride: experimental results and correlation. J. Sol. Chem. 23, 431-448. model as detailed in the paper by Spycher and Pruess2\n Spycher, N., and Pruess, K., 2005. CO2-H2O mixtures in the geological sequestration of CO2. II. Partitioning in chloride brines at 12–100°C and up to 600 bar. Geochimica Et Cosmochimica Acta 69, 3309–3320.. The model was calibrated in the P-T range 5 to 96 bar and 40 to 160°C, and was shown in Spycher and Pruess2 to be accurate in the P-T range 1 to 600 bar and 12 to 100°C. Note that this model requires a (fixed-point) iteration procedure to compute solubility, but usually converges within few iterations. Rumpf, B.,Nicolaisen, H., Ocal, C., and Maurer, G., 1994. Solubility of carbon dioxide in aqueous solutions of sodium chloride: experimental results and correlation. J. Sol. Chem. 23, 431-448. Spycher, N., and Pruess, K., 2005. CO2-H2O mixtures in the geological sequestration of CO2. II. Partitioning in chloride brines at 12–100°C and up to 600 bar. Geochimica Et Cosmochimica Acta 69, 3309–3320. The Duan and Sun3\n Duan Z., and Sun R., 2003. An improved model calculating CO2 solubility in pure water and aqueous NaCl solutions from 257 to 533 K and from 0 to 2000 bar. Chem. Geol. 193, 257–271. model as detailed in the paper by Spycher and Pruess4\n Spycher, N., and Pruess, K., 2009. A Phase-Partitioning Model for CO2–Brine Mixtures at Elevated Temperatures and Pressures: Application to CO2-Enhanced Geothermal Systems. Transp Porous Med 82, 173–196.. The model was recalibrated to the P-T range 1 to 600 bar and 12 to 300°C, and was shown to be accurate within the same range. Note that above 99°C a (fixed-point) iteration procedure is required to compute solubility, while below 99°C the computations are done in a direct manner without needing iterations. Duan Z., and Sun R., 2003. An improved model calculating CO2 solubility in pure water and aqueous NaCl solutions from 257 to 533 K and from 0 to 2000 bar. Chem. Geol. 193, 257–271. Spycher, N., and Pruess, K., 2009. A Phase-Partitioning Model for CO2–Brine Mixtures at Elevated Temperatures and Pressures: Application to CO2-Enhanced Geothermal Systems. Transp Porous Med 82, 173–196. The Duan and Sun3 model as detailed in the paper by Spycher and Pruess2. The model was calibrated to the P-T range 0 to 2000 bar and 0 to 260°C, and was shown in Spycher and Pruess2 to be accurate in the P-T range 1 to 600 bar and 12 to 100°C. Note that no iterations are required to compute the solubility.","units":{},"default":"3","value_type":"INT"}],"example":"The following example activates activity model number 1.\n--\n-- ACTIVITY MODEL FOR SALTING-OUT EFFECTS IN CO2\n--\nACTCO2S\n1 /","expected_columns":1,"size_kind":"fixed","size_count":1},"ADSALNOD":{"name":"ADSALNOD","sections":["PROPS"],"supported":false,"summary":"ADSALNOD defines the salt concentration value based on a cells SATNUM number. The ADSALNOD property is used in the calculation of a polymer viscosity when the polymer and the salt options has been activated by the POLYMER and BRINE keywords in the RUNSPEC section. In the RUNSPEC section the number of SATNUM functions is declared by the NTSFUN variable on the TABDIMS keyword and allocated to individual cells by the SATNUM property array in the REGIONS section. NSSFUN on the TABDIMS keyword in the RUNSPEC section defines the maximum number of rows (or saturation values) in the relative permeability saturation tables and also sets the maximum number of entries for each ADSALNOD data set. The number of values for each data set must correspond to the number of polymer solution adsorption entries on the PLYADSS keyword. For example, if there are three sets of relative permeability tables and four values on the PLYADSS keyword, then three ADSALNOD data sets with four values of salt concentrat...","parameters":[{"index":1,"name":"SALTCON","description":"Field","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"Metric","value_type":"DOUBLE","dimension":"Density"}],"example":"Given three sets of relative permeability tables and four values on the PLYADSS keyword, then the data salt concentration should be entered as follows:\n--\n-- SETS SALT CONCENTRATION FOR POLYMER SOLUTION ADSORPTION\n-- VIA SATNUM ARRAY ALLOCATION\n--\n-- SALT\n--\nADSALNOD\n1.0\n5.0\n10.5\n25.0 / SATNUM TABLE NO. 01\n1.0\n3.0\n7.5\n15.0 / SATNUM TABLE NO. 02\n1.0\n7.5\n20.5\n35.0 / SATNUM TABLE NO. 03\nSee also the SALTNODE keyword.","size_kind":"fixed","variadic_record":true},"ADSORP":{"name":"ADSORP","sections":["PROPS"],"supported":false,"summary":"The ADSORP keyword defines the parameters for the generalized Langmuir Adsorption174\n Langmuir, Irving (June 1918). \"The Adsorption of Gases on Plane Surface of Glass, Mica and Platinum\". The Research Laboratory of the General Electric Company. 40 (9): 1361–1402. doi:10.1021/ja02242a004 function for when the polymer, surfact, alkaline, foam and tracers phases have been activated in the RUNSPEC section by the POLYMER, SURFACT, ALKALINE, FOAM and TRACER keywords.","parameters":[{"index":1,"name":"ADSORBING_COMP","description":"","units":{},"default":"","value_type":"STRING","record":1},{"index":1,"name":"ADORPTION_ISOTHERM","description":"","units":{},"default":"LANGMUIR","value_type":"STRING","record":2},{"index":2,"name":"A1","description":"","units":{},"default":"","value_type":"DOUBLE","record":2},{"index":3,"name":"A2","description":"","units":{},"default":"","value_type":"DOUBLE","record":2},{"index":4,"name":"B","description":"","units":{},"default":"","value_type":"DOUBLE","record":2},{"index":5,"name":"M","description":"","units":{},"default":"0.5","value_type":"DOUBLE","dimension":"1","record":2},{"index":6,"name":"N","description":"","units":{},"default":"0.5","value_type":"DOUBLE","dimension":"1","record":2},{"index":7,"name":"K_REF","description":"","units":{},"default":"","value_type":"DOUBLE","record":2}],"example":"","records_meta":[{"expected_columns":1},{"expected_columns":7}],"size_kind":"list"},"ALKADS":{"name":"ALKADS","sections":["PROPS"],"supported":false,"summary":"ALKADS defines the alkaline adsorption functions for when the alkaline model has been activated via the ALKALINE keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Density","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"ALKROCK":{"name":"ALKROCK","sections":["PROPS"],"supported":false,"summary":"The ALKROCK keyword defines the rock alkaline properties for when the alkaline model has been activated via the ALKALINE keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"ROCK_ADS_INDEX","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":1,"size_kind":"fixed"},"ALPOLADS":{"name":"ALPOLADS","sections":["PROPS"],"supported":false,"summary":"ALPOLDS defines the polymer adsorption versus alkaline concentration multipliers for when the alkaline model has been activated via the ALKALINE keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Density","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"ALSURFAD":{"name":"ALSURFAD","sections":["PROPS"],"supported":false,"summary":"ALSURAD defines the surfactant adsorption versus alkaline concentration multipliers for when the alkaline model has been activated via the ALKALINE keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Density","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"ALSURFST":{"name":"ALSURFST","sections":["PROPS"],"supported":false,"summary":"The ALSURFST keyword defines the water-oil surface tension versus alkaline concentration multipliers for when the alkaline model has been activated via the ALKALINE keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Density","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"APIGROUP":{"name":"APIGROUP","sections":["PROPS"],"supported":false,"summary":"The APIGROUP keyword defines the maximum number of groups of oil PVT tables when the API tracking option has been activated via the API keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"MAX_OIL_PVT_GROUP_COUNT","description":"","units":{},"default":"1","value_type":"INT"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"AQUTAB":{"name":"AQUTAB","sections":["PROPS"],"supported":null,"summary":"The AQUTAB keyword defines additional Carter-Tracy175\n Carter, R. D., and Tracy, G. W. “An Improved Method for Calculating Water Influx.” Transactions of AIME, Vol. 219 (1060), pp 415-417. aquifer functions to be used in the model. Carter-Tracy representation of the aquifer influx is via a qw term in the non-linear aquifer influence function Q(t). It allows the water influx from the aquifer to be represented in the simulator by assuming that there is a constant water influx rate over finite time periods. It is derived from the superposition methods of van Everdingen and Hurst176\n Van Everdingen, A. F., and Hurst, W. “The Application of the Laplace Transform to Flow Problems in Reservoirs.” Transactions of AIME, Vol. 186 (1949), pp. 305-324., whose superposition methods are not suitable for implementation in reservoir simulation software, although they are very useful in interpreting aquifer response. The storage requirements and calculation complexity of handling the resu...","parameters":[{"index":1,"name":"TD","description":"Dimensionless Time","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":["1","1"]},{"index":2,"name":"PD","description":"Dimensionless Pressure","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- CARTER-TRACY AQUIFER INFLUENCE TABLES\n-- (STARTS FROM TABLE NO. 2, AS DEFAULT IS TABLE NO. 1)\n--\nAQUTAB\n--\n-- TD PD\n-- ------- ---------\n0.06 0.251\n0.08 0.288\n0.10 0.322\n0.12 0.355\n0.14 0.387\n0.16 0.420\n0.18 0.452\n0.20 0.484\n0.22 0.516\n0.24 0.548\n0.26 0.580\n0.28 0.612\n0.30 0.644\n0.35 0.724\n0.40 0.804\n0.45 0.884\n0.50 0.964\n0.55 1.044\n0.60 1.124 / RD=1.5 TABLE NO. 02\n--\n-- TD PD\n-- ------- ---------\n0.22 0.443\n0.24 0.459\n0.26 0.476\n0.28 0.492\n0.30 0.507\n0.32 0.522\n0.34 0.536\n0.36 0.551\n0.38 0.565\n0.40 0.579\n0.42 0.593\n0.44 0.607\n0.46 0.621\n0.48 0.634\n0.50 0.648\n0.6 0.715\n0.7 0.782\n0.8 0.849\n0.9 0.915\n1.0 0.982\n2.0 1.649\n3.0 2.316\n5.0 3.649 / RD=2.0 TABLE NO. 03\nThe above example defines tables two and three Carter-Tracy aquifer influence tables.\n| Note OPM Flow includes the infinite acting Carter-Tracy aquifer influence table as a default for table number one; thus data entered on this keyword starts from table number two. |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Carter-Tracy Aquifer Influence Functions | | | | | | | | |\n|------------------------------------------|------------------------|------------------------|------------------------|------------------------|--------|--------|--------|--------|\n| No. | rD = 1.5 Dimensionless | rD = 2.0 Dimensionless | rD = 2.5 Dimensionless | rD = 3.0 Dimensionless | | | | |\n| tD | pD | tD | pD | tD | pD | tD | pD | |\n| 1 | 0.0600 | 0.2510 | 0.2200 | 0.4430 | 0.4000 | 0.5650 | 0.5200 | 0.6270 |\n| 2 | 0.0800 | 0.2880 | 0.2400 | 0.4590 | 0.4200 | 0.5760 | 0.5400 | 0.6360 |\n| 3 | 0.1000 | 0.3220 | 0.2600 | 0.4760 | 0.4400 | 0.5870 | 0.5600 | 0.6450 |\n| 4 | 0.1200 | 0.3550 | 0.2800 | 0.4920 | 0.4600 | 0.5980 | 0.6000 | 0.6620 |\n| 5 | 0.1400 | 0.3870 | 0.3000 | 0.5070 | 0.4800 | 0.6080 | 0.6500 | 0.6830 |\n| 6 | 0.1600 | 0.4200 | 0.3200 | 0.5220 | 0.5000 | 0.6180 | 0.7000 | 0.7030 |\n| 7 | 0.1800 | 0.4520 | 0.3400 | 0.5360 | 0.5200 | 0.6280 | 0.7500 | 0.7210 |\n| 8 | 0.2000 | 0.4840 | 0.3600 | 0.5510 | 0.5400 | 0.6380 | 0.8000 | 0.7400 |\n| 9 | 0.2200 | 0.5160 | 0.3800 | 0.5650 | 0.5600 | 0.6470 | 0.8500 | 0.7580 |\n| 10 | 0.2400 | 0.5480 | 0.4000 | 0.5790 | 0.5800 | 0.6570 | 0.9000 | 0.7760 |\n| 11 | 0.2600 | 0.5800 | 0.4200 | 0.5930 | 0.6000 | 0.6660 | 0.9500 | 0.7910 |\n| 12 | 0.2800 | 0.6120 | 0.4400 | 0.6070 | 0.6500 | 0.688","size_kind":"fixed","variadic_record":true},"BDENSITY":{"name":"BDENSITY","sections":["PROPS"],"supported":false,"summary":"BDENSITY defines the brine surface density for when the brine phase has been activated in the model by the BRINE keyword in the RUNSPEC section. The number of BDENSITY vector data sets is defined by the NTPVT parameter on the TABDIMS keyword in the RUNSPEC section. Each record consists of a maximum of NPPVT values, as declared on the TABDIMS keyword in the RUNSPEC section, with each value representing a brine surface density.","parameters":[{"index":1,"name":"WATDEN","description":"Field","units":{"field":"lb/ft3","metric":"kg/m","laboratory":"gm/cc"},"default":"Metric","value_type":"DOUBLE","dimension":"Density"}],"example":"The following shows the BDENSITY and PVTWSALT keywords for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set equal to two and NPPVT is set to greater than four on the TABDIMS keyword.\n--\n-- BRINE WATER DENSITY DATA FOR PVTWSALT KEYWORD\n--\n-- SALTCON SALTCON SALTCON SALTCON SALTCON -- DENSITY DENSITY DENSITY DENSITY DENSITY\n-- ------- ------- ------- ------- -------\nBDENSITY\n62.20 63.50 64.75 65.90 / FOR PVTWSALT TABLE 1\n64.00 65.50 67.00 / FOR PVTWSALT TABLE 2 --\n-- WATER SALT PVT TABLE\n--\nPVTWSALT\n-- REF PRES REF SALT\n-- PSIA LB/STB\n-- -------- --------\n4500.0 0.000 / TABLE NO. REF. DATA\n--\n-- SALTCONC BW CW VISC VISC\n-- LB/STB RB/STB 1/PSIA CPOISE GRAD\n-- -------- -------- ------- ------ ------\n0.0 1.020 2.7E-6 0.370 0.0\n2.0 1.010 2.7E-6 0.370 0.0\n4.0 1.000 2.7E-6 0.370 0.0\n10.0 0.950 2.7E-6 0.370 0.0 / TABLE NO. 01 SALT DATA\n--\n-- REF PRES REF SALT\n-- PSIA LB/STB\n-- -------- --------\n4000.0 0.000 / TABLE NO. 02 REF. DATA\n--\n-- SALTCONC BW CW VISC VISC\n-- LB/STB RB/STB 1/PSIA CPOISE GRAD\n-- -------- -------- ------- ------ ------\n0.0 1.005 2.5E-6 0.320 0.0\n6.0 0.985 2.5E-6 0.320 0.0\n12.0 0.930 2.5E-6 0.320 0.0 / TABLE NO. 02 SALT DATA\n| Note In OPM Flow the tracer equations are solved decoupled from the reservoir equations at the end of a time step. For each tracer an implicit system is solved, however, the tracer equations are linear, resulting in converge in two iterations. However, the Brine phase is solved fully implicitly and is fully coupled with the other flow equations. This is different to the commercial simulator, where the tracer equations are solved explicitly after the flow equations have converged at the end of a time step. This can lead to numerical instabilities if there are large variations in brine densities. |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"fixed","variadic_record":true},"BGGI":{"name":"BGGI","sections":["PROPS"],"supported":false,"summary":"The BGGI keyword defines Gi gas formation volume factor as a function of Gi and pressure for when the Gi option has been invoked via the GIMODEL keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"GAS_PRESSURE","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":2,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"}],"example":"","size_kind":"fixed","variadic_record":true},"BIC":{"name":"BIC","sections":["PROPS"],"supported":false,"summary":"The BIC keyword defines the binary interaction coefficients for each pair of compositional components active in the model and for each equation of state. The keyword should only be used if the compositional mode has been requested using the COMPS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"BIC","description":"A series of real numbers that define the binary interaction coefficients [k_ij]for each pair (i, j) of compositional components active in the model. The matrix [k_ij]is symmetrical with zeroes on the diagonal so only the portion of the matrix below the diagonal is required (i.e., i = {2, ... COMPS} and j < i), where COMPS is specified by the COMPS keyword in the RUNSPEC section. The values are ordered with j cycling fastest (i.e. [k_21], , [k_31], , [k_32], , [k_41], , [k_42], , [k_43], ...)., ...).","units":{},"default":"0","value_type":"DOUBLE","dimension":"1"}],"example":"The following example defines the binary interaction coefficients for each pair of compositional components in a single three-component equation of state model.\n--\n-- Binary Interaction Coefficients\n--\nBIC\n0.1209\n0.1310 0.0339 /\nThe following example defines the binary interaction coefficients for each component in two three-component equation of state models.\n--\n-- Binary Interaction Coefficients\n--\nBIC\n0.1209\n0.1310 0.0339 /\n0.1209\n0.1310 0.0339 /","size_kind":"fixed","variadic_record":true},"BIOFPARA":{"name":"BIOFPARA","sections":["PROPS"],"supported":null,"summary":"The BIOFPARA keyword defines parameters for models including biofilms. For the parameters, biomass means both suspended microbes in the water phase (labeled as microbial) and biofilm. Currently the two available models with biofilm effects are the BIOFILM and the MICP model. See Landa-Marbán et al198\n Landa-Marbán, D., Tveit, S., Kumar, K., Gasda, S.E., 2021. Practical approaches to study microbially induced calcite precipitation at the field scale. Int. J. Greenh. Gas Control 106, 103256. https://doi.org/10.1016/j.ijggc.2021.103256. and 199\n Landa-Marbán, D., Kumar, K., Tveit, S., Gasda, S.E., 2021. Numerical studies of CO2 leakage remediation by micp-based plugging technology. In: Røkke, N.A. and Knuutila, H.K. (Eds) Short Papers from the 11th International Trondheim CCS conference, ISBN: 978-82-536-1714-5, 284-290.for further information on the MICP model parameters, which are also used in the BIOFILM model.","parameters":[{"index":1,"name":"DENSBIOF","description":"A real positive value that defines the density of the biofilm.","units":{"field":"lb/rft3","metric":"kg/rm3","laboratory":"gm/rcc"},"default":"None","value_type":"DOUBLE","dimension":["Density","1/Time","1/Time","Concentration","1","1","1/Time","1/Time","1","1/Time","Concentration","Density","1"]},{"index":2,"name":"DEATRATE","description":"A real value that defines the biomass death rate.","units":{"field":"1/days","metric":"1/days","laboratory":"1/hours"},"default":"None"},{"index":3,"name":"GROWRATE","description":"A real positive value that defines the maximum specific biomass growth rate.","units":{"field":"1/days","metric":"1/days","laboratory":"1/hours"},"default":"None"},{"index":4,"name":"HALFGROW","description":"A real positive value that defines the half-velocity coefficient in the Monod equation for the biomass growth rate.","units":{"field":"lb/rft3","metric":"kg/rm3","laboratory":"gm/rcc"},"default":"None"},{"index":5,"name":"YIELGROW","description":"A real value that defines the yield biomass growth coefficient.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":6,"name":"OXYGSUBS","description":"A real value that defines the mass ratio of oxygen consumed to substrate used for biomass growth.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":7,"name":"ATTARATE","description":"A real positive value that defines the microbial attachment rate.","units":{"field":"1/days","metric":"1/days","laboratory":"1/hours"},"default":"None"},{"index":8,"name":"DETARATE","description":"A real positive value that defines the biofilm detachment rate.","units":{"field":"1/days","metric":"1/days","laboratory":"1/hours"},"default":"None"},{"index":9,"name":"DETAEXPO","description":"A real value that defines the exponent in the norm for the water velocity in the detachment term (this value was set to 0.58 in the MICP publication).","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":10,"name":"UREARATE","description":"A real positive value that defines the maximum rate of urea utilization.","units":{"field":"1/days","metric":"1/days","laboratory":"1/hours"},"default":"None"},{"index":11,"name":"HALFUREA","description":"A real positive value that defines the half-velocity coefficient in the Monod equation for the urea utilization rate.","units":{"field":"lb/rft3","metric":"kg/rm3","laboratory":"gm/rcc"},"default":"None"},{"index":12,"name":"DENSCALC","description":"A real positive value that defines the calcite density.","units":{"field":"lb/rft3","metric":"kg/rm3","laboratory":"gm/rcc"},"default":"None"},{"index":13,"name":"YIELURCA","description":"A real value that defines the yield coefficient in the calcite precipitation term (units of produced calcite over units of urea utilization).","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"The example below is based on metric units, with NTSFUN equal to two on the TABDIMS keyword.\n--\n-- DEFINE BIOMASS PARAMETERS FOR THE MICP MODEL\n--\n-- DENS DEAT GROW HALF YIEL OXYG\n-- BIOF RATE RATE GROW GROW SUBS\n-- ------ ------ ------ ------ ------ ------ ------\n-- ATTA DETA DETA UREA HALF DENS YIEL\n-- RATE RATE EXPO RATE UREA CALC URCA\n-- ------ ------ ------ ------ ------ ------ ------\nBIOFPARA\n35 0.0275 3.6 2E-05 0.5 0.5\n0.0735 2.6E-13 0.58 1391 21.3 2710 1.67 /\n10 0.0275 3.6 2E-05 0.5 0.5\n0.0735 1.1E-05 0.58 1391 21.3 2710 1.67 /\n| Note This is an OPM Flow specific keyword. |\n|--------------------------------------------|","size_kind":"fixed","variadic_record":true},"BOGI":{"name":"BOGI","sections":["PROPS"],"supported":false,"summary":"The BOGI keyword defines Gi oil formation volume factor as a function of Gi and pressure for when the Gi option has been invoked via the GIMODEL keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"OIL_PRESSURE","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":2,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"}],"example":"","size_kind":"fixed","variadic_record":true},"CNAMES":{"name":"CNAMES","sections":["PROPS"],"supported":true,"summary":"The CNAMES keyword defines the names for each of the compositional components active in the model. The keyword should only be used if the compositional mode has been requested using the COMPS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"CNAMES","description":"A series of character strings of up to eight characters in length that define the names for each of the compositional components active in the model.","units":{},"default":"None"}],"example":"The following example defines how to confirm a three component formulation, together with defining the names of the compositional components, to be used with the CO2STORE and GASWAT options.\n--\n-- CONFIRM NUMBER OF COMPOSITIONAL COMPONENTS (OPM FLOW KEYWORD)\n--\nNCOMPS\n3 /\n--\n-- DEFINE COMPOSITIONAL COMPONENTS NAMES (OPM FLOW KEYWORD)\n--\nCNAMES\n'H2O'\n'CO2'\n'NACL' /\n| Note This keyword is only supported by OPM Flow when the two phase gas-water CO2 storage model has been activated using the CO2STORE keyword and either the GASWAT or the GAS and WATER keywords in the RUNSPEC section. Only the component names \"H2O\", \"CO2\" and \"NACL\" (water, CO2 and salt respectively) are recognized when the CNAMES keyword is used with the CO2STORE keyword; any other component names are ignored. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"array"},"COALADS":{"name":"COALADS","sections":["PROPS"],"supported":false,"summary":"The COALADS keyword defines the gas and solvent relative adsorption tables for when the coal phase has been activated via the COAL keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["1","1","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"COALPP":{"name":"COALPP","sections":["PROPS"],"supported":false,"summary":"The COALPP keyword defines the gas and solvent partial pressure adsorption tables for when the coal phase has been activated via the COAL keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["1","1","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"DENAQA":{"name":"DENAQA","sections":["PROPS"],"supported":true,"summary":"The DENAQA keyword specifies the three Ezrokhi coefficients for each compositional component and for each equation of state that are used to calculate the aqueous phase density. The keyword should only be used if the compositional mode has been requested using the COMPS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"COEFFS","description":"A series of real numbers that define the three Ezrokhi coeffients for each of the compositional components active in the model.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":"1"}],"example":"The following example defines the Ezrokhi coefficients for each component in a single three-component equation of state model.\n--\n-- Ezrokhi Coefficients for Aqueous Density Calculation\n--\nDENAQA\n--COEFF0 COEFF1 COEFF2\n2.0E-6 -5.0E-7 2.0E-9\n2.0E-6 -5.0E-7 2.0E-9\n2.0E-6 -5.0E-7 2.0E-9 /\nThe following example defines the Ezrokhi coefficients for each component in two three-component equation of state models.\n--\n-- Ezrokhi Coefficients for Aqueous Density Calculation\n--\nDENAQA\n--COEFF0 COEFF1 COEFF2\n2.0E-6 -5.0E-7 2.0E-9\n2.0E-6 -5.0E-7 2.0E-9\n2.0E-6 -5.0E-7 2.0E-9 /\n--\n2.0E-6 -5.0E-7 2.0E-9\n2.0E-6 -5.0E-7 2.0E-9\n2.0E-6 -5.0E-7 2.0E-9 /","size_kind":"fixed","variadic_record":true},"DENSITY":{"name":"DENSITY","sections":["PROPS"],"supported":null,"summary":"DENSITY defines the oil, water and gas surface densities for the fluids for various regions in the model. The number of DENSITY vector data sets is defined by the NTPVT parameter on the TABDIMS keyword in the RUNSPEC section and the allocation of the DENSITY data sets to different grid blocks in the model is done via the PVTNUM keyword in the REGIONS section. One data set consists of one record or line which is terminated by a “/”. The surface density or gravity must be entered using either the DENSITY or GRAVITY keywords irrespective of which phases are active in the model.","parameters":[{"index":1,"name":"OILDEN","description":"OILDEN is a real number defining the density of the oil phase at surface conditions.","units":{"field":"lb/ft3 37.457","metric":"kg/m3 600","laboratory":"gm/cc 0.6"},"default":"Defined","value_type":"DOUBLE","dimension":"Density"},{"index":2,"name":"WATDEN","description":"WATDEN is a real number defining the density of the water phase at surface conditions.","units":{"field":"lb/ft3 62.366","metric":"kg/m3 999.014","laboratory":"gm/cc 0.999014"},"default":"Defined","value_type":"DOUBLE","dimension":"Density"},{"index":3,"name":"GASDEN","description":"GASDEN is a real number defining the density of the gas phase at surface conditions.","units":{"field":"lb/ft3 0.062428","metric":"kg/m3 1.000","laboratory":"gm/cc 0.001"},"default":"Defined","value_type":"DOUBLE","dimension":"Density"}],"example":"The following shows the DENSITY keyword for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set to one.\n--\n-- OIL WAT GAS\n-- DENSITY DENSITY DENSITY\n-- ------- ------- -------\nDENSITY\n39.0 62.37 0.04520 / PVT DATA REGION 1\nThe next example shows the DENSITY keyword for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set to three.\n--\n-- OIL WAT GAS\n-- DENSITY DENSITY DENSITY\n-- ------- ------- -------\nDENSITY\n38.0 62.30 0.04500 / PVT DATA REGION 1\n39.0 62.37 0.04520 / PVT DATA REGION 2\n40.0 62.40 0.04800 / PVT DATA REGION 3\nThe third, and final, example shows the DENSITY keyword for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set to four. Here table two defaults to table one, and table four defaults to table three.\n--\n-- OIL WAT GAS\n-- DENSITY DENSITY DENSITY\n-- ------- ------- -------\nDENSITY\n38.0 62.30 0.04500 / PVT DATA REGION 1\n/ PVT DATA REGION 2\n39.0 62.37 0.04520 / PVT DATA REGION 3\n/ PVT DATA REGION 3\nAgain, note that there is no terminating “/” for this keyword.","expected_columns":3,"size_kind":"fixed"},"DEPTHTAB":{"name":"DEPTHTAB","sections":["PROPS"],"supported":false,"summary":"This keyword, DEPTHTAB, defines the river time and depth tables, for when the River option has been activated via the RIVRDIMS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","size_kind":"fixed","variadic_record":true},"DIAGDISP":{"name":"DIAGDISP","sections":["PROPS"],"supported":false,"summary":"This keyword, DIAGDISP, activates the alternate form of tracer dispersion matrix for when the Tracer facility has been activated by the TRACERS keyword in the RUNSPEC section.","parameters":[],"example":"","size_kind":"none","size_count":0},"DIFFAGAS":{"name":"DIFFAGAS","sections":["PROPS"],"supported":null,"summary":"The DIFFAGAS keyword defines the gas diffusion coefficients assuming a mass fraction formulation for each compositional component in the model and for each PVT region, for when the Molecular Diffusion option has been activated by the DIFFUSE keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"CO2DIFF","description":"A real positive number that declares the CO2 or H2 in gas diffusion coefficient in the given PVT region.","units":{"field":"ft2/day","metric":"m2/day","laboratory":"cm2/hour"},"default":"None","value_type":"DOUBLE","dimension":"Length*Length/Time"},{"index":2,"name":"WATDIFF","description":"A real positive number that specifies the water in gas diffusion coefficient in the given PVT region.","units":{"field":"ft2/day","metric":"m2/day","laboratory":"cm2/hour"},"default":"None","value_type":"DOUBLE","dimension":"Length*Length/Time"}],"example":"The example below is based on field units, with NTPVT equal to three on the TABDIMS keyword.\n--\n-- PVT REGION GAS COMPONENT DIFFUSION COEFFICIENTS (OPM FLOW KEYWORD)\n--\nDIFFAGAS\n-- CO2 IN WAT IN\n-- GAS DF GAS DF\n-- ------- -------\n0.160 0.150 / PVT REGION NO. 01\n0.165 0.155 / PVT REGION NO. 02\n/ PVT REGION NO. 03\nHere the third PVT region has no values for the two component diffusion coefficients, and therefore the simulator will use correlations to define the diffusivity coefficients for this PVT region.\n| Note This is an OPM Flow keyword used with OPM Flow’s CO2STORE or H2STORE and GASWAT keywords in the RUNSPEC section, and should not be confused with the version of the DIFFAGAS keyword used in the commercial compositional simulator that defines activity corrected diffusion coefficients. |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Note The option has been tested in combination with the CO2STORE keyword, but not for the general case at this point. |\n|-----------------------------------------------------------------------------------------------------------------------|\n| Diffusivity Conversion Factors | | |\n|--------------------------------|-------------------|-----------------|\n| Laboratory Measured Units | Conversion Factor | Simulator Units |\n| 1 cm2/s | 92.9979 ft2/day | Field |\n| 8.64 m2/day | Metric | |\n| 3600 cm2/hour | Laboratory | |","expected_columns":2,"size_kind":"fixed"},"DIFFAWAT":{"name":"DIFFAWAT","sections":["PROPS"],"supported":null,"summary":"The DIFFAWAT keyword defines the water diffusion coefficients assuming a mass fraction formulation for each compositional component in the model and for each PVT region, for when the Molecular Diffusion option has been activated by the DIFFUSE keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"CO2DIFF","description":"A real positive number that declares the CO2 or H2 in water diffusion coefficient in the given PVT region.","units":{"field":"ft2/day","metric":"m2/day","laboratory":"cm2/hour"},"default":"None","value_type":"DOUBLE","dimension":"Length*Length/Time"},{"index":2,"name":"WATDIFF","description":"A real positive number that specifies the water in water diffusion coefficient in the given PVT region.","units":{"field":"ft2/day","metric":"m2/day","laboratory":"cm2/hour"},"default":"None","value_type":"DOUBLE","dimension":"Length*Length/Time"}],"example":"The example below is based on field units, with NTPVT equal to three on the TABDIMS keyword.\n--\n-- PVT REGION WATER COMPONENT DIFFUSION COEFFICIENTS (OPM FLOW KEYWORD)\n--\nDIFFAWAT\n-- CO2 IN WAT IN\n-- WAT DF WAT DF\n-- ------- -------\n0.160 0.150 / PVT REGION NO. 01\n0.165 0.155 / PVT REGION NO. 02\n/ PVT REGION NO. 03\nHere the third PVT region has no values for the two component diffusion coefficients, and therefore the simulator will use correlations to define the diffusivity coefficients for this PVT region.\n| Note This is an OPM Flow specific keyword used with OPM Flow’s CO2STORE or H2STORE and GASWAT keywords in the RUNSPEC section. |\n|--------------------------------------------------------------------------------------------------------------------------------|\n| Note The option has been tested in combination with the CO2STORE keyword, but not for the general case at this point. |\n|-----------------------------------------------------------------------------------------------------------------------|\n| Diffusivity Conversion Factors | | |\n|--------------------------------|-------------------|-----------------|\n| Laboratory Measured Units | Conversion Factor | Simulator Units |\n| 1 cm2/s | 92.9979 ft2/day | Field |\n| 8.64 m2/day | Metric | |\n| 3600 cm2/hour | Laboratory | |","expected_columns":2,"size_kind":"fixed"},"DIFFC":{"name":"DIFFC","sections":["PROPS"],"supported":null,"summary":"The DIFFC keyword defines the molecular weight of the fluids and diffusion coefficients between phases for each PVT region, for when the Molecular Diffusion option has been activated by the DIFFUSE keyword in the RUNSPEC section. This keyword is optional as OPM Flow will automatically calculate the coefficients, as described by Sandve et al.182\n Tor Harald Sandve1, Sarah E. Gasda, Atgeirr Rasmussen, and Alf Birger Rustad. Convective dissolution in field scale CO2 storage simulation using the OPM Flow simulator. Submitted to TCCS 11 – Trondheim Conference on CO2 Capture, Transport and Storage Trondheim, Norway – June 21-23, 2021., if the DIFFC keyword is absent from the input deck. The keyword thus allows one to overwrite the automatically calculated values.","parameters":[{"index":1,"name":"OILMW","description":"OILMW is a real positive number that specifies the molecular weight of the oil in the given PVT region.","units":{"field":"lb/lb-M","metric":"kg/kg-M","laboratory":"gm/gm-M"},"default":"None","value_type":"DOUBLE","dimension":"1"},{"index":2,"name":"GASMW","description":"GASMW is a real positive number that defines the molecular weight of the gas in the given PVT region.","units":{"field":"lb/lb-M","metric":"kg/kg-M","laboratory":"gm/gm-M"},"default":"None","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"GASGASDF","description":"A real positive number that defines the gas in gas diffusion coefficient in the given PVT region.","units":{"field":"ft2/day","metric":"m2/day","laboratory":"cm2/hour"},"default":"None","value_type":"DOUBLE","dimension":"Length*Length/Time"},{"index":4,"name":"OILGASDF","description":"A real positive number that declares the oil in gas diffusion coefficient in the given PVT region.","units":{"field":"ft2/day","metric":"m2/day","laboratory":"cm2/hour"},"default":"None","value_type":"DOUBLE","dimension":"Length*Length/Time"},{"index":5,"name":"GASOILDF","description":"A real positive number that specifies the gas in oil diffusion coefficient in the given PVT region.","units":{"field":"ft2/day","metric":"m2/day","laboratory":"cm2/hour"},"default":"None","value_type":"DOUBLE","dimension":"Length*Length/Time"},{"index":6,"name":"OILOILDF","description":"A real positive number that defines the oil in oil diffusion coefficient in the given PVT region.","units":{"field":"ft2/day","metric":"m2/day","laboratory":"cm2/hour"},"default":"None","value_type":"DOUBLE","dimension":"Length*Length/Time"},{"index":7,"name":"GASOILCD","description":"A real positive number that defines the gas in oil cross phase diffusion coefficient in the given PVT region. This parameter is ignored by OPM Flow and should be defaulted or set equal to zero.","units":{"field":"ft2/day","metric":"m2/day","laboratory":"cm2/hour"},"default":"0.0","value_type":"DOUBLE","dimension":"Length*Length/Time"},{"index":8,"name":"OILOILCD","description":"A real positive number that defines the oil in oil cross phase diffusion coefficient in the given PVT region. This parameter is ignored by OPM Flow and should be defaulted or set equal to zero.","units":{"field":"ft2/day","metric":"m2/day","laboratory":"cm2/hour"},"default":"0.0","value_type":"DOUBLE","dimension":"Length*Length/Time"}],"example":"The example below is based on field units, with NTPVT equal to three on the TABDIMS keyword.\n--\n-- PVT REGION MOLECULAR DIFFUSION TABLES\n--\nDIFFC\n-- OIL GAS GAS IN OIL IN GAS IN OIL IN GAS IN OIL IN\n-- MW MW GAS DF GAS DF OIL DF OIL DF OIL CD OIL CD\n-- ------ ----- ------- ------- ------- ------- ------- ------\n103.20 1.120 1.35E-6 1.05E-7 4.50E-7 1.05E-8 /TAB-1\n102.00 1.130 1.25E-6 1.25E-7 4.80E-7 1.05E-8 /TAB-2\n100.00 1.250 1.22E-6 /TAB-3\nHere the third PVT region has no values for the various oil related diffusion coefficients.\n| Note The option has been tested in combination with the CO2STORE keyword, but not for the general case at this point. |\n|-----------------------------------------------------------------------------------------------------------------------|","expected_columns":8,"size_kind":"fixed"},"DIFFCGAS":{"name":"DIFFCGAS","sections":["PROPS"],"supported":null,"summary":"The DIFFCGAS keyword defines the gas diffusion coefficients assuming the standard mole fraction formulation for each compositional component in the model and for each PVT region, for when the Molecular Diffusion option has been activated by the DIFFUSE keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"CO2DIFF","description":"A real positive number that declares the CO2 or H2 in gas diffusion coefficient in the given PVT region.","units":{"field":"ft2/day","metric":"m2/day","laboratory":"cm2/hour"},"default":"None","value_type":"DOUBLE","dimension":"Length*Length/Time"},{"index":2,"name":"WATDIFF","description":"A real positive number that specifies the water in gas diffusion coefficient in the given PVT region.","units":{"field":"ft2/day","metric":"m2/day","laboratory":"cm2/hour"},"default":"None","value_type":"DOUBLE","dimension":"Length*Length/Time"}],"example":"The example below is based on field units, with NTPVT equal to three on the TABDIMS keyword.\n--\n-- PVT REGION GAS COMPONENT DIFFUSION COEFFICIENTS (OPM FLOW KEYWORD)\n--\nDIFFCGAS\n-- CO2 IN WAT IN\n-- GAS DF GAS DF\n-- ------- -------\n0.160 0.150 / PVT REGION NO. 01\n0.165 0.155 / PVT REGION NO. 02\n/ PVT REGION NO. 03\nHere the third PVT region has no values for the two component diffusion coefficients, and therefore the simulator will use correlations to define the diffusivity coefficients for this PVT region.\n| Note This is an OPM Flow keyword used with OPM Flow’s CO2STORE or H2STORE and GASWAT keywords in the RUNSPEC section, and should not be confused with the more general version of the DIFFCGAS keyword used in the commercial compositional simulator. |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Note The option has been tested in combination with the CO2STORE keyword, but not for the general case at this point. |\n|-----------------------------------------------------------------------------------------------------------------------|\n| Diffusivity Conversion Factors | | |\n|--------------------------------|-------------------|-----------------|\n| Laboratory Measured Units | Conversion Factor | Simulator Units |\n| 1 cm2/s | 92.9979 ft2/day | Field |\n| 8.64 m2/day | Metric | |\n| 3600 cm2/hour | Laboratory | |","expected_columns":2,"size_kind":"fixed"},"DIFFCOAL":{"name":"DIFFCOAL","sections":["PROPS"],"supported":false,"summary":"The DIFF keyword defines the coal bed methane diffusion data for when the Coal Bed Methane option has been activated via the COAL keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"GAS_DIFF_COEFF","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length*Length/Time"},{"index":2,"name":"RE_ADSORB_FRACTION","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"SOL_DIFF_COEFF","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length*Length/Time"}],"example":"","expected_columns":3,"size_kind":"fixed"},"DIFFCWAT":{"name":"DIFFCWAT","sections":["PROPS"],"supported":null,"summary":"The DIFFCWAT keyword defines the water diffusion coefficients assuming the standard mole fraction formulation for each compositional component in the model and for each PVT region, for when the Molecular Diffusion option has been activated by the DIFFUSE keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"CO2DIFF","description":"A real positive number that declares the CO2 or H2 in water diffusion coefficient in the given PVT region.","units":{"field":"ft2/day","metric":"m2/day","laboratory":"cm2/hour"},"default":"None","value_type":"DOUBLE","dimension":"Length*Length/Time"},{"index":2,"name":"WATDIFF","description":"A real positive number that specifies the water in water diffusion coefficient in the given PVT region.","units":{"field":"ft2/day","metric":"m2/day","laboratory":"cm2/hour"},"default":"None","value_type":"DOUBLE","dimension":"Length*Length/Time"}],"example":"The example below is based on field units, with NTPVT equal to three on the TABDIMS keyword.\n--\n-- PVT REGION WATER COMPONENT DIFFUSION COEFFICIENTS (OPM FLOW KEYWORD)\n--\nDIFFCWAT\n-- CO2 IN WAT IN\n-- WAT DF WAT DF\n-- ------- -------\n0.160 0.150 / PVT REGION NO. 01\n0.165 0.155 / PVT REGION NO. 02\n/ PVT REGION NO. 03\nHere the third PVT region has no values for the two component diffusion coefficients, and therefore the simulator will use correlations to define the diffusivity coefficients for this PVT region.\n| Note This is an OPM Flow keyword used with OPM Flow’s CO2STORE or H2STORE and GASWAT keywords in the RUNSPEC section, and should not be confused with the more general version of the DIFFCWAT keyword used in the commercial compositional simulator. |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Note The option has been tested in combination with the CO2STORE keyword, but not for the general case at this point. |\n|-----------------------------------------------------------------------------------------------------------------------|\n| Diffusivity Conversion Factors | | |\n|--------------------------------|-------------------|-----------------|\n| Laboratory Measured Units | Conversion Factor | Simulator Units |\n| 1 cm2/s | 92.9979 ft2/day | Field |\n| 8.64 m2/day | Metric | |\n| 3600 cm2/hour | Laboratory | |","expected_columns":2,"size_kind":"fixed"},"DIFFDP":{"name":"DIFFDP","sections":["PROPS"],"supported":false,"summary":"This keyword, DIFFDP, activates the dual porosity molecular diffusion for matrix-fracture flow only option for when the Dual Porosity option has be activated by either the DUALPORO or DUALPERM keywords, and the Diffusivity option has been activated by the DIFFUSE keywords; three keywords are in the RUNSPEC section.","parameters":[],"example":"","size_kind":"none","size_count":0},"DIFFMICP":{"name":"DIFFMICP","sections":["PROPS"],"supported":null,"summary":"The DIFFMICP keyword defines the diffusion coefficients assuming the mass concentration formulation for each component dissolved in water and for each PVT region, for when the molecular diffusion option has been activated by the DIFFUSE keyword in the RUNSPEC section. The keyword should only be used if either the MICP or BIOFILM model has been activated in the RUNSPEC section.","parameters":[{"index":1,"name":"MICRDIFF","description":"A real positive number that declares the microbial concentration in water diffusion coefficient in the given PVT region.","units":{"field":"ft2/day","metric":"m2/day","laboratory":"cm2/hour"},"default":"None","value_type":"DOUBLE","dimension":["Length*Length/Time","Length*Length/Time","Length*Length/Time"]},{"index":2,"name":"OXYGDIFF","description":"A real positive number that declares the oxygen concentration in water diffusion coefficient in the given PVT region.","units":{"field":"ft2/day","metric":"m2/day","laboratory":"cm2/hour"},"default":"None"},{"index":3,"name":"UREADIFF","description":"A real positive number that declares the urea concentration in water diffusion coefficient in the given PVT region.","units":{"field":"ft2/day","metric":"m2/day","laboratory":"cm2/hour"},"default":"None"}],"example":"The example below is based on metric units, with NTPVT equal to one on the TABDIMS keyword.\n--\n-- PVT REGION MICP COMPONENT DIFFUSION COEFFICIENTS (OPM FLOW KEYWORD)\n--\nDIFFMICP\n-- MICR IN OXYG IN UREA IN\n-- WAT DF WAT DF WAT DF\n-- ------- ------- -------\n2E-04 2E-04 1E-04 / PVT REGION NO. 01\n| Note This is an OPM Flow specific keyword. |\n|--------------------------------------------|","size_kind":"fixed","variadic_record":true},"DIFFMMF":{"name":"DIFFMMF","sections":["GRID","SCHEDULE"],"supported":false,"summary":"This keyword, DIFFMMF, defines the diffusivity multipliers for matrix-fractures for when the Dual Porosity option has be activated by either the DUALPORO or DUALPERM keywords, or the Coal Bed Methane option is selected by the COAL keyword, and the Diffusivity option has been activated by the DIFFUSE keywords; all four keywords are in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"DISPERSE":{"name":"DISPERSE","sections":["PROPS"],"supported":false,"summary":"This keyword, DISPERSE, defines the dispersion tables for when the Dispersion option has been activated via declaring the dimensions of the DISPERSE tables using the DISPDIMS keyword and activating the Tracer option via the TRACERS keyword.","parameters":[{"index":1,"name":"VELOCITY","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length/Time"},{"index":2,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["1","Length*Length/Time"]}],"example":"","size_kind":"list","variadic_record":true},"DPKRMOD":{"name":"DPKRMOD","sections":["PROPS"],"supported":false,"summary":"The DPKRMOD keyword can be used to modify the matrix oil relative permeability data (oil-water, oil-gas) and the scaling of the fracture to matrix relative permeabilities, for dual porosity runs for when a Dual Porosity model has been activated by either the DUALPORO or DUALPERM keywords in the RUNSPEC section.","parameters":[{"index":1,"name":"MOD_OIL_WAT_PERM","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"1"},{"index":2,"name":"MOD_OIL_GAS_PERM","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"SCALE_PERM_FRACTURE","description":"","units":{},"default":"YES","value_type":"STRING"}],"example":"","expected_columns":3,"size_kind":"fixed"},"DSPDEINT":{"name":"DSPDEINT","sections":["PROPS"],"supported":false,"summary":"This keyword, DSPDEINT, activates the brine tracer dispersion interpolation by water density option for when the Brine phase is activated in the model by the BRINE keyword in the RUNSPEC section and the DISPERSE keyword in the PROPS section is in the input file. They keyword cause the lookup and interpolation of the DISPERSE tracer concentration to water density, that is the tracer concentration data on the DISPERSE keyword has been replaced by the water density data.","parameters":[],"example":"","size_kind":"none","size_count":0},"EHYSTR":{"name":"EHYSTR","sections":["PROPS"],"supported":false,"summary":"The EHYSTR keyword defines the hysteresis model and associated parameters when the hysteresis option has been activated by the HYSTER variable on the SATOPTS keyword in the RUNSPEC section. Both the Carlson185\n Carlson, F. M. “Simulation of Relative Permeability Hysteresis to the Non-Wetting Phase,” paper SPE 10157, presented at the SPE Annual Technical Conference & Exhibition, San Antonio, Texas, USA (October 5-7, 1981). and Killough186\n Killough, J. E. “Reservoir Simulation with History-dependent Saturation Functions,” paper SPE 5106, Society of Petroleum Engineers Journal (1976) 16, No. 1, 37-48. models are available.","parameters":[{"index":0,"name":"Carlson Hysteresis Model","description":"SATNUM","units":{},"default":""},{"index":1,"name":"HYSTRCP","description":"HYSTRCP is a positive real value that defines the Killough curvature parameter for capillary pressure hysteresis model. The value should range from 0.05 to 0.10. This item is not supported by OPM Flow and should be defaulted (1*).","units":{},"default":"0.1","value_type":"DOUBLE"},{"index":1,"name":"Carlson Hysteresis Model","description":"IMBNUM","units":{},"default":"","value_type":"DOUBLE"},{"index":2,"name":"HYSTMOD","description":"An integer value that determines the relative permeability hysteresis model to be used depending on the phase and the wettability of the system. HYSTMOD should be set to one of the following values:","units":{"field":"HYSTMOD","metric":"Non-Wetting Phases","laboratory":"Wetting Phase"},"default":"0","value_type":"INT"},{"index":2,"name":"Killough Hysteresis Model","description":"SATNUM","units":{},"default":"","value_type":"INT"},{"index":3,"name":"Killough Hysteresis Model","description":"IMBNUM","units":{},"default":"","value_type":"DOUBLE"},{"index":3,"name":"HYSTREL","description":"HYSTREL is a positive real number that defines the Killough’s wetting phase relative permeability curvature parameter. This parameter is only applicable if HYSMOD is set to either 4 or 7. This item is not supported by OPM Flow and should be defaulted (1*).","units":{},"default":"1.0","value_type":"DOUBLE"},{"index":4,"name":"Killough Hysteresis Model","description":"Killough Hysteresis Model","units":{},"default":"","value_type":"DOUBLE"},{"index":4,"name":"HYSTSGR","description":"HYSTSGR is a positive real number that sets a scaling parameter for the trapped non-wetting phase saturation in the Killough model. This item is not supported by OPM Flow and should be defaulted (1*).","units":{},"default":"0.1","value_type":"DOUBLE"},{"index":5,"name":"Carlson Non- Wetting Modeling for Gas and Water","description":"SATNUM","units":{},"default":"","value_type":"STRING"},{"index":5,"name":"HYSTOPT","description":"A defined character string that determines if the hysteresis model should be activated for relative permeability, capillary pressure, or both, and should be set to one of the following: BOTH:apply hysteresis modeling to both relative permeability, and capillary pressure curves. PC:apply hysteresis modeling to capillary pressure curves only. KR:apply hysteresis modeling to relative permeability curves only.","units":{},"default":"BOTH","value_type":"STRING"},{"index":6,"name":"Killough Non- Wetting Modeling for Gas and Water","description":"SATNUM","units":{},"default":"","value_type":"STRING"},{"index":6,"name":"HYSTSCAN","description":"A defined character string that determines the shape of Killough capillary pressure scanning curves when secondary reversal occurs, that is for a drainage, imbibition, drainage cycle. RETR: Secondary drainage curves re-traverses the same scanning curve. NEW: Secondary drainage curves follows a new scanning curve and further reversals also generate a new scanning curve. Only the RETR option is supported by OPM Flow.","units":{},"default":"RETR","value_type":"STRING"},{"index":7,"name":"Killough Non- Wetting Modeling for Gas and Water","description":"Killough Non- Wetting Modeling for the Wetting Oil Phase","units":{},"default":"","value_type":"STRING"},{"index":7,"name":"HYSTMOB","description":"A defined character string that determines how to apply the mobility control correction invoked by the MOBILE variable on the EQLOPTS keyword in the RUNSPEC section. HYSTMOB should be set to one of the following: DRAIN:Only the drainage curve end-points are modified. BOTH:Both the drainage and imbibition curve end-points are modified. The Mobility Control option is not supported in OPM Flow so this parameter has no effect and will be ignored. This item should be defaulted.","units":{},"default":"DRAIN","value_type":"STRING"},{"index":8,"name":"HYSTWET","description":"A defined character string that sets the wetting phase between oil and gas in three phase systems and should be set to one of the following: OIL: Oil is set as the wetting phase between oil and gas, and the oil relative permeability with respect to gas is determined by HYSTMOD for the wetting phase. GAS: Oil is set as the non-wetting phase between oil and gas, and the oil relative permeability with respect to gas is determined by HYSTMOD for the non-wetting phase. Note for all the above cases the gas relative permeability is always modelled as a non-wetting phase. Note oil is always the wetting phase to gas in two phase systems. This item is not supported by OPM Flow and should be defaulted (1*).","units":{},"default":"OIL","value_type":"STRING"},{"index":9,"name":"HYBAKOIL","description":"Baker model one or model two relative permeability oil phase hysteresis option used in the commercial compositional simulator. This item is not supported by OPM Flow and should be defaulted (1*).","units":{},"default":"NO","value_type":"STRING"},{"index":10,"name":"HYBAKGAS","description":"Baker model one or model two relative permeability gas phase hysteresis option used in the commercial compositional simulator. This item is not supported by OPM Flow and should be defaulted (1*).","units":{},"default":"NO","value_type":"STRING"},{"index":11,"name":"HYBAKWAT","description":"Baker model one or model two relative permeability water phase hysteresis option used in the commercial compositional simulator. This item is not supported by OPM Flow and should be defaulted (1*).","units":{},"default":"NO","value_type":"STRING"},{"index":12,"name":"HYTHRESH","description":"Killough’s hysteresis threshold saturation value used in the commercial compositional simulator. This item is not supported by OPM Flow and should be defaulted (1*).","units":{},"default":"0.0","value_type":"DOUBLE"},{"index":13,"name":"HYSWETRP","description":"Killough’s hysteresis wetting phase modification used in the commercial black-oil simulator. This item is not supported by OPM Flow and should be defaulted (1*).","units":{},"default":"0","value_type":"INT"},{"index":14,"name":"HYSPCSCL","description":"An integer value that determines if capillary pressure scaling should be enabled to correct the construction of the scanning capillary pressure curve. 0: Capillary pressure scaling is disabled. 1: Capillary pressure scaling is enabled. This option is currently disabled by default but this is likely to change as the correction is believed to be a bug fix. For more information see #6383. This is an OPM Flow specific item that is not supported by the commercial simulator.","units":{},"default":"0","value_type":"INT"}],"example":"--\n-- HYSTERESIS MODEL AND PARAMETERS\n--\n-- PC-CUR MODEL RELPERM TRAPPED OPTION SHAPE MOBILIT WET\n-- HYSTRCP HYSTMOD HYSTREL HYSTSGR HYSTOPT HYSTSCAN HYSTMOB HYSTWET\nEHYSTR\n0.1 0 0.1 1* KR 1* 1* 1* /\nThe above example defines the hysteresis model and parameters used in the Norne model. Here the default value is used for the Killough curvature parameter for capillary pressure hysteresis mode, the Carlson hysteresis model is used for the non-wetting phase and SATNUM for the wetting phase, 0.1 is used for Killough’s wetting phase relative permeability curvature parameter (this parameter is ignored because the Carlson model has been selected), the default values for the trapped non-wetting phase saturation in the Killough mode (again, this parameter is ignored because the Carlson model has been selected, and the hysteresis modeling is only applied to relative permeability curves).","expected_columns":14,"size_kind":"fixed","size_count":1},"EHYSTRR":{"name":"EHYSTRR","sections":["PROPS"],"supported":false,"summary":"The EHYSTRR keyword defines the hysteresis model and associated parameters via the drainage SATNUM allocation region array, for when the hysteresis option has been activated by the HYSTER variable on the SATOPTS keyword in the RUNSPEC section. Only the Killough187\n Killough, J. E. “Reservoir Simulation with History-dependent Saturation Functions,” paper SPE 5106, Society of Petroleum Engineers Journal (1976) 16, No. 1, 37-48. model is available for this keyword and the keyword is optional.","parameters":[{"index":1,"name":"HYSTRCP","description":"HYSTRCP is a positive real value that defines the Killough curvature parameter for capillary pressure hysteresis model. The value should range from 0.05 to 0.10.","units":{},"default":"0.1","value_type":"DOUBLE"},{"index":2,"name":"HYSTREL","description":"HYSTREL is a positive real number that defines the Killough’s wetting phase relative permeability curvature parameter. This parameter is ignored if HYSMOD on the EHYSTR keyword is not set to 4.","units":{},"default":"1.0","value_type":"DOUBLE"},{"index":3,"name":"HYSTSGR","description":"HYSTSGR is a positive real number that sets a scaling parameter for the trapped non-wetting phase saturation in the Killough model.","units":{},"default":"0.1","value_type":"DOUBLE"}],"example":"--\n-- HYSTERESIS MODEL AND PARAMETERS VIA SATNUM\n--\n-- PC-CUR RELPERM TRAPPED\n-- HYSTRCP HYSTREL HYSTSGR\nEHYSTRR\n0.04 1.0 1* / SATNUM REGION 1\n0.06 1.0 1* / SATNUM REGION 2\n0.08 1.0 1* / SATNUM REGION 3\n0.10 1.0 1* / SATNUM REGION 4\n0.10 1.0 1* / SATNUM REGION 5\nThe above example defines the hysteresis model and parameters for when NTSFUN equals five on the TABDIMS keyword in the RUNSPEC section, that is for five SATNUM regions.","expected_columns":3,"size_kind":"fixed"},"ENKRVD":{"name":"ENKRVD","sections":["PROPS"],"supported":false,"summary":"This keyword defines the maximum oil, gas, and water relative permeability values versus depth for the three phases and for when the end-point scaling option has been invoked by the ENDSCALE keyword in the RUNSPEC section. This functionality is not supported in OPM Flow.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"-1","value_type":"DOUBLE","dimension":["Length","1","1","1","1","1","1","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"ENPCVD":{"name":"ENPCVD","sections":["PROPS"],"supported":false,"summary":"This keyword defines the maximum gas-oil and water-oil capillary pressure values versus depth for when the end-point scaling option has been invoked by the ENDSCALE keyword in the RUNSPEC section","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"-1","value_type":"DOUBLE","dimension":["Length","Pressure","Pressure"]}],"example":"","size_kind":"fixed","variadic_record":true},"ENPTVD":{"name":"ENPTVD","sections":["PROPS"],"supported":false,"summary":"This keyword defines the variation of the relative permeability saturation end-points (SWL, SWCR, etc.) for all three phases versus depth for when the end-point scaling option has been invoked by the ENDSCALE keyword in the RUNSPEC section. This functionality is not supported in OPM Flow.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"-1","value_type":"DOUBLE","dimension":["Length","1","1","1","1","1","1","1","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"ENSPCVD":{"name":"ENSPCVD","sections":["PROPS"],"supported":false,"summary":"This keyword defines the variation of the capillary pressure saturation end-points, connate gas (SGL) and connate water (SWL), versus depth for when the end-point scaling option has been invoked by the ENDSCALE keyword in the RUNSPEC section. This functionality is not supported in OPM Flow.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"-1","value_type":"DOUBLE","dimension":["Length","1","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"EPSDBGS":{"name":"EPSDBGS","sections":["PROPS","SCHEDULE"],"supported":false,"summary":"This keyword, EPSDBGS, defines the end-point debug data for multiple grid blocks that should be written to the DEBUG file (*.DBG) for when the End-Point Scaling option has been activated by the ENDSCALE keyword in the RONSPEC section.","parameters":[{"index":1,"name":"TABLE_OUTPUT","description":"","units":{},"default":"0","value_type":"INT","record":1},{"index":2,"name":"CHECK_DRAIN_HYST","description":"","units":{},"default":"0","value_type":"INT","record":1},{"index":1,"name":"IX1","description":"","units":{},"default":"","value_type":"INT","record":2},{"index":2,"name":"IX2","description":"","units":{},"default":"","value_type":"INT","record":2},{"index":3,"name":"JY1","description":"","units":{},"default":"","value_type":"INT","record":2},{"index":4,"name":"JY2","description":"","units":{},"default":"","value_type":"INT","record":2},{"index":5,"name":"KZ1","description":"","units":{},"default":"","value_type":"INT","record":2},{"index":6,"name":"KZ2","description":"","units":{},"default":"","value_type":"INT","record":2},{"index":7,"name":"GRID_NAME","description":"","units":{},"default":"","value_type":"STRING","record":2}],"example":"","records_meta":[{"expected_columns":2},{"expected_columns":7}],"size_kind":"list"},"EPSDEBUG":{"name":"EPSDEBUG","sections":["PROPS","SCHEDULE"],"supported":false,"summary":"This keyword, EPSDEBUG, defines the end-point debug data for individual grid blocks that should be written to the Debug file (*.DBG) for when the End-Point Scaling option has been activated by the ENDSCALE keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"IX1","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"IX2","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"JY1","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"JY2","description":"","units":{},"default":"","value_type":"INT"},{"index":5,"name":"KZ1","description":"","units":{},"default":"","value_type":"INT"},{"index":6,"name":"KZ2","description":"","units":{},"default":"","value_type":"INT"},{"index":7,"name":"TABLE_OUTPUT","description":"","units":{},"default":"0","value_type":"INT"},{"index":8,"name":"GRID_NAME","description":"","units":{},"default":"","value_type":"STRING"},{"index":9,"name":"CHECK_DRAIN_HYST","description":"","units":{},"default":"0","value_type":"INT"}],"example":"","expected_columns":9,"size_kind":"fixed","size_count":1},"ESSNODE":{"name":"ESSNODE","sections":["PROPS"],"supported":false,"summary":"This keyword, ESSNODE, defines the salt concentration data that is used in calculating the water-oil surface tension for when the Brine option has been activated by the BRINE keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Density"]}],"example":"","size_kind":"fixed","variadic_record":true},"FHERCHBL":{"name":"FHERCHBL","sections":["PROPS"],"supported":false,"summary":"The FHERCHBL keyword defines Herschel-Bulkley rheological property data for Non-Newtonian fluids versus polymer concentration, for when the Polymer option has been invoked via the POLYMER keyword in the RUNSPEC section and Non-Newtonian Fluid phase has been declared active by the NNEWTF keyword, also in the RUNSPEC section.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Density","1","1","Pressure"]}],"example":"","size_kind":"fixed","variadic_record":true},"FILLEPS":{"name":"FILLEPS","sections":["PROPS"],"supported":null,"summary":"This keyword switches on the export of the saturation end-point data (SWL, SWCR, SOWCR array etc.) to the *.INIT file so that the data can be viewed in post-processing software like OPM ResInsight.","parameters":[],"example":"--\n-- ACTIVATE SATURATION END-POINT EXPORT TO THE INIT FILE\n--\nFILLEPS\nThe above example switches on the export of the end-point saturation data to the *.INIT file.","size_kind":"none","size_count":0},"FOAMADS":{"name":"FOAMADS","sections":["PROPS"],"supported":null,"summary":"The FOAMADS keyword defines the foam rock adsorption tables for when the Foam option has been activated by the FOAM keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"FOAMCON","description":"A columnar vector of real monotonically increasing down the column values that defines the foam concentration in the solution surrounding the rock. The first entry should be zero to define a no foam concentration data set. Units are dependent on the transport phase specified via the FOAMOPT1 variable on the FOAMOPTS keywod in the PROPS section.","units":{"field":"Gas: lb/Mscf Water: lb/stb","metric":"Gas: kg/sm3 Water: kg/sm3","laboratory":"Gas: gm/scc Water: gm/scc"},"default":"None","value_type":"DOUBLE","dimension":["FoamDensity","1"]},{"index":2,"name":"FOAMRATI","description":"A columnar vector of real increasing down the column values that defines the mass of adsorbed foam per unit mass of rock for a given FOAMCON. The first table data set entry should be zero to define a no foam concentration data set.","units":{"field":"lb/lb","metric":"kg/kg","laboratory":"gm/gm"},"default":"None"}],"example":"--\n-- FOAM ROCK ADSORPTION TABLE\n--\nFOAMADS\n-- FOAM FOAM\n-- FOAMCON FOAMRATI\n-- ------- --------\n0.0 0.00000\n2.0 0.00003\n4.0 0.00005\n6.0 0.00007\n8.0 0.00009\n10.0 0.00011\n12.0 0.00012\n14.0 0.00015 / TABLE NO. 01\n-- FOAM FOAM\n-- FOAMCON FOAMRATI\n-- ------- --------\n0.0 0.00000\n3.0 0.00004\n5.0 0.00006\n7.0 0.00008\n8.0 0.00009\n10.0 0.00011 / TABLE NO. 02\nThe above example defines two foam rock adsorption tables assuming NTSFUN equals two and NSSFUN is greater than or equal to eight on the TABDIMS keyword in the RUNSPEC section.","size_kind":"fixed","variadic_record":true},"FOAMDCYO":{"name":"FOAMDCYO","sections":["PROPS"],"supported":false,"summary":"The FOAMDCYO keyword defines the foam decay half-life versus oil saturation for when the Foam option has been activated by the FOAM keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["1","Time"]}],"example":"","size_kind":"fixed","variadic_record":true},"FOAMDCYW":{"name":"FOAMDCYW","sections":["PROPS"],"supported":false,"summary":"The FOAMDCYW keyword defines the foam decay half-life versus water saturation for when the Foam option has been activated by the FOAM keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["1","Time"]}],"example":"","size_kind":"fixed","variadic_record":true},"FOAMFCN":{"name":"FOAMFCN","sections":["PROPS"],"supported":false,"summary":"The FOAMFCN keyword defines the reduction in gas mobility versus capillary number, for when the Foam option has been activated by the FOAM keyword in the RUNSPEC section, and the FOAMOPT2 parameter on the FOAMOPTS keyword in the PROPS section has been set to the character string FUNC.","parameters":[{"index":1,"name":"CAPILLARY_NUMBER","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":2,"name":"EXP","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"}],"example":"","expected_columns":2,"size_kind":"fixed"},"FOAMFRM":{"name":"FOAMFRM","sections":["PROPS"],"supported":false,"summary":"The FOAMFRM keyword defines the reduction in gas mobility versus the reference mobility reduction factor, for when the Foam option has been activated by the FOAM keyword in the RUNSPEC section, and the FOAMOPT2 parameter on the FOAMOPTS keyword in the PROPS section has been set to the character string FUNC.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["1"]}],"example":"","size_kind":"fixed","variadic_record":true},"FOAMFSC":{"name":"FOAMFSC","sections":["PROPS"],"supported":null,"summary":"The FOAMFSC keyword defines the reduction in gas mobility as a function of the foam surfactant concentration within a grid block. The Foam option must be activated by the FOAM keyword in the RUNSPEC section in order to use this keyword. In addition, the FOAMOPT2 parameter on the FOAMOPTS keyword in the PROPS section must be set to the character string FUNC, in order to activate the functional form of the gas mobility reduction calculations.","parameters":[{"index":1,"name":"FOAMCON","description":"A real positive value that defines the foam surfactant concentration at which foam modeling becomes active in the model and a strong foam is formed. FOAMCON cannot be defaulted and must be specified for the first table. Subsequent tables can be defaulted and will in this case use the previous tables’ entries as the default value.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None","value_type":"DOUBLE","dimension":"Concentration"},{"index":2,"name":"FOAMEXP","description":"A real positive value that defines an exponent that determines the gradient in the change of the reduction in gas mobility due to foam (es in equation (8.51). Note if es is less than one then the slope of Fs in equation (8.51)will be infinite at Cs equal to zero. In this case, small surfactant concentrations have a significant effect on the mobility, especially if the reference concentration Csr is also small. If this is the case use MINSURF on this keyword to set a minimum surfactant concentration to avoid small-scale numerical errors from affecting the simulation.","units":{"field":"dimensionless 1.0","metric":"dimensionless 1.0","laboratory":"dimensionless 1.0"},"default":"Defined","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"MINSURF","description":"MINSURF is a real positive value that defines the minimum surfactant concentration for which the reduction in gas mobility will be calculated. The default value of 1 x 10-20 implies that there is no minimum","units":{"field":"lb/stb 1 x 10-20","metric":"kg/sm3 1 x 10-20","laboratory":"gm/scc 1 x 10-20"},"default":"Defined","value_type":"DOUBLE","dimension":"Concentration"},{"index":4,"name":"MINSWAT","description":"MINSWAT is a real positive value less than 1.0 that sets the minimum water saturation below which foam has no effect. The default value of 1 x 10-6 implies that there is no minimum. Note that this parameter is only used in the commercial simulator’s compositional simulator and is therefore not used by OPM Flow or the commercial simulators black-oil simulator.","units":{"field":"dimensionless 1 x 10-6","metric":"dimensionless 1 x 10-6","laboratory":"dimensionless 1 x 10-6"},"default":"Defined","value_type":"DOUBLE","dimension":"1"}],"example":"--\n-- FOAM GAS MOBILITY VERSUS SURFACTANT CONCENTRATION FUNCTIONS\n--\nFOAMFSC\n-- FOAM FOAM FOAM FOAM\n-- FOAMCON FOAMEXP MINSURF MINSWAT\n-- ------- ------- ------- -------\n0.001 1.010 / TABLE NO. 01\n0.002 1.000 / TABLE NO. 02\n/ TABLE NO. 03 (DEFAULTED)\n0.001 0.850 1.0E-10 / TABLE NO. 04\n0.002 1.030 / TABLE NO. 05\n0.002 1.000 / TABLE NO. 06\nHere, NTSFUN equals six on the TABDIMS keyword in the RUNSPEC section and therefore six entries are required for the FOAMFSC keyword. Table number three is completed defaulted and will therefore use all the properties from the previous table, that is table number two.\n| [F sub{s}`=`left({C sub{s}} over{C sup{r} sub{s} }right) sup{e sub{s}}] | (8.51) |\n|-------------------------------------------------------------------------|--------|\n| [M sub{ rf}`=` 1 over{ 1 ` +` left( M sub{r} `times` F sub{s} `times` F sub{w} `times` F sub{o} `times` F sub{c} right)}] | (8.52) |\n|---------------------------------------------------------------------------------------------------------------------------|--------|","expected_columns":4,"size_kind":"fixed"},"FOAMFSO":{"name":"FOAMFSO","sections":["PROPS"],"supported":false,"summary":"The FOAMFSO keyword defines the reduction in gas mobility versus oil saturation, for when the Foam option has been activated by the FOAM keyword in the RUNSPEC section, and the FOAMOPT2 parameter on the FOAMOPTS keyword in the PROPS section has been set to the character string FUNC.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["1","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"FOAMFST":{"name":"FOAMFST","sections":["PROPS"],"supported":false,"summary":"The FOAMFST keyword defines the gas-water surface tension versus the foam surfactant concentration, for when the Foam option has been activated by the FOAM keyword in the RUNSPEC section, and the FOAMOPT2 parameter on the FOAMOPTS keyword in the PROPS section has been set to the character string FUNC.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["FoamDensity","SurfaceTension"]}],"example":"","size_kind":"fixed","variadic_record":true},"FOAMFSW":{"name":"FOAMFSW","sections":["PROPS"],"supported":false,"summary":"The FOAMFRM keyword defines the reduction in gas mobility versus water saturation, for when the Foam option has been activated by the FOAM keyword in the RUNSPEC section, and the FOAMOPT2 parameter on the FOAMOPTS keyword in the PROPS section has been set to the character string FUNC.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["1","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"FOAMMOB":{"name":"FOAMMOB","sections":["PROPS"],"supported":null,"summary":"The FOAMMOB keyword defines the reduction in gas mobility as a function of the foam concentration within a grid block. The Foam option must be activated by the FOAM keyword in the RUNSPEC section in order to use this keyword. In addition, this keyword must be supplied if the foam model is activated.","parameters":[{"index":1,"name":"FOAMCON","description":"A columnar vector of real monotonically increasing down the column values that defines the foam concentration for the corresponding gas mobility reduction factor (FOAMRATI). The first entry should be zero to define a no foam concentration data set. Units are dependent on the transport phase specified via the FOAMOPT1 variable on the FOAMOPTS keyword in the PROPS section. FOAMOPT1 should be set to either GAS or WATER.","units":{"field":"Gas: lb/Mscf Water: lb/stb","metric":"Gas: kg/sm3 Water: kg/sm3","laboratory":"Gas: gm/scc Water: gm/scc"},"default":"None","value_type":"DOUBLE","dimension":["FoamDensity","1"]},{"index":2,"name":"FOAMRATI","description":"A columnar vector of real decreasing down the column values that defines the corresponding gas mobility reduction factor for a given FOAMCON. The first table data set entry should be one to define a no foam concentration data set. Each FOAMCON/FOAMRATI data set should be terminated by a “/”","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- FOAM GAS MOBILITY VERSUS FOAM CONCENTRATION TABLES\n--\nFOAMMOB\n-- FOAM FOAM\n-- FOAMCON FOAMRATI\n-- ------- --------\n0.000 1.00000\n0.005 0.50000\n0.010 0.20000\n0.015 0.10000\n0.020 0.07500\n0.025 0.07000\n0.030 0.06500\n0.035 0.06500 / TABLE NO. 01\n-- FOAM FOAM\n-- FOAMCON FOAMRATI\n-- ------- --------\n0.000 1.00000\n0.010 0.50000\n0.015 0.25000\n0.020 0.07500\n0.025 0.07000\n0.030 0.07000 / TABLE NO. 02\nGiven NTPVT equals two and NPPVT is greater and or equal to eight on the TABDIMS keyword in the RUNSPEC section, the example defines the foam gas mobility versus foam concentration tables for two tables.\nThere is no terminating “/” for this keyword.","size_kind":"fixed","variadic_record":true},"FOAMMOBP":{"name":"FOAMMOBP","sections":["PROPS"],"supported":false,"summary":"The FOAMMOBP keyword defines the reduction in foam mobility reduction versus oil pressure, for when the Foam option has been activated by the FOAM keyword in the RUNSPEC.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Pressure","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"FOAMMOBS":{"name":"FOAMMOBS","sections":["PROPS"],"supported":false,"summary":"The FOAMMOBS keyword defines the reduction in foam mobility reduction versus shear, for when the Foam option has been activated by the FOAM keyword in the RUNSPEC.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Length/Time","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"FOAMOPTS":{"name":"FOAMOPTS","sections":["PROPS"],"supported":true,"summary":"The FOAMOPTS keyword defines the transport phase for the foam (gas, water or solvent) and how gas mobility reduction should be calculated for when the Foam option has been activated by the FOAM keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"FOAMOPT1","description":"A defined character string that specifies the transport phase for the foam, and should be set to one of the following: GAS: for the foam to be transport in the gas phase., WATER: for the foam to be transported in the water phase, or SOLVENT: for the foam to be transported in the solvent phase.","units":{},"default":"GAS","value_type":"STRING","options":["GAS","WATER","SOLVENT"]},{"index":2,"name":"FOAMOPT2","description":"A defined character string that specifies the method to be used to calculate the reduction in gas mobility, and should be set to one of the following: TAB: Sets the reduction in gas mobility is to be calculated based on tables using the FOAMMOB keyword as a function of foam concentration, the FOAMMOBS keyword as a function of shear, or as a function of pressure using the FOAMMOBP keyword. All keywords are in the PROPS section. FUNC: Sets the reduction in gas mobility to be calculated based on a function defined via the FOAMFRM, FOAMFSC, FOAMFSW, FOAMFSO, FOAMFCN, or FOAMFST keywords in the PROPS section. Only the default value of TAB is currently supported by OPM Flow.","units":{},"default":"TAB","value_type":"STRING"}],"example":"--\n-- FOAMOPT1 FOAMOPT2\n-- PHASE MOBILITY\n-- -------- --------\nFOAMOPTS\nGAS TAB / FOAM MODEL OPTIONS\nThe above example defines the transport phase is to be gas and the gas mobility reduction is to use a table as defined by the FOAMMOB keyword as a function of foam concentration, the FOAMMOBS keyword as a function of shear, or as a function of pressure using the FOAMMOBP keyword.","expected_columns":2,"size_kind":"fixed","size_count":1},"FOAMROCK":{"name":"FOAMROCK","sections":["PROPS"],"supported":true,"summary":"The FOAMROCK keyword defines the foam rock properties for when the Foam option has been activated by the FOAM keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"ADINDX","description":"A positive integer of 1 or 2 that defines foam desorption option, as per: then foam desorption may occur by retracing the foam adsorption isotherm when the local foam concentration in the solution decreases. then no foam desorption may occur. Only the default value of 1 is supported by OPM Flow.","units":{"field":"dimensionless 1","metric":"dimensionless 1","laboratory":"dimensionless 1"},"default":"Defined","value_type":"INT"},{"index":2,"name":"DENSITY","description":"A real value that defines the rock in situ density, that is at reservoir conditions.","units":{"field":"lb/rb","metric":"kg/rm3","laboratory":"gm/rcc"},"default":"None","value_type":"DOUBLE","dimension":"Density"}],"example":"--\n-- FOAM-ROCK PROPERTIES\n--\nFOAMROCK\n-- DESORP INSITU\n-- OPTN DENSITY\n-- ------ -------\n1 1800.0 / TABLE NO. 01\n2 1980.0 / TABLE NO. 02\n1 2005.0 / TABLE NO. 03\nThe above example defines three foam-rock tables, based on the NTSFUN variable on the TABDIMS keyword in the RUNSPEC section being equal to three.\nThere is no terminating “/” for this keyword.\n| Note In the commercial simulator if the POLYMER and SURFACT phases have been activated in conjunction with the FOAM phase then the mass density of rock will be set by the PLYROCK, SURFROCK, or the FOAMROCK keywords depending on the order entered in the run deck. This is not the case for OPM Flow. OPM Flow’s FOAM phase is a standalone implementation and cannot be used in conjunction with the either the POLYMER or SURFACT phases. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":2,"size_kind":"fixed"},"GASDENT":{"name":"GASDENT","sections":["PROPS"],"supported":null,"summary":"GASDENT defines the gas density as a function of temperature coefficients for when OPM Flow’s thermal option has been activated by the THERMAL keyword in the RUNSPEC. Note this is an OPM Flow keyword used with OPM Flow’s black-oil thermal model that is not available in the commercial simulator’s black-oil thermal formulation.","parameters":[{"index":1,"name":"TEMP","description":"TEMP is a real positive value greater than zero that defines the absolute reference temperature used with TEXP1 and TEXP2 to estimate the change in gas density with respect to temperature.","units":{"field":"oR 527.67","metric":"oK 293.15","laboratory":"oK 293.15"},"default":"Defined","value_type":"DOUBLE","dimension":"AbsoluteTemperature"},{"index":2,"name":"TEXP1","description":"TEXP1 is a real positive value greater than zero that defines the gas thermal expansion coefficient of the first order.","units":{"field":"1/oR 1.67 x 10-4","metric":"1/oK 3.0 x 10-4","laboratory":"1/oK 3.0 x 10-4"},"default":"Defined","value_type":"DOUBLE","dimension":"1/AbsoluteTemperature"},{"index":3,"name":"TEXP2","description":"TEXP2 is a real positive value greater than zero that defines the gas thermal expansion coefficient of the second order.","units":{"field":"1/oR2 9.26 x 10-7","metric":"1/oK2 3.0 x 10-6","laboratory":"1/oK2 3.0 x 10-6"},"default":"Defined","value_type":"DOUBLE","dimension":"1/AbsoluteTemperature*AbsoluteTemperature"}],"example":"The following example shows the GASDENT keyword using the default values, for when the thermal option has been activated by the THERMAL keyword in the RUNSPEC section and for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set to two.\n--\n-- GAS DENSITY TEMPERATURE COEFFICIENTS (OPM FLOW THERMAL KEYWORD)\n--\n-- GAS DENSITY DENSITY\n-- TEMP COEFF1 COEFF2\n-- -------- ------- -------\nGASDENT\n1* 1* 1* / TABLE NO. 01\n1* 1* 1* / TABLE NO. 02\nThere is no terminating “/” for this keyword.\n| [%rho_g( p, T ) = %rho_g( p_s, T_s ) b_g( p, T )] | (8.3.73.1) |\n|---------------------------------------------------|------------|\n| [b_g( p, T ) = { b_g( p, T_ref ) } over { 1 + c_1 ( T - T_ref ) + c_2 ( T - T_ref )^2 }] | (8.3.73.2) |\n|------------------------------------------------------------------------------------------|------------|","expected_columns":3,"size_kind":"fixed"},"GASJT":{"name":"GASJT","sections":["PROPS"],"supported":null,"summary":"GASJT activates the gas Joule-Thomson188\n Natural Gas Engineering (McGraw-Hill chemical engineering series), Donald L. Katz, Robert l Lee, McGraw-Hill Education, 1990 (ISBN 0071007776, 9780071007771). effect in temperature calculations, and defines the gas Joule-Thomson Coefficient (“JTC”) at a given reference pressure, for when OPM Flow’s thermal option has been activated by the THERMAL keyword in the RUNSPEC.","parameters":[{"index":1,"name":"PRESS","description":"A real positive value that defines the reference pressure for the corresponding Joule-Thomson Coefficient, GASJTC.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":"Pressure"},{"index":2,"name":"GASJTC","description":"GASJTC is a real positive or negative value that defines the gas phase Joule-Thomson Coefficient. If the value is defaulted (1*) or set to 0, then GASJTC is internally calculated using the thermal gas density data on the GASDENT keyword in the PROPS section. If a non-zero value is specified, then the GASJTC is assumed to be constant and equal to that value.","units":{"field":"oF/psia","metric":"oC/barsa","laboratory":"oC/atma"},"default":"0","value_type":"DOUBLE","dimension":"AbsoluteTemperature/Pressure"}],"example":"The following example shows the GASJT keyword for when the thermal option has been activated by the THERMAL keyword in the RUNSPEC section, and for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set equal to two.\n--\n-- GAS JOULE-THOMSON COEFFICIENT (OPM FLOW EXTENSION KEYWORD)\n--\n-- REF GAS\n-- PRESS JTC\n-- -------- -------\nGASJT\n20.0 1* / TABLE NO. 01\n20.0 0.50 / TABLE NO. 02\nHere the first entry is defaulted, and the simulator will therefore calculate the gas JTC internally using the data on the GASDENT keyword in the PROPS section.\nThere is no terminating “/” for this keyword.\n| Note This is an OPM Flow keyword used with OPM Flow’s black-oil thermal model, that is not available in the commercial simulator’s black-oil thermal formulation. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| [%eta` `=`` left({ partial T} over {partial P} right)] | (8.53) |\n|--------------------------------------------------------|--------|\n| [%eta ``=`` RT^2 over Pc_p left({ partial Z} over {partial T} right) _P] | (8.54) |\n|--------------------------------------------------------------------------|--------|","expected_columns":2,"size_kind":"fixed"},"GASVISCT":{"name":"GASVISCT","sections":["PROPS"],"supported":null,"summary":"GASVISCT defines the gas viscosity as a function of temperature for when OPM Flow’s thermal option has been activated by the THERMAL keyword in the RUNSPEC. The reference pressure for this table is given by the VISCREF keyword in the PROPS section. Note this is an OPM Flow keyword used with OPM Flow’s black-oil thermal model that is not available in the commercial simulator’s black-oil thermal formulation. However, the keyword and similar functionality is available in the commercial compositional simulator.","parameters":[{"index":1,"name":"TEMP","description":"A columnar vector of real monotonically increasing down the column values that defines the temperature values.","units":{"field":"oF","metric":"oC","laboratory":"oC"},"default":"None","value_type":"DOUBLE","dimension":["Temperature","Viscosity"]},{"index":2,"name":"VIS","description":"A columnar vector of real increasing down the column values that defines the gas viscosity for the corresponding temperature values (TEMP). VIS should be given at the reference pressure defined by the PRESS variable on the VISCREF keyword.","units":{"field":"cP","metric":"cP","laboratory":"cP"},"default":"None"}],"example":"The following example shows the GASVISCT keyword for when the thermal option has been activated by the THERMAL keyword in the RUNSPEC section and for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set equal to one.\n--\n-- GAS VISCOSITY VERSUS TEMPERATURE TABLES (OPM FLOW EXTENSION KEYWORD)\n--\n-- GAS GAS\n-- TEMP VISC\n-- -------- -------\nGASVISCT\n100.0 0.0500\n110.0 0.0550\n120.0 0.0580\n150.0 0.0620\n165.0 0.0625 / TABLE NO. 01\nThere is no terminating “/” for this keyword.","size_kind":"fixed","variadic_record":true},"GIALL":{"name":"GIALL","sections":["PROPS"],"supported":false,"summary":"The GIALL keyword defines the GI values and the associated RVGI, RSGI, BGGI and BOGI values as a function of pressure, for when the GI Pseudo Compositional option has been activated in the model via the GIMODEL keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"PRESSURE","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":2,"name":"TABLE","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["1","1","1","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"GINODE":{"name":"GINODE","sections":["PROPS"],"supported":false,"summary":"The GINODE keyword defines the Gi node values used when the GIMODEL keyword in the RUNSPEC section has been used to activate the GI Pseudo Compositional option for the run. The keyword is used in conjunction with the RSGI, RVGI, BGGI and BOGI keywords in the PROPS section to describe the fluid properties for the GI Pseudo Compositional option.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["1"]}],"example":"","size_kind":"fixed","variadic_record":true},"GRAVCONS":{"name":"GRAVCONS","sections":["PROPS"],"supported":false,"summary":"The GRAVCONS keyword re-defines the gravity constant used in various calculations from the default value used by the simulator. Normally this keyword should not be used.","parameters":[{"index":1,"name":"GRAVCONS","description":"GRAVCONS is a positive real number number that defines the gravity constant used in various calculations.","units":{"field":"ft2psi/lb 0.00694","metric":"m2bars/kg 0.0000981","laboratory":"cm2atm/gm 0.000968"},"default":"Defined","value_type":"DOUBLE","dimension":"Length*Length*Pressure/Mass"}],"example":"--\n-- RE-DEFINE GRAVITY CONSTANT\n--\nGRAVITY\n0.0000980665 /\nThe above example re-defines the gravity constant to be 0.0000980665 ft2psi/lb from the default value of 0.00694 ft2psi/lb.","expected_columns":1,"size_kind":"list"},"GRAVITY":{"name":"GRAVITY","sections":["PROPS"],"supported":null,"summary":"GRAVITY defines the oil API gravity and water and gas surface specific gravities for the fluids for various regions in the model. The number of GRAVITY vector data sets is defined by the NTPVT parameter on the TABDIMS keyword in the RUNSPEC section and the allocation of the GRAVITY data sets to different grid blocks in the model is done via the PVTNUM keyword in the REGION section. One data set consists of one record or line which is terminated by a “/”.","parameters":[{"index":1,"name":"OILAPI","description":"OILAPI is a real number defining the API gravity of the oil phase at surface conditions. The American Petroleum Institute (“API”) classifies oils based on an API gravity (γAPI), or degrees API (oAPI), the relationship between relative density (γo) of oil and API gravity (γAPI) is given by: [%gamma SUB { API } ~ = ~ { 141.5 } OVER { %gamma SUB { o }}~-~ 131.5]","units":{"field":"oAPI","metric":"oAPI","laboratory":"oAPI"},"default":"None","value_type":"DOUBLE","dimension":"1"},{"index":2,"name":"WATGRAV","description":"WATGRAV is a real number defining the specific gravity of the water phase relative to pure water at surface conditions.","units":{"field":"(water =1.0) 0.7773","metric":"(water =1.0) 0.7773","laboratory":"(water =1.0) 0.7773"},"default":"Defined","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"GASGRAV","description":"GASGRAV is a real number defining the specific gravity of the gas phase relative to air at surface conditions.","units":{"field":"(air =1.0) 1.000","metric":"(air =1.0) 1.000","laboratory":"(air =1.0) 1.000"},"default":"Defined","value_type":"DOUBLE","dimension":"1"}],"example":"The following shows the GRAVITY keyword for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set to one.\n--\n-- OIL WAT GAS\n-- GRAVITY GRAVITY GRAVITY\n-- ------- ------- -------\nGRAVITY\n39.0 1.012 0.650 / GRAVITY PVT DATA REGION 1\nThe next example shows the GRAVITY keyword for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set to three.\n--\n-- OIL WAT GAS\n-- GRAVITY GRAVITY GRAVITY\n-- ------- ------- -------\nGRAVITY\n37.0 1.012 0.650 / GRAVITY PVT DATA REGION 1\n38.0 1.012 0.646 / GRAVITY PVT DATA REGION 2\n39.0 1.012 0.640 / GRAVITY PVT DATA REGION 3\nThe third and final example shows the GRAVITY keyword for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set to four. Here table two defaults to table one, and table four defaults to table three.\n--\n-- OIL WAT GAS\n-- GRAVITY GRAVITY GRAVITY\n-- ------- ------- -------\nGRAVITY\n37.0 1.012 0.650 / GRAVITY PVT DATA REGION 1\n/ GRAVITY PVT DATA REGION 2\n38.0 1.012 0.646 / GRAVITY PVT DATA REGION 3\n/ GRAVITY PVT DATA REGION 4\nAgain, note that there is no terminating “/” for this keyword.","expected_columns":3,"size_kind":"fixed"},"GSF":{"name":"GSF","sections":["PROPS"],"supported":null,"summary":"The GSF keyword defines the gas relative permeability and gas-water capillary pressure data versus gas saturation tables for when only gas and water are present in the input deck. This keyword should only be used if the gas and water phases are present in the run, and can therefore also be used with the CO2STORE and H2STORE models. In addition, the keyword must be used in conjunction with the WSF keyword in the PROPS section, that defines the water relative permeability versus water saturation for gas-water systems.","parameters":[{"index":1,"name":"SGAS","description":"A columnar vector of real values monotonically increasing down the column starting from zero and terminating at one minus the connate water saturation, that defines the gas saturation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":["1","1","Pressure"]},{"index":2,"name":"KRG","description":"A columnar vector of real values that are either equal or increasing down the column and that are greater than or equal to zero and less than or equal to one that defines the gas relative permeability. Note that the first entry in the column must be zero.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":3,"name":"PCWG","description":"A columnar vector of real values that are either equal or increasing down the column that defines the gas-water capillary pressure.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"None"}],"example":"--\n-- GAS RELATIVE PERMEABILITY TABLES (OPM FLOW KEYWORD)\n--\nGSF\n-- SGAS KRG PCGW\n-- FRAC PSIA\n-- -------- -------- -------\n0.00 0.0000 0.0\n0.05 0.0000 0.0\n0.10 0.0000 0.0\n0.15 0.0000 0.0\n0.20 0.0002 0.0\n0.25 0.0010 0.0\n0.30 0.0062 0.0\n0.35 0.0140 0.0\n0.40 0.0273 0.0\n0.45 0.0450 0.0\n0.50 0.0707 0.0\n0.55 0.1020 0.0\n0.60 0.1412 0.0\n0.65 0.1870 0.0\n0.70 0.2412 0.0\n0.77 0.3288 0.0\n0.82 0.4000 0.0\n0.85 0.4450 0.0 / TABLE NO. 01\n-- SGAS KRG PCGW\n-- FRAC PSIA\n-- -------- -------- -------\n0.00 0.0000 0.0\n0.05 0.0000 0.0\n0.10 0.0000 0.0\n0.15 0.0000 0.0\n0.20 0.0002 0.0\n0.25 0.0010 0.0\n0.30 0.0062 0.0\n0.35 0.0140 0.0\n0.40 0.0273 0.0\n0.45 0.0450 0.0\n0.50 0.0707 0.0\n0.55 0.1020 0.0\n0.60 0.1412 0.0\n0.65 0.1870 0.0\n0.70 0.2412 0.0\n0.77 0.3288 0.0\n0.82 0.4000 0.0\n0.85 0.4450 0.0 / TABLE NO. 02\nThe example defines two GSF tables for when gas and water are present in the input deck. In the tables the gas-water capillary pressure data has been set to zero.\n| Note GSF is a compositional keyword in the commercial compositional simulator, and will therefore cause an error in the commercial black-oil simulator. Currently, both the GSF and WSF keywords can only be used with the CO2STORE and H2STORE models. |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"fixed","variadic_record":true},"HA":{"name":"HA","sections":["PROPS","REGIONS"],"supported":false,"summary":"The HA series of keywords defines the history match end-point gradient parameters used to set the additive cumulative end point data, for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section. In addition, the End-Point Scaling option must also be activated by the ENDSCALE keyword which is also in the RUNSPEC section. The keyword consists of the first two characters of “HA” followed by the end-point keyword shown in Table 8.45, for example, HASWL.","parameters":[],"example":"| Type | End-Point Keyword | Oil-Water End-Point Definitions |\n|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|\n| Saturation | SWL | Connate water saturation, that is the smallest water saturation in a water saturation function table. |\n| SWCR | Critical water saturation, that is the largest water saturation for which the water relative permeability is zero. | |\n| SOWCR | Critical oil-in-water saturation, that is the largest oil saturation for which the oil relative permeability is zero in an oil-water system. | |\n| Relative Permeability | KRW | Relative permeability of water at the maximum water saturation (normally the maximum water saturation is one). |\n| KRO | Relative permeability of oil at the maximum oil saturation. | |\n| KRWR | Relative permeability of water at the residual oil saturation or the residual gas saturation in a gas-water run. | |\n| KRORW | Relative permeability of oil at the critical water saturation. | |\n| Capillary Pressure | SWLPC | Capillary pressure connate water saturation, that is the smallest water saturation in a water saturation function table. |\n| Type | End-Point Keyword | Gas-Oil End-Point Definitions |\n| Saturation | SGL | Connate gas saturation, that is the smallest gas saturation in a gas saturation function table. |\n| SGCR | Critical gas saturation, that is the largest gas saturation for which the gas relative permeability is zero. | |\n| SOGCR | Critical oil-in-gas saturation, that is the larg"},"HDISP":{"name":"HDISP","sections":["PROPS"],"supported":false,"summary":"The HDISP keyword is combined with three character tracer name, specified by the TRACER keyword in the PROPS section, to define the tracer’s mechanical dispersivity parameters.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Length","Length"]}],"example":"","size_kind":"fixed","variadic_record":true},"HM":{"name":"HM","sections":["PROPS","REGIONS"],"supported":false,"summary":"The HM series of keywords defines the history match end-point gradient parameters used to set the multiplicative cumulative end point data, for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section. In addition, the End-Point Scaling option must also be activated by the ENDSCALE keyword which is also in the RUNSPEC section. The keyword consists of the first two characters of “HM” followed by the end-point keyword shown in Table 8.46, for example, HMSWL.","parameters":[],"example":"| Type | End-Point Keyword | Oil-Water End-Point Definitions |\n|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|\n| Saturation | SWL | Connate water saturation, that is the smallest water saturation in a water saturation function table. |\n| SWCR | Critical water saturation, that is the largest water saturation for which the water relative permeability is zero. | |\n| SOWCR | Critical oil-in-water saturation, that is the largest oil saturation for which the oil relative permeability is zero in an oil-water system. | |\n| Relative Permeability | KRW | Relative permeability of water at the maximum water saturation (normally the maximum water saturation is one). |\n| KRO | Relative permeability of oil at the maximum oil saturation. | |\n| KRWR | Relative permeability of water at the residual oil saturation or the residual gas saturation in a gas-water run. | |\n| KRORW | Relative permeability of oil at the critical water saturation. | |\n| Capillary Pressure | SWLPC | Capillary pressure connate water saturation, that is the smallest water saturation in a water saturation function table. |\n| Type | End-Point Keyword | Gas-Oil End-Point Definitions |\n| Saturation | SGL | Connate gas saturation, that is the smallest gas saturation in a gas saturation function table. |\n| SGCR | Critical gas saturation, that is the largest gas saturation for which the gas relative permeability is zero. | |\n| SOGCR | Critical oil-in-gas saturation, that is the larg"},"HMMROCK":{"name":"HMMROCK","sections":["PROPS"],"supported":false,"summary":"HMMROCK defines the rock compressibility gradient cumulative multipliers to be applied to the rock compressibility as defined by the ROCK keyword in the PROPS section, for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section. The constant should be a real number.","parameters":[],"example":""},"HMMROCKT":{"name":"HMMROCKT","sections":["PROPS"],"supported":false,"summary":"HMMROCKT defines the rock compaction gradient cumulative multipliers to be applied to the compaction data entered by the ROCTAB or ROCKTABH keywords in the PRROPS section, for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section","parameters":[],"example":""},"HMPROPS":{"name":"HMPROPS","sections":["PROPS","REGIONS"],"supported":false,"summary":"HMPROPS defines the start of a history match end-points section, for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section. In addition, the End-Point Scaling option must also be activated by the ENDSCALE keyword which is also in the RUNSPEC section. The keyword allows for the BOX, EQUALS, COPY, MINVALUE, MAXVALUE and ADD keywords to be used with the HA and HM series of keywords that reference the end-point scaling arrays, that is: HMKRG, HMKRGR, HMKRO, HMKRORG, HMKRORW, HMKRW, HMKRWR, HMPCW, HMPCG, HMSGCR, HMSOWCR, HMSOGCR, HMSWCR, and HMSWL keywords.","parameters":[],"example":"","size_kind":"none","size_count":0},"HMROCK":{"name":"HMROCK","sections":["PROPS"],"supported":false,"summary":"The HMROCK keyword defines the history match rock compressibility gradient parameters for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section","parameters":[{"index":1,"name":"TABLE_NUMBER","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"CALCULATE_GRADIENTS","description":"","units":{},"default":"0","value_type":"INT"}],"example":"","expected_columns":2,"size_kind":"list"},"HMROCKT":{"name":"HMROCKT","sections":["PROPS"],"supported":false,"summary":"The HMROCKT keyword defines the history match rock compaction gradient parameters for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section, and the history match rock compaction data has been entered via the HMMROCKT, ROCKTAB and ROCKTABH keywords in the PROPS section.","parameters":[{"index":1,"name":"TABLE_NUMBER","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"CALCULATE_GRADIENTS_1","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"CALCULATE_GRADIENTS_2","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":3,"size_kind":"list"},"HMRREF":{"name":"HMRREF","sections":["PROPS"],"supported":false,"summary":"The HMRREF keyword defines the history match rock compaction reference pressure gradient values to be used in conjunction with HMMROCKT, ROCKTAB and ROCKTABH keywords in the PROPS section, for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section. The history match rock compaction data is entered via the HMMROCKT, ROCKTAB and ROCKTABH keywords in the PROPS section.","parameters":[{"index":1,"name":"P_REF","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":2,"name":"P_DIM","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"}],"example":"","expected_columns":2,"size_kind":"fixed"},"HWKRO":{"name":"HWKRO","sections":["PROPS"],"supported":false,"summary":"HWKRO defines the scaling parameter for the oil relative permeability value at the connate water saturation (SWL), for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The data is used to scale the oil relative permeability in the high salinity water wet oil relative permeability saturation tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"HWKRORG":{"name":"HWKRORG","sections":["PROPS"],"supported":false,"summary":"HWKRORG defines the scaling parameter for the relative permeability of oil at the critical gas saturation (SGCR), for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The data is used to scale the oil relative permeability in the high salinity water wet oil relative permeability saturation tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"HWKRORW":{"name":"HWKRORW","sections":["PROPS"],"supported":false,"summary":"HWKRORW defines the scaling parameter for the relative permeability of oil at the critical water saturation (SWCR), for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The data is used to scale the oil relative permeability in the high salinity water wet oil relative permeability saturation tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"HWKRW":{"name":"HWKRW","sections":["PROPS"],"supported":false,"summary":"HWKRW defines the scaling parameter at the maximum oil relative permeability value (SWU), that is for Sw = 1.0, for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The data is used to scale the water relative permeability in the high salinity water wet water relative permeability saturation tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"HWKRWR":{"name":"HWKRWR","sections":["PROPS"],"supported":false,"summary":"HWKRWR defines the scaling parameter at the maximum oil relative permeability value (SWU), that is for Sw = 1.0, for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The data is used to scale the water relative permeability in the high salinity water wet water relative permeability saturation tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"HWPCW":{"name":"HWPCW","sections":["PROPS"],"supported":false,"summary":"HWPCW defines the maximum water-oil pressure values for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section. The keyword re-scales the oil-water capillary pressure in the high salinity water wet capillary saturation tables from a cell’s assigned saturation function by the grid block’s HWPCW value.","parameters":[],"example":"| [P sub c ~=~P sub{ c sub{TABLE} } LEFT( HWPCW OVER {P SUB {c sub {TABLE-MAX }}} RIGHT)] | (8.55) |\n|------------------------------------------------------------------------------------------|--------|","size_kind":"array"},"HWSOGCR":{"name":"HWSOGCR","sections":["PROPS"],"supported":false,"summary":"HWSOGCR defines the critical oil saturation with respect to gas (“SOGCR”), for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The data is used to scale the oil saturation in the high salinity water wet oil-gas relative permeability saturation tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"HWSOWCR":{"name":"HWSOWCR","sections":["PROPS"],"supported":false,"summary":"HWSOWCR defines the critical oil saturation with respect to water (“SOWCR”), for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The data is used to scale the oil saturation in the high salinity water wet water-oil relative permeability saturation tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"HWSWCR":{"name":"HWSWCR","sections":["PROPS"],"supported":false,"summary":"HWSWCR defines the critical water saturation (“SWCR”), for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The data is used to scale the water saturation in the high salinity water wet water-oil relative permeability saturation tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"HWSWL":{"name":"HWSWL","sections":["PROPS"],"supported":false,"summary":"HWSWL defines the connate water saturation (“SWL”), for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The data is used to scale the water saturation in the high salinity water wet water-oil relative permeability saturation tables, as well as the associated capillary pressure tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"HWSWLPC":{"name":"HWSWLPC","sections":["PROPS"],"supported":false,"summary":"HWSWLPC defines the capillary pressure connate water saturation (“SWLPC”), for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The data is used to scale the water saturation in the high salinity water wet water-oil capillary pressure tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"HWSWU":{"name":"HWSWU","sections":["PROPS"],"supported":false,"summary":"HWSWU defines the maximum water saturation(“SWU”), for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The data is used to scale the water saturation in the high salinity water wet water-oil relative permeability saturation tables, as well as the associated capillary pressure tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"HYDRHEAD":{"name":"HYDRHEAD","sections":["PROPS"],"supported":false,"summary":"The HYDRHEAD keyword defines the hydraulic head reference data for when the hydraulic head information is requested to be written out via one on the SUMMARY keywords (BHD, BHDF, etc.) in the SUMMARY section, or to the RESTART file via the HYDH or HYDHFW variables on the RESTART keyword","parameters":[{"index":1,"name":"REF_DEPTH","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":2,"name":"FRESHWATER_DENSITY","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Density"},{"index":3,"name":"REMOVE_DEPTH_TERMS","description":"","units":{},"default":"NO","value_type":"STRING"}],"example":"","expected_columns":3,"size_kind":"fixed","size_count":1},"HYMOBGDR":{"name":"HYMOBGDR","sections":["PROPS"],"supported":false,"summary":"This keyword, HYMOBGDR, activates the Carlson and Killough alternative secondary drainage hysteresis option for when the hysteresis option has been activated by the HYSTER variable on the SATOPTS keyword in the RUNSPEC section, and either the Carlson192\n Carlson, F. M. “Simulation of Relative Permeability Hysteresis to the Non-Wetting Phase,” paper SPE 10157, presented at the SPE Annual Technical Conference & Exhibition, San Antonio, Texas, USA (October 5-7, 1981). or Killough193\n Killough, J. E. “Reservoir Simulation with History-dependent Saturation Functions,” paper SPE 5106, Society of Petroleum Engineers Journal (1976) 16, No. 1, 37-48. models have been selected via the EHYSTR keyword in the PROPS section. Due to numerical accuracy, the gas saturation may fall below the critical gas saturation (SGCR), that is the largest gas saturation for which the gas relative permeability is zero, and gas would therefore be immobile until the gas saturation increases above SGCR. T...","parameters":[],"example":"--\n-- ACTIVATE CARLSON AND KILLOUGH ALTERNATIVE DRAINAGE HYSTERESIS OPTION\n--\nHYMOBGDR","size_kind":"none","size_count":0},"HYSTCHCK":{"name":"HYSTCHCK","sections":["PROPS"],"supported":false,"summary":"The HYSTCHCK keyword activate the hysteresis imbibition and drainage end-point check to validate that the two sets of end-points are consistent, for when the Hysteresis option has been activated by the HYSTER variable on the SATOPTS keyword in the RUNSPEC section, and the ENDSCALE keyword in the RUNSPEC section has been activated to enable end-point scaling.","parameters":[],"example":"","size_kind":"fixed","size_count":1},"IKRG":{"name":"IKRG","sections":["PROPS"],"supported":null,"summary":"IKRG defines the imbibition scaling parameter at the maximum gas relative permeability value (ISGU), normally ISGU is equal to 1.0 - Swc, for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the HYSTER option on the SATOPTS keyword in the RUNSPEC section has to be activated to invoke the Hysteresis option. The SCALCERS keyword in the PROPS section defines the options used in the re-scaling process, the options are two point scaling and three point scaling.","parameters":[{"index":1,"name":"IKRG","description":"IKRG is an array of positive real numbers which are greater than zero and less than or equal to 1.0, that are the assigned scaling IKRG imbibition values for each cell in the model. Repeat counts may be used, for example 50*0.400. dimensionless","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"The example below defines an input box for the whole grid and for layers one to three, for layer one IKRG is set equal to 0.550, for layer two IKRG equals 0.575, and for layer three IKRG equals 0.600.\n--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS (NX=100, NY=100)\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1* 1* 1* 1* 1 3 / DEFINE BOX AREA\n--\n-- SET IKRG VALUES FOR THREE LAYERS IN THE MODEL\n--\nIKRG\n1000*0.550 1000*0.575 1000*0.600 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\n| [k sub rg ~=~k sub{ rg sub{`TABLE} } LEFT(IKRG OVER {k SUB {rg sub {`TABLE-MAX }}} RIGHT)] | (8.56) |\n|--------------------------------------------------------------------------------------------|--------|\n| No | Phases Present | Critical Saturation |\n|----|----------------|----------------------------------|\n| 1 | Gas-Oil | S critical = 1.0 – ISOGCR - ISWL |\n| 2 | Gas-Oil-Water | S critical = 1.0 – ISOGCR - ISWL |\n| 3 | Gas-Water | S critical = 1.0 – ISWCR |"},"IKRGR":{"name":"IKRGR","sections":["PROPS"],"supported":null,"summary":"IKRGR defines the imbibition scaling parameter at the relative permeability of gas at residual oil saturation (1 – ISOGCR), or critical water saturation in a gas-water run (Swc), for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the HYSTER option on the SATOPTS keyword in the RUNSPEC section has to be activated to invoke the Hysteresis option. The SCALCERS keyword in the PROPS section defines the options used in the re-scaling process, the options are two point scaling and three point scaling.","parameters":[{"index":1,"name":"IKRGR","description":"IKRGR is an array of positive real numbers which are greater than zero and less than or equal to 1.0, that are the assigned imbibition scaling IKRGR values for each cell in the model. In addition, for a given grid block IKGRGT should be less than IKRG. Repeat counts may be used, for example 50*0.400.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"The first example defines an input box for the whole grid and for layers one to three, for layer one IKRRG is set equal to 0.500, for layer two IKRGR equals 0.570, and for layer three IKRGR equals 0.580.\n--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS (NX=100, NY=100)\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1* 1* 1* 1* 1 3 / DEFINE BOX AREA\n--\n-- SET IKRGR VALUES FOR THREE LAYERS IN THE MODEL\n--\nIKRGR\n10000*0.500 10000*0.570 10000*0.580 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe next example does exactly the same thing using the EQUALS keyword instead.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nIKRGR’ 0.5000 1* 1* 1* 1* 1 1 / IKRGR FOR LAYER 1\nIKRGR’ 0.5700 1* 1* 1* 1* 2 2 / IKRGR FOR LAYER 2\nIKRGR’ 0.5800 1* 1* 1* 1* 3 3 / IKRGR FOR LAYER 3\n/\n| No | Phases Present | Critical Saturation |\n|----|----------------|----------------------------------|\n| 1 | Gas-Oil | S critical = 1.0 – ISOGCR - ISWL |\n| 2 | Gas-Oil-Water | S critical = 1.0 – ISOGCR - ISWL |\n| 3 | Gas-Water | S critical = 1.0 – ISWCR |"},"IKRO":{"name":"IKRO","sections":["PROPS"],"supported":null,"summary":"IKRO defines the scaling parameter for the imbibition oil relative permeability value at the connate water saturation (ISWL), for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the HYSTER option on the SATOPTS keyword in the RUNSPEC section has to be activated to invoke the Hysteresis option. The SCALCERS keyword in the PROPS section defines the options used in the re-scaling process, the options are two point scaling and three point scaling.","parameters":[{"index":1,"name":"IKRO","description":"IKRO is an array of positive real numbers which are greater than zero and less than or equal to 1.0, that are the assigned imbibition scaling IKRO values for each cell in the model. Repeat counts may be used, for example 50*0.500.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"The example below defines an input box for the whole grid and for layers one to three, for layer one IKRO is set equal to 0.850, for layer two IKRO equals 0.875, and for layer three IKRO equals 0.900.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nIKRO 0.8500 1* 1* 1* 1* 1 1 / IKRO FOR LAYER 1\nIKRO 0.8750 1* 1* 1* 1* 2 2 / IKRO FOR LAYER 2\nIKRO 0.9000 1* 1* 1* 1* 3 3 / IKRO FOR LAYER 3\n/\n| [k sub ro ~=~k sub{ ro sub{`TABLE} } LEFT(IKRO OVER {k SUB {ro sub {`TABLE-MAX }}} RIGHT)] | (8.57) |\n|--------------------------------------------------------------------------------------------|--------|\n| No | Keywords Present | Critical Saturation |\n|----|------------------|-------------------------------|\n| 1 | KRORW | S critical = 1.0 – SWCR - SGL |\n| 2 | KRORG | S critical = 1.0 – SGCR - SWL |"},"IKRORG":{"name":"IKRORG","sections":["PROPS"],"supported":null,"summary":"IKRORG defines the scaling parameter for the imbibition relative permeability of oil at the critical gas saturation (ISGCR), for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the HYSTER option on the SATOPTS keyword in the RUNSPEC section has to be activated to invoke the Hysteresis option. The SCALCERS keyword in the PROPS section defines the options used in the re-scaling process, the options are two point scaling and three point scaling.","parameters":[{"index":1,"name":"IKRORG","description":"IKRORG is an array of positive real numbers which are greater than zero and less than or equal to 1.0, that are the assigned imbibition scaling IKRORG values for each cell in the model. Repeat counts may be used, for example 50*0.850.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"The first example defines an input box for the whole grid and for layers one to three, for layer one IKRORG is set equal to 0.755, for layer two IKRORG equals 0.775, and for layer three IKRORG equals 0.800.\n--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS (NX=100, NY=100)\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1* 1* 1* 1* 1 3 / DEFINE BOX AREA\n--\n-- SET IKRORG VALUES FOR THREE LAYERS IN THE MODEL\n--\nIKRORG\n10000*0.755 10000*0.775 10000*0.800 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe next example does exactly the same thing using the EQUALS keyword instead.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nIKRORG 0.7550 1* 1* 1* 1* 1 1 / IKRORG FOR LAYER 1\nIKRORG 0.7750 1* 1* 1* 1* 2 2 / IKRORG FOR LAYER 2\nIKRORG 0.8000 1* 1* 1* 1* 3 3 / IKRORG FOR LAYER 3\n/\n| No | Keywords Present | Critical Saturation |\n|----|------------------|---------------------------------|\n| 1 | IKRORW | S critical = 1.0 – ISWCR - ISGL |\n| 2 | IKRORG | S critical = 1.0 – ISGCR - SWL |"},"IKRORW":{"name":"IKRORW","sections":["PROPS"],"supported":null,"summary":"IKRORW defines the scaling parameter for the imbibition relative permeability of oil at the critical water saturation (ISWCR), for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the HYSTER option on the SATOPTS keyword in the RUNSPEC section has to be activated to invoke the Hysteresis option. The SCALECRS keyword in the PROPS section defines the options used in the re-scaling process, the options are two point scaling and three point scaling.","parameters":[{"index":1,"name":"IKRORW","description":"IKRORW is an array of positive real numbers which are greater than zero and less than or equal to 1.0, that are the assigned imbibition scaling IKRORW values for each cell in the model. Repeat counts may be used, for example 50*0.850","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"The first example defines an input box for the whole grid and for layers one to three, for layer one IKRORW is set equal to 0.755, for layer two IKRORW equals 0.775, and for layer three IKRORW equals 0.800.\n--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS (NX=100, NY=100)\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1* 1* 1* 1* 1 3 / DEFINE BOX AREA\n--\n-- SET IKRORW VALUES FOR THREE LAYERS IN THE MODEL\n--\nIKRORW\n10000*0.755 10000*0.775 10000*0.800 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe next example does exactly the same thing using the EQUALS keyword instead.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nIKRORW 0.7550 1* 1* 1* 1* 1 1 / IKRORW FOR LAYER 1\nIKRORW 0.7750 1* 1* 1* 1* 2 2 / IKRORW FOR LAYER 2\nIKRORW 0.8000 1* 1* 1* 1* 3 3 / IKRORW FOR LAYER 3\n/\n| No | Keywords Present | Critical Saturation |\n|----|------------------|---------------------------------|\n| 1 | IKRORW | S critical = 1.0 – ISWCR - ISGL |\n| 2 | IKRORG | S critical = 1.0 – ISGCR - ISWL |"},"IKRW":{"name":"IKRW","sections":["PROPS"],"supported":null,"summary":"IKRW defines the scaling parameter at the maximum imbibition water relative permeability value (ISWU), that is for Sw = 1.0, for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the HYSTER option on the SATOPTS keyword in the RUNSPEC section has to be activated to invoke the Hysteresis option. The SCALCERS keyword in the PROPS section defines the options used in the re-scaling process, the options are two point scaling and three point scaling.","parameters":[{"index":1,"name":"IKRW","description":"IKRW is an array of positive real numbers which are greater than zero and less than or equal to 1.0, that are the assigned imbibition scaling IKRW values for each cell in the model. Repeat counts may be used, for example 50*1.000.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"The example below defines an input box for the whole grid and for layers one to three, for layer one IKRW is set equal to 0.850, for layer two IKRW equals 0.875, and for layer three IKRW equals 0.900.\n--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS (NX=100, NY=100)\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1* 1* 1* 1* 1 3 / DEFINE BOX AREA\n--\n-- SET IKRW VALUES FOR THREE LAYERS IN THE MODEL\n--\nIKRW\n10000*0.850 10000*0.875 10000*0.900 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\n| [k sub rw ~=~k sub{ rw sub{`TABLE} } LEFT(IKRW OVER {k SUB {rw sub {`TABLE-MAX }}} RIGHT)] | (8.58) |\n|--------------------------------------------------------------------------------------------|--------|\n| No | Phases Present | Critical Saturation |\n|----|----------------|----------------------------------|\n| 1 | Gas-Oil | S critical = 1.0 – ISOWCR - ISGL |\n| 2 | Gas-Oil-Water | S critical = 1.0 – ISOWCR - ISGL |\n| 3 | Gas-Water | S critical = 1.0 – ISGCR |"},"IKRWR":{"name":"IKRWR","sections":["PROPS"],"supported":null,"summary":"IKRWR defines the scaling parameter at the imbibition critical oil to water saturation value (ISOWCR), for the imbibition water relative permeability curve, for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the HYSTER option on the SATOPTS keyword in the RUNSPEC section has to be activated to invoke the Hysteresis option. The SCALCERS keyword in the PROPS section defines the options used in the re-scaling process, the options are two point scaling and three point scaling.","parameters":[{"index":1,"name":"IKRWR","description":"IKRWR is an array of positive real numbers which are greater than zero and less than or equal to 1.0, that are the assigned imbibition scaling IKRWR values for each cell in the model. Repeat counts may be used, for example 50*1.000.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"The first example defines an input box for the whole grid and for layers one to three, for layer one IKRWR is set equal to 0.755, for layer two IKRWR equals 0.775, and for layer three IKRWR equals 0.800.\n--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS (NX=100, NY=100)\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1* 1* 1* 1* 1 3 / DEFINE BOX AREA\n--\n-- SET IKRWR VALUES FOR THREE LAYERS IN THE MODEL\n--\nIKRWR\n10000*0.755 10000*0.775 10000*0.800 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe next example does exactly the same thing using the EQUALS keyword instead.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nIKRWR 0.7550 1* 1* 1* 1* 1 1 / IKRWR FOR LAYER 1\nIKRWR 0.7750 1* 1* 1* 1* 2 2 / IKRWR FOR LAYER 2\nIKRWR 0.8000 1* 1* 1* 1* 3 3 / IKRWR FOR LAYER 3\n/\n| No | Phases Present | Critical Saturation |\n|----|----------------|----------------------------------|\n| 1 | Gas-Oil | S critical = 1.0 – ISOWCR - ISGL |\n| 2 | Gas-Oil-Water | S critical = 1.0 – ISOWCR - ISGL |\n| 3 | Gas-Water | S critical = 1.0 – ISGCR |"},"IMKRVD":{"name":"IMKRVD","sections":["PROPS"],"supported":false,"summary":"This keyword defines the maximum imbibition oil, gas, and water relative permeability versus depth for the three phases. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the HYSTER option on the SATOPTS keyword in the RUNSPEC section has to be activated to invoke the Hysteresis option.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Length","1","1","1","1","1","1","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"IMPCVD":{"name":"IMPCVD","sections":["PROPS"],"supported":false,"summary":"This keyword defines the maximum imbibition gas-oil and water-oil capillary pressure values versus depth for when the end-point scaling option has been invoked by the ENDSCALE keyword in the RUNSPEC section and the HYSTER option on the SATOPTS keyword in the RUNSPEC section has been activated to invoke the Hysteresis option.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Length","Pressure","Pressure"]}],"example":"","size_kind":"fixed","variadic_record":true},"IMPTVD":{"name":"IMPTVD","sections":["PROPS"],"supported":false,"summary":"This keyword defines the variation of the imbibition relative permeability saturation end-points (SWL, SWCR, etc.) for all three phases versus depth., for when the end-point scaling option has been invoked by the ENDSCALE keyword in the RUNSPEC section, and the HYSTER option on the SATOPTS keyword in the RUNSPEC section has been activated to invoke the Hysteresis option. This functionality is not supported in OPM Flow.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Length","1","1","1","1","1","1","1","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"IMSPCVD":{"name":"IMSPCVD","sections":["PROPS"],"supported":false,"summary":"This keyword defines the imbibition capillary pressure gas and water connate saturations values versus depth for when the end-point scaling option has been invoked by the ENDSCALE keyword in the RUNSPEC section, and the HYSTER option on the SATOPTS keyword in the RUNSPEC section has been activated to invoke the Hysteresis option. This functionality is not supported in OPM Flow.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Length","1","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"INTPC":{"name":"INTPC","sections":["PROPS"],"supported":false,"summary":"The INTPC keyword activates the integrated capillary pressure option for the oil, gas or both phases, for when a Dual Porosity model has been activated by either the DUALPORO or DUALPERM keywords in the RUNSPEC section. In addition, the keyword can only be used if the Gravity Drainage option has been specified by either the GRAVDR or GRAVDRM in the RUNSPEC section. Basically, activating this feature results in the simulator adjusting the capillary pressure curves by integrating the matrix capillary pressure curves over the matrix block height to calculate the average saturation.","parameters":[{"index":1,"name":"PHASE","description":"","units":{},"default":"BOTH","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"IONXROCK":{"name":"IONXROCK","sections":["PROPS"],"supported":false,"summary":"The IONXROCK keyword activates ion exchange and defines the ion exchange constant by saturation table regions, for when the brine phase has been activated by the BRINE keyword and the Multi-Component Brine model, that allows for the water phase to have multiple water salinities, has been activated by the ECLMC keyword. Both keywords are in the RUNSPEC section.","parameters":[{"index":1,"name":"VALUE","description":"","units":{},"default":"0","value_type":"DOUBLE"}],"example":"","expected_columns":1,"size_kind":"fixed"},"IONXSURF":{"name":"IONXSURF","sections":["PROPS"],"supported":false,"summary":"The IONXROCK keyword activates ion exchange on surfactant micellae194\n Particle of colloidal dimensions that exists in equilibrium with the molecules or ions in solution from which it is formed. A micella or micelle (plural micellae or micelles, respectively) is an aggregate (or supramolecular assembly) of surfactant molecules dispersed in a liquid colloid. A typical micella in aqueous solution forms an aggregate with the hydrophilic \"head\" regions in contact with surrounding solvent, sequestering the hydrophobic single-tail regions in the micella centre (https://en.wikipedia.org/wiki/Micelle). and defines the ion exchange constant by surfactant equivalent molecular weight for saturation table regions, for when the brine and surfactant phases has been activated by the BRINE and SURFACT keywords, and the Multi-Component Brine model, that allows for the water phase to have multiple water salinities, has been activated by the ECLMC keyword. All three keywords are in the RUNSPEC se...","parameters":[{"index":1,"name":"MOLECULAR_WEIGHT","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":2,"name":"ION_EXCH_CONST","description":"","units":{},"default":"0","value_type":"DOUBLE"}],"example":"","expected_columns":2,"size_kind":"fixed"},"IPCG":{"name":"IPCG","sections":["PROPS"],"supported":null,"summary":"IPCG defines the maximum imbibition gas-oil capillary pressure values for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the HYSTER option on the SATOPTS keyword in the RUNSPEC section has to be activated to invoke the hysteresis option. The keyword can be used with all grid types.","parameters":[{"index":1,"name":"IPCG","description":"IPCG is an array of positive real numbers assigning the maximum imbibition gas capillary pressure values for each cell in the model. Repeat counts may be used, for example 30*100.0.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK IPCG DATA FOR ALL CELLS (BASED ON NX x NY x NZ = 300)\n--\nIPCG\n100*50.0 100*75.0 100*125.0 /\nThe above example defines the IPCG for 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.\n| [P sub c ~=~P sub{ c sub{TABLE} } LEFT( IPCG OVER {P SUB {c sub {TABLE-MAX }}} RIGHT)] | (8.59) |\n|-----------------------------------------------------------------------------------------|--------|","size_kind":"array"},"IPCW":{"name":"IPCW","sections":["PROPS"],"supported":null,"summary":"IPCW defines the maximum imbibition water-oil or water-gas capillary pressure values for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the HYSTER option on the SATOPTS keyword in the RUNSPEC section has to be activated to invoke the hysteresis option. The keyword can be used with all grid types.","parameters":[{"index":1,"name":"IPCW","description":"IPCW is an array of positive real numbers assigning the maximum imbibition water capillary pressure values for each cell in the model. Repeat counts may be used, for example 30*100.0.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK IPCW DATA FOR ALL CELLS (BASED ON NX x NY x NZ = 300)\n--\nIPCW\n100*50.0 100*75.0 100*125.0 /\nThe above example defines the IPCW for 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.\n| [P sub c ~=~P sub{ c sub{TABLE} } LEFT( IPCW OVER {P SUB {c sub {TABLE-MAX }}} RIGHT)] | (8.60) |\n|-----------------------------------------------------------------------------------------|--------|","size_kind":"array"},"ISGCR":{"name":"ISGCR","sections":["PROPS"],"supported":null,"summary":"ISGCR defines the imbibition critical gas saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE keyword in the RUNSPEC section and the hysteresis model option has been activated on the SATOPTS keyword in the RUNSPEC section. The critical gas saturation is defined as the maximum gas saturation for which the gas relative permeability is zero in a two-phase relative permeability table.","parameters":[{"index":1,"name":"ISGCR","description":"ISGCR is an array of real numbers assigning the critical gas saturation values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.03","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT ISGCR DATA FOR CELLS (NX x NY x NZ = 300)\nISGCR\n300*0.050 /\nThe above example defines a constant critical gas saturation of 0.05 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"ISGL":{"name":"ISGL","sections":["PROPS"],"supported":null,"summary":"ISGL defines the imbibition connate gas saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE keyword in the RUNSPEC section and the hysteresis model option has been activated on the SATOPTS keyword in the RUNSPEC section. The connate gas saturation is defined as the minimum gas saturation in a two-phase gas relative permeability table.","parameters":[{"index":1,"name":"ISGL","description":"ISGL is an array of real numbers assigning the connate gas saturation values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.03 dimensionless","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT ISGL DATA FOR ALL CELLS (NX x NY x NZ = 300)\nISGL\n300*0.030 /\nThe above example defines a constant connate gas saturation of 0.03 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"ISGLPC":{"name":"ISGLPC","sections":["PROPS"],"supported":null,"summary":"ISGLPC defines the imbibition connate gas saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE keyword in the RUNSPEC section and the hysteresis model option has been activated on the SATOPTS keyword in the RUNSPEC section. The connate gas saturation is defined as the minimum gas saturation in a two-phase gas relative permeability table. The keyword only applies the scaling to the imbibition capillary pressures tables, unlike the ISGL keyword that applies the scaling to both the capillary pressure and relative permeability tables. The keyword can be used with all grid types.","parameters":[{"index":1,"name":"ISGLPC","description":"ISGLPC is an array of real numbers assigning the connate gas saturation values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. If ISGLPC is omitted from the input deck the values will be defaulted to those on the ISGL series of keywords. If the ISGL series of keywords are missing from the input deck then the values are taken from the cell allocated capillary pressure table. Repeat counts may be used, for example 30*0.03","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from SGL or from the cell allocated capillary pressure table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT ISGLPC DATA FOR ALL CELLS\n– (NX x NY x NZ = 300)\nISGLPC\n300*0.030 /\nThe above example defines a constant connate gas saturation of 0.03 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"ISGU":{"name":"ISGU","sections":["PROPS"],"supported":null,"summary":"ISGU defines the imbibition maximum gas saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE keyword in the RUNSPEC section and the hysteresis model option has been activated on the SATOPTS keyword in the RUNSPEC section. The maximum gas saturation is defined as the maximum gas saturation in a two-phase gas relative permeability table. The keyword can be used with all grid types.","parameters":[{"index":1,"name":"ISGU","description":"ISGU is an array of real numbers assigning the maximum gas saturation values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.70","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT ISGU DATA FOR ALL CELLS (NX x NY x NZ = 300)\nISGU\n300*0.700 /\nThe above example defines a constant connate gas saturation of 0.70 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"ISOGCR":{"name":"ISOGCR","sections":["PROPS"],"supported":null,"summary":"ISOGCR defines the imbibition critical oil saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE in the RUNSPEC section and the hysteresis model option has been activated on the SATOPTS keyword in the RUNSPEC section. The critical oil saturation with respect to gas is defined as the maximum oil saturation for which the oil relative permeability is zero in a two-phase gas-oil relative permeability table. The keyword can be used with all grid types.","parameters":[{"index":1,"name":"ISOGCR","description":"ISOGCR is an array of real numbers assigning the critical oil saturation with respect to gas values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.30","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT ISOGCR DATA FOR ALL CELLS\n-- (NX x NY x NZ = 300)\n--\nISOGCR\n300*0.200 /\nThe above example defines a constant critical gas saturation of 0.20 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"ISOWCR":{"name":"ISOWCR","sections":["PROPS"],"supported":null,"summary":"ISOWCR defines the imbibition critical oil saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE in the RUNSPEC section and the hysteresis model option has been activated on the SATOPTS keyword in the RUNSPEC section. The critical oil saturation with respect to water is defined as the maximum oil saturation for which the oil relative permeability is zero in a two-phase oil-water relative permeability table. The keyword can be used with all grid types.","parameters":[{"index":1,"name":"ISOWCR","description":"ISOWCR is an array of real numbers assigning the critical oil saturation with respect to water values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.30","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT ISOWCR DATA FOR ALL CELLS\n-- (NX x NY x NZ = 300)\n--\nISOWCR\n300*0.200 /\nThe above example defines a constant critical gas saturation of 0.20 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section","size_kind":"array"},"ISWCR":{"name":"ISWCR","sections":["PROPS"],"supported":null,"summary":"ISWCR defines the imbibition critical water saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE in the RUNSPEC section and the hysteresis model option has been activated on the SATOPTS keyword in the RUNSPEC section. The critical water saturation is defined as the maximum water saturation for which the water relative permeability is zero in a two-phase relative permeability table. The keyword can be used with all grid types.","parameters":[{"index":1,"name":"ISWCR","description":"ISWCR is an array of real numbers assigning the critical water saturation values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.20","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT ISWCR DATA FOR ALL CELLS\n-- (NX x NY x NZ = 300)\n--\nISWCR\n300*0.200 /\nThe above example defines a constant critical water saturation of 0.20 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"ISWL":{"name":"ISWL","sections":["PROPS"],"supported":null,"summary":"ISWL defines the imbibition connate water saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE in the RUNSPEC section and the hysteresis model option has been activated on the SATOPTS keyword in the RUNSPEC section. The connate water saturation is defined as the minimum water saturation in a two-phase water relative permeability table.","parameters":[{"index":1,"name":"ISWL","description":"ISWL is an array of real numbers assigning the connate water saturation values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.15","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT ISWL DATA FOR ALL CELLS (NX x NY x NZ = 300)\n--\nISWL\n300*0.150 /\nThe above example defines a constant connate water saturation of 0.15 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"ISWLPC":{"name":"ISWLPC","sections":["PROPS"],"supported":null,"summary":"ISWLPC defines the imbibition connate water saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE in the RUNSPEC section and the hysteresis model option has been activated on the SATOPTS keyword in the RUNSPEC section. The connate water saturation is defined as the minimum water saturation in a two-phase water relative permeability table. The keyword only applies the scaling to the imbibition capillary pressures tables, unlike the ISWL keyword that applies the scaling to both the capillary pressure and relative permeability tables. The keyword can be used with all grid types.","parameters":[{"index":1,"name":"ISWLPC","description":"ISWLPC is an array of real numbers assigning the connate water saturation values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. If ISWLPC is omitted from the input deck the values will be defaulted to those on the ISGL series of keywords. If the ISWL series of keywords are missing from the input deck then the values are taken from the cell allocated capillary pressure table. Repeat counts may be used, for example 30*0.15","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from SWL or from the cell allocated capillary pressure table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT ISWLPC DATA FOR ALL CELLS (\n-- NX x NY x NZ = 300)\n--\nISWLPC\n300*0.150 /\nThe above example defines a constant connate water saturation of 0.15 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"ISWU":{"name":"ISWU","sections":["PROPS"],"supported":null,"summary":"ISWU defines the imbibition maximum water saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE in the RUNSPEC section and the hysteresis model option has been activated on the SATOPTS keyword in the RUNSPEC section. The maximum water saturation is defined as the maximum water saturation in a two-phase water relative permeability table. The keyword can be used with all grid types.","parameters":[{"index":1,"name":"ISWU","description":"ISWU is an array of real numbers assigning the maximum water saturation values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.70","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT ISWU DATA FOR ALL CELLS (NX x NY x NZ = 300)\n--\nISWU\n300*0.700 /\nThe above example defines a constant connate gas saturation of 0.70 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"KRG":{"name":"KRG","sections":["PROPS"],"supported":null,"summary":"KRG defines the scaling parameter at the maximum drainage gas relative permeability value (SGU), normally SGU is equal to 1.0 - Swc, for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. The SCALCERS keyword in the PROPS section defines the options used in the re-scaling process, the options are two point scaling and three point scaling.","parameters":[{"index":1,"name":"KRG","description":"KRG is an array of positive real numbers which are greater than zero and less than or equal to 1.0, that are the assigned scaling KRG values for each cell in the model. Repeat counts may be used, for example 50*0.400. dimensionless","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"The first example defines an input box for the whole grid and for layers one to three, for layer one KRG is set equal to 0.555, for layer two KRG equals 0.575, and for layer three KRG equals 0.600.\n--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS (NX=100, NY=100)\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1* 1* 1* 1* 1 3 / DEFINE BOX AREA\n--\n-- SET KRG VALUES FOR THREE LAYERS IN THE MODEL\n--\nKRG\n10000*0.555 10000*0.575 10000*0.600 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe next example does exactly the same thing using the EQUALS keyword instead.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nKRG 0.5550 1* 1* 1* 1* 1 1 / KRG FOR LAYER 1\nKRG 0.5750 1* 1* 1* 1* 2 2 / KRG FOR LAYER 2\nKRG 0.6000 1* 1* 1* 1* 3 3 / KRG FOR LAYER 3\n/\n| [k sub rg ~=~k sub{ rg sub{`TABLE} } LEFT(KRG OVER {k SUB {rg sub {`TABLE-MAX }}} RIGHT)] | (8.61) |\n|-------------------------------------------------------------------------------------------|--------|\n| No | Phases Present | Critical Saturation |\n|----|----------------|--------------------------------|\n| 1 | Gas-Oil | S critical = 1.0 – SOGCR - SWL |\n| 2 | Gas-Oil-Water | S critical = 1.0 – SOGCR - SWL |\n| 3 | Gas-Water | S critical = 1.0 – SWCR |"},"KRGR":{"name":"KRGR","sections":["PROPS"],"supported":null,"summary":"KRGR defines the scaling parameter at the relative permeability of gas at residual oil saturation (1 – SOGCR), or critical water saturation in a gas-water run (Swc), for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. The SCALCERS keyword in the PROPS section defines the options used in the re-scaling process, the options are two point scaling and three point scaling.","parameters":[{"index":1,"name":"KRGR","description":"KRGR is an array of positive real numbers which are greater than zero and less than or equal to 1.0, that are the assigned scaling KRGR values for each cell in the model. In addition, for a given grid block KGRG should be less than KRG. Repeat counts may be used, for example 50*0.400.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"The first example defines an input box for the whole grid and for layers one to three, for layer one KRGR is set equal to 0.500, for layer two KRGR equals 0.570, and for layer three KRGR equals 0.580.\n--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS (NX=100, NY=100)\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1* 1* 1* 1* 1 3 / DEFINE BOX AREA\n--\n-- SET KRGR VALUES FOR THREE LAYERS IN THE MODEL\n--\nKRGR\n10000*0.500 10000*0.570 10000*0.580 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe next example does exactly the same thing using the EQUALS keyword instead.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nKRGR 0.5000 1* 1* 1* 1* 1 1 / KRGR FOR LAYER 1\nKRGR 0.5700 1* 1* 1* 1* 2 2 / KRGR FOR LAYER 2\nKRGR 0.5800 1* 1* 1* 1* 3 3 / KRGR FOR LAYER 3\n/\n| No | Phases Present | Critical Saturation |\n|----|----------------|--------------------------------|\n| 1 | Gas-Oil | S critical = 1.0 – SOGCR - SWL |\n| 2 | Gas-Oil-Water | S critical = 1.0 – SOGCR - SWL |\n| 3 | Gas-Water | S critical = 1.0 – SWCR |"},"KRO":{"name":"KRO","sections":["PROPS"],"supported":null,"summary":"KRO defines the scaling parameter for the drainage oil relative permeability value at the connate water saturation (SWL), for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. The SCALCERS keyword in the PROPS section defines the options used in the re-scaling process, the options are two point scaling and three point scaling.","parameters":[{"index":1,"name":"KRO","description":"KRO is an array of positive real numbers which are greater than zero and less than or equal to 1.0, that are the assigned scaling KRO values for each cell in the model. Repeat counts may be used, for example 50*0.500.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"The first example defines an input box for the whole grid and for layers one to three, for layer one KRO is set equal to 0.855, for layer two KRO equals 0.875, and for layer three KRO equals 0.900.\n--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS (NX=100, NY=100)\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1* 1* 1* 1* 1 3 / DEFINE BOX AREA\n--\n-- SET KRO VALUES FOR THREE LAYERS IN THE MODEL\n--\nKRO\n10000*0.855 10000*0.875 10000*0.900 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe next example does exactly the same thing using the EQUALS keyword instead.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nKRO 0.8550 1* 1* 1* 1* 1 1 / KRO FOR LAYER 1\nKOG 0.8750 1* 1* 1* 1* 2 2 / KRO FOR LAYER 2\nKRO 0.9000 1* 1* 1* 1* 3 3 / KRO FOR LAYER 3\n/\n| [k sub ro ~=~k sub{ ro sub{`TABLE} } LEFT(KRO OVER {k SUB {ro sub {`TABLE-MAX }}} RIGHT)] | (8.62) |\n|-------------------------------------------------------------------------------------------|--------|\n| No | Keywords Present | Critical Saturation |\n|----|------------------|-------------------------------|\n| 1 | KRORW | S critical = 1.0 – SWCR - SGL |\n| 2 | KRORG | S critical = 1.0 – SGCR - SWL |"},"KRORG":{"name":"KRORG","sections":["PROPS"],"supported":null,"summary":"KRORG defines the scaling parameter for the drainage relative permeability of oil at the critical gas saturation (SGCR), for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. The SCALCERS keyword in the PROPS section defines the options used in the re-scaling process, the options are two point scaling and three point scaling.","parameters":[{"index":1,"name":"KRORG","description":"KRORG is an array of positive real numbers which are greater than zero and less than or equal to 1.0, that are the assigned scaling KRORG values for each cell in the model. Repeat counts may be used, for example 50*0.850.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"The first example defines an input box for the whole grid and for layers one to three, for layer one KRORG is set equal to 0.755, for layer two KRORG equals 0.775, and for layer three KRORG equals 0.800.\n--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS (NX=100, NY=100)\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1* 1* 1* 1* 1 3 / DEFINE BOX AREA\n--\n-- SET KRORG VALUES FOR THREE LAYERS IN THE MODEL\n--\nKRORG\n10000*0.755 10000*0.775 10000*0.800 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe next example does exactly the same thing using the EQUALS keyword instead.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nKRORG 0.7550 1* 1* 1* 1* 1 1 / KRORG FOR LAYER 1\nKRORG 0.7750 1* 1* 1* 1* 2 2 / KRORG FOR LAYER 2\nKRORG 0.8000 1* 1* 1* 1* 3 3 / KRORG FOR LAYER 3\n/\n| No | Keywords Present | Critical Saturation |\n|----|------------------|-------------------------------|\n| 1 | KRORW | S critical = 1.0 – SWCR - SGL |\n| 2 | KRORG | S critical = 1.0 – SGCR - SWL |"},"KRORW":{"name":"KRORW","sections":["PROPS"],"supported":null,"summary":"KRORW defines the scaling parameter for the drainage relative permeability of oil at the critical water saturation (SWCR), for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. The SCALECRS keyword in the PROPS section defines the options used in the re-scaling process, the options are two point scaling and three point scaling.","parameters":[{"index":1,"name":"KRORW","description":"KRORW is an array of positive real numbers which are greater than zero and less than or equal to 1.0, that are the assigned scaling KRORW values for each cell in the model. Repeat counts may be used, for example 50*0.850","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"The first example defines an input box for the whole grid and for layers one to three, for layer one KRORW is set equal to 0.755, for layer two KRORW equals 0.775, and for layer three KRORW equals 0.800.\n--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS (NX=100, NY=100)\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1* 1* 1* 1* 1 3 / DEFINE BOX AREA\n--\n-- SET KRORW VALUES FOR THREE LAYERS IN THE MODEL\n--\nKRORW\n10000*0.755 10000*0.775 10000*0.800 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe next example does exactly the same thing using the EQUALS keyword instead.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nKRORW 0.7550 1* 1* 1* 1* 1 1 / KRORW FOR LAYER 1\nKRORW 0.7750 1* 1* 1* 1* 2 2 / KRORW FOR LAYER 2\nKRORW 0.8000 1* 1* 1* 1* 3 3 / KRORW FOR LAYER 3\n/\n| No | Keywords Present | Critical Saturation |\n|----|------------------|-------------------------------|\n| 1 | KRORW | S critical = 1.0 – SWCR - SGL |\n| 2 | KRORG | S critical = 1.0 – SGCR - SWL |"},"KRW":{"name":"KRW","sections":["PROPS"],"supported":null,"summary":"KRW defines the scaling parameter at the maximum drainage water relative permeability value (SWU), that is for Sw = 1.0, for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. The SCALCERS keyword in the PROPS section defines the options used in the re-scaling process, the options are two point scaling and three point scaling.","parameters":[{"index":1,"name":"KRW","description":"KRW is an array of positive real numbers which are greater than zero and less than or equal to 1.0, that are the assigned scaling KRW values for each cell in the model. Repeat counts may be used, for example 50*1.000.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"The first example defines an input box for the whole grid and for layers one to three, for layer one KRW is set equal to 0.855, for layer two KRW equals 0.875, and for layer three KRW equals 0.900.\n--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS (NX=100, NY=100)\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1* 1* 1* 1* 1 3 / DEFINE BOX AREA\n--\n-- SET KRW VALUES FOR THREE LAYERS IN THE MODEL\n--\nKRW\n10000*0.855 10000*0.875 10000*0.900 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe next example does exactly the same thing using the EQUALS keyword instead.\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nKRW 0.8550 1* 1* 1* 1* 1 1 / KRW FOR LAYER 1\nKRW 0.8750 1* 1* 1* 1* 2 2 / KRW FOR LAYER 2\nKRW 0.9000 1* 1* 1* 1* 3 3 / KRW FOR LAYER 3\n/\n| [k sub rw ~=~k sub{ rw sub{`TABLE} } LEFT(KRW OVER {k SUB {rw sub {`TABLE-MAX }}} RIGHT)] | (8.63) |\n|-------------------------------------------------------------------------------------------|--------|\n| No | Phases Present | Critical Saturation |\n|----|----------------|--------------------------------|\n| 1 | Gas-Oil | S critical = 1.0 – SOWCR - SGL |\n| 2 | Gas-Oil-Water | S critical = 1.0 – SOWCR - SGL |\n| 3 | Gas-Water | S critical = 1.0 – SGCR |"},"KRWR":{"name":"KRWR","sections":["PROPS"],"supported":null,"summary":"KRWR defines the scaling parameter at the drainage critical oil to water saturation value (SOWCR), for the drainage water relative permeability curve, for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. The SCALCERS keyword in the PROPS section defines the options used in the re-scaling process, the options are two point scaling and three point scaling.","parameters":[{"index":1,"name":"KRWR","description":"KRWR is an array of positive real numbers which are greater than zero and less than or equal to 1.0, that are the assigned scaling KRWR values for each cell in the model. Repeat counts may be used, for example 50*1.000.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"The first example defines an input box for the whole grid and for layers one to three, for layer one KRWR is set equal to 0.755, for layer two KRWR equals 0.775, and for layer three KRWR equals 0.800.\n--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS (NX=100, NY=100)\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1* 1* 1* 1* 1 3 / DEFINE BOX AREA\n--\n-- SET KRWR VALUES FOR THREE LAYERS IN THE MODEL\n--\nKRWR\n10000*0.755 10000*0.775 10000*0.800 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX\nThe next example does exactly the same thing using the EQUALS keyword instead.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nKRWR 0.7550 1* 1* 1* 1* 1 1 / KRWR FOR LAYER 1\nKRWR 0.7750 1* 1* 1* 1* 2 2 / KRWR FOR LAYER 2\nKRWR 0.8000 1* 1* 1* 1* 3 3 / KRWR FOR LAYER 3\n/\n| No | Phases Present | Critical Saturation |\n|----|----------------|--------------------------------|\n| 1 | Gas-Oil | S critical = 1.0 – SOWCR - SGL |\n| 2 | Gas-Oil-Water | S critical = 1.0 – SOWCR - SGL |\n| 3 | Gas-Water | S critical = 1.0 – SGCR |"},"LANGMPL":{"name":"LANGMPL","sections":["PROPS"],"supported":false,"summary":"This keyword, LANGMPL, defines the coal bed methane Langmuir Adsorption195\n Langmuir, Irving (June 1918). \"The Adsorption of Gases on Plane Surface of Glass, Mica and Platinum\". The Research Laboratory of the General Electric Company. 40 (9): 1361–1402. doi:10.1021/ja02242a004 pressure multiplier for each grid block, for when the Coal Bed Methane option has been activated via the COAL keyword in the RUNSPEC section. The keyword applies the multiplier to the pressure values in a cell’s allocated Langmuir table when calculating a cell’s adsorption capacity. See the LANGMUIR keyword in the PROPS section for specifying the Langmuir tables for the model.","parameters":[],"example":"","size_kind":"array"},"LANGMUIR":{"name":"LANGMUIR","sections":["PROPS"],"supported":false,"summary":"The LANGMUIR keyword defines the coal bed methane Langmuir Adsorption Isotherms196\n Langmuir, Irving (June 1918). \"The Adsorption of Gases on Plane Surface of Glass, Mica and Platinum\". The Research Laboratory of the General Electric Company. 40 (9): 1361–1402. doi:10.1021/ja02242a004 tables, for when the Coal Bed Methane option has been activated via the COAL keyword in the RUNSPEC section. See the COALNUM keyword in the GRID section for allocating the Langmuir tables to the grid blocks and also the LANGMPL keyword in the PROPS section for re-scaling the pressure values in the tables that are allocated to a cell.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Pressure","GasSurfaceVolume/Length*Length*Length","GasSurfaceVolume/Length*Length*Length"]}],"example":"","size_kind":"fixed","variadic_record":true},"LANGSOLV":{"name":"LANGSOLV","sections":["PROPS"],"supported":false,"summary":"The LANGMUIR keyword defines the coal bed methane Langmuir Adsorption Isotherms197\n Langmuir, Irving (June 1918). \"The Adsorption of Gases on Plane Surface of Glass, Mica and Platinum\". The Research Laboratory of the General Electric Company. 40 (9): 1361–1402. doi:10.1021/ja02242a004 Solvent tables, for when the Coal Bed Methane option has been activated via the COAL keyword and the Solvent phase has been declared by the SOLVENT keyword in the RUNSPEC section. See the COALNUM keyword in the GRID section for allocating the Langmuir solvent tables to the grid blocks, and also the LANGMUIR keyword in the PROPS section for defining the Langmuir Adsorption Isotherm tables. Keywords COALADS and COALPP, also in the PROPS section, are used to specify the relative adsorption data in runs containing the solvent phase.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Pressure","GasSurfaceVolume/Length*Length*Length"]}],"example":"","size_kind":"fixed","variadic_record":true},"LCUNIT":{"name":"LCUNIT","sections":["PROPS"],"supported":false,"summary":"The LCUNIT keyword defines the units for the Linear Combination facility which allows for a linear combination of oil, gas and water rates and volumes to be used as combination targets and constraints in controlling group and well production and injection data. See also the LINCOM in the SCHEDULE section that defines the actual linear combination equation.","parameters":[{"index":1,"name":"UNIT","description":"","units":{},"default":"UNIT","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"LKRO":{"name":"LKRO","sections":["PROPS"],"supported":false,"summary":"LKRO defines the scaling parameter for the oil relative permeability value at the connate water saturation (SWL), for all the cells in the model via an array, for when the Low Salt option and the End-point Scaling options has been activated by the LOWSALT and the ENDSCALE keywords in the RUNSPEC section. The data is used to scale the oil relative permeability in the low salinity oil wet oil relative permeability saturation tables.","parameters":[],"example":"","size_kind":"array"},"LKRORG":{"name":"LKRORG","sections":["PROPS"],"supported":false,"summary":"LKRORG defines the scaling parameter for the relative permeability of oil at the critical gas saturation (SGCR), for all the cells in the model via an array, for when the Low Salt option and the End-point Scaling options has been activated by the LOWSALT and the ENDSCALE keywords in the RUNSPEC section. The data is used to scale the oil relative permeability in the low salinity oil wet oil relative permeability saturation tables.","parameters":[],"example":"","size_kind":"array"},"LKRORW":{"name":"LKRORW","sections":["PROPS"],"supported":false,"summary":"LKRORW defines the scaling parameter for the relative permeability of oil at the critical water saturation (SWCR), for all the cells in the model via an array, for when the Low Salt option and the End-point Scaling options has been activated by the LOWSALT and the ENDSCALE keywords in the RUNSPEC section. The data is used to scale the oil relative permeability in the low salinity oil wet oil relative permeability saturation tables.","parameters":[],"example":"","size_kind":"array"},"LKRW":{"name":"LKRW","sections":["PROPS"],"supported":false,"summary":"LKRW defines the scaling parameter at the maximum oil relative permeability value (SWU), that is for Sw = 1.0, for all the cells in the model via an array, for when the Low Salt option and the End-point Scaling options has been activated by the LOWSALT and the ENDSCALE keywords in the RUNSPEC section. The data is used to scale the water relative permeability in the low salinity oil wet water relative permeability saturation tables.","parameters":[],"example":"","size_kind":"array"},"LKRWR":{"name":"LKRWR","sections":["PROPS"],"supported":false,"summary":"LKRWR defines the scaling parameter at the maximum oil relative permeability value (SWU), that is for Sw = 1.0, for all the cells in the model via an array, for when the Low Salt option and the End-point Scaling options has been activated by the LOWSALT and the ENDSCALE keywords in the RUNSPEC section. The data is used to scale the water relative permeability in the low salinity oil wet water relative permeability saturation tables.","parameters":[],"example":"","size_kind":"array"},"LPCW":{"name":"LPCW","sections":["PROPS"],"supported":false,"summary":"LPCW defines the maximum oil-water pressure values for all the cells in the model via an array, for when the Low Salt option and the End-point Scaling options has been activated by the LOWSALT and the ENDSCALE keywords in the RUNSPEC section. The keyword re-scales the oil-water capillary pressure in the low salinity oil wet capillary saturation tables from a cell’s assigned saturation function by the grid block’s LPCW value.","parameters":[],"example":"| [P sub c ~=~P sub{ c sub{TABLE} } LEFT( LPCW OVER {P SUB {c sub {TABLE-MAX }}} RIGHT)] | (8.64) |\n|-----------------------------------------------------------------------------------------|--------|","size_kind":"array"},"LSALTFNC":{"name":"LSALTFNC","sections":["PROPS"],"supported":false,"summary":"The LSALTFNC keyword defines the low salt weighting factors versus salt concentration functions for when the Low Salt option has been activated by the LOWSALT keyword in the RUNSPEC section. The tables are used to modify the oil and water relative permeability saturation end-points, as well as the water-oil capillary pressure end-points, for different salt concentrations within a grid cell.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Pressure","1","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"LSOGCR":{"name":"LSOGCR","sections":["PROPS"],"supported":false,"summary":"LSOGCR defines the critical oil saturation with respect to gas (“SOGCR”), for all the cells in the model via an array, for when the Low Salt option has been selected. The data is used to scale the oil saturation in the low salinity oil wet oil-gas relative permeability saturation tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"LSOWCR":{"name":"LSOWCR","sections":["PROPS"],"supported":false,"summary":"LSOWCR defines the critical oil saturation with respect to water (“SOWCR”), for all the cells in the model via an array, for when the Low Salt option has been selected. The data is used to scale the oil saturation in the low salinity oil wet water-oil relative permeability saturation tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"LSWCR":{"name":"LSWCR","sections":["PROPS"],"supported":false,"summary":"LSWCR defines the critical water saturation (“SWCR”), for all the cells in the model via an array, for when the Low Salt option has been selected. The data is used to scale the water saturation in the low salinity oil wet water-oil relative permeability saturation tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"LSWL":{"name":"LSWL","sections":["PROPS"],"supported":false,"summary":"LSWL defines the connate water saturation (“SWL”), for all the cells in the model via an array, for when the Low Salt option has been selected. The data is used to scale the water saturation in the low salinity oil wet water-oil relative permeability saturation tables, as well as the associated capillary pressure tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"LSWLPC":{"name":"LSWLPC","sections":["PROPS"],"supported":false,"summary":"LSWLPC defines the capillary pressure connate water saturation (“SWLPC”), for all the cells in the model via an array, for when the Low Salt option has been selected. The data is used to scale the water saturation in the low salinity oil wet water-oil capillary pressure tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"LSWU":{"name":"LSWU","sections":["PROPS"],"supported":false,"summary":"LSWU defines the maximum water saturation(“SWU”), for all the cells in the model via an array, for when the Low Salt option has been selected. The data is used to scale the water saturation in the low salinity oil wet water-oil relative permeability saturation tables, as well as the associated capillary pressure tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"LWKRO":{"name":"LWKRO","sections":["PROPS"],"supported":false,"summary":"LWKRO defines the scaling parameter for the oil relative permeability value at the connate water saturation (SWL), for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The data is used to scale the oil relative permeability in the low salinity water wet oil relative permeability saturation tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"LWKRORG":{"name":"LWKRORG","sections":["PROPS"],"supported":false,"summary":"LWKRORG defines the scaling parameter for the relative permeability of oil at the critical gas saturation (SGCR), for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The data is used to scale the oil relative permeability in the low salinity water wet oil relative permeability saturation tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"LWKRORW":{"name":"LWKRORW","sections":["PROPS"],"supported":false,"summary":"LWKRORW defines the scaling parameter for the relative permeability of oil at the critical water saturation (SWCR), for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The data is used to scale the oil relative permeability in the low salinity water wet oil relative permeability saturation tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"LWKRW":{"name":"LWKRW","sections":["PROPS"],"supported":false,"summary":"LWKRW defines the scaling parameter at the maximum water relative permeability value (SWU), that is for Sw = 1.0, for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The data is used to scale the water relative permeability in the low salinity water wet water relative permeability saturation tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"LWKRWR":{"name":"LWKRWR","sections":["PROPS"],"supported":false,"summary":"LWKRWR defines the scaling parameter at the critical oil to water saturation value (SOWCR), for the water relative permeability curve, for all the cells in the model via an array, and for when the Low Salt and Surfactant Wettability options have been selected. The data is used to scale the water relative permeability in the low salinity water wet water relative permeability saturation tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"LWPCW":{"name":"LWPCW","sections":["PROPS"],"supported":false,"summary":"LWPCW defines the maximum water-oil pressure values for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section. The keyword re-scales the oil-water capillary pressure in the low salinity water wet capillary saturation tables from the cell’s assigned saturation function by the grid block’s LWPCW value.","parameters":[],"example":"| [P sub c ~=~P sub{ c sub{TABLE} } LEFT( HWPCW OVER {P SUB {c sub {TABLE-MAX }}} RIGHT)] | (8.65) |\n|------------------------------------------------------------------------------------------|--------|","size_kind":"array"},"LWSOGCR":{"name":"LWSOGCR","sections":["PROPS"],"supported":false,"summary":"LWSOGCR defines the critical oil saturation with respect to gas (“SOGCR”), for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The data is used to scale the oil saturation in the low salinity water wet oil-gas relative permeability saturation tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"LWSOWCR":{"name":"LWSOWCR","sections":["PROPS"],"supported":false,"summary":"LWSOWCR defines the critical oil saturation with respect to water (“SOWCR”), for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The data is used to scale the oil saturation in the low salinity water wet water-oil relative permeability saturation tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"LWSWCR":{"name":"LWSWCR","sections":["PROPS"],"supported":false,"summary":"LWSWCR defines the critical water saturation (“SWCR”), for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The data is used to scale the water saturation in the low salinity water wet water-oil relative permeability saturation tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"LWSWL":{"name":"LWSWL","sections":["PROPS"],"supported":false,"summary":"LWSWL defines the connate water saturation (“SWL”), for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The data is used to scale the water saturation in the low salinity water wet water-oil relative permeability saturation tables, as well as the associated capillary pressure tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"LWSWLPC":{"name":"LWSWLPC","sections":["PROPS"],"supported":false,"summary":"LWSWLPC defines the capillary pressure connate water saturation (“SWLPC”), for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The data is used to scale the water saturation in the low salinity water wet water-oil capillary pressure tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"LWSWU":{"name":"LWSWU","sections":["PROPS"],"supported":false,"summary":"LWSWU defines the maximum water saturation(“SWU”), for all the cells in the model via an array, for when the Low Salt and Surfactant Wettability options have been selected. The data is used to scale the water saturation in the low salinity water wet water-oil relative permeability saturation tables, as well as the associated capillary pressure tables. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the Low Salt option should be activated by the LOWSALT keyword in the RUNSPEC section and the Surfactant Wettability option activated by the SURFACT or SURFACTW keywords, which are also in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"MASSFLOW":{"name":"MASSFLOW","sections":["PROPS"],"supported":false,"summary":"The MASSFLOW keyword defines the upstream river mass flow versus time tables for rivers, for when the River option has been activated via the RIVRDIMS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"WORD","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","size_kind":"list","variadic_record":true},"MICPPARA":{"name":"MICPPARA","sections":["PROPS"],"supported":null,"summary":"The MICPPARA keyword used to define the model parameters for when the MICP model had been activated via the MICP keyword in the RUNSPEC section.","parameters":[],"example":""},"MISC":{"name":"MISC","sections":["PROPS"],"supported":null,"summary":"MISC defines the transformation between the miscible and immiscible relative permeability models, for when the MISCIBLE and SOLVENT keywords in the RUNSPEC section have been activated. The keyword can only be used with the MISCIBLE option and for when the oil, water, gas and solvent phases are active in the model.","parameters":[{"index":1,"name":"SSOL","description":"A columnar vector of real monotonically increasing down the column values starting from zero and terminating at one, that defines the solvent fraction with respect to the solvent and gas saturation, and is defined by: [S sub s over { left(S sub g ~+~ S sub s right) }] Where Sg is the gas saturation and Ss is the solvent saturation. Note that the first entry in the columnar vector should be zero and the last entry should be one to fully define the solvent fraction range.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":["1","1"]},{"index":2,"name":"MISC","description":"A columnar vector of real equal or increasing down the column values that are greater than or equal to zero and less then one, that define the corresponding miscibility for the corresponding solvent fraction SSOL. The first entry in the columnar vector should be zero and the last entry should be one to fully define the miscible-immiscible relationship.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- SOLVENT MISCIBILITY-IMMISCIBLITY TRANSFORM TABLE\n--\nMISC\n-- SSOL MISC\n-- FRAC FRAC\n-- ------- --------\n0.0000 0.0000\n0.2000 0.2500\n0.5000 0.7500\n1.0000 1.0000 / TABLE NO. 01\n-- SSOL MISC\n-- FRAC FRAC\n-- ------- --------\n0.0000 0.0000\n0.3000 0.2500\n0.6000 1.0000\n1.0000 1.0000 / TABLE NO. 02\nThe above example defines two solvent miscible-immiscible transform tables assuming NTMISC equals two and NSMISC is greater than or equal to four on the MISCIBLE keyword in the RUNSPEC section.","size_kind":"fixed","variadic_record":true},"MLANG":{"name":"MLANG","sections":["PROPS"],"supported":false,"summary":"This keyword, MLANG, defines the coal bed methane Langmuir Adsorption200\n Langmuir, Irving (June 1918). \"The Adsorption of Gases on Plane Surface of Glass, Mica and Platinum\". The Research Laboratory of the General Electric Company. 40 (9): 1361–1402. doi:10.1021/ja02242a004 maximum gas concentration for each grid cell used to scale the Langmuir isotherm table allocated to the cell, for when the Coal Bed Methane option has been activated via the COAL keyword in the RUNSPEC section. See the LANGMUIR keyword in the PROPS section for specifying the Langmuir tables for the model.","parameters":[],"example":"","size_kind":"array"},"MLANGSLV":{"name":"MLANGSLV","sections":["PROPS"],"supported":false,"summary":"This keyword, MLANGSLV, defines the coal bed methane Langmuir Adsorption201\n Langmuir, Irving (June 1918). \"The Adsorption of Gases on Plane Surface of Glass, Mica and Platinum\". The Research Laboratory of the General Electric Company. 40 (9): 1361–1402. doi:10.1021/ja02242a004 maximum solvent concentration for each grid cell used to scale the Langmuir isotherm solvent table allocated to the cell, for when the Coal Bed Methane option has been activated via the COAL keyword in the RUNSPEC section. In addition, the Solvent phase must have been declared by the SOLVENT keyword in the RUNSPEC section. See the COALNUM keyword in the GRID section for allocating the Langmuir solvent tables to the grid blocks, and also the LANGMUIR keyword in the PROPS section for defining the Langmuir Adsorption Isotherm tables. Keywords COALADS and COALPP, also in the PROPS section, are used to specify the relative adsorption data in runs containing the solvent phase.","parameters":[],"example":"","size_kind":"array"},"MSFN":{"name":"MSFN","sections":["PROPS"],"supported":null,"summary":"The MSFN keyword defines the miscible normalized relative permeability tables for when the MISCIBLE and or SOLVENT options have been activated in the RUNSPEC section using the respective keyword. The MISCIBLE keyword invokes a three component formulation (oil, water and solvent gas or an oil, water and solvent oil). Whereas the SOLVENT keyword results in a four component model (oil, water and gas plus a solvent). This keyword should only be used if the MISCIBLE and or SOLVENT options have been activated.","parameters":[{"index":1,"name":"SGAS","description":"A columnar vector of real monotonically increasing down the column values starting from zero and terminating at one, that defines the gas plus solvent saturation.","units":{},"default":"None","value_type":"DOUBLE","dimension":["1","1","1"]},{"index":2,"name":"KRSG","description":"A columnar vector of real values that are either equal or increasing down the column and that are greater than or equal to zero and less than or equal to one that defines the gas plus solvent relative permeability multiplier.","units":{},"default":"None"},{"index":3,"name":"KRO","description":"A columnar vector of real values that are either equal or increasing down the column and that are greater than or equal to zero and less than or equal to one that defines the oil relative permeability multiplier.","units":{},"default":"None"}],"example":"--\n-- MISCIBLE NORMALIZED RELATIVE PERMEABILITY TABLES\n--\nMSFN\n-- SGAS KRSG KRO\n-- FRAC\n-- -------- -------- --------\n0.0000 0.0000 1.0000\n1.0000 1.0000 0.0000 / TABLE NO. 01\n-- SGAS KRSG KRO\n-- FRAC\n-- -------- -------- --------\n0.0000 0.0000 1.0000\n0.2000 0.2000 0.8000\n0.4000 0.3000 0.7000\n0.6000 0.4000 0.6000\n0.8000 0.5000 0.4000\n1.0000 1.0000 0.0000 / TABLE NO. 02\nThe above example defines two MSN tables for use the MISCIBLE and SOLVENT options.","size_kind":"fixed","variadic_record":true},"MW":{"name":"MW","sections":["PROPS"],"supported":false,"summary":"The MW keyword defines the molecular weights for each of the compositional components active in the model and for each equation of state. The keyword should only be used if the compositional mode has been requested using the COMPS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"MW","description":"A series of real numbers that define the molecular weights for each of the compositional components active in the model.","units":{"field":"lb/lb-M","metric":"kg/kg-M","laboratory":"gm/gm-M"},"default":"None","value_type":"DOUBLE","dimension":"Mass/Moles"}],"example":"The following example defines the molecular weights for each component in a single three-component equation of state model.\n--\n-- Molecular Weights\n--\nMW\n16.0425 44.009 18.01528 /\nThe following example defines the molecular weights for each component in two three-component equation of state models.\n--\n-- Molecular Weights\n--\nMW\n16.0425 44.009 18.01528 /\n16.0425 44.009 18.01528 /","size_kind":"fixed","variadic_record":true},"NCOMPS":{"name":"NCOMPS","sections":["PROPS"],"supported":true,"summary":"This keyword confirms the maximum number of compositional components in the model, as such it should have the same number of components as that declared via the COMPS keyword in the RUNSPEC section. The keyword should only be used if the CO2STORE keyword and either the GASWAT or the GAS and WATER keywords in the RUNSPEC section, have also be activated for the gas-water two component model.","parameters":[{"index":1,"name":"NCOMPS","description":"A positive integer defining the maximum number of compositional components in the model. Secondly the number of components must be the same as that enter via the COMPS keyword in the RUNSPEC section. Only the default value of two is currently supported by OPM Flow.","units":{},"default":"2","value_type":"INT"}],"example":"The following example defines how to confirm a two component formulation to be used with the CO2STORE and GASWAT options.\n--\n-- CONFIRM NUMBER OF COMPOSITIONAL COMPONENTS (OPM FLOW KEYWORD)\n--\nNCOMPS\n2 /\n| Note This is an OPM Flow keyword used with OPM Flow’s CO2STORE and GASWAT keywords in the RUNSPEC section, and should not be confused with the more general version of the NCOMPS keyword used in the commercial compositional simulator. Secondly, although OPM Flow parses the keyword, the simulator currently ignores the data for this keyword. |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":1,"size_kind":"fixed","size_count":1},"NOWARNEP":{"name":"NOWARNEP","sections":["PROPS"],"supported":null,"summary":"The NOWARNEP keyword deactivates the writing out of warning messages associated with checking the consistency of saturation table end-points; however error messages are still reported by the simulator.","parameters":[],"example":"--\n-- DEACTIVATE END-POINT SCALING WARNING MESSAGES\n--\nNOWARNEP\nThe above example switches off the writing out of warning messages associated with checking the consistency of saturation table end-points;","size_kind":"none","size_count":0},"OILDENT":{"name":"OILDENT","sections":["PROPS"],"supported":null,"summary":"OILDENT defines the oil density as a function of temperature coefficients for when OPM Flow’s thermal option has been activated by the THERMAL keyword in the RUNSPEC. Note this is an OPM Flow keyword used with OPM Flow’s black-oil thermal model that is not available in the commercial simulator’s black-oil thermal formulation.","parameters":[{"index":1,"name":"TEMP","description":"TEMP is a real positive value greater than zero that defines the absolute reference temperature used with TEXP1 and TEXP2 to estimate the change in oil density with respect to temperature.","units":{"field":"oR 527.67","metric":"K 293.15","laboratory":"K 293.15"},"default":"Defined","value_type":"DOUBLE","dimension":"AbsoluteTemperature"},{"index":2,"name":"TEXP1","description":"TEXP1 is a real positive value greater than zero that defines the oil thermal expansion coefficient of the first order.","units":{"field":"1/oR 1.67 x 10-4","metric":"1/K 3.0 x 10-4","laboratory":"1/K 3.0 x 10-4"},"default":"Defined","value_type":"DOUBLE","dimension":"1/AbsoluteTemperature"},{"index":3,"name":"TEXP2","description":"TEXP2 is a real positive value greater than zero that defines the oil thermal expansion coefficient of the second order.","units":{"field":"1/oR2 9.26 x 10-7","metric":"1/K2 3.0 x 10-6","laboratory":"1/K2 3.0 x 10-6"},"default":"Defined","value_type":"DOUBLE","dimension":"1/AbsoluteTemperature*AbsoluteTemperature"}],"example":"The following example shows the OILDENT keyword using the default values, for when the thermal option has been activated by the THERMAL keyword in the RUNSPEC section and for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set to two.\n--\n-- OIL DENSITY TEMPERATURE COEFFICIENTS (OPM FLOW THERMAL KEYWORD)\n--\n-- OIL DENSITY DENSITY\n-- TEMP COEFF1 COEFF2\n-- -------- ------- -------\nOILDENT\n1* 1* 1* / TABLE NO. 01\n1* 1* 1* / TABLE NO. 02\nThere is no terminating “/” for this keyword.\n| [%rho_o( p, T ) = %rho_o( p_s, T_s ) b_o( p, T )] | (8.3.186.1) |\n|---------------------------------------------------|-------------|\n| [b_o( p, T ) = { b_o( p, T_ref ) } over { 1 + c_1 ( T - T_ref ) + c_2 ( T - T_ref )^2 }] | (8.3.186.2) |\n|------------------------------------------------------------------------------------------|-------------|","expected_columns":3,"size_kind":"fixed"},"OILJT":{"name":"OILJT","sections":["PROPS"],"supported":null,"summary":"OILJT activates the oil Joule-Thomson effect202\n The Joule–Thomson coefficient is defined as the change in temperature with respect to an increase in pressure at constant enthalpy. in temperature calculations, and defines the oil Joule-Thomson Coefficient (“JTC”) at a given reference pressure, for when OPM Flow’s thermal option has been activated by the THERMAL keyword in the RUNSPEC.","parameters":[{"index":1,"name":"PRESS","description":"A real positive value that defines the reference pressure for the corresponding Joule-Thomson Coefficient, OILJTC.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":"Pressure"},{"index":2,"name":"OILJTC","description":"OILJTC is a real positive or negative value that defines the oil phase Joule-Thomson Coefficient. If the value is defaulted (1*) or set to 0, then OILJTC is internally calculated using the thermal oil density data on the OILDENT keyword in the PROPS section. If a non-zero value is specified, then the OILJTC is assumed to be constant and equal to that value.","units":{"field":"oF/psia","metric":"oC/barsa","laboratory":"oC/atma"},"default":"0","value_type":"DOUBLE","dimension":"AbsoluteTemperature/Pressure"}],"example":"The following example shows the OILJT keyword for when the thermal option has been activated by the THERMAL keyword in the RUNSPEC section, and for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set equal to two.\n--\n-- OIL JOULE-THOMSON COEFFICIENT (OPM FLOW EXTENSION KEYWORD)\n--\n-- REF OIL\n-- PRESS JTC\n-- -------- -------\nOILJT\n20.0 1* / TABLE NO. 01\n20.0 -0.20 / TABLE NO. 02\nHere the first entry is defaulted, and the simulator will therefore calculate the oil JTC internally using the data on the OILDENT keyword in the PROPS section.\nThere is no terminating “/” for this keyword.\n| Note This is an OPM Flow keyword used with OPM Flow’s black-oil thermal model, that is not available in the commercial simulator’s black-oil thermal formulation. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| [%eta` `=`` left({ partial T} over {partial P} right)] | (8.66) |\n|--------------------------------------------------------|--------|\n| [%eta ``=`` left( T %alpha``-``1 right) 1 over( %rho C_p )``-`` left( g over C_p dp over dz right)^-1] | (8.67) |\n|--------------------------------------------------------------------------------------------------------|--------|\n| [%eta ``=`` left( T %alpha``-``1 right) 1 over( %rho C_b )] | (8.68) |\n|-------------------------------------------------------------|--------|","expected_columns":2,"size_kind":"fixed"},"OILVISCT":{"name":"OILVISCT","sections":["PROPS"],"supported":null,"summary":"OILVISCT defines the oil viscosity as a function of temperature for when OPM Flow’s thermal option has been activated by the THERMAL keyword in the RUNSPEC section. The reference pressure and solution gas-oil ratio of the oil for this table is given by the VISCREF keyword in the PROPS section. Note this is an OPM Flow keyword used with OPM Flow’s black-oil thermal model that is not available in the commercial simulator’s black-oil thermal formulation.","parameters":[{"index":1,"name":"TEMP","description":"A columnar vector of real monotonically increasing down the column values that defines the temperature values.","units":{"field":"oF","metric":"oC","laboratory":"oC"},"default":"None","value_type":"DOUBLE","dimension":["Temperature","Viscosity"]},{"index":2,"name":"VIS","description":"A columnar vector of real increasing down the column values that defines the oil viscosity for the corresponding temperature values (TEMP). VIS should be given at the reference pressure and solution gas-oil ratio as defined by PRESS and RS variables on the VISCREF keyword.","units":{"field":"cP","metric":"cP","laboratory":"cP"},"default":"None"}],"example":"The following example shows the OILVISCT keyword for when the thermal option has been activated by the THERMAL keyword in the RUNSPEC section and for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set equal to one.\n--\n-- OIL VISCOSITY VERSUS TEMPERATURE TABLES (OPM FLOW EXTENSION KEYWORD)\n--\n-- OIL OIL\n-- TEMP VISC\n-- -------- -------\nOILVISCT\n100.0 0.600\n110.0 0.650\n120.0 0.680\n150.0 0.720\n165.0 0.725 / TABLE NO. 01","size_kind":"fixed","variadic_record":true},"OVERBURD":{"name":"OVERBURD","sections":["PROPS"],"supported":null,"summary":"The OVERBURD keyword defines the overburden pressures versus depth relationship to be applied for when the rock compaction option has been invoked by the ROCKCOMP keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"DEPTH","description":"A columnar vector of real monotonically increasing down the column values that defines the depth for corresponding overburden pressure parameter PRESS.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":["Length","Pressure"]},{"index":2,"name":"PRESS","description":"A columnar vector of real monotonically increasing down the column values that defines the corresponding overburden pressure for the given DEPTH.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"None"}],"example":"The example below defines three overburden tables, assuming NTROCC is equal to three on the ROCKCOMP keyword and NPPVT is greater than or equal to four on the TABDIMS keyword.\n--\n-- OVERBURDEN PRESSURE VERSUS DEPTH TABLES\n--\nOVERBURD\n-- DEPTH OVERBURDEN\n-- FEET PRESSURE\n-- ------ ----------\n1000.0 300.000\n2000.0 600.000\n3000.0 900.000\n4000.0 1200.000 / TABLE N0. 01\n-- DEPTH OVERBURDEN\n-- FEET PRESSURE\n-- ------ ----------\n1000.0 200.000\n2000.0 400.000\n3000.0 800.000\n4000.0 1000.000 / TABLE N0. 02\n-- DEPTH OVERBURDEN\n-- FEET PRESSURE\n-- ------ ----------\n1000.0 400.000\n2000.0 800.000\n3000.0 1100.000\n4000.0 1500.000 / TABLE N0. 03\nNote that there must be exactly NTROCC tables entered for this keyword, otherwise an error will occur.\n--\n-- ROCK COMPACTION TABLES\n--\nROCKTAB\n-- PRESS PORV TX(YZ)\n-- MULT MULT\n-- ------ ------ ------\n1000.0 0.9600 0.9650\n1500.0 0.9800 0.9850\n3000.0 0.9900 0.9950\n4500.0 1.0000 1.0000\n4750.0 1.0100 1.0100 / TABLE NO. 01\n-- PRESS PORV TX(YZ)\n-- MULT MULT\n-- ------ ------ ------\n1000.0 0.9600 0.9650\n1500.0 0.9800 0.9850\n3000.0 0.9900 0.9950\n4500.0 1.0000 1.0000\n4750.0 1.0100 1.0100 / TABLE NO. 02\n-- PRESS PORV TX(YZ)\n-- MULT MULT\n-- ------ ------ ------\n1000.0 0.9600 0.9650\n2000.0 0.9800 0.9850\n3000.0 0.9900 0.9950\n4000.0 1.0100 1.0100 / TABLE NO. 03\nHere ROCKTAB tables one and two are identical.","size_kind":"fixed","variadic_record":true},"PCFACT":{"name":"PCFACT","sections":["PROPS"],"supported":null,"summary":"PCFACT defines the capillary pressure multiplication factor due to a change in porosity. Currently the keyword is used in conjunction with OPM Flow’s Salt Precipitation model, in which the pore space is reduced due to salt precipitating in the pore space, causing a reduction in porosity and an associated increase in capillary pressure.","parameters":[{"index":1,"name":"POROFAC","description":"A real monotonically increasing positive columnar vector that defines the porosity factor ([%phi over %phi sub 0]) for the corresponding PCFAC vector.) for the corresponding PCFAC vector. In the simulator’s Salt Precipitation model, the maximum value of [%phi]is [%phi sub 0], implying a maximum value of one for POROFAC., implying a maximum value of one for POROFAC.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":["1","1"]},{"index":2,"name":"PCFAC","description":"A real positive monotonically decreasing columnar vector that defines the capillary pressure ([p sub c]) multiplier associated with POROFAC and used to scale a grid block's capillary pressure due to the reduction in pore volume caused by salt precipitation. ) multiplier associated with POROFAC and used to scale a grid block's capillary pressure due to the reduction in pore volume caused by salt precipitation. Where: [PCFAC~=~ m left (%phi over %phi_0 right) newline\nwith `` p sub c~=~ m left (%phi over %phi_0 right) p sub c0]","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"The example below defines two PCFACT tables assuming NTSFUN equals two and NSSFUN is greater than or equal to five on the TABDIMS keyword in the RUNSPEC section.\n--\n-- CAPILLARY PRESSURE FACTOR INCREASE DUE TO SALT PRECIPITATION\n-- (OPM FLOW KEYWORD)\n--\nPCFACT\n-- PORO PC\n-- FACTOR FACTOR\n-- ------- --------\n0.00 2.0000\n0.25 2.0000\n0.50 1.4142\n0.75 1.1547\n1.00 1.0000 / TABLE NO. 01\n-- ------- --------\n0.00 2.0000\n0.25 2.0000\n0.50 1.4142\n0.75 1.1547\n1.00 1.0000 / TABLE NO. 02\nNote that the capillary pressure factor has been capped for POROFAC less than 0.25.\n| Note This is an OPM Flow specific keyword for the simulator’s Salt Precipitation model that is activated by the BRINE and PRECSALT keywords and declaring that vaporized water is present in the run via the VAPWAT keyword. All three keywords are in the RUNSPEC section. |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| [%phi ~=~ ( 1`-` s sub s) %phi sub 0] | (8.3.199.1) |\n|---------------------------------------|-------------|\n| [p sub c over p sub c0`=`left( {%phi over %phi sub 0} {k sub 0 over k} right) ^ {1 over 2}] | (8.3.199.2) |\n|----------------------------------------------------------------------------------------------|-------------|","size_kind":"fixed","variadic_record":true},"PCG":{"name":"PCG","sections":["PROPS"],"supported":false,"summary":"PCG defines the maximum drainage gas-oil capillary pressure values for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. The keyword can be used with all grid types.","parameters":[{"index":1,"name":"PCG","description":"PCG is an array of positive real numbers assigning the maximum drainage gas-oil capillary pressure values for each cell in the model. Repeat counts may be used, for example 30*100.0.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK PCG DATA FOR ALL CELLS (BASED ON NX x NY x NZ = 300)\n--\nPCG\n100*50.0 100*75.0 100*125.0 /\nThe above example defines the PCW for 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.\n| [P sub c ~=~P sub{ c sub{TABLE} } LEFT( PCG OVER {P SUB {c sub {TABLE-MAX }}} RIGHT)] | (8.69) |\n|----------------------------------------------------------------------------------------|--------|","size_kind":"array"},"PCG32D":{"name":"PCG32D","sections":["PROPS"],"supported":false,"summary":"This keyword, PCG32D, enables the gas-oil capillary pressure data to be entered as a function of both oil and water saturations. The keyword should be used in conjunction with the SGF32D keyword in the PROPS section. See also the PCW32D keyword in the PROPS section that provides similar functionality for the water-oil capillary pressure data.","parameters":[{"index":1,"name":"SOME_DATA","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","size_kind":"list","variadic_record":true},"PCRIT":{"name":"PCRIT","sections":["PROPS"],"supported":false,"summary":"The PCRIT keyword defines the critical pressures for each of the compositional components active in the model and for each equation of state. The keyword should only be used if the compositional mode has been requested using the COMPS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"PCRIT","description":"A series of real numbers that define the critical pressures for each of the compositional components active in the model.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":"Pressure"}],"example":"The following example defines the critical pressures for each component in a single three-component equation of state model.\n--\n-- Critical Pressures\n--\nPCRIT\n1070.132 667.0576 616.5844 /\nThe following example defines the critical pressures for each component in two three-component equation of state models.\n--\n-- Critical Pressures\n--\nPCRIT\n1070.132 667.0576 616.5844 /\n1070.132 667.0576 616.5844 /","size_kind":"fixed","variadic_record":true},"PCW":{"name":"PCW","sections":["PROPS"],"supported":false,"summary":"PCW defines the maximum drainage water-oil or water-gas capillary pressure values for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. The keyword can be used with all grid types.","parameters":[{"index":1,"name":"PCW","description":"PCW is an array of positive real numbers assigning the maximum drainage water capillary pressure values for each cell in the model. Repeat counts may be used, for example 30*100.0.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK PCW DATA FOR ALL CELLS (BASED ON NX x NY x NZ = 300)\n--\nPCW\n100*50.0 100*75.0 100*125.0 /\nThe above example defines the PCW for 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.\n| [P sub c ~=~P sub{ c sub{TABLE} } LEFT( PCW OVER {P SUB {c sub {TABLE-MAX }}} RIGHT)] | (8.70) |\n|----------------------------------------------------------------------------------------|--------|","size_kind":"array"},"PCW32D":{"name":"PCW32D","sections":["PROPS"],"supported":false,"summary":"This keyword, PCW32D, enables the water-oil capillary pressure data to be entered as a function of both oil and gas saturations. The keyword should be used in conjunction with the SWF32D keyword in the PROPS section. See also the PCG32D keyword in the PROPS section that provides similar functionality for the gas-oil capillary pressure data.","parameters":[{"index":1,"name":"SOME_DATA","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","size_kind":"list","variadic_record":true},"PECOEFS":{"name":"PECOEFS","sections":["PROPS"],"supported":false,"summary":"The PECOEFS keyword defines the Petro-Elastic model coefficients.","parameters":[{"index":1,"name":"WAT_SALINITY","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":2,"name":"TEMP","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Temperature"},{"index":3,"name":"MINERAL_DENSITY","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Density"},{"index":4,"name":"PHI_EFF_0","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":5,"name":"PHI_EFF_1","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":6,"name":"C_0","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":7,"name":"C_K","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":8,"name":"SHEAR_MOD","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":9,"name":"ALPHA","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"},{"index":10,"name":"E","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"},{"index":11,"name":"METHOD","description":"","units":{},"default":"0","value_type":"INT"}],"example":"","expected_columns":11,"size_kind":"list"},"PEGTAB":{"name":"PEGTAB","sections":["PROPS"],"supported":null,"summary":"The PEGTAB series of keywords define a series of coefficients of a polynomial function used in the calculation of the shear modulus in the petro-elastic model. The series of keywords consist of: PEGTAB0 PEGTAB1, PEGTAB2, PEGTAB3, PEGTAB4, PEGTAB5, PEGTAB6, and PEGTAB7.","parameters":[],"example":""},"PEKTAB":{"name":"PEKTAB","sections":["PROPS"],"supported":null,"summary":"The PEKTAB series of keywords define a series of coefficients of a polynomial function used in the calculation of the bulk modulus in the petro-elastic model. The series of keywords consist of: PEKTAB0 PEKTAB1, PEKTAB2, PEKTAB3, PEKTAB4, PEKTAB5, PEKTAB6, and PEKTAB7.","parameters":[],"example":""},"PERMFACT":{"name":"PERMFACT","sections":["PROPS"],"supported":null,"summary":"PERMFACT defines the permeability multiplication factor due to a change in porosity. The keyword is used in conjunction with OPM Flow’s Salt Precipitation model, in which the pore space is reduced due to salt precipitating in the pore space, causing a reduction in porosity and an associated reduction in permeability. This keyword is also used for the BIOFILM and MICP model, where the pore space is reduced due to biofilm formation, and for the MICP model, also due to calcite precipitation.","parameters":[{"index":1,"name":"POROFAC","description":"A real monotonically increasing positive columnar vector that defines the porosity ([%phi over %phi sub 0]) factor for the corresponding PERMFAC vector.) factor for the corresponding PERMFAC vector. In the simulator’s Salt Precipitation model, the maximum value of [%phi]is [%phi sub 0], implying a maximum value of one for POROFAC., implying a maximum value of one for POROFAC.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":["1","1"]},{"index":2,"name":"PERMFAC","description":"A real positive monotonically increasing columnar vector that defines the permeability (k) multiplier associated with POROFAC and used to scale a grid block's permeability due to the reduction in pore volume caused by salt precipitation. Where: [PERMFAC~=~ m left (%phi right) newline\nwith `` k~=~ m left (%phi right) k sub 0]","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"The example below defines two PERMFACT tables assuming NTSFUN equals two and NSSFUN is greater than or equal to five on the TABDIMS keyword in the RUNSPEC section.\n--\n-- PERMEABILITY FACTOR AS A FUNCTION OF POROSITY REDUCTION\n-- (OPM FLOW KEYWORD)\n--\nPERMFACT\n-- PORO PERM\n-- FACTOR FACTOR\n-- ------- --------\n0.00 0.0000\n0.25 0.0625\n0.50 0.2500\n0.75 0.5625\n1.00 1.0000 / TABLE NO. 01\n-- ------- --------\n0.00 0.0000\n0.25 0.0625\n0.50 0.2500\n0.75 0.5625\n1.00 1.0000 / TABLE NO. 02\nBoth tables use equation (8.72)with Φc equal to zero and ɣ equal to 2.0. Note that PERMFACT changes the permeability in all three dimensions, that is the PERMX, PERMY and PERMZ arrays are all modified.\n| Note This is an OPM Flow specific keyword. |\n|--------------------------------------------|\n| [%phi ~=~ ( 1`-` s sub s) %phi sub o] | (8.71) |\n|---------------------------------------|--------|\n| [k over k sub o`=`left( {%phi - %phi sub c} over {%phi sub o - %phi sub c} right) sup %gamma] | (8.72) |\n|------------------------------------------------------------------------------------------------|--------|","size_kind":"fixed","variadic_record":true},"PLMIXPAR":{"name":"PLMIXPAR","sections":["PROPS"],"supported":null,"summary":"The PLMIXPAR keyword defines the Todd-Longstaff210\n Todd, M. and Longstaff, W. “The Development, Testing and Application of a Numerical Simulator for Predicting Miscible Flood Performance,” paper SPE 3484, Journal of Canadian Petroleum Technology (1972) 24, No. 7, 874-882. mixing parameters for when the polymer option has been activated by the POLYMER keyword in the RUNSPEC section. This keyword must be present in the input deck if the POLYMER keyword has been activated.","parameters":[{"index":1,"name":"PLMVIS","description":"A real positive value that is greater than or equal to zero and less than or equal to one, that defines the viscosity Todd-Longstaff mixing parameter for each polymer region.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":"1"}],"example":"--\n-- POLYMER TODD-LONGSTAFF MIXING PARAMETERS\n--\nPLMIXPAR\n-- PLM\n-- VISCOS\n-- -------\n0.3500 / TABLE NO. 01\n0.2500 / TABLE NO. 02\n0.6500 / TABLE NO. 03\nThe above example defines three polymer Todd-Longstaff mixing parameter data sets, based on the NPLMIX variable on the REGDIMS keyword in the RUNSPEC section being equal to three.","size_kind":"fixed","variadic_record":true},"PLYADS":{"name":"PLYADS","sections":["SPECIAL","PROPS"],"supported":null,"summary":"The PLYADS keyword defines the rock polymer adsorption tables for when the polymer option has been activated by the POLYMER keyword in the RUNSPEC section. Alternatively, the functions can be entered via the PLYADSS keyword in the PROPS section for when salt sensitivity is to be considered.","parameters":[{"index":1,"name":"POLCON","description":"A columnar vector of real monotonically increasing down the column values that defines the polymer concentration in the solution surrounding the rock. The first entry should be zero to define a no polymer concentration.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None","value_type":"DOUBLE","dimension":["Concentration","1"]},{"index":2,"name":"POLRATIO","description":"A columnar vector of real increasing down the column values that defines the mass of adsorbed polymer per unit mass of rock. The first entry should be zero to define a zero ratio of polymer concentration.","units":{"field":"lb/lb","metric":"kg/kg","laboratory":"gm/gm"},"default":"None"}],"example":"--\n-- POLYMER ROCK ADSORPTION TABLE\n--\nPLYADS\n-- POLYMER POLYMER\n-- POLCON POLRATIO\n-- ------- --------\n0.0 0.00000\n2.0 0.00003\n4.0 0.00005\n6.0 0.00007\n8.0 0.00009\n10.0 0.00011\n12.0 0.00012\n14.0 0.00015 / TABLE NO. 01\n-- POLYMER POLYMER\n-- POLCON POLRATIO\n-- ------- --------\n0.0 0.00000\n3.0 0.00004\n5.0 0.00006\n7.0 0.00008\n8.0 0.00009\n10.0 0.00011 / TABLE NO. 02\nThe above example defines two polymer rock adsorption tables assuming NTSFUN equals two and NSSFUN is greater than or equal to eight on the TABDIMS keyword in the RUNSPEC section.\nThere is no terminating “/” for this keyword.","size_kind":"fixed","variadic_record":true},"PLYADSS":{"name":"PLYADSS","sections":["PROPS"],"supported":true,"summary":"The PLYADSS keyword defines the rock polymer adsorption tables for when the polymer and the salt options has been activated by the POLYMER and BRINE keywords in the RUNSPEC section.","parameters":[{"index":1,"name":"POLCON","description":"A columnar vector of real monotonically increasing down the column values that defines the polymer concentration in the solution surrounding the rock. The first entry should be zero to define a no polymer and no salt concentration data set. POLCON should only be given for the first entry of the POLCON/POLRATIO set and skipped until another POLCON/POLRATIO table is entered.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None","value_type":"DOUBLE","dimension":"Concentration"},{"index":2,"name":"POLRATIO","description":"A columnar vector of real increasing down the column values that defines the mass of adsorbed polymer per unit mass of rock of the saturated concentration of polymer adsorbed by the rock for a given POLCON and the salt concentration given by SALTCON on the ADSALNOD keyword in the PROPS section. The first table data set entry should be zero to define a no polymer and no salt concentration data set. Subsequent POLRATIO values define the POLCON/POLRATIO combinations for a given salt concentration as listed (and in the same order) by the SALTCON variable on the ADSALNOD keyword in the PROPS section. Each POLCON/POLRATIO/SALT data sets should be terminated by a “/”","units":{"field":"lb/lb","metric":"kg/kg","laboratory":"gm/gm"},"default":"None","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"--\n-- SETS SALT CONCENTRATION FOR POLYMER SOLUTION ADSORPTION\n-- VIA SATNUM ARRAY ALLOCATION\n--\n-- SALT\n--\nADSALNOD\n1.0\n5.0\n10.5\n25.0 / SATNUM TABLE NO. 01\n--\n-- POLYMER ROCK ADSORPTION WITH SALT DEPENDENCY TABLE\n--\nPLYADSS\n-- POLYMER POLYMER\n-- POLCON POLRATIO\n-- ------- --------\n0.0 0.00000\n0.00000\n0.00000\n0.00000 / TABLE NO. 01\n-- POLYMER POLYMER\n-- POLCON POLRATIO\n-- ------- --------\n1.0 0.00002\n0.00003\n0.00004\n0.00005 / TABLE NO. 02\n-- POLYMER POLYMER\n-- POLCON POLRATIO\n-- ------- --------\n2.0 0.00003\n0.00004\n0.00005\n0.00006 / TABLE NO. 03\n-- POLYMER POLYMER\n-- POLCON POLRATIO\n-- ------- --------\n3.0 0.00004\n0.00005\n0.00006\n0.00007 / TABLE NO. 04\nThe above example defines four polymer rock adsorption tables for four salt concentration on the ADSALNOD keyword, assuming NTSFUN equals one and NSSFUN is greater than or equal to four on the TABDIMS keyword in the RUNSPEC section.\nThere is no terminating “/” for this keyword.","size_kind":"list","variadic_record":true},"PLYATEMP":{"name":"PLYATEMP","sections":["PROPS"],"supported":false,"summary":"This keyword defines the polymer adsorption temperature for subsequent polymer adsorption tables entered via the PLYADS and PLYADSS keywords in the PROPS section. The Polymer option must have been activated by the POLYMER keyword in the RUNSPEC section and the Thermal option invoked by the THERMAL keyword, also in the RUNSPEC section.","parameters":[{"index":1,"name":"PLYATEMP","description":"Single real positive value that defines polymer adsorption temperature for subsequent polymer adsorption tables.","units":{"field":"oF","metric":"oC","laboratory":"oC"},"default":"None"}],"example":"The example shows how to enter the polymer adsorption data using the PLYADS keyword for two different temperatures.\n--\n-- RESERVOIR\n-- TEMPERATURE\n-- -----------\nPLYATEMP\n60.0 / TEMPERATURE\n--\n-- POLYMER ROCK ADSORPTION TABLE\n--\nPLYADS\n-- POLYMER POLYMER\n-- POLCON POLRATIO\n-- ------- --------\n0.0 0.00000\n2.0 0.00003\n4.0 0.00005\n6.0 0.00007\n8.0 0.00009\n10.0 0.00011\n12.0 0.00012\n14.0 0.00015 / TABLE NO. 01\n--\n-- POLYMER POLYMER\n-- POLCON POLRATIO\n-- ------- --------\n0.0 0.00000\n3.0 0.00004\n5.0 0.00006\n7.0 0.00008\n8.0 0.00009\n10.0 0.00011 / TABLE NO. 02\n--\n-- RESERVOIR\n-- TEMPERATURE\n-- -----------\nPLYATEMP\n120.0 / TEMPERATURE\n--\n-- POLYMER ROCK ADSORPTION TABLE\n--\nPLYADS\n-- POLYMER POLYMER\n-- POLCON POLRATIO\n-- ------- --------\n0.0 0.00000\n2.0 0.00003\n4.0 0.00005\n6.0 0.00007\n8.0 0.00009\n10.0 0.00011\n12.0 0.00012\n14.0 0.00015 / TABLE NO. 01\n--\n-- POLYMER POLYMER\n-- POLCON POLRATIO\n-- ------- --------\n0.0 0.00000\n3.0 0.00004\n5.0 0.00006\n7.0 0.00008\n8.0 0.00009\n10.0 0.00011 / TABLE NO. 02\nHere the first PLYATEMP keyword defines the temperature to be 60 oF for the subsequent two polymer rock adsorption tables, assuming NTSFUN equals four and NSSFUN is greater than or equal to eight on the TABDIMS keyword in the RUNSPEC section. The next PLYATEMP keyword defines the temperature to be 120 oF for the subsequent two polymer rock adsorption tables.","size_kind":"array"},"PLYCAMAX":{"name":"PLYCAMAX","sections":["PROPS"],"supported":false,"summary":"The PLYCAMAX keyword defines the maximum polymer-rock adsorption value used in the calculation of the resistance factor for the water phase by individual grid block, for when the Polymer option has been activated by the POLYMER keyword in the RUNSPEC section. See the POLMAX parameter on the PLYROCK keyword in the PROPS section for setting the property for the whole grid.","parameters":[],"example":"","size_kind":"array"},"PLYDHFLF":{"name":"PLYDHFLF","sections":["SPECIAL","PROPS","SCHEDULE"],"supported":false,"summary":"The PLYDHFLF keyword defines the polymer thermal degradation half-life with respect to temperature functions for when the polymer option has been activated by the POLYMER keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"TEMP","description":"A columnar vector of real monotonically increasing down the column values that defines the polymer thermal degradation temperature.","units":{"field":"oF","metric":"oC","laboratory":"oC"},"default":"None","value_type":"DOUBLE","dimension":["Temperature","Time"]},{"index":2,"name":"POLHFLF","description":"A columnar vector of real values that defines the corresponding polymer half-life.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"None"}],"example":"--\n-- POLYMER THERMAL DEGRADATION HALF-LIFE TABLE\n--\nPLYDHFLF\n-- POLYMER POLYMER\n-- TEMP HALF-LIFE\n-- ------- ---------\n0.0 365.000\n40.0 200.000\n80.0 150.000\n120.0 100.000 / TABLE NO. 01\n-- POLYMER POLYMER\n-- TEMP HALF-LIFE\n-- ------- --------\n0.0 365.000\n50.0 175.000\n75.0 140.000\n100.0 120.000\n125.0 90.000\n150.0 85.000 / TABLE NO. 02\nThe example defines two polymer thermal degradation half-life tables, based on the NTPVT variable on the TABDIMS keyword in the RUNSPEC section being equal to two and NPPVT variable on the same keyword being greater than or equal to six.","size_kind":"fixed","variadic_record":true},"PLYESAL":{"name":"PLYESAL","sections":["PROPS"],"supported":false,"summary":"This keyword, PLYESAL, defines the polymer effective salinity coefficient as well as enabling the effective salinity calculation for polymer adsorption. The keyword should only be used if the BRINE keyword has been declared to activate the brine phase, the ECLMC keyword to enable the Multi-Component Brine model, and the POLYMER keyword has been used to activate the polymer phase. All three keywords are in the RUNSPEC section.","parameters":[{"index":1,"name":"ALPHAP","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","expected_columns":1,"size_kind":"fixed"},"PLYKRRF":{"name":"PLYKRRF","sections":["PROPS"],"supported":false,"summary":"The PLYKRRF keyword defines the polymer rock permeability reduction factor to the water phase by individual cell, for when the Polymer option has been activated by the POLYMER keyword in the RUNSPEC section. PLYKRRF should consist of an array of real positive values that are greater than or equal to one. See the PERMFAC parameter on the PLYROCK keyword in the PROPS section for setting the property for the whole grid.","parameters":[],"example":"","size_kind":"array"},"PLYMAX":{"name":"PLYMAX","sections":["SPECIAL","PROPS"],"supported":null,"summary":"The PLYMAX keyword defines maximum polymer and salt concentrations that are to be used in the mixing parameter calculation of the fluid component viscosities, for when the Polymer option has been activated by the POLYMER keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"POLCON","description":"A real value that defines the polymer concentration in the solution which is used to calculate maximum polymer fluid component viscosity.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None","value_type":"DOUBLE","dimension":"Concentration"},{"index":2,"name":"SALTCON","description":"A real value that defines the salt concentration in the solution which is used to calculate maximum polymer fluid component viscosity. Note that If the BRINE option has not been activated by the BRINE keyword in the RUNSPEC section, then this variable is ignored; however, there should still be dummy entries in this case. This variable is ignored as the BRINE and POLYMER combination is not implemented in OPM Flow.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None","value_type":"DOUBLE","dimension":"Concentration"}],"example":"--\n-- POLYMER-SALT VISCOSITY MIXING CONCENTRATIONS\n--\nPLYMAX\n-- POLYMER SALT\n-- POLCON SALTCON\n-- ------- --------\n0.0100 0.0500 / TABLE NO. 01\n0.0075 0.0400 / TABLE NO. 02\n0.0050 0.0300 / TABLE NO. 03\nThe above example defines three polymer-salt viscosity mixing concentrations, based on the NPLMIX variable on the REGDIMS keyword in the RUNSPEC section being equal to three.\n| Note Currently, combining the BRINE and POLYMER models is not implemented in OPM Flow, and therefore SALTCON parameter on the PLYMAX keyword is ignored. |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":2,"size_kind":"fixed"},"PLYMWINJ":{"name":"PLYMWINJ","sections":["PROPS"],"supported":null,"summary":"This keyword, PLYMWINJ, describes the relationship of the injected polymer molecular weight as a function of polymer throughput and polymer velocity, for the simulator's Polymer Molecular Weight Transport option, that uses the polymer molecular weight in calculating the polymer viscosity. The table is a two dimensional table that relates the polymer throughput values and velocity values to derive the resulting molecular weight of the injected polymer, which is then used via the PLYVHM keyword in the PROPS section, to derive the polymer molecular weight scaled viscosity.","parameters":[{"index":1,"name":"PLYMWNUM","description":"A positive integer value greater than zero and less than or equal to the NTPMWINJ variable, as defined on the PINTDIMS keyword in the RUNSPEC section, that defines the PLYMWINJ Polymer Molecular Weight Model throughput and velocity table number.","units":{},"default":"None","record":1,"value_type":"INT"},{"index":1,"name":"THRUPUT","description":"A real positive monotonically increasing vector, that defines the polymer throughput values. The first entry should be zero to define a no throughput data set, and each vector record should be on a separate line terminated by a “/”.","units":{"field":"feet3/feet2","metric":"m3/m2","laboratory":"cm3/cm2"},"default":"None","record":2,"value_type":"DOUBLE","dimension":"Length"},{"index":1,"name":"VELOCITY","description":"A real positive monotonically increasing vector, that defines the polymer velocity values. The first entry should be zero to define a no velocity data set, and each vector record should be on a separate line terminated by a “/”.","units":{"field":"feet/day","metric":"m/day","laboratory":"cm/hour"},"default":"None","record":3,"value_type":"DOUBLE","dimension":"Length/Time"},{"index":1,"name":"POLYMW","description":"A series of real positive vectors representing the polymer molecular weights for all combinations of the polymer throughput values (THRUPUT) and velocity values (VELOCITY), organized as a series of vectors POLYMW(THRUPUT, VELOCITY). Thus, the first vector represents the molecular weights of the first THRUPUT value and each entry in the vector is the corresponding molecular weight of the associated VELOCITY vector. Each vector should be on a separate line and should be terminated by a “/”. Thus, if THRUPUT has three entries and VELOCITY has four, then there should be three vectors, with each vector containing four elements representing molecular weight values, as a function of THRUPUT and VELOCITY.","units":{"field":"lb/lb-M","metric":"kg/kg-M","laboratory":"gm/gm-M"},"default":"None","record":4,"value_type":"DOUBLE","dimension":"1"}],"example":"Given NTPMWINJ equals two on the PINTDIMS keyword in the RUNSPEC section, then two PLYWINJ tables are required to be entered:\n--\n-- POLYMER MOLECULAR WEIGHT MODEL THROUGHPUT AND VELOCITY TABLE\n-- (OPM FLOW PROPS KEYWORD)\n--\nPLYMWINJ\n1 / TABLE NUMBER\n--\n-- THROUGHPUT VALUES\n--\n0.0 200.0 400.0 /\n--\n-- VELOCITY VALUES\n--\n0.0 50.0 80.0 100.0 /\n--\n-- POLYMW VALUES\n--\n20.0 19.0 18.0 16.0 / POLYMW(OUTPUT=1, VELOCITY=1 TO N)\n20.0 16.0 14.0 12.0 / POLYMW(OUTPUT=2, VELOCITY=1 TO N)\n20.0 12.0 8.0 4.0 / POLYMW(OUTPUT=3, VELOCITY=1 TO N)\n/\nPLYMWINJ\n2 / TABLE NUMBER\n--\n-- THROUGHPUT VALUES\n--\n0.0 200.0 400.0 /\n--\n-- VELOCITY VALUES\n--\n0.0 50.0 70.0 100.0 /\n--\n-- POLYMW VALUES\n--\n20.0 19.0 18.0 16.0 / POLYMW(OUTPUT=1, VELOCITY=1 TO N)\n20.0 16.0 14.0 12.0 / POLYMW(OUTPUT=2, VELOCITY=1 TO N)\n20.0 12.0 8.0 4.0 / POLYMW(OUTPUT=3, VELOCITY=1 TO N)\n/\nAs mentioned previously, the PLYMWINJ keyword requires that the keyword itself must be repeated for each table, as is shown in the above example.\n| Note This is an OPM Flow specific keyword that employs an alternative polymer flood model based on a Polymer Molecular Weight Transport equation, that is not available in the commercial simulator. The model has been tested using metric units; however, using either field or laboratory units with the option should be considered experimental. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","records_meta":[{"expected_columns":1},{},{},{}],"size_kind":"list"},"PLYRMDEN":{"name":"PLYRMDEN","sections":["GRID"],"supported":null,"summary":"The PLYRMDEN keyword defines the in situ rock density at reservoir conditions by individual cell, for when the Polymer option has been activated by the POLYMER keyword in the RUNSPEC section. PLYRMDEN should consist of an array of real positive values. See the DENSITY parameter on the PLYROCK keyword in the PROPS section for setting the property for the whole grid.","parameters":[],"example":"","size_kind":"array"},"PLYROCK":{"name":"PLYROCK","sections":["PROPS"],"supported":null,"summary":"The PLYROCK keyword defines rock properties for when the Polymer option has been activated by the POLYMER keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"PSPACE","description":"A real positive value that is greater than or equal to zero and less the maximum water saturation and less than one, that defines available pore space for this rock type.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":"1"},{"index":2,"name":"PERMFAC","description":"A real positive value that is greater than or equal to one that defines decrease in the rock permeability to the water phase when the maximum amount of polymer has been adsorbed.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"DENSITY","description":"A real value that defines the rock in-situ density, that is at reservoir conditions.","units":{"field":"lb/rb","metric":"kg/rm3","laboratory":"gm/rcc"},"default":"None","value_type":"DOUBLE","dimension":"Density"},{"index":4,"name":"ADINDX","description":"A positive integer of 1 or 2 that defines the polymer desorption option. then polymer desorption may occur by retracing the polymer adsorption isotherm when the local polymer concentration in the solution decreases. then no polymer desorption may occur.","units":{"field":"dimensionless 1","metric":"dimensionless 1","laboratory":"dimensionless 1"},"default":"Defined","value_type":"DOUBLE","dimension":"1"},{"index":5,"name":"POLMAX","description":"A real positive non-zero value that defines the maximum polymer adsorption to be used in the calculation of the resistance factor for the water phase.","units":{"field":"lb/lb","metric":"kg/kg","laboratory":"gm/gm"},"default":"None","value_type":"DOUBLE","dimension":"1"}],"example":"--\n-- POLYMER-ROCK PROPERTIES\n--\nPLYROCK\n-- PORE PERM INSITU DESORP MAX\n-- SPACE FACTOR DENSITY OPTN POLY\n-- ------ -------- ------- ------ -------\n0.1200 1.7500 1800.0 1 0.00012 / TABLE NO. 01\n0.1300 1.8500 1980.0 2 0.00015 / TABLE NO. 02\n0.1500 1.9500 2005.0 1 0.00014 / TABLE NO. 03\nThe above example defines three polymer-rock tables, based on the NTSFUN variable on the TABDIMS keyword in the RUNSPEC section being equal to three.\nThere is no terminating “/” for this keyword.","expected_columns":5,"size_kind":"fixed"},"PLYSHEAR":{"name":"PLYSHEAR","sections":["SPECIAL","PROPS"],"supported":false,"summary":"The PLYSHEAR keyword activates and defines the polymer shear thinning-thickening option for when the polymer option has been activated by the POLYMER keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"VELOCITY","description":"A columnar vector of real monotonically increasing down the column values that defines the water-polymer flow velocity. The VELOCITY value for the first row in the table should be zero.","units":{"field":"feet/day","metric":"m/day","laboratory":"cm/hour"},"default":"None","value_type":"DOUBLE","dimension":["Length/Time","1"]},{"index":2,"name":"VISFAC","description":"A columnar vector of real values that defines a factor that scales the effective water and polymer viscosities for when shear thinning-thickening of the polymer occurs. Normally VISFAC value for the first row in the table should be one.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- ACTIVATE AND DEFINE POLYMER SHEARING PARAMETERS\n--\nPLYSHEAR\n-- WAT-POLY VISCOSITY\n-- VELOCITY FACTOR\n-- -------- ---------\n0.0 1.000\n1.0 0.900\n3.0 0.800\n6.0 0.700 / TABLE NO. 01\n-- WAT-POLY VISCOSITY\n-- VELOCITY FACTOR\n-- -------- ---------\n0.0 1.000\n1.0 0.900\n2.0 0.800\n4.0 0.750\n6.0 0.700\n8.0 0.650 / TABLE NO. 02\nThe above example activates the polymer shear thinning-thickening option and defines two polymer shear thinning-thickening tables, based on the NTPVT variable on the TABDIMS keyword in the RUNSPEC section being equal to two and NPPVT variable on the same keyword being greater than or equal to six.","size_kind":"fixed","variadic_record":true},"PLYSHLOG":{"name":"PLYSHLOG","sections":["SPECIAL","PROPS","SCHEDULE"],"supported":null,"summary":"This keyword activates and defines the parameters for the logarithm-based polymer shear thinning/thickening option.","parameters":[{"index":1,"name":"POLCON","description":"A real positive value that defines the reference polymer concentration for the VELOCITY and VISFAC data for this keyword.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None","record":1,"value_type":"DOUBLE","dimension":"Concentration"},{"index":2,"name":"SALTCON","description":"A real positive value that defines the reference salt concentration for the VELOCITY and VISFAC data for this keyword. Note that If the BRINE option has not been activated by the BRINE keyword in the RUNSPEC section, then this variable is ignored. This variable is ignored as the BRINE option is not implemented in OPM Flow.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None","record":1,"value_type":"DOUBLE","dimension":"Concentration"},{"index":3,"name":"TEMP","description":"A real positive value defines the reference polymer temperature for the VELOCITY and VISFAC data for this keyword. Note that If the TEMP option has not been activated by the TEMP keyword in the RUNSPEC section, then this variable is ignored. This variable is ignored as the TEMP and POLYMER options combination is not implemented in OPM Flow.","units":{"field":"oF","metric":"oC","laboratory":"oC"},"default":"None","record":1,"value_type":"DOUBLE","dimension":"Temperature"},{"index":1,"name":"VELOCITY","description":"A columnar vector of real monotonically increasing down the column values that defines the water-polymer flow velocity for the reference conditions of POLCON, SALTCON and TEMP. The VELOCITY value for the first row in the table should be a very small value that is greater than zero and less than 1 x 10-6.","units":{"field":"feet/day","metric":"m/day","laboratory":"cm/hour"},"default":"None","record":2,"value_type":"DOUBLE","dimension":["1","1"]},{"index":2,"name":"VISFAC","description":"A columnar vector of real positive values that define the dimensionless shear effect multiplier for the given VELOCITY entry for the reference conditions of POLCON, SALTCON and TEMP. Normally VISFAC value for the first row in the table should be one.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","record":2}],"example":"The following example show how to enter two PLYSHLOG tables given that the NTPVT variable on the TABDIMS keyword in the RUNSPEC section is set equal to two.\n--\n-- POLYMER SHEARING LOGARITHMIC PARAMETERS\n--\nPLYSHLOG\n-- REF REF REF\n-- POLCON SALTCON TEMP\n-- -------- ------- ----\n0.5\n/\n--\n-- VELOCITY VISFAC\n-- -------- -------\n0.0000001 1.00\n0.000001 1.10\n0.0001 1.30\n0.001 1.47\n0.01 1.67\n0.1 2.00\n1.0 2.20\n10.0 2.30\n100.0 2.40\n1000.0 2.40\n/ TABLE NO. 01\n-- REF REF REF\n-- POLCON SALTCON TEMP\n-- -------- ------- ----\n0.5\n/\n--\n-- VELOCITY VISFAC\n-- -------- -------\n0.0000001 1.00\n0.000001 1.10\n0.0001 1.35\n0.001 1.57\n0.01 1.87\n0.1 2.20\n1.0 2.40\n10.0 2.60\n100.0 2.65\n1000.0 2.65\n/ TABLE NO. 02\nThe example activates the polymer logarithmic shear thinning-thickening option and defines two polymer shear thinning-thickening tables, based on the NTPVT variable on the TABDIMS keyword in the RUNSPEC section being equal to two and NPPVT variable on the same keyword being greater than or equal to ten.","records_meta":[{"expected_columns":3},{}],"size_kind":"fixed","size_count":2},"PLYTRRF":{"name":"PLYTRRF","sections":["PROPS"],"supported":false,"summary":"The PLYTRRF keyword defines the polymer rock permeability reduction factor to the water phase as a function of temperature, for when the Polymer option has been activated by the POLYMER keyword in the RUNSPEC section. See the PLYTRRF keyword for the options on how this data is used in the polymer model and the PERMFAC parameter on the PLYROCK keyword for setting the property for the whole grid for a constant temperature. Both keywords are in the PROPS section.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Temperature","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"PLYTRRFA":{"name":"PLYTRRFA","sections":["PROPS"],"supported":false,"summary":"The PLYTRRFA keyword defines the how the polymer rock permeability reduction factor to the water phase as a function of temperature data, entered via the PLYTRRA keyword in the PROPS section, should be used. This keyword should only be used if the Polymer option has been activated by the POLYMER keyword in the RUNSPEC section. See the PERMFAC parameter on the PLYROCK keyword in the PROPS section for setting the property for the whole grid for a constant temperature.","parameters":[{"index":1,"name":"NBTRRF","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"PLYVISC":{"name":"PLYVISC","sections":["SPECIAL","PROPS","SCHEDULE"],"supported":null,"summary":"PLYSVISC defines the polymer viscosity scaling factors used to determine the relationship of pure water viscosity with respect to increasing polymer concentration within a grid block. The polymer option must be activated by the POLYMER keyword in the RUNSPEC section in order to use this keyword.","parameters":[{"index":1,"name":"POLCON","description":"A columnar vector of real monotonically increasing down the column values that defines the polymer concentration in the solution surrounding the rock. The first entry should be zero to define a no polymer concentration.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None","value_type":"DOUBLE","dimension":["Concentration","1"]},{"index":2,"name":"VISFAC","description":"A columnar vector of real increasing or equal values that defines a factor that scales the effective viscosity of the solution for the given POLCON entry. Normally VISFAC value for the first row in the table should be one.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- POLYMER VISCOSITY SCALING FACTOR TABLES\n--\nPLYVISC\n-- POLYMER VISCOSITY\n-- POLCON VISFAC\n-- -------- ---------\n0.0000 1.000\n0.0002 10.000\n0.0004 20.000\n0.0008 40.000 / TABLE NO. 01\n-- POLYMER VISCOSITY\n-- POLCON VISFAC\n-- -------- ---------\n0.0000 1.000\n0.0003 10.000\n0.0005 20.000\n0.0007 40.000\n0.0009 45.000\n0.0011 55.000 / TABLE NO. 02\nThe example defines two polymer viscosity scaling factor tables, based on the NTPVT variable on the TABDIMS keyword in the RUNSPEC section being equal to two and NPPVT variable on the same keyword being greater than or equal to six.","size_kind":"fixed","variadic_record":true},"PLYVISCS":{"name":"PLYVISCS","sections":["PROPS","SCHEDULE"],"supported":false,"summary":"PLYSVISCS defines the polymer-salt viscosity scaling factor tables applied to pure water that are used to determine the viscosity of a polymer-salt mixture with respect to increasing polymer concentration within a grid block. The polymer option must be activated by the POLYMER keyword, as well as the brine phase declared by the BRINE keyword in the RUNSPEC section in order to use this keyword. However the ECLM keyword in the RUNSPEC must not be used with this keyword.","parameters":[{"index":1,"name":"PC","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Mass/LiquidSurfaceVolume"},{"index":2,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","size_kind":"fixed","variadic_record":true},"PLYVISCT":{"name":"PLYVISCT","sections":["PROPS","SCHEDULE"],"supported":false,"summary":"PLYSVISCT defines the polymer-temperature viscosity scaling factor tables applied to pure water that are used to determine the viscosity of the polymer at a given temperature with respect to increasing polymer concentration within a grid block. Both the polymer option must be activated by the POLYMER keyword and the temperature option invoked by the TEMP keyword in the RUNSPEC section in order to use this keyword. However the BRINE keyword in the RUNSPEC must not be used with this keyword, that is the salt sensitivity options should be deactivated.","parameters":[{"index":1,"name":"PC","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Mass/LiquidSurfaceVolume"},{"index":2,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","size_kind":"fixed","variadic_record":true},"PLYVMH":{"name":"PLYVMH","sections":["PROPS"],"supported":null,"summary":"This keyword, PLYVMH, defines the constants used to calculate viscosity of the polymer solution as a function of the polymer molecular weight and the polymer concentration, for the simulator's Polymer Molecular Weight Transport option, that uses the polymer molecular weight in calculating the polymer viscosity. The keyword consists of a series of row vectors, which each vector having four elements, that define the constants used in calculating the polymer viscosity","parameters":[{"index":1,"name":"K_MH","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":2,"name":"MHA","description":"The Mark-Houwink exponent parameter a, in the Mark-Houwink equation, see equation (8.77).","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"GAMMA","description":"The ɣ intrinsic water-polymer viscosity constant in the Huggins equation, see equation (8.79).","units":{},"default":"None","value_type":"DOUBLE","dimension":"1"},{"index":4,"name":"KAPPA","description":"The κ intrinsic water-polymer viscosity constant in the Huggins equation, see equation (8.79).","units":{},"default":"None","value_type":"DOUBLE","dimension":"1"}],"example":"Given NPLYVMH equals two on the PINTDIMS keyword in the RUNSPEC section, then:\n--\n-- POLYMER MOLECULAR WEIGHT MODEL POLYMER VISCOSITY CONSTANTS\n-- (OPM FLOW PROPS KEYWORD)\n--\n-- MHK MHA VISC VISC\n-- CONST EXPON GAMMA KAPPA\nPLYVMH\n0.02 0.50 0.40 0.60 /\n0.03 0.51 0.42 0.63 /\n/\nTwo sets of data should be entered with the PLYVMH keyword, as shown above.\n| Note This is an OPM Flow specific keyword that employs an alternative polymer flood model based on a Polymer Molecular Weight Transport equation, that is not available in the commercial simulator. The model has been tested using metric units; however, using either field or laboratory units with the option should be considered experimental. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| [%eta_rel~=~ %eta over %eta_s] | (8.73) |\n|--------------------------------|--------|\n| [%eta_{\"sp\"} ~=~ left( %eta - %eta_s right) over %eta_s newline\n~~~`\" \" = ~ %eta over %eta_s ``-`` 1 newline\n~~~````\" \" = ~ %eta_rel ``-`` 1] | (8.74) |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|--------|\n| [%eta_{\"red\"} ~=~ %eta_\"sp\" over C_p newline\n~~~~~~~~~~````\" \" = ~left( %eta_rel ``-`` 1 right) over C_p] | (8.75) |\n|------------------------------------------------------------------------------------------------------------|--------|\n| [left [%eta right ] ~=~ lim from{ C_p toward 0 } {%eta_\"sp\" over C_p} newline\n~~~~~``\" \" = ~lim from{ C_p toward 0 } {{%eta - %eta_0} over {%eta_0 C_p}}] | (8.76) |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|\n| [left [%eta right ] ~=~ K` cdot `{M_w}^a] | (8.77) |\n|-------------------------------------------|--------|\n| [ln left( [%eta] right) ~=~ ln(K) ~+~ a `times `ln (M_w)] | (8.78) |\n|-----------------------------------------------------------|--------|\n| [~~~~~~~~~~~%eta_0 over %eta_s ~=~ 1``+`` %gamma left(X``+`` %kappa X^2 right) newline \n\"where\"~~~~~ \nX~=~ left[%eta right] C_p] | (8.79) |\n|----------------------------------------------------------------------------------------------------------------------------------|--------|\n| [left[ %eta right]~ = ~ K left(M_w ` cdot `1.0 times 10^-3 right)^a dot \" \" 1.0 times 10^-3] | (8.80) |\n|-----------------------------------------------------------------------------------------------|--------|\n| [~~~~~~~~~~~%eta_0 over %eta_s ~=~ 1``+`` %gamma left(X``+`` %kappa X^2 right) newline \n\"where\"~~~~~ \nX~=~ 1.0 times 10^-6left[%eta right] C_p] | (8.81) |\n|-------------------------------------------------------------------------------------------------------------------------------------------------|--------|","expected_columns":4,"size_kind":"fixed"},"PLYVSCST":{"name":"PLYVSCST","sections":["PROPS","SCHEDULE"],"supported":false,"summary":"PLYVSCST defines the polymer-salt-temperature viscosity scaling factor tables applied to pure water that are used to determine the viscosity of the polymer at a given salt concentration and for a given temperature, with respect to increasing polymer concentration within a grid block. Both the polymer option must be activated by the POLYMER keyword and the temperature option invoked by the TEMP keyword in the RUNSPEC section in order to use this keyword. In addition, the BRINE keyword in the RUNSPEC must also be invoked. The keyword is used in conjunction with the SALTNODE keyword to define the various salt concentrations and the TEMPNODE keyword to define the various reservoir temperatures. Both keywords are in the PROPS section.","parameters":[{"index":1,"name":"PC1","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Mass/LiquidSurfaceVolume"},{"index":2,"name":"MULT","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","size_kind":"list","variadic_record":true},"PMAX":{"name":"PMAX","sections":["PROPS"],"supported":false,"summary":"The PMAX keyword defines the maximum and minimum pressures expected to be encountered during the run. The data is used to perform the PVT total compressibility check that ensures that the total compressibility of a mixture of oil-gas, for when the gas-oil ratio is increasing for an oil, or the condensate gas ratio is increasing for a gas condensate, is positive respect to pressure. The total compressibility check is used to ensure that the entered oil and gas PVT data is consistent. If the check fails for given oil-gas mixture at a given pressure, resulting in a negative total compressibility, then this will result in numerical instabilities in the run causing this simulator difficulties in converging to a solution.","parameters":[{"index":1,"name":"MAX_PRESSURE","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":2,"name":"MAX_PRESSURE_CHECK","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Pressure"},{"index":3,"name":"MIN_PRESSURE_CHECK","description":"","units":{},"default":"1e+20","value_type":"DOUBLE","dimension":"Pressure"},{"index":4,"name":"NUM_NODES","description":"","units":{},"default":"30","value_type":"INT"}],"example":"","expected_columns":4,"size_kind":"fixed","size_count":1},"PMISC":{"name":"PMISC","sections":["PROPS"],"supported":null,"summary":"PMISC defines the transition between immiscible and miscible displacement as a function of oil pressure tables, for when the MISCIBLE keyword in the RUNSPEC section has be activated. If this keyword is absent from the input deck and MISCIBLE keyword in the RUNSPEC keyword has been activated, then miscibility is independent of the oil phase pressure.","parameters":[{"index":1,"name":"PRESS","description":"A columnar vector of real monotonically increasing down the column values that defines the oil phase pressure.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":["Pressure","1"]},{"index":2,"name":"MISC","description":"A columnar vector of real equal or increasing down the column values that defines the corresponding miscibility factor. MISC is a scaling that should lie be zero and one, where zero means no miscibility and one means full miscibility.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- MISCIBILITY VERSUS PRESSURE TABLES\n--\nPMISC\n-- OIL MISCIBILE\n-- PRESS FACTOR\n-- ------- ---------\n1000.0 0.000\n2000.0 0.250\n3000.0 1.000\n4000.0 1.000 / TABLE NO. 01\n-- OIL MISCIBILE\n-- PRESS FACTOR\n-- ------- ---------\n1500.0 0.000\n2000.0 0.000\n2500.0 0.250\n3000.0 0.350\n3500.0 1.000\n4000.0 1.000 / TABLE NO. 02\nThe above example defines two miscibility versus pressure tables assuming NTMISC equals two and NSMISC is greater than or equal to six on the MISCIBLE keyword in the RUNSPEC section.","size_kind":"fixed","variadic_record":true},"PPCWMAX":{"name":"PPCWMAX","sections":["PROPS"],"supported":null,"summary":"The PPCWMAX keyword defines the maximum capillary pressure allowed when scaling the capillary pressure tables to match the inputted SWATINIT array. This is primary used for when the SWATINIT array has values of water saturation above the connate water saturation significantly outside than capillary pressure transition zone, that is high on the structure. In this case OPM Flow may generate large values for the capillary pressure which may result in numerical converge problems. This keyword sets the maximum allowable calculated capillary pressure and how the water saturation should be treated when the limit is exceeded.","parameters":[{"index":1,"name":"PCWO","description":"A columnar vector of real values that defines the maximum allowable capillary pressure for each SATNUM region. The default value of infinity means there is no limit applied.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"Infinity","value_type":"DOUBLE","dimension":"Pressure"},{"index":2,"name":"OPTN","description":"A columnar vector of character strings that should be set to: NO: To ignore the SWATINIT value for the offending cell for when PCWO is exceeded. In this cases the capillary pressure for the block is set to the maximum (PCWO) and the water saturation is re-calculated based on PCWO. YES: To set the SWATINIT value to the connate water saturation for the offending cell for when PCWO is exceeded. In this case the capillary pressure is set to the maximum value of the appropriate SATNUM table and the initial water saturation is calculated to be consistent with the tables maximum capillary pressure. This results in the capillary pressures not being re-scale for the offending cell.","units":{},"default":"No","value_type":"STRING"}],"example":"--\n-- SET MAXIMUM PC FOR SWATINIT INITIALIZATION\n-- MAX MATCH\n-- PC SWATINIT\n-- -------- --------\nPPCWMAX\n100.0 YES / TABLE NO 01\n125.0 YES / TABLE NO 02\n135.0 YES / TABLE NO 03\nThe above example sets the maximum capillary pressure for three saturation regions to 100, 125 and 135 with SWATINIT reset to the connate water saturation for when the capillary pressure limit is exceeded.\n| Note Using this keyword to limit the re-scaled grid block capillary pressure values will effect the fluids in-place when the simulator has to re-calculate values due to the capillary pressure limit being exceeded. In addition, the high grid block capillary pressures may be indicative of an inconsistency between the tabular SATNUM capillary pressure values and the provided SWATINIT array water saturations. This inconsistency may be a result of the SWATINIT array being derived using a saturation height function, as is customary in static modeling software, and the numerical models tabulated capillary pressure. Rather than resetting the maximum calculated capillary pressure using the PPCWMAX keyword, it may be more appropriate to investigate the reason for the high capillary pressures values first, prior to applying the keyword. |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":2,"size_kind":"fixed"},"PROPS":{"name":"PROPS","sections":["PROPS"],"supported":null,"summary":"The PROPS activation keyword marks the end of the EDIT section and the start of the PROPS section that defines the key fluid and rock property data for the simulator","parameters":[],"example":"-- ==============================================================================\n--\n-- PROPS SECTION\n--\n-- ==============================================================================\nPROPS\nThe above example marks the end of the EDIT section and the start of the PROPS section in the OPM Flow data input file.","size_kind":"none","size_count":0},"PVCDO":{"name":"PVCDO","sections":["PROPS"],"supported":null,"summary":"PVCDO defines the oil PVT properties for dead oil1\n “Dead” oil is oil that it contains no dissolved gas or a relatively thick oil or residue that has lost its volatile components. with constant compressibility. If the oil has a constant and uniform dissolved gas concentration, Gas-Oil Ratio (“GOR”), and if the reservoir pressure never drops below the saturation pressure (bubble point pressure), then the model can be run more efficiently by omitting the GAS and DISGAS keywords from the RUNSPEC section, treating the oil as a dead oil, and defining a constant Rs (GOR) value with keyword RSCONST or RSCONSTT in the PROPS section. This results in the model being run as a dead oil problem with no active gas phase. However, OPM Flow takes into account the constant Rs in the calculations and reporting.","parameters":[{"index":1,"name":"PRESS","description":"PRESS is a real positive value defining the oil reference pressure for the other parameters for this data set.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":"Pressure"},{"index":2,"name":"OFVF","description":"OFVF is a real positive value defining the oil formation volume factor (Bo) at the reference pressure.","units":{"field":"rb/stb","metric":"rm3/sm3","laboratory":"rcc/scc"},"default":"None","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"OCOMP","description":"OCOMP is a real positive value defining the oil compressibility (Co) at the oil reference pressure and is defined as: [C sub{o}~=~ - 1 over {B sub{o}}left({dB sub{o}} over{dP} right)]","units":{"field":"1/psia","metric":"1/barsa","laboratory":"1/atma"},"default":"None","value_type":"DOUBLE","dimension":"1/Pressure"},{"index":4,"name":"OVISC","description":"OVISC is a real positive value defining the oil viscosity (µo) at the oil reference pressure.","units":{"field":"cP","metric":"cP","laboratory":"cP"},"default":"None","value_type":"DOUBLE","dimension":"Viscosity"},{"index":5,"name":"OVISCOMP","description":"OVISCOMP is a real positive value defining the oil viscosibility (µoc) at the oil reference pressure and is defined as: [%mu sub{oc}~=~ 1 over { %mu sub{o}}left({d%mu sub{o}} over{dP} right)]","units":{"field":"1/psia","metric":"1/barsa","laboratory":"1/atma"},"default":"None","value_type":"DOUBLE","dimension":"1/Pressure"}],"example":"--\n-- OIL PVT TABLE FOR DEAD WITH CONSTANT COMPRESSIBILITY\n--\nPVCDO\n-- REF PRES BO CO VISC VISC\n-- PSIA RB/STB 1/PSIA CPOISE GRAD\n-- -------- -------- ------- ------ ------\n3840.0 1.080 1.5E-6 1.750 0.0 / TABLE NO. 01\n3840.0 1.100 1.5E-6 1.050 0.0 / TABLE NO. 02\n3840.0 1.120 1.6E-6 0.950 0.0 / TABLE NO. 03\n3840.0 1.140 1.7E-6 0.850 0.0 / TABLE NO. 04\n3840.0 1.160 1.7E-6 0.800 0.0 / TABLE NO. 05\nThe above example defines five dead oil PVT tables with constant compressibility and viscosity, and assumes that NTPVT equals five on the TABDIMS keyword in the RUNSPEC section.\nThere is no terminating “/” for this keyword.","expected_columns":5,"size_kind":"fixed"},"PVCO":{"name":"PVCO","sections":["PROPS"],"supported":false,"summary":"PVCO defines the oil PVT properties for live216\n “Live” oil is oil that contains gas in solution, which is normally the case for most conventional oil reservoirs. However, for oil reservoirs classified as heavy oil reservoirs, the in situ dissolved gas may be negligible and oil would then be classified as gas-free oil which is commonly referred to as “dead” oil. and the keyword should only be used if the there is both oil and gas phases in the model. This keyword should be used when the DISGAS keyword has be declared in the RUNSPEC section indicating that dissolved gas (more commonly referred to as solution gas) is present in the oil. The keyword may be used for oil-water and oil-water-gas input decks. This is an alternative keyword to the PVTO keyword in the PROPS section that also enables entering live oil PVT data. Here, the PVCO keyword assumes that for the undersaturated oil with a given Gas-Oil Ratio (“GOR” or “Rs”), the oil compressibility is independent of the pressure....","parameters":[{"index":1,"name":"PRESS","description":"PRESS is a real columnar vector of real monotonically increasing down the column values that defines the oil phase saturation pressure (bubble-point pressure), that defines the RS, oil formation volume factor and the oil viscosity at PRESS.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":["Pressure","GasSurfaceVolume/LiquidSurfaceVolume","ReservoirVolume/LiquidSurfaceVolume","Viscosity","1/Pressure","1/Pressure"]},{"index":2,"name":"RS","description":"RS is a real monotonically increasing down the column values that defines the saturated gas-oil ratio (“GOR”) or Rs, for the given value of PRESS.","units":{"field":"Mscf/stb","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"1*"},{"index":3,"name":"OFVF","description":"OFVF is a real positive value defining the oil saturated formation volume factor (Bo) at the saturation pressure PRESS.","units":{"field":"rb/stb","metric":"rm3/sm3","laboratory":"rcc/scc"},"default":"None"},{"index":4,"name":"OVISC","description":"OVISC is a real positive value defining the oil viscosity (µo) at the oil saturated reference pressure, PRESS.","units":{"field":"cP","metric":"cP","laboratory":"cP"},"default":"1*"},{"index":5,"name":"OCOMP","description":"OCOMP is a real positive value defining the oil compressibility (Co) at the saturated oil reference pressure and is defined as: [C sub{o}~=~ - 1 over {B sub{o}}left({dB sub{o}} over{dP} right)]","units":{"field":"1/psia","metric":"1/barsa","laboratory":"1/atma"},"default":"1*"},{"index":6,"name":"OVISCOMP","description":"OVISCOMP is a real positive value defining the oil viiscosibility (µoc) at the saturated oil reference pressure with the given RS, where (µoc) is defined as: [%mu sub{oc}~=~ - 1 over { %mu sub{o}}left({d%mu sub{o}} over{dP} right)]","units":{"field":"1/psia","metric":"1/barsa","laboratory":"1/atma"},"default":"1*"}],"example":"--\n-- OIL PVT TABLE FOR LIVE OIL\n--\nPVCO\n-- PSAT RS BO VISC OIL OIL\n-- PSIA MSCF/STB RB/STB CPOISE COMPRES VISCOS\n-- -------- -------- ------- ------ ------- ------\n14.7 0.0010 1.05340 1.7230 3.0E-5 1*\n500.0 0.0890 1.08890 1.1670 1* 1*\n1000.0 0.2060 1.13850 0.8570 1* 1*\n1500.0 0.3360 1.19640 0.6840 1* 1*\n2000.0 0.4750 1.26110 0.5750 1* 1*\n2500.0 0.6220 1.33160 0.5000 1* 1*\n3000.0 0.7750 1.40740 0.4450 1* 1*\n3500.0 0.9330 1.48790 0.4020 1* 1*\n4000.0 1.0960 1.57280 0.3680 1* 1*\n4258.0 1.1800 1.61760 0.3530 1* 1*\n4500.0 1.2630 1.66190 0.3400 1* 1*\n5000.0 1.4340 1.75480 0.3170 1* 1*\n5500.0 1.6060 1.85020 0.2980 1* 1* / TABLE NO. 01\n--\n-- PSAT RS BO VISC OIL OIL\n-- PSIA MSCF/STB RB/STB CPOISE COMPRES VISCOS\n-- -------- -------- ------- ------ ------- ------\n14.7 0.0010 1.05340 1.7230 3.0E-5 1*\n500.0 0.0890 1.08890 1.1670 1* 1*\n1000.0 0.2060 1.13850 0.8570 1* 1*\n1500.0 0.3360 1.19640 0.6840 1* 1*\n2000.0 0.4750 1.26110 0.5750 1* 1*\n2500.0 0.6220 1.33160 0.5000 1* 1*\n3000.0 0.7750 1.40740 0.4450 1* 1*\n3500.0 0.9330 1.48790 0.4020 1* 1*\n4000.0 1.0960 1.57280 0.3680 1* 1*\n4258.0 1.1800 1.61760 0.3530 1* 1*\n4500.0 1.2630 1.66190 0.3400 1* 1*\n5000.0 1.4340 1.75480 0.3170 1* 1*\n5500.0 1.6060 1.85020 0.2980 1* 1* / TABLE NO. 02\nThe example defines two live oil PVT tables with constant compressibility above the saturation pressure, and assumes that NTPVT equals two on the TABDIMS keyword in the RUNSPEC section.","size_kind":"fixed","variadic_record":true},"PVDG":{"name":"PVDG","sections":["PROPS"],"supported":null,"summary":"PVDG defines the gas PVT properties for dry gas217\n Natural gas that occurs in the absence of condensate or liquid hydrocarbons, or gas that had condensable hydrocarbons removed, is called dry gas. It is primarily methane with some intermediates. The hydrocarbon mixture is solely gas in the reservoir and there is no liquid (condensate surface liquid) formed either in the reservoir or at surface. The term dry indicates that the gas does not contain heavier hydrocarbons to form liquids at the surface conditions. Dry gas typically has GOR's greater than 100,000 scf/stb or 18,000 Sm3/m3. . If the gas has a constant and uniform vaporized oil concentration, Condensate-Gas Ratio (“CGR”), and if the reservoir pressure never drops below the saturation pressure (dew point pressure), then the model can be run more efficiently by omitting the OIL and VAPOIL keywords from the RUNSPEC section, treating the gas as a dry gas, and defining a constant Rv (CGR) value with keyword RVCONST or RVCONS...","parameters":[{"index":1,"name":"PRESS","description":"A columnar vector of real monotonically increasing down the column values that defines the gas phase pressure.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":["Pressure","OilDissolutionFactor","Viscosity"]},{"index":2,"name":"GFVF","description":"A columnar vector of real decreasing down the column values that defines the corresponding gas phase formation volume factor.","units":{"field":"rb/Mscf","metric":"rm3/sm3","laboratory":"rcc/scc"},"default":"None"},{"index":3,"name":"GVISC","description":"A columnar vector of real increasing down the column values that defines the corresponding gas phase viscosity.","units":{"field":"cP","metric":"cP","laboratory":"cP"},"default":"None"}],"example":"The first example below defines two dry gas PVT tables assuming NTPVT equals two and NPPVT is greater than or equal to 22 on the TABDIMS keyword in the RUNSPEC section.\n--\n-- GAS PVT TABLE FOR DRY GAS\n--\nPVDG\n-- PRES BG VISC\n-- PSIA RB/MSCF CPOISE\n-- ------ -------- ------\n14.7 197.8092 0.0129\n50.0 65.9364 0.0130\n100.0 31.6495 0.0130\n230.0 13.8813 0.0131\n460.0 6.8210 0.0132\n690.0 4.4703 0.0135\n920.0 3.2968 0.0138\n1150.0 2.6113 0.0141\n1380.0 2.1560 0.0145\n1610.0 1.8316 0.0150\n1840.0 1.5952 0.0155\n2070.0 1.4129 0.0161\n2300.0 1.2700 0.0167\n2372.0 1.2305 0.0169\n2530.0 1.1551 0.0174\n2760.0 1.0621 0.0181\n2990.0 0.9841 0.0189\n3220.0 0.9190 0.0196\n3450.0 0.8638 0.0204\n4500.0 0.6910 0.0242\n6000.0 0.5616 0.0293 / TABLE N0. 01\n--\n-- PRES BG VISC\n-- PSIA RB/MSCF CPOISE\n-- ------ -------- ------\n14.7 265.0126 0.0133\n50.0 66.2531 0.0133\n100.0 33.1266 0.0133\n230.0 14.4552 0.0134\n460.0 7.0357 0.0136\n690.0 4.6493 0.0138\n920.0 3.4417 0.0140\n1150.0 2.7227 0.0144\n1380.0 2.2522 0.0147\n1610.0 1.9158 0.0151\n1840.0 1.6702 0.0156\n2070.0 1.4805 0.0162\n2300.0 1.3317 0.0167\n2372.0 1.2927 0.0169\n2530.0 1.2119 0.0173\n2760.0 1.1135 0.0180\n2990.0 1.0325 0.0187\n3220.0 0.9637 0.0194\n3450.0 0.9055 0.0201\n4500.0 0.7228 0.0236\n6000.0 0.5837 0.0285 / TABLE N0. 02\nThe second example defines four dry gas PVT tables assuming NTPVT equals four and NPPVT is greater than or equal to 22 on the TABDIMS keyword in the RUNSPEC section. Here table two defaults to table one, and table four defaults to table three.\n--\n-- GAS PVT TABLE FOR DRY GAS\n--\nPVDG\n-- PRES BG VISC\n-- PSIA RB/MSCF CPOISE\n-- ------ -------- ------\n14.7 197.8092 0.0129\n50.0 65.9364 0.0130\n100.0 31.6495 0.0130\n230.0 13.8813 0.0131\n460.0 6.8210 0.0132\n690.0 4.4703 0.0135\n920.0 3.2968 0.0138\n1150.0 2.6113 0.0141\n1380.0 2.1560 0.0145\n1610.0 1.8316 0.0150\n1840.0 1.5952 0.0155\n2070.0 1.4129 0.0161\n2300.0 1.2700 0.0167\n2372.0 1.2305 0.0169\n2530.0 1.1551 0.0174\n2760.0 1.0621 0.0181\n2990.0 0.9841 0.0189\n3220.0 0.9190 0.0196\n3450.0 0.8638 0.0204\n4500.0 0.6910 0.0242\n6000.0 0.5616 0.0293 / TABLE N0. 01\n/ TABLE N0. 02\n--\n-- PRES BG VISC\n-- PSIA RB/MSCF CPOISE\n-- ------ -------- ------\n14.7 265.0126 0.0133\n50.0 66.2531 0.0133\n100.0 33.1266 0.0133\n230.0 14.4552 0.0134\n460.0 7.0357 0.0136\n690.0 4.6493 0.0138\n920.0 3.4417 0.0140\n1150.0 2.7227 0.0144\n1380.0 2.2522 0.0147\n1610.0 1.9158 0.0151\n1840.0 1.6702 0.0156\n2070.0 1.4805 0.0162\n2300.0 1.3317 0.0167\n2372.0 1.2927 0.0169\n2530.0 1.2119 0.0173\n2760.0 1.1135 0.0180\n2990.0 1.0325 0.0187\n3220.0 0.9637 0.0194\n3450.0 0.9055 0.0201\n4500.0 0.7228 0.0236\n6000.0 0.5837 0.0285 / TABLE N0. 03\n/ TABLE N0. 04\nThere is no terminating “/” for this keyword.","size_kind":"fixed","variadic_record":true},"PVDO":{"name":"PVDO","sections":["PROPS"],"supported":null,"summary":"PVDO defines the oil PVT properties for dead oil218\n “Dead” oil is oil that it contains no dissolved gas or a relatively thick oil or residue that has lost its volatile components. . If the oil has a constant and uniform dissolved gas concentration, Gas-Oil Ratio (“GOR”), and if the reservoir pressure never drops below the saturation pressure (bubble point pressure), then the model can be run more efficiently by omitting the GAS and DISGAS keywords from the RUNSPEC section, treating the oil as a dead oil, and defining a constant Rs (GOR) value with keyword RSCONST or RSCONSTT in the PROPS section. This results in the model being run as a dead oil problem with no active gas phase. However, OPM Flow takes into account the constant Rs in the calculations and reporting.","parameters":[{"index":1,"name":"PRESS","description":"A columnar vector of real monotonically increasing down the column values that defines the oil phase pressure.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":["Pressure","1","Viscosity"]},{"index":2,"name":"OFVF","description":"A columnar vector of real decreasing down the column values that defines the corresponding oil phase formation volume factor.","units":{"field":"rb/stb","metric":"rm3/sm3","laboratory":"rcc/scc"},"default":"None"},{"index":3,"name":"OVISC","description":"A columnar vector of real increasing down the column values that defines the corresponding oil phase viscosity.","units":{"field":"cP","metric":"cP","laboratory":"cP"},"default":"None"}],"example":"The example below defines two dead oil PVT tables with variable viscosity and compressibility with respect to pressure, and assumes that NTPVT equals two and NPPVT is greater than or equal to eight on the TABDIMS keyword in the RUNSPEC section.\n--\n-- OIL PVT TABLE FOR DEAD OIL\n--\nPVDO\n-- PSAT BO VISC\n-- PSIA RB/STB CPOISE\n-- -------- ------- ------\n400 1.0102 1.16\n1200 1.0040 1.164\n2000 0.9960 1.167\n2800 0.9880 1.172\n3600 0.9802 1.177\n4400 0.9724 1.181\n5200 0.9646 1.185\n5600 0.9607 1.19 / TABLE NO. 01\n-- -------- ------- ------\n800 1.0255 1.14\n1600 1.0172 1.14\n2400 1.0091 1.14\n3200 1.0011 1.14\n4000 0.9931 1.14\n4800 0.9852 1.14\n5600 0.9774 1.14 / TABLE NO. 02\nThe second example defines four dead oil PVT tables with variable viscosity and compressibility with respect to pressure, and assumes that NTPVT equals four and NPPVT is greater than or equal to eight on the TABDIMS keyword in the RUNSPEC section. Here table two defaults to table one, and table four defaults to table three.\n--\n-- OIL PVT TABLE FOR DEAD OIL\n--\nPVDO\n-- PSAT BO VISC\n-- PSIA RB/STB CPOISE\n-- -------- ------- ------\n400 1.0102 1.16\n1200 1.0040 1.164\n2000 0.9960 1.167\n2800 0.9880 1.172\n3600 0.9802 1.177\n4400 0.9724 1.181\n5200 0.9646 1.185\n5600 0.9607 1.19 / TABLE NO. 01\n/ TABLE NO. 02\n800 1.0255 1.14\n1600 1.0172 1.14\n2400 1.0091 1.14\n3200 1.0011 1.14\n4000 0.9931 1.14\n4800 0.9852 1.14\n5600 0.9774 1.14 / TABLE NO. 03\n/ TABLE NO. 04\nThere is no terminating “/” for this keyword.","size_kind":"fixed","variadic_record":true},"PVDS":{"name":"PVDS","sections":["PROPS"],"supported":null,"summary":"PVDS defines the solvent PVT properties for use with SOLVENT option. The solvent is treated as an additional dry gas phase within the model. This keyword should only be used if the SOLVENT model has been invoked in the RUNSPEC section.","parameters":[{"index":1,"name":"PRESS","description":"A columnar vector of real monotonically increasing down the column values that defines the solvent phase pressure.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":["Pressure","OilDissolutionFactor","Viscosity"]},{"index":2,"name":"GFVF","description":"A columnar vector of real decreasing down the column values that defines the corresponding solvent phase formation volume factor.","units":{"field":"rb/Mscf","metric":"rm3/sm3","laboratory":"rcc/scc"},"default":"None"},{"index":3,"name":"GVISC","description":"A columnar vector of real increasing down the column values that defines the corresponding solvent phase viscosity.","units":{"field":"cP","metric":"cP","laboratory":"cP"},"default":"None"}],"example":"--\n-- GAS SOLVENT PVT TABLE\n--\nPVDS\n-- PRES BG VISC\n-- PSIA RB/MSCF CPOISE\n-- ------ -------- ------\n700.0 4.4703 0.0135\n920.0 3.2968 0.0138\n1150.0 2.6113 0.0141\n1380.0 2.1560 0.0145\n1610.0 1.8316 0.0150\n1840.0 1.5952 0.0155\n2070.0 1.4129 0.0161\n2300.0 1.2700 0.0167\n2372.0 1.2305 0.0169\n2530.0 1.1551 0.0174\n2760.0 1.0621 0.0181\n2990.0 0.9841 0.0189\n3220.0 0.9190 0.0196\n3450.0 0.8638 0.0204\n4500.0 0.6910 0.0242\n6000.0 0.5616 0.0293 / TABLE N0. 01\n--\n-- PRES BG VISC\n-- PSIA RB/MSCF CPOISE\n-- ------ -------- ------\n700.0 4.6493 0.0138\n920.0 3.4417 0.0140\n1150.0 2.7227 0.0144\n1380.0 2.2522 0.0147\n1610.0 1.9158 0.0151\n1840.0 1.6702 0.0156\n2070.0 1.4805 0.0162\n2300.0 1.3317 0.0167\n2372.0 1.2927 0.0169\n2530.0 1.2119 0.0173\n2760.0 1.1135 0.0180\n2990.0 1.0325 0.0187\n3220.0 0.9637 0.0194\n3450.0 0.9055 0.0201\n4500.0 0.7228 0.0236\n6000.0 0.5837 0.0285 / TABLE N0. 02\nThe above example defines two solvent PVT tables assuming NTPVT equals two and NPPVT is greater than or equal to 16 on the TABDIMS keyword in the RUNSPEC section.\nThere is no terminating “/” for this keyword.","size_kind":"fixed","variadic_record":true},"PVTG":{"name":"PVTG","sections":["PROPS"],"supported":null,"summary":"PVTG defines the gas PVT properties for wet gas219\n Natural gas that contains significant heavy hydrocarbons such as propane, butane and other liquid hydrocarbons is known as wet gas or rich gas. The general rule of thumb is if the gas contains less methane (typically less than 85% methane) and more ethane, and other more complex hydrocarbons, it is labeled as wet gas. Wet gas normally has GOR's less than 100,000 scf/stb or 18,000 Sm3/m3, with the condensate having a gravity greater than 50 oAPI.. This keyword should be used when the VAPOIL keyword has be declared in the RUNSPEC section indicating that that vaporized oil (more commonly referred to as condensate) is present in the wet gas phase. The keyword may be used for gas-water and oil-water-gas input decks that contain the oil and gas phases.","parameters":[{"index":1,"name":"PRESS","description":"A real monotonically increasing down the column vector that defines the gas phase pressure, associated with the saturated condensate-gas ratio (“CGR”) or Rv, the gas formation volume factor and the gas viscosity for the corresponding pressure for the stated saturated RVS. For a given PRESS the variability of the gas formation volume factor and the gas viscosity with respect to the under-saturated Rv is optionally included as a sub table under RVU, FVFU and VISU columns, that is it is not necessary to repeat PRESS for each sub table entry. However, each sub table must be terminated by a “/”. The under saturated Rv entries are optional, except for perhaps the last PRESS entry to define the PVT properties above the initial saturation pressure.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":"Pressure"},{"index":2,"name":"RVS / RVU","description":"A columnar vector of real positive number for both the saturated (RVS) and under saturated (RVU) Rv sub table entries. The RVS entry on the main table is the saturated CGR at the pressure indicated by PRESS and may be increasing or decreasing in value as PRESS varies. Subsequent under-saturated Rv for a sub table at the given PRESS, as defined by RVU, are monotonically decreasing for entries in a given sub table.","units":{"field":"stb/Mscf","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"None","value_type":"DOUBLE","dimension":["OilDissolutionFactor","OilDissolutionFactor","Viscosity"]},{"index":3,"name":"FVFS / FVFU","description":"A columnar vector of real decreasing down the column values that defines the corresponding gas phase formation volume factor for a given pressure (PRESS) and for a given Rv (either RVS or RVU).","units":{"field":"rb/Mscf","metric":"rm3/sm3","laboratory":"rcc/scc"},"default":"None"},{"index":4,"name":"VISS / VISU","description":"VISS a columnar vector of real increasing down the column values that defines the corresponding gas phase viscosity for a given pressure (PRESS) and for a given RVS. VISU a columnar vector of real decreasing from VISS down the column values that defines the corresponding gas phase viscosity for a given pressure (PRESS) and for a given RVU.","units":{"field":"cP","metric":"cP","laboratory":"cP"},"default":"None"}],"example":"The first example defines two wet gas PVT tables assuming NTPVT equals two, NPPVT is greater than or equal to eight, and NRPVT greater than or equal to two on the TABDIMS keyword in the RUNSPEC section.\n--\n-- GAS PVT TABLE FOR WET GAS WITH VAPORIZED OIL\n--\nPVTG\n-- PRES RV BG VISC\n-- BARSASM^3/SM^3 RM^3/SM^3 CPOISE\n-- ------ --------- ------- ------\n20 0.000132 0.042340 0.01344\n0 0.042310 0.01389 /\n40 0.000124 0.020460 0.01420\n0 0.020430 0.01450 /\n60 0.000126 0.013280 0.01526\n0 0.013250 0.01532 /\n80 0.000135 0.009770 0.01660\n0 0.009730 0.01634 /\n100 0.000149 0.007730 0.01818\n0 0.007690 0.01752 /\n120 0.000163 0.006426 0.01994\n0 0.006405 0.01883 /\n140 0.000191 0.005541 0.02181\n0 0.005553 0.02021 /\n160 0.000225 0.004919 0.02370\n0 0.004952 0.02163 /\n/ TABLE NO. 1\n-- PRES RV BG VISC\n-- BARSASM^3/SM^3 RM^3/SM^3 CPOISE\n-- ------ --------- ------- ------\n20 0.000132 0.042340 0.01344 /\n40 0.000124 0.020460 0.01420 /\n60 0.000126 0.013280 0.01526 /\n80 0.000135 0.009770 0.01660 /\n100 0.000149 0.007730 0.01818 /\n120 0.000163 0.006426 0.01994 /\n140 0.000191 0.005541 0.02181 /\n160 0.000225 0.004919 0.02370\n0 0.004952 0.02163 /\n/ TABLE NO. 2\nThe second example defines four wet gas PVT tables assuming NTPVT equals four, NPPVT is greater than or equal to eight, and NRPVT greater than or equal to two on the TABDIMS keyword in the RUNSPEC section. Here table two defaults to table one, and table four defaults to table three.\n--\n-- GAS PVT TABLE FOR WET GAS WITH VAPORIZED OIL\n--\nPVTG\n-- PRES RV BG VISC\n-- BARSASM^3/SM^3 RM^3/SM^3 CPOISE\n-- ------ --------- ------- ------\n20 0.000132 0.042340 0.01344\n0 0.042310 0.01389 /\n40 0.000124 0.020460 0.01420\n0 0.020430 0.01450 /\n60 0.000126 0.013280 0.01526\n0 0.013250 0.01532 /\n80 0.000135 0.009770 0.01660\n0 0.009730 0.01634 /\n100 0.000149 0.007730 0.01818\n0 0.007690 0.01752 /\n120 0.000163 0.006426 0.01994\n0 0.006405 0.01883 /\n140 0.000191 0.005541 0.02181\n0 0.005553 0.02021 /\n160 0.000225 0.004919 0.02370\n0 0.004952 0.02163 /\n/ TABLE NO. 1\n/ TABLE NO. 2\n-- PRES RV BG VISC\n-- BARSASM^3/SM^3 RM^3/SM^3 CPOISE\n-- ------ --------- ------- ------\n20 0.000132 0.042340 0.01344 /\n40 0.000124 0.020460 0.01420 /\n60 0.000126 0.013280 0.01526 /\n80 0.000135 0.009770 0.01660 /\n100 0.000149 0.007730 0.01818 /\n120 0.000163 0.006426 0.01994 /\n140 0.000191 0.005541 0.02181 /\n160 0.000225 0.004919 0.02370\n0 0.004952 0.02163 /\n/ TABLE NO. 3\n/ TABLE NO. 4\nNotice that in both examples there is no terminating “/” for this keyword only for a table and a sub table.\n| Note If the VAPWAT keyword in the RUNSPEC section is also present in the input deck, then the PVTG keyword in the PROPS section should be used to define the gas properties as function of pressure and RV, assuming water-saturated gas. Also, in this case, the PVTGW keyword, also in the PROPS section, should also be in the input deck. In this case, PVTGW defines the gas properties as function of pressure and RVW, assuming oil-saturated gas. |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"list","variadic_record":true},"PVTGW":{"name":"PVTGW","sections":["PROPS"],"supported":null,"summary":"PVTGW defines the gas PVT properties for dry gas1\n Natural gas that occurs in the absence of condensate or liquid hydrocarbons, or gas that had condensable hydrocarbons removed, is called dry gas. It is primarily methane with some intermediates. The hydrocarbon mixture is solely gas in the reservoir and there is no liquid (condensate surface liquid) formed either in the reservoir or at surface. The term dry indicates that the gas does not contain heavier hydrocarbons to form liquids at the surface conditions. Dry gas typically has GOR's greater than 100,000 scf/stb or 18,000 Sm3/m3. with vaporized water. This keyword should be used when the VAPWAT keyword has be declared in the RUNSPEC section indicating that that vaporized water is present in the dry gas phase. The keyword may be used for gas-water and oil-water-gas input decks that contain the dry gas and vaporized water phases.","parameters":[{"index":1,"name":"PRESS","description":"A real monotonically increasing down the column vector that defines the gas phase pressure, associated with the corresponding saturated water-gas ratio (“WGR”) or Rw, the gas formation volume factor, and the gas viscosity for the stated saturated RWS. For a given PRESS the variability of the gas formation volume factor and the gas viscosity with respect to the under-saturated Rw is optionally included as a sub table under RWU, FVFU and VISU columns, that is it is not necessary to repeat PRESS for each sub table entry. However, each sub table must be terminated by a “/”. The under saturated Rw entries are optional, except for perhaps the last PRESS entry to define the PVT properties above the initial saturation pressure.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":"Pressure"},{"index":2,"name":"RWS / RWU","description":"A columnar vector of real positive numbers for both the saturated (RWS) and under saturated (RWU) Rw sub table entries. The RWS entry on the main table is the saturated WGR at the pressure indicated by PRESS and may be increasing or decreasing in value as PRESS varies. Subsequent under-saturated Rw for a sub table at the given PRESS, as defined by RWU, are monotonically decreasing for entries in a given sub table.","units":{"field":"stb/Mscf","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"None","value_type":"DOUBLE","dimension":["OilDissolutionFactor","OilDissolutionFactor","Viscosity"]},{"index":3,"name":"FVFS / FVFU","description":"A columnar vector of real decreasing down the column values that defines the corresponding gas phase formation volume factor for a given pressure (PRESS) and for a given Rw (either RWS or RWU).","units":{"field":"rb/Mscf","metric":"rm3/sm3","laboratory":"rcc/scc"},"default":"None"},{"index":4,"name":"VISS / VISU","description":"VISS a columnar vector of real increasing down the column values that defines the corresponding gas phase viscosity for a given pressure (PRESS) and for a given RWS. VISU a columnar vector of real decreasing from VISS down the column values that defines the corresponding gas phase viscosity for a given pressure (PRESS) and for a given RWU.","units":{"field":"cP","metric":"cP","laboratory":"cP"},"default":"None"}],"example":"--\n-- GAS PVT TABLE FOR DRY GAS WITH VAPORIZED WATER (OPM FLOW KEYWORD)\n--\nPVTGW\n-- PRES RW BG VISC\n-- PSIA SM^3/SM^3 RM^3/SM^3 CPOISE\n-- ------ --------- ------- ------\n300 0.000479 0.042340 0.01344\n0 0.042310 0.01389 /\n600 0.000469 0.020460 0.01420\n0 0.020430 0.01450 /\n900 0.000403 0.013280 0.01526\n0 0.013250 0.01532 /\n1200 0.000354 0.009770 0.01660\n0 0.009730 0.01634 /\n1500 0.000272 0.007730 0.01818\n0 0.007690 0.01752 /\n1800 0.000225 0.006426 0.01994\n0 0.006405 0.01883 /\n2100 0.000191 0.005541 0.02181\n0 0.005553 0.02021 /\n2400 0.000163 0.004919 0.02370\n0 0.004952 0.02163 /\n/ TABLE NO. 1\n-- PRES RW BG VISC\n-- PSIA SM^3/SM^3 RM^3/SM^3 CPOISE\n-- ------ --------- ------- ------\n300 0.000479 0.042340 0.01344 /\n600 0.000469 0.020460 0.01420 /\n900 0.000403 0.013280 0.01526 /\n1200 0.000354 0.009770 0.01660 /\n1500 0.000272 0.007730 0.01818 /\n1800 0.000225 0.006426 0.01994 /\n2100 0.000191 0.005541 0.02181 /\n2400 0.000163 0.004919 0.02370 /\n/ TABLE NO. 2\nThe above example defines two dry gas PVT tables assuming NTPVT equals two and NPPVT is greater than or equal to eight on the TABDIMS keyword in the RUNSPEC section.\nNotice that there is no terminating “/” for this keyword only for a table and a sub table.\n| Note This is an OPM Flow specific keyword for the simulator’s Water Vaporization Model that is activated by declaring that vaporized water is present in the run. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Note If both the VAPWAT and VAPOIL keywords have been declared in the RUNSPEC section indicating that both vaporized water and vaporized oil are present in the wet gas, then the PVTGW keyword should be used along with the PVTG keyword in the PROPS section to fully define the wet gas PVT properties. The PVTGW keyword should be used to define the gas properties as a function of pressure and water-gas ratio (RVW), assuming oil-saturated gas. The PVTG keyword should be used to define the gas properties as a function of pressure and oil-gas ratio (RV), assuming water-saturated gas. Alternatively, the PVTGWO keyword in the PROPS section may be used instead of the PVTGW and PVTG keywords to fully define the wet gas PVT properties. |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"list","variadic_record":true},"PVTGWO":{"name":"PVTGWO","sections":["PROPS"],"supported":false,"summary":"PVTGWO defines the gas PVT properties for wet gas1\n Natural gas that contains significant heavy hydrocarbons such as propane, butane and other liquid hydrocarbons is known as wet gas or rich gas. The general rule of thumb is if the gas contains less methane (typically less than 85% methane) and more ethane, and other more complex hydrocarbons, it is labeled as wet gas. Wet gas normally has GOR's less than 100,000 scf/stb or 18,000 Sm3/m3, with the condensate having a gravity greater than 50 oAPI. with vaporized water and oil. This keyword should be used when the VAPOIL and VAPWAT keywords have been declared in the RUNSPEC section indicating that vaporized oil and water are present in the wet gas phase. The keyword may be used for oil-water-gas input decks that contain the wet gas with vaporized oil and water phases.","parameters":[{"index":1,"name":"PRESS","description":"A real monotonically increasing down the column vector that defines the gas phase pressure, associated with the saturated water-gas ratio (“WGR”) or Rw, the saturated condensate-gas ratio (“CGR”) or Rv, the gas formation volume factor, and the gas viscosity for the corresponding pressure for the stated saturated RWS. For a given PRESS the variability of the gas formation volume factor and the gas viscosity with respect to the under-saturated Rw and Rv is optionally included as a sub table under RWU, RVU, FVFU and VISU columns, that is it is not necessary to repeat PRESS for each sub table entry. However, each sub table must be terminated by a “/”. The under saturated Rw and Rv entries are optional, except for perhaps the last PRESS entry to define the PVT properties above the initial saturation pressure.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":"Pressure"},{"index":2,"name":"RWS / RWU","description":"A columnar vector of real positive numbers for both the saturated (RWS) and under saturated (RWU) Rw sub table entries. The RWS entry on the main table is the saturated WGR at the pressure indicated by PRESS and may be increasing or decreasing in value as PRESS varies. Subsequent under-saturated Rw for a sub table at the given PRESS, as defined by RWU, are monotonically decreasing for entries in a given sub table.","units":{"field":"stb/Mscf","metric":"sm3/sm3","laboratory":"rcc/scc"},"default":"None","value_type":"DOUBLE","dimension":["OilDissolutionFactor","OilDissolutionFactor","OilDissolutionFactor","Viscosity"]},{"index":3,"name":"RVS / RVU","description":"A columnar vector of real positive numbers for both the saturated (RVS) and under saturated (RVU) Rv sub table entries. The RVS entry on the main table is the saturated CGR at the pressure indicated by PRESS and may be increasing or decreasing in value as PRESS varies. Subsequent under-saturated Rv for a sub table at the given PRESS, as defined by RVU, are monotonically decreasing for entries in a given sub table.","units":{"field":"stb/Mscf","metric":"sm3/sm3","laboratory":"rcc/scc"},"default":"None"},{"index":4,"name":"FVFS / FVFU","description":"A columnar vector of real decreasing down the column values that defines the corresponding gas phase formation volume factor for a given pressure (PRESS) and for a given Rw (either RWS or RWU) and Rv (either RVS or RVU).","units":{"field":"rb/Mscf","metric":"rm3/sm3","laboratory":"rcc/scc"},"default":"None"},{"index":5,"name":"VISS / VISU","description":"VISS a columnar vector of real increasing down the column values that defines the corresponding gas phase viscosity for a given pressure (PRESS) and for a given RWS and RVS. VISU a columnar vector of real decreasing from VISS down the column values that defines the corresponding gas phase viscosity for a given pressure (PRESS) and for a given RWU and RVU.","units":{"field":"cP","metric":"cP","laboratory":"cP"},"default":"None"}],"example":"--\n-- GAS PVT TABLE FOR WET GAS WITH VAPORIZED WATER & OIL (OPM FLOW KEYWORD)\n--\nPVTGWO\n-- PRES RW RV BG VISC\n-- PSIA STB/MSCF STB/MSCF RB/MSCF CPOISE\n-- ------ -------- --------- ------- ------\n300 0.000479 0.000132 0.042340 0.01344\n0 0 0.042310 0.01389 /\n600 0.000469 0.000124 0.020460 0.01420\n0 0 0.020430 0.01450 /\n900 0.000403 0.000126 0.013280 0.01526\n0 0 0.013250 0.01532 /\n1200 0.000354 0.000135 0.009770 0.01660\n0 0 0.009730 0.01634 /\n1500 0.000272 0.000149 0.007730 0.01818\n0 0 0.007690 0.01752 /\n1800 0.000225 0.000163 0.006426 0.01994\n0 0 0.006405 0.01883 /\n2100 0.000191 0.000191 0.005541 0.02181\n0 0 0.005553 0.02021 /\n2400 0.000163 0.000225 0.004919 0.02370\n0 0 0.004952 0.02163 /\n/ TABLE NO. 1\n-- PRES RW RV BG VISC\n-- PSIA STB/MSCF STB/MSCF RB/MSCF CPOISE\n-- ------ -------- --------- ------- ------\n300 0.000479 0.000132 0.042340 0.01344 /\n600 0.000469 0.000124 0.020460 0.01420 /\n900 0.000403 0.000126 0.013280 0.01526 /\n1200 0.000354 0.000135 0.009770 0.01660 /\n1500 0.000272 0.000149 0.007730 0.01818 /\n1800 0.000225 0.000163 0.006426 0.01994 /\n2100 0.000191 0.000191 0.005541 0.02181 /\n2400 0.000163 0.000225 0.004919 0.02370 /\n/ TABLE NO. 2\nThe above example defines two wet PVT tables assuming NTPVT equals two and NPPVT is greater than or equal to eight on the TABDIMS keyword in the RUNSPEC section.\nNotice that there is no terminating “/” for this keyword only for a table and a sub table.\n| Note This is an OPM Flow specific keyword for the simulator’s Water Vaporization Model that is activated by declaring that vaporized water is present in the run. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"list","variadic_record":true},"PVTO":{"name":"PVTO","sections":["PROPS"],"supported":null,"summary":"PVTO defines the oil PVT properties for live oil222\n “Live” oil is oil that contains gas in solution, which is normally the case for most conventional oil reservoirs. However, for oil reservoirs classified as heavy oil reservoirs, the in situ dissolved gas may be negligible and oil would then be classified as gas-free oil which is commonly referred to as “dead” oil. and the keyword should only be used if the there is both oil and gas phases in the model. This keyword should be used when the DISGAS keyword has be declared in the RUNSPEC section indicating that dissolved gas (more commonly referred to as solution gas) is present in the oil. The keyword may be used for oil-water and oil-water-gas input decks.","parameters":[{"index":1,"name":"RS","description":"A real monotonically increasing down the column values that defines the saturated gas-oil ratio (“GOR”) or Rs, that defines the oil formation volume factor and the oil viscosity for the tabulated corresponding pressure for stated saturated RS. For a given RS the variability of the oil formation volume factor and the oil viscosity with respect to the saturated RS and pressure is optionally included as a sub table under PRSU, FVFU and VISU columns, that is it is not necessary to repeat RS for each sub table entry. However, each sub table must be terminated by a “/”. The under-saturated PRSU entries are optional, except for perhaps the last RS entry to define the PVT properties above the initial saturation pressure. If there are no following under-saturated PRSU entries then the RS entry row should be terminated by a “/”, if there are under-saturated PRSU entries then the last PRSU entry row should be terminated by a “/”.","units":{"field":"Mscf/stb","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"None","value_type":"DOUBLE","dimension":"GasDissolutionFactor"},{"index":2,"name":"PRSS / PRSU","description":"PRSS is a real columnar vector of real monotonically increasing down the column values that defines the oil phase saturation pressure (bubble-point pressure), that defines the oil formation volume factor and the oil viscosity for the corresponding PRSS pressure for a given saturated RS. PRSU is a real columnar vector of real monotonically increasing down the column values that defines the oil phase under-saturated pressure that defines the oil formation volume factor and the oil viscosity for the corresponding PRSU pressure for a given saturated RS. Note that PRSU should be greater than PRSS.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":["Pressure","1","Viscosity"]},{"index":3,"name":"FVFS / FVFU","description":"FVFS is a columnar vector of real increasing down the column values that defines the corresponding oil phase saturated formation volume factor for a given pressure (PRSS) and for a given RS. FVFU is a columnar vector of real decreasing down the column values that defines the corresponding oil phase under-saturated formation volume factor for a given pressure (PRSU) and for a given RS.","units":{"field":"rb/stb","metric":"rm3/sm3","laboratory":"rcc/scc"},"default":"None"},{"index":4,"name":"VISS / VISU","description":"VISS a columnar vector of real increasing down the column values that defines the corresponding oil phase saturated viscosity for a given pressure (PRSS) and for a given RS. If this is the only entry for a given RS and PRSS then the record should be terminate by a “/”. VISU a columnar vector of real decreasing from VISS down the column values that defines the corresponding oil phase under-saturated viscosity for a given pressure (PRSU) and for a given RS. If this is the only entry for a given RS and PRSU then the record should be terminate by a “/”.","units":{"field":"cP","metric":"cP","laboratory":"cP"},"default":"None"}],"example":"The first example defines live oil PVT tables assuming NTPVT equals two, NPPVT is greater than or equal to two, and NRPVT is greater than or equal to 18 on the TABDIMS keyword in the RUNSPEC section.\n--\n-- OIL PVT TABLE FOR LIVE OIL\n--\nPVTO\n-- RS PSAT BO VISC\n-- MSCF/STB PSIA RB/STB CPOISE\n-- -------- -------- ------- ------\n0.0010 14.7 1.05340 1.7230 /\n0.0890 500.0 1.08890 1.1670 /\n0.2060 1000.0 1.13850 0.8570 /\n0.3360 1500.0 1.19640 0.6840 /\n0.4750 2000.0 1.26110 0.5750 /\n0.5480 2250.0 1.29570 0.5340 /\n0.6220 2500.0 1.33160 0.5000 /\n0.6980 2750.0 1.36890 0.4700 /\n0.7750 3000.0 1.40740 0.4450 /\n0.8530 3250.0 1.44710 0.4220 /\n0.9330 3500.0 1.48790 0.4020 /\n1.0140 3750.0 1.52980 0.3840 /\n1.0960 4000.0 1.57280 0.3680 /\n1.1800 4258.0 1.61760 0.3530 /\n1.2630 4500.0 1.66190 0.3400 /\n1.3480 4750.0 1.70780 0.3280 /\n1.4340 5000.0 1.75480 0.3170 /\n1.6060 5500.0 1.85020 0.2980\n6242.0 1.83040 0.3186 /\n/ TABLE NO. 1\n--\n--\n-- RS PSAT BO VISC\n-- MSCF/STB PSIA RB/STB CPOISE\n-- -------- -------- ------- ------\n0.0010 14.7 1.05340 1.7230 /\n0.0390 250.0 1.06830 1.4220 /\n0.0890 500.0 1.08890 1.1670 /\n0.1460 750.0 1.11250 0.9850 /\n0.2060 1000.0 1.13850 0.8570 /\n0.2700 1250.0 1.16660 0.7590 /\n0.3360 1500.0 1.19640 0.6840 /\n0.4050 1750.0 1.22800 0.6240 /\n0.4750 2000.0 1.26110 0.5750 /\n0.5480 2250.0 1.29570 0.5340 /\n0.6220 2500.0 1.33160 0.5000 /\n0.6980 2750.0 1.36890 0.4700 /\n0.7750 3000.0 1.40740 0.4450 /\n0.8530 3250.0 1.44710 0.4220 /\n0.9330 3500.0 1.48790 0.4020 /\n1.0140 3750.0 1.52980 0.3840 /\n1.0960 4000.0 1.57280 0.3680 /\n1.1800 4258.0 1.61760 0.3530 /\n1.2630 4500.0 1.66190 0.3400 /\n1.3480 4750.0 1.70780 0.3280 /\n1.4340 5000.0 1.75480 0.3170 /\n1.6060 5500.0 1.85020 0.2980\n6242.0 1.83040 0.3186 /\n/ TABLE NO. 2\nNotice that there must be at least two entries for the last Rs value to enable the simulator to interpolate over the undersaturated pressure region.\nThe second example defines live oil PVT tables assuming NTPVT equals four, NPPVT is greater than or equal to two, and NRPVT is greater than or equal to 13 on the TABDIMS keyword in the RUNSPEC section. Here, tables two to four all default to table number one.\n--\n-- OIL PVT TABLE FOR LIVE OIL\n--\nPVTO\n-- RS PSAT BO VISC\n-- MSCF/STB PSIA RB/STB CPOISE\n-- -------- -------- ------- ------\n0.0010 14.7 1.05340 1.7230 /\n0.0890 500.0 1.08890 1.1670 /\n0.2060 1000.0 1.13850 0.8570 /\n0.3360 1500.0 1.19640 0.6840 /\n0.4750 2000.0 1.26110 0.5750 /\n0.5480 2250.0 1.29570 0.5340 /\n0.6220 2500.0 1.33160 0.5000 /\n0.7750 3000.0 1.40740 0.4450 /\n0.9330 3500.0 1.48790 0.4020 /\n1.0960 4000.0 1.57280 0.3680 /\n1.2630 4500.0 1.66190 0.3400 /\n1.4340 5000.0 1.75480 0.3170 /\n1.6060 5500.0 1.85020 0.2980\n6242.0 1.83040 0.3186 /\n/ TABLE NO. 1\n/ TABLE NO. 2\n/ TABLE NO. 3\n/ TABLE NO. 4\nAgain, note that there is no terminating “/” for this keyword only for a table and a sub table.","size_kind":"list","variadic_record":true},"PVTSOL":{"name":"PVTSOL","sections":["PROPS"],"supported":null,"summary":"PVTSOL defines the live oil PVT properties as a function of CO2 mass fraction. The keyword automatically invokes the simulator’s CO2 Dynamic EOR Model223\n T. H. Sandve, O. Sævareid and I. Aavatsmark: “Improved Extended Blackoil Formulation -- for CO2 EOR Simulations.” in ECMOR XVII – The 17th European Conference on the -- Mathematics of Oil Recovery, September 2020. , that uses a fourth component to model the injected CO2., for use in evaluating CO2 Enhanced Oil Recovery (“EOR”) projects. Normally CO2 EOR projects are evaluated via compositional simulators to account for the mass transfer of the various components and phases. Unfortunately, compositional models are computationally expensive compared to the black-oil approach, which for field studies is challenging, especially if an ensemble approach is being used to capture the uncertainties. Previous extended black-oil formulations often poorly represent the PVT properties of the oil-CO2 mixtures, resulting in poor agreement wi...","parameters":[{"index":1,"name":"CO2","description":"A real monotonically increasing down the column values that stipulates the CO2 mass fraction, that defines the oil and gas properties, formation volume factor, viscosity etc., for the tabulated corresponding pressure for the stated CO2 mass fraction. CO2 should be greater than or equal to zero and less than or equal to one. Note it is not necessary to repeat the value of CO2 for the pressure column. However, for a given CO2 mass fraction, the last pressure entry (PRESS) of the sub table should be terminated by a “/”.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":"1"},{"index":2,"name":"PRESS","description":"PRESS is a real columnar vector of real monotonically increasing down the column values that defines the oil phase saturation pressure (bubble-point pressure), that defines the oil formation volume factor and the oil viscosity for the corresponding PRESS pressure for a given saturated value of CO2.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":["Pressure","1","OilDissolutionFactor","GasDissolutionFactor","OilDissolutionFactor","1","1","Viscosity","Viscosity"]},{"index":3,"name":"OFVF","description":"OFVF is a columnar vector of real increasing down the column values that defines the corresponding oil phase saturated formation volume factor for a given pressure (PRESS) and for a given saturated value of CO2.","units":{"field":"rb/stb","metric":"rm3/sm3","laboratory":"rcc/scc"},"default":"None"},{"index":4,"name":"GFVF","description":"GFVF is a columnar vector of real decreasing down the column values that defines the corresponding gas phase saturated formation volume factor for a given pressure (PRESS) and for a given saturated value of CO2.","units":{"field":"rb/Mscf","metric":"rm3/sm3","laboratory":"rcc/scc"},"default":"None"},{"index":5,"name":"RS","description":"RS is a real monotonically increasing down the column values that defines the saturated gas-oil ratio (“GOR”) or Rs, for the given value of PRESS and for a given saturated value of CO2.","units":{"field":"Mscf/stb","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"None"},{"index":6,"name":"RV","description":"RV is a real monotonically increasing down the column values that defines the saturated condensate-gas ratio (“CGR”) or Rv, for the given value of PRESS and for a given saturated value of CO2.","units":{"field":"stb/Mscf","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"None"},{"index":7,"name":"XVOL","description":"XVOL is a real positive value greater than or equal to zero and less than or equal to one, that stipulates the volumetric fraction of CO2 in the oil phase, that is: [XVOL~=~{Volume_oil (CO_2)} over { Volume_oil (CO_2) `+` Volume_oil (Gas) `+` Volume_oil (Oil)}] where: Volume oil (CO2) is the surface volume of CO2 in the oil phase, Volume oil (Gas) is the surface volume of gas in the oil phase, and Volume oil (Oil) is the surface volume of oil in the oil phase.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":8,"name":"YVOL","description":"YVOL is a real positive value greater than or equal to zero and less than or equal to one, that defines the volumetric fraction of CO2 in the gas phase, that is: [YVOL~=~{Volume_gas (CO_2)} over { Volume_gas (CO_2)`+` Volume_gas (Gas)`+` Volume_gas (Oil) }] where: Volume gas (CO2) is the surface volume of CO2 in the gas phase, Volume gas (Gas) is the surface volume of gas in the gas phase, and Volume gas (Oil) is the surface volume of oil in the gas phase.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":9,"name":"OVISC","description":"OVISC is a columnar vector of real decreasing down the column values that defines the corresponding oil phase saturated viscosity for a given pressure (PRESS) and for a given saturated value of CO2.","units":{"field":"cP","metric":"cP","laboratory":"cP"},"default":"None"},{"index":10,"name":"GVISC","description":"GVISC is a columnar vector of real increasing down the column values that defines the corresponding gas phase saturated viscosity for a given pressure (PRESS) and for a given saturated value of CO2.","units":{"field":"cP","metric":"cP","laboratory":"cP"},"default":"None"}],"example":"--\n-- OIL PVT PROPERTIES FOR LIVE OIL VERSUS CO2 MASS FRACTION\n--\nPVTSOL\n-- CO2 PSAT BO BG RS RV XVOL YVOL OIL VISC GAS VISC\n-- MFRAC PSIA RB/STB RB/MSCF MSCF/STB STB/MSCF CPOISE CPOISE\n-- ----- ------- ------ ---------- -------- ---------- ------ ------ ---------- ----------\n0.000 14.50 1.0000 1.7810e+02 0.0000 0.0000e+00 0.0000 0.0000 2.0340e-01 1.3016e-02\n725.18 1.0655 6.0855e+00 0.1302 1.4432e-04 0.0000 0.0000 2.0340e-01 1.3016e-02\n870.22 1.0806 5.0340e+00 0.1591 1.9594e-04 0.0000 0.0000 1.9973e-01 1.3222e-02\n1015.26 1.0961 4.2814e+00 0.1886 2.8389e-04 0.0000 0.0000 1.9609e-01 1.3452e-02\n1160.30 1.1121 3.7174e+00 0.2189 4.1914e-04 0.0000 0.0000 1.9246e-01 1.3708e-02\n1305.33 1.1285 3.2799e+00 0.2499 6.0779e-04 0.0000 0.0000 1.8886e-01 1.3994e-02\n1450.37 1.1454 2.9314e+00 0.2819 8.5105e-04 0.0000 0.0000 1.8527e-01 1.4309e-02\n1595.41 1.1629 2.6479e+00 0.3148 1.1490e-03 0.0000 0.0000 1.8171e-01 1.4657e-02\n1740.45 1.1809 2.4133e+00 0.3487 1.5030e-03 0.0000 0.0000 1.7819e-01 1.5037e-02\n1885.49 1.1996 2.2163e+00 0.3838 1.9155e-03 0.0000 0.0000 1.7469e-01 1.5450e-02\n2030.52 1.2189 2.0490e+00 0.4200 2.3899e-03 0.0000 0.0000 1.7122e-01 1.5897e-02\n2175.56 1.2389 1.9055e+00 0.4574 2.9302e-03 0.0000 0.0000 1.6779e-01 1.6377e-02\n2320.60 1.2597 1.7812e+00 0.4962 3.5412e-03 0.0000 0.0000 1.6440e-01 1.6890e-02\n2465.64 1.2812 1.6728e+00 0.5364 4.2273e-03 0.0000 0.0000 1.6104e-01 1.7435e-02\n2610.67 1.3037 1.5775e+00 0.5782 4.9942e-03 0.0000 0.0000 1.5772e-01 1.8011e-02\n2755.71 1.3270 1.4933e+00 0.6216 5.8471e-03 0.0000 0.0000 1.5443e-01 1.8617e-02\n2900.75 1.3514 1.4185e+00 0.6668 6.7918e-03 0.0000 0.0000 1.5117e-01 1.9253e-02\n3045.79 1.3768 1.3517e+00 0.7139 7.8347e-03 0.0000 0.0000 1.4795e-01 1.9917e-02\n3137.32 1.3937 1.3132e+00 0.7450 8.5549e-03 0.0000 0.0000 1.4592e-01 2.0353e-02\n4061.05 1.3705 1.3132e+00 0.7450 8.5549e-03 0.0000 0.0000 1.5939e-01 2.0353e-02 /\n0.010 14.50 1.0000 1.7810e+02 0.0000 0.0000e+00 0.0464 0.0381 2.0301e-01 1.3203e-02\n725.18 1.0670 6.0041e+00 0.1341 1.4845e-04 0.0464 0.0381 2.0301e-01 1.3203e-02\n…………….………….….…….…….…….…….……….………….…….…….…….………….…….……….……………….……….…...…….…….….…….…………...\n3135.04 1.4082 1.2950e+00 0.7755 8.9113e-03 0.0298 0.0277 1.4422e-01 2.0743e-02\n4061.05 1.3840 1.2950e+00 0.7755 8.9113e-03 0.0298 0.0277 1.5772e-01 2.0743e-02 /\n0.100 14.50 1.0000 1.7810e+02 0.0000 0.0000e+00 0.3426 0.3023 1.9984e-01 1.4740e-02\n725.18 1.0795 5.3329e+00 0.1666 1.8243e-04 0.3426 0.3023 1.9984e-01 1.4740e-02\n…………….………….….…….…….…….…….……….………….…….…….…….………….…….……….……………….……….…...…….…….….…….…………...\n3116.25 1.5281 1.1444e+00 1.0268 1.1849e-02 0.2492 0.2431 1.3023e-01 2.3961e-02\n4061.05 1.4955 1.1444e+00 1.0268 1.1849e-02 0.2492 0.2431 1.4400e-01 2.3961e-02 /\n0.200 14.50 1.0000 1.7810e+02 0.0000 0.0000e+00 0.5303 0.4898 1.9699e-01 1.5838e-02\n725.18 1.0909 4.8402e+00 0.1964 2.1919e-04 0.5303 0.4898 1.9699e-01 1.5838e-02\n…………….………….….…….…….…….…….……….………….…….…….…….………….…….……….……………….……….…...…….…….….…….…………...\n4061.05 1.6501 1.0017e+00 1.3720 1.6728e-02 0.4220 0.4240 1.2963e-01 2.7757e-02 /\n0.300 14.50 1.0000 1.7810e+02 0.0000 0.0000e+00 0.6486 0.6159 1.9471e-01 1.6588e-02\n725.18 1.1003 4.4992e+00 0.2210 2.5440e-04 0.6486 0.6159 1.9471e-01 1.6588e-02\n…………….………….….…….…….…….…….……….………….…….…….…….………….…….……….……………….……….…...…….…….….…….…………...\n4061.05 1.8529 8.8189e-01 1.8200 2.4541e-02 0.5491 0.5597 1.1636e-01 3.2195e-02 /\n0.400 14.50 1.0000 1.7810e+02 0.0000 0.0000e+00 0.7303 0.7059 1.9292e-01 1.7131e-02\n725.18 1.1079 4.2506e+00 0.2413 2.8832e-04 0.7303 0.7059 1.9292e-01 1.7131e-02\n…………….………….….…….…….…….…….……….………….…….…….…….………….…….……….……………….……….…...…….…….….…….…………...\n4061.05 2.1298 7.8515e-01 2.4251 3.7664e-02 0.6468 0.6616 1.0441e-01 3.7755e-02 /\n0.500 14.50 1.0000 1.7810e+02 0.0000 0.0000e+00 0.7905 0.7733 1.9156e-01 1.7543e-02\n725.18 1.1140 4.0628e+00 0.2581 3.2217e-04 0.7905 0.7733 1.9156e-01 1.7543e-02\n…………….………….….…….…….…….…….……….………….…….…….…….………….…….……….……………….……….…...…….…….….…….…………...\n4061.05 2.5282 7.1557e-01 3.2879 6.07","size_kind":"list","variadic_record":true},"PVTW":{"name":"PVTW","sections":["PROPS"],"supported":null,"summary":"PVTW defines the water properties for various regions in the model. The number of PVTW vector data sets is defined by the NTPVT parameter on the TABDIMS keyword in the RUNSPEC section and the allocation of the PVTW tables to different grid blocks in the model is done via the PVTNUM keyword in the REGIONS section. One data set consists of one record or line which is terminated by a “/”. If the water phase is active in the model, which is normally the case, then this keyword must be defined in the OPM Flow input deck.","parameters":[{"index":1,"name":"PRES","description":"PRES is a real number defining the water reference pressure (P) for the other parameters for this data set.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":"Pressure"},{"index":2,"name":"WFVF","description":"WFVF is a real number defining the water formation volume factor (Bw) at the water reference pressure.","units":{"field":"rb/stb 1.0","metric":"rm3/sm3 1.0","laboratory":"rcc/scc 1.0"},"default":"Defined","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"WCOMP","description":"WCOMP is a real number defining the water compressibility (Cw) at the water reference pressure and is defined as: [C sub{w}~=~ - 1 over {B sub{w}}left({dB sub{w}} over{dP} right)]","units":{"field":"1/psia 0.00004","metric":"1/barsa 0.00004","laboratory":"1/atma 0.00004"},"default":"Defined","value_type":"DOUBLE","dimension":"1/Pressure"},{"index":4,"name":"WVISC","description":"WVISC is a real number defining the water viscosity (µw) at the water reference pressure.","units":{"field":"cP 0.50","metric":"cP 0.50","laboratory":"cP 0.50"},"default":"Defined","value_type":"DOUBLE","dimension":"Viscosity"},{"index":5,"name":"WVISCOMP","description":"WVISCOMP is a real number defining the water viscosibility (µwc) at the water reference pressure, µwc(Pref) and is defined as: [%mu sub{wc}~=~ - 1 over { %mu sub{w}}left({d%mu sub{w}} over{dP} right)]","units":{"field":"1/psia 0.0","metric":"1/barsa 0.0","laboratory":"1/atma 0.0"},"default":"Defined","value_type":"DOUBLE","dimension":"1/Pressure"}],"example":"The following shows the PVTW keyword for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set to one.\n--\n-- WATER PVT TABLE\n--\nPVTW\n-- REF PRES BW CW VISC VISC\n-- PSIA RB/STB 1/PSIA CPOISE GRAD\n-- -------- -------- ------- ------ ------\n4840.0 1.019 2.7E-6 0.370 1* / TABLE NO. 01\nThe next example shows the PVTW keyword for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set to three.\n--\n-- WATER PVT TABLE\n--\nPVTW\n-- REF PRES BW CW VISC VISC\n-- PSIA RB/STB 1/PSIA CPOISE GRAD\n-- -------- -------- ------- ------ ------\n4640.0 1.008 2.5E-6 0.350 1* / TABLE NO. 01\n4840.0 1.019 2.7E-6 0.370 1* / TABLE NO. 02\n4940.0 1.030 2.8E-6 0.390 1* / TABLE NO. 03\nThe above example defines three water PVT tables and assumes that NTPVT equals three on the TABDIMS keyword in the RUNSPEC section.\nThe third, and final example, shows the PVTW keyword for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set to four. Here table two defaults to table one, and table four defaults to table three\n--\n-- WATER PVT TABLE\n--\nPVTW\n-- REF PRES BW CW VISC VISC\n-- PSIA RB/STB 1/PSIA CPOISE GRAD\n-- -------- -------- ------- ------ ------\n4640.0 1.008 2.5E-6 0.350 1* / TABLE NO. 01\n/ TABLE NO. 02\n4940.0 1.030 2.8E-6 0.390 1* / TABLE NO. 03\n/ TABLE NO. 04\nNote that there is no terminating “/” for this keyword.","expected_columns":5,"size_kind":"fixed"},"PVTWSALT":{"name":"PVTWSALT","sections":["PROPS"],"supported":null,"summary":"PVTWSALT defines the brine water properties for various regions in the model, for when the brine phase has been activated by the BRINE keyword in the RUNSPEC section. In this case PVTWSALT is used instead of PVTW in the input file. However, if the ECLMC keyword has been entered in the RUNSPEC section to invoke the Multi-Component Brine model, the PVTW keyword should be used instead of PVTWSALT, as with this combination the salinity effect on the density is ignored.","parameters":[{"index":1,"name":"PRESS","description":"Single real positive value that defines the reference pressure for the data in the following records (Pref). PRESS should be approximately equal to the average reservoir pressures in the model. The simulator uses the previous time step values to forecast the current time step water properties by linear interpolation. If PRESS is not representative of the average reservoir pressures in the model then the linear interpolation might result in nonphysical values of the water saturation and water viscosity.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","record":1},{"index":1,"name":"","description":"","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"","record":1},{"index":1,"name":"SALTCON","description":"A columnar vector of real monotonically increasing values that defines the salt concentration in the solution (Cs).","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None","record":2},{"index":1,"name":"","description":"","units":{"field":"rb/stb","metric":"rm3/sm3","laboratory":"rcc/scc"},"default":"","record":2},{"index":3,"name":"WCOMP","description":"WCOMP is a real columnar vector defining the water compressibility (Cw) at the water reference pressure PRESS, for the corresponding salt concentration SALTCON. The water compressibility is defined as: [C sub{w}~=~ - 1 over {B sub{w}}left({dB sub{w}} over{dP} right)]","units":{"field":"1/psia","metric":"1/bars","laboratory":"1/atma"},"default":"None","record":2}],"example":"The following shows the PVTWSALT keyword for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set equal to two and NPPVT is set to greater than four on the TABDIMS keyword.\n--\n-- WATER SALT PVT TABLE\n--\nPVTWSALT\n-- REF PRES REF SALT\n-- PSIA LB/STB\n-- -------- --------\n4500.0 0.000 / TABLE NO. REF. DATA\n--\n-- SALTCONBW CW VISC VISC\n-- LB/STB RB/STB 1/PSIA CPOISE GRAD\n-- -------- -------- ------- ------ ------\n0.0 1.020 2.7E-6 0.370 0.0\n2.0 1.010 2.7E-6 0.370 0.0\n4.0 1.000 2.7E-6 0.370 0.0\n10.0 0.950 2.7E-6 0.370 0.0 / TABLE NO. 01 SALT DATA\n--\n-- REF PRES REF SALT\n-- PSIA LB/STB\n-- -------- --------\n4000.0 0.000 / TABLE NO. 02 REF. DATA\n--\n-- SALTCON BW CW VISC VISC\n-- LB/STB RB/STB 1/PSIA CPOISE GRAD\n-- -------- -------- ------- ------ ------\n0.0 1.005 2.5E-6 0.320 0.0\n3.0 1.000 2.5E-6 0.320 0.0\n6.0 0.985 2.5E-6 0.320 0.0\n12.0 0.930 2.5E-6 0.320 0.0 / TABLE NO. 02 SALT DATA\nNote that each table is terminated by a “/” and there is no “/” terminator for the keyword.\n| 1-1 |\n|-----|\n| 2-1 |\n|-----|\n| [{ B _ w ( { P , C _ s } ) `` = `` { { B _ w ( { P _ ref , C _ {s, ref} } ) } over { 1 ` + ` C _ w ( P - P _ ref ) ` + ` { left ( { C _ w ( P - P _ ref ) } right ) ^ 2 over 2 } } } }] | (8.82) |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|\n| [{ B _ w ( { P , C _ s } ) `` %mu _ w ( { P , C _ s } ) `` = `` { { B _ w ( { P _ ref , C _ {s, ref} } ) `` %mu _ w ( { P_ref , C _ {s, ref} } ) } over { 1 ` + ` ( { C _w - `` %mu _ wc } ) ( P - P _ ref ) ` + ` { left ( { ( C _ w - ``%mu _ wc ) ( P - P _ ref ) } right ) ^ 2 over 2 } } } }] | (8.83) |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|","size_kind":"fixed"},"PVZG":{"name":"PVZG","sections":["PROPS"],"supported":false,"summary":"PVZG defines the gas PVT properties for dry gas224\n Natural gas that occurs in the absence of condensate or liquid hydrocarbons, or gas that had condensable hydrocarbons removed, is called dry gas. It is primarily methane with some intermediates. The hydrocarbon mixture is solely gas in the reservoir and there is no liquid (condensate surface liquid) formed either in the reservoir or at surface. The term dry indicates that the gas does not contain heavier hydrocarbons to form liquids at the surface conditions. Dry gas typically has GOR's greater than 100,000 scf/stb or 18,000 Sm3/m3. via the gas compressibility factor (z-factor), instead of the gas formation volume factor. If the gas has a constant and uniform vaporized oil concentration, Condensate-Gas Ratio (“CGR”), and if the reservoir pressure never drops below the saturation pressure (dew point pressure), then the model can be run more efficiently by omitting the OIL and VAPOIL keywords from the RUNSPEC section, treating t...","parameters":[{"index":1,"name":"RTEMP","description":"Single real positive value that defines the reservoir temperature for the data in the following records.","units":{"field":"oF","metric":"oC","laboratory":"oC"},"default":"","record":1},{"index":1,"name":"PRESS","description":"A columnar vector of real monotonically increasing down the column values that defines the gas phase pressure.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","record":2},{"index":1,"name":"","description":"","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"","record":2},{"index":3,"name":"GVISC","description":"A columnar vector of real increasing down the column values that defines the corresponding gas phase viscosity.","units":{"field":"cP","metric":"cP","laboratory":"cP"},"default":"None","record":2}],"example":"---\n-- GAS PVT TABLE USING GAS Z-FACTOR\n--\nPVZG\n-- RESERVOIR TEMPERATURE FOR Z TO BG CONVERSION\n--\n180.0 /\n--\n-- PRES ZG VISC\n-- PSIA DIMLESS CPOISE\n-- ------ --------- -------\n14.7 0.998970 0.0130\n250.0 0.976260 0.0131\n500.0 0.954790 0.0134\n750.0 0.932050 0.0137\n1000.0 0.912990 0.0142\n1250.0 0.896320 0.0147\n1500.0 0.881610 0.0152\n1750.0 0.870830 0.0159\n2000.0 0.863130 0.0166\n2250.0 0.858920 0.0173\n2500.0 0.857800 0.0181\n2750.0 0.860430 0.0189\n3000.0 0.866440 0.0197\n3250.0 0.874980 0.0206\n3500.0 0.885470 0.0214\n3750.0 0.898350 0.0223\n4000.0 1.025120 0.0277 / TABLE NO 01 --\n-- GAS PVT TABLE USING GAS Z-FACTOR\n--\nPVZG\n-- RESERVOIR TEMPERATURE FOR Z TO BG CONVERSION\n--\n180.0 /\n--\n-- PRES ZG VISC\n-- PSIA DIMLESS CPOISE\n-- ------ --------- -------\n14.7 0.998970 0.0130\n250.0 0.976260 0.0131\n500.0 0.954790 0.0134\n750.0 0.932050 0.0137\n1000.0 0.912990 0.0142\n1250.0 0.896320 0.0147\n1500.0 0.881610 0.0152\n1750.0 0.870830 0.0159\n2000.0 0.863130 0.0166\n2250.0 0.858920 0.0173\n2500.0 0.857800 0.0181\n2750.0 0.860430 0.0189\n3000.0 0.866440 0.0197\n3250.0 0.874980 0.0206\n3500.0 0.885470 0.0214\n3750.0 0.898350 0.0223\n4000.0 1.025120 0.0277 / TABLE NO 01\nThe above example defines two dry PVZG tables assuming NTPVT equals two and NPPVT is greater than or equal to 17 on the TABDIMS keyword in the RUNSPEC section. There is no terminating “/” for this keyword.\n| 2-1 |\n|-----|\n| [PV~=~ZnRT] | (8.84) |\n|-------------|--------|\n| [V SUB{sc}~=~{Z SUB{sc}nRT SUB{sc}} OVER{ P SUB{sc}}] | (8.85) |\n|-------------------------------------------------------|--------|\n| [V SUB{i}~=~{Z SUB{i}n RT SUB{i}} OVER {P SUB{i}}] | (8.86) |\n|----------------------------------------------------|--------|\n| [E~=~{{V SUB{sc}} OVER { V SUB{i}}}] | (8.87) |\n|---------------------------------------|--------|\n| [E~=~ LEFT (P SUB { i } OVER P SUB {sc } RIGHT)\n ` ` LEFT(T SUB {sc } OVER T SUB { i } RIGHT )\n ` ` LEFT (1 OVER Z SUB { i } RIGHT )] | (8.88) |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------|\n| [E~=~ LEFT (P SUB { i } OVER {101.325} RIGHT)\n ` ` LEFT({273.15 ~+~15 } OVER T SUB { i } RIGHT )\n ` ` LEFT (1 OVER Z SUB { i } RIGHT )~=~\n 2.84` ` LEFT (P SUB { i } OVER { Z SUB {i } T SUB { i } } RIGHT )] | (8.89) |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|\n| [E~=~ LEFT (P SUB { i } OVER {14.7} RIGHT)\n ` ` LEFT({460 ~+~60 } OVER T SUB { i } RIGHT )\n ` ` LEFT (1 OVER Z SUB { i } RIGHT )~=~\n 35.37` ` LEFT (P SUB { i } OVER { Z SUB {i } T SUB { i } } RIGHT )] | (8.90) |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|","size_kind":"fixed"},"QHRATING":{"name":"QHRATING","sections":["PROPS"],"supported":false,"summary":"The QHRATING keyword defines a river’s mass flow rate versus depth tables, for when the River option has been activated via the RIVRDIMS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Length*Length*Length/Time","Length"]}],"example":"","size_kind":"fixed","variadic_record":true},"RIVRXSEC":{"name":"RIVRXSEC","sections":["PROPS"],"supported":false,"summary":"The RIVRXSEC keyword defines a river’s cross-sectional area and perimeter versus depth parameters. The River option must be activated via the RIVRDIMS keyword in the RUNSPEC section in order to use this keyword.","parameters":[{"index":1,"name":"DEPTH","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":2,"name":"WET_PERIMTER","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":3,"name":"AREA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length*Length"}],"example":"","expected_columns":3,"size_kind":"fixed"},"RKTRMDIR":{"name":"RKTRMDIR","sections":["PROPS"],"supported":false,"summary":"This keyword activates the directional transmissibility multipliers for the ROCKTAB keyword. This results in two additional columns being inputted on the ROCKTAB keyword. This feature is currently not supported in OPM Flow.","parameters":[],"example":"","size_kind":"none","size_count":0},"ROCK":{"name":"ROCK","sections":["PROPS"],"supported":null,"summary":"ROCK defines the rock compressibility for various regions in the model. The number of ROCK vector data sets is defined by the NTPVT parameter on the TABDIMS keyword in the RUNSPEC section and the allocation of the ROCK tables to different grid blocks in the model is done via the PVTNUM keyword in the REGIONS section. One data set consists of one record or line which is terminated by a “/”.","parameters":[{"index":1,"name":"PRESS","description":"PRESS is a real number defining the rock reference pressure for the other parameters for this data set.","units":{"field":"psia 14.7","metric":"barsa 1.0132","laboratory":"atma 1.0"},"default":"Default"},{"index":2,"name":"RCOMP","description":"RCOMP is a real number defining the rock compressibility (cf) at the rock reference pressure and is defined as: [c sub{f}~=~ - 1 over {V}left({dV} over{dP} right)]","units":{"field":"1/psia 0.0","metric":"1/barsa 0.0","laboratory":"1/atma 0.0"},"default":"Defined"}],"example":"The following shows the ROCK keyword for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set to one.\n--\n-- ROCK COMPRESSIBILITY\n--\n-- REFERENCE PRESSURE IS TAKEN FROM THE HCPV WEIGHTED RESERVOIR PRESSURE\n-- AS THE PORV IS ALREADY AT RESERVOIR CONDITIONS (OPM FLOW USES THE\n-- REFERENCE PRESSURE) TO CONVERT THE GIVEN PORV TO RESERVOIR CONDITIONS\n-- USING THE DATA ON THE ROCK KEYWORD)\n--\n-- REF PRES CF\n-- PSIA 1/PSIA\n-- -------- --------\nROCK\n3966.9 5.0E-06 / ROCK COMPRESSIBILITY\nThe next example shows the ROCK keyword for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set to three.\n--\n-- ROCK COMPRESSIBILITY\n--\n-- REFERENCE PRESSURE IS TAKEN FROM THE HCPV WEIGHTED RESERVOIR PRESSURE\n-- AS THE PORV IS ALREADY AT RESERVOIR CONDITIONS (OPM FLOW USES THE\n-- REFERENCE PRESSURE) TO CONVERT THE GIVEN PORV TO RESERVOIR CONDITIONS\n-- USING THE DATA ON THE ROCK KEYWORD)\n--\n-- REF PRES CF\n-- PSIA 1/PSIA\n-- -------- --------\nROCK\n3566.9 5.0E-06 / ROCK COMPRESSIBILITY REGION 1\n3966.9 5.5E-06 / ROCK COMPRESSIBILITY REGION 2\n4566.9 6.0E-06 / ROCK COMPRESSIBILITY REGION 3\nThe above example defines three ROCK tables and assumes that NTPVT equals three on the TABDIMS keyword in the RUNSPEC section.\nThere is no terminating “/” for this keyword, and thus the number entries must match the value entered via the TABDIMS(NTPVT), TABDIMS(NTROCC), or TABDIMS(NTSFUN) parameters, depending on the option selected via the ROCKOPTS keyword.\n| [V(P_i)``=``V(P_r) left( 1``+``c_f left( P_i`-`P_r right) ``+`` \n{ left( c_f ( P_i`-`P_r ) right) ^2} over 2 right)] | (8.91) |\n|------------------------------------------------------------------------------------------------------------------------|--------|\n| Note If the Rock Compaction option has been activated via the ROCKCOMP keyword in the RUNSPEC section, then the ROCKTAB keyword in the PROPS section should be used instead of ROCK keyword. |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|"},"ROCK2D":{"name":"ROCK2D","sections":["PROPS"],"supported":null,"summary":"The ROCK2D keyword defines rock compressibility pore volume multipliers as a function of pressure and water saturation (“Sw”) for when the rock compaction option has been invoked by the ROCKCOMP keyword in the RUNSPEC section. The pressure values are defined on this keyword and the water saturations are declared on the associated ROCKWNOD keyword in the PROPS section","parameters":[{"index":1,"name":"PRESS","description":"A columnar vector of real monotonically increasing down the column values that defines the corresponding overburden pressure for the subsequent MULT columnar vector.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"None","value_type":"DOUBLE","dimension":"Pressure"},{"index":2,"name":"MULT","description":"A columnar vector of real equal or decreasing down the column values that are less than or equal to one, that defines the rock compressibility pore volume multipliers corresponding to PRESS and for each water saturation entry in the ROCKWNOD keyword.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":"1"}],"example":"The following example defines two pore volume compaction tables, assuming NTROCC is equal to two on the ROCKCOMP keyword and NSSFUN is greater than or equal to four on the TABDIMS keyword.\n--\n-- ROCK COMPACTION VERSUS PRESSURE AND SW TABLES\n--\nROCK2D\n-- PRESS PORV FIRST ROCK2D TABLE DATA\n-- PSIA MULTIPLER\n-- ------ ----------\n0.0 0.850\n0.850\n0.850\n0.085 / P-SW SET TABLE NO. 01\n-- PRESS PORV\n-- PSIA MULTIPLER\n-- ------ ----------\n1000.0 0.900\n0.900\n0.900\n0.900 / P-SW SET TABLE NO. 01\n-- PRESS PORV\n-- PSIA MULTIPLER\n-- ------ ----------\n2500.0 0.950\n0.950\n0.950\n0.950 / P-SW SET TABLE NO. 01\n-- PRESS PORV\n-- PSIA MULTIPLER\n-- ------ ----------\n5000.0 1.000\n1.000\n1.000\n1.000 / P-SW SET TABLE NO. 01\n--\n-- PRESS PORV SECOND ROCK2D TABLE DATA\n-- PSIA MULTIPLER\n-- ------ ----------\n0.0 0.800\n0.800\n0.800\n0.800 / P-SW SET TABLE NO. 02\n-- PRESS PORV\n-- PSIA MULTIPLER\n-- ------ ----------\n1000.0 0.880\n0.880\n0.880\n0.880 / P-SW SET TABLE NO. 02\n-- PRESS PORV\n-- PSIA MULTIPLER\n-- ------ ----------\n2500.0 0.950\n0.950\n0.950\n0.950 / P-SW SET TABLE NO. 02\n-- PRESS PORV\n-- PSIA MULTIPLER\n-- ------ ----------\n5000.0 1.000\n1.000\n1.000\n1.000 / P-SW SET TABLE NO. 02\nNote that there must be exactly NTROCC tables entered for this keyword, otherwise an error will occur.","size_kind":"list","variadic_record":true},"ROCK2DTR":{"name":"ROCK2DTR","sections":["PROPS"],"supported":null,"summary":"The ROCK2DTR keyword defines rock compressibility transmissibility multipliers as a function of pressure and water saturation (“Sw”) for when the rock compaction option has been invoked by the ROCKCOMP keyword in the RUNSPEC section. The pressure values are defined on this keyword and the water saturations are declared on the associated ROCKWNOD keyword in the PROPS section","parameters":[{"index":1,"name":"PRESS","description":"A columnar vector of real monotonically increasing down the column values that defines the corresponding overburden pressure for the subsequent MULT columnar vector.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"None","value_type":"DOUBLE","dimension":"Pressure"},{"index":2,"name":"MULT","description":"A columnar vector of real equal or decreasing down the column values that are less than or equal to one, that defines the rock compressibility transmissibility multipliers corresponding to PRESS and for each water saturation entry in the ROCKWNOD keyword.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":"1"}],"example":"The following example defines two rock compressibility transmissibility compaction tables, assuming NTROCC is equal to two on the ROCKCOMP keyword and NSSFUN is greater than or equal to four on the TABDIMS keyword.\n--\n-- TRANSMISSIBILITY COMPACTION VERSUS PRESSURE AND SW TABLES\n--\nROCK2DTR\n-- PRESS TRAN FIRST ROCK2DTR TABLE DATA\n-- PSIA MULTIPLER\n-- ------ ----------\n0.0 0.850\n0.850\n0.850\n0.085 / P-SW SET TABLE NO. 01\n-- PRESS TRAN\n-- PSIA MULTIPLER\n-- ------ ----------\n1000.0 0.900\n0.900\n0.900\n0.900 / P-SW SET TABLE NO. 01\n-- PRESS TRAN\n-- PSIA MULTIPLER\n-- ------ ----------\n2500.0 0.950\n0.950\n0.950\n0.950 / P-SW SET TABLE NO. 01\n-- PRESS TRAN\n-- PSIA MULTIPLER\n-- ------ ----------\n5000.0 1.000\n1.000\n1.000\n1.000 / P-SW SET TABLE NO. 01\n--\n-- PRESS TRAN SECOND ROCK2DTR TABLE DATA\n-- PSIA MULTIPLER\n-- ------ ----------\n0.0 0.800\n0.800\n0.800\n0.800 / P-SW SET TABLE NO. 02\n-- PRESS TRAN\n-- PSIA MULTIPLER\n-- ------ ----------\n1000.0 0.880\n0.880\n0.880\n0.880 / P-SW SET TABLE NO. 02\n-- PRESS TRAN\n-- PSIA MULTIPLER\n-- ------ ----------\n2500.0 0.950\n0.950\n0.950\n0.950 / P-SW SET TABLE NO. 02\n-- PRESS TRAN\n-- PSIA MULTIPLER\n-- ------ ----------\n5000.0 1.000\n1.000\n1.000\n1.000 / P-SW SET TABLE NO. 02\nNote that there must be exactly NTROCC tables entered for this keyword, otherwise an error will occur.","size_kind":"list","variadic_record":true},"ROCKOPTS":{"name":"ROCKOPTS","sections":["PROPS"],"supported":true,"summary":"The ROCKOPTS keyword defines various options with respect to rock compaction and rock compressibility.","parameters":[{"index":1,"name":"ROCKOPT1","description":"A defined character string that specifies how the overburden pressures supplied by the OVERBURD keyword are applied to the tabulated pressures in the ROCKTAB keywords: STRESS: Use this option if the overburden pressures on the OVERBURD keyword are greater than the fluid pressure which results in the effective fluid pressure being negative. To avoid the rock compaction tables being entered with negative pressure values use this option. In this case the pore volume and transmissibility multipliers will be tabulated against the effective overburden pressure. PRESSURE: In this case the pore volume and transmissibility multipliers should be tabulated against the effective fluid pressure. This the default value. ROCKOPT1 should be set to PRESSURE if the OVERBURD is not used in the input deck. Only the default value of PRESSURE is supported.","units":{},"default":"PRESSURE","value_type":"STRING"},{"index":2,"name":"ROCKOPT2","description":"A defined character string that sets the reference pressure option: STORE: Copies the initial calculated grid block pressures into the overburden pressure array, resulting in the pore volumes being referenced at the initial pressures instead of the reference pressures as per the ROCKTAB keyword. NOSTORE: This option results in the pore volumes being referenced as per the ROCKTAB keyword. This is the default value. Note that STORE option should not be used with the OVERBURD keywords as the OVERBURD data will be overwritten.","units":{},"default":"NOSTORE","value_type":"STRING"},{"index":3,"name":"ROCKOPT3","description":"A defined character string that specifies which region array should be used to allocate the various ROCK and ROCKTAB property tables in the model: ROCKOPT3, should be set to ROCKNUM, SATNUM or PVTNUM. If the parameter is defaulted or the ROCKOPT keyword is not present in the deck, then the PVTNUM array is used. Secondly, if ROCKOPT3 is set to ROCKNUM but the NTROCC parameter on the TABDIMS keyword in the RUNSPEC section is defaulted, then again the PVTNUM array will be utilized. Only the PVTNUM and ROCKNUM options are currently supported.","units":{},"default":"PVTNUM","value_type":"STRING"},{"index":4,"name":"ROCKOPT4","description":"A defined character string that sets the initial conditions for the HYSTER and BOBERG options: DEFLATION: This option defines the reservoir rock to be fully compacted and the deflation curve is used to calculated the initial pore volume and transmissibility multipliers. This is the default value. ELASTIC: This option sets the pore volume and transmissibility multipliers to one, as the reservoir rock is set to lie on the elastic curve. This parameter is ignored by OPM Flow as the ROCKCOMP(ROCKOPT) options of HYSTER and BOBERG are not supported by the simulator.","units":{},"default":"DEFLATION","value_type":"STRING"}],"example":"--\n-- ROCKOPT1 ROCKOPT2 ROCKOPT3 ROCKOPT4\n-- PRS/STRE NO/STORE ARRAY\n-- -------- -------- -------- --------\nROCKOPTS\nPRESSURE NOSTORE PVTNUM / ROCK COMP OPTIONS\nThe above example defines the default values for the ROCKOPTS keyword.","expected_columns":4,"size_kind":"fixed","size_count":1},"ROCKPAMA":{"name":"ROCKPAMA","sections":["PROPS"],"supported":false,"summary":"ROCKPAMA defines the Palmer-Mansoori226\n Palmer, I. and Mansoori, J. “How Permeability Depends on Stress and Pore Pressure in Coalbeds: A New Model,” paper SPE 52607, SPE Reservoir Evaluation & Engineering (1998) 1, No. 6, 539-544. and 227\n Clarkson, C.R., Pan, Z., Palmer, I. and Harpalani, S. \"Predicting Sorption-Induced Strain and Permeability Increase With Depletion for Coalbed-Methane Reservoirs\", SPE 114778-PA, SPE Journal (2010) 15, No. 1, 152–159.parameters used for this rock model, for when the Coal Bed Methane option has been activated via the COAL keyword, and PALM-MAN has been declared for the ROCKOPT variable on the ROCKCOMP keyword; both keywords are in the RUNSPEC section. The Palmer-Mansoori rock model is used to calculate the impact on pore volume and permeability due to rock compaction.","parameters":[{"index":1,"name":"K","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":2,"name":"M","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":3,"name":"G","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":4,"name":"B","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":5,"name":"E1","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":6,"name":"f","description":"","units":{},"default":"0.5","value_type":"DOUBLE"},{"index":7,"name":"n","description":"","units":{},"default":"3","value_type":"DOUBLE"},{"index":8,"name":"g","description":"","units":{},"default":"1","value_type":"DOUBLE"},{"index":9,"name":"Bs","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":10,"name":"Es","description":"","units":{},"default":"0","value_type":"DOUBLE"}],"example":"","expected_columns":10,"size_kind":"fixed"},"ROCKTAB":{"name":"ROCKTAB","sections":["PROPS"],"supported":null,"summary":"The ROCKTAB keyword defines the rock compaction attributes to be applied when the rock compaction option has been invoked by the ROCKCOMP keyword in the RUNSPEC section. ROCKTAB defines pore volume and transmissibility multipliers versus pressure that are used in the compaction calculations. If the RKTRMDIR has been activated in the PROPS section, then the transmissibility multiplier is directional dependent and two additional columns are used to define the y and z direction transmissibility multipliers.","parameters":[{"index":1,"name":"PRESS","description":"If the ROCKOPT1 variable has been set to PRESSURE on the ROCKOPTS keyword in the PROPS section, then PRESS should be a columnar vector of real monotonically increasing down the column values, that define the reference pressure for which the other parameters correspond to. If ROCKOPT1 has been set to STRESS, then PRESS should be a columnar vector of real monotonically decreasing down the column values.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"None","value_type":"DOUBLE","dimension":["Pressure","1","1"]},{"index":2,"name":"PORV","description":"A columnar vector of real positive values that are either equal or increasing down the column that define the rock pore volume multiplier for a given PRESS.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":3,"name":"TRANS","description":"If the RKTRMDIR is absent from the input deck, then TRANS is a columnar vector of real positive values that are either equal or increasing down the column that define the x, y, and z directional transmissibility multipliers for the corresponding PRESS. If the RKTRMDIR is present in the input deck, then TRANS is a columnar vector of real positive values that are either equal or increasing down the column that define only the x directional transmissibility multipliers for the corresponding PRESS.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":4,"name":"TRANSY","description":"If the RKTRMDIR is absent from the input deck, then TRANSY is ignored. If the RKTRMDIR is present in the input deck, then TRANSY is a columnar vector of real positive values that are either equal or increasing down the column that define only the y directional transmissibility multipliers for the corresponding PRESS.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":5,"name":"TRANSZ","description":"If the RKTRMDIR is absent from the input deck, then TRANSZ is ignored. If the RKTRMDIR is present in the input deck, then TRANSZ is a columnar vector of real positive values that are either equal or increasing down the column that define only the z directional transmissibility multipliers for the corresponding PRESS.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"The example below defines two rock compaction tables, assuming NTROCC is equal to two on the ROCKCOMP keyword and NPPVT is greater than or equal to five on the TABDIMS keyword and that the RKTRMDIR keyword is present in the input deck.\n--\n-- ROCK COMPACTION TABLES\n--\nROCKTAB\n-- PRESS PORV TX(YZ) TY TZ\n-- MULT MULT MULT MULT\n-- ------ ------ ------ ------ ------\n1000.0 0.9600 0.9650 0.9650 0.9650\n1500.0 0.9800 0.9850 0.9850 0.9500\n3000.0 0.9900 0.9950 0.9950 0.9950\n4500.0 1.0000 1.0000 1.0000 1.0000\n4750.0 1.0100 1.0100 1.0100 1.0100 / TABLE NO. 01\n-- PRESS PORV TX(YZ) TY TZ\n-- MULT MULT MULT MULT\n-- ------ ------ ------ ------ ------\n1000.0 0.9600 0.9650 0.9650 0.9650\n1500.0 0.9800 0.9850 0.9850 0.9500\n3000.0 0.9900 0.9950 0.9950 0.9950\n4500.0 1.0000 1.0000 1.0000 1.0000\n4750.0 1.0100 1.0100 1.0100 1.0100 / TABLE NO. 02\nAs the x, y and z directional transmissibility multipliers are identical in the above example, we could eliminate the RKTRMDIR keyword from the input deck and enter the data in the three column format, as shown on the next page.\n--\n-- ROCK COMPACTION TABLES\n--\nROCKTAB\n-- PRESS PORV TX(YZ)\n-- MULT MULT\n-- ------ ------ ------\n1000.0 0.9600 0.9650\n1500.0 0.9800 0.9850\n3000.0 0.9900 0.9950\n4500.0 1.0000 1.0000\n4750.0 1.0100 1.0100 / TABLE NO. 01\n-- PRESS PORV TX(YZ)\n-- MULT MULT\n-- ------ ------ ------\n1000.0 0.9600 0.9650\n1500.0 0.9800 0.9850\n3000.0 0.9900 0.9950\n4500.0 1.0000 1.0000\n4750.0 1.0100 1.0100 / TABLE NO. 02\nThe net result of the two examples in this case is identical.","size_kind":"fixed","variadic_record":true},"ROCKTABH":{"name":"ROCKTABH","sections":["PROPS"],"supported":false,"summary":"The ROCKTABH keyword defines the rock compaction hysteresis attributes to be applied for when the rock compaction option has been invoked by the ROCKCOMP keyword in the RUNSPEC section. ROCKTABH defines pore volume and transmissibility multipliers versus pressure that are used in the compaction calculations. If the RKTRMDIR has been activated in the PROPS section, then the transmissibility multiplier is directional dependent and two additional columns are used to define the y and z direction transmissibility multipliers. The keyword should only be used if the Rock Compaction Hysteresis option has been activated by either setting the ROCKOPT parameter on the ROCKCOMP keyword to HYSTER or BOBERG.","parameters":[{"index":1,"name":"PRESS","description":"If the ROCKOPT1 variable has been set to PRESSURE on the ROCKOPTS keyword in the PROPS section, then PRESS should be a columnar vector of real monotonically increasing down the column values, that define the reference pressure for which the other parameters correspond to. If ROCKOPT1 has been set to STRESS, then PRESS should be a columnar vector of real monotonically decreasing down the column values.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"None","value_type":"DOUBLE"},{"index":2,"name":"PORV","description":"A columnar vector of real positive values that are either equal or increasing down the column that define the rock pore volume multiplier for a given PRESS.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":3,"name":"TRANS","description":"If the RKTRMDIR is absent from the input deck, then TRANS is a columnar vector of real positive values that are either equal or increasing down the column that define the x, y, and z directional transmissibility multipliers for the corresponding PRESS. If the RKTRMDIR is present in the input deck, then TRANS is a columnar vector of real positive values that are either equal or increasing down the column that define only the x directional transmissibility multipliers for the corresponding PRESS.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":4,"name":"TRANSY","description":"If the RKTRMDIR is absent from the input deck, then TRANSY is ignored. If the RKTRMDIR is present in the input deck, then TRANSY is a columnar vector of real positive values that are either equal or increasing down the column that define only the y directional transmissibility multipliers for the corresponding PRESS.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":5,"name":"TRANSZ","description":"If the RKTRMDIR is absent from the input deck, then TRANSZ is ignored. If the RKTRMDIR is present in the input deck, then TRANSZ is a columnar vector of real positive values that are either equal or increasing down the column that define only the z directional transmissibility multipliers for the corresponding PRESS.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"The example below defines two rock compaction tables, assuming NTROCC is equal to two on the ROCKCOMP keyword and NPPVT is greater than or equal to four on the TABDIMS keyword and that the RKTRMDIR keyword is not present in the input deck.\n--\n-- ROCK COMPACTION HYSTERESIS TABLES\n--\nROCKTABH\n-- PRESS PORV TX(YZ) TY TZ\n-- MULT MULT MULT MULT\n-- ------ ------ ------ ------ ------\n1500.0 0.9600 0.9800\n2500.0 0.9700 0.9850\n3500.0 0.9800 0.9900\n4500.0 0.9900 0.9950 / NPPVT = 1\n2500.0 0.9900 0.9900\n3500.0 0.9950 0.9950\n4750.0 0.9980 0.9980 / NPPVT = 2\n3500.0 1.0000 1.0000\n5500.0 1.0100 1.0100 / NPPVT = 3\n4500.0 1.0100 1.0100\n5750.0 1.0200 1.0200 / NPPVT = 4\n/ TABLE NO. 01 -- PRESS PORV TX(YZ) TY TZ\n-- MULT MULT MULT MULT\n-- ------ ------ ------ ------ ------\n1500.0 0.9400 0.9700\n2750.0 0.9400 0.9700 / NPPVT = 1\n2250.0 0.9800 0.9900\n3250.0 0.9800 0.9900 / NPPVT = 2\n3000.0 1.0000 1.0000\n4250.0 1.0000 1.0000 / NPPVT = 3\n4550.0 1.0200 1.0100\n5750.0 1.0200 1.0100 / NPPVT = 4\n/ TABLE NO. 02\nHere the deflation curve is define for table number one is:\n1500.0 0.9600 0.9800\n2500.0 0.9900 0.9900\n3500.0 1.0000 1.0000\n4500.0 1.0100 1.0100\nand for table number 2:\n1500.0 0.9400 0.9700\n2250.0 0.9800 0.9900\n3250.0 1.0000 1.0000\n4250.0 1.0200 1.0100\nAnd the dilation curve is define for table number one is:\n4500.0 0.9900 0.9950\n4750.0 0.9980 0.9980\n5500.0 1.0100 1.0100\n5750.0 1.0200 1.0200\nand for table number 2:\n2250.0 0.9400 0.9700\n3250.0 0.9800 0.9900\n4250.0 1.0000 1.0000\n5250.0 1.0200 1.0100","size_kind":"fixed","variadic_record":true},"ROCKTABW":{"name":"ROCKTABW","sections":["PROPS"],"supported":false,"summary":"The ROCKTABW keyword defines the rock compaction tables induced by increasing water saturation within a grid cell due to water invasion, for when the rock compaction option has been invoked by the ROCKCOMP keyword in the RUNSPEC section. ROCKTABW defines pore volume and transmissibility multipliers versus water saturation that are used in the compaction calculations. The keyword should be used together with the ROCK, ROCKTAB or ROCKTABH keywords that specify the pore volume and transmissibility multipliers as functions of pressure. Alternatively the ROCKWNOD, ROCK2D and ROCK2DTR keywords can be used to enter two dimensional tables of the data. All keywords are in the PROPS section.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","size_kind":"fixed","variadic_record":true},"ROCKTHSG":{"name":"ROCKTHSG","sections":["PROPS"],"supported":false,"summary":"The ROCKTHSG keyword defines the rock compaction hysteresis attributes to be applied for when the rock compaction option has been invoked by the ROCKCOMP keyword in the RUNSPEC section and the either the Dual Permeability or Dual Porosity models are activated by the DUALPERM and DUALPORO keywords in the RUNSPEC section. ROCKTHSG specifies sigma multipliers versus pressure that are used in the dual porosity rock compaction calculations. The keyword should only be used if the Rock Compaction Hysteresis option has been activated by either setting the ROCKOPT parameter on the ROCKCOMP keyword to one of the available options.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Pressure","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"ROCKTSIG":{"name":"ROCKTSIG","sections":["PROPS"],"supported":false,"summary":"The ROCKTSIG keyword defines the rock compaction attributes to be applied for when the rock compaction option has been invoked by the ROCKCOMP keyword in the RUNSPEC section, and the either the Dual Permeability or Dual Porosity models are activated by the DUALPERM and DUALPORO keywords in the RUNSPEC section. ROCKTSIG specifies sigma multipliers versus pressure that are used in the dual porosity rock compaction calculations. The keyword should only be used if the Rock Compaction Hysteresis option has been activated by either setting the ROCKOPT parameter on the ROCKCOMP keyword to one of the available options.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Pressure","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"ROCKWNOD":{"name":"ROCKWNOD","sections":["PROPS"],"supported":null,"summary":"The ROCK2D and the ROCK2DTR keywords in the PROPS section define rock compressibility pore volume and transmissibility multipliers as a function of pressure and water saturation (“Sw”), for when the rock compaction option has been invoked by the ROCKCOMP keyword in the RUNSPEC section. The pressure values are defined on ROCK2D and the ROCK2DTR keywords together with the multipliers. This keyword ROCKWNOD, defines the water saturations that are used in conjunction with the ROCK2D and the ROCK2DTR keywords.","parameters":[{"index":1,"name":"SWAT","description":"A columnar vector of real monotonically increasing down the column values that defines the water saturations to be associated with the data on the ROCK2D and the ROCKTR keywords.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":"1"}],"example":"The following example defines two ROCKWNOD tables for the pore volume and transmissibility compaction tables, assuming NTROCC is equal to two on the ROCKCOMP keyword and NSSFUN is greater than or equal to four on the TABDIMS keyword.\n--\n-- WATER SATURATION VALUES FOR COMPACTION PRESSURE-SW TABLES\n--\nROCKWNOD\n-- COMPACT\n-- SWAT\n-- ------\n0.000\n0.200\n0.400\n1.000 / P-SW SET TABLE NO. 01\n-- COMPACT\n-- SWAT\n-- ------\n0.000\n0.250\n0.750\n1.000 / P-SW SET TABLE NO. 02\nNote that there must be exactly NTROCC tables entered for this keyword, otherwise an error will occur.","size_kind":"fixed","variadic_record":true},"RPTPROPS":{"name":"RPTPROPS","sections":["PROPS"],"supported":false,"summary":"This keyword defines the data in the PROPS section that is to be printed to the output print file in human readable format. The keyword has two distinct forms, the first of which consists of the keyword followed by a series of integers on the next line indicating the data to be printed (see the first example). This is the original formal in the commercial simulator and was subsequently superseded by the second format. The second format consists of the keyword followed by a series of character strings that indicate the data to be printed. In most cases the character string is the keyword used to load the data in the OPM Flow input deck, for example PVDG for the dry gas PVT tables. Its is anticipated that OPM Flow will eventually support the functionality of the second format only, the first format although recognized will be completely ignored.","parameters":[{"index":1,"name":"PVDG","description":"Print dry gas PVT tables","units":{},"default":"N/A","value_type":"STRING"},{"index":2,"name":"PVTG","description":"Print wet gas PVT tables","units":{},"default":"N/A"},{"index":3,"name":"SGFN","description":"Print gas relative permeability saturation function tables.","units":{},"default":"N/A"},{"index":4,"name":"SGL","description":"Print connate gas saturation array.","units":{},"default":"N/A"}],"example":"The first example shows the original format of this keyword; although the keyword and format are recognized by OPM Flow, the format is ignored and is unlikely to be implemented in in the simulator.\n--\n-- DEFINE PROPS SECTION REPORT OPTION (ORIGINAL FORMAT)\n–\nRPTPROPS\n1 2*0 1 3*1 /\nThe next example shows the second format of the keyword which may be supported in a future release of OPM Flow.\n--\n-- DEFINE PROPS SECTION REPORT OPTIONS\n--\nRPTPROPS\nPVDO SOF2 SGFN SWFN /\n| Note Except for tabular like data, PVDG etc., this keyword has the potential to produce very large print files that some text editors may have difficulty loading. A more efficient solution for array type data is to load the *.INIT file into OPM ResInsight to view the data graphically, this also has the benefit of being able to filter the grid based on I, J, K ranges and grid properties. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"fixed","size_count":1,"variadic_record":true},"RSCONST":{"name":"RSCONST","sections":["PROPS"],"supported":false,"summary":"RSCONST defines a constant Gas-Oil Ratio (“GOR”), for all dead oil228\n “Dead” oil is oil that it contains no dissolved gas or a relatively thick oil or residue that has lost its volatile components. PVT fluids. If the oil has a constant and uniform dissolved gas concentration, GOR, and if the reservoir pressure never drops below the saturation pressure (bubble point pressure), then the model can be run more efficiently by omitting the GAS and DISGAS keywords from the RUNSPEC section, treating the oil as a dead oil, and defining a constant Rs (GOR) value with keywords RSCONST or RSCONSTT in the PROPS section. This results in the model being run as a dead oil problem with no active gas phase. However, OPM Flow takes into account the constant Rs in the calculations and reporting.","parameters":[{"index":1,"name":"RS","description":"A real positive value that defines the dead oil GOR for all oil PVT tables in the model","units":{"field":"Mscf/stb","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"None","value_type":"DOUBLE","dimension":"GasDissolutionFactor"},{"index":2,"name":"PRESS","description":"A real positive value that defines that saturation pressure (bubble point pressure) for all the oil PVT tables in the model.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":"Pressure"}],"example":"The example sets the dead oil GOR to 5 scf/stb and the bubble point pressure to 14.7 psia.\n--\n-- DEAD OIL PVT CONSTANT GOR AND SATURATION PRESSURE\n--\nRSCONST\n-- RS PSAT\n-- MSCF/STB PSIA\n-- -------- ------\n0.0050 14.7 /","expected_columns":2,"size_kind":"fixed","size_count":1},"RSCONSTT":{"name":"RSCONSTT","sections":["PROPS"],"supported":false,"summary":"RSCONSTT defines a constant Gas-Oil Ratio (“GOR”), for each dead oil229\n “Dead” oil is oil that it contains no dissolved gas or a relatively thick oil or residue that has lost its volatile components. PVT fluid in the model. If the oil has a constant and uniform dissolved gas concentration, GOR, and if the reservoir pressure never drops below the saturation pressure (bubble point pressure), then the model can be run more efficiently by omitting the GAS and DISGAS keywords from the RUNSPEC section, treating the oil as a dead oil, and defining a constant Rs (GOR) value with keywords RSCONST or RSCONSTT in the PROPS section. This results in the model being run as a dead oil problem with no active gas phase. However, OPM Flow takes into account the constant Rs in the calculations and reporting.","parameters":[{"index":1,"name":"RS","description":"A real positive columnar vector that defines the dead oil GOR for each oil PVT table in the model","units":{"field":"Mscf/stb","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"None","value_type":"DOUBLE","dimension":"GasDissolutionFactor"},{"index":2,"name":"PRESS","description":"A real positive columnar vector that defines the saturation pressure (bubble point pressure) for each the oil PVT table in the model.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":"Pressure"}],"example":"The example sets the dead oil GOR to 5, 6.5 and 8.0 scf/stb for PVT tables one, two and three, respectively and the bubble point pressure to 14.7 psia for all three tables.\n--\n-- DEAD OIL PVT CONSTANT GOR AND SATURATION PRESSURE\n--\nRSCONSTT\n-- RS PSAT\n-- MSCF/STB PSIA\n-- -------- ------\n0.0050 14.7 / TABLE NO. 01\n0.0065 14.7 / TABLE NO. 02\n0.0080 14.7 / TABLE NO. 03","expected_columns":2,"size_kind":"fixed"},"RSGI":{"name":"RSGI","sections":["PROPS"],"supported":false,"summary":"The RSGI keyword specifies the saturated oil Gas-Oil Ratio (“GOR”) factors used to specify the variation of the maximum possible GOR of oil with respect to pressure and Gi values, for when the GIMODEL keyword in the RUNSPEC section has been used to activate the GI Pseudo Compositional option for the run. See also the GINODE, RSGI, RVGI, BGGI and BOGI keywords in the PROPS section to describe the fluid properties for the GI Pseudo Compositional option.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Pressure","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"RTEMP":{"name":"RTEMP","sections":["PROPS","SOLUTION"],"supported":true,"summary":"This keyword defines the initial reservoir temperature for the model. Note that the RTEMP keyword is an alias for RTEMPA, and that both keywords are supported by OPM Flow, in both the PROPS and SOLUTION sections, but are treated as being mutually exclusive.","parameters":[{"index":1,"name":"RTEMP","description":"Single real positive value that defines the reservoir temperature for the model.","units":{"field":"oF","metric":"oC","laboratory":"oC"},"default":"None","value_type":"DOUBLE","dimension":"Temperature"}],"example":"--\n-- RESERVOIR\n-- TEMPERATURE\n-- -----------\nRTEMP\n190.0 / RESERVOIR TEMPERATURE\nThe above example defines the reservoir temperature to be 190 oF.","expected_columns":1,"size_kind":"fixed","size_count":1},"RTEMPA":{"name":"RTEMPA","sections":["PROPS","SOLUTION"],"supported":true,"summary":"This keyword defines the initial reservoir temperature for the model. Note that the RTEMPA keyword is an alias for RTEMP, and that both keywords are supported by OPM Flow, in both the PROPS and SOLUTION sections, but are treated as being mutually exclusive.","parameters":[{"index":1,"name":"RTEMPA","description":"Single real positive value that define the reservoir temperature for the model.","units":{"field":"oF","metric":"oC","laboratory":"oC"},"default":"None","value_type":"DOUBLE","dimension":"Temperature"}],"example":"--\n-- RESERVOIR\n-- TEMPERATURE\n-- -----------\nRTEMPA\n190.0 / RESERVOIR TEMPERATURE\nThe above example defines the reservoir temperature to be 190 oF.","expected_columns":1,"size_kind":"fixed","size_count":1},"RTEMPVD":{"name":"RTEMPVD","sections":["PROPS","SOLUTION"],"supported":true,"summary":"This keyword defines the initial reservoir temperature versus depth tables for each equilibration region. Note that the RTEMPVD keyword is an alias for TEMPVD, and that both keywords are supported by OPM Flow, in both the PROPS and SOLUTION sections, but are treated as being mutually exclusive.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Length","Temperature"]}],"example":"","size_kind":"fixed","variadic_record":true},"RVCONST":{"name":"RVCONST","sections":["PROPS"],"supported":false,"summary":"RVCONST defines a constant Condensate-Gas Ratio (“CGR” or Rv), for all dry gas230\n Natural gas that occurs in the absence of condensate or liquid hydrocarbons, or gas that had condensable hydrocarbons removed, is called dry gas. It is primarily methane with some intermediates. The hydrocarbon mixture is solely gas in the reservoir and there is no liquid (condensate surface liquid) formed either in the reservoir or at surface. The term dry indicates that the gas does not contain heavier hydrocarbons to form liquids at the surface conditions. Dry gas typically has GOR's greater than 100,000 scf/stb or 18,000 Sm3/m3. PVT fluids. If the gas has a constant and uniform dissolved condensate concentration, and if the reservoir pressure never drops below the saturation pressure (dew point pressure), then the model can be run more efficiently by omitting the OIL and VAPOIL keywords from the RUNSPEC section, treating the gas as a dry gas, and defining a constant Rv (CGR) value with keywor...","parameters":[{"index":1,"name":"RV","description":"A real positive value that defines the dry gas CGR for all dry gas PVT tables in the model","units":{"field":"stb/Mscf","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"None","value_type":"DOUBLE","dimension":"OilDissolutionFactor"},{"index":2,"name":"PRESS","description":"A real positive value that defines that saturation pressure (dew point pressure) for all the dry gas PVT tables in the model.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"0.0","value_type":"DOUBLE","dimension":"Pressure"}],"example":"The example sets the dry gas CGR to 5 stb/MMscf and the bubble point pressure to 14.7 psia.\n--\n-- DRY GAS PVT CONSTANT GCR AND SATURATION PRESSURE\n--\nRVCONST\n-- RV PSAT\n-- STB/MSCF PSIA\n-- -------- ------\n0.0050 14.7 /","expected_columns":2,"size_kind":"fixed","size_count":1},"RVCONSTT":{"name":"RVCONSTT","sections":["PROPS"],"supported":null,"summary":"RVCONSTT defines a constant Condensate-Gas Ratio (“CGR” or Rv), for each dry gas231\n Natural gas that occurs in the absence of condensate or liquid hydrocarbons, or gas that had condensable hydrocarbons removed, is called dry gas. It is primarily methane with some intermediates. The hydrocarbon mixture is solely gas in the reservoir and there is no liquid (condensate surface liquid) formed either in the reservoir or at surface. The term dry indicates that the gas does not contain heavier hydrocarbons to form liquids at the surface conditions. Dry gas typically has GOR's greater than 100,000 scf/stb or 18,000 Sm3/m3. PVT fluid. If the gas has a constant and uniform dissolved condensate concentration, and if the reservoir pressure never drops below the saturation pressure (dew point pressure), then the model can be run more efficiently by omitting the OIL and VAPGAS keywords from the RUNSPEC section, treating the gas as a dry gas, and defining a constant Rv (CGR) value with keywo...","parameters":[{"index":1,"name":"RS","description":"A real positive value that defines the dry gas CGR for each dry gas PVT table in the model","units":{"field":"stb/Mscf","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"None","value_type":"DOUBLE","dimension":["OilDissolutionFactor","Pressure"]},{"index":2,"name":"PRESS","description":"A real positive value that defines that saturation pressure (dew point pressure) for each dry gas PVT table in the model.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"0.0"}],"example":"The example sets the dry gas CGR to 5, 6.5 and 8.0 stb/MMscf for PVT tables one, two and three, respectively and the bubble point pressure to 14.7 psia for all three tables.\n--\n-- DRY GAS PVT CONSTANT GCR AND SATURATION PRESSURE\n--\nRVCONSTT\n-- RV PSAT\n-- STB/MSCF PSIA\n-- -------- ------\n0.0050 14.7 / TABLE NO. 01\n0.0065 14.7 / TABLE NO. 02\n0.0080 14.7 / TABLE NO. 03","size_kind":"fixed","variadic_record":true},"RVGI":{"name":"RVGI","sections":["PROPS"],"supported":false,"summary":"The RVGI keyword specifies the saturated gas Condensate-Gas Ratio (“CGR”) factors used to specify the variation of the maximum possible CGR of gas with respect to pressure and Gi values, for when the GIMODEL keyword in the RUNSPEC section has been used to activate the GI Pseudo Compositional option for the run. See also the GINODE, RSGI, RVGI, BGGI and BOGI keywords in the PROPS section to describe the fluid properties for the GI Pseudo Compositional option.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Pressure","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"RWGSALT":{"name":"RWGSALT","sections":["PROPS"],"supported":null,"summary":"RWGSALT defines the relationship of water vaporization versus pressure and salt concentration. This keyword should be used when the VAPWAT keyword has be declared in the RUNSPEC section indicating that vaporized water is present in the gas phase. In addition, if the Salt Precipitation model has been activated via the BRINE and PRECSALT keywords, also in the RUNSPEC section, then this keyword must be present. The keyword may be used for gas-water and oil-water-gas input decks that contain the either dry or wet gas and vaporized water phases.","parameters":[{"index":1,"name":"PRESS","description":"A real monotonically increasing down the column values that define the gas phase pressure, that together with salt concentration, defines the vaporized water in gas ratio (“VWGR”) or Rw","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":"Pressure"},{"index":2,"name":"SALTCON","description":"A real monotonically increasing positive columnar vector defining the salt concentration in water.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None","value_type":"DOUBLE","dimension":["Concentration","OilDissolutionFactor"]},{"index":3,"name":"RW","description":"A columnar vector of real positive number values defining the vaporized water in gas ratio (Rw) that for a given PRESS and SALTCON.","units":{"field":"stb/Mscf","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"None"}],"example":"The example defines two RWGSALT tables assuming NTPVT equals two and NPPVT is greater than or equal to eight on the TABDIMS keyword in the RUNSPEC section.\n--\n-- WATER VAPORIZATION TABLE FOR BRINE (OPM FLOW KEYWORD)\n--\nRWGSALT\n-- PRES SALTCONC RVW\n-- PSIA LB/STB STB/MSCF\n-- ------ ---------- ---------\n300 0 0.000132\n0.5 0.000132\n1 0.000132 /\n600 0 0.000132\n0.5 0.000132\n1 0.000132 /\n900 0 0.000132\n0.5 0.000132\n1 0.000132 /\n1200 0 0.000132\n0.5 0.000132\n1 0.000132 /\n1500 0 0.000132\n0.5 0.000132\n1 0.000132 /\n1800 0 0.000132\n0.5 0.000132\n1 0.000132 /\n2100 0 0.000132\n0.5 0.000132\n1 0.000132 /\n2400 0 0.000132\n0.5 0.000132\n1 0.000132 /\n/ Table NO. 1\n-- PRES SALTCONC RW\n-- PSIA LB/STB STB/MSCF\n-- ------ ---------- ---------\n300 0 0.000132\n0.5 0.000132\n1 0.000132 /\n600 0 0.000132\n0.5 0.000132\n1 0.000132 /\n900 0 0.000132\n0.5 0.000132\n1 0.000132 /\n1200 0 0.000132\n0.5 0.000132\n1 0.000132 /\n1500 0 0.000132\n0.5 0.000132\n1 0.000132 /\n1800 0 0.000132\n0.5 0.000132\n1 0.000132 /\n2100 0 0.000132\n0.5 0.000132\n1 0.000132 /\n2400 0 0.000132\n0.5 0.000132\n1 0.000132 /\n/ Table NO. 2\n| Note This is an OPM Flow specific keyword for the simulator’s Water Vaporization and Salt Precipitation Models, note that these are extensions to the simulator’s standard Brine model. |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"list","variadic_record":true},"SALINITY":{"name":"SALINITY","sections":["PROPS"],"supported":null,"summary":"The SALINITY keyword defines a uniform salinity for all cells in the model. The keyword should only be used with OPM Flow’s CO2-Brine model which is activated via the CO2STORE keyword in the RUNSPEC section. This keyword is a compositional keyword in the commercial simulator but has been implemented in OPM Flow’s black-oil CO2-Brine model.","parameters":[{"index":1,"name":"SALINITY","description":"A real positive value that defines the salinity for all grid blocks in the model for when the CO2-Brine model has been activated. Note that the units for salinity are molality, that is gm-M/Kg, and therefore the units are defined as given below with the 10-3 prefix.","units":{"field":"10-3 x lb-M/lb","metric":"10-3 x kg-M/kg","laboratory":"10-3 x gm-M/gm"},"default":"","value_type":"DOUBLE"}],"example":"The example sets the salt salinity for all cells in the model to 0.001 lb-M/Ib.\n--\n-- SET SALINITY FOR ALL CELLS (OPM FLOW KEYWORD)\n--\nSALINITY\n1.0 /\nNote that units for salinity are to the 10-3, that is a value of 0.001 lb-M/lb should be entered as 1.0 (10-3 x lb-M/lb), as per the example.","expected_columns":1,"size_kind":"fixed","size_count":1},"SALTMF":{"name":"SALTMF","sections":["PROPS"],"supported":null,"summary":"The SALTMF keyword defines a uniform salt liquid-phase mole fraction for all cells in the model. The keyword should only be used with OPM Flow’s CO2-Brine model which is activated via the CO2STORE keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"SALTMF","description":"A real positive value that defines the salt liquid-phase mole fraction for all grid blocks in the model for when the CO2-Brine model has been activated.","units":{"field":"mole fraction","metric":"mole fraction","laboratory":"mole fraction"},"default":"","value_type":"DOUBLE"}],"example":"The example sets the salt liquid-phase mole fraction for all cells in the model to 0.018.\n--\n-- SET SALT LIQUID-PHASE MOLE FRACTION FOR ALL CELLS (OPM FLOW KEYWORD)\n--\nSALTMF\n0.018 /","expected_columns":1,"size_kind":"fixed","size_count":1},"SALTNODE":{"name":"SALTNODE","sections":["PROPS"],"supported":false,"summary":"SALTNODE defines the salt concentration value based on a cells PVTNUM number. The SALTNODE property is used in the calculation of a polymer viscosity when the polymer and the salt options has been activated by the POLYMER and BRINE keywords in the RUNSPEC section. In the RUNSPEC section the number of PVTNUM functions is declared by NTPVT variable on the TABDIMS keyword and allocated to individual cells by the PVTNUM property array in the REGIONS section. NPPVT on the TABDIMS keyword in the RUNSPEC section defines the maximum number of rows (or pressure values) in the PVT tables and also sets the maximum number of entries for each SALNODE data set. The number of values for each data set must correspond to the number of polymer solution adsorption entries on the PLYADSS keyword. For example if there are three sets of PVT tables and four values on the PLYADSS keyword, then three SALTNODE data sets with four values of salt concentrations need to be entered.","parameters":[{"index":1,"name":"SALTNODE","description":"A real monotonically increasing positive columnar vector defining the salt concentration for a given PVTNUM table.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None","value_type":"DOUBLE","dimension":"Concentration"}],"example":"Given three sets of relative permeability tables and four values on the PLYADSS keyword and two SALNODE data sets with four values of salt concentrations then the data should be entered as follows:\n--\n-- SETS SALT CONCENTRATION FOR POLYMER SOLUTION ADSORPTION\n-- VIA PVTNUM ARRAY ALLOCATION\n--\n-- SALT\n--\nSALTNODE\n1.0\n5.0\n10.5\n25.0 / PVTNUM TABLE NO. 01\n1.0\n3.0\n7.5\n15.0 / PVTNUM TABLE NO. 02\nSee also the ADSALNOD keyword.","size_kind":"fixed","variadic_record":true},"SALTSOL":{"name":"SALTSOL","sections":["PROPS"],"supported":null,"summary":"SALTSOL defines a grid block's maximum salt solubility for each PVTNUM region. The keyword should only be used with OPM Flow’s Salt Precipitation model which is activated via the PRECSALT keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"SALTSOL","description":"A real positive value that defines the maximum salt solubility for all grid blocks in a PVTNUM region.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None","value_type":"DOUBLE","dimension":["Concentration","Density"]}],"example":"The first example sets the maximum salt solubility for all cells in the model to 134.6 lb/stb, assuming that there is only one PVT region, that is NTPVT is equal to one on the TABDIMS keyword in the RUNSPEC section.\n--\n-- SET SALT SOLUBILITY LIMIT FOR EACH REGION (OPM FLOW KEYWORD)\n--\nSALTSOL\n-- MAX SALT\n-- SALTSOL DENSITY\n134.6 1* /\nThe 134.6 lb/stb, (380 kg/sm3 or 0.384 gm/scc for metric and laboratory units, respectively) is based on the solubility of NACL at 212 oF (100 oC) and should be used with care.\nThe next example shows how to set the maximum salt solubility for when NTPVT is equal to three on the TABDIMS keyword in the RUNSPEC section.\n--\n-- SET SALT SOLUBILITY LIMIT FOR EACH REGION (OPM FLOW KEYWORD)\n--\nSALTSOL\n134.6 / PVT REGION NO. 1\n124.0 / PVT REGION NO. 2\n/ PVT REGION NO. 3\nHere the last entry, which is for region number three, is defaulted, and results in region’s three maximum salt solubility to take the previous value, in this case 124.0 lb/stb.\n| Note This is an OPM Flow specific keyword for the simulator’s Salt Precipitation model that is activated by the PRECSALT keyword and declaring that vaporized water is present in the run via the VAPWAT in the RUNSPEC section. |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"fixed","variadic_record":true},"SCALECRS":{"name":"SCALECRS","sections":["PROPS"],"supported":null,"summary":"The SCALECRS keyword sets the end-point scaling option to be either two-point or three-point scaling, for when the End-Point Scaling option has been invoked by the ENDSCALE keyword in the RUNSPEC section. This determines which end-points on the relative permeability curves are used for scaling based on the supplied end-point arrays (SGCR, SWCR, etc.).","parameters":[{"index":1,"name":"SCALEOPT","description":"SCALEOPT is a character string that sets the end-point scaling option and should be set to either NO or YES: NO: Activates two-point end-point scaling. YES: Activates three-point end-point","units":{},"default":"NO","value_type":"STRING"}],"example":"--\n-- TWO-POINT END-POINT SCALING IS NO THREE POINT IS YES\n--\n-- SCALEOPT\n-- ---------\nSCALECRS\nYES / SCALING OPTION\nThe above example activates three-point end-point scaling of the relative permeability curves.\n| Option | Phases | Relative Permeability End-Point | Minimum Saturation End-Point | Middle Saturation End-Point | Maximum Saturation End-Point |\n|---------------------------------|--------|---------------------------------|------------------------------|-----------------------------|------------------------------|\n| Two-Point | Water | KRW | SWCR | | SWU |\n| Gas | KRG | SGCR | | SGU | |\n| Oil-Water | KRORW | SOWCR | | (1.0 – SWL - SGL) | |\n| Oil-Gas | KRORG | SOGCR | | (1.0 – SWL - SGL) | |\n| Three-Point | Water | KRW | SWCR | (1.0 – SOWCR - SGL) | SWU |\n| Gas | KRG | SGCR | (1.0 - SOGCR-SWL) | SGU | |\n| Oil-Water | KRORW | SOWCR | (1.0 – SWCR - SGL) | (1.0 – SWL - SGL) | |\n| Oil-Gas | KRORG | SOGCR | (1.0 – SGCR - SGL) | (1.0 – SWL - SGL) | |\n| Two Phase Gas-Water Simulations | | | | | |\n| Water | KRW | SWCR | (1.0 - SGCR) | SWU | |\n| Gas | KRG | SGCR | (1.0 -SWCR) | SGU | |","expected_columns":1,"size_kind":"fixed","size_count":1},"SCALELIM":{"name":"SCALELIM","sections":["PROPS"],"supported":false,"summary":"This keyword defines the maximum water saturation allowed in a cell for when the end-point versus depth tables are used in the End-Point Scaling option to calculate the water saturation for a grid block. The End-Point Scaling option must be invoked by the ENDSCALE keyword in the RUNSPEC section to use this keyword, and the keyword may only be used in two phase runs containing water, or if the Miscible Flood option has been activated by the MISCIBLE keyword in the RUNSPEC section. This keyword functionality is not supported in OPM Flow.","parameters":[{"index":1,"name":"SAT_LIMIT","description":"","units":{},"default":"0","value_type":"DOUBLE"}],"example":"","expected_columns":1,"size_kind":"fixed"},"SDENSITY":{"name":"SDENSITY","sections":["PROPS"],"supported":null,"summary":"The SDENSITY keyword defines density at surface conditions of either the miscible injection gas for when the MISCIBLE option has been invoked in the RUNSPEC section, or the solvent for when the SOLVENT option has been invoked in the RUNSPEC section. This keyword must be invoked if either the MISCIBLE or SOLVENT options have been activated in the RUNSPEC section.","parameters":[{"index":1,"name":"SDENSITY","description":"SDENSITY is a real positive number defining the density at surface conditions of either: the miscible injection gas for when the MISCIBLE option has been invoked in the RUNSPEC section, or, the solvent for when the SOLVENT option has been invoked in the RUNSPEC section.","units":{"field":"lb/ft3","metric":"kg/m3","laboratory":"gm/cc"},"default":"None","value_type":"DOUBLE","dimension":"Density"}],"example":"The following shows the SDENSITY keyword for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set to one.\n--\n-- MIS-SOL\n-- DENSITY\n-- -------\nSDENSITY\n0.04520 / MIS-SOL DENSITY\nThe next example shows the SDENSITY keyword for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set to three.\n--\n-- MIS-SOL\n-- DENSITY\n-- -------\nSDENSITY\n0.04520 / MIS-SOL DENSITY 1\n0.05520 / MIS-SOL DENSITY 2\n0.06420 / MIS-SOL DENSITY 3\nThere is no terminating “/” for this keyword.","expected_columns":1,"size_kind":"fixed"},"SGCR":{"name":"SGCR","sections":["PROPS"],"supported":null,"summary":"SGCR defines the critical gas saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE keyword in the RUNSPEC section. The critical gas saturation is defined as the maximum gas saturation for which the gas relative permeability is zero in a two-phase relative permeability table.","parameters":[{"index":1,"name":"SGCR","description":"SGCR is an array of real numbers assigning the critical gas saturation values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.03","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT SGCR DATA FOR ALL CELLS\n-- (FOR NX x NY x NZ = 300)\n--\nSGCR\n300*0.050 /\nThe above example defines a constant critical gas saturation of 0.05 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"SGCWMIS":{"name":"SGCWMIS","sections":["PROPS"],"supported":null,"summary":"SGCWMIS defines the dependency between the miscible critical gas saturation and the water saturation, for when the MISCIBLE keyword in the RUNSPEC section has been activated. The keyword can only be used with the MISCIBLE option and for when the oil, water and gas phases are active in the model.","parameters":[{"index":1,"name":"SWAT","description":"A columnar vector of real monotonically increasing down the column values starting from zero and terminating atone, that defines the water saturation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":["1","1"]},{"index":2,"name":"SGCMIS","description":"A columnar vector of real equal or increasing down the column values that are greater than or equal to zero and less than one, that define the corresponding miscible gas critical gas saturation for the corresponding water saturation SWAT.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- MISCIBLE CRITICAL GAS VERSUS WATER SATURATION TABLE\n--\nSGCWMIS\n-- SWAT SGCRMIS\n-- FRAC FRAC\n-- ------- --------\n0.0000 0.0000\n0.2000 0.0300\n1.0000 0.0300 / TABLE NO. 01\n-- SWAT SGCRMIS\n-- FRAC FRAC\n-- ------- --------\n0.0000 0.0000\n0.3000 0.0500\n1.0000 0.0500 / TABLE NO. 02\nThe above example defines two miscible critical gas saturation versus water saturation tables assuming NTMISC equals two and NSMISC is greater than or equal to three on the MISCIBLE keyword in the RUNSPEC section.","size_kind":"fixed","variadic_record":true},"SGF32D":{"name":"SGF32D","sections":["PROPS"],"supported":false,"summary":"The SGF32D keyword defines the gas relative permeability as a function of both oil and water saturations. This keyword should only be used if the gas is present in the run.","parameters":[{"index":1,"name":"SOIL","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1","record":1},{"index":1,"name":"SWAT","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1","record":2},{"index":2,"name":"KRG","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1","record":2}],"example":"","records_meta":[{},{"expected_columns":2}],"size_kind":"list"},"SGFN":{"name":"SGFN","sections":["PROPS"],"supported":null,"summary":"The SGFN keyword defines the gas relative permeability and oil-gas capillary pressure data versus gas saturation tables for when gas is present in the input deck. This keyword should only be used if the gas is present in the run.","parameters":[{"index":1,"name":"SGAS","description":"A columnar vector of real monotonically increasing down the column values starting from zero and terminating at one, that defines the gas saturation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":["1","1","Pressure"]},{"index":2,"name":"KRG","description":"A columnar vector of real values that are either equal or increasing down the column and that are greater than or equal to zero and less than or equal to one that defines the gas relative permeability.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":3,"name":"PCOG","description":"A columnar vector of real values that are either equal or increasing down the column that defines the oil-gas capillary pressure.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"None"}],"example":"--\n-- GAS RELATIVE PERMEABILITY TABLES (SGFN)\n--\nSGFN\n-- SGAS KRG PCGO\n-- FRAC PSIA\n-- -------- -------- -------\n0.00 0.0000 0.0\n0.05 0.0000 0.0\n0.10 0.0000 0.0\n0.15 0.0000 0.0\n0.20 0.0002 0.0\n0.25 0.0010 0.0\n0.30 0.0062 0.0\n0.35 0.0140 0.0\n0.40 0.0273 0.0\n0.45 0.0450 0.0\n0.50 0.0707 0.0\n0.55 0.1020 0.0\n0.60 0.1412 0.0\n0.65 0.1870 0.0\n0.70 0.2412 0.0\n0.77 0.3288 0.0\n0.82 0.4000 0.0\n0.85 0.4450 0.0 / TABLE NO. 01\n-- SGAS KRG PCGO\n-- FRAC PSIA\n-- -------- -------- -------\n0.00 0.0000 0.0\n0.05 0.0000 0.0\n0.10 0.0000 0.0\n0.15 0.0000 0.0\n0.20 0.0002 0.0\n0.25 0.0010 0.0\n0.30 0.0062 0.0\n0.35 0.0140 0.0\n0.40 0.0273 0.0\n0.45 0.0450 0.0\n0.50 0.0707 0.0\n0.55 0.1020 0.0\n0.60 0.1412 0.0\n0.65 0.1870 0.0\n0.70 0.2412 0.0\n0.77 0.3288 0.0\n0.82 0.4000 0.0\n0.85 0.4450 0.0 / TABLE NO. 02\nThe example defines two SGFN tables for when gas is present in the input deck.","size_kind":"fixed","variadic_record":true},"SGL":{"name":"SGL","sections":["PROPS"],"supported":null,"summary":"SGL defines the connate gas saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE keyword in the RUNSPEC section. The connate gas saturation is defined as the minimum gas saturation in a two-phase gas relative permeability table.","parameters":[{"index":1,"name":"SGL","description":"SGL is an array of real numbers assigning the connate gas saturation values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.03","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT SGL DATA FOR ALL CELLS\n– (FOR NX x NY x NZ = 300)\n--\nSGL\n300*0.030 /\nThe above example defines a constant connate gas saturation of 0.03 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"SGLPC":{"name":"SGLPC","sections":["PROPS"],"supported":null,"summary":"SGLPC defines the connate gas saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE keyword in the RUNSPEC section. The connate gas saturation is defined as the minimum gas saturation in a two-phase gas relative permeability table. The keyword only applies the scaling to the drainage capillary pressure tables, unlike the SGL keyword that applies the scaling to both the capillary pressure and relative permeability tables. The keyword can be used with all grid types.","parameters":[{"index":1,"name":"SGLPC","description":"SGLPC is an array of real numbers assigning the connate gas saturation values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. If SGLPC is omitted from the input deck the values will be defaulted to those on the SGL series of keywords. If the SGL series of keywords are missing from the input deck then the values are taken from the cell allocated capillary pressure table. Repeat counts may be used, for example 30*0.03","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from SGL or from the cell allocated capillary pressure table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT SGLPC DATA FOR ALL CELLS\n–- (FOR NX x NY x NZ = 300)\n--\nSGLPC\n300*0.030 /\nThe above example defines a constant connate gas saturation of 0.03 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"SGOF":{"name":"SGOF","sections":["PROPS"],"supported":null,"summary":"The SGOF keyword defines the oil and gas relative permeability and oil-gas capillary versus gas saturation tables for when oil and gas are present in the input deck. This keyword should only be used if both oil and gas are present in the run.","parameters":[{"index":1,"name":"SGAS","description":"A columnar vector of real monotonically increasing down the column values starting from zero and terminating at one, that defines the gas saturation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":["1","1","1","Pressure"]},{"index":2,"name":"KRG","description":"A columnar vector of real values that are either equal or increasing down the column and that are greater than or equal to zero and less than or equal to one that defines the gas relative permeability.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":3,"name":"KRO","description":"A columnar vector of real values that are either equal or decreasing down the column and that are greater than or equal to zero and less than or equal to one that defines the oil relative permeability with respect to gas and connate water saturation. When water is active in the run, the first entry the column, that is at krog(Sg = 0), must be the same as the first entry in the corresponding SWOF table, that is at krow(So = 1 - Swco). The last value in the column should be zero.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":4,"name":"PCOG","description":"A columnar vector of real values that are either equal or increasing down the column that defines the oil-gas relative capillary pressure.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"None"}],"example":"The following example is based on NTSFUN equals two on the TABDIMS keyword in the RUNSPEC section.\n--\n-- GAS-OIL RELATIVE PERMEABILITY TABLES (SGOF)\nSGOF\n-- SG KRG KROG PCOG\n-- FRAC PSIA\n-- ------- -------- ------- -------\n0.00000 0.000000 0.90000 0.0000\n0.03000 0.000000 0.82500 0.0000\n0.80000 0.900000 0.00000 0.0000 / TABLE No. 01\n-- ------- -------- ------- -------\n0.00000 0.000000 0.90000 0.0000\n0.03000 0.000000 0.82500 0.0000\n0.04420 0.024200 0.80000 0.0000\n0.05850 0.048500 0.77500 0.0000\n0.07270 0.072700 0.75000 0.0000\n0.08700 0.097000 0.72500 0.0000\n0.10120 0.121200 0.70000 0.0000\n0.11550 0.145500 0.67500 0.0000\n0.12970 0.169700 0.65000 0.0000\n0.14390 0.193900 0.62500 0.0000\n0.15820 0.218200 0.60000 0.0000\n0.17240 0.242400 0.57500 0.0000\n0.18670 0.266700 0.55000 0.0000\n0.20090 0.290900 0.52500 0.0000\n0.21520 0.315200 0.50000 0.0000\n0.22940 0.339400 0.47500 0.0000\n0.24360 0.363600 0.45000 0.0000\n0.25790 0.387900 0.42500 0.0000\n0.27210 0.412100 0.40000 0.0000\n0.28640 0.436400 0.37500 0.0000\n0.30060 0.460600 0.35000 0.0000\n0.31480 0.484800 0.32500 0.0000\n0.32910 0.509100 0.30000 0.0000\n0.34330 0.533300 0.27500 0.0000\n0.35760 0.557600 0.25000 0.0000\n0.37180 0.581800 0.22500 0.0000\n0.38610 0.606100 0.20000 0.0000\n0.40030 0.630300 0.17500 0.0000\n0.41450 0.654500 0.15000 0.0000\n0.42880 0.678800 0.12500 0.0000\n0.44300 0.703000 0.10000 0.0000\n0.45730 0.727300 0.07500 0.0000\n0.47150 0.751500 0.05000 0.0000\n0.48580 0.775800 0.02500 0.0000\n0.50000 0.800000 0.00000 0.0000\n0.80000 0.900000 0.00000 0.0000 / TABLE No. 02\nThe example defines two SGOF tables for use when oil, gas and water are present in the run.","size_kind":"fixed","variadic_record":true},"SGOFLET":{"name":"SGOFLET","sections":["PROPS"],"supported":null,"summary":"SGOFLET defines the relative permeability and capillary pressure parameters for the gas-oil LET family of models. Both the gas and oil phases should be made active in the model via the GAS and OIL keywords in the RUNSPEC section. See section 8.2.6Saturation Table Generation - LET Functionsand Lomeland et al.232\n Lomeland F., Ebeltoft E. and Thomas W.H., 2005. A New Versatile Relative Permeability Correlation. Paper SCA2005-32 presented at the International Symposium of the Society of Core Analysts held in Toronto, Canada, 21-25 August, 2005.,233\n Lomeland F. and Ebeltoft E., 2008. A New Versatile Capillary Pressure Correlation. Paper SCA2008-08 presented at the International Symposium of the Society of Core Analysts held in Abu Dhabi, UAE, 29 Oct. – 2 Nov., 2008. 234\n Lomeland F., Hasanov B., Ebeltoft E. and Berge M., 2012. A Versatile Representation of Up-scaled Relative Permeability for Field Applications. Paper SPE 154487-MS presented at the EAGE Annual Conferen...","parameters":[{"index":1,"name":"SGL","description":"SGL is a real positive number less than one that defines the connate gas saturation, that is smallest gas saturation in the LET function.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0,0","value_type":"DOUBLE","dimension":"1"},{"index":2,"name":"SGCR","description":"SGCR is a real positive number greater than or equal to SGL and less than one, that defines the critical gas saturation, that is the largest gas saturation for which the gas relative permeability is zero.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0,0","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"LGAS","description":"LGAS is a real positive number that defines the LET Lower empirical parameter Lg for the gas phase with the associated oil phase in the LET relative permeability equation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0","value_type":"DOUBLE","dimension":"1"},{"index":4,"name":"EGAS","description":"EGAS is a real positive number that defines the LET Elevation empirical parameter Eg for the gas phase with the associated oil phase in the LET relative permeability equation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0","value_type":"DOUBLE","dimension":"1"},{"index":5,"name":"TGAS","description":"TGAS is a real positive number that defines the LET Top empirical parameter Tg for the gas phase with the associated oil phase in the LET relative permeability equation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0","value_type":"DOUBLE","dimension":"1"},{"index":6,"name":"KRTGAS","description":"KRTGAS is a real positive number less than one, that defines the relative permeability of gas at the maximum gas saturation Krgt in the LET relative permeability equation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0","value_type":"DOUBLE","dimension":"1"},{"index":7,"name":"SORG","description":"SORG is a real positive number less than one that defines the residual oil saturation in a gas-oil system in the LET equations.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0,0","value_type":"DOUBLE","dimension":"1"},{"index":8,"name":"SOGCR","description":"SOGCR is a real positive number less than one that defines critical oil-in-gas saturation, that is the largest oil saturation for which the oil relative permeability is zero in a gas-oil system.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0,0","value_type":"DOUBLE","dimension":"1"},{"index":9,"name":"LOIL","description":"LOIL is a real positive number that defines the LET Lower empirical parameter Lo for the oil phase with the associated gas phase in the LET relative permeability equation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0","value_type":"DOUBLE","dimension":"1"},{"index":10,"name":"EOIL","description":"EOIL is a real positive number that defines the LET Elevation empirical parameter Eo for the oil phase with the associated gas phase in the LET relative permeability equation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0","value_type":"DOUBLE","dimension":"1"},{"index":11,"name":"TOIL","description":"TOIL is a real positive number that defines the LET Top empirical parameter To for the oil phase with the associated gas phase in the LET relative permeability equation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0","value_type":"DOUBLE","dimension":"1"},{"index":12,"name":"KRTOIL","description":"KRTOIL is a real positive number less than or equal to one, that defines the relative permeability of oil at the residual oil saturation, Krot in the LET relative permeability equation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0","value_type":"DOUBLE","dimension":"1"},{"index":13,"name":"LPC","description":"LPC is a real positive number that defines the gas-oil LET Lower empirical parameter L in the LET capillary pressure equation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0","value_type":"DOUBLE","dimension":"1"},{"index":14,"name":"EPC","description":"EPC is a real positive number that defines the gas-oil LET Elevation empirical parameter E in the LET capillary pressure equation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0","value_type":"DOUBLE","dimension":"1"},{"index":15,"name":"TPC","description":"TPC is a real positive number that defines the gas-oil LET Top empirical parameter T in the LET capillary pressure equation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0","value_type":"DOUBLE","dimension":"1"},{"index":16,"name":"PCIR","description":"PCIR is a real positive number that defines the gas-oil capillary pressure at connate water saturation (SWL) in the LET capillary pressure equations.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"0,0","value_type":"DOUBLE","dimension":"Pressure"},{"index":17,"name":"PCIT","description":"PCIT is a real positive number that defines the gas-oil threshold capillary pressure at the maximum water saturation in the LET capillary pressure equations.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"0,0","value_type":"DOUBLE","dimension":"Pressure"}],"example":"The following example uses the SGOFLET keyword to define two relative gas-oil relative permeability tables, based on NTSFUN equals two on the TABDIMS keyword in the RUNSPEC section.\n--\n-- SGOFLET – GAS-OIL LET REL. PERMEABILITY FUNCTIONS (OPM FLOW KEYWORD)\n--\nSGOFLET\n-- SGL SGCR L-GAS E-GAS T-GAS KRT-GAS\n-- SOR SOGCR L-OIL E-OIL T-OIL KRT-OIL\n-- L-PC E-PC T-PC PCIR PCIT\n-- ------- ------ ------- ------- ------- -------\n0.00000 0.0000 1.00000 1.00000 1.00000 1.00000\n0.00000 0.0000 1.00000 1.00000 1.00000 1.00000\n1* 1* 1* 1* 1* / TABLE NO. 01\n0.00000 0.0000 1.00000 1.00000 1.00000 1.00000\n0.00000 0.0000 1.00000 1.00000 1.00000 1.00000\n1* 1* 1* 1* 1* / TABLE NO. 02\nHere the SGOFLET keyword parameters are all set to their default values.\n| Note This is an OPM Flow specific keyword and will therefore cause an error in the commercial simulator. |\n|----------------------------------------------------------------------------------------------------------|\n| Note All the LET parameters are dependent on the flooding event and flooding cycle, and thus are expected vary as such. To be clear, the values of SGCR, Lg, Lo etc. should be different for each flooding cycle. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":17,"size_kind":"fixed"},"SGU":{"name":"SGU","sections":["PROPS"],"supported":null,"summary":"SGU defines the maximum gas saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE keyword in the RUNSPEC section. The maximum gas saturation is defined as the maximum gas saturation in a two-phase gas relative permeability table.","parameters":[{"index":1,"name":"SGU","description":"SGU is an array of real numbers assigning the maximum gas saturation values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.70","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT SGU DATA FOR ALL CELLS\n-- (FOR NX x NY x NZ = 300)\n--\nSGU\n300*0.700 /\nThe above example defines a constant connate gas saturation of 0.70 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"SGWFLET":{"name":"SGWFLET","sections":["PROPS"],"supported":null,"summary":"SWGFLET defines the relative permeability and capillary pressure parameters for the water-gas LET family of models. Both the gas and water phases should be made active in the model via the GAS and WATER keywords in the RUNSPEC section. This keyword should only be used in two-phase models containing the gas and water phases only, that is the oil phase must be absent. See section 8.2.6Saturation Table Generation - LET Functionsand Lomeland et al.237\n Lomeland F., Ebeltoft E. and Thomas W.H., 2005. A New Versatile Relative Permeability Correlation. Paper SCA2005-32 presented at the International Symposium of the Society of Core Analysts held in Toronto, Canada, 21-25 August, 2005.,238\n Lomeland F. and Ebeltoft E., 2008. A New Versatile Capillary Pressure Correlation. Paper SCA2008-08 presented at the International Symposium of the Society of Core Analysts held in Abu Dhabi, UAE, 29 Oct. – 2 Nov., 2008. 239\n Lomeland F., Hasanov B., Ebeltoft E. and Berge M., 2012. A Ve...","parameters":[{"index":1,"name":"SGL","description":"SGL is a real positive number less than one that defines the connate gas saturation, that is smallest gas saturation in the LET function.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0,0"},{"index":2,"name":"SGCR","description":"SGCR is a real positive number greater than or equal to SGL and less than one, that defines the critical gas saturation, that is the largest gas saturation for which the gas relative permeability is zero.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0,0"},{"index":3,"name":"LGAS","description":"LGAS is a real positive number that defines the LET Lower empirical parameter Lg for the gas phase with the associated water phase in the LET relative permeability equations.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0"},{"index":4,"name":"EGAS","description":"EGAS is a real positive number that defines the LET Elevation empirical parameter Eg for the gas phase with the associated water phase in the LET relative permeability equations.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0"},{"index":5,"name":"TGAS","description":"TGAS is a real positive number that defines the LET Top empirical parameter Tg for the gas phase with the associated water phase in the LET relative permeability equations.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0"},{"index":6,"name":"KRTGAS","description":"KRTGAS is a real positive number less than one, that defines the relative permeability of gas at the maximum gas saturation Krgt in the LET relative permeability equations.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0"},{"index":7,"name":"SWL","description":"SWL is a real positive number less than one, that defines the connate water saturation, that is the smallest water saturation in the LET function.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0,0"},{"index":8,"name":"SWCR","description":"SWCR is a real positive number greater than or equal to SWL and less than one, that defines the critical water saturation, that is the largest water saturation for which the water relative permeability is zero, Swirr in equations.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0,0"},{"index":9,"name":"LWAT","description":"LWAT is a real positive number that defines the LET Lower empirical parameter Lw for the water phase with the associated gas phase in the LET relative permeability equations.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0"},{"index":10,"name":"EWAT","description":"EWAT is a real positive number that defines the LET Elevation empirical parameter Ew for the water phase with the associated gas phase in the LET relative permeability equations.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0"},{"index":11,"name":"TWAT","description":"TWAT is a real positive number that defines the LET Top empirical parameter Tw for the water phase with the associated gas phase in the LET relative permeability equations.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0"},{"index":12,"name":"KRTWAT","description":"KRTWAT is a real positive number less than one, that defines the relative permeability of water at the maximum water saturation (normally the maximum water saturation is one) Krwt in the LET relative permeability equations.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0"},{"index":13,"name":"LPC","description":"LPC is a real positive number that defines the gas-water LET Lower empirical parameter L in the LET capillary pressure equation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0"},{"index":14,"name":"EPC","description":"EPC is a real positive number that defines the gas-water LET Elevation empirical parameter E in the LET capillary pressure equation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0"},{"index":15,"name":"TPC","description":"TPC is a real positive number that defines the gas-water LET empirical parameter T in the LET capillary pressure equation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0"},{"index":16,"name":"PCIR","description":"PCIR is a real positive number that defines the gas-water capillary pressure at connate water saturation (SWL) in the LET capillary pressure equations.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"0,0"},{"index":17,"name":"PCIT","description":"PCIT is a real positive number that defines the gas-water threshold capillary pressure at the maximum water saturation in the LET capillary pressure equations.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"0,0"}],"example":"The following example uses the SWGFLET keyword to define two relative gas-water relative permeability tables, based on NTSFUN equals two on the TABDIMS keyword in the RUNSPEC section.\n--\n-- SGWFLET – GAS-WATER LET REL. PERMEABILITY FUNCTIONS (OPM FLOW KEYWORD)\n--\nSGWFLET\n-- SGL SGCR L-GAS E-GAS T-GAS KRT-GAS\n-- SWL SWCR L-WAT E-WAT T-WAT KRT-WAT\n-- L-PC E-PC T-PC PCIR PCIT\n-- ------- ------ ------- ------- ------- -------\n0.00000 0.0000 1.00000 1.00000 1.00000 1.00000\n0.00000 0.0000 1.00000 1.00000 1.00000 1.00000\n1* 1* 1* 1* 1* / TABLE NO. 01\n0.00000 0.0000 1.00000 1.00000 1.00000 1.00000\n0.00000 0.0000 1.00000 1.00000 1.00000 1.00000\n1* 1* 1* 1* 1* / TABLE NO. 02\nHere the SGWFLET keyword parameters are all set to their default values.\n| Note This is an OPM Flow specific keyword and will therefore cause an error in the commercial simulator. |\n|----------------------------------------------------------------------------------------------------------|\n| Note All the LET parameters are dependent on the flooding event and flooding cycle, and thus are expected vary as such. To be clear, the values of SWCR, Lg, Lw etc. should be different for each flooding cycle. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|"},"SGWFN":{"name":"SGWFN","sections":["PROPS"],"supported":null,"summary":"The SGWFN keyword defines the gas and water relative permeability and gas-water capillary pressure data versus gas saturation tables for when gas and water are present in the input deck. This keyword should only be used if gas and water are present in the run.","parameters":[{"index":1,"name":"SGAS","description":"A columnar vector of real monotonically increasing down the column values starting from zero and terminating at one, that defines the gas saturation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":["1","1","1","Pressure"]},{"index":2,"name":"KRG","description":"A columnar vector of real values that are either equal or increasing down the column and that are greater than or equal to zero and less than or equal to one that defines the gas relative permeability. Note that the first entry in the column must be zero.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":3,"name":"KRW","description":"A columnar vector of real values that are either equal or decreasing down the column and that are greater than or equal to zero and less than or equal to one that defines the water relative permeability with respect to gas saturation. The last value in the column should be zero.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":4,"name":"PCGW","description":"A columnar vector of real values that are either equal or increasing down the column that defines the gas-water relative capillary pressure.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"None"}],"example":"--\n-- GAS-WATER RELATIVE PERMEABILITY TABLES (SGWFN)\nSGWFN\n-- SG KRG KRW PCOW\n-- FRAC PSIA\n-- -------- -------- ------- -------\n0.000000 0.0000 0.9000 0.000000\n0.200000 0.0002 0.7664 0.000000\n0.699099 0.4973 0.0000 0.000000\n0.700000 1.0000 0.0000 0.000000 / TABLE NO. 01\n-- -------- -------- ------- -------\n0.000000 0.0000 0.9000 0.000000\n0.200000 0.0002 0.7664 0.000000\n0.245309 0.0004 0.7443 0.000000\n0.261989 0.0010 0.6907 0.000000\n0.303091 0.0044 0.5671 0.000000\n0.368269 0.0191 0.3962 0.000000\n0.435026 0.0519 0.2528 0.000000\n0.486387 0.0940 0.1643 0.000000\n0.522283 0.1339 0.1137 0.000000\n0.550683 0.1725 0.0803 0.000000\n0.575342 0.2115 0.0559 0.000000\n0.599076 0.2542 0.0367 0.000000\n0.621294 0.2991 0.0223 0.000000\n0.642171 0.3458 0.0120 0.000000\n0.658984 0.3868 0.0061 0.000000\n0.671123 0.4183 0.0030 0.000000\n0.679268 0.4403 0.0015 0.000000\n0.684963 0.4562 0.0008 0.000000\n0.688893 0.4674 0.0004 0.000000\n0.692025 0.4765 0.0002 0.000000\n0.694641 0.4841 0.0001 0.000000\n0.696976 0.4910 0.0000 0.000000\n0.699099 0.4973 0.0000 0.000000\n0.700000 1.0000 0.0000 0.000000 / TABLE NO. 02\nThe example defines two SGWFN tables for use when gas and water are present in the run.","size_kind":"fixed","variadic_record":true},"SHRATE":{"name":"SHRATE","sections":["PROPS"],"supported":null,"summary":"This keyword activates the logarithm-based polymer shear thinning/thickening option and defines the shear rate constant. This keyword can only be used in conjunction with the PLYSHLOG in the PROPS section","parameters":[{"index":1,"name":"SHRATE","description":"A positive real value that defines the shear rate constant.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"4.8","value_type":"DOUBLE","dimension":"1"}],"example":"The following example activates the logarithm-based polymer shear thinning/thickening option and defines the shear rate constants for a run with two PVT regions.\n--\n--ACTIVATE LOG-BASED POLYMER SHEAR THINNING-THICKENING OPTION\n--AND DEFINE THE SHEAR RATE CONSTANT\n--\nSHRATE\n--SHEAR RATE\n--CONSTANT\n4.8 /\n4.8 /","size_kind":"fixed","variadic_record":true},"SKPRPOLY":{"name":"SKPRPOLY","sections":["PROPS"],"supported":null,"summary":"This keyword, SKPRPOLY, describes the relationship of a water injection well's injected polymer skin pressure as a function of polymer throughput and water velocity, for the simulator's Polymer Molecular Weight Transport option. The table is a two dimensional table that relates the polymer throughput values and water velocity values to derive the resulting wellbore skin pressure of the injected polymer, which is then used to calculate the total wellbore skin pressure based on the polymer concentration.","parameters":[{"index":1,"name":"SKPRPNUM","description":"A positive integer value greater than zero and less than or equal to the NTSKPOLY variable, as defined on the PINTDIMS keyword in the RUNSPEC section, that defines the SKPRPOLY Polymer Molecular Weight Model polymer injection skin pressure table number.","units":{},"default":"None","record":1,"value_type":"INT"},{"index":2,"name":"POLCON","description":"A real positive value that the defines the reference polymer concentration for the table.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None","record":1,"value_type":"DOUBLE","dimension":"Concentration"},{"index":1,"name":"THRUPUT","description":"A real positive monotonically increasing vector, that defines the polymer throughput values. The first entry should be zero to define a no throughput data set, and each vector record should be on a separate line terminated by a “/”.","units":{"field":"feet3/feet2","metric":"m3/m2","laboratory":"cm3/cm2"},"default":"None","record":2,"value_type":"DOUBLE","dimension":"Length"},{"index":1,"name":"VELOCITY","description":"A real positive monotonically increasing vector, that defines the polymer velocity values. The first entry should be zero to define a no velocity data set, and each vector record should be on a separate line terminated by a “/”.","units":{"field":"feet/day","metric":"m/day","laboratory":"cm/hour"},"default":"None","record":3,"value_type":"DOUBLE","dimension":"Length/Time"},{"index":1,"name":"PRESS","description":"A series of real positive vectors representing the wellbore skin pressure, for the given reference polymer concentration (POLCON), for all combinations of the polymer throughput values (THRUPUT) and velocity values (VELOCITY), organized as a series of vectors PRESS(THRUPUT, VELOCITY). Thus, the first vector represents the wellbore skin pressure of the first THRUPUT value and each entry in the vector is the corresponding wellbore skin pressure of the associated VELOCITY vector. Each vector should be on a separate line and should be terminated by a “/”. Thus, if THRUPUT has three entries and VELOCITY has four, then there should be three vectors, with each vector containing four elements representing wellbore skin pressure values, as a function of THRUPUT and VELOCITY.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","record":4,"value_type":"DOUBLE","dimension":"Pressure"}],"example":"Given NTSKPOLY equals two on the PINTDIMS keyword in the RUNSPEC section, then two SKPRPOLY tables are required to be entered:\n--\n-- POLYMER MOLECULAR WEIGHT MODEL POLYMER INJECTION SKIN TABLE\n-- (OPM FLOW PROPS KEYWORD)\n--\nSKPRPOLY\n-- TABLE POLYMER REF\n-- NO. CONCENTRATION\n1 2.00 /\n--\n-- THROUGHPUT VALUES\n--\n0.0 200.0 400.0 /\n--\n-- VELOCITY VALUES\n--\n0.0 50.0 80.0 100.0 /\n--\n-- PRESS SKIN VALUES\n--\n0.0 10.0 20.0 40.0 / PRESS(THRUPUT=1, VELOCITY=1 TO N)\n0.0 50.0 100.0 200.0 / PRESS(THRUPUT=2, VELOCITY=1 TO N)\n0.0 100.0 200.0 400.0 / PRESS(THRUPUT=3, VELOCITY=1 TO N)\n/\nSKPRPOLY\n-- TABLE POLYMER REF\n-- NO. CONCENTRATION\n2 2.0 /\n--\n-- THROUGHPUT VALUES\n--\n0.0 200.0 400.0 /\n--\n-- VELOCITY VALUES\n--\n0.0 30.0 50.0 100.0 /\n--\n-- PRESS SKIN VALUES\n--\n0.0 10.0 20.0 40.0 / PRESS(THRUPUT=1, VELOCITY=1 TO N)\n0.0 50.0 100.0 200.0 / PRESS(THRUPUT=2, VELOCITY=1 TO N)\n0.0 100.0 200.0 400.0 / PRESS(THRUPUT=3, VELOCITY=1 TO N)\n/\nAs mentioned previously, the SKPRPOLY keyword requires that the keyword itself must be repeated for each table, as is shown in the above example.\n| Note This is an OPM Flow specific keyword that employs an alternative polymer flood model based on a Polymer Molecular Weight Transport equation, that is not available in the commercial simulator. The model has been tested using metric units; however, using either field or laboratory units with the option should be considered experimental. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","records_meta":[{"expected_columns":2},{},{},{}],"size_kind":"list"},"SKPRWAT":{"name":"SKPRWAT","sections":["PROPS"],"supported":null,"summary":"This keyword, SKPRWAT, describes the relationship of a water injection well's injected water skin pressure as a function of water throughput and water velocity, for the simulator's Polymer Molecular Weight Transport option. The table is a two dimensional table that relates the water throughput values and water velocity values to derive the resulting wellbore skin pressure of the injected water, which is then used to calculate the total wellbore skin pressure based on the polymer concentration.","parameters":[{"index":1,"name":"SKPRWNUM","description":"A positive integer value greater than zero and less than or equal to the NTSKWAT variable, as defined on the PINTDIMS keyword in the RUNSPEC section, that defines the SKPRWAT Polymer Molecular Weight Model water injection skin pressure table number.","units":{},"default":"None","record":1,"value_type":"INT"},{"index":1,"name":"THRUPUT","description":"A real positive monotonically increasing vector, that defines the water throughput values. The first entry should be zero to define a no throughput data set, and each vector record should be on a separate line terminated by a “/”.","units":{"field":"feet3/feet2","metric":"m3/m2","laboratory":"cm3/cm2"},"default":"None","record":2,"value_type":"DOUBLE","dimension":"Length"},{"index":1,"name":"VELOCITY","description":"A real positive monotonically increasing vector, that defines the water velocity values. The first entry should be zero to define a no velocity data set, and each vector record should be on a separate line terminated by a “/”.","units":{"field":"feet/day","metric":"m/day","laboratory":"cm/hour"},"default":"None","record":3,"value_type":"DOUBLE","dimension":"Length/Time"},{"index":1,"name":"PRESS","description":"A series of real positive vectors representing the wellbore skin pressure, for all combinations of the water throughput values (THRUPUT) and velocity values (VELOCITY), organized as a series of vectors PRESS(THRUPUT, VELOCITY). Thus, the first vector represents the wellbore skin pressure of the first THRUPUT value and each entry in the vector is the corresponding wellbore skin pressure of the associated VELOCITY vector. Each vector should be on a separate line and should be terminated by a “/”. Thus, if THRUPUT has three entries and VELOCITY has four, then there should be three vectors, with each vector containing four elements representing wellbore skin pressure values, as a function of THRUPUT and VELOCITY.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","record":4,"value_type":"DOUBLE","dimension":"Pressure"}],"example":"Given NTSKWAT equals two on the PINTDIMS keyword in the RUNSPEC section, then two SKPRWAT tables are required to be entered:\n--\n-- POLYMER MOLECULAR WEIGHT MODEL WATER INJECTION SKIN TABLE\n-- (OPM FLOW PROPS KEYWORD)\n--\nSKPRWAT\n1 / TABLE NUMBER\n--\n-- THROUGHPUT VALUES\n--\n0.0 200.0 400.0 /\n--\n-- VELOCITY VALUES\n--\n0.0 50.0 70.0 100.0 /\n--\n-- PRESS SKIN VALUES\n--\n0.0 2.0 4.0 8.0 / PRESS(THRUPUT=1, VELOCITY=1 TO N)\n0.0 20.0 40.0 80.0 / PRESS(THRUPUT=2, VELOCITY=1 TO N)\n0.0 50.0 100.0 200.0 / PRESS(THRUPUT=3, VELOCITY=1 TO N)\n/\nSKPRWAT\n2 / TABLE NUMBER\n--\n-- THROUGHPUT VALUES\n--\n0.0 200.0 400.0 /\n--\n-- VELOCITY VALUES\n--\n0.0 30.0 50.0 100.0 /\n--\n-- PRESS SKIN VALUES\n--\n0.0 2.0 4.0 8.0 / PRESS(THRUPUT=1, VELOCITY=1 TO N)\n0.0 20.0 40.0 80.0 / PRESS(THRUPUT=2, VELOCITY=1 TO N)\n0.0 50.0 100.0 200.0 / PRESS(THRUPUT=3, VELOCITY=1 TO N)\n/\nAs mentioned previously, the SKPRWAT keyword requires that the keyword itself must be repeated for each table, as is shown in the above example.\n| Note This is an OPM Flow specific keyword that employs an alternative polymer flood model based on a Polymer Molecular Weight Transport equation, that is not available in the commercial simulator. The model has been tested using metric units; however, using either field or laboratory units with the option should be considered experimental. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","records_meta":[{"expected_columns":1},{},{},{}],"size_kind":"list"},"SKRO":{"name":"SKRO","sections":["PROPS"],"supported":false,"summary":"SKRO defines the scaling parameter for the surfactant oil relative permeability value at the connate water saturation (SWL), for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the Surfactant option must be enabled by either the SURFST or SURFSTES keywords in the RUNSPEC section.","parameters":[{"index":1,"name":"SKRO","description":"SKRO is an array of positive real numbers which are greater than zero and less than or equal to 1.0, that are the assigned scaling SKRO values for each cell in the model. Repeat counts may be used, for example 50*0.500.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"The example defines an input box for the whole grid and for layers one to three, for layer one SKRO is set equal to 0.850, for layer two SKRO equals 0.875, and for layer three SKRO equals 0.900.\n--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS (NX=100, NY=100)\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1* 1* 1* 1* 1 3 / DEFINE BOX AREA\n--\n-- SET SKRO VALUES FOR THREE LAYERS IN THE MODEL\n--\nSKRO\n1000*0.855 1000*0.875 1000.0.900 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX","size_kind":"array"},"SKRORG":{"name":"SKRORG","sections":["PROPS"],"supported":false,"summary":"SKRORG defines the scaling parameter for the surfactant relative permeability of oil at the critical gas saturation (SGCR), for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the Surfactant option must be enabled by either the SURFST or SURFSTES keywords in the RUNSPEC section.","parameters":[{"index":1,"name":"SKRORG","description":"SKRORG is an array of positive real numbers which are greater than zero and less than or equal to 1.0, that are the assigned scaling SKRORG values for each cell in the model. Repeat counts may be used, for example 50*0.850.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"The example uses the EQUALS keyword to set layer one SKRORG equal to 0.750, layer two SKRORG equals 0.775, and layer three SKRORG equals 0.800.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nSKRORG 0.7550 1* 1* 1* 1* 1 1 / SKRORG FOR LAYER 1\nSKRORG 0.7750 1* 1* 1* 1* 2 2 / SKRORG FOR LAYER 2\nSKRORG 0.8000 1* 1* 1* 1* 3 3 / SKRORG FOR LAYER 3\n/","size_kind":"array"},"SKRORW":{"name":"SKRORW","sections":["PROPS"],"supported":false,"summary":"SKRORW defines the scaling parameter for the surfactant relative permeability of oil at the critical water saturation (SWCR), for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the Surfactant option must be enabled by either the SURFST or SURFSTES keywords in the RUNSPEC section.","parameters":[{"index":1,"name":"SKRORW","description":"SKRORW is an array of positive real numbers which are greater than zero and less than or equal to 1.0, that are the assigned scaling SKRORW values for each cell in the model. Repeat counts may be used, for example 50*0.850","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"The example defines an input box for the whole grid and for layers one to three, for layer one SKRORW is set equal to 0.750, for layer two SKRORW equals 0.775, and for layer three SKRORW equals 0.800.\n--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS (NX=100, NY=100)\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1* 1* 1* 1* 1 3 / DEFINE BOX AREA\n--\n-- SET SKRORW VALUES FOR THREE LAYERS IN THE MODEL\n--\nSKRORW\n1000*0.755 1000*0.775 1000.0.800 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX","size_kind":"array"},"SKRW":{"name":"SKRW","sections":["PROPS"],"supported":false,"summary":"SKRW defines the scaling parameter at the maximum surfactant water relative permeability value (SWU), that is for Sw = 1.0, for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword. In addition, the Surfactant option must be enabled by either the SURFST or SURFSTES keywords in the RUNSPEC section.","parameters":[{"index":1,"name":"SKRW","description":"SKRW is an array of positive real numbers which are greater than zero and less than or equal to 1.0, that are the assigned scaling SKRW values for each cell in the model. Repeat counts may be used, for example 50*1.000.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"The example uses the EQUALS keyword to set SKRW for layer one equal to 0.850, layer two SKRW to 0.875, and layer three KRW to 0.900.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nSKRW 0.8550 1* 1* 1* 1* 1 1 / SKRW FOR LAYER 1\nSKRW 0.8750 1* 1* 1* 1* 2 2 / SKRW FOR LAYER 2\nSKRW 0.9000 1* 1* 1* 1* 3 3 / SKRW FOR LAYER 3\n/","size_kind":"array"},"SKRWR":{"name":"SKRWR","sections":["PROPS"],"supported":false,"summary":"SKRWR defines the scaling parameter at the critical oil to water saturation value (SOWCR), for the surfactant water relative permeability curve, for all the cells in the model via an array. The ENDSCALE keyword in the RUNSPEC section should be activated to enable end-point scaling and the use of this keyword.In addition, the Surfactant option must be enabled by either the SURFST or SURFSTES keywords in the RUNSPEC section.","parameters":[{"index":1,"name":"SKRWR","description":"SKRWR is an array of positive real numbers which are greater than zero and less than or equal to 1.0, that are the assigned scaling SKRWR values for each cell in the model. Repeat counts may be used, for example 50*1.000.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"The first example defines an input box for the whole grid and for layers one to three, for layer one SKRWR is set equal to 0.750, for layer two SKRWR equals 0.775, and for layer three SKRWR equals 0.800.\n--\n-- DEFINE INPUT BOX FOR EDITING INPUT ARRAYS (NX=100, NY=100)\n--\n-- ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nBOX\n1* 1* 1* 1* 1 3 / DEFINE BOX AREA\n--\n-- SET SKRWR VALUES FOR THREE LAYERS IN THE MODEL\n--\nSKRWR\n1000*0.755 1000*0.775 1000.0.800 /\n--\n-- DEFINE END OF INPUT BOX EDITING OF INPUT ARRAYS\n--\nENDBOX","size_kind":"array"},"SLGOF":{"name":"SLGOF","sections":["PROPS"],"supported":null,"summary":"The SLGOF keyword defines the oil and gas relative permeability and oil-gas capillary pressure versus liquid saturation tables for when oil and gas are present in the input deck. This keyword should only be used if both oil and gas are present in the run.","parameters":[{"index":1,"name":"SLIQ","description":"A columnar vector of real monotonically increasing down the column values starting from zero and terminating at one, that defines the liquid saturation, that is the connate water saturation (SWL) plus the oil saturation. The first entry should correspond to residual liquid, that is Swc + Sorg and the last entry should be 1.0 to correspond to a gas saturation of zero.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":["1","1","1","Pressure"]},{"index":2,"name":"KRG","description":"A columnar vector of real values that are either equal or decreasing down the column and that are greater than or equal to zero and less than or equal to one that defines the gas relative permeability..","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":3,"name":"KRO","description":"A columnar vector of real values that are either equal or increasing down the column and that are greater than or equal to zero and less than or equal to one that defines the oil relative permeability with respect to gas and connate water saturation. When water is active in the run, the last entry the column, that is at krog(Sg = 0), must be the same as the first entry in the corresponding SWOF table, that is at krow(So = 1 - Swco). The first value in the column should be zero.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":4,"name":"PCOG","description":"A columnar vector of real values that are either equal or decreasing down the column that defines the oil-gas relative capillary pressure.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"None"}],"example":"--\n-- GAS-OIL RELATIVE PERMEABILITY TABLES (SLGOF)\nSLGOF\n-- SLIQ KRG KROG PCOG\n-- FRAC PSIA\n-- ------- -------- ------- -------\n0.30060 0.55000 0.0000 0.0000\n0.31480 0.42500 0.2848 0.0000\n0.32910 0.35000 0.3091 0.0000\n0.34330 0.27500 0.4333 0.0000\n0.35760 0.25000 0.5576 0.0000\n0.37180 0.22500 0.5818 0.0000\n0.38610 0.20000 0.6061 0.0000\n0.40030 0.17500 0.6303 0.0000\n0.41450 0.15000 0.6545 0.0000\n0.42880 0.12500 0.6788 0.0000\n0.44300 0.10000 0.7030 0.0000\n0.45730 0.07500 0.7273 0.0000\n0.47150 0.05000 0.7515 0.0000\n0.48580 0.02500 0.7758 0.0000\n0.50000 0.00000 0.8000 0.0000\n0.80000 0.00000 0.9000 0.0000 / TABLE No. 01\n-- ------- -------- ------- -------\n0.30060 0.55000 0.0000 0.0000\n0.31480 0.42500 0.2848 0.0000\n0.32910 0.35000 0.3091 0.0000\n0.34330 0.27500 0.4333 0.0000\n0.35760 0.25000 0.5576 0.0000\n0.37180 0.22500 0.5818 0.0000\n0.38610 0.20000 0.6061 0.0000\n0.40030 0.17500 0.6303 0.0000\n0.41450 0.15000 0.6545 0.0000\n0.42880 0.12500 0.6788 0.0000\n0.44300 0.10000 0.7030 0.0000\n0.45730 0.07500 0.7273 0.0000\n0.47150 0.05000 0.7515 0.0000\n0.48580 0.02500 0.7758 0.0000\n0.50000 0.00000 0.8000 0.0000\n0.80000 0.00000 0.9000 0.0000 / TABLE No. 02\nThe example defines two SLGOF tables for use when oil, gas and water are present in the run.","size_kind":"fixed","variadic_record":true},"SOCRS":{"name":"SOCRS","sections":["PROPS"],"supported":false,"summary":"SOCRS defines the miscible critical oil saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE keyword in the RUNSPEC section. The critical oil saturation with respect to water is defined as the maximum oil saturation for which the oil relative permeability is zero in a two-phase oil-water relative permeability table. The keyword is used with the Surfactant model to re-scale the surfactant relative permeability saturation tables allocated to a grid block by the by the SURFNUM keyword in the REGIONS section.","parameters":[{"index":1,"name":"SOCRS","description":"SOCRS is an array of real numbers assigning the critical oil saturation with respect to water values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.30","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT SOCRS DATA FOR ALL CELLS\n-- (FOR NX x NY x NZ = 300)\n--\nSOCRS\n300*0.200 /\nThe above example defines a constant critical oil saturation of 0.20 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"SOF2":{"name":"SOF2","sections":["PROPS"],"supported":null,"summary":"The SOF2 keyword defines the oil relative permeability versus oil saturation tables for when oil and gas or oil and water are present in the input deck. The keyword is also used to define the relative permeability of the miscible hydrocarbon phase in SOLVENT runs. This keyword should only be used if oil is present in the run.","parameters":[{"index":1,"name":"SOIL","description":"A columnar vector of real monotonically increasing down the column values starting from zero and terminating at one, that defines the oil or the hydrocarbon solvent saturation. For two phase runs the oil saturation should be entered and for when the SOLVENT option has been activated in the RUNSPEC section the total hydrocarbon phase (including the solvent) should be entered, that is SOIL = So + Sg + Ss.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":["1","1"]},{"index":3,"name":"KRO","description":"A columnar vector of real values that are either equal or increasing down the column and that are greater than or equal to zero and less than or equal to one that defines the oil relative permeability with respect to gas and connate water saturation. For two phase runs the oil relative permeability should be entered and for when the SOLVENT option has been activated in the RUNSPEC section the relative permeability of the miscible hydrocarbon phase with respect to water. The last value in the column should be zero.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- OIL RELATIVE PERMEABILITY TABLES (SOF2)\n--\nSOF2\n-- SOIL KRO\n-- FRAC FRAC\n-- -------- --------\n0.00 0.000000\n0.05 1.197e-5\n0.10 0.000191\n0.15 0.000969\n0.20 0.003065\n0.25 0.007483\n0.30 0.015517\n0.35 0.028747\n0.40 0.049041\n0.45 0.078555\n0.50 0.119730\n0.55 0.175297\n0.60 0.248272\n0.65 0.341961\n0.70 0.459956\n0.75 0.606134\n0.80 0.784664\n0.85 1.000000 / TABLE NO. 01\n-- -------- --------\n0.00 0.000000\n0.05 1.197e-5\n0.10 0.000191\n0.15 0.000969\n0.20 0.003065\n0.25 0.007483\n0.30 0.015517\n0.35 0.028747\n0.40 0.049041\n0.45 0.078555\n0.50 0.119730\n0.55 0.175297\n0.60 0.248272\n0.65 0.341961\n0.70 0.459956\n0.75 0.606134\n0.80 0.784664\n0.85 1.000000 / TABLE NO. 02\nThe example defines two SOF2 tables for when oil and gas or oil and water are present in the input deck.","size_kind":"fixed","variadic_record":true},"SOF3":{"name":"SOF3","sections":["PROPS"],"supported":null,"summary":"The SOF3 keyword defines the oil relative permeability versus oil saturation tables for when oil, gas and water are present in the input deck. The keyword should only be used if oil, gas and water are present in the input deck.","parameters":[{"index":1,"name":"SOIL","description":"A columnar vector of real monotonically increasing down the column values starting from zero and terminating at one, that defines the oil or the hydrocarbon solvent saturation. The final entry should be at the connate water saturation, that is 1- Swc.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":["1","1","1"]},{"index":3,"name":"KROW","description":"A columnar vector of real values that are either equal or increasing down the column and that are greater than or equal to zero and less than or equal to one that defines the oil relative permeability with respect to oil and water saturation. The first value in the column should be zero.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":4,"name":"KROG","description":"A columnar vector of real values that are either equal or increasing down the column and that are greater than or equal to zero and less than or equal to one that defines the oil relative permeability with respect to oil, gas and connate water saturation. The first value in the column should be zero.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- OIL RELATIVE PERMEABILITY TABLES (SOF3)\n--\nSOF3\n-- SOIL KRO KROG\n-- FRAC FRAC FRAC\n-- -------- -------- --------\n0.00 0.000000 0.00000\n0.05 1.197e-5 0.00000\n0.10 0.000191 0.00000\n0.15 0.000969 0.00000\n0.20 0.003065 0.00000\n0.25 0.007483 0.00000\n0.30 0.015517 0.05932\n0.35 0.028747 0.13158\n0.40 0.049041 0.21082\n0.45 0.078555 0.29960\n0.50 0.119730 0.40095\n0.55 0.175297 0.51818\n0.60 0.248272 0.65476\n0.65 0.341961 0.81420\n0.70 0.459956 1.00000\n0.75 0.606134 1.00000\n0.80 0.784664 1.00000\n0.85 1.000000 1.00000 / TABLE NO. 1\n-- -------- -------- --------\n0.00 0.000000 0.00000\n0.05 1.197e-5 0.00000\n0.10 0.000191 0.00000\n0.15 0.000969 0.00000\n0.20 0.003065 0.00000\n0.25 0.007483 0.00000\n0.30 0.015517 0.05932\n0.35 0.028747 0.13158\n0.40 0.049041 0.21082\n0.45 0.078555 0.29960\n0.50 0.119730 0.40095\n0.55 0.175297 0.51818\n0.60 0.248272 0.65476\n0.65 0.341961 0.81420\n0.70 0.459956 1.00000\n0.75 0.606134 1.00000\n0.80 0.784664 1.00000\n0.85 1.000000 1.00000 / TABLE NO. 2\nThe example defines two SOF3 tables for when oil, gas and water are present in the input deck.","size_kind":"fixed","variadic_record":true},"SOF32D":{"name":"SOF32D","sections":["PROPS"],"supported":false,"summary":"The SOF32D keyword defines the three phase oil relative permeability versus water and gas saturation tables for when oil, gas and water are present in the input deck. The keyword should only be used if oil, gas and water are present in the input deck. Normally the simulator calculates the three-phase oil relative permeabilities based on the entered two phase tables of water-oil and gas-oil, combined with the STONE1 and STONE2 keywords in the PROPS section that determine the method used to generate the thee phase oil relative permeability curves. SOF32D allows for the direct input of the three phase tables, as such the STONE1 and STONE2 keywords should not be entered if SOF32D is used in the input deck.","parameters":[{"index":1,"name":"SWAT","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1","record":1},{"index":1,"name":"SGAS","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1","record":2},{"index":2,"name":"KRO","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1","record":2}],"example":"","records_meta":[{},{"expected_columns":2}],"size_kind":"list"},"SOGCR":{"name":"SOGCR","sections":["PROPS"],"supported":null,"summary":"SOGCR defines the critical oil saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE keyword in the RUNSPEC section. The critical oil saturation with respect to gas is defined as the maximum oil saturation for which the oil relative permeability is zero in a two-phase gas-oil relative permeability table. The keyword can be used with all grid types.","parameters":[{"index":1,"name":"SOGCR","description":"SOGCR is an array of real numbers assigning the critical oil saturation with respect to gas values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.30 dimensionless","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT SOGCR DATA FOR ALL CELLS\n-- (FOR NX x NY x NZ = 300)\n--\nSOGCR\n300*0.200 /\nThe above example defines a constant critical gas saturation of 0.20 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"SOMGAS":{"name":"SOMGAS","sections":["PROPS"],"supported":false,"summary":"This keyword defines the minimum oil saturation as a function of gas saturation for Stone’s242\n Stone, H. L. “Probability Model for Estimating Three-Phase Relative Permeability,” paper SPE 2116, Journal of Canadian Petroleum Technology (1973) 22, No. 2, 214-218. first three phase oil relative permeability model as modified by Aziz and Settari243\n Aziz, K. and Settari, A. Petroleum Reservoir Simulation, London, UK, Applied Science Publishers (1979), page 398.. If the STONE1 and STONE2 keywords are not present in the input deck then the default three phase oil relative permeability model is employed. The SOMGAS and STONE1 keywords should only be used in three phase runs containing the oil, gas and water phases. The keyword is optional.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["1","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"SOMWAT":{"name":"SOMWAT","sections":["PROPS"],"supported":false,"summary":"This keyword defines the minimum oil saturation as a function of water saturation for Stone’s244\n Stone, H. L. “Probability Model for Estimating Three-Phase Relative Permeability,” paper SPE 2116, Journal of Canadian Petroleum Technology (1973) 22, No. 2, 214-218. first three phase oil relative permeability model as modified by Aziz and Settari245\n Aziz, K. and Settari, A. Petroleum Reservoir Simulation, London, UK, Applied Science Publishers (1979), page 398.. If the STONE1 and STONE2 keywords are not present in the input deck then the default three phase oil relative permeability model is employed. The SOMWAT and STONE1 keywords should only be used in three phase runs containing the oil, gas and water phases. The keyword is optional.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["1","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"SORWMIS":{"name":"SORWMIS","sections":["PROPS"],"supported":null,"summary":"SORWMIS defines the dependency between the miscible residual oil saturation and the water saturation, for when the MISCIBLE keyword in the RUNSPEC section has been activated. The keyword can only be used with the MISCIBLE option and for when the oil, water and gas phases are active in the model.","parameters":[{"index":1,"name":"SWAT","description":"A columnar vector of real monotonically increasing down the column values starting from zero and terminating at one, that defines the water saturation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":["1","1"]},{"index":2,"name":"SORMIS","description":"A columnar vector of real equal or increasing down the column values that are greater than or equal to zero and less than one, that define the corresponding miscible residual oil saturation for the corresponding water saturation SWAT.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- MISCIBLE RESIDUAL OIL VERSUS WATER SATURATION TABLE\n--\nSORWMIS\n-- SWAT SORWMIS\n-- FRAC FRAC\n-- ------- --------\n0.0000 0.0000\n0.2000 0.0000\n1.0000 0.0000 / TABLE NO. 01\n-- SWAT SORWMIS\n-- FRAC FRAC\n-- ------- --------\n0.0000 0.0000\n0.3000 0.1000\n0.7500 0.1500 / TABLE NO. 02\nThe above example defines two miscible residual oil versus water saturation tables assuming NTMISC equals two and NSMISC is greater than or equal to three on the MISCIBLE keyword in the RUNSPEC section.","size_kind":"fixed","variadic_record":true},"SOWCR":{"name":"SOWCR","sections":["PROPS"],"supported":null,"summary":"SOWCR defines the critical oil saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE keyword in the RUNSPEC section. The critical oil saturation with respect to water is defined as the maximum oil saturation for which the oil relative permeability is zero in a two-phase oil-water relative permeability table.","parameters":[{"index":1,"name":"SOWCR","description":"SOWCR is an array of real numbers assigning the critical oil saturation with respect to water values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.30","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT SOWCR DATA FOR ALL CELLS\n– (FOR NX x NY x NZ = 300)\n--\nSOWCR\n300*0.200 /\nThe above example defines a constant critical oil saturation of 0.20 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"SPECHEAT":{"name":"SPECHEAT","sections":["PROPS"],"supported":null,"summary":"SPECHEAT defines the specific heat of the oil, water and gas phases for various PVT regions in the model for when the THERMAL option has been activated in the RUNSPEC section. The number of SPECHEAT vector data sets is defined by the NTPVT parameter on the TABDIMS keyword in the RUNSPEC section and the allocation of the SPECHEAT data sets to different grid blocks in the model is done via the PVTNUM keyword in the REGIONS section.","parameters":[{"index":1,"name":"TEMP","description":"A columnar vector of real monotonically increasing down the column values that define the temperature for the corresponding oil, water and gas specific heat values.","units":{"field":"oF","metric":"oC","laboratory":"oC"},"default":"None","value_type":"DOUBLE","dimension":["Temperature","Energy/Mass*AbsoluteTemperature","Energy/Mass*AbsoluteTemperature","Energy/Mass*AbsoluteTemperature"]},{"index":2,"name":"OILSHEAT","description":"OILSHEAT is a columnar vector of positive real numbers defining the specific heat of oil at the corresponding temperature, TEMP.","units":{"field":"Btu/lb/oR","metric":"kJ/kg/K","laboratory":"J/gm/K"},"default":"None"},{"index":3,"name":"WATSHEAT","description":"WATSHEAT is a columnar vector of positive real numbers defining the specific heat of water at the corresponding temperature, TEMP.","units":{"field":"Btu/lb/oR","metric":"kJ/kg/K","laboratory":"J/gm/K"},"default":"None"},{"index":4,"name":"GASSHEAT","description":"GASHEAT is a columnar vector of positive real numbers defining the specific heat of gas at the corresponding temperature, TEMP.","units":{"field":"Btu/lb/oR","metric":"kJ/kg/K","laboratory":"J/gm/K"},"default":"None"}],"example":"The example below defines three fluid phases specific heat versus temperature tables assuming NTPVT equals three and NPPVT is greater than or equal to two on the TABDIMS keyword in the RUNSPEC section.\n--\n-- SPECIFIC HEAT OF OIL, WATER AND GAS TABLE\n--\nSPECHEAT\n-- TEMP SPECHEAT SPECHEAT SPECHEAT\n-- OIL WATER GAS\n-- ------- -------- -------- --------\n0.000 0.5000 1.5000 0.5000\n250.000 0.5000 1.5000 0.5000 / TABLE NO. 01\n-- TEMP SPECHEAT SPECHEAT SPECHEAT\n-- OIL WATER GAS\n-- ------- -------- -------- --------\n0.000 0.5500 1.5000 0.5000\n260.000 0.5500 1.5000 0.5000 / TABLE NO. 02\n-- TEMP SPECHEAT SPECHEAT SPECHEAT\n-- OIL WATER GAS\n-- ------- -------- -------- --------\n0.000 0.5500 1.5500 0.5000\n270.000 0.6000 1.5500 0.5000 / TABLE NO. 03\nThere is no terminating “/” for this keyword.","size_kind":"fixed","variadic_record":true},"SPECROCK":{"name":"SPECROCK","sections":["PROPS"],"supported":null,"summary":"SPECROCK defines the specific heat of the reservoir rock for various PVT regions in the model for when the THERMAL option has been activated in the RUNSPEC section. The number of SPECROCK vector data sets is defined by the NTSFUN parameter on the TABDIMS keyword in the RUNSPEC section and the allocation of the SPECROCK data sets to different grid blocks in the model is done via the SATNUM keyword in the REGIONS section.","parameters":[{"index":1,"name":"TEMP","description":"A columnar vector of real monotonically increasing down the column values that define the temperature for the corresponding rock specific heat values.","units":{"field":"oF","metric":"oC","laboratory":"oC"},"default":"None","value_type":"DOUBLE","dimension":["Temperature","Energy/Length*Length*Length*AbsoluteTemperature"]},{"index":2,"name":"ROCKHEAT","description":"ROCKHEAT is a columnar vector of positive real numbers defining the specific heat of the rock at the corresponding temperature, TEMP.","units":{"field":"Btu/ft3/oR","metric":"kJ/m3/K","laboratory":"J/cc/K"},"default":"None"}],"example":"The example below defines three rock specific heat versus temperature tables assuming NTSFUN equals three and NSSFUN is greater than or equal to two on the TABDIMS keyword in the RUNSPEC section.\n--\n-- SPECIFIC HEAT OF ROCK\n--\nSPECROCK\n-- TEMP SPECHEAT\n-- ROCK\n-- ------- --------\n0.000 20.000\n250.000 20.000 / TABLE NO. 01\n-- ------- --------\n0.000 21.000\n260.000 21.000 / TABLE NO. 02\n-- ------- --------\n0.000 23.000\n270.000 23.000 / TABLE NO. 03\nThere is no terminating “/” for this keyword.","size_kind":"fixed","variadic_record":true},"SSFN":{"name":"SSFN","sections":["PROPS"],"supported":null,"summary":"The SSFN keyword defines the miscible normalized relative permeability tables for when the SOLVENT option has been activated in the RUNSPEC section using the respective keyword. The SOLVENT keyword results in a four component model (oil, water and gas, plus a solvent). This keyword should only be used if the SOLVENT option has been activated.","parameters":[{"index":1,"name":"SGAS","description":"A columnar vector of real monotonically increasing down the column values starting from zero and terminating at one, that defines the gas plus solvent saturation ration which is defined as either: [S sub g over { left(S sub g ~+~ S sub s right) }]or or [S sub s over { left(S sub g ~+~ S sub s right) }] Where Sg is the gas saturation and Ss is the solvent saturation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":["1","1","1"]},{"index":2,"name":"KRGt","description":"A columnar vector of real values that are either equal or increasing down the column and that are greater than or equal to zero and less than or equal to one that defines the gas relative permeability. The resulting gas relative permeability is calculated from: [k sub rg ~=~ k sub rgt left( S sub g ~+~ S sub s Right) {k sub rg} sup t] where krgt is the data in this column and krgt is the gas relative permeability from the SGFN keyword.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":3,"name":"KRSt","description":"A columnar vector of real values that are either equal or increasing down the column and that are greater than or equal to zero and less than or equal to one that defines the solvent relative permeability. The resulting solvent relative permeability is calculated from: [k sub rs ~=~ k sub rgt left( S sub g ~+~ S sub s Right) {k sub rs} sup t] where krSt is the data in this column and krgt is the gas relative permeability from the SGFN keyword.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- SOLVENT RELATIVE PERMEABILITY TABLES\n--\nSSFN\n-- SGAS KRGT KRST\n-- FRAC\n-- -------- -------- --------\n0.0000 0.0000 0.0000\n1.0000 1.0000 1.0000 / TABLE NO. 01\n-- -------- -------- --------\n0.0000 0.0000 0.0000\n0.2000 0.2000 0.3000\n0.4000 0.3000 0.5000\n0.6000 0.4000 0.7000\n0.8000 0.5000 0.7500\n1.0000 1.0000 1.0000 / TABLE NO. 02\nThe above example defines two SSFN tables for use with the SOLVENT option.","size_kind":"fixed","variadic_record":true},"SSGCR":{"name":"SSGCR","sections":["PROPS"],"supported":false,"summary":"SSGCR defines the surfactant critical gas saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE keyword and the surfactant phase has been activated by the SURFACT keyword in the RUNSPEC section. The critical gas saturation is defined as the maximum gas saturation for which the gas relative permeability is zero in a two-phase relative permeability table. SSGCR is used to scale the surfactant oil relative permeability to gas data.","parameters":[{"index":1,"name":"SSGCR","description":"SSGCR is an array of real numbers assigning the surfactant critical gas saturation values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.03","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT SSGCR DATA FOR ALL CELLS\n-- (FOR NX x NY x NZ = 300)\n--\nSSGCR\n300*0.050 /\nThe above example defines a constant surfactant critical oil saturation with respect to gas of 0.05 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"SSGL":{"name":"SSGL","sections":["PROPS"],"supported":false,"summary":"SSGL defines the surfactant connate gas saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE keyword and the surfactant phase has been activated by the SURFACT keyword in the RUNSPEC section. The connate gas saturation is defined as the minimum gas saturation in a two-phase gas relative permeability table. SSGL is used to scale the surfactant oil and water relative permeability data.","parameters":[{"index":1,"name":"SSGL","description":"SSGL is an array of real numbers assigning the surfactant connate gas saturation values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.03","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT SSGL DATA FOR ALL CELLS\n-- (FOR NX x NY x NZ = 300)\n--\nSSGL\n300*0.030 /\nThe above example defines a constant surfactant connate gas saturation of 0.03 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"SSOGCR":{"name":"SSOGCR","sections":["PROPS"],"supported":false,"summary":"SSOGCR defines the surfactant critical oil saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE keyword and the surfactant phase has been activated by the SURFACT keyword in the RUNSPEC section. The critical oil saturation with respect to gas is defined as the maximum oil saturation for which the oil relative permeability is zero in a two-phase gas-oil relative permeability table. SSOGCR scales the surfactant oil relative permeability to gas data.","parameters":[{"index":1,"name":"SSOGCR","description":"SSOGCR is an array of real numbers assigning the surfactant critical oil saturation with respect to gas values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.30 dimensionless","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT SSOGCR DATA FOR ALL CELLS\n-- (FOR NX x NY x NZ = 300)\n--\nSSOGCR\n300*0.200 /\nThe above example defines a surfactant constant critical oil saturation with respect to gas of 0.20 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"SSOWCR":{"name":"SSOWCR","sections":["PROPS"],"supported":false,"summary":"SSOWCR defines the surfactant critical oil saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE keyword and the surfactant phase has been activated by the SURFACT keyword in the RUNSPEC section. The critical oil saturation with respect to water is defined as the maximum oil saturation for which the oil relative permeability is zero in a two-phase oil-water relative permeability table. SSOWCR scales the surfactant oil relative permeability to water data.","parameters":[{"index":1,"name":"SSOWCR","description":"SSOWCR is an array of real numbers assigning the surfactant critical oil saturation with respect to water values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.30","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT SSOWCR DATA FOR ALL CELLS\n-- (FOR NX x NY x NZ = 300)\n--\nSSOWCR\n300*0.200 /\nThe above example defines a constant critical oil saturation of 0.20 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"SSWCR":{"name":"SSWCR","sections":["PROPS"],"supported":false,"summary":"SSWCR defines the surfactant critical water saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE keyword and the surfactant phase has been activated by the SURFACT keyword in the RUNSPEC section. The critical water saturation is defined as the maximum water saturation for which the water relative permeability is zero in a two-phase relative permeability table. SSWCR scales the surfactant water relative permeability data.","parameters":[{"index":1,"name":"SSWCR","description":"SSWCR is an array of real numbers assigning the surfactant critical water saturation values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.20","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT SSWCR DATA FOR ALL CELLS\n-- (FOR NX x NY x NZ = 300)\n--\nSSWCR\n300*0.200 /\nThe above example defines a constant surfactant critical water saturation of 0.20 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"SSWL":{"name":"SSWL","sections":["PROPS"],"supported":false,"summary":"SSWL defines the surfactant connate water saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE keyword and the surfactant phase has been activated by the SURFACT keyword in the RUNSPEC section. The connate water saturation is defined as the minimum water saturation in a two-phase water relative permeability table. SSWL scales the surfactant oil relative permeability to water and gas data.","parameters":[{"index":1,"name":"SSWL","description":"SSWL is an array of real numbers assigning the connate water saturation values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.15","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT SSWL DATA FOR ALL CELLS\n-- (FOR NX x NY x NZ = 300)\n--\nSSWL\n300*0.150 /\nThe above example defines a constant surfactant connate water saturation of 0.15 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"SSWU":{"name":"SSWU","sections":["PROPS"],"supported":false,"summary":"SSWU defines the surfactant maximum water saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE keyword and the surfactant phase has been activated by the SURFACT keyword in the RUNSPEC section. The maximum water saturation is defined as the maximum water saturation in a two-phase water relative permeability table. SSWU scales the surfactant water relative permeability data.","parameters":[{"index":1,"name":"SSWU","description":"SSWU is an array of real numbers assigning the surfactant maximum water saturation values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.70","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT SSWU DATA FOR ALL CELLS\n-- (FOR NX x NY x NZ = 300)\n--\nSSWU\n300*0.700 /\nThe above example defines a constant surfactant connate gas saturation of 0.70 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"STOG":{"name":"STOG","sections":["PROPS"],"supported":false,"summary":"The STOG keyword defines capillary pressure oil-gas surface tension versus pressure tables used in adjusting the pressure independent capillary pressure vectors in the SGFN, SGOF or SLGOF saturation tables, entered by their respective keywords in the PROPS section. The SATOPTS keyword in the RUNSPEC section should state the SURFTENS character string to activate the Capillary Pressure Surface Tension Pressure Dependency option. If the STOG keyword is not supplied then no capillary pressure surface tension pressure scaling will occur and the capillary pressure values on the SGFN, SGOF or SLGOF saturation tables will be used directly.","parameters":[],"example":"","size_kind":"fixed"},"STONE":{"name":"STONE","sections":["PROPS"],"supported":null,"summary":"This keyword is an alias for STONE2 keyword that activates Stone’s246\n Stone, H. L. “Estimation of Three-Phase Relative Permeability and Residual Oil Data,” Journal of Canadian Petroleum Technology (1973) 12, No. 4, 53-61. second three phase oil relative permeability model as modified by Aziz and Settari247\n Aziz, K. and Settari, A. Petroleum Reservoir Simulation, London, UK, Applied Science Publishers (1979), page 398.. If the STONE, STONE1 and STONE2 keywords are not present in the input deck then the default three phase oil relative permeability model is employed. The STONE keyword should only be used in three phase runs containing the oil, gas and water phases.","parameters":[],"example":"--\n-- ACTIVATE STONE’S SECOND THREE PHASE RELATIVE PERMEABILITY MODEL\n--\nSTONE\nThe above example switches on the Modified Stone three phase relative permeability model.","size_kind":"none","size_count":0},"STONE1":{"name":"STONE1","sections":["PROPS"],"supported":null,"summary":"This keyword activates Stone’s248\n Stone, H. L. “Probability Model for Estimating Three-Phase Relative Permeability,” paper SPE 2116, Journal of Canadian Petroleum Technology (1973) 22, No. 2, 214-218. first three phase oil relative permeability model as modified by Aziz and Settari249\n Aziz, K. and Settari, A. Petroleum Reservoir Simulation, London, UK, Applied Science Publishers (1979), page 398.. If the STONE1 and STONE2 keywords are not present in the input deck then the default three phase oil relative permeability model is employed. The STONE1 keyword should only be used in three phase runs containing the oil, gas and water phases.","parameters":[],"example":"--\n-- ACTIVATE STONE’S FIRST THREE PHASE RELATIVE PERMEABILITY MODEL\n--\nSTONE1\nThe above example switches on the Modified Stone three phase relative permeability model.","size_kind":"none","size_count":0},"STONE1EX":{"name":"STONE1EX","sections":["PROPS"],"supported":null,"summary":"This keyword defines the exponent used in Stone’s250\n Stone, H. L. “Probability Model for Estimating Three-Phase Relative Permeability,” paper SPE 2116, Journal of Canadian Petroleum Technology (1973) 22, No. 2, 214-218. first three phase oil relative permeability model as modified by Aziz and Settari251\n Aziz, K. and Settari, A. Petroleum Reservoir Simulation, London, UK, Applied Science Publishers (1979), page 398.. The STONE1EX keyword should only be used in three phase runs containing the oil, gas and water phases and when the STONE1 keyword in the PROPS section has been used to activate Stone’s first three phase oil relative permeability model.","parameters":[{"index":1,"name":"STONEPAR1","description":"A real positive value that defines the exponent to be used in the Modified Stone first three phase oil relative permeability model.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":"1"}],"example":"Given NTSFUN equals five on the TABDIMS keyword in the RUNSPEC section, then:\n--\n-- DEFINE STONE'S FIRST THREE PHASE RELATIVE PERMEABILITY MODEL PARAMETER\n--\nSTONE1EX\n1.000 / SATURATION TABLE NO. 01\n1.000 / SATURATION TABLE NO. 02\n2.000 / SATURATION TABLE NO. 03\n1.000 / SATURATION TABLE NO. 04\n3.000 / SATURATION TABLE NO. 05\nDefines the exponents to be used in the Modified Stone first three phase oil relative permeability model, for each of the five saturation tables.","expected_columns":1,"size_kind":"fixed"},"STONE2":{"name":"STONE2","sections":["PROPS"],"supported":null,"summary":"This keyword activates Stone’s252\n Stone, H. L. “Estimation of Three-Phase Relative Permeability and Residual Oil Data,” Journal of Canadian Petroleum Technology (1973) 12, No. 4, 53-61. second three phase oil relative permeability model as modified by Aziz and Settari253\n Aziz, K. and Settari, A. Petroleum Reservoir Simulation, London, UK, Applied Science Publishers (1979), page 398.. If the STONE, STONE1 and STONE2 keywords are not present in the input deck then the default three phase oil relative permeability model is employed. The STONE2 keyword should only be used in three phase runs containing the oil, gas and water phases.","parameters":[],"example":"--\n-- ACTIVATE STONE’S SECOND THREE PHASE RELATIVE PERMEABILITY MODEL\n--\nSTONE2\nThe above example switches on the Modified Stone three phase relative permeability model.","size_kind":"none","size_count":0},"STOW":{"name":"STOW","sections":["PROPS"],"supported":false,"summary":"The STOW keyword defines capillary pressure oil-water surface tension versus pressure tables used in adjusting the pressure independent capillary pressure vectors in the SWFN or SWOF saturation tables, entered by their respective keywords in the PROPS section. The SATOPTS keyword in the RUNSPEC section should state the SURFTENS character string to activate the Capillary Pressure Surface Tension Pressure Dependency option. If the STOW keyword is not supplied then no capillary pressure surface tension pressure scaling will occur and the capillary pressure values on the SWFN or SWOF saturation tables will be used directly.","parameters":[],"example":"","size_kind":"fixed"},"STWG":{"name":"STWG","sections":["PROPS"],"supported":false,"summary":"The STWG keyword defines capillary pressure water-gas surface tension versus pressure tables for use with multi-segment wells. This facility has not been incorporated in OPM Flow’s multi-segment well implementation. Note that STWG is not required for Capillary Pressure Surface Tension Pressure Dependency option.","parameters":[],"example":"","size_kind":"fixed"},"SURFADDW":{"name":"SURFADDW","sections":["PROPS"],"supported":false,"summary":"SURFADDW defines tables of surfactant adsorbed concentration versus wettability fraction for when the SURFACTW keyword in the RUNSPEC section as been declared to activate the surfactant phase with changing wettability. The tables consists of columnar vectors of adsorbed surfactant concentration versus a wettability fraction that indicates the fraction of phase wettability. Here, a wettability fraction of zero indicates a 100% water wet rock resulting in the SURFWNUM allocated saturation tables being used, and a value of one meaning 100% oil wet rock, with the SATNUM allocated saturations tables being employed. Both the SURFWNUM and SATNUM keywords are in the REGIONS section.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["1","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"SURFADS":{"name":"SURFADS","sections":["PROPS"],"supported":false,"summary":"The SURFADS keyword defines the rock surfactant adsorption tables for when the surfactant option has been activated by the SURFACT keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"SURCON","description":"A columnar vector of real monotonically increasing down the column values that defines the surfactant concentration in the solution surrounding the rock. The first entry should be zero to define a no surfactant concentration.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None","value_type":"DOUBLE","dimension":["Concentration","1"]},{"index":2,"name":"SURRATIO","description":"A columnar vector of real increasing down the column values that defines the mass of adsorbed surfactant per unit mass of rock of the saturated concentration of surfactant adsorbed by the rock. The first entry should be zero to define a zero ratio of surfactant concentration.","units":{"field":"lb/lb","metric":"kg/kg","laboratory":"gm/gm"},"default":"None"}],"example":"--\n-- SURFACTANT ROCK ADSORPTION TABLE\n--\nSURFADS\n-- SURF SURF\n-- SURCON SURRATIO\n-- ------- --------\n0.0 0.00000\n2.0 0.00003\n4.0 0.00005\n6.0 0.00007\n8.0 0.00009\n10.0 0.00011\n12.0 0.00012\n14.0 0.00015 / TABLE NO. 01\n-- SURF SURF\n-- SURCON SURRATIO\n-- ------- --------\n0.0 0.00000\n3.0 0.00004\n5.0 0.00006\n7.0 0.00008\n8.0 0.00009\n10.0 0.00011 / TABLE NO. 02\nThe above example defines two surfactant rock adsorption tables assuming NTSFUN equals two and NSSFUN is greater than or equal to eight on the TABDIMS keyword in the RUNSPEC section.\nThere is no terminating “/” for this keyword.","size_kind":"fixed","variadic_record":true},"SURFCAPD":{"name":"SURFCAPD","sections":["PROPS"],"supported":false,"summary":"The SURFCAPD keyword defines the relationship between the log of the capillary number and the level of miscibility, for when the Surfactant option has been activated by the SURFACT keyword in the RUNSPEC section. A value of zero for the level of miscibility means fully immiscible conditions and consequently a value of one implies fully miscible conditions.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["1","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"SURFESAL":{"name":"SURFESAL","sections":["PROPS"],"supported":false,"summary":"This keyword, SURFESAL, defines the surfactant effective salinity coefficient as well as enabling the effective salinity calculation for surfactant adsorption. The keyword should only be used if the BRINE keyword has been declared to activate the brine phase, the ECLMC keyword to enable the Multi-Component Brine model, and the SURFACT keyword has been used to activate the surfact phase. All three keywords are in the RUNSPEC section.","parameters":[{"index":1,"name":"COEFF","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"}],"example":"","expected_columns":1,"size_kind":"fixed"},"SURFROCK":{"name":"SURFROCK","sections":["PROPS"],"supported":false,"summary":"The SURFROCK keyword defines rock properties for when the Surfactant option has been activated by the SURFACTANT keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"ADINDX","description":"A positive integer of 1 or 2 that defines the surfactant desorption option. then surfactant desorption may occur by retracing the surfactant adsorption isotherm when the local surfactant concentration in the solution decreases. then no surfactant desorption may occur.","units":{"field":"dimensionless 1","metric":"dimensionless 1","laboratory":"dimensionless 1"},"default":"Defined","value_type":"INT"},{"index":2,"name":"DENSITY","description":"A real value that defines the rock in-situ density, that is at reservoir conditions.","units":{"field":"lb/rtb","metric":"kg/rm3","laboratory":"gm/rcc"},"default":"None","value_type":"DOUBLE","dimension":"Mass/ReservoirVolume"}],"example":"--\n-- SURFACTANT-ROCK PROPERTIES\n--\nSURFROCK\n-- DESORP INSITU\n-- OPTN DENSITY\n-- ------ -------\n1 1800.0 / TABLE NO. 01\n2 1980.0 / TABLE NO. 02\n1 2005.0 / TABLE NO. 03\nThe above example defines three surfactant-rock tables, based on the NTSFUN variable on the TABDIMS keyword in the RUNSPEC section being equal to three.\nThere is no terminating “/” for this keyword.","expected_columns":2,"size_kind":"fixed"},"SURFST":{"name":"SURFST","sections":["PROPS"],"supported":false,"summary":"The SURFST keyword defines surfactant water-oil surface tension versus surfactant concentration in the water phase tables, used in adjusting the pressure independent capillary pressure vectors in the SWFN or SWOF saturation tables, entered by their respective keywords in the PROPS section. SURFST is also used to adjust the relative permeability curves on the aforementioned tables via the capillary number. The Surfactant option must have been activated by the SURFACTANT keyword in the RUNSPEC section to use this keyword and either this keyword or the SURFSTES keyword, also in the PROPS section, is obligatory in this case.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","size_kind":"fixed","variadic_record":true},"SURFSTES":{"name":"SURFSTES","sections":["PROPS"],"supported":false,"summary":"The SURFSTES keyword defines surfactant water-oil surface tension versus surfactant concentration in the water phase tables, used in adjusting the pressure independent capillary pressure vectors in the SWFN or SWOF saturation tables, entered by their respective keywords in the PROPS section. SURFSTES is also used to adjust the relative permeability curves on the aforementioned tables via the capillary number. The Surfactant option must have been activated by the SURFACTANT keyword in the RUNSPEC section to use this keyword and either this keyword or the SURFST keyword, also in the PROPS section, is obligatory in this case. In addition, the BRINE keyword in the RUNSPEC section must be activated and the ESSNODE keyword in the PROPS section must be used to define the salt concentration or the effective salinity.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","size_kind":"fixed","variadic_record":true},"SURFVISC":{"name":"SURFVISC","sections":["PROPS"],"supported":false,"summary":"SURFSVISC defines the surfactant viscosity relationship of solution water viscosity with respect to increasing surfactant concentration within a grid block. The surfactant option must be activated by the SURFACT keyword in the RUNSPEC section in order to use this keyword.","parameters":[{"index":1,"name":"SURFCON","description":"A columnar vector of real monotonically increasing down the column values that defines the surfactant concentration in the solution surrounding the rock. The first entry should be zero to define a no surfactant concentration.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None","value_type":"DOUBLE","dimension":["Concentration","Viscosity"]},{"index":2,"name":"SURFVISC","description":"A columnar vector of real positive values that defines the solution water viscosity of the solution for the given SURFCON entry at the reference pressure value, PRES, entered on the PVTW keyword in the PROPS section.","units":{"field":"cP","metric":"cP","laboratory":"cP"},"default":"None"}],"example":"--\n-- SURFACTANT SOLUTION WATER VISCOSITY TABLES\n--\nSURFVISC\n-- SURF VISCOSITY\n-- SURFCON SURFVISC\n-- -------- -----------\n0.0000 0.3500\n0.0100 0.3900\n0.0200 0.4200\n0.0300 0.4300 / TABLE NO. 01\n-- SURF VISCOSITY\n-- SURFCON VISFAC\n-- -------- ---------\n0.0000 1.000\n0.0003 10.000\n0.0005 20.000\n0.0007 40.000\n0.0009 45.000\n0.0011 55.000 / TABLE NO. 02\nThe example defines two surfactant viscosity scaling factor tables, based on the NTPVT variable on the TABDIMS keyword in the RUNSPEC section being equal to two and NPPVT variable on the same keyword being greater than or equal to six.","size_kind":"fixed","variadic_record":true},"SWATINIT":{"name":"SWATINIT","sections":["PROPS"],"supported":null,"summary":"SWATINIT defines the initial water saturation for all the cells in the model via an array. The keyword can be used with all grid types. SWATINIT is used to initialize the model by setting each grid block’s initial water saturation (“Sw”). If the array is present in the input deck, then OPM Flow will re-scale the water-oil capillary pressure curves entered via the SWFN saturation functions in the PROPS section, so that the resulting initialized Sw matches the values in the SWATINIT array.","parameters":[{"index":1,"name":"SWATINIT","description":"SWATINIT is an array of real positive numbers that are greater than or equal to zero and less than or equal to one, that define the initial water saturation values to each cell in the model. Repeat counts may be used, for example 3000*0.15","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK INITIAL SW DATA FOR ALL CELLS\n-- (BASED ON NX x NY x NZ = 300)\n--\nSWATINIT\n300*0.300 /\nThe above example defines a constant initial water saturation of 0.300 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"SWCR":{"name":"SWCR","sections":["PROPS"],"supported":null,"summary":"SWCR defines the critical water saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE keyword in the RUNSPEC section. The critical water saturation is defined as the maximum water saturation for which the water relative permeability is zero in a two-phase relative permeability table.","parameters":[{"index":1,"name":"SWCR","description":"SWCR is an array of real numbers assigning the critical water saturation values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.20","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT SWCR DATA FOR ALL CELLS\n-- (FOR NX x NY x NZ = 300)\n--\nSWCR\n300*0.200 /\nThe above example defines a constant critical water saturation of 0.20 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"SWF32D":{"name":"SWF32D","sections":["PROPS"],"supported":false,"summary":"The SWF32D keyword defines the three phase water relative permeability versus oil and gas saturation tables for when oil, gas and water are present in the input deck. The keyword should only be used if oil, gas and water are present in the input deck. Normally the simulator calculates the three-phase oil relative permeabilities based on the entered two phase tables of water-oil and gas-oil, combined with the STONE1 and STONE2 keywords in the PROPS section that determine the method used to generate the thee phase water relative permeability curves. SWF32D allows for the direct input of the three phase tables, as such the STONE1 and STONE2 keywords should not be entered if SWF32D is used in the input deck.","parameters":[{"index":1,"name":"SOIL","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1","record":1},{"index":1,"name":"SGAS","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1","record":2},{"index":2,"name":"KRW","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1","record":2}],"example":"","records_meta":[{},{"expected_columns":2}],"size_kind":"list"},"SWFN":{"name":"SWFN","sections":["PROPS"],"supported":null,"summary":"The SWFN keyword defines the water relative permeability and water-oil capillary pressure data versus water saturation tables for when water is present in the input deck. This keyword should only be used if water is present in the run.","parameters":[{"index":1,"name":"SWAT","description":"A columnar vector of real monotonically increasing down the column values starting from zero and terminating at one, that defines the water saturation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":["1","1","Pressure"]},{"index":2,"name":"KRW","description":"A columnar vector of real values that are either equal or increasing down the column and that are greater than or equal to zero and less than or equal to one that defines the water relative permeability with respect to gas saturation. The first value in the column should be zero.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":3,"name":"PCWO","description":"A columnar vector of real values that are either equal or increasing down the column that defines the water-oil relative capillary pressure. If the SWATINIT keyword has been used to initialize the model then columnar vector has to be strictly monotonically increasing.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"None"}],"example":"--\n-- WATER RELATIVE PERMEABILITY TABLES (SWFN)\n--\nSWFN\n-- SWAT KRW PCOW\n-- FRAC FRAC PSIA\n-- -------- -------- -------\n0.15 0.00000 0.0\n0.20 6.25e-6 0.0\n0.25 0.00010 0.0\n0.30 0.00050 0.0\n0.35 0.00160 0.0\n0.40 0.00390 0.0\n0.45 0.00810 0.0\n0.50 0.01500 0.0\n0.55 0.02560 0.0\n0.60 0.04100 0.0\n0.65 0.06250 0.0\n0.70 0.09150 0.0\n0.75 0.12960 0.0\n0.80 0.17850 0.0\n0.85 0.24010 0.0\n0.90 0.31640 0.0\n0.95 0.40960 0.0\n1.00 0.52200 0.0 / TABLE NO. 1\n-- -------- -------- -------\n0.15 0.00000 0.0\n0.20 6.25e-6 0.0\n0.25 0.00010 0.0\n0.30 0.00050 0.0\n0.35 0.00160 0.0\n0.40 0.00390 0.0\n0.45 0.00810 0.0\n0.50 0.01500 0.0\n0.55 0.02560 0.0\n0.60 0.04100 0.0\n0.65 0.06250 0.0\n0.70 0.09150 0.0\n0.75 0.12960 0.0\n0.80 0.17850 0.0\n0.85 0.24010 0.0\n0.90 0.31640 0.0\n0.95 0.40960 0.0\n1.00 0.52200 0.0 / TABLE NO. 2\nThe example defines two SWFN tables for use when water is present in the run.","size_kind":"fixed","variadic_record":true},"SWL":{"name":"SWL","sections":["PROPS"],"supported":null,"summary":"SWL defines the connate water saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE keyword in the RUNSPEC section. The connate water saturation is defined as the minimum water saturation in a two-phase water relative permeability table.","parameters":[{"index":1,"name":"SWL","description":"SWL is an array of real numbers assigning the connate water saturation values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.15","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT SWL DATA FOR ALL CELLS\n-- (FOR NX x NY x NZ = 300)\n--\nSWL\n300*0.150 /\nThe above example defines a constant connate water saturation of 0.15 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"SWLPC":{"name":"SWLPC","sections":["PROPS"],"supported":null,"summary":"SWLPC defines the connate water saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE keyword in the RUNSPEC section. The connate water saturation is defined as the minimum water saturation in a two-phase water relative permeability table. The keyword only applies the scaling to the drainage capillary pressures tables, unlike the SWL keyword that applies the scaling to both the capillary pressure and relative permeability tables. The keyword can be used with all grid types.","parameters":[{"index":1,"name":"SWLPC","description":"SWLPC is an array of real numbers assigning the connate water saturation values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. If SWLPC is omitted from the input deck the values will be defaulted to those on the SWL series of keywords. If the SWL series of keywords are missing from the input deck then the values are taken from the cell allocated capillary pressure table. Repeat counts may be used, for example 30*0.03","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from SGL or from the cell allocated capillary pressure table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT SWLPC DATA FOR ALL CELLS\n-- (FOR NX x NY x NZ = 300)\n--\nSWLPC\n300*0.150 /\nThe above example defines a constant connate water saturation of 0.15 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"SWOF":{"name":"SWOF","sections":["PROPS"],"supported":null,"summary":"The SWOF keyword defines the water and oil relative permeability and water-oil capillary pressure data versus water saturation tables for when water and oil are present in the input deck. This keyword should only be used if water and oil are present in the run.","parameters":[{"index":1,"name":"SWAT","description":"A columnar vector of real monotonically increasing down the column values starting from zero and terminating at one, that defines the water saturation. The first entry is the connate water saturation Swc and the last entry should be 1.0.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":["1","1","1","Pressure"]},{"index":2,"name":"KRW","description":"A columnar vector of real values that are either equal or increasing down the column and that are greater than or equal to zero and less than or equal to one that defines the water relative permeability with respect to gas saturation. The first value in the column should be zero.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":3,"name":"KRO","description":"A columnar vector of real values that are either equal or decreasing down the column and that are greater than or equal to zero and less than or equal to one that defines the oil relative permeability with respect to oil and water saturation. When gas is active in the run, the first entry the column, that is at krow(So = 1-Swc), must be the same as the first entry in the corresponding SGOF or SLGOF table, that is at krog(Sg = 0). The first value in the column should be one.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"},{"index":4,"name":"PCWO","description":"A columnar vector of real values that are either equal or decreasing down the column that defines the water-oil relative capillary pressure. If the SWATINIT keyword has been used to initialize the model then columnar vector has to be strictly monotonically increasing.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"None"}],"example":"The following example is based on NTSFUN equals two on the TABDIMS keyword in the RUNSPEC section.\n--\n-- WATER-OIL RELATIVE PERMEABILITY TABLES (SWOF)\n--\nSWOF\n-- SWAT KRW KROW PCOW\n-- FRAC PSIA\n-- -------- -------- ------- -------\n0.200000 0.0000 0.9000 0.000000\n0.238616 0.0002 0.7664 0.000000\n0.245309 0.0004 0.7443 0.000000\n0.261989 0.0010 0.6907 0.000000\n0.303091 0.0044 0.5671 0.000000\n0.368269 0.0191 0.3962 0.000000\n0.435026 0.0519 0.2528 0.000000\n0.486387 0.0940 0.1643 0.000000\n0.550683 0.1725 0.0803 0.000000\n0.575342 0.2115 0.0559 0.000000\n0.599076 0.2542 0.0367 0.000000\n0.621294 0.2991 0.0223 0.000000\n0.642171 0.3458 0.0120 0.000000\n0.658984 0.3868 0.0061 0.000000\n0.671123 0.4183 0.0030 0.000000\n0.679268 0.4403 0.0015 0.000000\n0.684963 0.4562 0.0008 0.000000\n0.688893 0.4674 0.0004 0.000000\n0.692025 0.4765 0.0002 0.000000\n0.694641 0.4841 0.0001 0.000000\n0.696976 0.4910 0.0000 0.000000\n0.699099 0.4973 0.0000 0.000000\n0.700000 0.5000 0.0000 0.000000\n1.000000 0.9000 0.0000 0.000000 / TABLE NO. 01\n-- -------- -------- ------- -------\n0.200000 0.0000 0.9000 0.000000\n0.238616 0.0002 0.7664 0.000000\n0.245309 0.0004 0.7443 0.000000\n0.261989 0.0010 0.6907 0.000000\n0.303091 0.0044 0.5671 0.000000\n0.368269 0.0191 0.3962 0.000000\n0.435026 0.0519 0.2528 0.000000\n0.486387 0.0940 0.1643 0.000000\n0.550683 0.1725 0.0803 0.000000\n0.575342 0.2115 0.0559 0.000000\n0.599076 0.2542 0.0367 0.000000\n0.621294 0.2991 0.0223 0.000000\n0.642171 0.3458 0.0120 0.000000\n0.658984 0.3868 0.0061 0.000000\n0.671123 0.4183 0.0030 0.000000\n0.679268 0.4403 0.0015 0.000000\n0.684963 0.4562 0.0008 0.000000\n0.688893 0.4674 0.0004 0.000000\n0.692025 0.4765 0.0002 0.000000\n0.694641 0.4841 0.0001 0.000000\n0.696976 0.4910 0.0000 0.000000\n0.699099 0.4973 0.0000 0.000000\n0.700000 0.5000 0.0000 0.000000\n1.000000 0.9000 0.0000 0.000000 / TABLE NO. 01\nThe example defines two SWOF tables for use when water and oil are present in the run. In the tables the water-oil capillary pressure data has been set to zero.","size_kind":"fixed","variadic_record":true},"SWOFLET":{"name":"SWOFLET","sections":["PROPS"],"supported":null,"summary":"SWOFLET defines the relative permeability and capillary pressure parameters for the water-oil LET family of models. Both the oil and water phases should be made active in the model via the OIL and WATER keywords in the RUNSPEC section. See section 8.2.6Saturation Table Generation - LET Functionsand Lomeland et al.254\n Lomeland F., Ebeltoft E. and Thomas W.H., 2005. A New Versatile Relative Permeability Correlation. Paper SCA2005-32 presented at the International Symposium of the Society of Core Analysts held in Toronto, Canada, 21-25 August, 2005.,255\n Lomeland F. and Ebeltoft E., 2008. A New Versatile Capillary Pressure Correlation. Paper SCA2008-08 presented at the International Symposium of the Society of Core Analysts held in Abu Dhabi, UAE, 29 Oct. – 2 Nov., 2008. 256\n Lomeland F., Hasanov B., Ebeltoft E. and Berge M., 2012. A Versatile Representation of Up-scaled Relative Permeability for Field Applications. Paper SPE 154487-MS presented at the EAGE Annual Co...","parameters":[{"index":1,"name":"SWL","description":"SWL is a real positive number less than one, that defines the connate water saturation, that is the smallest water saturation in the LET function.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0,0","value_type":"DOUBLE","dimension":"1"},{"index":2,"name":"SWCR","description":"SWCR is a real positive number greater than or equal to SWL and less than one, that defines the critical water saturation, that is the largest water saturation for which the water relative permeability is zero, Swirr in equations.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0,0","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"LWAT","description":"LWAT is a real positive number that defines the LET Lower empirical parameter Lw for the water phase with the associated oil phase in the LET relative permeability equations.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0","value_type":"DOUBLE","dimension":"1"},{"index":4,"name":"EWAT","description":"EWAT is a real positive number that defines the LET Elevation empirical parameter Ew for the water phase with the associated oil phase in the LET relative permeability equations.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0","value_type":"DOUBLE","dimension":"1"},{"index":5,"name":"TWAT","description":"TWAT is a real positive number that defines the LET Top empirical parameter Tw for the water phase with the associated oil phase in the LET relative permeability equations.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0","value_type":"DOUBLE","dimension":"1"},{"index":6,"name":"KRTWAT","description":"KRTWAT is a real positive number less than one, that defines the relative permeability of water at the maximum water saturation (normally the maximum water saturation is one) Krwt in the LET relative permeability equations.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0","value_type":"DOUBLE","dimension":"1"},{"index":7,"name":"SORW","description":"SORW is a real positive number less than one that defines the residual oil saturation in an oil-water system in the LET equation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0,0","value_type":"DOUBLE","dimension":"1"},{"index":8,"name":"SOWCR","description":"SOWCR is a real positive number less than one that defines critical oil-in-water saturation, that is the largest oil saturation for which the oil relative permeability is zero in an oil-water system.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0,0","value_type":"DOUBLE","dimension":"1"},{"index":9,"name":"LOIL","description":"LOIL is a real positive number that defines the LET Lower empirical parameter Lo for the oil phase with the associated water phase in the LET relative permeability equationss","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0","value_type":"DOUBLE","dimension":"1"},{"index":10,"name":"EOIL","description":"EOIL is a real positive number that defines the LET Elevation empirical parameter Eo for the oil phase with the associated water phase in the LET relative permeability equations.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0","value_type":"DOUBLE","dimension":"1"},{"index":11,"name":"TOIL","description":"TOIL is a real positive number that defines the LET Top empirical parameter To for the oil phase with the associated water phase in the LET relative permeability equations.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0","value_type":"DOUBLE","dimension":"1"},{"index":12,"name":"KRTOIL","description":"KRTOIL is a real positive number less than or equal to one, that defines the relative permeability of oil at the residual oil saturation, Krot in the LET relative permeability equations.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0","value_type":"DOUBLE","dimension":"1"},{"index":13,"name":"LPC","description":"LPC is a real positive number that defines the water-oil LET Lower empirical parameter L in the LET capillary pressure equation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0","value_type":"DOUBLE","dimension":"1"},{"index":14,"name":"EPC","description":"EPC is a real positive number that defines the water-oil LET Elevation empirical parameter E in the LET capillary pressure equation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0","value_type":"DOUBLE","dimension":"1"},{"index":15,"name":"TPC","description":"TPC is a real positive number that defines the water-oil LET empirical parameter T in the LET capillary pressure equations.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1,0","value_type":"DOUBLE","dimension":"1"},{"index":16,"name":"PCIR","description":"PCIR is a real positive number that defines the water-oil capillary pressure at connate water saturation (SWL) in the LET capillary pressure equations.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"0,0","value_type":"DOUBLE","dimension":"Pressure"},{"index":17,"name":"PCIT","description":"PCIT is a real positive number that defines the water-oil threshold capillary pressure at the maximum water saturation in the LET capillary pressure equations.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"0,0","value_type":"DOUBLE","dimension":"Pressure"}],"example":"The following example uses the SWOFLET keyword to define two relative oi-water relative permeability tables, based on NTSFUN equals two on the TABDIMS keyword in the RUNSPEC section.\n--\n-- SWOFLET – WATER-OIL LET REL. PERMEABILITY FUNCTIONS (OPM FLOW KEYWORD)\n--\nSWOFLET\n-- SWL SWCR L-WAT E-WAT T-WAT KRT-WAT\n-- SOR SOWCR L-OIL E-OIL T-OIL KRT-OIL\n-- L-PC E-PC T-PC PCIR PCIT\n-- ------- ------ ------- ------- ------- -------\n0.00000 0.0000 1.00000 1.00000 1.00000 1.00000\n0.00000 0.0000 1.00000 1.00000 1.00000 1.00000\n1* 1* 1* 1* 1* / TABLE NO. 01\n0.00000 0.0000 1.00000 1.00000 1.00000 1.00000\n0.00000 0.0000 1.00000 1.00000 1.00000 1.00000\n1* 1* 1* 1* 1* / TABLE NO. 02\nHere the SWOFLET keyword parameters are all set to their default values.\n| Note This is an OPM Flow specific keyword and will therefore cause an error in the commercial simulator. |\n|----------------------------------------------------------------------------------------------------------|\n| Note All the LET parameters are dependent on the flooding event and flooding cycle, and thus are expected vary as such. To be clear, the values of SWCR, Lo, Lw etc. should be different for each flooding cycle. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":17,"size_kind":"fixed"},"SWU":{"name":"SWU","sections":["PROPS"],"supported":null,"summary":"SWU defines the maximum water saturation for all the cells in the model via an array when the end-point scaling option has been invoked via the ENDSCALE keyword in the RUNSPEC section. The maximum water saturation is defined as the maximum water saturation in a two-phase water relative permeability table.","parameters":[{"index":1,"name":"SWU","description":"SWU is an array of real numbers assigning the maximum water saturation values to each cell in the model. The number of entries should correspond to the NX x NY x NZ parameters on the DIMENS keyword. Repeat counts may be used, for example 30*0.70","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"Taken from cell allocated relative permeability table."}],"example":"--\n-- DEFINE GRID BLOCK END-POINT SWU DATA FOR ALL CELLS\n-- (FOR NX x NY x NZ = 300)\n--\nSWU\n300*0.700 /\nThe above example defines a constant connate gas saturation of 0.70 to all 300 cells in the model as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"TCRIT":{"name":"TCRIT","sections":["PROPS"],"supported":false,"summary":"The TCRIT keyword defines the critical temperatures for each of the compositional components active in the model and for each equation of state. The keyword should only be used if the compositional mode has been requested using the COMPS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"TCRIT","description":"A series of real numbers that define the critical temperatures for each of the compositional components active in the model.","units":{"field":"°R","metric":"K","laboratory":"K"},"default":"None","value_type":"DOUBLE","dimension":"AbsoluteTemperature"}],"example":"The following example defines the critical temperatures for each component in a single three-component equation of state model.\n--\n-- Critical Temperatures\n--\nTCRIT\n547.4412 343.0152 665.802 /\nThe following example defines the critical temperatures for each component in two three-component equation of state models.\n--\n-- Critical Temperatures\n--\nTCRIT\n547.4412 343.0152 665.802 /\n547.4412 343.0152 665.802 /","size_kind":"fixed","variadic_record":true},"TEMPNODE":{"name":"TEMPNODE","sections":["PROPS"],"supported":false,"summary":"This keyword defines the reservoir temperature table used to calculate the polymer solution viscosity when the temperature option has been activated by the TEMP keyword in the RUNSPEC section in the commercial simulator. Naturally, the polymer option must also be activated by the POLYMER keyword in the RUNSPEC section in order to use this keyword.","parameters":[{"index":1,"name":"TABLE_DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Temperature"}],"example":"","expected_columns":1,"size_kind":"fixed"},"TEMPTVD":{"name":"TEMPTVD","sections":["PROPS"],"supported":false,"summary":"TEMPTVD activates the Temperature Flux Limited Transport option in the commercial simulator, to reduce numerical dispersion for when either the TEMP or THERMAL keywords in the RUNSPEC section have been declared.","parameters":[],"example":"","size_kind":"none","size_count":0},"TEMPVD":{"name":"TEMPVD","sections":["PROPS"],"supported":true,"summary":"This keyword defines the initial reservoir temperature versus depth tables for each equilibration region. Note that the TEMPVD keyword is an alias for RTEMPVD, and that both keywords are supported by OPM Flow, in both the PROPS and SOLUTION sections, but are treated as being mutually exclusive.","parameters":[{"index":1,"name":"DEPTH","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":2,"name":"TEMP","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Temperature"}],"example":"","expected_columns":2,"size_kind":"list"},"THCO2MIX":{"name":"THCO2MIX","sections":["PROPS"],"supported":null,"summary":"The THCO2MIX keyword specifies the thermal mixing models for salt in the water phase, CO2 in the liquid phase and vaporized water in gas phase.","parameters":[{"index":1,"name":"SALTMOD","description":"A defined character string that specifies the thermal mixing model for salt in the liquid phase, and should be set to one of the following: NONE: pure water enthalpy will be used, or MICHAELIDES: account for salt concentration according to Michaelides1\n Michaelides, E. E., “Thermodynamic Properties of Geothermal Fluids”, Geothermal Resources Council, Trans. Vol. 5 (361-364), October 1981., 1981. Michaelides, E. E., “Thermodynamic Properties of Geothermal Fluids”, Geothermal Resources Council, Trans. Vol. 5 (361-364), October 1981.","units":{},"default":"MICHAELIDES","value_type":"STRING"},{"index":2,"name":"LIQMOD","description":"A defined character string that specifies the thermal mixing model for CO2 in the liquid phase, and should be set to one of the following: NONE: do not account for CO2 in brine, IDEAL: account for CO2 assuming an ideal mixture (based on mass fractions), or DUANSUN: also add the heat of dissolution for CO2 according to Dun and Sun2\n Duan, Zhenhao, and Rui Sun. \"An improved model calculating CO2 solubility in pure water and aqueous NaCl solutions from 273 to 533 K and from 0 to 2000 bar.\" Chemical geology 193.3-4 (2003): 257-271., 2003 (Fig. 6). Duan, Zhenhao, and Rui Sun. \"An improved model calculating CO2 solubility in pure water and aqueous NaCl solutions from 273 to 533 K and from 0 to 2000 bar.\" Chemical geology 193.3-4 (2003): 257-271.","units":{},"default":"DUANSUN","value_type":"STRING","options":["NONE","IDEAL","DUANSUN"]},{"index":3,"name":"GASMOD","description":"A defined character string that specifies the thermal mixing model for vaporized water in the gas phase, and should be set to one of the following: NONE: pure CO2 enthalpy will be used, or IDEAL: account for vaporized water assuming an ideal mixture (based on mass fractions).","units":{},"default":"NONE","value_type":"STRING","options":["NONE","IDEAL"]}],"example":"The following example specifies the default thermal mixing models for salt in the liquid phase, CO2 in the liquid phase, and vaporized water in the gas phase.\n--\n-- SPECIFY THERMAL MIXING MODELS\n--\n-- SALT LIQUID GAS\n-- -------- -------- --------\nTHCO2MIX\nMICHAELIDES DUANSUN NONE /","expected_columns":3,"size_kind":"fixed","size_count":1},"TLMIXPAR":{"name":"TLMIXPAR","sections":["PROPS"],"supported":null,"summary":"The TLMIXPAR keyword defines the Todd-Longstaff259\n Todd, M. and Longstaff, W. “The Development, Testing and Application of a Numerical Simulator for Predicting Miscible Flood Performance,” paper SPE 3484, Journal of Canadian Petroleum Technology (1972) 24, No. 7, 874-882. mixing parameters, for when either the miscible or solvent options have been activated by the MISCIBLE or SOLVENT keywords in the RUNSPEC section. This keyword must be present in the input deck if the MISCIBLE or SOLVENT keywords have been activated.","parameters":[{"index":1,"name":"TLMVIS","description":"A real positive value that is greater than or equal to zero and less than or equal to one, that defines the viscosity Todd-Longstaff mixing parameter for each miscibility region.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":"1"},{"index":2,"name":"TLMDEN","description":"A real positive value that is greater than or equal to zero and less than or equal to one, that defines the density Todd-Longstaff mixing parameter for each miscibility region.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"The same value as entered for TLMVIS","value_type":"DOUBLE","dimension":"1"}],"example":"--\n-- TODD-LONGSTAFF MIXING PARAMETERS\n--\nTLMIXPAR\n-- TLM TLM\n-- VISCOS DENSITY\n-- ------- --------\n0.3500 0.3500 / TABLE NO. 01\n0.2500 1* / TABLE NO. 02\n0.6500 0.7500 / TABLE NO. 03\nThe above example defines three Todd-Longstaff mixing parameter data sets, based on the NTMISC variable on the MISCIBLE keyword in the RUNSPEC section being equal to three.","expected_columns":2,"size_kind":"fixed"},"TOLCRIT":{"name":"TOLCRIT","sections":["PROPS"],"supported":null,"summary":"Critical fluid saturations are determined from the relative permeability tables, that is the last saturation in a relative permeability table where the relative permeability of a phase is set equal to zero. Since floating-point numbers (as implemented in computers) are never exact, one cannot compare floating point numbers for exact equality. Thus, this keyword defines a value below which is considered equivalent to zero in determining the critical saturation for a phase.","parameters":[{"index":1,"name":"TOLCRIT","description":"TOLCRIT is a real positive number greater than zero and less than one that defines the critical saturation tolerance used to determine the critical saturation of a fluid in the relative permeability tables. The default value of 1 x 10-6 means that relative permeabilty values less than this value will be treated as being equal to zero.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1 x 10-6","value_type":"DOUBLE","dimension":"1"}],"example":"---\n-- SET THE CRITICAL SATURATION TOLERANCE\n--\nTOLCRIT\n1.0E-6 /\nThe above example defines the critical saturation tolerance to be the default value of 1 x 10-6.","expected_columns":1,"size_kind":"fixed","size_count":1},"TPAMEPS":{"name":"TPAMEPS","sections":["PROPS"],"supported":false,"summary":"TPAMEPS defines the volumetric strain versus coal gas concentration tables, for when the Coal Bed Methane option has been activated via the COAL keyword, and PALM-MAN has been declared for the ROCKOPT variable on the ROCKCOMP keyword; both keywords are in the RUNSPEC section. The Palmer-Mansoorii260\n Palmer, I. and Mansoori, J. “How Permeability Depends on Stress and Pore Pressure in Coalbeds: A New Model,” paper SPE 52607, SPE Reservoir Evaluation & Engineering (1998) 1, No. 6, 539-544. and 261\n Clarkson, C.R., Pan, Z., Palmer, I. and Harpalani, S. \"Predicting Sorption-Induced Strain and Permeability Increase With Depletion for Coalbed-Methane Reservoirs\", SPE 114778-PA, SPE Journal (2010) 15, No. 1, 152–159.rock model is used to calculate the impact on pore volume and permeability due to rock compaction.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","size_kind":"fixed","variadic_record":true},"TPAMEPSS":{"name":"TPAMEPSS","sections":["PROPS"],"supported":false,"summary":"TPAMEPSS defines the volumetric strain versus coal solvent concentration tables, for when the Coal Bed Methane option has been activated via the COAL keyword, and PALM-MAN has been declared for the ROCKOPT variable on the ROCKCOMP keyword; both keywords are in the RUNSPEC section. The Palmer-Mansoorii262\n Palmer, I. and Mansoori, J. “How Permeability Depends on Stress and Pore Pressure in Coalbeds: A New Model,” paper SPE 52607, SPE Reservoir Evaluation & Engineering (1998) 1, No. 6, 539-544. and 263\n Clarkson, C.R., Pan, Z., Palmer, I. and Harpalani, S. \"Predicting Sorption-Induced Strain and Permeability Increase With Depletion for Coalbed-Methane Reservoirs\", SPE 114778-PA, SPE Journal (2010) 15, No. 1, 152–159.rock model is used to calculate the impact on pore volume and permeability due to rock compaction.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","size_kind":"fixed","variadic_record":true},"TRACER":{"name":"TRACER","sections":["PROPS"],"supported":null,"summary":"The TRACER keyword defines a series of passive tracers that are associated with a phase (oil, water, or gas) in the model. The maximum number of tracers for each phase are declared on the TRACERS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"NAME","description":"A three letter character string defining the tracer’s name. NAME is used by the TNUM keyword in the REGIONS section, and unlike other keywords, the TNUM keyword itself must be concatenated with the phase and the name of the tracer defined by NAME. Similarly for the TVDP keyword in the SOLUTION section, where the TVDP keyword itself must be concatenated with the either letter F (for free) or S (for solution), followed by the name of the tracer defined by NAME. Note it is best to void names beginning with the letters F, S, and T as these names may create naming issues in post-processing software.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"PHASE","description":"A three letter character string that defines the tracer given by NAME to a particular fluid phase. The character should be set to OIL, WAT or GAS.","units":{},"default":"None","value_type":"STRING"},{"index":3,"name":"UNITS","description":"The units for the tracer. This can be any unit but should be consistent with values entered via the TBLK and TVDP keywords in the SOLUTION section. The default values are the same as the PHASE in the model.","units":{"field":"Liquid: stb Gas: Mscf","metric":"Liquid: sm3 Gas: sm3","laboratory":"Liquid: scc Gas: scc"},"default":"Same as the phases in the model","value_type":"STRING"},{"index":4,"name":"SOLPHASE","description":"A three or four letter character string defining the partitioned tracer’s solution phase. The character string should be set to OIL, WAT, GAS or MULT. Note that SOLPHASE only needs to be defined if the partitioned tracer option has been activate with the PARTTRAC keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"STRING"},{"index":5,"name":"KPNUM","description":"The table number to be used with the partitioned tracers defined by the PARTTRAC, TRACERKP and TRACERKM keywords. Note that KPNUM only needs to be defined if the partitioned tracer option has been activate with the PARTTRAC keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"INT"},{"index":6,"name":"ADSPHASE","description":"A three letter character string defining the phase used for the adsorption calculation for when the MULT option has been for SOLPHASE. The character string should be set to OIL, WAT, GAS or ALL. Note that ADSPHASE only needs to be defined if the partitioned tracer option has been activate with the PARTTRAC keyword in the RUNSPEC section.","units":{},"default":"None","value_type":"STRING"}],"example":"--\n-- DEFINE TRACER NAMES\n--\n-- TRACER TRACER\n-- NAME PHASE\n-- ------ ------\nTRACER\n'IGS' 'GAS' / GAS INJECTOR\n'DGS' 'GAS' / DISOLVED GAS\n'IW1' 'WAT' / WAT INJECTOR 1\n'Iw2' 'WAT' / WAT INJECTOR 2\n/\nThe above example defines four passive tracers one for a gas injection well, one for tracking the dissolved gas, and two to track the injected water from two water injection wells.","expected_columns":6,"size_kind":"list"},"TRACERKM":{"name":"TRACERKM","sections":["PROPS"],"supported":false,"summary":"This keyword, TRACERKM, defines the Multi-Partitioned Tracer option K(P) tables, for when the Partitioned Tracer option has been activate with the PARTTRAC keyword in the RUNSPEC section, and the SOLPHASE parameter on the TRACER keyword in the PROPS section has been set to MULT to activate the Multi-Partitioned Tracer option. Multi-partitioned tracers can partition into any number of phases (oil, water, gas etc.) and have adsorption, decay and diffusion parameters specific to each phase; whereas the standard partitioned tracers only have a “free” and “solution” phases. For the TRACERKM keyword the K(P) tables relate the ratio of the reference phase to the other phases versus pressure. So for example, given a multi-partitioned tracer in oil, water and gas, with the water phase acting as the reference phase, then TRACERKM would consist of columnar vectors of:","parameters":[{"index":1,"name":"TRACER_NAME","description":"","units":{},"default":"","value_type":"STRING","record":1},{"index":2,"name":"PARTITION_FUNCTION_TYPE","description":"","units":{},"default":"STANDARD","value_type":"STRING","record":1},{"index":1,"name":"PHASES","description":"","units":{},"default":"","value_type":"STRING","record":2},{"index":1,"name":"TABLE","description":"","units":{},"default":"","value_type":"DOUBLE","record":3}],"example":"| [K sub { ow} left( P right)`=`{C sub{ oil }} over {C sub{ water } } \" and \" K sub { gw} left( P right)`=`{C sub{ gas }} over {C sub{ water } }] | (8.92) |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------|--------|","records_meta":[{"expected_columns":2},{},{}],"size_kind":"list"},"TRACERKP":{"name":"TRACERKP","sections":["PROPS"],"supported":false,"summary":"This keyword, TRACERKP, defines the Standard Partitioned Tracer option K(P) tables, for when the Partitioned Tracer option has been activate with the PARTTRAC keyword in the RUNSPEC section. Standard partitioned tracers only have a “free” and “solution” phases; whereas, Multi-partitioned tracers can partition into any number of phases (oil, water, gas etc.) and have adsorption, decay and diffusion parameters specific to each phase. For the TRACERKP keyword the K(P) tables relate the ratio of the reference phase (the “free” phase) to the solution phase versus pressure. So for example, given a standard partitioned tracer in oil and gas, with the oil phase acting as the reference phase, then TRACERKP would consist of columnar vectors of:","parameters":[{"index":1,"name":"TABLE","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Pressure","1"]}],"example":"| [K left( P right)`=`{C sub{ gas }} over {C sub{ oil } }] | (8.93) |\n|----------------------------------------------------------|--------|","size_kind":"fixed","variadic_record":true},"TRACITVD":{"name":"TRACITVD","sections":["PROPS"],"supported":false,"summary":"TRACITVD activates the Tracer Implicit Flux Limited Transport option and sets various parameters for this option. Basically the option is used to control numerical dispersion for tracers. Both the TRACERS keyword in the RUNSPEC section and the TRACER keyword in the PROPS section must be declared to activate tracers and to define the tracers.","parameters":[{"index":1,"name":"FLUX_LIMITER","description":"","units":{},"default":"1","value_type":"INT"},{"index":2,"name":"BOTH_TIMESTEP","description":"","units":{},"default":"YES","value_type":"STRING"}],"example":"","expected_columns":2,"size_kind":"fixed","size_count":1},"TRACTVD":{"name":"TRACTVD","sections":["PROPS"],"supported":false,"summary":"TRACTVD activates the Tracer Explicit Flux Limited Transport option. Basically the option is used to control numerical dispersion for tracers. Both the TRACERS keyword in the RUNSPEC section and the TRACER keyword in the PROPS section must be declared to activate tracers and to define the tracers.","parameters":[],"example":"","size_kind":"none","size_count":0},"TRADS":{"name":"TRADS","sections":["PROPS"],"supported":false,"summary":"This keyword, TRADS, specifies the environmental tracer adsorption tables that describe how a tracer is absorbed by the surrounding rock, for when the MXENVTR parameter has been set to greater than zero on the TRACERS keyword in the RUNSPEC section to activate environmental tracers. The keyword can only be used with environmental tracers.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","size_kind":"fixed","variadic_record":true},"TRDCY":{"name":"TRDCY","sections":["PROPS"],"supported":false,"summary":"This keyword, TRDCY, specifies the environmental tracer decay tables that specifies the tracer decay half-life, for when the MXENVTR parameter has been set to greater than zero on the TRACERS keyword in the RUNSPEC section to activate environmental tracers. The keyword can only be used with environmental tracers.","parameters":[{"index":1,"name":"HALF_TIME","description":"","units":{},"default":"1e+20","value_type":"DOUBLE","dimension":"Time"}],"example":"","expected_columns":1,"size_kind":"fixed"},"TRDIF":{"name":"TRDIF","sections":["PROPS"],"supported":false,"summary":"This keyword, TRDIF, specifies the tracer diffusion tables that specify the diffusion coefficient for a tracer. The keyword can be used with Environmental Tracers if the MXENVTR parameter has been set greater than zero on the TRACERS keyword in the RUNSPEC section. When used with a Standard Partitioned Tracer the diffusion coefficient applies to the solution phase, whereas as for a Multi-Partitioned Tracer the diffusion coefficient can be entered for each defined tracer phase. Unlike other keywords, the TRADS keyword must be concatenated with the three character name of the tracer declared by TRACER keyword in the PROPS section.","parameters":[{"index":1,"name":"HALF_TIME","description":"","units":{},"default":"1e+20","value_type":"DOUBLE","dimension":"Time"}],"example":"","expected_columns":1,"size_kind":"fixed"},"TRDIS":{"name":"TRDIS","sections":["PROPS"],"supported":false,"summary":"This keyword, TRDIS, specifies the tracer diffusion tables that should be allocated to a tracer, the actual dispersion tables are specified by the DISPERSE keyword in the PROPS section. The keyword can be used with Environmental Tracers if the MXENVTR parameter has been set greater than zero on the TRACERS keyword in the RUNSPEC section. The option does not work with two-phase Standard Partitioned Tracers and Multi-Partitioned Tracers. Unlike other keywords, the TRADS keyword must be concatenated with the three character name of the tracer declared by TRACER keyword in the PROPS section.","parameters":[{"index":1,"name":"D1TABLE","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"D2TABLE","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"D3TABLE","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"D4TABLE","description":"","units":{},"default":"","value_type":"INT"},{"index":5,"name":"D5TABLE","description":"","units":{},"default":"","value_type":"INT"},{"index":6,"name":"D6TABLE","description":"","units":{},"default":"","value_type":"INT"},{"index":7,"name":"D7TABLE","description":"","units":{},"default":"","value_type":"INT"},{"index":8,"name":"D8TABLE","description":"","units":{},"default":"","value_type":"INT"},{"index":9,"name":"D9TABLE","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":9,"size_kind":"fixed"},"TRNHD":{"name":"TRNHD","sections":["PROPS"],"supported":false,"summary":"The TRNHD keyword activates the Dispersion Non-Homogeneous Diffusion option for when tracer dispersion is independent of velocity or tracer concentration. Unlike other keywords, the TRNHD keyword must be concatenated with the name of the tracer declared by TRACER keyword in the PROPS section.","parameters":[],"example":"","size_kind":"none","size_count":0},"TRROCK":{"name":"TRROCK","sections":["PROPS"],"supported":false,"summary":"This keyword, TRROCK, specifies the environmental tracer rock data for the tracer adsorption model, for when the MXENVTR parameter has been set to greater than zero on the TRACERS keyword in the RUNSPEC section to activate environmental tracers. The keyword can only be used with environmental tracers.","parameters":[{"index":1,"name":"ADSORPTION_INDEX","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"MASS_DENSITY","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Mass/ReservoirVolume"},{"index":3,"name":"INIT_MODEL","description":"","units":{},"default":"1","value_type":"INT"}],"example":"","expected_columns":3,"size_kind":"fixed"},"TZONE":{"name":"TZONE","sections":["PROPS"],"supported":false,"summary":"The TZONE keyword sets the transition end-point scaling options for the oil, water and gas phases, for when the End-Point Scaling option has been activated by the ENDSCALE keyword in the RUNSPEC section. The keyword determines if the phase critical saturation should or should not be set to the initial immobile saturation in areas where the initial saturation is below the entered critical saturation.","parameters":[{"index":1,"name":"OILZONE","description":"OILZONE is a single character that sets the oil phase transition zone end-point scaling option and should be set to either T or F: T: for true, results in the SOWCR values being adjusted to the initial immobile saturation for oil-water or oil-water-miscible gas simulations. For oil-gas simulations the SOGCR values are modified to be the initial immobile saturation. The modifications only occur in cells where the initial saturation is below the entered critical saturation. F: for false, means the critical saturations are not modified.","units":{},"default":"F","value_type":"STRING"},{"index":2,"name":"WATZONE","description":"WATZONE is a single character that sets the water phase transition zone end-point scaling option and should be set to either T or F: T: for true, results in the SWCR values being adjusted to the initial immobile saturations. The modifications only occur in cells where the initial saturation is below the entered critical saturation values (SWCR). F: for false, means the critical saturations are not modified.","units":{},"default":"F","value_type":"STRING"},{"index":3,"name":"GASZONE","description":"GASZONE is a single character that sets the gas phase transition zone end-point scaling option and should be set to either T or F: T: for true, results in the SGCR values being adjusted to the initial immobile saturation for oil-gas or gas-water simulations. The modifications only occur in cells where the initial saturation is below the entered critical saturation (SGCR). F: for false, means the critical saturations are not modified.","units":{},"default":"F","value_type":"STRING"}],"example":"--\n-- END-POINT SCALING TRANSITION ZONE OPTIONS\n--\n-- OILZONE WATZONE GASZONE\n-- ------- ------- -------\nTZONE\nF T F / SCALING OPTION\nThe above example results in the SWCR values being adjusted to the initial immobile saturations.","expected_columns":3,"size_kind":"fixed","size_count":1},"VCRIT":{"name":"VCRIT","sections":["PROPS"],"supported":false,"summary":"The VCRIT keyword defines the critical volumes for each of the compositional components active in the model and for each equation of state. The keyword should only be used if the compositional mode has been requested using the COMPS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"VCRIT","description":"A series of real numbers that define the critical volumes for each of the compositional components active in the model.","units":{"field":"ft3/lb-M","metric":"m3/kg-M","laboratory":"m3/kg-M"},"default":"None","value_type":"DOUBLE","dimension":"GeometricVolume/Moles"}],"example":"The following example defines the critical volumes for each component in a single three-component equation of state model.\n--\n-- Critical Volumes\n--\nVCRIT\n1.505 1.585 3.250 /\nThe following example defines the critical volumes for each component in two three-component equation of state models.\n--\n-- Critical Volumes\n--\nVCRIT\n1.505 1.585 3.250 /\n1.505 1.585 3.250 /","size_kind":"fixed","variadic_record":true},"VDFLOW":{"name":"VDFLOW","sections":["PROPS"],"supported":false,"summary":"VDFLOW activates non-Darcy flow between grid blocks and defines a constant non-Darcy flow coefficient for the whole grid, the coefficient only applies to the gas phase. The coefficient is normally derived from well tests or calculated analytically based on the coefficient of inertial resistance, usually known as β, in Forchheimer’s flow equation,264\n Geertsma, J., 1974. Estimating the Coefficient of Inertial Resistance in Fluid Flow Through Porous Media. Soc.Pet.Eng.J., October: 445-450., 265\n Gewers, C.W.W. and Nichol, L.R., 1969. Gas Turbulence Factor in a Microvugular Carbonate. J.Can.Pet.Tech., April.and 266\n Wong, S.W., 1970. Effects of Liquid Saturation on Turbulence Factors for Gas Liquid Systems. J.Can.Pet.Tech., October. Dake267\n Dake, L.P. Fundamentals of Reservoir Engineering, Amsterdam, The Netherlands, Elsevier Science BV (1978) Chapter 8.6, pages 252-257., in chapter eight, reports a typical value of β to be 10.07 cm-1.","parameters":[{"index":1,"name":"BETA","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"VDFLOWR":{"name":"VDFLOWR","sections":["PROPS"],"supported":false,"summary":"VDFLOW activates non-Darcy flow between grid blocks and defines a constant non-Darcy flow coefficient for individual regions allocated by the SATNUM keyword in the REGIONS section. Note that the coefficient only applies to the gas phase. The coefficient is normally derived from well tests or calculated analytically based on the coefficient of inertial resistance, usually known as β, in Forchheimer’s flow equation,268\n Geertsma, J., 1974. Estimating the Coefficient of Inertial Resistance in Fluid Flow Through Porous Media. Soc.Pet.Eng.J., October: 445-450., 269\n Gewers, C.W.W. and Nichol, L.R., 1969. Gas Turbulence Factor in a Microvugular Carbonate. J.Can.Pet.Tech., April.and 270\n Wong, S.W., 1970. Effects of Liquid Saturation on Turbulence Factors for Gas Liquid Systems. J.Can.Pet.Tech., October. Dake271\n Dake, L.P. Fundamentals of Reservoir Engineering, Amsterdam, The Netherlands, Elsevier Science BV (1978) Chapter 8.6, pages 252-257., in chapter eight, re...","parameters":[{"index":1,"name":"BETA","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","expected_columns":1,"size_kind":"fixed"},"VEFRAC":{"name":"VEFRAC","sections":["PROPS"],"supported":false,"summary":"This keyword defines the Vertical Equilibrium (“VE”) relative permeability weighting factor (α) used to calculate the VE relative permeability curves to be used in the simulation, for when the VE option has been activated by the VE keyword in the RUNSPEC section. If α = 1.0, then the VE model calculated relative permeability curves will be used, and if α = 0.0, then the curves entered via the SWOF, SGOF, SLGOF series of keywords or the SWFN, SGFN, SGWFN, SOF2, SOF3, SOF32D series of keywords, will be used. A value of α between zero and one will result in weighted average relative permeability curves being employed, that is:","parameters":[{"index":1,"name":"FRAC","description":"","units":{},"default":"10","value_type":"DOUBLE"}],"example":"| [VE sub( average )~=~left( 1.0`-` %alpha right ) `times` left(SATNUM sub{curves}right)~+~ %alpha `times` left(VE Model sub{ curves } right)] | (8.94) |\n|----------------------------------------------------------------------------------------------------------------------------------------------|--------|","expected_columns":1,"size_kind":"fixed","size_count":1},"VEFRACP":{"name":"VEFRACP","sections":["PROPS"],"supported":false,"summary":"This keyword defines the Vertical Equilibrium (“VE”) capillary pressure weighting factor (α) used to calculate the VE capillary pressure curves to be used in the simulation, for when the VE option has been activated by the VE keyword in the RUNSPEC section. If α = 1.0, then the VE model calculated capillary pressure curves will be used, and if α = 0.0, then the curves entered via the SWOF, SGOF, SLGOF series of keywords or the SWFN, SGFN, SGWFN, SOF2, SOF3, SOF32D series of keywords, will be used. A value of α between zero and one will result in weighted average capillary pressure curves being employed, that is:","parameters":[{"index":1,"name":"FRAC","description":"","units":{},"default":"1","value_type":"DOUBLE"}],"example":"| [VE sub( average )~=~left( 1.0`-` %alpha right ) `times` left(SATNUM sub{curves}right)~+~ %alpha `times` left(VE Model sub{ curves } right)] | (8.95) |\n|----------------------------------------------------------------------------------------------------------------------------------------------|--------|","expected_columns":1,"size_kind":"fixed","size_count":1},"VEFRACPV":{"name":"VEFRACPV","sections":["PROPS"],"supported":false,"summary":"This keyword defines the Vertical Equilibrium (“VE”) capillary pressure weighting factor (α) used to calculate the VE capillary pressure curves to be used in the simulation, for when the VE option has been activated by the VE keyword in the RUNSPEC section. If α = 1.0, then the VE model calculated capillary pressure curves will be used, and if α = 0.0, then the curves entered via the SWOF, SGOF, SLGOF series of keywords or the SWFN, SGFN, SGWFN, SOF2, SOF3, SOF32D series of keywords, will be used. A value of α between zero and one will result in weighted average capillary pressure curves being employed, that is:","parameters":[],"example":"| [VE sub( average )~=~left( 1.0`-` %alpha right ) `times` left(SATNUM sub{curves}right)~+~ %alpha `times` left(VE Model sub{ curves } right)] | (8.96) |\n|----------------------------------------------------------------------------------------------------------------------------------------------|--------|","size_kind":"array"},"VEFRACV":{"name":"VEFRACV","sections":["PROPS"],"supported":false,"summary":"This keyword defines the Vertical Equilibrium (“VE”) relative permeability weighting factor (α) used to calculate the VE relative permeability curves to be used in the simulation, for when the VE option has been activated by the VE keyword in the RUNSPEC section. If α = 1.0, then the VE model calculated relative permeability curves will be used, and if α = 0.0, then the curves entered via the SWOF, SGOF, SLGOF series of keywords or the SWFN, SGFN, SGWFN, SOF2, SOF3, SOF32D series of keywords, will be used. A value of α between zero and one will result in weighted average relative permeability curves being employed, that is:","parameters":[],"example":"| [VE sub( average )~=~left( 1.0`-` %alpha right ) `times` left(SATNUM sub{curves}right)~+~ %alpha `times` left(VE Model sub{ curves } right)] | (8.97) |\n|----------------------------------------------------------------------------------------------------------------------------------------------|--------|","size_kind":"array"},"VISCAQA":{"name":"VISCAQA","sections":["PROPS"],"supported":true,"summary":"The VISCAQA keyword specifies the three Ezrokhi coefficients for each compositional component and for each equation of state that are used to calculate the aqueous phase viscosity. The keyword should only be used if the compositional mode has been requested using the COMPS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"COEFFS","description":"A series of real numbers that define the three Ezrokhi coeffients for each of the compositional components active in the model.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":"1"}],"example":"The following example defines the Ezrokhi coefficients for each component in a single three-component equation of state model.\n--\n-- Ezrokhi Coefficients for Aqueous Viscosity Calculation\n--\nVISCAQA\n--COEFF0 COEFF1 COEFF2\n2.0E-7 0.0 1.0E-9\n2.0E-7 0.0 1.0E-9\n2.0E-7 0.0 1.0E-9 /\nThe following example defines the Ezrokhi coefficients for each component in two three-component equation of state models.\n--\n-- Ezrokhi Coefficients for Aqueous Viscosity Calculation\n--\nVISCAQA\n--COEFF0 COEFF1 COEFF2\n2.0E-7 0.0 1.0E-9\n2.0E-7 0.0 1.0E-9\n2.0E-7 0.0 1.0E-9 /\n--\n2.0E-7 0.0 1.0E-9\n2.0E-7 0.0 1.0E-9\n2.0E-7 0.0 1.0E-9 /","size_kind":"fixed","variadic_record":true},"VISCREF":{"name":"VISCREF","sections":["PROPS"],"supported":null,"summary":"VISCREF defines the reference conditions for the viscosity-temperature tables, GASVISCT, OILVISCT and WATVISCT, for when the thermal option has been activated by THERMAL keyword in the RUNSPEC section. This keyword can only be used if the thermal option has been activated by the THERMAL keyword in the RUNSPEC section. Note this is different to the commercial simulator that uses the TEMP keyword in the RUNSPEC section to activate the black-oil thermal model.","parameters":[{"index":1,"name":"PRES","description":"PRES is a real positive number defining the reference pressure for the viscosity and temperature tables","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":"Pressure"},{"index":2,"name":"RS","description":"RS is a real positive number defining the reference gas-oil ratio for when the model contains gas dissolved as activated by the DISGAS keyword in the RUNSPEC section","units":{"field":"Mscf/stb","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"None","value_type":"DOUBLE","dimension":"GasDissolutionFactor"},{"index":3,"name":"API","description":"API is a real number defining the oil API for when the API tracking option has been invoked by the API keyword in the RUNSPEC section. Note that OPM Flow does not support API tracking, and therefore this variable is ignored.","units":{"field":"oAPI","metric":"oAPI","laboratory":"oAPI"},"default":"None","value_type":"DOUBLE","dimension":"1"}],"example":"The following example shows the VISCREF keyword for when the thermal option has been activated by the THERMAL keyword in the RUNSPEC section and for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set to five.\n--\n-- REF REF REF\n-- PRESSURE GOR API\n-- -------- ------- -------\nVISCREF\n3000.0 0.500 / TABLE NO. 01\n3200.0 0.550 / TABLE NO. 02\n3300.0 0.580 / TABLE NO. 03\n3400.0 0.620 / TABLE NO. 04\n3500.0 0.625 / TABLE NO. 05\nThere is no terminating “/” for this keyword.","expected_columns":3,"size_kind":"fixed"},"WAGHYSTR":{"name":"WAGHYSTR","sections":["PROPS"],"supported":true,"summary":"This keyword defines the parameters for the Water-Alternating-Gas (“WAG”) hysteresis option, for when the hysteresis option has been activated by the WAGHYSTR variable on the SATOPTS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"LANDS_PARAMETER","description":"A real value greater than zero that defines Land’s parameter, [C].. The Land’s parameter controls how the trapped gas saturation depends on the maximum gas saturation attained and the critical gas saturation; and the shape of the imbibition curve. [s_gtrap = s_gcr + ( s_gm - s_gcr ) over ( 1 + C(s_gm - s_gcr) )] where, [s_gtrap]is the trapped gas saturation, [s_gm]is the maximum gas saturation attained, and [s_gcr]is the critical gas saturation. Values of the Land’s parameter that are too small give a trapped gas saturation close to the maximum gas saturation attained. This results in an unphysical steep relative permeability curve giving potential convergence problems.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE"},{"index":2,"name":"SECONDARY_DRAINAGE_REDUCTION","description":"A real value greater than or equal to zero that defines the secondary drainage reduction factor, alpha. As alpha increases the reduction in gas mobility on secondary drainage increases.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.0","value_type":"DOUBLE"},{"index":3,"name":"GAS_MODEL","description":"A defined character string that defines whether the gas hysteresis model should be used, and should be set to one of the following character strings: YES: Use the WAG hysteresis model for the gas phase relative permeability. NO: Turn off the WAG hysteresis model and use the drainage curve. Only the YES option is currently supported by the simulator.","units":{},"default":"YES","value_type":"STRING"},{"index":4,"name":"RES_OIL","description":"A defined character string that defines whether the residual oil model should be used, and should be set to one of the following character strings: YES: Use the trapped gas to modify the residual oil saturation (SOM) in the STONE 1 three-phase oil relative permeability model. No action is taken unless the STONE1 keyword has been entered. NO: Do not modify the residual oil saturation. Only the NO option is currently supported by the simulator.","units":{},"default":"YES","value_type":"STRING"},{"index":5,"name":"WATER_MODEL","description":"A defined character string that defines whether the water hysteresis model should be used, and should be set to one of the following character strings: YES: Use the WAG hysteresis model for the water phase relative permeability NO: Turn off the WAG hysteresis model. Note that the hysteresis model specified in EHYSTR keyword applies. Only the NO option is currently supported by the simulator.","units":{},"default":"YES","value_type":"STRING"},{"index":6,"name":"IMB_LINEAR_FRACTION","description":"A real value greater than zero that defines the imbibtion curve linear fraction. This is the fraction of the curve between Sgm and Sgtrap that uses a linear transformation. A non-zero value for the linear fraction prevents the potential infinite gradient in the imbibition curve when using the Carlson analytic model.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.1","value_type":"DOUBLE"},{"index":7,"name":"THREEPHASE_SAT_LIMIT","description":"A real value between zero and one that defines the three-phase model threshold saturation. When the water saturation exceeds this threshold above the connate water saturation the gas (non-wetting) phase hysteresis switches from the two-phase model to the three-phase model. In the two-phase model a secondary drainage process follows the imbibition curve. However, if the water saturation exceeds the connate saturation by the given threshold, at the beginning of the secondary drainage process a three-phase secondary drainage curve is followed. This value also defines the minimum percentage change in gas saturation to allow switching from drainage to imbibition curve and vice-versa. This threshold allows better control of the numerical sensitivity of the system, preventing it from being too unstable.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.001","value_type":"DOUBLE"},{"index":8,"name":"RES_OIL_MOD_FRACTION","description":"A real value between zero and one that defines the residual oil modification fraction. This is the fraction of the trapped gas saturation subtracted from the residual oil (SOM) in the STONE 1 three-phase oil relative permeability model. This is not supported and will be ignored by the simulator.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0","value_type":"DOUBLE"}],"example":"The following example defines the WAG hysteresis model parameters using the WAGHYSTR keyword for a case with three saturation table regions\n--\n-- WAG HYSTERESIS PARAMETERS\n--\n-- LAND ALPHA GAS RES WATER LINEAR\n-- C FACTOR MODEL OIL MODEL FRAC\nWAGHYSTR\n2.0 1.0 YES YES YES 0.2 /\n2.0 1.0 YES NO /\n2.0 /\nHere, saturation table region one uses the gas WAG hysteresis, residual oil and water WAG hysteresis models, with a Land’s parameter of 2.0, an alpha factor of 1.0, and a imbibition curve linear factor of 0.2. The gas and water WAG hysteresis models are used in region two but the residual oil model is turned off, with a Land’s parameter of 2.0, an alpha factor of 1.0, and a default imbibition curve linear factor of 0.1. A Land’s parameter of 2.0 has been specified for region three with the remainder of the parameters defaulted.\nNote that the above example uses some options that are not currently supported by OPM Flow.","expected_columns":8,"size_kind":"fixed"},"WATDENT":{"name":"WATDENT","sections":["PROPS"],"supported":null,"summary":"WATDENT defines the water density as a function of temperature coefficients for when the thermal option has been activated by the THERMAL keyword in the RUNSPEC. Note this is an OPM Flow keyword used with OPM Flow’s black-oil thermal model that is not available in the commercial simulator’s black-oil thermal formulation.","parameters":[{"index":1,"name":"TEMP","description":"TEMP is a real positive value greater than zero that defines the absolute reference temperature used with TEXP1 and TEXP2 to estimate the change in water density with respect to temperature.","units":{"field":"oR 527.67","metric":"K 293.15","laboratory":"K 293.15"},"default":"Defined","value_type":"DOUBLE","dimension":"AbsoluteTemperature"},{"index":2,"name":"TEXP1","description":"TEXP1 is a real positive value greater than zero that defines the water thermal expansion coefficient of the first order.","units":{"field":"1/oR 1.67 x 10-4","metric":"1/K 3.0 x 10-4","laboratory":"1/K 3.0 x 10-4"},"default":"Defined","value_type":"DOUBLE","dimension":"1/AbsoluteTemperature"},{"index":3,"name":"TEXP2","description":"TEXP2 is a real positive value greater than zero that defines the water thermal expansion coefficient of the second order.","units":{"field":"1/oR2 9.26 x 10-7","metric":"1/K2 3.0 x 10-6","laboratory":"1/K2 3.0 x 10-6"},"default":"Defined","value_type":"DOUBLE","dimension":"1/AbsoluteTemperature*AbsoluteTemperature"}],"example":"The following example shows the WATDENT keyword using the default values, for when the thermal option has been activated by the THERMAL keyword in the RUNSPEC section and for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set to two.\n--\n-- WATER DENSITY TEMPERATURE COEFFICIENTS (OPM FLOW EXTENSION KEYWORD)\n--\n-- WATER DENSITY DENSITY\n-- TEMP COEFF1 COEFF2\n-- -------- ------- -------\nWATDENT\n1* 1* 1* / TABLE NO. 01\n1* 1* 1* / TABLE NO. 02\nThere is no terminating “/” for this keyword.\n| [%rho_w( p, T ) = %rho_w( p_s, T_s ) b_w( p, T )] | (8.3.366.1) |\n|---------------------------------------------------|-------------|\n| [b_w( p, T ) = { b_w( p, T_ref ) } over { 1 + c_1 ( T - T_ref ) + c_2 ( T - T_ref )^2 }] | (8.3.366.2) |\n|------------------------------------------------------------------------------------------|-------------|","expected_columns":3,"size_kind":"fixed"},"WATJT":{"name":"WATJT","sections":["PROPS"],"supported":null,"summary":"WATJT activates the water Joule-Thomson effect275\n The Joule–Thomson coefficient is defined as the change in temperature with respect to an increase in pressure at constant enthalpy. in temperature calculations, and defines the water Joule-Thomson Coefficient (“JTC”) at a given reference pressure, for when OPM Flow’s thermal option has been activated by the THERMAL keyword in the RUNSPEC.","parameters":[{"index":1,"name":"PRESS","description":"A real positive value that defines the reference pressure for the corresponding Joule-Thomson Coefficient, WATJTC.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":"Pressure"},{"index":2,"name":"WATJTC","description":"WATJTC is a real positive or negative value that defines the water phase Joule-Thomson Coefficient. If the value is defaulted (1*) or set to 0, then WATJTC is internally calculated using thermal water density data on the WATSDENT keyword in the PROPS section. If a non-zero value is specified, then the WATJTC is assumed to be constant and equal to that value.","units":{"field":"oF/psia","metric":"oC/barsa","laboratory":"oC/atma"},"default":"0","value_type":"DOUBLE","dimension":"AbsoluteTemperature/Pressure"}],"example":"The following example shows the WATJT keyword for when the thermal option has been activated by the THERMAL keyword in the RUNSPEC section, and for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set equal to two.\n--\n-- WATER JOULE-THOMSON COEFFICIENT (OPM FLOW EXTENSION KEYWORD)\n--\n-- REF OIL\n-- PRESS JTC\n-- -------- -------\nWATJT\n20.0 1* / TABLE NO. 01\n20.0 -0.20 / TABLE NO. 02\nHere the first entry is defaulted, and the simulator will therefore calculate the water JTC internally using the data on the WATDENT keyword in the PROPS section.\nThere is no terminating “/” for this keyword.\n| Note This is an OPM Flow keyword used with OPM Flow’s black-oil thermal model, that is not available in the commercial simulator’s black-oil thermal formulation. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| [%eta` `=`` left({ partial T} over {partial P} right)] | (8.98) |\n|--------------------------------------------------------|--------|\n| [%eta ``=`` left( T %alpha``-``1 right) 1 over( %rho C_p )``-`` left( g over C_p dp over dz right)^-1] | (8.99) |\n|--------------------------------------------------------------------------------------------------------|--------|\n| [%eta ``=`` left( T %alpha``-``1 right) 1 over( %rho C_b )] | (8.100) |\n|-------------------------------------------------------------|---------|","expected_columns":2,"size_kind":"fixed"},"WATVISCT":{"name":"WATVISCT","sections":["PROPS"],"supported":null,"summary":"WATVISCT defines the water viscosity as a function of temperature for when thermal option has been activated by the THERMAL keywords in the RUNSPEC. The reference pressure for this table is given by the VISCREF keyword in the PROPS section.","parameters":[{"index":1,"name":"TEMP","description":"A columnar vector of real monotonically increasing down the column values that defines the temperature values.","units":{"field":"oF","metric":"oC","laboratory":"oC"},"default":"None","value_type":"DOUBLE","dimension":["Temperature","Viscosity"]},{"index":2,"name":"VIS","description":"A columnar vector of real decreasing down the column values that defines the water viscosity for the corresponding temperature values (TEMP). VIS should be given at the reference pressure defined by the PRESS variable on the VISCREF keyword.","units":{"field":"cP","metric":"cP","laboratory":"cP"},"default":"None"}],"example":"The following example shows the WATVISCT keyword for when the thermal option has been activated by the THERMAL keyword in the RUNSPEC section and for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set equal to one.\n--\n-- WATER VISCOSITY VERSUS TEMPERATURE TABLES\n--\n-- WATER WATER\n-- TEMP VISC\n-- -------- -------\nWATVISCT\n100.0 0.625\n110.0 0.620\n120.0 0.580\n150.0 0.550\n165.0 0.500 / TABLE NO. 01\nThere is no terminating “/” for this keyword.","size_kind":"fixed","variadic_record":true},"WSF":{"name":"WSF","sections":["PROPS"],"supported":null,"summary":"The WSF keyword defines the water relative permeability data versus water saturation tables for when only gas and water are present in the input deck. This keyword should only be used if the gas and water phases are present in the run, and can therefore also be used with the CO2STORE and H2STORE models. In addition, the keyword must be used in conjunction with the GSF keyword in the PROPS section, that defines the gas relative permeability and gas-water capillary pressure data versus gas saturation for gas-water systems.","parameters":[{"index":1,"name":"SWAT","description":"A columnar vector of real values monotonically increasing down the column starting from the connate water saturation and terminating at one, that defines the water saturation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":["1","1"]},{"index":2,"name":"KRW","description":"A columnar vector of real values that are either equal or increasing down the column and that are greater than or equal to zero and less than or equal to one that defines the water relative permeability with respect to water saturation. Note that the first entry in the column must be zero.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- WATER RELATIVE PERMEABILITY TABLES (OPM FLOW KEYWORD)\n--\nWSF\n-- SWAT KRW\n-- FRAC\n-- -------- --------\n0.200000 0.0000\n0.238616 0.0002\n0.245309 0.0004\n0.261989 0.0010\n0.303091 0.0044\n0.368269 0.0191\n0.435026 0.0519\n0.486387 0.0940\n0.550683 0.1725\n0.575342 0.2115\n0.599076 0.2542\n0.621294 0.2991\n0.642171 0.3458\n0.658984 0.3868\n0.671123 0.4183\n0.679268 0.4403\n0.684963 0.4562\n0.688893 0.4674\n0.692025 0.4765\n0.694641 0.4841\n0.696976 0.4910\n0.699099 0.4973\n0.700000 0.5000\n1.000000 0.9000 / TABLE NO. 01\n-- -------- --------\n0.200000 0.0000\n0.238616 0.0002\n0.245309 0.0004\n0.261989 0.0010\n0.303091 0.0044\n0.368269 0.0191\n0.435026 0.0519\n0.486387 0.0940\n0.550683 0.1725\n0.575342 0.2115\n0.599076 0.2542\n0.621294 0.2991\n0.642171 0.3458\n0.658984 0.3868\n0.671123 0.4183\n0.679268 0.4403\n0.684963 0.4562\n0.688893 0.4674\n0.692025 0.4765\n0.694641 0.4841\n0.696976 0.4910\n0.699099 0.4973\n0.700000 0.5000\n1.000000 0.9000 / TABLE NO. 01\nThe example defines two WSF tables for use when only gas and water are present in the run.\n| Note WSF is a compositional keyword in the commercial compositional simulator, and will therefore cause an error in the commercial black-oil simulator. Currently, both the GSF and WSF keywords can only be used with the CO2STORE and H2STORE models. |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"fixed","variadic_record":true},"ZMFVD":{"name":"ZMFVD","sections":["PROPS"],"supported":true,"summary":"The ZMFVD keyword defines the compositional component mole fractions, for each component, as a function of depth, as such the keyword should have the same number of component columnar vectors as that declared via the COMPS keyword in the RUNSPEC section, and the NCOMPS keyword in the PROPS section. The keyword should only be used if the CO2STORE and GASWAT keywords in the RUNSPEC section have also be activated for the gas-water two component model.","parameters":[{"index":1,"name":"DEPTH","description":"A columnar vector of real monotonically increasing down the column values that defines the depth values for the corresponding compositional component mole fractions. The default number of DEPTH values is 20, as defined by the NDRXVD parameter on the EQLDIMS keyword in the RUNSPEC section, and which may be used to reset the number of DEPTH values.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":["Length","1","1"]},{"index":2,"name":"ZCOMP","description":"A series of columnar vectors, with each columnar vector representing a compositional component mole fraction as a function of DEPTH. In addition, the sum of the compositional component mole fractions must sum to one for a given DEPTH value, otherwise an error will occur. Secondly, if the composition is independent of depth, then only one single row may be entered. Note that the number of columnar vectors, should be the same as that entered via the NCOMPS keyword in the PROPS section, and the COMPS keyword in the RUNSPEC section. Finally, only the default value of two components are currently supported by OPM Flow.","units":{"field":"mole fraction","metric":"mole fraction","laboratory":"mole fraction"},"default":"None"}],"example":"The following example defines how to confirm a two component formulation, together with defining the names of the composition components, as well as the compositional gradient, to be used with the CO2STORE and GASWAT options.\n--\n-- CONFIRM NUMBER OF COMPOSITIONAL COMPONENTS (OPM FLOW KEYWORD)\n--\nNCOMPS\n2 /\n--\n-- DEFINE COMPOSITIONAL COMPONENTS NAMES (OPM FLOW KEYWORD)\n--\nCNAMES\n'CO2'\n'H2O' /\n--\n-- COMPOSITIONAL COMPONENT MOLE FRACTIONS VS DEPTH (OPM FLOW KEYWORD)\n--\n-- DEPTH CO2 H2O\nZMFVD\n2000 0.0 1.0\n2100 0.0 1.0\n/\n| Note This is an OPM Flow keyword used with OPM Flow’s CO2STORE and GASWAT keywords in the RUNSPEC section, and should not be confused with the more general version of the ZMFVD keyword used in the commercial compositional simulator. |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"fixed","variadic_record":true},"ENDNUM":{"name":"ENDNUM","sections":["REGIONS"],"supported":false,"summary":"The ENDNUM keyword defines the end-point scaling depth table region numbers for each grid block. The end-point scaling depth tables for various regions are defined by the ENPVTD280\n This keyword is not supported by OPM Flow but would change the results if supported so the simulation will be stopped. and the ENKRVD281\n This keyword is not supported by OPM Flow but would change the results if supported so the simulation will be stopped. keywords in the PROPS section. In the RUNSPEC section the NTENDP variable on the ENDSCALE keyword defines the maximum number of depth tables.","parameters":[{"index":1,"name":"ENDNUM","description":"ENDNUM defines an array of positive integers assigning a grid cell to a particular end-point scaling depth table region. The maximum number of ENDNUM regions is set by the NTENDP variable on the ENDSCALE keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"The example below sets three ENDNUM regions for a 4 x 5 x 2 model.\n--\n-- DEFINE ENDNUM REGIONS FOR ALL CELLS\n--\nENDNUM\n2 2 1 1 2 2 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n3 3 1 1 3 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n/\nAlternatively the EQUALS keyword could be employed to accomplish the same task, that is:\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nENDNUM 1 1* 1* 1* 1* 1* 1* / SET REGION 1\nENDNUM 2 1 2 1 2 1 1 / SET REGION 2\nENDNUM 3 1 2 1 2 2 2 / SET REGION 3\n/","size_kind":"array"},"EOSNUM":{"name":"EOSNUM","sections":["REGIONS"],"supported":false,"summary":"The EOSNUM keyword defines the Equation Of State (EOS) region number for all the cells in the model via an array. The region number specifies which Equation Of State is used in each grid block. The keyword should only be used if the compositional mode has been requested using the COMPS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"EOSNUM","description":"EOSNUM is an array of positive integers less than or equal to NMEOSR that define the EOS region number for each cell in the model. The NMEOSR variable on the TABDIMS keyword in the RUNSPEC section defines the number of EOS regions in the model.","units":{},"default":"1"}],"example":"The example below sets two EOSNUM regions for a 4 x 5 x 2 model.\n--\n-- DEFINE EOSNUM REGIONS FOR ALL CELLS\n--\nEOSNUM\n20*1\n20*2\n/","size_kind":"array"},"EQLNUM":{"name":"EQLNUM","sections":["REGIONS"],"supported":null,"summary":"The EQLNUM keyword defines the equilibration region numbers for each grid block. The equilibration data for various regions are defined in the SOLUTION section. For example, the EQUIL keyword in the SOLUTION section defines the initial pressures and fluid contacts for each equilibration region identified by the EQLNUM region array.","parameters":[{"index":1,"name":"EQLNUM","description":"EQLNUM defines an array of positive integers assigning a grid cell to a particular equilibration region. The maximum number of EQLNUM regions is set by the NTEQUL variable on the EQLDIMS keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"The example below sets three EQLNUM regions for a 4 x 5 x 2 model.\n--\n-- DEFINE EQLNUM REGIONS FOR ALL CELLS\n--\nEQLNUM\n2 2 1 1 2 2 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n3 3 1 1 3 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n/\nAlternatively the EQUALS keyword could be employed to accomplish the same task, that is:\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nEQLNUM’ 1 1* 1* 1* 1* 1* 1* / SET REGION 1\nEQLNUM’ 2 1 2 1 2 1 1 / SET REGION 2\nEQLNUM’ 3 1 2 1 2 2 2 / SET REGION 3\n/","size_kind":"array"},"FIP":{"name":"FIP","sections":["REGIONS"],"supported":null,"summary":"The FIP keyword defines the fluid in-place name and the associated region numbers for each grid block. The simulator can print out summaries of the fluid in-place in each region, the current flow rates between regions, and the cumulative flows between regions. This keyword is not in the standard keyword format due to the fluid in-place name being concatenated to the keyword FIP to fully define the keyword.","parameters":[{"index":1,"name":"FIPNAME","description":"A character string of up to eight characters, consisting of FIP as the first three characters followed by up to a five letter character string defining the fluid in-place’s name.","units":{},"default":"None"},{"index":2,"name":"FIPNUM","description":"FIPNUM defines an array of positive integers greater than or equal to one, that assigns a grid cell to a particular fluid in-place region named by FIPNAME. The maximum number of FIP and FIPNUM regions is set by the REGDIMS(NMFIPR) or the TABDIMS(NTFIP) keywords(variables) in the RUNSPEC section. If both REGDIMS(NMFIPR) and TABDIMS(NTFIP) have been defined then the maximum of the two is used.","units":{},"default":"1"}],"example":"The example below defines a region name of UNIT and sets three FIPUNIT regions for a 4 x 5 x 2 model.\n--\n-- DEFINE FIPUNIT FIP REGIONS FOR ALL CELLS\n--\nFIPUNIT\n2 2 1 1 2 2 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n3 3 1 1 3 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n/\nThe second example is based on the Norne model that defines two FIP regions based on geological layers and numerical layers using the EQUALS keyword.\n-- FIPGL BASED ON GEOLOGICAL LAYERS\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nFIPGL 1 1 46 1 112 1 3 / Garn\nFIPGL 2 1 46 1 112 4 4 / Not\nFIPGL 3 1 46 1 112 5 5 / Ile 2.2\nFIPGL 4 1 46 1 112 6 8 / Ile 2.1\nFIPGL 5 1 46 1 112 9 11 / Ile 1\nFIPGL 6 1 46 1 112 12 12 / Tofte 2.2\nFIPGL 7 1 46 1 112 13 15 / Tofte 2.1\nFIPGL 8 1 46 1 112 16 18 / Tofte 1\nFIPGL 9 1 46 1 112 19 22 / Tilje\n--\n-- FIPNL BASED ON NUMERICAL LAYERS\n--\nFIPNL 1 1 46 1 112 1 1 / Garn 3\nFIPNL 2 1 46 1 112 2 2 / Garn 2\nFIPNL 3 1 46 1 112 3 3 / Garn 1w\nFIPNL 4 1 46 1 112 4 4 / Not\nFIPNL 5 1 46 1 112 5 5 / Ile 2.2\nFIPNL 6 1 46 1 112 6 6 / Ile 2.1.3\nFIPNL 7 1 46 1 112 7 7 / Ile 2.1.2\nFIPNL 8 1 46 1 112 8 8 / Ile 2.1.1\nFIPNL 9 1 46 1 112 9 9 / Ile 1.3\nFIPNL 10 1 46 1 112 10 10 / Ile 1.2\nFIPNL 11 1 46 1 112 11 11 / Ile 1.1\nFIPNL 12 1 46 1 112 12 12 / Tofte 2.2\nFIPNL 13 1 46 1 112 13 13 / Tofte 2.1.3\nFIPNL 14 1 46 1 112 14 14 / Tofte 2.1.2\nFIPNL 15 1 46 1 112 15 15 / Tofte 2.1.1\nFIPNL 16 1 46 1 112 16 16 / Tofte 1.2.2\nFIPNL 17 1 46 1 112 17 17 / Tofte 1.2.1\nFIPNL 18 1 46 1 112 18 18 / Tofte 1.1\nFIPNL 19 1 46 1 112 19 19 / Tilje 4\nFIPNL 20 1 46 1 112 20 20 / Tilje 3\nFIPNL 21 1 46 1 112 21 21 / Tilje 2\nFIPNL 22 1 46 1 112 22 22 / Tilje 1\n/\nThen in order to get the reservoir pressure for the regions and the in-place oil volumes SUMMARY variables written to the SUMMARY file, one would use the following SUMMARY variable names in the SUMMARY section\n-- ==============================================================================\n--\n-- SUMMARY SECTION\n--\n-- ==============================================================================\nSUMMARY\n-- FIP REGION REPORTING\n--\nROIP_GL\n/\nROIP_NL\n/\nRPR__GL\n/\nRPR__NL\n/\nNotice how the “_” character has been used to extend the SUMMARY variable name to five characters.\n| Note The commercial simulator prints out a fluid in-place report if the FIP option on the RPTSCHED keyword is set equal to three, that is: FIP=3. This option is currently not available in OPM Flow. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","templated":true},"FIPNUM":{"name":"FIPNUM","sections":["REGIONS"],"supported":null,"summary":"The FIPNUM keyword defines the fluid in-place region numbers for each grid block. The simulator can print out summaries of the fluid in-place in each region, the current flow rates between regions, and the cumulative flows between regions.","parameters":[{"index":1,"name":"FIPNUM","description":"FIPNUM defines an array of positive integers greater than or equal to one, that assigns a grid cell to a particular fluid in-place region. The maximum number of FIPNUM and FIP regions is set by the REGDIMS(NMFIPR) or the TABDIMS(NTFIP) keywords(variables) in the RUNSPEC section. If both REGDIMS(NMFIPR) and TABDIMS(NTFIP) have been defined then the maximum of the two is used.","units":{},"default":"1"}],"example":"The example below sets three FIPNUM regions for a 4 x 5 x 2 model.\n--\n-- DEFINE FIPNUM REGIONS FOR ALL CELLS\n--\nFIPNUM\n2 2 1 1 2 2 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n3 3 1 1 3 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n/\nAlternatively the EQUALS keyword could be employed to accomplish the same task, that is:\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nFIPNUM 1 1* 1* 1* 1* 1* 1* / SET REGION 1\nFIPNUM 2 1 2 1 2 1 1 / SET REGION 2\nFIPNUM 3 1 2 1 2 2 2 / SET REGION 3\n/\n| Note In most simulation models the FIPNUM array is used to define various regions in the model for fluid in-place reporting and to identify (or report) the flow between the different regions. When calibrating a model’s in-place volumes it would be useful to use the FIPNUM array combined with the MULTREGP keyword to accomplish this. However, the FIPNUM array cannot be used in the GRID section. A work around is to: Use the FIPNUM array but change the keyword to MULTNUM and incorporate this keyword or INCLUDE file in the GRID section. Use the MULTREGP to calibrate the fluid in-place volumes for the various regions. In the REGIONS section, use the COPY keyword to copy the MULTNUM array to the FIPNUM array. The above work flow will ensure that both arrays and the reporting of fluid in-place regions are consistent. |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"array"},"FIPOWG":{"name":"FIPOWG","sections":["REGIONS"],"supported":false,"summary":"The FIPOWG keyword activates automatic fluid in-place reporting based on the initial oil, gas and water zones defined by the initial equilibration. The fluid contacts on the EQUIL keyword in the SOLUTION section determine the reporting fluid category a grid cell belongs to. For example all grid cells with depths above the gas-oil contact on the EQUIL keyword will be assigned to the gas zone and reported accordingly. Similarly, grid cells with depths between the gas-oil contact and the water-oil contact will be assigned to the oil zone. And finally, grid cells with depths below the oil-water contact will be assigned to the water zone. The simulator can print out summaries of the fluid in-place in each region, the current flow rates between regions, and the cumulative flows between regions.","parameters":[],"example":"--\n-- ACTIVATE OIL, GAS, AND WATER FIP ZONE REPORTING\n--\nFIPOWG\nThe above example switches on automatic fluid in-place reporting based on the initial oil, gas and water zones defined by the initial equilibration.","size_kind":"none","size_count":0},"HBNUM":{"name":"HBNUM","sections":["REGIONS"],"supported":false,"summary":"The HBNUM keyword defines the Herschel-Bulkley rheological property table region numbers for each grid block, as such there must be one entry for each cell in the model. The region number specifies which table of Herschel-Bulkley rheological property data is assigned to a grid block, for when the Polymer option has been invoked via the POLYMER keyword in the RUNSPEC section and the Non-Newtonian Fluid phase has been declared active by the NNEWTF keyword, also in the RUNSPEC section. The FHERCHBL keyword in the PROPS section is used to specify the Herschel-Bulkley rheological property table data.","parameters":[],"example":"","size_kind":"array"},"HWSNUM":{"name":"HWSNUM","sections":["REGIONS"],"supported":false,"summary":"The HWSNUM keyword defines the saturation tables (relative permeability and capillary pressure tables) region numbers for each grid block, as such there must be one entry for each cell in the mode, for when the Surfactant Wettability option has been selected. The keyword may also be used with the Low Salt Brine option, in this case the water wet curves are calculated as a function of the low and high water wet salinity curves. The region number specifies which set of relative permeability tables are used to calculate the relative permeability and capillary pressure in a grid block. Note that the keyword is obligatory if the SURFACTW keyword in the RUNSPEC section has been used to invoke the Surfactant Wettability option.","parameters":[{"index":1,"name":"HWSNUM","description":"HWSNUM defines an array of positive integers assigning a grid cell to a particular saturation table region. The maximum number of HWSNUM regions is set by the NTSFUN variable on the TABDIMS keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"The example below sets three HWSNUM regions for a 4 x 5 x 2 model.\n--\n-- DEFINE HWSNUM REGIONS FOR ALL CELLS\n--\nHWSNUM\n2 2 1 1 2 2 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n3 3 1 1 3 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n/\nAlternatively the EQUALS keyword could be employed to accomplish the same task, that is:\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nHWSNUM 1 1* 1* 1* 1* 1* 1* / SET REGION 1\nHWSNUM 2 1 2 1 2 1 1 / SET REGION 2\nHWSNUM 3 1 2 1 2 2 2 / SET REGION 3\n/","size_kind":"array"},"IMBNUM":{"name":"IMBNUM","sections":["REGIONS"],"supported":false,"summary":"The IMBNUM keyword defines the imbibition saturation tables (relative permeability and capillary pressure tables) region numbers for each grid block, as such there must be one entry for each cell in the model. The region number specifies which set of relative permeability tables (SGFN, SWFN, SOF2, SOF3, SOF32D, SGOF, SLGOF and SWOF) are used to calculate the relative permeability and capillary pressure in a grid block.","parameters":[{"index":1,"name":"IMBNUM","description":"IMBNUM defines an array of positive integers assigning a grid cell to a particular saturation table region. The maximum number of IMBNUM regions is set by the NTSFUN variable on the TABDIMS keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"The example below sets three IMBNUM regions for a 4 x 5 x 2 model using the EQUALS keyword.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nIMBNUM 1 1* 1* 1* 1* 1* 1* / SET REGION 1\nIMBNUM 2 1 2 1 2 1 1 / SET REGION 2\nIMBNUM 3 1 2 1 2 2 2 / SET REGION 3\n/","size_kind":"array"},"IMBNUMMF":{"name":"IMBNUMMF","sections":["REGIONS"],"supported":false,"summary":"The IMBNUMMF keyword defines the imbibition saturation tables (relative permeability and capillary pressure tables) region numbers for flow between the matrix and fracture blocks, for when the HYSTER option on the SATOPTS keyword has been invoked to activate the Hysteresis option, and the Dual Porosity or Dual Permeability models have been activated via the DUALPORO or DUALPERM keywords. All keywords are in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"KRNUM":{"name":"KRNUM","sections":["REGIONS"],"supported":false,"summary":"The KRNUM keyword defines the direction dependent saturation tables (relative permeability and capillary pressure tables) region numbers for each grid block face, as such there must be one entry for each cell in the model. The region number specifies which set of relative permeability tables (SGFN, SWFN, SOF2, SOF3, SOF32D, SGOF, SLGOF and SWOF) are used to calculate the relative permeability and capillary pressure in a grid block. The keyword should only be used if Directional Dependent Saturation Function option has been activated by the DIRECT parameter on the SATOPTS keyword in the RUNSPEC section. Otherwise the standard none directional relative permeability curves should be assigned by the SATNUM keyword in the REGIONS section.","parameters":[{"index":1,"name":"KRNUM","description":"KRNUM defines an array of positive integers assigning a grid cell to a particular saturation table region. The maximum number of KRNUM regions is set by the NTSFUN variable on the TABDIMS keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"The example below sets the directional saturation tables in all three directions using the EQUALS keyword.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nKRNUMX 1 1* 1* 1* 1* 1* 1* / SET X-DIR TABLES\nKRNUMY 2 1* 1* 1* 1* 1* 1* / SET Y-DIR TABLES\nKRNUMZ 3 1* 1* 1* 1* 1* 1* / SET Z-DIR TABLES\n/","size_kind":"array"},"KRNUMMF":{"name":"KRNUMMF","sections":["REGIONS"],"supported":false,"summary":"The KRNUMMF keyword defines the drainage saturation tables (relative permeability and capillary pressure tables) region numbers for flow between the matrix and fracture blocks, for when the Dual Porosity or Dual Permeability models have been activated via the DUALPORO or DUALPERM keywords in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"LSLTWNUM":{"name":"LSLTWNUM","sections":["REGIONS"],"supported":false,"summary":"The LSLTWNUM keyword defines the saturation tables (relative permeability and capillary pressure tables) region numbers for each grid block, as such there must be one entry for each cell in the model. The region number specifies which set of relative permeability tables (SWFN, SOF3 and related keywords) are used to calculate the relative permeability and capillary pressure in a grid block. The keyword should only be used if the Low Salinity option for the Brine model and the Surfactant Wettability option have been activated by the LOWSALT and SURFACTW keywords, respectively, in the RUNSPEC section.","parameters":[{"index":1,"name":"LSLTWNUM","description":"LSLTWNUM defines an array of positive integers assigning a grid cell to a particular saturation table region. The maximum number of LSLTWNUM regions is set by the NTSFUN variable on the TABDIMS keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"The example below sets three LSLTWNUM regions for the model.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nLSLTWNUM 1 1* 1* 1* 1* 1* 1* / SET REGION 1\nLSLTWNUM 2 1 2 1 2 1 1 / SET REGION 2\nLSLTWNUM 3 1 2 1 2 2 2 / SET REGION 3\n/","size_kind":"array"},"LSNUM":{"name":"LSNUM","sections":["REGIONS"],"supported":false,"summary":"The LSNUM keyword defines the saturation tables (relative permeability and capillary pressure tables) region numbers for each grid block, as such there must be one entry for each cell in the model. The region number specifies which set of relative permeability tables (SWFN, SOF3 and related keywords) are used to calculate the relative permeability and capillary pressure in a grid block. The keyword should only be used if the Low Salinity option for the Brine model has been activated in the RUNSPEC section using the LOWSALT keyword.","parameters":[{"index":1,"name":"LSNUM","description":"LSNUM defines an array of positive integers assigning a grid cell to a particular saturation table region. The maximum number of LSNUM regions is set by the NTSFUN variable on the TABDIMS keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"The example below sets three LSNUM regions for the model.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nLSNUM 1 1* 1* 1* 1* 1* 1* / SET REGION 1\nLSNUM 2 1 2 1 2 1 1 / SET REGION 2\nLSNUM 3 1 2 1 2 2 2 / SET REGION 3\n/","size_kind":"array"},"LWSLTNUM":{"name":"LWSLTNUM","sections":["REGIONS"],"supported":false,"summary":"The LWSLTNUM keyword defines the saturation tables (relative permeability and capillary pressure tables) region numbers for each grid block, as such there must be one entry for each cell in the model. The region number specifies which set of relative permeability tables (SWFN, SOF3 and related keywords) are used to calculate the relative permeability and capillary pressure in a grid block. The keyword should only be used if the Low Salinity option for the Brine model has been activated by the LOWSALT kwyword in the RUNSPEC section.","parameters":[{"index":1,"name":"LWSLTNUM","description":"LWSLTNUM defines an array of positive integers assigning a grid cell to a particular saturation table region. The maximum number of LSLTWNUM regions is set by the NTSFUN variable on the TABDIMS keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"The example below sets three LWSLTNUM regions for the model.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nLWSLTNUM 1 1* 1* 1* 1* 1* 1* / SET REGION 1\nLWSLTNUM 2 1 2 1 2 1 1 / SET REGION 2\nLWSLTNUM 3 1 2 1 2 2 2 / SET REGION 3\n/","size_kind":"array"},"LWSNUM":{"name":"LWSNUM","sections":["REGIONS"],"supported":false,"summary":"The LWSNUM keyword defines the saturation tables (relative permeability and capillary pressure tables) region numbers for each grid block, as such there must be one entry for each cell in the model. The region number specifies which set of relative permeability tables (SWFN, SOF3 and related keywords) are used to calculate the relative permeability and capillary pressure in a grid block. The keyword should only be used if the Low Salinity option for the Brine model and the Surfactant Wettability option have been activated by the LOWSALT and SURFACTW keywords, respectively, in the RUNSPEC section.","parameters":[{"index":1,"name":"LWSNUM","description":"LWSNUM defines an array of positive integers assigning a grid cell to a particular saturation table region. The maximum number of LWSNUM regions is set by the NTSFUN variable on the TABDIMS keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"The example below sets three LWSNUM regions for the model.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nLWSNUM 1 1* 1* 1* 1* 1* 1* / SET REGION 1\nLWSNUM 2 1 2 1 2 1 1 / SET REGION 2\nLWSNUM 3 1 2 1 2 2 2 / SET REGION 3\n/","size_kind":"array"},"MISCNUM":{"name":"MISCNUM","sections":["REGIONS"],"supported":null,"summary":"The MISCNUM keyword defines the miscibility region number mixing tables as defined by the TLMIXPAR keyword in the PROPS section, for when the miscibility option has been activated by the MISCIBLE keyword in the RUNSPEC section. MISCNUM also allocates miscible residual oil saturation versus water saturation tables (SORWMIS keyword in the PROPS section) used to calculate the relative permeability and PVT properties for a grid cell.","parameters":[{"index":1,"name":"MISCNUM","description":"MISCNUM defines an array of positive integers greater than or equal to zero, that assign a grid cell to a particular table of mixing parameters as defined by the TLMIXPAR and SORWMIS keywords. A value of zero sets the fluids within a grid cell to be immiscible. The maximum number of MISCNUM regions is set by the NTMIS variable on the MISCIBLE keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"The example below sets three MISCNUM regions in the model on a layer by layer basis, using the EQUALS keyword.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nMISCNUM 1 1* 1* 1* 1* 1 12 / SET REGION 1\nMISCNUM 2 1* 1* 1* 1* 13 55 / SET REGION 2\nMISCNUM 3 1* 1* 1* 1* 56 120 / SET REGION 3\n/","size_kind":"array"},"PENUM":{"name":"PENUM","sections":["REGIONS"],"supported":false,"summary":"The PENNUM keyword defines the petro-elastic region number for each grid block that is used to assign the of petro-elastic coefficients, bulk modulus functions and shear modulus functions as defined by the PECOEFS, PEKTAB and PEGTAB series of keywords in the PROPS section.","parameters":[],"example":"","size_kind":"array"},"PLMIXNUM":{"name":"PLMIXNUM","sections":["REGIONS"],"supported":null,"summary":"The PLMIXNUM keyword defines the polymer region number for each grid block that is used to assign the mixing tables as well as the maximum polymer and salt concentrations, as defined by the PLMIXPAR and PLYMAX keywords in the PROPS section, for when the polymer option has been activated by the POLYMER keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"PLMIXNUM","description":"PLMIXNUM defines an array of positive integers greater than or equal to one, that assign a grid cell to a particular table of mixing parameters as defined by the PLMIXPAR and PLYMAX keywords. The maximum number of PLMIXNUM regions is set by the NPLMIX variable on the REGDIMS keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"The example below sets three PLMIXNUM regions in the model on a layer by layer basis, using the EQUALS keyword.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nPLMIXNUM 1 1* 1* 1* 1* 1 12 / SET REGION 1\nPLMIXNUM 2 1* 1* 1* 1* 13 55 / SET REGION 2\nPLMIXNUM 3 1* 1* 1* 1* 56 120 / SET REGION 3\n/","size_kind":"array"},"PVTNUM":{"name":"PVTNUM","sections":["REGIONS"],"supported":null,"summary":"The PVTNUM keyword defines the PVT region numbers for each grid block, as such there must be one entry for each cell in the model. The region number specifies which set of PVT tables (DENSITY, PVDG, PVDO, PVTG, PVTO, PVCO, PVTW and ROCK) are used to calculate the PVT properties in a grid block.","parameters":[{"index":1,"name":"PVTNUM","description":"PVTNUM defines an array of positive integers assigning a grid cell to a particular PVT region. The maximum number of PVTNUM regions is set by the NTPVT variable on the TABDIMS keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"The example below sets three PVTNUM regions for a 4 x 5 x 2 model.\n--\n-- DEFINE PVTNUM REGION FOR ALL CELLS\n--\nPVTNUM\n2 2 1 1 2 2 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n3 3 1 1 3 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n/\nAlternatively the EQUALS keyword could be employed to accomplish the same task, that is:\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nPVTNUM 1 1* 1* 1* 1* 1* 1* / SET REGION 1\nPVTNUM 2 1 2 1 2 1 1 / SET REGION 2\nPVTNUM 3 1 2 1 2 2 2 / SET REGION 3\n/\nThere third example shows how to ensure the various PVT regions are isolated. First of all define the MULTNUM array in the GRID section and ensure all the regions are isolated.\n-- ==============================================================================\n--\n-- GRID SECTION\n--\n-- ==============================================================================\nGRID\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nMULTNUM 1 1* 1* 1* 1* 1* 1* / SET REGION 1\nMULTNUM 2 1 2 1 2 1 1 / SET REGION 2\nMULTNUM 3 1 2 1 2 2 2 / SET REGION 3\n/\n--\n-- SET TRANSMISSIBILITES ACROSS DIFFERENT RESERVOIRS TO ZERO TO ISOLATE\n-- RESERVOIRS\n--\n-- REGION REGION TRANS DIREC NNC REGION ARRAY\n-- FROM TO MULT OPT OPTS M / F / O\nMULTREGT\n1* 1* 0.0 1* 'ALL' M / ALL REGIONS SEALED\n/\nThen in the REGIONS section copy the MULTNUM array to the PVTNUM array.\n-- ==============================================================================\n--\n-- REGIONS SECTION\n--\n-- ==============================================================================\nREGIONS\n--\n-- COPY AN ARRAY TO ANOTHER ARRAY BASED ON A REGION NUMBER\n--\n-- ARRAY ARRAY REGION REGION ARRAY\n-- FROM TO NUMBER M / F / O\nCOPYREG\nMULTNUM PVTNUM 1 M / COPY MULT TO PVT 1\nMULTNUM PVTNUM 2 M / COPY MULT TO PVT 2\nMULTNUM PVTNUM 3 M / COPY MULT TO PVT 3\n/\nAll the separate PVT regions are now isolated.\n| Note Care should be taken that cells in different PVTNUM regions are not in communication, since the fluid properties are associated with a cell. If for example, a rbbl or a rm3 of oil flows from PVTNUM region 1 to PVTNUM region 2, then the oil properties of that oil will change from the PVT 1 data set to the PVT data set 2. This will result in material balance errors, that may or may not cause numerical issues. To avoid this one should use the MULTNUM (or FLUXNUM, or OPERNUM) array with the MULTREGT array to ensure that the various PVTNUM regions are not in communication. |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"array"},"REGIONS":{"name":"REGIONS","sections":["REGIONS"],"supported":null,"summary":"The REGIONS activation keyword marks the end of the PROPS section and the start of the REGIONS section that defines how various fluid and rock property data defined in the PROPS section are allocated to the individual cells in the model.","parameters":[],"example":"-- ==============================================================================\n--\n-- REGIONS SECTION\n--\n-- ==============================================================================\nREGIONS\nThe above example marks the end of the PROPS section and the start of the REGIONS section in the OPM Flow data input file.","size_kind":"none","size_count":0},"RESIDNUM":{"name":"RESIDNUM","sections":["REGIONS"],"supported":false,"summary":"The RESIDNUM keyword defines the Vertical Equilibrium (“VE”) residual flow calculation saturation tables (relative permeability and capillary pressure tables) region numbers for each grid block, as such there must be one entry for each cell in the model. The region number specifies which set of relative permeability tables (SGFN, SWFN, SOF2, SOF3, SOF32D, SGOF, SLGOF and SWOF) are used to calculate the relative permeability and capillary pressure in a grid block. The keyword should only be used if the Vertical Equilibrium option has been invoked via the VE keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"RESIDNUM","description":"RESIDNUM defines an array of positive integers assigning a grid cell to a particular saturation table region. The maximum number of RESIDNUM regions is set by the NTSFUN variable on the TABDIMS keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"The example below sets three RESIDNUM regions for the model, by first setting all values to one, then setting layers 2 to 10 to two, and finally setting layers 30 to 50 to three.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nSATNUM 1 1* 1* 1* 1* 1* 1* / SET REGION 1\nSATNUM 2 1 2 1 2 2 10 / SET REGION 2\nSATNUM 3 1 2 1 2 30 50 / SET REGION 3\n/","size_kind":"array"},"ROCKNUM":{"name":"ROCKNUM","sections":["REGIONS"],"supported":null,"summary":"The ROCKNUM keyword defines the rock compaction table region numbers for each grid block, as such there must be one entry for each cell in the model. The region number specifies which set of rock compaction tables defined by the ROCKTAB keyword are used to calculate the rock compaction in a grid block.","parameters":[{"index":1,"name":"ROCKNUM","description":"ROCKNUM defines an array of positive integers assigning a grid cell to a particular rock compaction table region. The maximum number of ROCKNUM regions is set by the NTROCC variable on the ROCKCOMP keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"The example below sets three ROCKNUM regions for a 4 x 5 x 2 model.\n--\n-- DEFINE ROCKNUM REGION FOR ALL CELLS\n--\nROCKNUM\n2 2 1 1 2 2 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n3 3 1 1 3 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n/\nAlternatively the EQUALS keyword could be employed to accomplish the same task, that is:\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nROCKNUM 1 1* 1* 1* 1* 1* 1* / SET REGION 1\nROCKNUM 2 1 2 1 2 1 1 / SET REGION 2\nROCKNUM 3 1 2 1 2 2 2 / SET REGION 3\n/","size_kind":"array"},"RPTREGS":{"name":"RPTREGS","sections":["REGIONS"],"supported":false,"summary":"This keyword defines the data in the REGIONS section that is to be printed to the output print file in human readable format. The keyword has two distinct forms, the first of which consists of the keyword followed by a series of integers on the next line indicating the data to be printed (see the first example). This is the original formal in the commercial simulator and was subsequently superseded by the second format. The second format consists of the keyword followed by a series of character strings that indicate the data to be printed. In most cases the character string is the keyword used to load the data in the OPM Flow input deck, for example FIPNUM for the fluid in-place array. Its is anticipated that OPM Flow will eventually support the functionality of the second format only, the first format although recognized will be completely ignored.","parameters":[{"index":1,"name":"EQLNUM","description":"Print the equilibration region array.","units":{},"default":"N/A","value_type":"STRING"},{"index":2,"name":"FIPNUM","description":"Print the fluid in-place array.","units":{},"default":"N/A"},{"index":3,"name":"PVTNUM","description":"Print the PVT table assignment array.","units":{},"default":"N/A"},{"index":4,"name":"SATNUM","description":"Print the saturation function (relative permeability) assignment array.","units":{},"default":"N/A"}],"example":"The first example shows the original format of this keyword; although the keyword and format are recognized by OPM Flow, the format is ignored and is unlikely to be implemented in in the simulator.\n--\n-- DEFINE REGIONS SECTION REPORT OPTION (ORIGINAL FORMAT)\n–\nRPTREGS\n1 2*0 1 3*1 /\nThe next example shows the second format of the keyword which may be supported in a future release of OPM Flow.\n-- DEFINE REGIONS SECTION REPORT OPTIONS\n--\nRPTREGS\nFIPMUM EQLNUM PVTNUM SATNUM /\n| Note This keyword has the potential to produce very large print files that some text editors may have difficulty loading, coupled with the fact that reviewing the data in this format is very cumbersome. A more efficient solution is to load the *.INIT file into OPM ResInsight to view the data graphically, this also has the benefit of being able to filter the grid based on I, J, K ranges and grid properties. |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"fixed","size_count":1,"variadic_record":true},"SATNUM":{"name":"SATNUM","sections":["REGIONS"],"supported":null,"summary":"The SATNUM keyword defines the saturation tables (relative permeability and capillary pressure tables) region numbers for each grid block, as such there must be one entry for each cell in the model. The region number specifies which set of relative permeability tables (SGFN, SWFN, SOF2, SOF3, SOF32D, SGOF, SLGOF and SWOF) are used to calculate the relative permeability and capillary pressure in a grid block.","parameters":[{"index":1,"name":"SATNUM","description":"SATNUM defines an array of positive integers assigning a grid cell to a particular saturation table region. The maximum number of SATNUM regions is set by the NTSFUN variable on the TABDIMS keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"The example below sets three SATNUM regions for a 4 x 5 x 2 model.\n--\n-- DEFINE SATNUM REGIONS FOR ALL CELLS\n--\nSATNUM\n2 2 1 1 2 2 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n3 3 1 1 3 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1\n/\nAlternatively the EQUALS keyword could be employed to accomplish the same task, that is:\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nSATNUM 1 1* 1* 1* 1* 1* 1* / SET REGION 1\nSATNUM 2 1 2 1 2 1 1 / SET REGION 2\nSATNUM 3 1 2 1 2 2 2 / SET REGION 3\n/","size_kind":"array"},"SURFNUM":{"name":"SURFNUM","sections":["REGIONS"],"supported":false,"summary":"The SURFNUM keyword defines the saturation tables (relative permeability and capillary pressure tables) region numbers for each grid block, as such there must be one entry for each cell in the model. The region number specifies which set of oil-water relative permeability tables (SWFN, SOF2, SOF3, and SWOF) are used to calculate the relative permeability and capillary pressure in a grid block. In this case the SURFNUM allocated tables assume that oil and water are miscible, whereas the SATNUM allocated tables are used to allocate the immiscible saturation tables. To use this keyword the Surfactant option must have been activated by the SURFACT keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"SURFNUM","description":"SURFNUM defines an array of positive integers assigning a grid cell to a particular saturation table region. The maximum number of SURFNUM regions is set by the NTSFUN variable on the TABDIMS keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"The example below sets three SURFNUM for the model.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nSURFNUM 1 1* 1* 1* 1* 1* 1* / SET REGION 1\nSURFNUM 2 1* 1* 1* 1* 1 1 / SET REGION 2\nSURFNUM 3 1* 1* 1* 1* 2 2 / SET REGION 3\n/","size_kind":"array"},"SURFWNUM":{"name":"SURFWNUM","sections":["REGIONS"],"supported":false,"summary":"The SURFWNUM keyword defines the saturation tables (relative permeability and capillary pressure tables) region numbers for each grid block, as such there must be one entry for each cell in the mode, for when the Surfactant Wettability option has been selected. The keyword may also be used with the Low Salt Brine option, in this case the water wet curves are calculated as a function of the low and high water wet salinity curves. The region number specifies which set of relative permeability tables are used to calculate the relative permeability and capillary pressure in a grid block. Note that the keyword is obligatory if the SURFACTW keyword in the RUNSPEC section has been used to invoke the Surfactant Wettability option.","parameters":[{"index":1,"name":"SURFWNUM","description":"SURFWNUM defines an array of positive integers assigning a grid cell to a particular saturation table region. The maximum number of SURFWNUM regions is set by the NTSFUN variable on the TABDIMS keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"The example below sets three SURFWNUM regions for the model.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nSURFWNUM 1 1* 1* 1* 1* 1* 1* / SET REGION 1\nSURFWNUM 2 1 2 1 2 1 1 / SET REGION 2\nSURFWNUM 3 1 2 1 2 2 2 / SET REGION 3\n/","size_kind":"array"},"TNUM":{"name":"TNUM","sections":["REGIONS"],"supported":false,"summary":"The TNUM keyword defines the regions associated with the series of tracers associated with a phase (oil, water, or gas) in the model. The maximum number of tracers for each phase are declared on the TRACER keyword in the RUNSPEC section. Unlike other keywords, the TNUM keyword must be concatenated with the phase and the name of the tracer declared by TRACER keyword in the PROPS section. Table 9.24outlines the format of the TNUM keyword name.","parameters":[{"index":1,"name":"TNUMREG","description":"TUNREG defines an array of positive integers assigning a grid cell to a particular tracer table region. The maximum number of TNUMREG regions is set by the NTTRVD variable on the EQLDIMS keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"First define four passive tracers one for a free gas, one for dissolved gas, one for oil and one to track the water.\n--\n-- DEFINE TRACER NAMES\n--\n-- TRACER TRACER\n-- NAME PHASE\n-- ------ ------\nTRACER\n'GCG' 'GAS' / GAS CAP GAS\n'DGS' 'GAS' / DISOLVED GAS\n'OIL' 'OIL' / OIL\n'WAT' 'WAT' / WAT\n/\nGiven a 100 x 100 x 5 grid with DISGAS activated in the RUNSPEC section, then the following TNUM keywords define the various tracer regions given that NTTRVD equals four on the EQLDIMS keyword in the RUNSPEC section.\n--\n-- DEFINE PASSIVE TRACER CONCENTRATION REGIONS\n--\nTNUMFGCG\n1000*1\n1000*2\n1000*2\n1000*2\n1000*2\n/\nTNUMSDGS\n1000*1\n1000*1\n1000*1\n1000*1\n1000*1\n/\nTNUMFOIL\n1000*3\n1000*3\n1000*3\n1000*3\n1000*3\n/\nTNUMFWAT\n1000*4\n1000*4\n1000*4\n1000*4\n1000*4\n/\nThe keyword name is derived from the TNUM keyword, plus either F or S, plus the tracer name declared in the TRACER keyword. For example for the gas cap (free gas) this would be TNUM+F+GAS to give the TNUMFGAS keyword. And for the dissolved (solution) gas this would be TNUM+S+DGS resulting in the TNUMSDGS keyword.","size_kind":"array"},"TRKPF":{"name":"TRKPF","sections":["REGIONS"],"supported":false,"summary":"The TRKPF keyword defines the regions associated with the series of partition tracers and the partitioning tables allocated to grid blocks in the model, for when the Partitioned Tracer option has been enabled by the PARTTRAC keyword in the RUNSPEC section. The maximum number of tracers for each phase are declared on the TRACERS keyword in the RUNSPEC section. Unlike other keywords, the TRKPF keyword must be concatenated with the name of the tracer declared by TRACER keyword in the PROPS section. Table 9.26outlines the format of the TRKPF keyword name.","parameters":[{"index":1,"name":"TRKPFREG","description":"TRKPFREG defines an array of positive integers assigning a grid cell to a particular tracer table region. The maximum number of TRKPFREG regions is set by the NTTRVD variable on the EQLDIMS keyword in the RUNSPEC section.","units":{},"default":"1"}],"example":"First define one mult-partitioned tracer for the water phase.\n--\n-- DEFINE TRACER NAMES\n--\n-- TRACER TRACER TRACER PARTITION NUM ADSOR\n-- NAME PHASE VOLUME PHASE K(P) PHASE\n-- ------ ------ ------ --------- ---- -----\nTRACER\n'WAT' 'WAT' 1* MULT 2 ALL / WAT\n/\nThen for a given a 100 x 100 x 5 grid assign the partitioned tracer regions and K(P) tables, based on two regions.\n--\n-- DEFINE PARTITIONED TRACER REGIONS\n--\nTRKPFWAT\n1000*1\n1000*1\n1000*2\n1000*2\n1000*2\n/\nThe keyword name is derived from the TRKPF keyword, plus the tracer name declared in the TRACER keyword, in this case the keyword name is TRKPFWAT.","size_kind":"array"},"WH2NUM":{"name":"WH2NUM","sections":["REGIONS"],"supported":false,"summary":"The WH2NUM keyword defines the two phase Water-Alternating-Gas (“WAG”) hysteresis tables (relative permeability and capillary pressure tables) region numbers for each grid block, for when the hysteresis option has been activated by the WAGHYSTR variable on the SATOPTS keyword in the RUNSPEC section. The region number specifies which set of relative permeability tables (SGFN, SWFN, SOF2, SOF3, SOF32D, SGOF, SLGOF and SWOF) are used to calculate the relative permeability and capillary pressure in a grid block. Note that this keyword if the two phase water relative permeabilities WAG option.","parameters":[{"index":1,"name":"WH2NUM","description":"WH2NUM defines an array of positive integers assigning a grid cell to a particular saturation table region. The maximum number of WH2NUM regions is set by the NTSFUN variable on the TABDIMS keyword in the RUNSPEC section.","units":{},"default":"Taken from cell allocated SATNUM"}],"example":"The example below sets three WH2NUM regions for a model.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nWH2NUM 1 1* 1* 1* 1* 1* 1* / SET REGION 1\nWH2NUM 2 1 2 1 2 1 1 / SET REGION 2\nWH2NUM 3 1 2 1 2 2 2 / SET REGION 3\n/","size_kind":"array"},"WH3NUM":{"name":"WH3NUM","sections":["REGIONS"],"supported":false,"summary":"The WH3NUM keyword defines the three phase Water-Alternating-Gas (“WAG”) hysteresis tables (relative permeability and capillary pressure tables) region numbers for each grid block, for when the hysteresis option has been activated by the WAGHYSTR variable on the SATOPTS keyword in the RUNSPEC section. The region number specifies which set of relative permeability tables (SGFN, SWFN, SOF2, SOF3, SOF32D, SGOF, SLGOF and SWOF) are used to calculate the relative permeability and capillary pressure in a grid block. Note that this keyword if the three phase water relative permeabilities WAG option.","parameters":[{"index":1,"name":"WH3NUM","description":"WH3NUM defines an array of positive integers assigning a grid cell to a particular saturation table region. The maximum number of WH3NUM regions is set by the NTSFUN variable on the TABDIMS keyword in the RUNSPEC section.","units":{},"default":"Taken from cell allocated SATNUM"}],"example":"The example below sets three WH3NUM regions for a model.\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nWH3NUM 1 1* 1* 1* 1* 1* 1* / SET REGION 1\nWH3NUM 2 1 2 1 2 1 1 / SET REGION 2\nWH3NUM 3 1 2 1 2 2 2 / SET REGION 3\n/","size_kind":"array"},"APIVD":{"name":"APIVD","sections":["SOLUTION"],"supported":false,"summary":"The APIVD keyword defines the oil API gravity versus depth tables for each equilibration region when API Tracking as been activated by the API keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"DEPTH","description":"A columnar vector of real monotonically increasing down the column values that defines the depth values for the corresponding API gravity values, API.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":["Length","1"]},{"index":2,"name":"API","description":"A columnar vector of real values that defines the API gravity at the corresponding DEPTH. The American Petroleum Institute (“API”) classifies oils based on an API gravity (γAPI), or degrees API (oAPI), the relationship between relative density (γo) of oil and API gravity (γAPI) is given by: [%gamma SUB { API } ~ = ~ { 141.5 } OVER { %gamma SUB { o }}~-~ 131.5]","units":{"field":"oAPI","metric":"oAPI","laboratory":"oAPI"},"default":"None"}],"example":"Given NTEQUL equals three and NDRXVD is greater than or equal to two on the EQLDIMS keyword in the RUNSPEC section, then the following example defines the bubble-point versus depth functions.\n--\n-- DEPTH API\n-- GRAVITY\n-- ------ --------\nAPIVD\n3000.0 41.10\n8000.0 41.10 / API VS DEPTH EQUIL REGN 01\n-- ------ --------\n3000.0 41.10\n8000.0 38.50 / API VS DEPTH EQUIL REGN 02\n-- ------ --------\n3000.0 41.10\n8000.0 38.50 / API VS DEPTH EQUIL REGN 03\nHere three tables are entered; the first table has a constant API gravity versus depth relationship for equilibration region number one and the other two equilibration regions have the API gravity varying with depth.","size_kind":"fixed","variadic_record":true},"AQANCONL":{"name":"AQANCONL","sections":["SOLUTION"],"supported":false,"summary":"The AQANCON keyword defines how analytical aquifers are connected to a Local Grid Refinement (\"LGR\") grid, this includes the Carter-Tracy, Fetkovich and Constant Flux analytical aquifers, all of which are implemented in OPM Flow. Carter-Tracy analytical aquifers are characterized by the AQUCT keyword in the GRID section and Fetkovich analytical aquifers are defined by either the AQUFET or AQUFETP keywords in the SOLUTION section. Finally, the Constant Flux aquifer is defined by the AQUFLUX keyword in SOLUTION section.","parameters":[{"index":1,"name":"AQUID","description":"AQUID is a positive integer greater than or equal to one and less than the maximum number of analytical aquifers as defined by the NANAQU variable on the AQUDIMS keyword in the RUNSPEC section, that defines the aquifer to be connected to the grid.","units":{},"default":"None","value_type":"INT"},{"index":2,"name":"LGRNAME","description":"A character string of up to eight characters in length that defines the name of the LGR that will connect to an analytical aquifer AQUID. The LGR must have been previously defined by the either the CARFIN (Cartesian LGR grid) keyword, or the RADIN/RADIN4 (radial LGR grid) keyword in the GRID section.","units":{},"default":"None","value_type":"STRING"},{"index":3,"name":"I1","description":"A positive integer that defines the LGR's lower bound of the cells in the I-direction to be connected to the aquifer, and must be greater than or equal to one and less than or equal to I2 and NX on the CARFIN keyword for Cartesian grids.","units":{},"default":"1","value_type":"INT"},{"index":4,"name":"I2","description":"A positive integer that defines the LGR's upper bound of the cells in the I-direction to be connected to the aquifer, and must be greater than or equal to I1 and less than or equal to NX on the CARFIN keyword for Cartesian grids.","units":{},"default":"NX","value_type":"INT"},{"index":5,"name":"J1","description":"A positive integer that defines the LGR's lower bound of the cells in the J-direction to be connected to the aquifer, and must be greater than or equal to one and less than or equal to J2 and NY on the CARFIN keyword for Cartesian grids.","units":{},"default":"1","value_type":"INT"},{"index":6,"name":"J2","description":"A positive integer that defines the LGR's upper bound of the cells in the J-direction to be connected to the aquifer, and must be greater than or equal to JI and less than or equal to NY on the CARFIN keyword for Cartesian grids.","units":{},"default":"NY","value_type":"INT"},{"index":7,"name":"K1","description":"A positive integer that defines the LGR's lower bound of the cells in the K-direction to be to be connected to the aquifer, and must be greater than or equal to one and less than or equal to K2 and NZ on the CARFIN keyword for Cartesian grids.","units":{},"default":"1","value_type":"INT"},{"index":8,"name":"K2","description":"A positive integer that defines the LGR's upper bound of the cells in the K-direction to be connected to the aquifer, and must be greater than or equal to KI and less than or equal to NZ on the CARFIN keyword for Cartesian grids.","units":{},"default":"NZ","value_type":"INT"},{"index":9,"name":"AQUFACE","description":"AQUFACE is a character string that sets the connection “face” of the cells declared by this record and should be set to one of the following: X+, Y+, or Z+ for the positive direction, or X-, Y- or Z- for the negative direction transmissibilities. I+, J+, or K+ for the positive direction, or I-, J- or K- for the negative direction transmissibilities.","units":{},"default":"None","value_type":"STRING"},{"index":10,"name":"AQUFLUX","description":"AQUFLUX is a positive real value that sets the fraction of the total influx between the aquifer and the defined cells declared on this keyword. If defaulted the cell face for each cell is applied and if a values is declared then this values is applied to all cells declared by this record.","units":{"field":"ft2","metric":"m2","laboratory":"cm2"},"default":"1*","value_type":"DOUBLE","dimension":"Length*Length"},{"index":11,"name":"AQUCOEF","description":"AQUCOEF is a real positive values that scales the calculated connection between the aquifer and the cells declared on this record.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0","value_type":"DOUBLE","dimension":"1"},{"index":12,"name":"AQUOPT","description":"AQUOPT is a character string that sets the cell face connection and should be set to one of the following: YES: Aquifer connections can adjoin to active cells allowing for connections inside the reservoir grid. It is not recommended to use this option without thoroughly checking the connections in the model. NO: Aquifer connections cannot adjoin to active cells preventing connections inside the reservoir grid. This is the recommended and the default value.","units":{},"default":"NO","value_type":"STRING"}],"example":"The following example defines aquifer number one connected to the J- face of various cells in the LGROP001 LGR, and a second basal aquifer connected to the K+ face.\n--\n-- LGR ANALYTIC AQUIFER CONNECTION\n--\n-- ID LGR ---------- BOX --------- CONNECT AQF AQF ADJOIN\n-- NUM NAME I1 I2 J1 J2 K1 K2 FACE INFLX MULTI CELLS\nAQANCONL\n1 LGROP001 1 10 1 15 1 10 J- 1* 1.0 'NO' /\n1 LGROP001 1 10 1 15 12 18 J- 1* 1.0 'NO' /\n2 LGROP001 1 10 1 15 20 20 K+ 1* 1.0 'NO' /\n/\nSee the AQUCT keyword in the GRID section for a complete example on defining and connecting a Carter-Tracy aquifer to a simulation grid.\n| Note If the AQANCONL keyword has been utilized in the run deck then OPM Flow will write the AQUIFERA array to the *.INIT file in order to visualize the aquifer connections in OPM ResInsight. This is accomplished by setting the AQUIFERA value to 2(AQUID-1) for cells connected to aquifer AQUID. If a cell is connected to multiple analytical aquifers then AQUIFERA is summed for all aquifers connected to a cell. Note that connecting cells to multiple aquifers is best avoided. |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":12,"size_kind":"list"},"AQANNC":{"name":"AQANNC","sections":["SOLUTION"],"supported":false,"summary":"AQANNC defines the analytic aquifer non-neighbor connections.","parameters":[{"index":1,"name":"AQUIFER_NUMBER","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"IX","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"IY","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"IZ","description":"","units":{},"default":"","value_type":"INT"},{"index":5,"name":"AREA","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Length*Length"}],"example":"","expected_columns":5,"size_kind":"list"},"AQANTRC":{"name":"AQANTRC","sections":["SOLUTION"],"supported":false,"summary":"The AQANTRC keyword defines the initial tracer concentrations for analytic aquifers that have previously been defined by the AQCT keyword in the GRID, PROPS, or SOLUTION sections for Carter-Tracy analytical aquifers, or the AQFET and AQFETP keywords in the SOLUTION section for Fetkovich analytical aquifers.","parameters":[{"index":1,"name":"AQUIFER_ID","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"TRACER","description":"","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"VALUE","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","expected_columns":3,"size_kind":"list"},"AQUALIST":{"name":"AQUALIST","sections":["SOLUTION"],"supported":false,"summary":"The AQUALIST keyword defines named lists of analytic aquifers identified by aquifer numbers for greater readability in the output.","parameters":[{"index":1,"name":"AQUIFER_LIST","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"LIST","description":"","units":{},"default":"","value_type":"INT"}],"example":"","size_kind":"list","variadic_record":true},"AQUCHGAS":{"name":"AQUCHGAS","sections":["SOLUTION","SCHEDULE"],"supported":false,"summary":"The AQUCHGAS keyword defines the properties of constant pressure gas analytical aquifers.","parameters":[{"index":1,"name":"AQUIFER_ID","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"DATUM_DEPTH","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":3,"name":"GAS_PRESSURE","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":4,"name":"AQUIFER_PROD_INDEX","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"GasSurfaceVolume/Time*Pressure"},{"index":5,"name":"TABLE_NUM","description":"","units":{},"default":"1","value_type":"INT"},{"index":6,"name":"TEMPERATURE","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Temperature"}],"example":"","expected_columns":6,"size_kind":"list"},"AQUCHWAT":{"name":"AQUCHWAT","sections":["SOLUTION","SCHEDULE"],"supported":false,"summary":"The AQUCHWAT keyword defines the properties of constant pressure water analytical aquifers.","parameters":[{"index":1,"name":"AQUIFER_ID","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"DATUM_DEPTH","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":3,"name":"INPUT_4","description":"","units":{},"default":"","value_type":"STRING"},{"index":4,"name":"ITEM4","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":5,"name":"AQUIFER_PROD_INDEX","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time*Pressure"},{"index":6,"name":"TABLE_NUM","description":"","units":{},"default":"1","value_type":"INT"},{"index":7,"name":"INIT_SALT_CONC","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"Mass/LiquidSurfaceVolume"},{"index":8,"name":"MINIMUM","description":"","units":{},"default":"-1e+200","value_type":"DOUBLE"},{"index":9,"name":"MAXIMUM","description":"","units":{},"default":"1e+200","value_type":"DOUBLE"},{"index":10,"name":"IGNORE_CAP_PRESSURE","description":"","units":{},"default":"NO","value_type":"STRING"},{"index":11,"name":"MIN_FLOW_PR_CONN","description":"","units":{},"default":"-1e+200","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time"},{"index":12,"name":"MAX_FLOW_PR_CONN","description":"","units":{},"default":"1e+200","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time"},{"index":13,"name":"REMOVE_DEPTH_TERM","description":"","units":{},"default":"NO","value_type":"STRING"},{"index":14,"name":"IMPORT_MAX_MIN_FLOW_RATE","description":"","units":{},"default":"0","value_type":"INT"},{"index":15,"name":"TEMPERATURE","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Temperature"}],"example":"","expected_columns":15,"size_kind":"list"},"AQUFET":{"name":"AQUFET","sections":["SOLUTION"],"supported":false,"summary":"The AQUFET keyword defines Fetkovich287\n Fetkovich, M. J. “A Simplified Approach to Water Influx Calculations - Finite Aquifer Systems,” Journal of Petroleum Technology, (1971) 23, No. 7, 814-828. analytical aquifers, the aquifer properties, together with the cell connections to the aquifer. Each row entry in the AQUFETP keyword defines one Fetkovich analytical aquifer and one cell face to be connected to the aquifer.","parameters":[{"index":1,"name":"DATUM","description":"DATUM is a single positive value that defines the Fetkovich reference datum depth for PRESS.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":"Length"},{"index":2,"name":"PRESS","description":"PRESS is a single positive value that defines the aquifer pressure at DATUM. If PRESS is defaulted then the simulator will set the aquifer’s initial reservoir pressure to be in equilibrium with the cells the aquifer is contacted to. Defaulting this parameter will avoid inconsistent equilibration pressures between the reservoir cells and the aquifer.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1*","value_type":"DOUBLE","dimension":"Pressure"},{"index":3,"name":"PORV","description":"A real positive value that defines the initial water volume of the aquifer.","units":{"field":"stb","metric":"sm3","laboratory":"scc"},"default":"None","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume"},{"index":4,"name":"COMP","description":"COMP is a real number defining the total compressibility (Ct) of the aquifer, that is the rock compressibility (Cf) plus the water compressibility (Cw) at the aquifer datum pressure (DATUM) and is defined as: [C sub{t}~=~ C sub{f}`+`C sub {w}]","units":{"field":"1/psia","metric":"1/barsa","laboratory":"1/atma"},"default":"None","value_type":"DOUBLE","dimension":"1/Pressure"},{"index":5,"name":"PI","description":"A real positive number that defines the aquifer productivity index based on the aquifer influx rate per unit pressure drop.","units":{"field":"stb/d/psia","metric":"sm3/barsa","laboratory":"scc/hr/atma"},"default":"None","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Pressure*Time"},{"index":6,"name":"PVTW","description":"A positive integer that defines the aquifer’s PVTW water property table.","units":{},"default":"1","value_type":"INT"},{"index":7,"name":"I1","description":"A positive integer that defines the lower bound of the cells in the I-direction to be connected to the aquifer and must be greater than or equal to one and less than or equal to I2 and NX.","units":{},"default":"1","value_type":"INT"},{"index":8,"name":"I2","description":"A positive integer that defines the upper bound of the cells in the I-direction to be connected to the aquifer and must be greater than or equal to I1 and less than or equal to NX","units":{},"default":"NX","value_type":"INT"},{"index":9,"name":"J1","description":"A positive integer that defines the lower bound of the cells in the J-direction to be connected to the aquifer and must be greater than or equal to one and less than or equal to J2 and NY.","units":{},"default":"1","value_type":"INT"},{"index":10,"name":"J2","description":"A positive integer that defines the upper bound of the cells in the J-direction to be connected to the aquifer and must be greater than or equal to JI and less than or equal to NY.","units":{},"default":"NY","value_type":"INT"},{"index":11,"name":"K1","description":"A positive integer that defines the lower bound of the cells in the K-direction to be to be connected to the aquifer and must be greater than or equal to one and less than or equal to K2 and NZ.","units":{},"default":"1","value_type":"INT"},{"index":12,"name":"K2","description":"A positive integer that defines the upper bound of the cells in the K-direction to be connected to the aquifer and must be greater than or equal to KI and less than or equal to NZ.","units":{},"default":"NZ","value_type":"INT"},{"index":13,"name":"AQUFACE","description":"AQUFACE is a character string that sets the connection “face” of the cells declared by this record and should be set to one of the following: X+, Y+, or Z+ for the positive direction, or X-, Y- or Z- for the negative direction transmissibilities. I+, J+, or K+ for the positive direction, or I-, J- or K- for the negative direction transmissibilities.","units":{},"default":"None","value_type":"STRING"},{"index":14,"name":"SALTCON","description":"SALTCON is a real positive number that defines the initial salt concentration in the aquifer. This variable is ignored by OPM Flow.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"0.0","value_type":"DOUBLE","dimension":"Concentration"}],"example":"Given the following grid and aquifer dimensions in the RUNSPEC section:\n-- ==============================================================================\n--\n-- RUNSPEC SECTION\n--\n-- ==============================================================================\nRUNSPEC --\n-- MAX MAX MAX\n-- NDIVIX NDIVIY NDIVIZ\nDIMENS\n20 1 5 /\n-- AQF AQF AQF AQF AQF AQF AQF AQF\n-- MXAQN MXNAQC NIFTBL NRIFTB NANAQU NCAMAX MXNALI MXAAQL\nAQUDIMS\n1* 1* 5 100 1 1* 1* 1* /\nThe Fetkovich Analytical aquifer is defined in the SOLUTION sections as:\n-- ==============================================================================\n--\n-- SOLUTION SECTION\n--\n-- ==============================================================================\nSOLUTION --\n-- FETKOVICH AQUIFER DESCRIPTION AND CONNECTIONS\n--\n-- DATUM AQF AQF AQF AQF AQF -------- BOX ------- CONNECT SALT\n-- DEPTH PRESS VOLM COMP PI PVT I1 I2 J1 J2 K1 K2 FACE CONC\n--\nAQUFET\n1130. 1* 1.0E+12 3.0E-5 500E3 1 1 1 1 1 1 1 'J-' /\nHere one Fetkovich Analytical aquifer is connected to a single cell (1, 1, 1) at the J- face (or X- face) of the grid.\n| Note If the model is unstable then this may be due to an aquifer not being in equilibrium with the connecting reservoir blocks, for example the aquifer is connected to only hydrocarbon reservoir cells. Try commenting out the aquifer and see if this resolves the instabilities. |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":14,"size_kind":"list"},"AQUFETP":{"name":"AQUFETP","sections":["SOLUTION","SCHEDULE"],"supported":null,"summary":"The AQUFETP keyword defines Fetkovich288\n Fetkovich, M. J. “A Simplified Approach to Water Influx Calculations - Finite Aquifer Systems,” Journal of Petroleum Technology, (1971) 23, No. 7, 814-828. analytical aquifers and the aquifer properties. Each row entry in the AQUFETP keyword defines one Fetkovich analytical aquifer. In order to fully define this type of aquifer, the aquifer must be connected to the reservoir using the AQUANCON keyword in the GRID or SOLUTION sections.","parameters":[{"index":1,"name":"AQUID","description":"A positive integer greater than or equal to one and less than or equal to NANAQ on the AQUDIMS keyword in the RUNSPEC section, that defines the Fetkovich aquifer number.","units":{},"default":"1","value_type":"INT"},{"index":2,"name":"DATUM","description":"DATUM is a single positive value that defines the Fetkovich reference datum depth for PRESS.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":"Length"},{"index":3,"name":"PRESS","description":"PRESS is a single positive value that defines the aquifer pressure at DATUM. If PRESS is defaulted then the simulator will set the aquifer’s initial reservoir pressure to be in equilibrium with the cells the aquifer is contacted to. Defaulting this parameter will avoid inconsistent equilibration pressures between the reservoir cells and the aquifer.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1*","value_type":"DOUBLE","dimension":"Pressure"},{"index":4,"name":"PORV","description":"A real positive value that defines the initial water volume of the aquifer.","units":{"field":"stb","metric":"sm3","laboratory":"scc"},"default":"None","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume"},{"index":5,"name":"COMP","description":"COMP is a real number defining the total compressibility (Ct) of the aquifer, that is the rock compressibility (Cf) plus the water compressibility (Cw) at the aquifer datum pressure (DATUM) and is defined as: [C sub{t}~=~ C sub{f}`+`C sub {w}]","units":{"field":"1/psia","metric":"1/barsa","laboratory":"1/atma"},"default":"None","value_type":"DOUBLE","dimension":"1/Pressure"},{"index":6,"name":"PI","description":"A real positive number that defines the aquifer productivity index based on the aquifer influx rate per unit pressure drop.","units":{"field":"stb/d/psia","metric":"sm3/d/barsa","laboratory":"scc/hr/atma"},"default":"None","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Pressure*Time"},{"index":7,"name":"PVTW","description":"A positive integer that defines the aquifer’s PVTW water property table.","units":{},"default":"1","value_type":"INT"},{"index":8,"name":"SALTCON","description":"SALTCON is a real positive number that defines the initial salt concentration in the aquifer, for when the simulator's Brine Model has been activated via the BRINE keyword in the RUNSPEC section. This variable is ignored by OPM Flow.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"0.0","value_type":"DOUBLE","dimension":"Concentration"},{"index":9,"name":"TEMP","description":"TEMP is a real positive number that defines the initial temperature of the aquifer at DATUM for use with OPM Flow's thermal option. The THERMAL keyword in the RUNSPEC section must be activated to use this option.","units":{"field":"oF","metric":"oC","laboratory":"oC"},"default":"1*","value_type":"DOUBLE","dimension":"Temperature"}],"example":"Given the following grid and aquifer dimensions in the RUNSPEC section:\n-- ==============================================================================\n--\n-- RUNSPEC SECTION\n--\n-- ==============================================================================\nRUNSPEC\n--\n-- MAX MAX MAX\n-- NDIVIX NDIVIY NDIVIZ\nDIMENS\n20 1 5 /\n-- AQF AQF AQF AQF AQF AQF AQF AQF\n-- MXAQN MXNAQC NIFTBL NRIFTB NANAQU NCAMAX MXNALI MXAAQL\nAQUDIMS\n1* 1* 5 100 1 1* 1* 1* /\nThe Fetkovich analytical aquifer is defined in the SOLUTION sections as:\n-- ==============================================================================\n--\n-- SOLUTION SECTION\n--\n-- ==============================================================================\nSOLUTION --\n-- FETKOVICH AQUIFER DESCRIPTION\n--\n-- ID DATUM AQF AQF AQF AQF AQF SALT\n-- NUM DEPTH PRESS VOLM COMP PI PVT CONC\n--\nAQUFETP\n1 1130. 1* 1.0E+12 3.0E-5 500E3 1 0.0 /\n/\nAnd the connection of the aquifer is set in the GRID or the SOLUTION sections as:\n--\n-- ANALYTIC AQUIFER CONNECTION\n--\n-- ID ---------- BOX --------- CONNECT AQF AQF ADJOIN\n-- NUMBER I1 I2 J1 J2 K1 K2 FACE INFLX MULTI CELLS\nAQUANCON\n1 1 1 1 1 1 1 J- 1.0 1.0 'NO' /\n/\nHere one Fetkovich analytical aquifer is connected to a single cell (1, 1, 1) at the J- face (or Y- face) of the cell.\n| Note If the model is unstable then this may be due to an aquifer not being in equilibrium with the connecting reservoir blocks, for example if the aquifer is connected to some hydrocarbon reservoir cells. Try commenting out the aquifer and see if this resolves the instabilities, and if so amend the aquifer connections accordingly. |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":9,"size_kind":"list"},"AQUFLUX":{"name":"AQUFLUX","sections":["SOLUTION","SCHEDULE"],"supported":null,"summary":"The AQUFLUX keyword defines the properties of Constant Flux Analytical Aquifers, that allows for a constant water influx to the connected grid blocks. This type of aquifer is connected to the model using either the AQUANCON keyword for global cells, or the AQUANCONL keyword for cells belonging to a Local Grid Refinement (\"LGR\"), both the aforementioned keywords are in the GRID and SOLUTION sections. The keyword itself may be utilized in both the SOLUTION and SCHEDULE sections, with subsequent entries overwriting the previous entry.","parameters":[{"index":1,"name":"AQUID","description":"A positive integer greater than or equal to one and less than or equal to NANAQ on the AQUDIMS keyword in the RUNSPEC section, that defines the AQUFLUX aquifer number.","units":{"field":"stb/day/ft2","metric":"sm3/day/m2","laboratory":"scc/hour/cm2"},"default":"1","value_type":"INT"},{"index":2,"name":"FLUX","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time*Length*Length"},{"index":3,"name":"SALTCON","description":"SALTCON is a real positive number that defines the initial salt concentration in the aquifer, for when with simulator's Brine Model has been activated via the BRINE keyword in the RUNSPEC section. This variable is ignored by OPM Flow.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"0.0","value_type":"DOUBLE","dimension":"Density"},{"index":4,"name":"TEMP","description":"TEMP is a real positive number that defines the initial temperature of the aquifer for use with OPM Flow's thermal option. The THERMAL keyword in the RUNSPEC section must be activated to use this option. If the THERMAL keyword is absent from the input deck, then the parameter is ignored.","units":{"field":"oF","metric":"oC","laboratory":"oC"},"default":"1*","value_type":"DOUBLE","dimension":"Temperature"},{"index":5,"name":"PRESS","description":"PRESS is a single positive value that defines the aquifer pressure for use with OPM Flow's thermal option. The THERMAL keyword in the RUNSPEC section must be activated to use this option. If the THERMAL keyword is absent from the input deck, then the parameter is ignored.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1*","value_type":"DOUBLE","dimension":"Pressure"}],"example":"Given a total of five analytical aquifers as declared by the NANAQ parameter on the AQUDIMS keyword being set to five, of which three are Constant Flux Aquifers and two Carter-Tracy Aquifers, then:\n--\n-- CONSTANT FLUX AQUIFER DESCRIPTION\n--\n-- ID WATER SALT AQF AQU\n-- NUM INFLUX CONC TEMP PRES\n--\nAQUFLUX\n1 0.0004 1* 1* 1* /\n2 0.0005 1* 1* 1* /\n3 0.0003 1* 1* 1* /\n/\n--\n-- CARTER-TRACY AQUIFER DESCRIPTION\n--\n-- ID DATUM AQF AQF AQF AQF AQF AQF INFL PVT AQU\n-- NUM DEPTH PRESS PERM PORO RCOMP RE DZ ANGLE NUM TAB\n--\nAQUCT\n4 2000.0 269 100.0 0.30 3.0e-5 330 10.0 360.0 1 2 /\n5 2000.0 269 100.0 0.30 3.0e-5 330 10.0 360.0 1 2 /\n/\nDefines three Constant Flux Aquifers and three Carter-Tracy Aquifers, and the connection of the aquifers are set in the GRID or SOLUTION sections via:\n--\n-- ANALYTIC AQUIFER CONNECTION\n--\n-- ID ---------- BOX --------- CONNECT AQF AQF ADJOIN\n-- NUMBER I1 I2 J1 J2 K1 K2 FACE INFLX MULTI CELLS\nAQUANCON\n1 1 198 1 14 1 10 J- 1* 1.0 'NO' /\n2 1 198 1 14 12 22 J- 1* 1.0 'NO' /\n3 1 198 1 14 23 54 J- 1* 1.0 'NO' /\n4 1 198 1 14 61 70 J- 1* 1.0 'NO' /\n5 1 198 15 172 71 71 K+ 1* 1.0 'NO' /\n/\n| [q_w`=`AQUFLUX(AQFLUX) ` times ` A_( i, j, k) ` times ` AQUANCON(AQUCOEF)] | (10.14) |\n|----------------------------------------------------------------------------|---------|","expected_columns":5,"size_kind":"list"},"BC":{"name":"BC","sections":["SOLUTION"],"supported":false,"summary":"The BC keyword defines the boundary conditions for the model, and can be used to set boundary conditions for when external influx or efflux volumes are influencing the reservoir pressure and production history. For example, when the average reservoir pressure remains constant throughout the production period due to water influx, or gas migration from an external source.","parameters":[{"index":1,"name":"I1","description":"A positive integer that defines the lower bound of the grid in the I-direction for which the boundary conditions are to be applied, must be greater than or equal 1 and less than or equal to I2 and NX.","units":{},"default":"1","value_type":"INT"},{"index":2,"name":"I2","description":"A positive integer that defines the upper bound of the grid in the I-direction for which the boundary conditions are to be applied, must be greater than or equal to II and less than or equal to NX","units":{},"default":"NX","value_type":"INT"},{"index":3,"name":"J1","description":"A positive integer that defines the lower bound of the grid in the J-direction for which the boundary conditions are to be applied, must be greater than or equal 1 and less than or equal to J2 and NY.","units":{},"default":"1","value_type":"INT"},{"index":4,"name":"J2","description":"A positive integer that defines the upper bound of the grid in the J-direction for which the boundary conditions are to be applied, must be greater than or equal to JI and less than or equal to NY.","units":{},"default":"NY","value_type":"INT"},{"index":5,"name":"K1","description":"A positive integer that defines the lower bound of the grid in the K-direction for which the boundary conditions are to be applied, must be greater than or equal to one and less than or equal to K2 and NZ.","units":{},"default":"1","value_type":"INT"},{"index":6,"name":"K2","description":"A positive integer that defines the upper bound of the grid in the K-direction for which the boundary conditions are to be applied, must be greater than or equal to KI and less than or equal to NZ.","units":{},"default":"NZ","value_type":"INT"},{"index":7,"name":"DIRECT","description":"A character string that defines the direction to apply the boundary conditions, and should be set to one of the following X, Y, or Z for the positive direction, or X-, Y- or Z- for the negative direction.","units":{},"default":"None","value_type":"STRING"},{"index":8,"name":"TYPE","description":"A defined character string that defines the type of boundary condition to be applied, and should be set to one of the following character strings: DIRICHLET: for a user defined boundary conditions. In this case, items (1) through (7) must be set, together with PHASE for the fluid type, and PRESS and TEMP for the constant pressure and temperature boundary conditions. This option is currently not supported but will be available in the next release. FREE: for the initial state of the boundary to be kept throughout the simulation, that is a constant boundary condition. For this option only items (1) through (7) need to be defined. RATE: for the boundary to have a constant influx or efflux rate. Again items (1) through (7) are required, plus PHASE for the fluid type, and RATE to set the PHASE rate. Only the FREE and RATE options are currently supported; however the next release will support the DIRICHLET option.","units":{},"default":"None","value_type":"STRING","options":["DIRICHLET","FREE","RATE"]},{"index":9,"name":"PHASE","description":"A defined character string that sets fluid type used in the boundary calculations, and should be set to one of the following character strings: GAS: the gas phase will be used to control the boundary conditions for when the TYPE has been set to DIRICHLET or RATE. OIL: the oil phase will be used to control the boundary conditions for when the TYPE has been set to DIRICHLET or RATE. WATER or WAT: the water phase will be used to control the boundary conditions for when the TYPE has been set to DIRICHLET or RATE. PHASE must be declared if TYPE has been set to either DIRICHLET or RATE.","units":{},"default":"None","value_type":"STRING","options":["GAS","OIL","WAT"]},{"index":10,"name":"RATE","description":"A real value that defines the constant surface oil, gas or water rate to be injected or withdrawn at the boundary, for when TYPE has been set to RATE. Note a negative value implies an injection rate, whereas, a positive value indicates a withdrawal rate.","units":{"field":"Liquid: stb/day Gas: Mscf/day","metric":"Liquid: sm3/day Gas: sm3/day","laboratory":"Liquid: scc/hr Gas: scc/hr"},"default":"0,0","value_type":"DOUBLE","dimension":"Mass/Time*Length*Length"},{"index":11,"name":"PRESS","description":"PRESS is a real positive value that defines the constant pressure boundary condition. PRESS should only be entered if TYPE has been set to DIRICHLET. If the pressure at the boundary is less than PRESS, then the fluid type declared via PHASE will flow across the boundary. The default value of 1* will use the simulator's calculated value based on data entered via the EQUIL keyword in the SOLUTION section.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1*","value_type":"DOUBLE","dimension":"Pressure"},{"index":12,"name":"TEMP","description":"TEMP is a real positive number that defines the constant temperature boundary condition. TEMP should only be entered if TYPE has been set to DIRICHLET. The default value of 1* will use the simulator's calculated value based on data entered via one of the following reservoir temperature keywords: RTEMP, RTEMPA, RTEMPVD, TEMPI, or TEMPVD, in the SOLUTION section. Note that all of the aforementioned reservoir temperature keywords, except for TEMPI, may also be used in the PROPS section as well.","units":{"field":"oF","metric":"oC","laboratory":"oC"},"default":"1*","value_type":"DOUBLE","dimension":"Temperature"}],"example":"The first example shows how to set a constant pressure boundary using TYPE equal to FREE:\n--\n-- DEFINE MODEL BOUNDARY CONDITIONS (OPM FLOW SOLUTION GRID KEYWORD)\n--\n-- ---------- BOX --------- BC BC BC BC BC BC\n-- I1 I2 J1 J2 K1 K2 DIRC TYPE PHASE RATE PRESS TEMP\nBC\n1 1 1 1* 1 1* X- FREE 1* 1* 1* 1* /\n1 1* 1 1 1 1* Y FREE /\n/\nWith this option it is only necessary to define the boundary cells and all the other parameters (PHASE, RATE, PRESS, and TEMP) can be defaulted, as they are ignored for when TYPE equals FREE.\nThe next example is based on NX, NY and NZ equal to 20, 1, 10 respectively, on the DIMENS keyword in the RUNSPEC section, and shows how different boundary types can be assigned to different parts of the model.\n--\n-- DEFINE MODEL BOUNDARY CONDITIONS (OPM FLOW SOLUTION GRID KEYWORD)\n--\n-- ---------- BOX --------- BC BC BC BC BC BC\n-- I1 I2 J1 J2 K1 K2 DIRC TYPE PHASE RATE PRESS TEMP\nBC\n1 1 1 1 1 10 X- RATE GAS 1* 256.0 100.0 /\n20 20 1 1 1 10 X FREE 4* /\n/\nThe last example shows how the DIRICHLET boundary condition option may be used:\n--\n-- DEFINE MODEL BOUNDARY CONDITIONS (OPM FLOW SOLUTION GRID KEYWORD)\n--\n-- ---------- BOX --------- BC BC BC BC BC BC\n-- I1 I2 J1 J2 K1 K2 DIRC TYPE PHASE RATE PRESS TEMP\nBC\n1 1 1 1* 1 1* X- DIRICHLET WAT 1* 256.0 100.0 /\n1 1* 1 1 1 1* Y DIRICHLET WAT 1* 1* 100.0 /\n/\nHere, the first line sets both the pressure and temperature at the boundary, and the second line defaults the pressure entry, so that the simulator calculated initial boundary pressure will be used.\n| Note This is an OPM Flow specific keyword and will therefore cause an error in the commercial simulator. |\n|----------------------------------------------------------------------------------------------------------|","expected_columns":12,"size_kind":"list"},"DATUM":{"name":"DATUM","sections":["SOLUTION"],"supported":null,"summary":"The DATUM keyword defines the datum depth for the model. This allows for all grid block potentials (depth corrected pressures) to be calculated at a common depth.","parameters":[{"index":1,"name":"DATUM","description":"DATUM is a single positive value that defines the datum depth for the model.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":"Length"}],"example":"-- DATUM\n-- DEPTH\n-- ------\nDATUM\n5000.0 / DATUM DEPTH FOR REPORTING\nThe above example defines the datum for the model to be 5000.0","expected_columns":1,"size_kind":"fixed","size_count":1},"DATUMR":{"name":"DATUMR","sections":["SOLUTION"],"supported":null,"summary":"The DATUMR keyword defines the datum depth for each fluid in-place region (FIPNUM) declared in the model. This allows for all grid block potentials (depth corrected pressures) to be calculated at a common depth within a FIPNUM region.","parameters":[{"index":1,"name":"DATUMR","description":"DATUMR is a vector of positive values that defines the datum depth for each fluid in-place region.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None"}],"example":"--\n-- DATUM\n-- DEPTH\n-- ------\nDATUMR\n4800.0\n4900.0\n5000.0 / DATUM DEPTH FOR REPORTING\nThe above example defines the datum depth for three FIPNUM regions, for when NTFIP has been set equal to three on the REGDIMS keyword in the RUNSPEC section.","size_kind":"fixed","size_count":1},"DATUMRX":{"name":"DATUMRX","sections":["SOLUTION"],"supported":null,"summary":"The DATUMRX keyword defines the datum depth for each fluid in-place family region defined by the FIP keyword. This allows for all grid block potentials (depth corrected pressures) to be calculated at a common depth within a given FIP region. The FIP keyword in the REGIONS section allows one to define additional sets of fluid in-place regions to the standard FIPNUM keyword. For example, one could use FIPNUM to define the reservoir layers as fluid in-place regions and the FIP keyword to define the fluid in-place region for fault blocks.","parameters":[{"index":1,"name":"FIPNAME","description":"A character string of up to five characters in length that defines the FIP family name for which the datum depth data is being defined. The default value of 1* will set DATUMR to the standard FIPNUM region numbers.","units":{},"default":"1*","value_type":"STRING"},{"index":2,"name":"DATUMR","description":"DATUMR is a vector of positive values that defines the datum depth for each fluid in-place family region. There must be one entry for each region in the FIP family name. A maximum of NTFIP values, as declared by the REGDIMS keyword in the RUNSPEC section, may be entered for each FIPNAME entry.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":"Length"}],"example":"--\n-- FIP DATUM\n-- NAME DEPTH\nDATUMRX\n'FLTBL' 5000.0 5000.0 5000.0 5000.0 / DATUM DEPTH FOR REPORTING\n'LICBL' 5000.0 5050.0 / DATUM DEPTH FOR REPORTING\n/\nThe above example defines the datum depth for two FIP families, FLTBL and LICBL, with the datum set to a constant 5000.0 psia for FLTBL family and different values for each of the regions in the LICBL family of regions.","size_kind":"list","variadic_record":true},"DYNAMICR":{"name":"DYNAMICR","sections":["SOLUTION","SCHEDULE"],"supported":false,"summary":"The DYNAMICR keyword marks the start of a Dynamic Region section and defines the parameters used for Dynamic Regions that allows for property and reporting regions to vary as the run progresses, based on the parameters and logic defined by this keyword and section. A Dynamic Region section is terminated by the ENDDYN keyword in the SOLUTION or SCHEDULE sections.","parameters":[],"example":"","size_kind":"none","size_count":0},"ENDDYN":{"name":"ENDDYN","sections":["SOLUTION","SCHEDULE"],"supported":false,"summary":"The ENDDYN keyword marks the end of a Dynamic Region section that was started with the DYNAMICR keyword in the SOLUTION or SCHEDULE sections. Dynamic Regions allow for property and reporting regions to vary as the run progresses, based on the parameters and logic defined within the section.","parameters":[],"example":"","size_kind":"none","size_count":0},"EQUIL":{"name":"EQUIL","sections":["SOLUTION"],"supported":null,"summary":"This keyword defines the parameters used to initialize the model for when equilibration is calculated by OPM Flow. This is the standard methodology to initialize a model, the non-standard formulation of entering the pressures and saturations for each grid cell is seldom employed in the industry. The keyword can be used with all grid types.","parameters":[{"index":1,"name":"DATUM","description":"DATUM is a single positive value that defines the reference datum depth for PRESS.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"0.0","value_type":"DOUBLE","dimension":"Length"},{"index":2,"name":"PRESS","description":"PRESS is a single positive value that defines the pressure at DATUM. If the DATUM depth lies above the GOC then PRESS is the pressure with respect to the gas phase. If the DATUM depth is below OWC then PRESS refers to the water phase pressure. Otherwise, PRESS refers to the oil phase pressure.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"0.0","value_type":"DOUBLE","dimension":"Pressure"},{"index":3,"name":"WATCONT","description":"For three phase runs containing oil, gas and water WATCONT is the depth of the oil-water contact (OWC). For two phase runs containing oil and water WATCONT is the depth of the oil-water contact (OWC). For two phase runs containing gas and water WATCONT is the depth of the gas-water contact (GWC).","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"0.0","value_type":"DOUBLE","dimension":"Length"},{"index":4,"name":"WATCAP","description":"For three phase runs containing oil, gas and water WATCAP is the oil-water capillary pressure at the OWC. For two phase runs containing oil and water WATCAP is the oil-water capillary pressure at the OWC. For two phase runs containing gas and water WATCAP is the gas-water capillary pressure at the GWC","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"0.0","value_type":"DOUBLE","dimension":"Pressure"},{"index":5,"name":"GASCONT","description":"For three phase runs containing oil, gas and water GASCONT is the depth of the gas-oil contact (GOC). Note in cases where there is no gas cap (or free gas) then GASCONT should be set to a value shallower than the top of the reservoir. In cases where there is initially no oil zone, as for a gas condensate field for example, the GASCONT should be set to the same depth as WATCONT. For two phase runs containing oil and water, or gas and water, GASCONT is ignored.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"0.0","value_type":"DOUBLE","dimension":"Length"},{"index":6,"name":"GASCAP","description":"For three phase runs containing oil, gas and water GASCAP is the gas-oil capillary pressure at the GWC. For two phase runs containing oil and water, or gas and water, GASCAP is ignored.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"0.0","value_type":"DOUBLE","dimension":"Pressure"},{"index":7,"name":"EQLOPT1","description":"EQLOPT1 is an integer value that sets the initialization option for when dissolved gas is present in the run, as activated by the DISGAS keyword in the RUNSPEC section. A positive value of EQLOPT1 results in the gas-oil ratio being calculated from data entered on the PBVD (saturation pressure or bubble-point pressure versus depth table) or the RSVD keyword (gas-oil ratio versus depth table). If this option is selected, then either the PBVD or RSVD keywords must be present in the input deck. Note that the allocation of multiple PBVD and RSVD tables to each grid cell is through the EQLNUM keyword and not the PVTNUM keyword. A zero value of EQLOPT1 results in the gas-oil ratio being set to the saturated gas-oil ratio at the GOC. In this case DATUM must be equal GASCONT and the PBVD and RSVD keywords may be omitted. A negative value of EQLOPT1 results in the same option for when EQLOPT1 is zero. EQLOPT1 is ignored if there is no dissolved gas in the run.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0","value_type":"INT"},{"index":8,"name":"EQLOPT2","description":"EQLOPT2 is an integer value that sets the initialization option for when vaporized oil (condensate) is present in the run, as activated by the VAPOIL keyword in the RUNSPEC section. A positive value of EQLOPT2 results in the condensate-gas ratio being calculated from data entered on the PDVD (saturation pressure or dew point pressure versus depth table) or the RVVD keyword (condensate-gas ratio versus depth table). If this option is selected, then either the PDVD or RVVD keywords must be present in the input deck Note that the allocation of multiple PDVD and RVVD tables to each grid cell is through the EQLNUM keyword and not the PVTNUM keyword. A zero value of EQLOPT2 results in the condensate-gas ratio being set to the saturated condensate-gas ratio at the GOC. In this case DATUM must be equal GASCONT and the PDVD and RVVD keywords may be omitted. A negative value of EQLOPT2 results in the same option for when EQLOPT2 is zero. EQLOPT2 is ignored if there is no vaporized oil in the run.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0","value_type":"INT"},{"index":9,"name":"EQLOPT3","description":"EQLOPT3 is an integer value that sets the initialization accuracy options for the equilibration calculation. A zero value of EQLOPT3 results in OPM Flow using the fluid saturations at the center of the grid block in the equilibration calculation. This results in a stable initialization at the expense of a potentially less accurate fluid in-place calculation, especially for large thick grid blocks with a fluid contact in the block. A negative value of EQLOPT3 results in the simulator dividing each grid cell into[2` abs{N}~+~1]horizontal sub-blocks for the equilibration calculation. This results in an accurate fluid in-place calculation at the expense of initialization stability, that is there may be some movement of fluids when there is no production at the start of the run. horizontal sub-blocks for the equilibration calculation. This results in an accurate fluid in-place calculation at the expense of initialization stability, that is there may be some movement of fluids when there is no production at the start of the run. Increasing the value of N increases the accuracy of the calculation, with the maximum value of N being set to 20 by OPM Flow. A positive value of EQLOPT3 results in the same option for when EQLOPT3 is negative, except that tilted fault blocks are used in the calculation. Again, increasing the value of N increases the accuracy of the calculation, with the maximum value of N being set to 20 by OPM Flow. Note this option should be used with Irregular Corner-Point Grids. EQLOPT3 is ignored for Radial Grids.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0","value_type":"INT"},{"index":10,"name":"EQLOPT4","description":"A positive integer value greater than or equal one and less than or equal to three, that sets the initialization option in the commercial compositional simulator. EQLOPT4 should be defaulted with 1*, as it is not used by OPM Flow.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"INT"},{"index":11,"name":"EQLOPT5","description":"A positive integer value that if set to one forces PRESS to be used for the datum pressure in the commercial compositional simulator. EQLOPT5 should be defaulted with either 1*, as it is not used by OPM Flow.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"INT"},{"index":12,"name":"EQLOPT6","description":"EQLOPT6 is an integer value that sets the initialization option for when vaporized water is present in the run, as activated by the VAPWAT keyword in the RUNSPEC section. Note this is an OPM Flow specific parameter for use with simulator's Vaporized Water Model. A positive value of EQLOPT6 results in the vaporized water-gas ratio being calculated from data entered on the RVWVD keyword (vaporized water-gas ratio versus depth table). If this option is selected, then the RVWVD keyword must be present in the input deck Note that the allocation of multiple RVWVD tables to each grid cell is through the EQLNUM keyword and not the PVTNUM keyword. A zero value of EQLOPT2 results in the vaporized water-gas ratio being set to the saturated vaporized water-gas ratio at the GOC. In this case DATUM must be equal GASCONT and the RVWVD keyword may be omitted. A negative value of EQLOPT6 results in the same option for when EQLOPT6 is zero. EQLOPT6 is ignored if there is no vaporized water in the run.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0","value_type":"INT"}],"example":"--\n-- DATUM DATUM OWC PCOW GOC PCGO RS RV N E300 RVW\n-- DEPTH PRESS DEPTH ---- DEPTH ---- OPT OPT OPT OPTS OPT\nEQUIL\n3650.0 1560.0 3712.0 0.00 1000.0 0.00 1 0 -5 2* 1* /\n3650.0 1560.0 3741.0 0.00 1000.0 0.00 1 0 -5 2* 1* /\n3650.0 1560.0 3741.0 0.00 1000.0 0.00 1 0 -5 2* 1* /\nThe above example defines three equilibration records for when NTEQUL equals three on the EQLDIMS keyword in the RUNSPEC section. Here there is no gas cap and the GOC has been set to a value above the reservoirs (1000.0), and the value of EQLOPT3 (-5) has been explicitly stated.\n| Note A common method to initialize a model is by using the SWATINIT property array to set the initial water saturation for each cell in the model. This property is normally exported from a static model, where Saturation Height Functions (“SHF”) have been used to describe the water saturation profile with depth. In the dynamic model capillary pressure functions are used to described the water profile versus depth. Note that if the SWATINIT array has been used to initialize the model then the fine grid block initialization via the EQLOPT3 variable, should not normally be used, and should be defaulted or set equal to zero; otherwise, the resulting water saturation will not strictly honor the SWATINIT array. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":12,"size_kind":"fixed"},"GASCONC":{"name":"GASCONC","sections":["SOLUTION"],"supported":false,"summary":"The GASCONC keyword defines the initial equilibration coal gas concentration values for all matrix grid cells in the model and should be used in conjunction with the GCVD keyword in the SOLUTION section, to fully describe the initial state of the model. The keyword should only be used if the coal phase has been activated in the model via the COAL keyword in the RUNSPEC section. Note both GASCONC and GCVD are optional as the simulator will calculate the coal gas concentration based on the equilibrium concentration and the block pressure.","parameters":[{"index":1,"name":"GASCONC","description":"GASCONC is an array of real positive numbers that define the initial equilibration coal gas concentration values to each matrix cell in the model. Repeat counts may be used, for example 20*75.0.","units":{"field":"Mscf/ft3","metric":"sm3/m3","laboratory":"scc/cc"},"default":"None"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION COAL GAS CONCENTRATION FOR ALL CELLS\n-- BASED ON NX = 100, NY = 100 AND NZ = 6\n--\nGASCONC\n1000*75.500 1000*65.500 1000*60.000 /\nThe above example defines the initial equilibration coal gas concentration values to be 75.500 for all the matrix cells in the first layer, 65.500 for all the cells in the second layer, and finally 60.000 for all the cells in the third layer.","size_kind":"array"},"GASSATC":{"name":"GASSATC","sections":["SOLUTION"],"supported":false,"summary":"The GASSATC keyword defines the initial equilibration saturated coal gas concentration values for all grid cells in the model. The keyword should only be used if the coal phase has been activated in the model via the COAL keyword in the RUNSPEC section. The keyword is used to re-scale the Langmuir isotherms entered via the LANGMUIR keyword in the PROPS section, in conjunction with a matrix grid blocks initial reservoir pressure. The keyword is optional, and if absent from the input file, the matrix grid block Langmuir isotherm is left unscaled.","parameters":[{"index":1,"name":"GASSATC","description":"GASSATC is an array of real positive numbers that define the initial equilibration saturated coal gas concentration values to each cell in the model. Repeat counts may be used, for example 20*75.0.","units":{"field":"Mscf/ft3","metric":"sm3/m3","laboratory":"scc/cc"},"default":"None"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION SAT COAL GAS CONCENTRATION ALL CELLS MODEL\n-- BASED ON NX = 100, NY = 100 AND NZ = 6\n--\nGASSATC\n1000*75.500 1000*65.500 1000*60.000 /\nThe above example defines the initial equilibration saturated coal gas concentration values to be 75.500 for all the matrix cells in the first layer, 65.500 for all the cells in the second layer, and finally 60.000 for all the cells in the third layer.","size_kind":"array"},"GCVD":{"name":"GCVD","sections":["SOLUTION"],"supported":false,"summary":"The GCVD keyword defines the initial coal gas concentration versus depth tables for each equilibration region for when the coal phase has been activated in the run via the COAL keyword in the RUNSPEC section. The keyword may be used in conjunction with the GASCONC keyword in the SOLUTION section, to fully describe the initial state of the model. Note both GASCONC and GCVD are optional as the simulator will calculate the coal gas concentration based on the equilibrium concentration and the block pressure.","parameters":[{"index":1,"name":"DEPTH","description":"A columnar vector of real monotonically increasing down the column values that defines the depth values for the corresponding coal gas concentration, GCVALS.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":["Length","GasSurfaceVolume/Length*Length*Length"]},{"index":2,"name":"GCVALS","description":"A columnar vector of real values that defines the coal gas concentration values at the corresponding DEPTH.","units":{"field":"Mscf/ft3","metric":"sm3/m3","laboratory":"scc/cc"},"default":"None"}],"example":"Given NTEQUL equals three and NDRXVD is greater than or equal to two on the EQLDIMS keyword in the RUNSPEC section, then the following example defines the coal gas concentration versus depth functions.\n--\n-- DEPTH GC\n-- MSCF/FT\n-- ------ --------\nGCVD\n100.0 75.5000\n1000.0 75.5000 / GC VS DEPTH EQUIL REGN 01\n-- ------ --------\n100.0 65.5000\n1000.0 65.5000 / GC VS DEPTH EQUIL REGN 02\n-- ------ --------\n100.0 60.0000\n1000.0 60.0000 / GC VS DEPTH EQUIL REGN 03\nHere three tables are entered with a constant coal gas concentration versus depth relationship for each equilibration region.","size_kind":"fixed","variadic_record":true},"GETGLOB":{"name":"GETGLOB","sections":["SOLUTION"],"supported":false,"summary":"This keyword, GETGLOB, switches on the global grid read option for when the run is restarting from a RESTART file. Only the global grid will be loaded in the subsequent RESTART keyword and any Local Grid Refinements (“LGR”) on the RESTART file will be ignored.","parameters":[],"example":"--\n-- ACTIVATE LOADING OF GLOBAL GRID RESTART DATA OPTION\n--\nGETGLOB\nThe above example switches on the option to only load the global grid from the RESTART file.","size_kind":"none","size_count":0},"GI":{"name":"GI","sections":["SOLUTION"],"supported":false,"summary":"The GI keyword defines the initial equilibration GI values for all grid cells in the model and should be used in conjunction with the other enumeration equilibration keywords; PBUB, PDEW, PRESSURE, RS, RV, SOIL and SWAT keywords etc., to fully describe the initial state of the model. The keyword should only be used if the GI Pseudo Compositional option has been activated in the model via the GIMODEL keyword in the RUNSPEC section.","parameters":[],"example":"","size_kind":"array"},"HMAQUCT":{"name":"HMAQUCT","sections":["SOLUTION"],"supported":false,"summary":"The HMAQUCT keyword defines the history match analytical Carter-Tracy aquifer gradient parameters for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section, and analytical Carter-Tracy aquifers have been specified in the model via the AQUCT and connected to the grid using the AQUANCON or AQANCONL keywords. All keywords are in the SOLUTION section.","parameters":[{"index":1,"name":"AQUIFER_ID","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"DERIVATIES_RESP_PERM_MULT","description":"","units":{},"default":"NO","value_type":"STRING"},{"index":3,"name":"DERIVATIES_RESP_OPEN_ANGLE_MULT","description":"","units":{},"default":"NO","value_type":"STRING"},{"index":4,"name":"DERIVATIES_RESP_AQUIFER_DEPTH","description":"","units":{},"default":"NO","value_type":"STRING"}],"example":"","expected_columns":4,"size_kind":"list"},"HMAQUFET":{"name":"HMAQUFET","sections":["SOLUTION"],"supported":false,"summary":"The HMAQUFET keyword defines the history match analytical Fetkovich aquifer gradient parameters for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section, and analytical Fetkovich aquifers have been specified in the model via the AQUFET and/or the AQUFETP keywords and connected to the grid using AQUANCON or AQANCONL keywords. All keywords are in the SOLUTION section.","parameters":[{"index":1,"name":"AQUIFER_ID","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"DERIVATIES_RESP_WAT_VOL_MULT","description":"","units":{},"default":"NO","value_type":"STRING"},{"index":3,"name":"DERIVATIES_RESP_AQUIFER_PROD_INDEX_MULT","description":"","units":{},"default":"NO","value_type":"STRING"},{"index":4,"name":"DERIVATIES_RESP_AQUIFER_DEPTH","description":"","units":{},"default":"NO","value_type":"STRING"}],"example":"","expected_columns":4,"size_kind":"list"},"HMMLCTAQ":{"name":"HMMLCTAQ","sections":["SOLUTION"],"supported":false,"summary":"The HMMLCTAQ keyword defines the history match analytical Carter-Tracy aquifer gradient multipliers for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section, and analytical Carter-Tracy aquifers have been specified in the model via the AQUCT and connected to the grid using the AQUANCON or AQANCONL keywords. All keywords are in the SOLUTION section.","parameters":[{"index":1,"name":"AQUIFER_ID","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"AQUIFER_PERM_MULT","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"AQUIFER_ANGLE_MULT","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"},{"index":4,"name":"AQUIFER_DEPTH_MULT","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"}],"example":"","expected_columns":4,"size_kind":"list"},"HMMLFTAQ":{"name":"HMMLFTAQ","sections":["SOLUTION"],"supported":false,"summary":"The HMAQUFET keyword defines the history match analytical Fetkovich aquifer gradient multipliers for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section, and analytical Fetkovich aquifers have been specified in the model via the AQUFET and/or the AQUFETP keywords and connected to the grid using AQUANCON or AQANCONL keywords. All keywords are in the SOLUTION section.","parameters":[{"index":1,"name":"AQUIFER_ID","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"AQUIFER_WAT_VOL_MULT","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"AQUIFER_PROD_INDEX_MULT","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"},{"index":4,"name":"AQUIFER_DEPTH_MULT","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"}],"example":"","expected_columns":4,"size_kind":"list"},"HMMLTWCN":{"name":"HMMLTWCN","sections":["SOLUTION"],"supported":false,"summary":"This keyword, HMMLTWCN, defines the history match gradient multipliers for well connection factors and connection skins, for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section. Wells must be specified using the WELPSECS keyword in the SCHEDULE section and their connections defined by the COMPDAT and/or COMPDATL keywords, also in the SCHEDULE section","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"GRID","description":"","units":{},"default":"FIELD","value_type":"STRING"},{"index":3,"name":"I","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"J","description":"","units":{},"default":"","value_type":"INT"},{"index":5,"name":"K","description":"","units":{},"default":"","value_type":"INT"},{"index":6,"name":"CTF","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"},{"index":7,"name":"SKIN","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"}],"example":"","expected_columns":7,"size_kind":"list"},"HMWELCON":{"name":"HMWELCON","sections":["SOLUTION"],"supported":false,"summary":"This keyword, HMWELCON, defines the history match gradient parameters for well connection factors and connection skins, for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section. Wells must be specified using the WELPSECS keyword in the SCHEDULE section and their connections defined by the COMPDAT and/or COMPDATL keywords, also in the SCHEDULE section","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"GRID","description":"","units":{},"default":"FIELD","value_type":"STRING"},{"index":3,"name":"I","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"J","description":"","units":{},"default":"","value_type":"INT"},{"index":5,"name":"K","description":"","units":{},"default":"","value_type":"INT"},{"index":6,"name":"REQ_TRANS_FACTOR_GRAD","description":"","units":{},"default":"NO","value_type":"STRING"},{"index":7,"name":"REQ_SKIN_FACTOR_GRAD","description":"","units":{},"default":"NO","value_type":"STRING"}],"example":"","expected_columns":7,"size_kind":"list"},"NOHMD":{"name":"NOHMD","sections":["SOLUTION","SCHEDULE"],"supported":false,"summary":"The NOHMD deactivates various history match gradient derivative calculations for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section. The keyword consists of a series of character strings that define which derivative should be switch off based on the keyword that requested the derivatives to be calculated, for example HMFAULTS keyword in the GRID section. If an empty list is entered then all the gradient derivative calculations previously requested are switch off. The keyword is useful for changing from history matching runs to predication cases, as the prediction cases will be more computationally efficient without the burden of the gradient derivative calculations.","parameters":[{"index":1,"name":"GRAD_PARAMS","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","size_kind":"fixed","size_count":1,"variadic_record":true},"NOHMO":{"name":"NOHMO","sections":["SOLUTION","SCHEDULE"],"supported":false,"summary":"The NOHMO deactivates various history match gradient derivative calculations for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section. The keyword consists of a series of character strings that define which derivative should be switch off based on the keyword that requested the derivatives to be calculated, for example HMFAULTS keyword in the GRID section. If an empty list is entered then all the gradient derivative calculations previously requested are switch off. The keyword is useful for changing from history matching runs to predication cases, as the prediction cases will be more computationally efficient without the burden of the gradient derivative calculations.","parameters":[{"index":1,"name":"GRAD_PARAMS","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","size_kind":"fixed","size_count":1,"variadic_record":true},"OILAPI":{"name":"OILAPI","sections":["SOLUTION"],"supported":null,"summary":"The OILAPI keyword defines the initial equilibration oil API gravity pressures for all grid cells in the model, for when the Oil API Tracking option as been invoked by the API keyword in the RUNSPEC section. The keyword should be used in conjunction with the PBUB, PDEW, PRESSURE, RS, RV, SGAS, SOIL and SWAT keywords etc., to fully describe the initial state of the model.","parameters":[{"index":1,"name":"OILAPI","description":"OILAPI is an array of real positive numbers assigning the initial equilibration oil API gravity to each cell in the model. The American Petroleum Institute (“API”) classifies oils based on an API gravity (γAPI), or degrees API (oAPI), the relationship between relative density (γo) of oil and API gravity (γAPI) is given by: [%gamma SUB { API } ~ = ~ { 141.5 } OVER { %gamma SUB { o }}~-~ 131.5] Repeat counts may be used, for example 20*38.5","units":{"field":"oAPI","metric":"oAPI","laboratory":"oAPI"},"default":"None"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION OIL API FOR ALL CELLS IN THE MODEL\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nOILAPI\n1000*40.2 1000*39.5 1000*38.2 /\nThe above example defines the initial equilibration oil API gravity to be 40.2 for all the cells in the first layer, 39.5 for all the cells in the second layer, and finally 38.2 for all the cells in the third layer.","size_kind":"array"},"OUTSOL":{"name":"OUTSOL","sections":["SOLUTION","SCHEDULE"],"supported":false,"summary":"This keyword defines the data and frequency of the data to be written to the RESTART file at each requested restart point. The keyword has been replaced by the RPTRST keyword in the SOLUTION and SCHEDULE sections and is therefore considered retired.","parameters":[],"example":"","size_kind":"none","size_count":0},"PBUB":{"name":"PBUB","sections":["SOLUTION"],"supported":false,"summary":"The PBUB keyword defines the initial equilibration buble-point saturation pressures values for all grid cells in the model and should be used in conjunction with the PDEW, PRESSURE, RS, RV, SGAS, SOIL and SWAT keywords etc., to fully describe the initial state of the model. The keyword should only be used if dissolved gas has been activated in the model via the DISGAS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"PBUB","description":"PBUB is an array of real positive numbers assigning the initial equilibration bubble-point saturation pressure values to each cell in the model. Repeat counts may be used, for example 20*3500.0","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION PSAT VALUES FOR ALL CELLS IN THE MODEL\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nPBUB\n1000*3500.0 1000*3525.0 1000*0.3535.0 /\nThe above example defines the initial equilibration bubble-point saturation pressure values to be 3500.0 for all the cells in the first layer, 3525.0 for all the cells in the second layer, and finally 3535.0 for all the cells in the third layer.","size_kind":"array"},"PBVD":{"name":"PBVD","sections":["SOLUTION"],"supported":null,"summary":"The PBVD keyword defines the bubble-point pressure versus depth tables for each equilibration region that should be used when there is dissolved gas in the model (DISGAS has been activated in the RUNSPEC section) and the EQLOPT1 variable has been set to a positive integer on the EQUIL keyword in the SOLUTION section.","parameters":[{"index":1,"name":"DEPTH","description":"A columnar vector of real monotonically increasing down the column values that defines the depth values for the corresponding bubble-point values, PBVALS.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":["Length","Pressure"]},{"index":2,"name":"PBVALS","description":"A columnar vector of real values that defines the oil bubble-point values at the corresponding DEPTH.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None"}],"example":"Given NTEQUL equals three and NDRXVD is greater than or equal to two on the EQLDIMS keyword in the RUNSPEC section, then the following example defines the bubble-point versus depth functions.\n--\n-- DEPTH PSAT\n-- PRESS\n-- ------ ------\nPBVD\n3000.0 3000.0\n8000.0 3025.0 / PSAT VS DEPTH EQUIL REGN 01\n-- ------ ------\n3000.0 3100.0\n8000.0 3125.0 / PSAT VS DEPTH EQUIL REGN 02\n-- ------ ------\n3000.0 3200.0\n8000.0 3225.0 / PSAT VS DEPTH EQUIL REGN 03\nHere three tables are entered and each table is terminated by a “/” and there is no keyword terminating “/”.","size_kind":"fixed","variadic_record":true},"PDEW":{"name":"PDEW","sections":["SOLUTION"],"supported":false,"summary":"The PDEW keyword defines the initial equilibration dew-point pressure values for all grid cells in the model and should be used in conjunction with the PBUB, PRESSURE, RS, RV, SGAS, SOIL and SWAT keywords etc., to fully describe the initial state of the model. The keyword should only be used if vaporized oil been activated in the model via the VAPOIL keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"PDEW","description":"PDEW is an array of real positive numbers assigning the initial equilibration dew-point pressure values to each cell in the model. Repeat counts may be used, for example 20*3525.0","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION PSAT VALUES FOR ALL CELLS IN THE MODEL\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nPDEW\n1000*3500.0 1000*3525.0 1000*0.3535.0 /\nThe above example defines the initial equilibration dew-point saturation pressure values to be 3500.0 for all the cells in the first layer, 3525.0 for all the cells in the second layer, and finally 3535.0 for all the cells in the third layer.","size_kind":"array"},"PDVD":{"name":"PDVD","sections":["SOLUTION"],"supported":null,"summary":"The PDVD keyword defines the dew-point pressure versus depth tables for each equilibration region that should be used when there is vaporized oil in the model (VAPOIL has been activated in the RUNSPEC section) and the EQLOPT2 variable has been set to a positive integer on the EQUIL keyword in the SOLUTION section.","parameters":[{"index":1,"name":"DEPTH","description":"A columnar vector of real monotonically increasing down the column values that defines the depth values for the corresponding dew-point values, PDVALS.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":["Length","Pressure"]},{"index":2,"name":"PDVALS","description":"A columnar vector of real values that defines the gas dew-point values at the corresponding DEPTH.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None"}],"example":"Given NTEQUL equals three and NDRXVD is greater than or equal to two on the EQLDIMS keyword in the RUNSPEC section, then the following example defines the bubble-point versus depth functions.\n--\n-- DEPTH PSAT\n-- PRESS\n-- ------ ------\nPDVD\n3000.0 2000.0\n8000.0 2025.0 / PSAT VS DEPTH EQUIL REGN 01\n-- ------ ------\n3000.0 2100.0\n8000.0 2125.0 / PSAT VS DEPTH EQUIL REGN 02\n-- ------ ------\n3000.0 2200.0\n8000.0 2225.0 / PSAT VS DEPTH EQUIL REGN 03\nHere three tables are entered and each table is terminated by a “/” and there is no keyword terminating “/”.","size_kind":"fixed","variadic_record":true},"PRESSURE":{"name":"PRESSURE","sections":["SOLUTION"],"supported":null,"summary":"The PRESSURE keyword defines the initial equilibration pressures for all grid cells in the model and should be used in conjunction with the PBUB, PDEW, RS, RV, SGAS, SOIL and SWAT keywords etc., to fully describe the initial state of the model.","parameters":[{"index":1,"name":"PRESSURE","description":"PRESSURE is an array of real positive numbers assigning the initial equilibration pressures to each cell in the model. Repeat counts may be used, for example 20*4200.0.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION PRESSURES FOR ALL CELLS IN THE MODEL\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nPRESSURE\n1000*4500.0 1000*4510.0 1000*4520.0 /\nThe above example defines the initial equilibration pressures to be 4500.0 for all the cells in the first layer, 4510.0 for all the cells in the second layer, and finally 4520.0 for all the cells in the third layer.","size_kind":"array"},"PRVD":{"name":"PRVD","sections":["SOLUTION"],"supported":false,"summary":"The PRVD keyword defines the initial reservoir pressure versus depth and should be used in conjunction with the PBUB, PDEW, RS, RV, SGAS, SOIL and SWAT keywords etc., to fully describe the initial state of the model. PRVD is an alternative to the PRESSURE keyword in the SOLUTION section, that defines the initial equilibration pressures for all grid cells in the model","parameters":[{"index":1,"name":"DEPTH","description":"A columnar vector of real monotonically increasing down the column values that defines the depth values for the corresponding reservoir oil pressures values, PRESSURE.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":["Length","Pressure"]},{"index":2,"name":"PRESSURE","description":"A columnar vector of real values that defines the initial equilibration oil pressure values at the corresponding DEPTH.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None"}],"example":"Given NTEQUL equals three and NDRXVD is greater than or equal to five on the EQLDIMS keyword in the RUNSPEC section, then the following example defines the initial oil reservoir pressure versus depth\n--\n-- DEPTH INIT\n-- PRESS\n-- ------ ------\nPRVD\n3000.0 3000.0\n4000.0 3345.0\n5000.0 3690.0\n7000.0 4700.0\n7200.0 4769.0 / POIL VS DEPTH EQUIL REGN 01\n-- ------ ------\n3000.0 3100.0\n4000.0 3445.0\n5000.0 3790.0\n7000.0 4700.0\n7200.0 4769.0 / POIL VS DEPTH EQUIL REGN 02\n-- ------ ------\n3000.0 3150.0\n4000.0 3495.0\n5000.0 3840.0\n7000.0 4700.0\n7200.0 4769.0 / POIL VS DEPTH EQUIL REGN 03\nHere three tables are entered and each table is terminated by a “/” and there is no keyword terminating “/”.","size_kind":"fixed","variadic_record":true},"RAINFALL":{"name":"RAINFALL","sections":["SOLUTION","SCHEDULE"],"supported":false,"summary":"This RAINFALL keyword defines the month by month rainfall flux for constant flux aquifers.","parameters":[{"index":1,"name":"AQUIFER_ID","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"JAN_FLUX","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time*Length*Length"},{"index":3,"name":"FEB_FLUX","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time*Length*Length"},{"index":4,"name":"MAR_FLUX","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time*Length*Length"},{"index":5,"name":"APR_FLUX","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time*Length*Length"},{"index":6,"name":"MAI_FLUX","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time*Length*Length"},{"index":7,"name":"JUN_FLUX","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time*Length*Length"},{"index":8,"name":"JUL_FLUX","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time*Length*Length"},{"index":9,"name":"AUG_FLUX","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time*Length*Length"},{"index":10,"name":"SEP_FLUX","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time*Length*Length"},{"index":11,"name":"OCT_FLUX","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time*Length*Length"},{"index":12,"name":"NOV_FLUX","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time*Length*Length"},{"index":13,"name":"DES_FLUX","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time*Length*Length"}],"example":"","expected_columns":13,"size_kind":"fixed","size_count":1},"RBEDCONT":{"name":"RBEDCONT","sections":["PROPS"],"supported":false,"summary":"The RBEDCONT keyword defines the river grid block contact area versus depth tables, for when the River option has been activated via the RIVRDIMS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Length","Length*Length"]}],"example":"","size_kind":"fixed","variadic_record":true},"RESTART":{"name":"RESTART","sections":["SOLUTION"],"supported":false,"summary":"The RESTART keyword defines the parameters to restart the simulation from a previous run that has written a RESTART file out to disk. Only restarting from RESTART files is permitted by OPM Flow; restarting from SAVE files is not implemented.","parameters":[{"index":1,"name":"RSNAME","description":"The RSNAME variable is a character string that defines the root name of the RESTART file to be read into the current input deck.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"RSNUM","description":"A positive integer that defines the restart point on the RESTART file to be read and to be used to initialize the model. When OPM Flow writes a restart point a message is printed to the *.PRT file indicating the time step the restart was written out.","units":{},"default":"None","value_type":"INT"},{"index":3,"name":"RSTYPE","description":"A defined character sting set to SAVE to read the restart data from the SAVE file, otherwise defaulted to 1* to read the data from the RESTART file. The SAVE file option is not supported by OPM Flow and should be defaulted with 1*.","units":{},"default":"1*","value_type":"STRING"},{"index":4,"name":"RSFORMAT","description":"A defined character string that defines the format of the SAVE file to be read if RSTYPE has been set to SAVE, and should be set to one of the following: FORMATTED: If the file is formatted as ASCII i.e. a text file, as oppose to a binary file. The option can be abbreviated to just the letter F. UNFORMATTED: If the file is in binary format, note this option can be abbreviated to just the letter U. This type of file is operating system dependent If the variable RSFORMAT omitted then the default is for binary file input. This option is not supported by OPM Flow and should be defaulted with 1*.","units":{},"default":"U","value_type":"STRING"}],"example":"The example below defines a restart from the previously run NOR-OPM-A01 case at time step number 40.\n-- ==============================================================================\n--\n-- SOLUTION SECTION\n--\n-- ==============================================================================\nSOLUTION\n--\n-- FLEXIBLE RESTART FROM PREVIOUS SIMULATION RUN\n--\n-- FILE RESTART RESTART FILE\n-- NAME NUMBER TYPE FORMAT\nRESTART\n'NOR-OPM-A01' 40 1* 1* /\nIn addition in the SCHEDULE section the SKIPREST keyword should be used to correctly read in the schedule data up to the RESTART point.\n-- ==============================================================================\n--\n-- SCHEDULE SECTION\n--\n-- ==============================================================================\nSCHEDULE\n--\n-- ACTIVATE SKIPREST OPTION TO AVOID MODIFYING SCHEDULE SECTION\n--\nSKIPREST\nNote is advisable to place the SKIPREST keyword at the very beginning of the SCHEDULE section.","expected_columns":4,"size_kind":"fixed","size_count":1},"RIVERSYS":{"name":"RIVERSYS","sections":["SOLUTION","SCHEDULE"],"supported":false,"summary":"RIVERSYS defines a river system by specifying the branch structure of the river together with the branch's associated boundary conditions, for when the River option has been activated via the RIVRDIMS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"RIVER","description":"","units":{},"default":"","value_type":"STRING","record":1},{"index":2,"name":"EQUATION","description":"","units":{},"default":"","value_type":"STRING","record":1},{"index":1,"name":"BRANCH_NR","description":"","units":{},"default":"","value_type":"INT","record":2},{"index":2,"name":"BRANCH_NAME","description":"","units":{},"default":"","value_type":"STRING","record":2},{"index":3,"name":"DOWNSTREAM_BC","description":"","units":{},"default":"","value_type":"STRING","record":2}],"example":"","records_meta":[{"expected_columns":2},{}],"size_kind":"list"},"RPTRST":{"name":"RPTRST","sections":["SOLUTION","SCHEDULE"],"supported":false,"summary":"This keyword defines the data to be written to the RESTART file and the frequency at which restart points will be created. In addition to the solution data arrays required to restart a run, the user may request extra data to be written to the restart file for visualization in OPM ResInsight.","parameters":[{"index":1,"name":"XMFCO2","description":"CO2 liquid-phase mole fractions written when the CO2STORE option has been activated in the RUNSPEC section.","units":{},"default":"XMFCO2","value_type":"STRING"},{"index":2,"name":"XMFH2","description":"H2 liquid-phase mole fractions written when the H2STORE option has been activated in the RUNSPEC section.","units":{},"default":"XMFH2"},{"index":3,"name":"YMFWAT","description":"Water gas-phase mole fractions written when either the CO2STORE or H2STORE option has been activated in the RUNSPEC section.","units":{},"default":"YMFWAT"}],"example":"The first example request that the standard restart data be written out every month.\n--\n-- RESTART CONTROL BASIC = 4 (YEARLY) 5 (MONTHLY)\n--\nRPTRST\nBASIC=5 /\nThe next example requests that the standard restart data be written at every report time step until this switch is reset and all the restarts are kept. In addition to the standard the data the gas, oil and water relative permeability data will also be written out at each report time step.\n--\n-- RESTART CONTROL BASIC = 4 (YEARLY) 5 (MONTHLY)\n--\nRPTRST\nBASIC=2 KRG KRO KRW /\n| Note Currently, OPM Flow distinguishes between those arrays which are required for restarting a run and those which are \"merely\" for visualization and analysis. However, this classification is imperfect and leads to potentially exporting arrays that are incompatible with the commercial simulator, such as the TEMP array in non-thermal simulation runs. If one is willing to forego the ability to restart an OPM Flow simulation run, using the commercial simulator, e.g., simulating the historic period using OPM Flow and the prediction period using the commercial simulator, then additional arrays are available, including the PBUB and PDEW vectors generated by the PBPD option, by using the following command line option: --enable-opm-rst-file=true |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"fixed","size_count":1,"variadic_record":true},"RPTSOL":{"name":"RPTSOL","sections":["SOLUTION"],"supported":true,"summary":"This keyword defines the data in the SOLUTION section that is to be printed to the output print file in human readable format. The keyword has two distinct forms, the first of which consists of the keyword followed by a series of integers on the next line indicating the data to be printed (see the first example). This is the original formal in the commercial simulator and was subsequently superseded by the second format. The second format consists of the keyword followed by a series of character strings that indicate the data to be printed. In most cases the character string is the keyword used to load the data in the OPM Flow input deck, for example PVDG for the dry gas PVT tables. Its is anticipated that OPM Flow will eventually support the functionality of the second format only, the first format although recognized will be completely ignored.","parameters":[{"index":1,"name":"DENO","description":"Print the oil reservoir density array","units":{},"default":"N/A","value_type":"STRING"},{"index":2,"name":"EQUIL","description":"Print the equilibration report.","units":{},"default":"N/A"},{"index":3,"name":"FIP","description":"Print the fluid in-place report. The parameter is assigned a value, OPTION, using the form FIP=OPTION, where OPTION is an integer variable set to: OPTION = 1 then the report is for the field only. OPTION = 2 then in addition to the field report, a report is produced for each FIPNUM region, as defined by the FIPNUM keyword in the REGIONS section. Note the commercial simulator also prints the flows to other regions as well as the flows from the wells. This additional reporting option has not been implemented in OPM Flow. OPTION = 3 then in addition to the above, a balance report is also produced for fluid in-place regions defined by the FIP keyword in the REGIONS section.","units":{},"default":"FIP=2"},{"index":4,"name":"FIPRESV","description":"Print the reservoir volumes in-place report.","units":{},"default":"N/A"},{"index":5,"name":"WELSPECS","description":"WELSPECS switches on reporting of the well connections, wells and groups at each report time step. There are numerous reports associated with this option. Unlike the other reporting parameters that produce a report for each reporting time step, the WELSPECS report option only produces a report if an associated keyword has been activated at the current reporting time step. For example, if the reporting time steps are January, February, and March 2020, and the RPTSCHED WELSPECS option is activated in January, with wells OP01 and OP02 being declared via the WELSPECS and COMPDAT keywords, then a report will be printed for January for these two wells. If there are no further well activations until March, with well OP03 being declared, then there will be no report for February, and only well OP03 will reported at the March reporting time step.","units":{},"default":"N/A"}],"example":"The first example shows the original format of this keyword; although the keyword and format are recognized by OPM Flow, the format is ignored and is unlikely to be implemented in in the simulator.\n--\n-- DEFINE SOLUTION SECTION REPORT OPTION (ORIGINAL FORMAT)\n–\nRPTSOL\n1 2*0 1 3*1 /\nThe next example shows the second format of the keyword which may be supported in a future release of OPM Flow.\n--\n-- DEFINE SOLUTION SECTION REPORT OPTIONS\n--\nRPTSOL\nFIP=2 FIPRESV RESTART=3 /\n| Note Except for non-array like data, FIP etc., this keyword has the potential to produce very large print files that some text editors may have difficulty loading. A more efficient solution for array type data is to load the *.INIT and *.RESTART files into OPM ResInsight to view the data graphically, this also has the benefit of being able to filter the grid based on I, J, K ranges and grid properties. |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"fixed","size_count":1,"variadic_record":true},"RS":{"name":"RS","sections":["SOLUTION"],"supported":null,"summary":"The RS keyword defines the initial equilibration gas-oil ratio values for all grid cells in the model and should be used in conjunction with the PBUB, PDEW, PRESSURE, RV, SGAS, SOIL and SWAT keywords etc., to fully describe the initial state of the model. The keyword should only be used if dissolved gas has been activated in the model via the DISGAS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"RS","description":"RS is an array of real positive numbers assigning the initial equilibration gas-oil ratio values to each cell in the model. Repeat counts may be used, for example 20*1.30.","units":{"field":"Mscf/stb","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"None"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION GOR VALUES FOR ALL CELLS IN THE MODEL\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nRS\n1000*1.3500 1000*1.3010 1000*1.3000 /\nThe above example defines the initial equilibration GOR values to be 1.3500 for all the cells in the first layer, 1.3010 for all the cells in the second layer, and finally 1.3000 for all the cells in the third layer.","size_kind":"array"},"RSVD":{"name":"RSVD","sections":["SOLUTION"],"supported":null,"summary":"The RSVD keyword defines the dissolved gas-oil ratio (Rs) versus depth tables for each equilibration region that should be used when there is dissolved gas in the model (DISGAS has been activated in the RUNSPEC section) and the EQLOPT1 variable has been set to a positive integer on the EQUIL keyword in the SOLUTION section.","parameters":[{"index":1,"name":"DEPTH","description":"A columnar vector of real monotonically increasing down the column values that defines the depth values for the corresponding dissolve gas-oil ratio values, RS.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":["Length","GasDissolutionFactor"]},{"index":2,"name":"RS","description":"A columnar vector of real values that defines the dissolved gas-oil ratio values at the corresponding DEPTH.","units":{"field":"Mscf/stb","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"None"}],"example":"Given NTEQUL equals three and NDRXVD is greater than or equal to two on the EQLDIMS keyword in the RUNSPEC section, then the following example defines the bubble-point versus depth functions.\n--\n-- DEPTH RS\n-- MSCF/STB\n-- ------ --------\nRSVD\n3000.0 1.400\n8000.0 1.400 / RS VS DEPTH EQUIL REGN 01\n-- ------ --------\n3000.0 1.400\n8000.0 1.400 / RS VS DEPTH EQUIL REGN 02\n-- ------ --------\n3000.0 1.400\n8000.0 1.400 / RS VS DEPTH EQUIL REGN 03\nHere three tables are entered with a constant GOR versus depth relationship.","size_kind":"fixed","variadic_record":true},"RSW":{"name":"RSW","sections":["SOLUTION"],"supported":null,"summary":"The RSW keyword defines the initial equilibration solution gas in water ratio values for all grid cells in the model and should be used in conjunction with the PBUB, PDEW, PRESSURE, RS, SGAS, SOIL and SWAT keywords etc., to fully describe the initial state of the model. The keyword should only be used if both gas and water phases have been activated in the model via the GAS and WATER keywords, and the DISGASW keyword is also present activating OPM Flow’s Dissolved Gas in Water Model. All the aforementioned keywords are in the RUNSPEC section.","parameters":[{"index":1,"name":"RSW","description":"RSW is an array of positive real numbers assigning the initial equilibration solution gas-water ratio values to each cell in the model. Repeat counts may be used, for example 20*1.30.","units":{"field":"Mscf/stb","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"None"}],"example":"--\n-- INITIAL EQUILIBRATION SOLUTION GAS IN WATER RATIO VALUES FOR ALL CELLS\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nRSW\n1000*0.0000 1000* 0.0000 1000*1.3000 /\nThe above example defines the initial equilibration solution gas-water values to be 0.000 for all the cells in the first and second layers and 1.3000 for all the cells in the third layer.\n| Note This is an OPM Flow specific keyword for the simulator’s Dissolved Gas in Water Model that is activated by declaring that dissolved gas in water is present in the run using the DISGASW keyword in the RUNSPEC section. Use the command line option --enable-opm-rst-file=true to output the RSW data to the RESTART file. |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"array"},"RV":{"name":"RV","sections":["SOLUTION"],"supported":null,"summary":"The RV keyword defines the initial equilibration vaporized oil-gas ratio values for all grid cells in the model and should be used in conjunction with the PBUB, PDEW, PRESSURE, RS, SGAS, SOIL and SWAT keywords etc., to fully describe the initial state of the model. The keyword should only be used if vaporized oil been activated in the model via the VAPOIL keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"RV","description":"RV is an array of real positive numbers assigning the initial equilibration vaporized oil-gas ratio values to each cell in the model. Repeat counts may be used, for example 20*0.00720","units":{"field":"stb/Mscf","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"None"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION CGR VALUES FOR ALL CELLS IN THE MODEL\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nRV\n1000*0.00720 1000*0.00725 1000*0.00730 /\nThe above example defines the initial equilibration GOR values to be 0.00720 for all the cells in the first layer, 0.00725 for all the cells in the second layer, and finally 0.00730 for all the cells in the third layer.","size_kind":"array"},"RVVD":{"name":"RVVD","sections":["SOLUTION"],"supported":null,"summary":"The RVVD keyword defines the vaporized oil-gas ratio (Rv) versus depth tables for each equilibration region that should be used when there is vaporized oil in the model (VAPOIL has been activated in the RUNSPEC section) and the EQLOPT2 variable has been set to a positive integer on the EQUIL keyword in the SOLUTION section.","parameters":[{"index":1,"name":"DEPTH","description":"A columnar vector of real monotonically increasing down the column values that defines the depth values for the corresponding vaporized oil-gas ratio values, RV.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":["Length","OilDissolutionFactor"]},{"index":2,"name":"RV","description":"A columnar vector of real values that defines the vaporized oil-gas ratio values at the corresponding DEPTH.","units":{"field":"stb/Mscf","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"None"}],"example":"Given NTEQUL equals three and NDRXVD is greater than or equal to two on the EQLDIMS keyword in the RUNSPEC section, then the following example defines the dew-point versus depth functions.\n--\n-- DEPTH RV\n-- STB/MSCF\n-- ------ --------\nRVVD\n3000.0 0.00725\n8000.0 0.00725 / RV VS DEPTH EQUIL REGN 01\n-- ------ --------\n3000.0 0.00730\n8000.0 0.00730 / RV VS DEPTH EQUIL REGN 02\n-- ------ --------\n3000.0 0.00750\n8000.0 0.00750 / RV VS DEPTH EQUIL REGN 03\nHere three tables are entered with a constant CGR versus depth relationship for each equilibration region.","size_kind":"fixed","variadic_record":true},"RVW":{"name":"RVW","sections":["SOLUTION"],"supported":null,"summary":"The RVW keyword defines the initial equilibration vaporized water in gas ratio values for all grid cells in the model and should be used in conjunction with the PBUB, PDEW, PRESSURE, RV, SGAS, SOIL and SWAT keywords etc., to fully describe the initial state of the model. The keyword should only be used if both gas and water phases have been activated in the model via the GAS and WATER keywords, and the VAPWAT is also present activating OPM Flow’s Vaporized Water Model. All the aforementioned keywords are in the RUNSPEC section.","parameters":[{"index":1,"name":"RVW","description":"RVW is an array of real positive numbers assigning the initial equilibration gas-vaporized water ratio values to each cell in the model. Repeat counts may be used, for example 20*1.30.","units":{"field":"stb/Mscf","metric":"sm3/sm3","laboratory":"rcc/scc"},"default":"None"}],"example":"--\n-- INITIAL EQUILIBRATION WATER VAPOR IN GAS RATIO VALUES FOR ALL CELLS\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nRVW\n1000*0.0000 1000* 0.0000 1000*1.3000 /\nThe above example defines the initial equilibration gas-vaporized water values to be 0.000 for all the cells in the first and second layers and 1.3000 for all the cells in the third layer.\n| Note This is an OPM Flow specific keyword for the simulator’s Water Vaporization Model that is activated by declaring that vaporized water is present in the run using the VAPWAT keyword in the RUNSPEC section. Use the command line option --enable-opm-rst-file=true to output the RVW data to the RESTART file. |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"array"},"RVWVD":{"name":"RVWVD","sections":["SOLUTION"],"supported":null,"summary":"The RVWVD keyword defines the vaporized water-gas ratio (Rvw) versus depth tables for each equilibration region that should be used when there is vaporized water in the model and the EQLOPT6 variable has been set to a positive integer on the EQUIL keyword in the SOLUTION section.","parameters":[{"index":1,"name":"DEPTH","description":"A columnar vector of real monotonically increasing down the column values that defines the depth values for the corresponding vaporized oil-gas ratio values, RVW","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":["Length","OilDissolutionFactor"]},{"index":2,"name":"RVW","description":"A columnar vector of real values that defines the vaporized water-gas ratio values, values at the corresponding DEPTH.","units":{"field":"stb/Mscf","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"None"}],"example":"Given NTEQUL equals three and NDRXVD is greater than or equal to two on the EQLDIMS keyword in the RUNSPEC section, then the following example defines the vaporized water-gas ratio versus depth functions.\n--\n-- DEPTH RVW\n-- STB/MSCF\n-- ------ --------\nRVWVD\n3000.0 0.00000\n8000.0 0.00000 / RVW VS DEPTH EQUIL REGN 01\n-- ------ --------\n3000.0 0.00000\n8000.0 0.00000 / RVW VS DEPTH EQUIL REGN 02\n-- ------ --------\n3000.0 0.00100\n8000.0 0.00100 / RVW VS DEPTH EQUIL REGN 03\nThe example shows three tables for three regions with constant RVW versus depth relationships for each equilibration region, with the first two tables having a zero vaporized water-gas ratio and the last region having a constant 0.001 stb/Mscf versus depth relationship.\n| Note This is an OPM Flow specific keyword for the simulator’s Water Vaporization Model that is activated by declaring that vaporized water is present in the run using the VAPWAT keyword in the RUNSPEC section. Use the command line option --enable-opm-rst-file=true to output the RVW data to the RESTART file. |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"fixed","variadic_record":true},"SALT":{"name":"SALT","sections":["SOLUTION"],"supported":null,"summary":"The SALT keyword defines the initial equilibration salt concentration values for all grid cells in the model and should be used in conjunction with the PBUB, PDEW, PRESSURE, RS, RV, SGAS, SGAS and SWAT keywords etc., to fully describe the initial state of the model. The keyword should only be used if the salt (brine) phase has been activated in the model via the BRINE keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"SALT","description":"SALT is an array of real positive numbers that are greater than or equal to zero assigning the initial equilibration salt concentration values to each cell in the model. Repeat counts may be used, for example 20*15.0.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None","value_type":"DOUBLE","dimension":"Concentration"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION SALT CONCENTRATION FOR ALL CELLS\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nSALT\n10000*0.0000 10000*0.0000 10000*15.000 /\nThe above example defines the initial equilibration salt concentration values to be 0.0000 for all the cells in the first and second layers and finally 15.000 for all the cells in the third layer.","size_kind":"fixed","size_count":1,"variadic_record":true},"SALTP":{"name":"SALTP","sections":["SOLUTION"],"supported":null,"summary":"The SALTP keyword defines the initial equilibration precipitated salt volume fraction values for all grid cells in the model and should be used in conjunction with the PBUB, PDEW, PRESSURE, RS, RV, SGAS, SOIL and SWAT keywords etc., to fully describe the initial state of the model. The keyword should only be used if the salt (brine) phase has been activated in the model via the BRINE keyword, and the PRECSALT keyword to activate OPM Flow’s Salt Precipitation Model. Both keywords are in the RUNSPEC section.","parameters":[{"index":1,"name":"SALTP","description":"SALTP is an array of real positive numbers that are greater than or equal to zero and less than or equal to one, that define the initial equilibration salt volume fraction values to each cell in the model. Repeat counts may be used, for example 20*0.15.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":"1"}],"example":"The example activates the standard Brine Tracking model using the BRINE keyword, OPM Flow’s Salt Precipitation model using the PRECSALT keyword, and OPM Flow’s vaporized water phase with the VAPWAT keyword; all three keywords are in the RUNSPEC section.\n-- ==============================================================================\n--\n-- RUNSPEC SECTION\n--\n-- ==============================================================================\nRUNSPEC\n--\n-- MAX MAX RSVD TVDP TVDP\n-- EQLNUM DEPTH NODES TABLE NODES\nEQLDIMS\n3 1* 20 1* 1* /\n--\n-- ACTIVATE STANDARD BRINE MODEL\n--\nBRINE\n--\n-- ACTIVATE THE OPM FLOW SALT PRECIPITATION MODEL (OPM FLOW KEYWORD)\n--\nPRECSALT\n--\n-- VAPORIZED WATER IN WET GAS IS PRESENT IN THE RUN (OPM FLOW KEYWORD)\n--\nVAPWAT\nThen in the SOLUTION section the SALTP keyword would be of the form:\n-- ==============================================================================\n--\n-- SOLUTION SECTION\n--\n-- ==============================================================================\nSOLUTION\n--\n-- DEFINE INITIAL PRECIPITATED SALT VOLUME FRACTION FOR ALL CELLS\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nSALTP\n1000*0.0000 1000*0.0000 1000*0.100 /\nHere the initial equilibration precipitated salt volume fraction values are set to 0.0000 for all the cells in the first and second layers and finally 0.1000 for all the cells in the third layer.\n| Note This is an OPM Flow specific keyword for the simulator’s Salt Precipitation Model that is activated by the PRECSALT keyword and declaring that vaporized water is present in the run via the VAPWAT in the RUNSPEC section. This keyword defines the initial precipitated salt volume fraction contained within the pore space. See SALT in the SOLUTION section that defines the initial salt concentration within the water phase. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"fixed","size_count":1,"variadic_record":true},"SALTPVD":{"name":"SALTPVD","sections":["SOLUTION"],"supported":true,"summary":"The SALTPVD keyword defines the initial precipitated salt volume fraction versus depth tables for each equilibration region for when OPM Flow’s Salt Precipitation Model has been activated in the input deck via the PRECSALT keyword in the RUNSPEC section. The keyword defines the initial deposited salt as a volume fraction (Ss), that is solid salt saturation.","parameters":[{"index":1,"name":"DEPTH","description":"A columnar vector of real monotonically increasing down the column values that defines the depth for corresponding salt volume fraction SALTPSAT.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":["Length","1"]},{"index":2,"name":"SALTPSAT","description":"A columnar vector of real values that defines the corresponding volume fraction of precipitated salt for the given depth. Note only the standard Brine Model is supported and therefore there should be only one columnar vector of SALTPSAT.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"The example activates the standard Brine Tracking model using the BRINE keyword, OPM Flow’s Salt Precipitation model using the PRECSALT keyword, and OPM Flow’s vaporized water phase with the VAPWAT keyword; all three keywords are in the RUNSPEC section. The example also sets the number of equilibrium regions to three (NTEQUL set to three on the EQLDIMS keyword also in the RUNSPEC), that is:\n-- ==============================================================================\n--\n-- RUNSPEC SECTION\n--\n-- ==============================================================================\nRUNSPEC\n--\n-- MAX MAX RSVD TVDP TVDP\n-- EQLNUM DEPTH NODES TABLE NODES\nEQLDIMS\n3 1* 20 1* 1* /\n--\n-- ACTIVATE STANDARD BRINE MODEL\n--\nBRINE\n--\n-- ACTIVATE THE OPM FLOW SALT PRECIPITATION MODEL (OPM FLOW KEYWORD)\n--\nPRECSALT\n--\n-- VAPORIZED WATER IN WET GAS IS PRESENT IN THE RUN (OPM FLOW KEYWORD)\n--\nVAPWAT\nThen in the SOLUTION section the SALTPVD keyword would be of the form:\n-- ==============================================================================\n--\n-- SOLUTION SECTION\n--\n-- ==============================================================================\nSOLUTION\n--\n-- PRECIPITATED SALT VOLUME FRACTION VERSUS DEPTH (OPM FLOW KEYWORD)\n--\n-- DEPTH SALTPSAT\n-- ------ --------\nSALTPVD\n3000.0 0.000\n8000.0 0.000 / EQUIL REGN 01\n-- ------ --------\n3000.0 0.000\n8000.0 0.000 / EQUIL REGN 02\n-- ------ --------\n3000.0 0.000\n8000.0 0.000 / EQUIL REGN 03\nHere the initial precipitated salt volume fraction has been set to zero for all three equilibration regions.\n| Note This is an OPM Flow specific keyword for the simulator’s Salt Precipitation Model that is activated by the PRECSALT keyword and declaring that vaporized water is present in the run via the VAPWAT in the RUNSPEC section. This is the initial precipitated salt volume fraction contained within the pore space, see SALTVD in the SOLUTION section that defines the initial salt concentration within the water phase. |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"fixed","variadic_record":true},"SALTREST":{"name":"SALTREST","sections":["SOLUTION"],"supported":false,"summary":"The SALTREST keyword defines restart salt concentration values for all grid cells in the model and should be used in runs that are using the RESTART facility, where the initial run has not used the Low Salt or Brine options. This allows for initial runs that have used the standard water PVT properties via the PVTW keyword in the PROPS section, to be restarted with salt dependent water properties. The keyword should only be used if the salt (brine) phase has been activated in the current restart run (not the initial run) via the BRINE keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"SALTREST","description":"SALTREST is an array of real positive numbers that are greater than or equal to zero assigning the restart salt concentration values to each cell in the model. Repeat counts may be used, for example 20*15.0.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None","value_type":"DOUBLE","dimension":"Concentration"}],"example":"--\n-- DEFINE RESTART SALTREST VALUES FOR ALL CELLS IN THE MODEL\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nSALTREST\n1000*0.0000 1000*0.0000 1000*15.000 /\nThe above example defines the restart salt concentration values to be 0.0000 for all the cells in the first and second layers and finally 15.000 for all the cells in the third layer.","size_kind":"fixed","size_count":1,"variadic_record":true},"SALTVD":{"name":"SALTVD","sections":["SOLUTION"],"supported":null,"summary":"The SALTVD keyword defines the initial salt concentration versus depth tables for each equilibration region for when the salt (brine) phase has been activated in the model via the BRINE keyword in the RUNSPEC section, and the EQLOPT1 variable has been set to a positive integer on the EQUIL keyword in the SOLUTION section. Secondly, the keyword should also be used to set the initial salt concentration versus depth if OPM Flow’s PRECSALT keyword in the RUNSPEC section has been used to activate the simulators Salt Precipitation model.","parameters":[{"index":1,"name":"DEPTH","description":"A columnar vector of real monotonically increasing down the column values that defines the depth for corresponding salt concentrations SALTCON.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":["Length","Concentration"]},{"index":2,"name":"SALTCON","description":"A columnar vector of real monotonically increasing down the column values that defines the corresponding salt concentration within the water phase for the given depth. There should be one columnar vector for each type of salt. For the standard Brine Model there is only one salt type and therefore there should be only one columnar vector of SALTCON. However, if the BRINE keyword has been invoked with the ECLMC keyword in the RUNSPEC section, then there should one columnar SALTCON vector for each declared salt type. It is recommended to provide initial salt concentrations less then or equal to values provided by SALTSOL keyword in the PROPS section.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None"}],"example":"The first example activates the standard Brine Tracking model using the BRINE keyword in the RUNSPEC section and sets the number of equilibrium regions to three (NTEQUIL set to 3 on the EQLDIMS keyword also in the RUNSPEC), that is:\n-- ==============================================================================\n--\n-- RUNSPEC SECTION\n--\n-- ==============================================================================\nRUNSPEC\n--\n-- MAX MAX RSVD TVDP TVDP\n-- EQLNUM DEPTH NODES TABLE NODES\nEQLDIMS\n3 1* 20 1* 1* /\n--\n-- ACTIVATE STANDARD BRINE MODEL\n--\nBRINE\nThen in the SOLUTION section the SALTVD keyword would be of the form:\n-- ==============================================================================\n--\n-- SOLUTION SECTION\n--\n-- ==============================================================================\nSOLUTION\n--\n-- DEPTH SALT-1 SALT-2 SALT-3 SALT-4\n-- SALTCON SALTCON SALTCON SALTCON\n-- ------ ------- ------- ------- ------- SALTVD\n3000.0 1.200\n8000.0 1.200 / EQUIL REGN 01\n-- ------ --------\n3000.0 1.300\n8000.0 1.300 / EQUIL REGN 02\n-- ------ --------\n3000.0 1.400\n8000.0 1.400 / EQUIL REGN 03\nThe next example shows how the SALTVD keyword is entered when both the ECLMC and BRINE keywords have activated the Multi-Component Brine model in the RUNSPEC section, that is:\n-- ==============================================================================\n--\n-- RUNSPEC SECTION\n--\n-- ==============================================================================\nRUNSPEC\n--\n-- MAX MAX RSVD TVDP TVDP\n-- EQLNUM DEPTH NODES TABLE NODES\nEQLDIMS\n3 1* 20 1* 1* /\n--\n--\n-- ACTIVATE MULTI-COMPONENT BRINE MODEL\n--\nECLMC\n--\n-- DEFINE WATER PHASE MULTI-COMPONENT BRINE COMPONENTS\n--\n-- SALT1 SALT2 SALT3 SALT4 SALT5\nBRINE\nNACL CACL MGC03 /\nThe above example activates the Multi-Component Brine model with three different water salinities for three equilibrium regions. In this case the resulting SALTVD keyword would be of the form:\n-- ==============================================================================\n--\n-- SOLUTION SECTION\n--\n-- ==============================================================================\nSOLUTION\n--\n-- DEPTH SALT-01 SALT-02 SALT-03 SALT-04\n-- CONCENTR CONCENTR CONCENTR CONCENTR\n-- ------ -------- -------- -------- -------- SALTVD\n3000.0 1.200 0.540 0.020\n7000.0 1.200 0.640 0.040 / EQUIL REGN 01\n-- ------ -------- -------- --------\n3000.0 1.300 0.440 0.020\n8000.0 1.300 0.540 0.040 / EQUIL REGN 02\n-- ------ -------- -------- --------\n5000.0 1.400 0.640 0.002\n8000.0 1.400 0.640 0.002 / EQUIL REGN 03\nIn this case there are three data sets, on one for each equilibrium region and three SALTCON columnar vectors, one for each salt type (NACL, CACL and MGC03) declared via the BRINE keyword in the RUNSPEC section.\nNote that the Multi-Component Brine model is not available in OPM Flow.\n| Note This is the initial salt concentration contained within the water phase, see the SALTPVD keyword in the SOLUTION section that defines the initial salt volume fraction that has been precipitated into the pore space. |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"fixed","variadic_record":true},"SBIOF":{"name":"SBIOF","sections":["SOLUTION"],"supported":null,"summary":"The SBIOF keyword defines the initial equilibration biofilm volume fraction for all grid cells in the model. The keyword should only be used if either the BIOFILM or MICP model has been activated in the RUNSPEC section.","parameters":[{"index":1,"name":"SBIOF","description":"SBIOF is an array of real numbers that are greater than or equal to zero and less than or equal to one assigning the initial equilibration biofilm volume fraction values to each cell in the model. Repeat counts may be used, for example 20*0.0010.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION BIOFILM VOLUME FRACTION FOR ALL CELLS\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nSBIOF\n10000*0.0000 10000*0.0000 10000*0.0010 /\nThe above example defines the initial equilibration biofilm volume fraction values to be 0.0000 for all the cells in the first and second layers and finally 0.0010 for all the cells in the third layer.\n| Note This is an OPM Flow specific keyword. |\n|--------------------------------------------|","size_kind":"array"},"SCALC":{"name":"SCALC","sections":["SOLUTION"],"supported":null,"summary":"The SCALC keyword defines the initial equilibration calcite volume fraction for all grid cells in the model. The keyword should only be used if the MICP model has been activated in the RUNSPEC section.","parameters":[{"index":1,"name":"SCALC","description":"SCALC is an array of real numbers that are greater than or equal to zero and less than or equal to one assigning the initial equilibration calcite volume fraction values to each cell in the model. Repeat counts may be used, for example 20*0.0010.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION CALCITE VOLUME FRACTION FOR ALL CELLS\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nSCALC\n1000*0.0000 1000*0.0000 1000*0.0010 /\nThe above example defines the initial equilibration calcite volume fraction values to be 0.0000 for all the cells in the first and second layers and finally 0.0010 for all the cells in the third layer.\n| Note This is an OPM Flow specific keyword. |\n|--------------------------------------------|","size_kind":"array"},"SCVD":{"name":"SCVD","sections":["SOLUTION"],"supported":false,"summary":"The SCVD keyword defines the initial coal solvent concentration versus depth tables for each equilibration region for when the coal phase has been activated in the run via the COAL keyword in the RUNSPEC section. The keyword may be used in conjunction with the SOLVCONC keyword in the SOLUTION section, to fully describe the initial state of the model. Note both SOLVCONC and SCVD are optional as the simulator will calculate the coal gas concentration based on the equilibrium concentration and the block pressure.","parameters":[{"index":1,"name":"DEPTH","description":"A columnar vector of real monotonically increasing down the column values that defines the depth values for the corresponding coal solvent concentration, SCVALS.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":["Length","1"]},{"index":2,"name":"SCVALS","description":"A columnar vector of real values that defines the coal solvent concentration values at the corresponding DEPTH.","units":{"field":"Mscf/ft3","metric":"sm3/m3","laboratory":"scc/cc"},"default":"None"}],"example":"Given NTEQUL equals three and NDRXVD is greater than or equal to two on the EQLDIMS keyword in the RUNSPEC section, then the following example defines the coal solvent concentration versus depth functions.\n--\n-- DEPTH SOLVC\n-- MSCF/FT\n-- ------ --------\nSCVD\n100.0 75.5000\n1000.0 75.5000 / SC VS DEPTH EQUIL REGN 01\n-- ------ --------\n100.0 65.5000\n1000.0 65.5000 / SC VS DEPTH EQUIL REGN 02\n-- ------ --------\n100.0 60.0000\n1000.0 60.0000 / SC VS DEPTH EQUIL REGN 03\nHere three tables are entered with a constant coal solvent concentration versus depth relationship for each equilibration region","size_kind":"fixed","variadic_record":true},"SFOAM":{"name":"SFOAM","sections":["SOLUTION"],"supported":false,"summary":"The SFOAM keyword defines the initial equilibration foam concentration values for all grid cells in the model and should be used in conjunction with the PBUB, PDEW, PRESSURE, RS, RV, SGAS, SGAS and SWAT keywords etc., to fully describe the initial state of the model. The keyword should only be used if the foam phase has been activated in the model via the FOAM keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"SFOAM","description":"SFOAM is an array of real positive numbers that are greater than or equal to zero assigning the initial equilibration foam concentration values to each cell in the model. Units are dependent on the transport phase specified via the FOAMOPT1 variable on the FOAMOPTS keyword in the PROPS section. FOAMOPT1 should be set to either GAS or WATER. Repeat counts may be used, for example 20*0.5","units":{"field":"Gas: lb/Mscf Water: lb/stb","metric":"Gas: kg/sm3 Water: kg/sm3","laboratory":"Gas: gm/scc Water: gm/scc"},"default":"None"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION FOAM VALUES FOR ALL CELLS IN THE MODEL\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nSFOAM\n1000*0.0000 1000*0.0000 1000*0.500 /\nThe above example defines the initial equilibration foam concentration values to be 0.0000 for all the cells in the first and second layers and finally 0.500 for all the cells in the third layer.","size_kind":"array"},"SGAS":{"name":"SGAS","sections":["SOLUTION"],"supported":null,"summary":"The SGAS keyword defines the initial equilibration gas saturation values for all grid cells in the model and should be used in conjunction with the PBUB, PDEW, PRESSURE, RS, RV, SOIL and SWAT keywords etc., to fully describe the initial state of the model. The keyword should only be used if the gas phase has been activated in the model via the GAS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"SGAS","description":"SGAS is an array of real positive numbers that are greater than or equal to zero and less than or equal to one assigning the initial equilibration gas saturation values to each cell in the model. Repeat counts may be used, for example 20*0.600.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION GAS SAT VALUES FOR ALL CELLS IN THE MODEL\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nSGAS\n1000*0.7000 1000*0.6500 1000*0.6000 /\nThe above example defines the initial equilibration gas saturation values to be 0.7000 for all the cells in the first layer, 0.6500 for all the cells in the second layer, and finally 0.6000 for all the cells in the third layer.","size_kind":"array"},"SMICR":{"name":"SMICR","sections":["SOLUTION"],"supported":null,"summary":"The SMICR keyword defines the initial equilibration microbial concentration values for all grid cells in the model. The keyword should only be used if either the BIOFILM or MICP model has been activated in the RUNSPEC section.","parameters":[{"index":1,"name":"SMICR","description":"SMICR is an array of real numbers that are greater than or equal to zero assigning the initial equilibration microbial concentration values to each cell in the model. Repeat counts may be used, for example 20*0.1500.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION MICROBIAL CONCENTRATION FOR ALL CELLS\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nSMICR\n1000*0.0000 1000*0.0000 1000*0.1500 /\nThe above example defines the initial equilibration microbial concentration values to be 0.0000 for all the cells in the first and second layers and finally 0.1500 for all the cells in the third layer.\n| Note This is an OPM Flow specific keyword. |\n|--------------------------------------------|","size_kind":"array"},"SOIL":{"name":"SOIL","sections":["SOLUTION"],"supported":null,"summary":"The SOIL keyword defines the initial equilibration oil saturation values for all grid cells in the model and should be used in conjunction with the PBUB, PDEW, PRESSURE, RS, RV, SGAS and SWAT keywords etc., to fully describe the initial state of the model. The keyword should only be used if the oil phase has been activated in the model via the OIL keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"SOIL","description":"SOIL is an array of real positive numbers that are greater than or equal to zero and less than or equal to one assigning the initial equilibration oil saturation values to each cell in the model. Repeat counts may be used, for example 20*0.600.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION OIL SAT VALUES FOR ALL CELLS IN THE MODEL\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nSOIL\n1000*0.7000 1000*0.6500 1000*0.6000 /\nThe above example defines the initial equilibration oil saturation values to be 0.7000 for all the cells in the first layer, 0.6500 for all the cells in the second layer, and finally 0.6000 for all the cells in the third layer.","size_kind":"array"},"SOLUTION":{"name":"SOLUTION","sections":["SOLUTION"],"supported":null,"summary":"The SOLUTION activation keyword marks the end of the REGIONS section and the start of the SOLUTION section that defines the parameters used to initialize the model, by:","parameters":[],"example":"-- ==============================================================================\n--\n-- SOLUTION SECTION\n--\n-- ==============================================================================\nSOLUTION\nThe above example marks the end of the REGIONS section and the start of the SOLUTION section in the OPM Flow data input file.","size_kind":"none","size_count":0},"SOLVCONC":{"name":"SOLVCONC","sections":["GRID"],"supported":false,"summary":"The SOLVCONC keyword defines the initial coal solvent concentration values for all matrix grid cells in the model and should be used in conjunction with the SCVD keyword in the SOLUTION section, to fully describe the initial state of the model. The keyword should only be used if the coal phase has been activated in the model via the COAL keyword in the RUNSPEC section. Note both SOLVCONC and SCVD are optional as the simulator will calculate the coal solvent concentration based on the equilibrium concentration and the block pressure.","parameters":[{"index":1,"name":"SOLVCONC","description":"SOLVCONC is an array of real positive numbers that define the initial equilibration coal solvent concentration values to each matrix cell in the model. Repeat counts may be used, for example 20*75.0.","units":{"field":"Mscf/ft3","metric":"sm3/m3","laboratory":"scc/cc"},"default":"None"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION COAL SOLVENT CONCENTRATION FOR ALL CELLS\n-- BASED ON NX = 100, NY = 100 AND NZ = 6\n--\nSOLVCONC\n1000*75.500 1000*65.500 1000*60.000 /\nThe above example defines the initial coal solvent concentration values to be 75.500 for all the matrix cells in the first layer, 65.500 for all the cells in the second layer, and finally 60.000 for all the cells in the third layer.","size_kind":"array"},"SOLVFRAC":{"name":"SOLVFRAC","sections":["SOLUTION"],"supported":false,"summary":"The SOLVFRAC keyword defines the initial solvent faction within the gas phase values for all matrix grid cells in the model. The keyword should only be used if the coal phase has been activated in the model via the COAL keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"SOLVFRAC","description":"SOLVFRAC is an array of real positive numbers that define the initial solvent fraction within the gas phase values for each matrix cell in the model. Repeat counts may be used, for example 20*0.075.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION GAS SOLVENT FRACTION FOR ALL CELLS\n-- BASED ON NX = 100, NY = 100 AND NZ = 6\n--\nSOLVFRAC\n1000*0.0250 1000*0.0350 1000*0.0500 /\nThe above example defines the initial gas solvent fraction values to be 0.250 for all the matrix cells in the first layer, 0.0350 for all the cells in the second layer, and finally 0.0500 for all the cells in the third layer.","size_kind":"array"},"SOXYG":{"name":"SOXYG","sections":["SOLUTION"],"supported":null,"summary":"The SOXYG keyword defines the initial equilibration oxygen concentration values for all grid cells in the model. The keyword should only be used if the MICP model has been activated in the RUNSPEC section.","parameters":[{"index":1,"name":"SOXYG","description":"SOXYG is an array of real numbers that are greater than or equal to zero assigning the initial equilibration oxygen concentration values to each cell in the model. Repeat counts may be used, for example 20*0.1500","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION OXYGEN CONCENTRATION FOR ALL CELLS\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nSOXYG\n1000*0.0000 1000*0.0000 1000*0.1500 /\nThe above example defines the initial equilibration oxygen concentration values to be 0.0000 for all the cells in the first and second layers and finally 0.1500 for all the cells in the third layer.\n| Note This is an OPM Flow specific keyword. |\n|--------------------------------------------|","size_kind":"array"},"SPOLY":{"name":"SPOLY","sections":["SOLUTION","SPECIAL"],"supported":null,"summary":"The SPOLY keyword defines the initial equilibration polymer concentration values for all grid cells in the model and should be used in conjunction with the PBUB, PDEW, PRESSURE, RS, RV, SGAS, SGAS and SWAT keywords etc., to fully describe the initial state of the model. The keyword should only be used if the polymer phase has been activated in the model via the POLYMER keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"SPOLY","description":"SPOLY is an array of real positive numbers that are greater than or equal to zero assigning the initial equilibration polymer concentration values to each cell in the model. Repeat counts may be used, for example 20*25.0.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION POLYMER VALUES FOR ALL CELLS IN THE MODEL\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nSPOLY\n1000*0.0000 1000*0.0000 1000*15.000 /\nThe above example defines the initial equilibration polymer concentration values to be 0.0000 for all the cells in the first and second layers and finally 15.000 for all the cells in the third layer.","size_kind":"array"},"SPOLYMW":{"name":"SPOLYMW","sections":["SOLUTION"],"supported":null,"summary":"The SPOLYMW keyword defines the initial equilibration polymer molecular weights for all grid cells in the model and should only be be used with OPM Flow's Polymer Molecular Weight Transport option, together with the other standard equilibration keywords, in order to fully describe the initial state of the model.","parameters":[{"index":1,"name":"SPOLYMW","description":"SPOLYMW is an array of real positive numbers that are greater than or equal to zero assigning the initial equilibration polymer molecular weights to each cell in the model. Repeat counts may be used, for example 20*5.0","units":{"field":"lb/lb-M","metric":"kg/kg-M","laboratory":"gm/gm-M"},"default":"0,0"}],"example":"--\n-- INITIAL EQUILIBRATION POLYMER MOLECULAR WEIGHTS FOR ALL CELLS\n--\n-- ARRAY CONSTANT ---------- BOX ---------\n-- I1 I2 J1 J2 K1 K2\nEQUALS\nSPOLYMW 0.0000 1* 1* 1* 1* 1 5 / LAYERS 1 TO 5\nSPOLYMW 5.0000 1* 1* 1* 1* 6 7 / LAYERS 6 TO 7\nSPOLYMW 0.0000 1* 1* 1* 1* 8 20 / LAYERS 8 TO 20\n/\nThe above example defines the initial equilibration polymer molecular weights to be 0.0000 for all the cells, except for layers six to seven, where the polymer molecular weight is set to five for these cells.\n| Note This is an OPM Flow specific keyword that employs an alternative polymer flood model based on a Polymer Molecular Weight Transport equation, that is not available in the commercial simulator. The model has been tested using metric units; however, using either field or laboratory units with the option should be considered experimental. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"array"},"SSOL":{"name":"SSOL","sections":["SOLUTION"],"supported":null,"summary":"The SSOL keyword defines the initial equilibration solvent saturation values for all grid cells in the model and should be used in conjunction with the PBUB, PDEW, PRESSURE, RS, RV, SGAS, SOIL and SWAT keywords etc., to fully describe the initial state of the model. The keyword should only be used if the solvent phase has been activated in the model via the SOLVENT keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"SSOL","description":"SSOL is an array of real positive numbers that are greater than or equal to zero and less than or equal to one assigning the initial equilibration solvent saturation values to each cell in the model. Repeat counts may be used, for example 20*0.000.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION GAS SAT VALUES FOR ALL CELLS IN THE MODEL\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nSSOL\n1000*0.0000 1000*0.0000 1000*0.0000 /\nThe above example defines the initial equilibration solvent saturation values to be 0.0 for all the cells in the in the model.","size_kind":"array"},"SUREA":{"name":"SUREA","sections":["SOLUTION"],"supported":null,"summary":"The SUREA keyword defines the initial equilibration urea concentration values for all grid cells in the model. The keyword should only be used if the MICP model has been activated in the RUNSPEC section.","parameters":[{"index":1,"name":"SUREA","description":"SUREA is an array of real numbers that are greater than or equal to zero assigning the initial equilibration urea concentration values to each cell in the model. Repeat counts may be used, for example 20*30.0.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION UREA CONCENTRATION FOR ALL CELLS\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nSUREA\n1000*0.0000 1000*0.0000 1000*20.0 /\nThe above example defines the initial equilibration urea concentration values to be 0.0000 for all the cells in the first and second layers and finally 20.0 for all the cells in the third layer.\n| Note This is an OPM Flow specific keyword. |\n|--------------------------------------------|","size_kind":"array"},"SURF":{"name":"SURF","sections":["SOLUTION"],"supported":false,"summary":"The SURF keyword defines the initial equilibration surfactant concentration values for all grid cells in the model and should be used in conjunction with the PBUB, PDEW, PRESSURE, RS, RV, SGAS, SGAS and SWAT keywords etc., to fully describe the initial state of the model. The keyword should only be used if the surfactant phase has been activated in the model via the SURFACT keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"SURF","description":"SURF is an array of real positive numbers that are greater than or equal to zero assigning the initial equilibration surfactant concentration values to each cell in the model. Repeat counts may be used, for example 20*25.0.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION SURFACTANT VALUES FOR ALL CELLS\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nSURF\n1000*0.0000 1000*0.0000 1000*0.2500 /\nThe above example defines the initial equilibration surfactant concentration values to be 0.0000 for all the cells in the first and second layers and finally 0.2500 for all the cells in the third layer.","size_kind":"array"},"SWAT":{"name":"SWAT","sections":["SOLUTION"],"supported":null,"summary":"The SWAT keyword defines the initial equilibration water saturation values for all grid cells in the model and should be used in conjunction with the PBUB, PDEW, PRESSURE, RS, RV, SGAS and SOIL keywords etc., to fully describe the initial state of the model. The keyword should only be used if the water phase has been activated in the model via the WATER keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"SWAT","description":"SWAT is an array of real positive numbers that are greater than or equal to zero and less than or equal to one assigning the initial equilibration water saturation values to each cell in the model. Repeat counts may be used, for example 20*0.300.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"--\n-- DEFINE INITIAL EQUILIBRATION WAT SAT VALUES FOR ALL CELLS IN THE MODEL\n-- BASED ON NX = 100, NY = 100 AND NZ = 3\n--\nSWAT\n1000*0.2000 1000*0.2500 1000*0.4500 /\nThe above example defines the initial equilibration water saturation values to be 0.2000 for all the cells in the first layer, 0.2500 for all the cells in the second layer, and finally 0.4500 for all the cells in the third layer.","size_kind":"array"},"TBLK":{"name":"TBLK","sections":["SOLUTION"],"supported":null,"summary":"TBLK keyword defines the initial tracer concentration for all or selected cells in the model, for when the TRACERS keyword in the RUNSPEC section has declared the maximum number of tracers for each phase, and the TRACER keyword in the PROPS section has defined the tracer. This keyword is not in the standard keyword format due to the tracer name being concatenated to the keyword TBLK to fully define the tracer being initialized.","parameters":[{"index":1,"name":"NAME","description":"A character string of up to eight characters, consisting of TBLK as the first four characters followed by a four letter character string defining the tracer’s name. The fifth character should either be the letter F or the letter S, that indicates the state of the tracer either to be free (F) or in solution (S). For example, TBLKFIGS (free) or TBLKSIGS (solution). The last three characters of NAME (the effective tracer name) must also match an entry on the TRACER keyword’s NAME parameter, in the PROPS section. Note it is best to void names beginning with the letters F, S, and T as these names may create naming issues in post-processing software.","units":{},"default":"None"},{"index":2,"name":"TBLK","description":"TBLK is an array of real numbers greater than or equal to zero, that are assigned the tracer concentration values for each cell in the model or the current input BOX. Repeat counts may be used, for example 200*0.0. The units for the tracer, if required, are set on the TRACER keyword in the PROPS section. This should be the same as the PHASE in the model.","units":{"field":"Liquid: TBLK/stb Gas: TBLK/Mscf","metric":"Liquid: TBLK/sm3 Gas: TBLK/sm3","laboratory":"Liquid: TBLK/scc Gas: TBLK/scc"},"default":"None"}],"example":"The following TRACERS keyword in the RUNSPEC section declares the number of tracers in the model.\n--\n-- NUMBER AND TYPE OF TRACERS\n-- NO OIL NO WAT NO GAS NO ENV DIFF MAX MIN TRACER\n-- TRACERS TRACERS TRACERS TRACERS CONTL NONLIN NONLIN NONLIN\nTRACERS\n0 0 1 0 'NODIFF' 1* 1* 1* /\nAnd the TRACER keyword in the PROPS section declares the tracer name and the phase for the tracer.\n--\n-- DEFINE TRACER NAMES\n--\n-- TRACER TRACER\n-- NAME PHASE\n-- ------ ------\nTRACER\n'IGS' 'GAS' / INJECTED GAS\n/\nFinally, the TBLK keyword in the SOLUTION section sets the initial tracer grid block concentrations in both the free and solution states.\n--\n-- INITIAL TRACER CONCENTRATIONS\n--\nTBLKFIGS\n1000*0.0 / TRACER FIGS CONCENTRATIONS\nTBLKSIGS\n1000*0.0 / TRACER SIGS CONCENTRATIONS\nHere the initial concentrations are set to zero.\nThen in the SCHEDULE section one can us the WTRACER keyword to define the well injecting the tracer and the tracer concentration being injected,.\n--\n-- DEFINE CONCENTRATION OF TRACERS IN THE INJECTION STREAMS,\n-- INJECTION TRACER CONCENTRATIONS NOT DEFINED USING THE WTRACER\n-- KEYWORD ARE ASSUMED TO BE ZERO.\n--\n-- WELL NAME TRACER TRACER TRACER\n-- NAME TRACER VALUE CUM GROUP\nWTRACER\n'GI01' 'IGS' 1.0 /\n/\nIn this case, well GI01 is a gas injection well injecting gas with a tracer concentration of 1.0. The example shows how to track dry gas injection in a gas condensate reservoir, although, the example can be used for any type of gas injection.\n| Note Currently, one cannot initialize tracers using the EQUALS keyword. Instead use the array format, that is the keyword followed by the required number of values, or the TVDP keyword in the SOLUTION section to set the initial tracer concentrations as a function of depth. |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"array"},"TEMPI":{"name":"TEMPI","sections":["SOLUTION"],"supported":null,"summary":"This keyword defines the initial reservoir temperature for each cell in the model. The keyword is used to explicitly define the initial reservoir temperature via the Enumeration Initialization method rather than defining a uniform initial temperature or defining temperature versus depth tables.","parameters":[{"index":1,"name":"TEMPI","description":"TEMPI is an array of real positive numbers assigning the initial temperature to each cell in the model. Repeat counts may be used, for example 20*100.0.","units":{"field":"oF","metric":"oC","laboratory":"oC"},"default":"None"}],"example":"--\n-- DEFINE GRID BLOCK TEMPERATURE FOR ALL CELLS\n– (BASED ON NX x NY x NZ = 300)\n--\nTEMPI\n100*212.0 100*215.0 100*220.0 /\nThe above example defines the initial temperature to be 212.0, 215.0, and 220.0 oF for the first, second and third layers in the model for all 300 cells, as defined by the DIMENS keyword in the RUNSPEC section.","size_kind":"array"},"THPRES":{"name":"THPRES","sections":["SOLUTION"],"supported":false,"summary":"The THPRES defines the threshold pressure between various equilibration regions that have been defined by the EQLNUM keyword in the REGIONS section. The threshold pressure defines the potential difference between two regions which must be exceeded before flow can occur between the two regions. Once flow occurs the potential between the two regions is reduced by the threshold pressure.","parameters":[{"index":1,"name":"EQLNUM1","description":"EQLNUM1 is an a positive integer that is greater or equal to one and less than or equal to NTEQUL on the EQLDIMS keyword in the RUNSPEC section, that defines the “from” equilibration region number.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"INT"},{"index":2,"name":"EQLNUM2","description":"EQLNUM1 is an a positive integer that is greater or equal to one and less than or equal to NTEQUL on the EQLDIMS keyword in the RUNSPEC section, that defines the “to” equilibration region number.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"INT"},{"index":3,"name":"THPRES","description":"THPRES defines the threshold pressure from EQLNUM1 to EQLNUM2 and from EQLNUM2 to EQLNUM1. The default value of 1* sets the threshold pressure to a value that initially prevents flow between the two equilibration regions. Any subsequent production or injection in either of the two equilibration regions will therefore result in flow between the two regions. Thus, this default initially isolates the two equilibration regions. If a equilibration region number pair has not been explicitly defined by this keyword the THPRES is set to zero, for no threshold pressure.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1*","value_type":"DOUBLE","dimension":"Pressure"}],"example":"Given NTEQUL is equal to six on the EQLDIMS keyword in the RUNSPEC section,\n--\n-- EQLNUM EQLNUM THPRES\n-- FROM TO VALUE\nTHPRES\n1 2 0.588031 / REGN 1 TO REGN 2\n2 1 0.588031 / REGN 2 TO REGN 1\n1 3 0.787619 / REGN 1 TO REGN 3\n3 1 0.787619 / REGN 3 TO REGN 1\n1 4 7.000830 / REGN 1 TO REGN 4\n4 1 7.000830 / REGN 4 TO REGN 1\n/\nThe above example defines the threshold pressures between equilibration regions one and two, one and three and one and four. As the threshold pressures between regions one and five and one and six (as well as other combinations), have not been explicitly set in the example, the threshold pressures for these combinations are set to zero.\nHowever, as the irreversible option, as defined by IRREVER variable on EQLOPTS keyword in the RUNSPEC section, is not supported, then example can be simplified to:\n--\n-- EQLNUM EQLNUM THPRES\n-- FROM TO VALUE\nTHPRES\n1 2 0.588031 / REGN 1 AND REGN 2\n1 3 0.787619 / REGN 1 AND REGN 3\n1 4 7.000830 / REGN 1 AND REGN 4\n/\nAgain, as the threshold pressures between regions one and five and one and six (as well as other combinations), have not been explicitly set in the example, the threshold pressures for these combinations are set to zero.\n| Note Care should be taken that cells in different EQLNUM regions are not in communication, as this will result in an unstable initial equilibration. |\n|------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":3,"size_kind":"list"},"TVDP":{"name":"TVDP","sections":["SOLUTION"],"supported":null,"summary":"This keyword defines the initial equilibration tracer concentration versus depth functions for each grid cell in the model, for when the Tracer option has been enabled by the TRACERS keyword in the RUNSPEC section. The maximum number of tracers for each phase are declared on the TRACERS keyword in the RUNSPEC section. Unlike other keywords, the TVDP keyword must be concatenated with the name of the tracer declared by the TRACER keyword in the PROPS section as outlined in Table 10.61.","parameters":[{"index":1,"name":"DEPTH","description":"A columnar vector of real monotonically increasing down the column values that defines the depth values for the corresponding initial tracer saturations, TVDP","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":["Length","1"]},{"index":2,"name":"TVDPVAL","description":"A columnar vector of real values, greater than or equal to zero, that defines the initial tracer concentration values at the corresponding DEPTH. If tracer units have been defined by the UNITS parameter on the TRACER keyword in the PROPS section, then the units of TVDPVAL are the ratio of UNITS divided by the TVDPVAL units given below. For example, if UNITS was defined as kg, then for metric units TVDPVAL units would be kg/sm3.","units":{"field":"Liquid: stb Gas: Mscf","metric":"Liquid: sm3 Gas: sm3","laboratory":"Liquid: scc Gas: scc"},"default":"None"}],"example":"This example is taken from Norne model, in which there are seven tracers related to the water phase.\n-- ==============================================================================\n--\n-- RUNSPEC SECTION\n--\n-- ==============================================================================\nRUNSPEC\n--\n-- MAX MAX RSVD TVDP TVDP\n-- EQLNUM DEPTH NODES TABLE NODES\nEQLDIMS\n9 1* 20 7 1* /\n-- ==============================================================================\n--\n-- PROPS SECTION\n--\n-- ==============================================================================\nPROPS\n--\n-- DEFINE TRACER NAMES\n--\n-- TRACER TRACER\n-- NAME PHASE\n-- ------ ------\nTRACER\nSEA WAT /\nHTO WAT /\nS36 WAT /\n2FB WAT /\n4FB WAT /\nDFB WAT /\nTFB WAT /\n/\n-- ==============================================================================\n--\n-- SOLUTION SECTION\n--\n-- ==============================================================================\nSOLUTION\n--\n-- INITIAL EQUILIBRATION TRACER SATURATION VERSUS DEPTH\n--\n-- DEPTH TRACER\n-- CONCENT\n-- ------ --------\nTVDPFSEA\n1000.0 0.0\n5000.0 0.0 / TRACER FSEA CONCENTRATION VS DEPTH\nTVDPFHTO\n1000.0 0.0\n5000.0 0.0 / TRACER FHTO CONCENTRATION VS DEPTH\nTVDPFS36\n1000.0 0.0\n5000.0 0.0 / TRACER FS36 CONCENTRATION VS DEPTH\nTVDPF2FB\n1000.0 0.0\n5000.0 0.0 / TRACER F2FB CONCENTRATION VS DEPTH\nTVDPF4FB\n1000.0 0.0\n5000.0 0.0 / TRACER F4FB CONCENTRATION VS DEPTH\nTVDPFDFB\n1000.0 0.0\n5000.0 0.0 / TRACER FDFB CONCENTRATION VS DEPTH\nTVDPFTFB\n1000.0 0.0\n5000.0 0.0 / TRACER FTFB CONCENTRATION VS DEPTH\nHere we first define the number of tracers in the model via the EQLDIMS keyword in the RUNSPEC section, then the actual tracers themselves in the PROPS section using the TRACER keyword, and finally the initial tracer concentrations are all set to zero via the TVDP keyword in the PROPS section.","size_kind":"fixed","templated":true,"variadic_record":true},"VAPPARS":{"name":"VAPPARS","sections":["SOLUTION","SCHEDULE"],"supported":null,"summary":"VAPPARS defines the rate of oil vaporization in the presence of undersaturated gas and the rate at which the remaining oil gets “heavier” via the reduction in the solution gas-oil ratio (“Rs”). This keyword should only be used if the OIL, GAS, DISGAS and VAPOIL keywords in the RUNSPEC section have been invoked to allow oil, gas, dissolved gas and vaporized oil to be present in the model.","parameters":[{"index":1,"name":"VAPPAR1","description":"VAPPAR1 is a real positive dimensionless number that defines the rate at which oil vaporizes into the available undersaturated gas in a grid block. The default value of zero invokes the standard black-oil formulation in which all oil vaporizes into the available undersaturated phase in a grid cell. Increasing this parameter decreases the rate of vaporization. Typical values for VAPPAR1 range from zero to five.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0","value_type":"DOUBLE"},{"index":2,"name":"VAPPAR2","description":"VAPPAR2 is a real positive dimensionless number that defines the rate at which the Rs of the remaining oil in a grid cell decreases The default value of zero invokes the standard black-oil formulation in which the remaining oil’s Rs does not change as the oil vaporizes into the available undersaturated gas in a grid cell. Increasing this parameter increases the difference between the remaining oil and the vaporized oil Rs values. Typical values for VAPPAR2 are less than one.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0","value_type":"DOUBLE"}],"example":"The first example sets the black-oil default parameters\n--\n-- OIL VAPORIZATION PARAMETERS\n--\n-- OIL-VAP RS-INCS\n-- VAPPAR1 VAPPAR2\nVAPPARS\n0 0 /\nAnd the second example decreases the rate at which the oil vaporizes into the available undersaturated gas and increases the difference between the grid block oil saturation Rs and the vaporized oil Rs within a grid cell.\n--\n-- OIL VAPORIZATION PARAMETERS\n--\n-- OIL-VAP RS-INCS\n-- VAPPAR1 VAPPAR2\nVAPPARS\n1.5 0.150 /\nAgain, the keyword is normally used in history matching field performance to control the availability of the vaporized oil phase.","expected_columns":2,"size_kind":"fixed","size_count":1},"VISDATES":{"name":"VISDATES","sections":["SCHEDULE"],"supported":false,"summary":"The VISDATES keyword defines External Reservoir Geo-Mechanics VISAGE option stress dates. The keyword should not be used in input decks as the associated data is generated by an external program.","parameters":[{"index":1,"name":"DAY","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"MONTH","description":"","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"YEAR","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"TIMESTAMP","description":"","units":{},"default":"00:00:00","value_type":"STRING"}],"example":"","expected_columns":4,"size_kind":"list"},"VISOPTS":{"name":"VISOPTS","sections":["SOLUTION"],"supported":false,"summary":"The VISDATES keyword defines External Reservoir Geo-Mechanics VISAGE option modeling options. The keyword should not be used in input decks as the associated data is generated by an external program.","parameters":[{"index":1,"name":"INIT_RUN","description":"","units":{},"default":"NO","value_type":"STRING"},{"index":2,"name":"EXIT","description":"","units":{},"default":"NO","value_type":"STRING"},{"index":3,"name":"ACTIVE","description":"","units":{},"default":"NO","value_type":"STRING"},{"index":4,"name":"REL_TOL","description":"","units":{},"default":"0.05","value_type":"DOUBLE"},{"index":5,"name":"UNUSED","description":"","units":{},"default":"","value_type":"STRING"},{"index":6,"name":"RETAIN_RESTART_FREQUENCY","description":"","units":{},"default":"NO","value_type":"STRING"},{"index":7,"name":"RETAIN_RESTART_CONTENT","description":"","units":{},"default":"NO","value_type":"STRING"},{"index":8,"name":"ERROR","description":"","units":{},"default":"ERROR","value_type":"STRING"}],"example":"","expected_columns":8,"size_kind":"list"},"ALL":{"name":"ALL","sections":["SUMMARY"],"supported":null,"summary":"This keyword activates the writing out of a standard set of summary production and injection data vectors for the field, group and well objects to the SUMMARY (*.SMSPEC and *.UNSMRY) and RSM (*.RSM) files. Table 11.26lists the production, injection, pressure and volume summary variables written out by the ALL keyword, and Table 11.27list the aquifer variables.","parameters":[],"example":"-- ==============================================================================\n--\n-- SUMMARY SECTION\n--\n-- ==============================================================================\nSUMMARY\n--\n-- EXPORT STANDARD SUMMARY VARIABLE VECTORS TO FILE\n--\nALL\n--\n-- ACTIVATE COLUMNAR SUMMARY DATA REPORTING OPTION\n--\nRUNSUM\n--\n-- ACTIVATE SUMMARY DATA RSM FILE OUTPUT OPTION\n--\nSEPARATE\nNote the SEPARATE keyword is not required for OPM Flow as this is the default behavior; however, it is probably good practice to include it if the same input decks are being run with commercial simulator.\n| Standard Production, Injection, and Pressures Summary Variables | | | | | |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-------|-------|------|-----------------------------------------------------------|\n| Variable | Root | Field | Group | Well | Comment |\n| Gas Injection Rate | GIR | FGIR | GGIR | WGIR | |\n| Gas Injection Total | GIT | FGIT | GGIT | WGIT | |\n| Gas Production Rate | GPR | FGPR | GGPR | WGPR | Produced reservoir gas only, gas lift gas is excluded. |\n| Gas Production Total | GPT | FGPT | GGPT | WGPT | |\n| Oil Injection Rate | OIR | FOIR | GOIR | WOIR | |\n| Oil Injection Total | OIT | FOIT | GOIT | WOIT | |\n| Oil Production Rate ","size_kind":"none","size_count":0},"DATE":{"name":"DATE","sections":["SUMMARY"],"supported":null,"summary":"This keyword activates the writing out of the date of each time step to the SUMMARY file. Normally only the time in days and decimal years are written out to the SUMMARY file, activating the DATE option also results in the DATE being written out to the SUMMARY file as well. This option is normally used when the RUNSUM keyword in the SUMMARY section has been activated to produce a RSM file.","parameters":[],"example":"The following example shows an example RSM file output when the DATE option has not been activated.\n-------------------------------------------------------------------------------\nSUMMARY OF RUN NO-DATE-KEYWORD\n-------------------------------------------------------------------------------\nTIME YEARS FPR FOEW FOPR FOPT\nDAYS YEARS PSIA STB/DAY STB\n-------------------------------------------------------------------------------\n0 0 4467.125 0 0 0\n1.000000 0.002738 4466.943 0.000239 3235.662 3235.662\n31.00000 0.084873 4464.476 0.007407 3230.117 100256.4\n60.00000 0.164271 4462.717 0.014291 3193.902 193421.5\n91.00000 0.249144 4460.813 0.021523 3127.557 291306.3\n121.0000 0.331280 4458.909 0.028362 3055.878 383879.7\n152.0000 0.416153 4456.914 0.035262 2982.212 477271.4\n……………………………………………….\nAnd activating the SUMMARY file DATE option with:\n--\n-- ACTIVATE DATE SUMMARY FILE OPTION\n--\nDATE\nResults in the following example RSM file output.\n-------------------------------------------------------------------------------\nSUMMARY OF RUN WITH-DATE-KEYWORD\n-------------------------------------------------------------------------------\nDATE YEARS DAY MONTH YEAR FPR FOEW FOPR\nYEARS PSIA STB/DAY\n-------------------------------------------------------------------------------\n1-JAN-98 0 19 10 1992 4467.125 0 0\n2-JAN-98 0.002738 20 10 1992 4466.943 0.000239 3235.662\n31-JAN-98 0.084873 21 10 1992 4464.476 0.007407 3230.117\n28-FEB-98 0.164271 24 10 1992 4462.717 0.014291 3193.902\n31-MAR-98 0.249144 28 10 1992 4460.813 0.021523 3127.557\n30-APR-98 0.331280 3 11 1992 4458.909 0.028362 3055.878\n31-MAY-98 0.416153 14 11 1992 4456.914 0.035262 2982.212\n……………………………………………….","size_kind":"none","size_count":0},"EXCEL":{"name":"EXCEL","sections":["SUMMARY"],"supported":false,"summary":"This keyword activates the writing out of the RSM file data in a format that can easily be loaded into Microsoft's EXCEL spreadsheet program or LibreOffice’s CALC spreadsheet program. The RSM file output is activated by the RUNSUM keyword in the SUMMARY section.","parameters":[],"example":"-- ==============================================================================\n--\n-- SUMMARY SECTION\n--\n-- ==============================================================================\nSUMMARY\n--\n-- ACTIVATE COLUMNAR SUMMARY DATA REPORTING OPTION\n--\nRUNSUM\n--\n-- ACTIVATE EXCEL SUMMARY FILE OPTION\n--\nEXCEL\nThe above example activates the SUMMARY file EXCEL option for directly loading the RSM file into either Microsoft's EXCEL or LibreOffice’s CALC spreadsheet programs.","size_kind":"none","size_count":0},"FMWSET":{"name":"FMWSET","sections":["SUMMARY"],"supported":false,"summary":"This keyword is similar to the ALL keyword in the SUMMARY section, in that it results in a group of summary variables to be written out to the SUMMARY file. In this case the keyword activates the writing out of a set of data vectors that give the production and injections status of all the wells in the model, as well as the number of wells in the drilling queue and the number of workover events occurring within a time step. Both instantaneous and cumulative well counts and events are written out as listed in Table 11.28.","parameters":[],"example":"-- ==============================================================================\n--\n-- SUMMARY SECTION\n--\n-- ==============================================================================\nSUMMARY\n--\n-- EXPORT WELL STATUS VECTORS FOR THE FIELD TO FILE\n--\nFMWSET\n--\n-- ACTIVATE COLUMNAR SUMMARY DATA REPORTING OPTION\n--\nRUNSUM\n--\n-- ACTIVATE SUMMARY DATA RSM FILE OUTPUT OPTION\n--\nSEPARATE\nThe above example exports the field standard well status variables to the SUMMARY file.\n| Field and Group Well Status Summary Variables | | | | |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-------|-------|---------|\n| Variable | Root | Field | Group | Comment |\n| Number of abandoned injection wells | MWIA | FMWIA | GMWIA | |\n| Number of abandoned production wells | MWPA | FMWPA | GMWPA | |\n| Number of drilling events in total | MWDT | FMWDT | GMWDT | |\n| Number of drilling events this time step | MWDR | FMWDR | GMWDR | |\n| Number of injection wells currently flowing | MWIN | FMWIN | GMWIN | |\n| Number of injectors on group control | MWIG | FMWIG | GMWIG | |\n| Number of injectors on own reservoir volume rate limit control ","size_kind":"none","size_count":0},"GMWSET":{"name":"GMWSET","sections":["SUMMARY"],"supported":false,"summary":"This keyword is similar to the ALL keyword in the SUMMARY section, in that it results in a group of summary variables to be written out to the SUMMARY file. In this case the keyword activates the writing out of a set of data vectors that give the production and injections status of all the wells in the named groups, as well as the number of wells in the drilling queue and the number of workover events occurring within a time step for the requested groups. Both instantaneous and cumulative well counts and events for the groups are written out as tabulated in Table 11.29.","parameters":[],"example":"The first example below exports all the group standard well status variables to the SUMMARY file.\n-- ==============================================================================\n--\n-- SUMMARY SECTION\n--\n-- ==============================================================================\nSUMMARY\n--\n-- EXPORT WELL STATUS VECTORS FOR NAMED GROUPS TO FILE\n--\nGMWSET\n/\n--\n-- ACTIVATE COLUMNAR SUMMARY DATA REPORTING OPTION\n--\nRUNSUM\n--\n-- ACTIVATE SUMMARY DATA RSM FILE OUTPUT OPTION\n--\nSEPARATE\nThe second example exports all the group standard well status variables for just the PLAT1 and PLT2 groups only to the SUMMARY file.\n--\n-- EXPORT WELL STATUS VECTORS FOR NAMED GROUPS TO FILE\n--\nGMWSET\n‘PLAT1’ ‘PLAT2’\n/\n--\n-- ACTIVATE COLUMNAR SUMMARY DATA REPORTING OPTION\n--\nRUNSUM\n--\n-- ACTIVATE SUMMARY DATA RSM FILE OUTPUT OPTION\n--\nSEPARATE\n| Field and Group Well Status Summary Variables | | | | |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-------|-------|---------|\n| Variable | Root | Field | Group | Comment |\n| Number of abandoned injection wells | MWIA | FMWIA | GMWIA | |\n| Number of abandoned production wells | MWPA | FMWPA | GMWPA | |\n| Number of drilling events in total | MWDT | FMWDT | GMWDT | |\n| Number of drilling events this timestep | MWDR | FMWDR | GMWDR | |\n| Number of injection wells currently flowing | MWIN | FMWIN | GMWIN | |\n| Number of injectors on group control ","size_kind":"none","size_count":0},"NARROW":{"name":"NARROW","sections":["SUMMARY"],"supported":false,"summary":"The NARROW keyword activates the Run Summary Narrow Column Output option, for when printed SUMMARY data has been requested by the RUNSUM keyword in the SUMMARY section. The option increases the number of columns “printed on the page”.","parameters":[],"example":"","size_kind":"none","size_count":0},"NEWTON":{"name":"NEWTON","sections":["SUMMARY"],"supported":null,"summary":"This keyword activates the writing out of the Newton iteration vector (the number of non-linear iterations per time step) to the SUMMARY file, and the RSM file if the RSM file option has been requested by the RUNSUM keyword in the SUMMARY section,","parameters":[],"example":"-- ==============================================================================\n--\n-- SUMMARY SECTION\n--\n-- ==============================================================================\nSUMMARY\n--\n-- ACTIVATE COLUMNAR SUMMARY DATA REPORTING OPTION\n--\nRUNSUM\n--\n-- ACTIVATE SUMMARY DATA RSM FILE OUTPUT OPTION\n--\nSEPARATE --\n-- ACTIVATE NEWTON ITERATION SUMMARY OUTPUT\n--\nNEWTON\nThe above example actives the writing out of the Newton iteration vector to the SUMMARY file."},"NMESSAGE":{"name":"NMESSAGE","sections":["SUMMARY"],"supported":true,"summary":"This keyword activates the writing out of a standard set of summary OPM Flow simulation performance summary variables to the SUMMARY (*.SMSPEC and *.UNSMRY) and RSM (*.RSM) files, namely the number of messages written per message class. Table 11.30lists the summary variables written out by the NMESSAGE keyword.","parameters":[],"example":"-- ==============================================================================\n--\n-- SUMMARY SECTION\n--\n-- ==============================================================================\nSUMMARY\n--\n-- EXPORT PERFORMANCE CUMULATIVE MESSAGE VARIABLE VECTORS TO FILE\n--\nNMESSAGE\n--\n-- ACTIVATE COLUMNAR SUMMARY DATA REPORTING OPTION\n--\nRUNSUM\n--\n-- ACTIVATE SUMMARY DATA RSM FILE OUTPUT OPTION\n--\nSEPARATE\nNote the SEPARATE keyword is not required for OPM Flow as this is the default behavior; however, it is probably good practice to include it if the same input decks are being run with the commercial simulator.\n| OPM Flow Simulator Performance Summary Variables Cumulative Message Variables | | |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|--------------|\n| Variable Description | Variable | Comment |\n| Messages - Cumulative number of BUG messages. | MSUMBUG | Unsupported. |\n| Messages - Cumulative number of COMMENT messages. | MSUMCOMM | Unsupported. |\n| Messages - Cumulative number of ERROR messages. | MSUMERR | Unsupported. |\n| Messages - Cumulative number of MESSAGES messages. ","size_kind":"none","size_count":0},"OFM":{"name":"OFM","sections":["SUMMARY"],"supported":false,"summary":"This keyword activates the writing out of the SUMMARY file data in the Oil Field Manager (“OFM”) file format to enable the simulated data to be directly loaded into Oil Field Manager.","parameters":[],"example":"","size_kind":"none","size_count":0},"PERFORMA":{"name":"PERFORMA","sections":["SUMMARY"],"supported":null,"summary":"The PERFORMA keyword activates the writing out of a standard set of OPM Flow simulation numerical performance summary variables to the SUMMARY (*.SMSPEC and .*UNSMRY) and RSM (*.RSM) files. Table 11.31lists the summary variables written out by the keyword.","parameters":[],"example":"-- ==============================================================================\n--\n-- SUMMARY SECTION\n--\n-- ==============================================================================\nSUMMARY\n--\n-- EXPORT NUMERICAL PERFORMANCE SUMMARY VARIABLES TO FILE\n--\nPERFORMA\n--\n-- ACTIVATE COLUMNAR SUMMARY DATA REPORTING OPTION\n--\nRUNSUM\n--\n-- ACTIVATE SUMMARY DATA RSM FILE OUTPUT OPTION\n--\nSEPARATE\nNote the SEPARATE keyword is not required for OPM Flow as this is the default behavior; however, it is probably good practice to include it if the same input decks are being run with commercial simulator.\n| OPM Flow Simulator Performance Summary Variables Numerical Performance Variables | | |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Variable Description | Variable | Comment |\n| Elapsed - Elapsed time in seconds. | ELAPSED | No data written to file. |\n| Iterations - Number linear iterations for each time step. | MLINEARS | |\n| Iterat"},"RPTONLY":{"name":"RPTONLY","sections":["SUMMARY","SCHEDULE"],"supported":null,"summary":"This keyword activates the writing out of the SUMMARY file and the RSM file data, if the RSM file option has been requested by the RUNSUM keyword in the SUMMARY section, at report time steps only. The default is for the data to be written out for all time steps to the SUMMARY files. This keyword reduces the file size at the expense of lower resolution in the time domain.","parameters":[],"example":"-- ==============================================================================\n--\n-- SUMMARY SECTION\n--\n-- ==============================================================================\nSUMMARY\n--\n-- EXPORT STANDARD SUMMARY VARIABLE VECTORS TO FILE\n--\nALL\n--\n-- ACTIVATE COLUMNAR SUMMARY DATA REPORTING OPTION\n--\nRUNSUM\n--\n-- ACTIVATE SUMMARY DATA RSM FILE OUTPUT OPTION\n--\nSEPARATE\n--\n-- ACTIVATE REPORT TIME STEPS ONLY SUMMARY FILE OPTION\n--\nRPTONLY\nThe above example activates the writing out of the SUMMARY file at report time steps only.","size_kind":"none","size_count":0},"RPTONLYO":{"name":"RPTONLYO","sections":["SUMMARY","SCHEDULE"],"supported":null,"summary":"This keyword deactivates the writing out of the SUMMARY file and the RSM file data, if the RSM file option has been requested by the RUNSUM keyword in the SUMMARY section, at report time steps only, and switches on writing out all the time steps to the files. This option is the default behavior for when RPTONLY has not been activated.","parameters":[],"example":"-- ==============================================================================\n--\n-- SUMMARY SECTION\n--\n-- ==============================================================================\nSUMMARY\n--\n-- EXPORT STANDARD SUMMARY VARIABLE VECTORS TO FILE\n--\nALL\n--\n-- ACTIVATE COLUMNAR SUMMARY DATA REPORTING OPTION\n--\nRUNSUM\n--\n-- ACTIVATE SUMMARY DATA RSM FILE OUTPUT OPTION\n--\nSEPARATE\n--\n-- DEACTIVATE REPORT TIME STEPS ONLY SUMMARY FILE OPTION\n--\nRPTONLYO\nThe above example deactivates the writing out of the SUMMARY file at report time steps only, and switches on writing out all the time steps to the file.","size_kind":"none","size_count":0},"RPTSMRY":{"name":"RPTSMRY","sections":["SUMMARY"],"supported":false,"summary":"This keyword activates or deactivates a listing of all the summary variables that are going to be written to the SUMMARY file and the RSM file, if the RSM file option has been requested by the RUNSUM keyword in the SUMMARY section.","parameters":[{"index":1,"name":"RPTSMRY","description":"An integer value set to zero for no report, or one to produce the report.","units":{},"default":"0","value_type":"INT"}],"example":"-- ==============================================================================\n--\n-- SUMMARY SECTION\n--\n-- ==============================================================================\nSUMMARY\n--\n-- EXPORT STANDARD SUMMARY VARIABLE VECTORS TO FILE\n--\nALL\n--\n-- ACTIVATE COLUMNAR SUMMARY DATA REPORTING OPTION\n--\nRUNSUM\n--\n-- ACTIVATE SUMMARY DATA RSM FILE OUTPUT OPTION\n--\nSEPARATE\n--\n-- ACTIVATE OR DEACTIVATE SUMMARY LIST REPORT\n--\nRPTSMRY\n1 /\nThe example switches on the summary list report.","expected_columns":1,"size_kind":"fixed","size_count":1},"RUNSUM":{"name":"RUNSUM","sections":["SUMMARY"],"supported":null,"summary":"This keyword activates the writing out of the SUMMARY file data in a columnar format to the PRT file. Normally the SEPARATE keyword in the SUMMARY section is invoked in the same run to direct the data stream to a separate RSM file for easy loading into other programs, for example, Microsoft's EXCEL or LibreOffice’s CALC spreadsheet programs.","parameters":[],"example":"-- ==============================================================================\n--\n-- SUMMARY SECTION\n--\n-- ==============================================================================\nSUMMARY\n--\n-- ACTIVATE COLUMNAR SUMMARY DATA REPORTING OPTION\n--\nRUNSUM\n--\n-- ACTIVATE SUMMARY DATA RSM FILE OUTPUT OPTION\n--\nSEPARATE\nNote unlike the commercial simulator, OPM Flow always writes out the data to a separate file.","size_kind":"none","size_count":0},"SEPARATE":{"name":"SEPARATE","sections":["SUMMARY"],"supported":null,"summary":"This keyword activates the writing out of the SUMMARY file date in a columnar format to the RSM file, if the RUNSUM keyword has also been activated in the SUMMARY section. Both the SEPARATE and the RUNSUM keywords need to be invoked. If the SEPARATE option is not activated then the RSM output is directed to the end of the PRT file. Normally the both the SEPARATE and RUNSUM keywords are invoked in the same run to enable easy loading of the data into Microsoft's EXCEL or LibreOffice’s CALC spreadsheet programs.","parameters":[],"example":"-- ==============================================================================\n--\n-- SUMMARY SECTION\n--\n-- ==============================================================================\nSUMMARY\n--\n-- ACTIVATE COLUMNAR SUMMARY DATA REPORTING OPTION\n--\nRUNSUM\n--\n-- ACTIVATE SUMMARY DATA RSM FILE OUTPUT OPTION\n--\nSEPARATE\nNote unlike the commercial simulator, OPM Flow always writes out the data to a separate file; however, it is probably good practice to include it if the same input decks are being run with commercial simulator.","size_kind":"none","size_count":0},"SUMMARY":{"name":"SUMMARY","sections":["SUMMARY"],"supported":null,"summary":"The SUMMARY activation keyword marks the end of the SOLUTION section and the start of the SUMMARY section that defines the variables to be written out to the SUMMARY file for reporting and plotting of grid block data, production data, etc.","parameters":[],"example":"-- ==============================================================================\n--\n-- SUMMARY SECTION\n--\n-- ==============================================================================\nSUMMARY\nThe above example marks the end of the SOLUTION section and the start of the SUMMARY section in the OPM Flow data input file.","size_kind":"none","size_count":0},"SUMTHIN":{"name":"SUMTHIN","sections":["SUMMARY","SCHEDULE"],"supported":null,"summary":"This keyword defines a time interval for writing out the SUMMARY data to the SUMMARY file and the RSM file, if the RUNSUM keyword has also been activated in the SUMMARY section. Only the data for the first time step in the time interval is written out and the other time steps are skipped until the next time interval, except for report time steps. Note that report time steps data are always written out regardless of the setting on this keyword. This enables the size of the SUMMARY files to be reduced depending on the size of the time interval. However, the keyword will produce irregular time steps reports of the SUMMARY data.","parameters":[{"index":1,"name":"SUMSTEP","description":"SUMSTEP is a real positive number that defines the time interval for which the first time step of data will be written to the SUMMARY file (and the RSM file if RSM output has been activated). For example, if SUMSTEP is set to 30 days, and if the simulator takes time steps of 0, 5, 10, 16, 24, 30, 40, 45, 60, 90 days. Then the SUMMARY data will be written out at time steps 0, 30, 40 and 60 days.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"None","value_type":"DOUBLE","dimension":"Time"}],"example":"--\n-- DEFINE SUMMARY DATA REPORTING TIME STEP INTERVAL\n--\n-- SUMSTEP\nSUMTHIN\n30.0 / /\nThe above example defines the SUMMARY file time step interval to be 30 days for both field and metric units.","expected_columns":1,"size_kind":"fixed","size_count":1},"ACTION":{"name":"ACTION","sections":["SCHEDULE"],"supported":false,"summary":"The ACTION keyword defines a series of conditions that invoke run time processing of ACTION functions and is similar to executing a run time script for conditions and variables at the field level.","parameters":[{"index":1,"name":"ACTION_NAME","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"QUANTITY","description":"","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"OPERATOR","description":"","units":{},"default":"","value_type":"STRING"},{"index":4,"name":"TRIGGER_VALUE","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","expected_columns":4,"size_kind":"fixed","size_count":1},"ACTIONG":{"name":"ACTIONG","sections":["SCHEDULE"],"supported":false,"summary":"The ACTIONG keyword defines a series of conditions that invoke run time processing of ACTION functions and is similar to executing a run time script for conditions and variables at the group level","parameters":[{"index":1,"name":"ACTION","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"GROUP_NAME","description":"","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"QUANTITY","description":"","units":{},"default":"","value_type":"STRING"},{"index":4,"name":"OPERATOR","description":"","units":{},"default":"","value_type":"STRING"},{"index":5,"name":"TRIGGER_VALUE","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":6,"name":"REPETITIONS","description":"","units":{},"default":"1","value_type":"INT"},{"index":7,"name":"INCREMENT","description":"","units":{},"default":"0","value_type":"DOUBLE"}],"example":"","expected_columns":7,"size_kind":"fixed","size_count":1},"ACTIONR":{"name":"ACTIONR","sections":["SCHEDULE"],"supported":false,"summary":"The ACTIONR keyword defines a series of conditions that invoke run time processing of ACTION functions and is similar to executing a run time script for conditions and variables at the region level.","parameters":[{"index":1,"name":"ACTION","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"FLUID_IN_PLACE_NR","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"FLUID_IN_PLACE_REG_FAM","description":"","units":{},"default":"","value_type":"STRING"},{"index":4,"name":"QUANTITY","description":"","units":{},"default":"","value_type":"STRING"},{"index":5,"name":"OPERATOR","description":"","units":{},"default":"","value_type":"STRING"},{"index":6,"name":"TRIGGER_VALUE","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":7,"name":"REPETITIONS","description":"","units":{},"default":"1","value_type":"INT"},{"index":8,"name":"INCREMENT","description":"","units":{},"default":"0","value_type":"DOUBLE"}],"example":"","expected_columns":8,"size_kind":"fixed","size_count":1},"ACTIONS":{"name":"ACTIONS","sections":["SCHEDULE"],"supported":false,"summary":"The ACTIONS keyword defines a series of conditions that invoke run time processing of ACTION functions and is similar to executing a run time script for conditions and variables associated with well segments.","parameters":[{"index":1,"name":"ACTION","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"WELL_SEGMENT","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"QUANTITY","description":"","units":{},"default":"","value_type":"STRING"},{"index":5,"name":"OPERATOR","description":"","units":{},"default":"","value_type":"STRING"},{"index":6,"name":"TRIGGER_VALUE","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":7,"name":"REPETITIONS","description":"","units":{},"default":"1","value_type":"INT"},{"index":8,"name":"INCREMENT","description":"","units":{},"default":"0","value_type":"DOUBLE"}],"example":"","expected_columns":8,"size_kind":"fixed","size_count":1},"ACTIONW":{"name":"ACTIONW","sections":["SCHEDULE"],"supported":false,"summary":"This keyword starts the definition of an ACTIONW section that stipulates the Boolean conditions to test the nominated well parameters, and the resulting SCHEDULE keywords to be executed, if the Boolean condition evaluates to true. An ACTIONW Definition Section is terminated by an ENDACTIO keyword on a separate line. Here, the keyword defines a series of conditions applied to wells only, that invoke run time processing of ACTION functions, and is similar to executing a run time script for conditions and variables at the well level. The ACTION series of keywords (ACTION, ACTIONG, ACTIONR, ACTIONS and ACTIONW) can apply Boolean conditional tests to variables at the field, group, region, well segment and well levels.","parameters":[{"index":1,"name":"Bottom-Hole Pressure","description":"WBHP","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"Gas Injection Rate","description":"WGIR","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"Gas Injection Total","description":"WGIT","units":{},"default":"","value_type":"STRING"},{"index":4,"name":"Gas-Liquid Ratio","description":"WGLR","units":{},"default":"","value_type":"STRING"},{"index":5,"name":"Gas-Liquid Ratio (Bottom Hole)","description":"WBGLR","units":{},"default":"","value_type":"DOUBLE"},{"index":6,"name":"Gas-Oil Ratio","description":"WGOR","units":{},"default":"","value_type":"INT"},{"index":7,"name":"Gas Production Rate","description":"WGPR","units":{},"default":"","value_type":"DOUBLE"},{"index":8,"name":"Gas Production Total","description":"WGPT","units":{},"default":""},{"index":9,"name":"Liquid Production Rate","description":"WLPR","units":{},"default":""},{"index":10,"name":"Liquid Production Rate","description":"WLPT","units":{},"default":""},{"index":11,"name":"Oil Injection Rate","description":"WOIR","units":{},"default":""},{"index":12,"name":"Oil Injection Total","description":"WOIT","units":{},"default":""},{"index":13,"name":"Oil Production Rate","description":"WOPR","units":{},"default":""},{"index":14,"name":"Oil Production Total","description":"WOPT","units":{},"default":""},{"index":15,"name":"Polymer Production Concentration","description":"WCPC","units":{},"default":""},{"index":16,"name":"Polymer Production Rate","description":"WCPR","units":{},"default":""},{"index":17,"name":"Salt Production Concentration","description":"WSPC","units":{},"default":""},{"index":18,"name":"Salt Production Rate","description":"WSPR","units":{},"default":""},{"index":19,"name":"Tracer Production Concentration (Tracer name should be added to WTPC)","description":"WTPC","units":{},"default":""},{"index":20,"name":"Tracer Production Rate (Tracer name should be added to WTPC)","description":"WTPR","units":{},"default":""},{"index":21,"name":"Tubing Head Pressure","description":"WTHP","units":{},"default":""},{"index":22,"name":"Voidage Injection Rate","description":"WVIR","units":{},"default":""},{"index":23,"name":"Voidage Injection Total","description":"WVIT","units":{},"default":""},{"index":24,"name":"Voidage Production Rate","description":"WVPR","units":{},"default":""},{"index":25,"name":"Voidage Production Total","description":"WVPT","units":{},"default":""},{"index":26,"name":"Water Cut","description":"WWCT","units":{},"default":""},{"index":27,"name":"Water Injection Rate","description":"WWIR","units":{},"default":""},{"index":28,"name":"Water Injection Total","description":"WWIT","units":{},"default":""},{"index":29,"name":"Water Production Rate","description":"WWPR","units":{},"default":""},{"index":30,"name":"Water Production Total","description":"WWPT","units":{},"default":""},{"index":31,"name":"Water-Gas Ratio","description":"WWGR","units":{},"default":""},{"index":32,"name":"User Defined Quantity","description":"WUXXXXXX","units":{},"default":""}],"example":"The first example uses the ACTIONW keyword to re-complete a gas injection well, GI01, when the well’s bottom-hole pressure exceeds the fracture pressure of the formation, and to open up a structurally higher zone in the well. The keyword NEXTSTEP is used to set the next step to 0.1 days to avoid convergence issues due to a well event.\n--\n-- ACTIONW WELL COMMANDS\n--\nACTIONW\n-- ACTION WELL ACTION ACTION ACTION MAX INCREMENT\n-- NAME NAME LHS TEST RHS ACTIONS RHS\nACTW-1 GI01 WBHP > 6800.0 /\n--\n-- ACTION COMMANDS TO BE EXECUTED\n--\n-- NEXT ALL\n-- STEP TIME\nNEXTSTEP\n0.1 'NO' /\n--\n-- WELL PRODUCTION STATUS\n--\n-- WELL WELL --LOCATION-- COMPLETION\n-- NAME STAT I J K FIRST LAST\nWELOPEN\nGI01 SHUT /\nGI01 SHUT 0 0 0 2 2 /\nGI01 OPEN /\nGI01 OPEN 0 0 0 1 1 /\n/\nENDACTIO\nThe second example shows how to reduce a producing well's deliverability due to water production. Here, well OP01’s productivity index is reduced by 2% when the well’s liquid production total is greater than 100,000 stb. The reduction is repeated 300 times and each time the action is executed the ACTRHS constant is increased by 10,000 stb.\n--\n-- ACTIONW WELL COMMANDS\n--\nACTIONW\n-- ACTION WELL ACTION ACTION ACTION MAX ICREMENT\n-- NAME NAME LHS TEST RHS ACTIONS RHS\nACTW-01 OP01 WLPT > 100E3 300 10E3 /\n--\n-- DEFINE WELL CONNECTION MULTIPLIERS\n--\n-- WELL PI --LOCATION-- COMPLETION\n-- NAME MULT I J K FIRST LAST\nWPIMULT\nOP01 0.980 1* 1* 1* 1* 1* /\n/\nENDACTIO\nThe final example is similar to the previous example, and shows how to nest ACTIONW blocks and how to apply ACTIONW to all the oil producers when the Boolean condition are satisfied.\n--\n-- ACTIONW WELL COMMANDS\n--\nACTIONW\n-- ACTION WELL ACTION ACTION ACTION MAX ICREMENT\n-- NAME NAME LHS TEST RHS ACTIONS RHS\nACTW-01A 'OP*' WLPT > 100E3 300 10E3 /\n--\n-- ACTIONW WELL COMMANDS\n--\nACTIONW\n-- ACTION WELL ACTION ACTION ACTION MAX ICREMENT\n-- NAME NAME LHS TEST RHS ACTIONS RHS\nACTW-01B 'OP*' WPI > 5.0 1 0.0 /\n--\n-- DEFINE WELL CONNECTION MULTIPLIERS\n--\n-- WELL PI --LOCATION-- COMPLETION\n-- NAME MULT I J K FIRST LAST\nWPIMULT\n'?' 0.980 1* 1* 1* 1* 1* /\n/\nENDACTIO\nENDACTIO\nIn this case the outer ACTIONW checks if the liquid production for each OP* well is great than the calculated ACTRHS constant, if it is, then inner ACTIONW reduces all the selected wells’ productivity indices by 2%, provided the well’s productivity index is greater than five.\n| Note Within an ACTIONW Definition Section any UDQ variables utilizing well variables, must have their associated wells previously fully defined in the commercial simulator, otherwise an error will occur. For example, if a well’s GOR is being used as part of a UDQ definition, then the well must be fully characterized prior to declaring the UDQ definition. This restriction does not apply to OPM Flow; however, it should be considered if the same deck is to be run with both simulators. |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":7,"size_kind":"fixed","size_count":1},"ACTIONX":{"name":"ACTIONX","sections":["SCHEDULE"],"supported":true,"summary":"The ACTIONX keyword defines a series of conditions that invoke run time processing of ACTION functions and is similar to executing a run time script. This is the general purpose version of the ACTION series of keywords that can apply Boolean conditional tests to variables at the field, group, region, well segment and well levels. The ACTION, ACTIONG, ACTIONR, ACTIONS and ACTIONW keywords are not implemented in OPM Flow and are unlikely to be so, as the ACTIONX keyword implements their functionality with greater flexibility.","parameters":[{"index":1,"name":"ACTNAME","description":"ACTNAME is a character sting of up to eight characters in length, that defines the name of this action definition. If ACTNAME has previously been used by any ACTION series keyword, then the previous ACTION series definition will be replaced by the definition declared by this ACTIONX Definition Section.","units":{},"default":"","record":1,"value_type":"STRING"},{"index":2,"name":"ACTNSTEP","description":"ACTNSTEP is a positive integer that defines the number times that the ACTNAME definition is executed. ACTIONX definitions are activated at the end of a time step and this parameter is used to set how many time steps the ACTNAME definition will be invoked. The default value of one means that the definition will be executed only once. Use a large value, for example 10,000 for the definition to be executed at every time step. Note that the counter only affects successful evaluations; i.e. if ACTNSTEP is set equal to one (the default), then the simulator will test the action at the end of every time step until it evaluates to true.","units":{},"default":"1","record":1,"value_type":"INT"},{"index":3,"name":"ACTDELTA","description":"ACTDELTA is a real positive value that defines the minimum duration of time after the conditions defined on the second record have been satisfied before the ACTIONX actions are executed. For example, if ACTDELTA is defaulted the actions will be executed at the end of the time step for which the conditions are met. If set to say 30, then a minimum of 30 days will pass before the actions are executed (assuming field or metric units).","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"0.0","record":1,"value_type":"DOUBLE","dimension":"Time"},{"index":1,"name":"ACTLHS","description":"ACTLHS is a series of character strings, each up to eight characters in length, that defines a constant, UDQ defined value, or a SUMMARY variable on the left hand side of a Boolean conditional test. The format for ACTLHS is dependent on the SUMMARY variable type: Aquifer, Block, Field, Group, Region, Time, Well, Well Connection, Well Local Grid Refinement Connection, or a Well Segment. In addition to SUMMARY variables, an UDQ defined value or a Constant variable can be used. The format for the various data types is given in Table 12.7.","units":{},"default":"Not Applicable","record":2,"value_type":"RAW_STRING"},{"index":2,"name":"ACTTEST","description":"ACTTEST is a defined character string that states the Boolean operator and must be set to one of the following Boolean conditionals: >: Greater than. <: Less than. >=: Greater than or equal to. <=: Less than or equal to. =: Equal to. !=: Not equal to. For example to test if the field’s gas production rate is less than 600 MMscf/d then one would use: ACTIONX PHASE2 1 / GGPR 'FIELD' < 600E3 / / ... ENDACTIO","units":{},"default":"Not Applicable","record":2},{"index":3,"name":"ACTRHS","description":"ACTRHS is a numeric value or a series of character strings, each up to eight characters in length, that defines a constant, an UDQ defined value, or a SUMMARY variable on the right hand side of a Boolean conditional test, as outlined in Table 12.7(see also ACTLHS). In the case of well quantities the set of matching wells is captured and can be used as a general \"well list\" with the symbol '?' in subsequent well keywords. For example, to shut-in all oil producing wells (‘OP*’) with a water cut greater than 90% for every time the field water production rate exceeds 60,000 stb/d one would use: ACTIONX MXWATER 10000 / GWPR 'FIELD' > 60E3 AND / WWCT 'OP*' > 0.90 / / -- WELL PRODUCTION STATUS -- -- WELL WELL --LOCATION-- COMPLETION -- NAME STAT I J K FIRST LAST WELOPEN '?' SHUT / / ENDACTIO","units":{},"default":"Not Applicable","record":2},{"index":4,"name":"ANDOR","description":"An optional defined character string that specifies a Boolean operator that must be set to either AND or OR if included on this record, that links this record with additional records of this type. For example, to test if the field’s gas production rate is less than 600 MMscf/d after 2020 then one would use: ACTIONX PHASE2 1 / GGPR 'FIELD' < 600E3 AND / YEAR > 2020 / / ... ENDACTIO This item should be left blank if not required.","units":{},"default":"Not Applicable","record":2}],"example":"The first example uses the UDQ keyword to sort the oil wells from high water cut to low, via the WU_WLIST variable, and then use the ACTIONX keyword to shut-in the worst offending well when the field’s water production is greater than 30,000 stb/d.\n--\n-- DEFINE START OF USER DEFINED QUANTITY SECTION\n--\nUDQ\n--\n-- OPERATOR VARIABLE EXPRESSION\n--\nDEFINE WU_WCUT WWCT 'OP*' / WELL WWCT LIST\nDEFINE WU_LIST SORTD(WU_WCUT) / WELL WWCT LIST SORTED\n/ END OF UDQ SECTION\n--\n-- DEFINE START OF ACTIONX SECTION\n--\nACTIONX\nWSHUTIN 10 /\nGWPR 'FIELD' > 30E3 AND /\nWU_LIST 'OP*' = 1 /\n/\n--\n-- DEFINE WELL AND WELL CONNECTIONS FLOWING STATUS\n--\n-- WELL WELL --LOCATION-- COMPLETION\n-- NAME STAT I J K FIRST LAST\nWELOPEN\n'?' SHUT /\n'?' SHUT 0 0 0 0 0 /\n/\nENDACTIO\nApart from checking that the field’s water production rate is greater than 30,000 stb/d the Boolean conditional also checks that there is at least one well in the sorted well list. Notice also the use of ‘?’ symbol as a substitution of the well name and that the ACTIONX WSHUTIN series of commands will be executed a total of ten times.\nThe second example checks to see if the field’s gas rate is below 600 MMscf/d and if the simulation time is greater that July 1, 2030. If it is, then compression is installed by re-setting all the gas producing well’s THP and BHP pressures to 450 psia and 300 psia respectively. In addition all gas wells currently shut-in are tested to see if they can be opened up under the new THP and BHP constraints.\n--\n-- START ACTIONX FIELD PHASE-3 AUTOMATIC COMPRESSION\n--\nACTIONX\nPHASE-3 1 /\nGGPR 'FIELD' < 600E3 AND /\nDAY >= 1 AND /\nMNTH >= JUL AND /\nYEAR >= 2030 /\n/\n--\n-- INSTALL COMPRESSION AND RESET WELL THP AND BHPS\n--\n-- WELL WELL TARGET\n-- NAME TARG VALUE\nWELTARG\n'GP*' THP 450 /\n'GP*' BHP 300 /\n/\n--\n-- TEST AND OPEN ALL WELLS UNDER COMPRESSION CONSTRAINTS\n--\n-- WELL TEST CLOSE NO. START\n-- NAME INTV CHECK CHECK TIME\nWTEST\n'GP*' 1.0 PE 1 3 /\n/\n--\n-- END OF ACTIONX FIELD PHASE-3 AUTOMATIC COMPRESSION DEFINITION\n--\nENDACTIO\n| Variable Type | Description |\n|---------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------","records_meta":[{"expected_columns":3},{}],"size_kind":"list"},"APILIM":{"name":"APILIM","sections":["SCHEDULE"],"supported":false,"summary":"The APILIM keyword defines API Tracking grid block limits for when API Tracking has been activated via the API keyword in the RUNSPEC section. The keyword enables the simulator to monitor the grid blocks outside the limits defined on the keyword, as well as to optionally contrain the values within a given range.","parameters":[{"index":1,"name":"LIMITER","description":"","units":{},"default":"NONE","value_type":"STRING"},{"index":2,"name":"SCOPE","description":"","units":{},"default":"BOTH","value_type":"STRING"},{"index":3,"name":"LOWER_API_LIMIT","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":4,"name":"UPPER_API_LIMIT","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":5,"name":"NUM_ROWS","description":"","units":{},"default":"10","value_type":"INT"}],"example":"","expected_columns":5,"size_kind":"fixed","size_count":1},"AQUCWFAC":{"name":"AQUCWFAC","sections":["SCHEDULE"],"supported":false,"summary":"The AQUCWFAC keyword modifies the datum depth and pressure for all aquifers specified by the AQUCHWAT keyword in the SOLUTION or SCHEDULE sections.","parameters":[{"index":1,"name":"ADD_TO_DEPTH","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Length"},{"index":2,"name":"MULTIPLY","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"}],"example":"","expected_columns":2,"size_kind":"list"},"BCPROP":{"name":"BCPROP","sections":["SCHEDULE"],"supported":true,"summary":"The BCPROP keyword defines the type and properties of the boundary conditions.","parameters":[{"index":1,"name":"INDEX","description":"A positive integer that identifies the boundary condition.","units":{},"default":"None","value_type":"INT"},{"index":2,"name":"TYPE","description":"A defined character string that defines the type of boundary condition to be applied, and should be set to one of the following character strings: DIRICHLET: for user defined boundary conditions. In this case, COMPONENT for the fluid type, and PRESS and TEMP for the constant pressure and temperature boundary conditions must be specified. FREE: for the initial state of the boundary to be kept throughout the simulation, that is a constant boundary condition. The remaining items should be defaulted. RATE: for the boundary to have a constant influx or efflux rate. In this case, COMPONENT for the fluid type, and RATE to set the mass rate per unit area must be specified. THERMAL: Constant temperature boundary condition (no-flow of mass). NONE: No flow boundary condition.","units":{},"default":"None","value_type":"STRING","options":["DIRICHLET","FREE","RATE"]},{"index":3,"name":"COMPONENT","description":"A defined character string that sets fluid type used in the boundary calculations, and should be set to one of the following character strings: GAS: the gas phase will be used to control the boundary conditions for when the TYPE has been set to DIRICHLET or RATE. OIL: the oil phase will be used to control the boundary conditions for when the TYPE has been set to DIRICHLET or RATE . WATER or WAT: the water phase will be used to control the boundary conditions for when the TYPE has been set to DIRICHLET or RATE. SOLVENT: the solvent component will be used to control the boundary conditions for when the TYPE has been set to RATE. POLYMER: the polymer component will be used to control the boundary conditions for when the TYPE has been set to RATE. MICR: the microbial component will be used to control the boundary conditions for when the TYPE has been set to RATE. OXYG: the oxygen component will be used to control the boundary conditions for when the TYPE has been set to RATE. UREA: the urea component will be used to control the boundary conditions for when the TYPE has been set to RATE. NONE: the fluid type is undefined. COMPONENT must be declared and not equal to NONE if TYPE has been set to either DIRICHLET or RATE. MICR requires the BIOFILM or MICP keyword, and OXYG or UREA requires the MICP keyword.","units":{},"default":"NONE","value_type":"STRING","options":["GAS","OIL","WAT","SOLVENT","POLYMER","MICR","OXYG","UREA","NONE"]},{"index":4,"name":"RATE","description":"A real value that defines the constant mass rate per unit area of the specified COMPONENT to be injected or withdrawn at the boundary, when TYPE has been set to RATE. Note a negative value implies an influx rate, whereas, a positive value indicates an efflux.","units":{"field":"lb/day/ft2","metric":"kg/day/m2","laboratory":"gm/hour/cm2"},"default":"0.0","value_type":"DOUBLE","dimension":"Mass/Time*Length*Length"},{"index":5,"name":"PRESS","description":"PRESS is a real positive value that defines the constant pressure boundary condition. PRESS should only be entered if TYPE has been set to DIRICHLET. If the pressure at the boundary is less than PRESS, then the fluid type declared via COMPONENT will flow across the boundary. The default value of 1* will use the simulator's calculated value based on data entered via the EQUIL keyword in the SOLUTION section.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1*","value_type":"DOUBLE","dimension":"Pressure"},{"index":6,"name":"TEMP","description":"TEMP is a real positive number that defines the constant temperature boundary condition. TEMP should only be entered if TYPE has been set to DIRICHLET or THERMAL. The default value of 1* will use the simulator's calculated value based on data entered via one of the following reservoir temperature keywords: RTEMP, RTEMPA, RTEMPVD, TEMPI, or TEMPVD, in the SOLUTION section. Note that all of the aforementioned reservoir temperature keywords, except for TEMPI, may also be used in the PROPS section as well.","units":{"field":"oF","metric":"oC","laboratory":"oC"},"default":"1*","value_type":"DOUBLE","dimension":"Temperature"},{"index":7,"name":"MECHTYPE","description":"A defined character string that defines the type of geo-mechanical boundary condition to be applied, and should be set to one of the following character strings: FREE: Surface is free to move with no external stress. FIXED: Surface is fixed in the x/y/z-directions if FIXEDX / FIXEDY / FIXEDZ > 0. The displacement in each direction defined by DISPX / DISPY / DISPZ. The external stess is defined by STRESSXX / STRESSYY / STRESSZZ. NONE: No geo-mechanical boundary condition.","units":{},"default":"NONE","value_type":"STRING"},{"index":8,"name":"FIXEDX","description":"A positive integer that identifies the whether the boundary is free or fixed in the x-direction. A value of 0 implies the boundary is free to move in the x-direction. A value > 0 implies the boundary is fixed in the x-direction with displacement defined by DISPX,","units":{},"default":"1","value_type":"INT"},{"index":9,"name":"FIXEDY","description":"A positive integer that identifies the whether the boundary is free or fixed in the y-direction. A value of 0 implies the boundary is free to move in the y-direction. A value > 0 implies the boundary is fixed in the y-direction with displacement defined by DISPY,","units":{},"default":"1","value_type":"INT"},{"index":10,"name":"FIXEDZ","description":"A positive integer that identifies the whether the boundary is free or fixed in the z-direction. A value of 0 implies the boundary is free to move in the z-direction. A value > 0 implies the boundary is fixed in the z-direction with displacement defined by DISPZ,","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1","value_type":"INT"},{"index":11,"name":"STRESSXX","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Pressure"},{"index":12,"name":"STRESSYY","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Pressure"},{"index":13,"name":"STRESSZZ","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Pressure"},{"index":14,"name":"DISPX","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Length"},{"index":15,"name":"DISPY","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Length"},{"index":16,"name":"DISPZ","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Length"}],"example":"The first example shows how to set a constant pressure boundary using TYPE equal to FREE:\n--\n-- DEFINE BOUNDARY CONDITIONS CONNECTION (OPM FLOW GRID KEYWORD)\n--\n--INDEX ---------- BOX --------- BC\n-- I1 I2 J1 J2 K1 K2 DIRC\nBCCON\n1 1 1 1 1* 1 1* X- /\n2 1 1* 1 1 1 1* Y /\n/\n--\n-- DEFINE BOUNDARY CONDITIONS PROPERTIES (OPM FLOW SCHEDULE KEYWORD)\n--\n--INDEX BC BC BC BC BC\n-- TYPE COMPT RATE PRESS TEMP\nBCPROP\n1 FREE 1* 1* 1* 1* /\n2 FREE /\n/\nWith this option it is only necessary to define the boundary cells and all the other parameters (COMPONENT, RATE, PRESS, and TEMP) can be defaulted, as they are ignored when TYPE equals FREE.\nThe next example is based on NX, NY and NZ equal to 20, 1, 10 respectively, on the DIMENS keyword in the RUNSPEC section, and shows how different boundary types can be assigned to different parts of the model.\n--\n-- DEFINE BOUNDARY CONDITIONS CONNECTION (OPM FLOW GRID KEYWORD)\n--\n--INDEX ---------- BOX --------- BC\n-- I1 I2 J1 J2 K1 K2 DIRC\nBCCON\n1 1 1 1 1 1 10 X- /\n2 20 20 1 1 1 10 X /\n/\n--\n-- DEFINE BOUNDARY CONDITIONS PROPERTIES (OPM FLOW SCHEDULE KEYWORD)\n--\n--INDEX BC BC BC BC BC\n-- TYPE COMPT RATE PRESS TEMP\nBCPROP\n1 DIRICHLET GAS 1* 256.0 100.0 /\n2 FREE 4* /\n/\nThe last example shows how the DIRICHLET boundary condition option may be used:\n--\n-- DEFINE BOUNDARY CONDITIONS CONNECTION (OPM FLOW GRID KEYWORD)\n--\n--INDEX ---------- BOX --------- BC\n-- I1 I2 J1 J2 K1 K2 DIRC\nBCCON\n1 1 1 1 1* 1 1* X- /\n2 1 1* 1 1 1 1* Y /\n/\n--\n-- DEFINE BOUNDARY CONDITIONS PROPERTIES (OPM FLOW SCHEDULE KEYWORD)\n--\n--INDEX BC BC BC BC BC\n-- TYPE COMPT RATE PRESS TEMP\nBCPROP\n1 DIRICHLET WAT 1* 256.0 100.0 /\n2 DIRICHLET WAT 1* 1* 100.0 /\n/\nHere, the first line sets both the pressure and temperature at the boundary, and the second line defaults the pressure entry, so that the simulator calculated initial boundary pressure will be used.\n| Note This is an OPM Flow specific keyword and will therefore cause an error in the commercial simulator. |\n|----------------------------------------------------------------------------------------------------------|","expected_columns":16,"size_kind":"list"},"BRANPROP":{"name":"BRANPROP","sections":["SCHEDULE"],"supported":null,"summary":"BRANPROP defines network branch properties for the extended network option for when the Extended Network Model has been activated by the NETWORK keyword in the RUNSPEC section. There are two types of network facilities in the simulator, the Standard Network model, which is defined with the GRUPNET keyword in the SCHEDULE section and the Extended Network Model defined by the BRANPROP and NODEPROP keywords, again in the SCHEDULE section.","parameters":[{"index":1,"name":"DOWNNODE","description":"A character string of up to eight characters in length that defines the down stream node name for this branch, that is the node closest to the wells. Thus for a production network, this will be an inlet node as the wells are importing fluid into the branch node. Whereas for an injection node, this is an outlet node as injection fluid is being exported to the wells.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"UPNODE","description":"A character string of up to eight characters in length that defines the up stream node name for this branch, that is the node furthermost from the wells. Thus for a production network, this will be an outlet node as the wells are exporting fluid from the branch node. Whereas for an injection node, this is an inlet node as the wells are importing the injection fluid.","units":{},"default":"None","value_type":"STRING"},{"index":3,"name":"VFPTAB","description":"A positive integer greater than or equal to zero that defines the vertical lift performance table to be used for calculating the pressure behavior between the inlet (for production) or outlet (for injection) node (DOWNNODE) and the outlet (for production) or inlet (for injection) node (UPNODE). For a production network this must reference a table associated with the VFPPROD keyword, and for an injection network a table declared via the VFPINJ keyword. Both keywords are in the SCHEDULE section. If the pressure behavior between the two nodes is zero (no pressure loss in the network branch), then a value of 9999 should be entered for this variable. A value of zero for VFPTAB removes the branch from the extended network and the resulting flows are ignored in the network flow stream.","units":{},"default":"None","value_type":"INT"},{"index":4,"name":"ALQ-NODE","description":"A real positive value that defines the artificial lift quantity to be used in conjunction with the VFPPROD assigned to the branch via the VPFTAB variable. VFPTAB vertical lift performance table and the artificial lift quantity ALQ-NODE are used with the branch fluid rates to calculate the pressure behavior through the branch. For a network this can be considered to be either a pump to pump fluid through the network or a compressor to compress gas to a higher export pressure. Basically, ALQ-NODE is used to reduce the pressure loss through the branch. Note that the units for ALQ-NODE are dependent on the associated variable on the VFPPROD keyword. Should be set to zero if ALQ-DEN is set to either DENO or DENG, or if the branch is associated with an automatic compressor.","units":{},"default":"0.0","value_type":"DOUBLE"},{"index":5,"name":"ALQ-DEN","description":"A defined character string that defines that ALQ-NODE variable represents either as a surface density or as an artificial lift quantity for a pump or a compressor, and should be set to one of the following: DENO: ALQ-NODE represents the average surface oil density flowing through the branch. DENG: ALQ-NODE represents the average surface gas density flowing through the branch. NONE: ALQ-NODE is the artificial lift quantity as defined on the VFPPROD keyword to model a pump or a compressor. The VFPPROD keyword should be consistent with this variable, that is, if ALQ-DEN is set to to DENO then the surface oil should be used as the ALQ variable on the VFPPROD keyword.","units":{},"default":"NONE","value_type":"STRING"}],"example":"Given the following Extended Network model in Figure 12.3.\n[formula]\n[formula]\nFigure 12.3: Extend Network Example\nFirst the Extended Network model should be used invoked in the RUNSPEC section, and then the BRANPROP keyword should be used to define the branch network, and finally the NODEPROP keyword is used to describe the node properties.\n-- ==============================================================================\n--\n-- RUNSPEC SECTION\n--\n-- ==============================================================================\nRUNSPEC\n--\n-- ACTIVATE THE EXTENDED NETWORK OPTION AND DEFINE PARAMETERS\n--\n-- MAX. MAX NOT\n-- NODE LINK USED\nNETWORK\n3 2 1* /\n…..…………..\n..……..…..\n-- ==============================================================================\n--\n-- SCHEDULE SECTION\n--\n-- ==============================================================================\nSCHEDULE\n--\n-- EXTENDED NETWORK BRANCH PROPERTIES\n--\n-- DOWN UP VFP VFP\n-- NODE NODE TABLE ALFQ\nBRANPROP\nB1 PLAT-A 5 1* /\nC1 PLAT-A 4 1* /\n/\n--\n-- EXTENDED NETWORK NODE PROPERTIES\n--\n-- NODE NODE CHOKE GAS CHOKE SOURCE NETWORK\n-- NAME PRESS OPTN LIFT GROUP SINK TYPE\nNODEPROP\nPLAT-A 21.0 NO NO /\nB1 1* NO NO /\nC1 1* NO NO /\n/\nHere the main platform for the field, PLAT-A, has a fixed 21 barsa pressure applied as an operating constraint.","expected_columns":5,"size_kind":"list"},"CALTRAC":{"name":"CALTRAC","sections":["SCHEDULE"],"supported":false,"summary":"The CALTRAC keyword is used to assign a gas calorfic value to a tracer, for when the Tracer option has been invoked by the TRACER keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"IX1","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"CECON":{"name":"CECON","sections":["SCHEDULE"],"supported":false,"summary":"CECON sets the economic cut-off criteria for a well’s connection to the simulation grid.","parameters":[{"index":1,"name":"WELLNAME","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"I","description":"","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"J","description":"","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"K1","description":"","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"K2","description":"","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"MAX_WCUT","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":7,"name":"MAX_GOR","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":8,"name":"MAX_WGR","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":9,"name":"WORKOVER_PROCEDURE","description":"","units":{},"default":"CON","value_type":"STRING"},{"index":10,"name":"CHECK_STOPPED","description":"","units":{},"default":"NO","value_type":"STRING"},{"index":11,"name":"MIN_OIL","description":"","units":{},"default":"-1e+20","value_type":"DOUBLE"},{"index":12,"name":"MIN_GAS","description":"","units":{},"default":"-1e+20","value_type":"DOUBLE"},{"index":13,"name":"FOLLOW_ON_WELL","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":13,"size_kind":"list"},"CECONT":{"name":"CECONT","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, CECONT, sets the tracer economic cut-off criteria for a well’s connection to the simulation grid.","parameters":[],"example":"","size_kind":"none","size_count":0},"COMPDAT":{"name":"COMPDAT","sections":["SCHEDULE"],"supported":false,"summary":"The COMPDAT keyword defines how a well is connected to the reservoir by defining or modifying existing well connections. Ideally the connections should be declared in the correct sequence, starting with the connection nearest the well head and then working along the wellbore towards the bottom or toe of the well, however this may not be possible or convenient, for example when connections are added or removed from a well during the simulation (see COMPORD in the SCHEDULE section for options regarding connection ordering).","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well connection data are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"I","description":"A positive integer greater than or equal to zero and less than or equal to NX that defines the connection location in the I-direction. If set to zero or defaulted with 1* the location is taken from the wellhead location I-direction value on the WELSPECS keyword in the SCHEDULE section.","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"J","description":"A positive integer greater than or equal to zero and less than or equal to NY that defines the connection location in the J-direction. If set to zero or defaulted with 1* the location is taken from the wellhead location J-direction value on the WELSPECS keyword in the SCHEDULE section.","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"K1","description":"A positive integer greater than or equal to one and less than or equal to NZ that defines the UPPER connection location in the K-direction.","units":{},"default":"None","value_type":"INT"},{"index":5,"name":"K2","description":"A positive integer greater than or equal to K1 and less than or equal to NZ that defines the LOWER connection location in the K-direction.","units":{},"default":"None","value_type":"INT"},{"index":6,"name":"STATUS","description":"A defined character string of length four that defines the connections’ operational status, STATUS should be set to one of the following character strings: OPEN: the connections are open to flow. SHUT: the connections are closed to flow (shut-in). AUTO: the connection are initially closed, but may be opened automatically if an economic limit is violated. Currently this option is not supported by OPM Flow.","units":{},"default":"OPEN","value_type":"STRING","options":["OPEN","SHUT","AUTO"]},{"index":7,"name":"SATNUM","description":"An integer greater than or equal to zero and less than NTSFUN as declared on the TABDIMS keyword in the RUNSPEC section, that defines the saturation table number to be used for flow between the reservoir grid block and the well connections. If SATNUM is set to zero or defaulted with 1* then: The saturation table allocated to the grid block that the connections are located within are used. If the hysteresis option has been activated via the HYSTER variable on the SATOPTS keyword in the RUNSPEC section, then both the imbibition and drainage saturation tables allocated to the grid block that the connections are located within are used. The imbibition table allocation can be changed by the COMPIMB keyword in the RUNSPEC section, provided it is entered after the COMPDAT keyword.","units":{},"default":"0","value_type":"INT"},{"index":8,"name":"CONFACT","description":"A real value greater than or equal to zero that defines the transmissibility connection factor between the well bore and the reservoir grid block. If set to zero or defaulted with 1* then items (9) through (13) are used to calculate CONFACT.","units":{"field":"cP.rb/day/psia 0","metric":"cP.rm3/day/bars 0","laboratory":"cP.rcc/hr/atm 0"},"default":"Defined","value_type":"DOUBLE","dimension":"Viscosity*ReservoirVolume/Time*Pressure"},{"index":9,"name":"DW","description":"A real positive value that defines the well bore diameter of the connections for the well. DW is used in calculating a well’s productivity or injectivity index; however the value will be ignored in calculating the connections CONFACT value if CONFACT has been directly entered.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":"Length"},{"index":10,"name":"KH","description":"A real value that defines the effective KH (permeability x length) for the connections. If less than or equal to zero, or defaulted by 1*, then KH is calculated from the connected grid blocks. KH is ignored if CONFAC has been directly entered.","units":{"field":"mD.ft","metric":"mD.m","laboratory":"mD.cm"},"default":"Calculated from connected grid blocks","value_type":"DOUBLE","dimension":"Permeability*Length"},{"index":11,"name":"SKIN","description":"A real value that defines the connections dimensionless skin factor. SKIN is used in calculating a well’s productivity or injectivity index; however, the value will be ignored in calculating the connections CONFACT value if CONFAC has been directly entered.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.0","value_type":"DOUBLE","dimension":"1"},{"index":12,"name":"DFACT","description":"A real value that defines the non-Darcy D factor coefficient for gas wells. It is recommended that the value should be defaulted with 1* and the non-Darcy D factor coefficient for gas wells defined via the WDFAC keyword in the SCHEDULE section. If the value is greater than or equal to zero then the value is used to define the well D factor and the simulator evaluates the connection D factors internally. If the value is less than zero then its sign is reversed and then used directly to define the connection D factors. In this case any D factor values previously defined using the WDFAC keyword for other connections will retained, whereas, any connection D factors previously defined for the entire well using the WDFACCOR keyword will be discarded.","units":{"field":"day/Mscf","metric":"day/m3","laboratory":"hour/sc"},"default":"0.0","value_type":"DOUBLE","dimension":"Time/GasSurfaceVolume"},{"index":13,"name":"DIRECT","description":"A defined character string of length one that defines the orientation of the connections and should be set to either X, Y, or Z. The direction of connections also determines the length of the connection used to calculate the connection factor if CONFACT has not been entered directly. The default value is for a vertical connection, that is DIRECT is defaulted to Z.","units":{},"default":"Z","value_type":"STRING"},{"index":14,"name":"PR","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"}],"example":"The following example defines two vertical oil wells using the WELSPECS keyword and their associated connection data.\n--\n-- WELL SPECIFICATION DATA\n--\n-- WELL GROUP LOCATION BHP PHASE DRAIN INFLOW OPEN CROSS PRESS\n-- NAME NAME I J DEPTH FLUID AREA EQUANS SHUT FLOW TABLE WELSPECS\nOP01 PLATFORM 14 13 1* OIL 1* STD SHUT NO 1* /\nOP02 PLATFORM 35 96 1* OIL 1* STD SHUT NO 1* /\n/\n--\n-- WELL CONNECTION DATA\n--\n-- WELL --- LOCATION --- OPEN SAT CONN WELL KH SKIN D DIR\n-- NAME II JJ K1 K2 SHUT TAB FACT DIA FACT FACT FACT PEN\nCOMPDAT\nOP01 1* 1* 20 56 OPEN 1* 1* 0.708 1* 0.0 1* 'Z' /\nOP01 1* 1* 75 100 SHUT 1* 1* 0.708 1* 0.0 1* 'Z' /\nOP02 35 96 75 100 OPEN 1* 1* 0.708 1* 0.0 1* 'Z' /\nWell OP01 has two sets of connections; the first one connects grid cells (14, 13, 20) to (14, 13, 56) to the well and is open to flow and the second connecting grid cells (14, 13, 75) to (14, 13, 100) is shut. Well OP02 has only one open set of connections from cells (35, 96, 75) to cells (35, 96, 100).\n| Note The term well connection is used to describe individual connections from the wellbore to the reservoir grid, as opposed to well completions. A well completion is used to describe a set of connections, for example, a well may consist of several completions with each completion consisting of multiple connections. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":14,"size_kind":"list"},"COMPDATL":{"name":"COMPDATL","sections":["SCHEDULE"],"supported":false,"summary":"The COMPDATL keyword defines how a well in a Local Grid Refinement (“LGR”) is connected to the reservoir by declaring the LGR and defining or modifying existing well connections. Ideally the connections should be declared in the correct sequence, starting with the connection nearest the well head and then working along the wellbore towards the bottom or toe of the well, however this may not be possible or convenient, for example when connections are added or removed from a well during the simulation (see the COMPORD keyword in the SCHEDULE section for options regarding connection ordering).","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well connection data are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None"},{"index":2,"name":"LGRNAME","description":"A character string of up to eight characters in length that defines the LGR name for which the well LGR connection data are being defined. Note that the well name (LGRNAME) must have been declared previously using the WELSPECL keyword in the SCHEDULE section, otherwise an error may occur. If defaulted with 1* the LGR on the WELSPECL keyword will be utilized.","units":{},"default":"Defined"},{"index":3,"name":"I","description":"A positive integer greater than or equal to zero and less than or equal to NX that defines the connection location in the I-direction. If set to zero or defaulted with 1* the location is taken from the wellhead location I-direction value on the WELSPECS keyword in the SCHEDULE section.","units":{},"default":"0"},{"index":4,"name":"J","description":"A positive integer greater than or equal to zero and less than or equal to NY that defines the connection location in the J-direction. If set to zero or defaulted with 1* the location is taken from the wellhead location J-direction value on the WELSPECS keyword in the SCHEDULE section.","units":{},"default":"0"},{"index":5,"name":"K1","description":"A positive integer greater than or equal to one and less than or equal to NZ that defines the UPPER connection location in the K-direction.","units":{},"default":"None"},{"index":6,"name":"K2","description":"A positive integer greater than or equal to K1 and less than or equal to NZ that defines the LOWER connection location in the K-direction.","units":{},"default":"None"},{"index":7,"name":"STATUS","description":"A character string of length four that defines the connections’ operational status, STATUS should be set to one of the following character strings: OPEN: the connections are open to flow. SHUT: the connections are closed to flow (shut-in). AUTO: the connection are initially closed, but may be opened automatically if an economic limit is violated. Currently this option is not supported by OPM Flow","units":{},"default":"OPEN"},{"index":8,"name":"SATNUM","description":"An integer greater than or equal to zero and less than NTSFUN as declared on the TABDIMS keyword in the RUNSPEC, that defines the saturation table number to be used for flow between the reservoir grid block and the well connections. If SATNUM is set to zero or defaulted with 1* then: The saturation table allocated to the grid block that the connections are located within are used. If the hysteresis option has been activated via the HYSTER variable on the SATOPTS keyword in the RUNSPEC section, then both the imbibition and drainage saturation tables allocated to the grid block that the connections are located within are used. The imbibition table allocation can be changed by the COMPIMB keyword in the RUNSPEC section, provided it is entered after the COMPDAT keyword.","units":{},"default":"0"},{"index":9,"name":"CONFACT","description":"A real value greater than or equal to zero that defines the transmissibility connection factor between the well bore and the reservoir grid block. If set to zero or defaulted with 1* then items (9) through (13) are used to calculate CONFACT.","units":{"field":"cP.rb/day/psia 0","metric":"cP.rm3/day/bars 0","laboratory":"cP.rcc/hr/atm 0"},"default":"Defined"},{"index":10,"name":"DW","description":"A real positive value that defines the well bore diameter of the connections for the well. DW is used in calculating a well’s productivity or injectivity index; however the value will be ignored in calculating the connections CONFACT value if CONFAC has been directly entered.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None"},{"index":11,"name":"KH","description":"A real value that defines the effective KH (permeability x length) for the connections. If less than or equal to zero or defaulted by 1* then KH is calculated from the connected grid blocks. KH is ignored if CONFAC has been directly entered.","units":{"field":"mD.ft","metric":"mD.m","laboratory":"mD.cm"},"default":"Calculated from connected grid blocks"},{"index":12,"name":"SKIN","description":"A real value that defines the connections dimensionless skin factor. SKIN is used in calculating a well’s productivity or injectivity index; however, the value will be ignored in calculating the connections CONFACT value if CONFAC has been directly entered.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.0"},{"index":13,"name":"DFACT","description":"A real value that defines the non-Darcy D factor coefficient for gas wells. This value should be defaulted with 1* and the non-Darcy D factor coefficient for gas wells defined via the WDFAC keyword in the SCHEDULE section. Currently this option is not supported by OPM Flow.","units":{"field":"day/Mscf","metric":"day/m3","laboratory":"hour/sc"},"default":"1*"},{"index":14,"name":"DIRECT","description":"A one letter character string that defines the orientation of the connections and should be set to either X, Y, or Z. The direction of connections also determines the length of the connection used to calculate the connection factor if CONFAC has not been entered directly. The default value is for a vertical connection, that is DIRECT is defaulted to Z.","units":{},"default":"Z"}],"example":"The following example defines two vertical oil wells using the WELSPECS keyword and their associated connection data.\n--\n-- WELL LGR SPECIFICATION DATA\n--\n-- WELL GROUP LGR -LOCATION- BHP PHASE DRAIN INFLOW SHUT CROSS PVT\n-- NAME NAME NAME I J DEPTH FLUID AREA EQUA. IN FLOW TABLE\nWELSPECL\nOP01 PLAT OP01LGR 14 13 1* OIL 1* STD SHUT NO 1* /\nOP02 PLAT OP02LGR 28 96 1* OIL 1* STD SHUT NO 1* /\n/\n--\n-- WELL LGR CONNECTION DATA\n--\n-- WELL LGR ---LOCATION--- OPEN SAT CONN WELL KH SKIN D DIR\n-- NAME NAME II JJ K1 K2 SHUT TAB FACT DIA FACT FACT FACT PEN\nCOMPDATL\nOP01 OP01LGR 1* 1* 20 56 OPEN 1* 1* 0.708 1* 1* 1* Z /\nOP01 OP01LGR 1* 1* 75 100 SHUT 1* 1* 0.708 1* 1* 1* Z / OP02 OP02LGR 35 96 75 100 OPEN 1* 1* 0.708 1* 1* 1* Z /\n/\nWell OP01 has two sets of connections; the first one connects grid cells (14, 13, 20) to (14, 13, 56) to the well and is open to flow and the second connecting grid cells (14, 13, 75) to (14, 13, 100) is shut. Well OP02 has only one open connection from cells (35, 96, 75) to cells (35, 96, 100).\n| Note The term well connection is used to describe individual connections from the wellbore to the reservoir grid, as opposed to well completions. A well completion is used to describe a set of connections, for example, a well may consist of several completions with each completion consisting of multiple connections. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|"},"COMPDATM":{"name":"COMPDATM","sections":["SCHEDULE"],"supported":false,"summary":"The COMPDATM keyword is an alias for the COMPDATL keyword. COMPDATM defines how a well in an amalgamated Local Grid Refinement (“LGR”) is connected to the reservoir by declaring the LGR and defining or modifying existing well connections. Ideally the connections should be declared in the correct sequence, starting with the connection nearest the well head and then working along the wellbore towards the bottom or toe of the well, however this may not be possible or convenient, for example when connections are added or removed from a well during the simulation (see the COMPORD keyword in the SCHEDULE section for options regarding connection ordering).","parameters":[],"example":""},"COMPFLSH":{"name":"COMPFLSH","sections":["SCHEDULE"],"supported":false,"summary":"COMPFLSH is used to assign saturated PVT differential-flash liberation ratios to individual well completions for both the oil formation volume factor and the gas-oil ratio. Only the saturated oil properties are changed by this keyword, that is only data entered via the PVCO or PVTO keywords in the PROPS section will be used in the calculation. The other fluid PVT property keywords: PVTW, PVTG, DENSITY, etc., are not used.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"I","description":"","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"J","description":"","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"UPPER_K","description":"","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"LOWER_K","description":"","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"F1","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"},{"index":7,"name":"F2","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"},{"index":8,"name":"FLASH_PVTNUM","description":"","units":{},"default":"0","value_type":"INT"}],"example":"","expected_columns":8,"size_kind":"list"},"COMPIMB":{"name":"COMPIMB","sections":["SCHEDULE"],"supported":false,"summary":"The COMPIMB keyword assigns imbibition saturation tables to well connections. The COMPDAT keyword in the SCHEDULE section also assigns imbibition saturation tables to connections, but in this case the table number is the same as for the drainage curve. If this is not the required assignment then the COMPIMB keyword can be used to reset the imbibition saturation table number. For this to be effective the COMPIMB keyword must precede the COMPDAT keyword, otherwise it will have no effect.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well connection data is being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"I","description":"A positive integer greater than or equal to zero and less than or equal to NX that defines the connection location in the I-direction. If set to zero or defaulted with 1* then all connections in the I-direction that also satisfy J, K1 and K2 criteria are assigned the IMBNUM imbibition table number.","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"J","description":"A positive integer greater than or equal to zero and less than or equal to NY that defines the connection location in the J-direction. If set to zero or defaulted with 1* then all connections in the J-direction that also satisfy I, K1 and K2 criteria are assigned the IMBNUM imbibition table number.","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"K1","description":"A positive integer greater than or equal to one and less than or equal to NZ that defines the UPPER connection location in the K-direction. If set to zero or defaulted with 1* then the upper most connection in the well is used.","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"K2","description":"A positive integer greater than or equal to K1 and less than or equal to NZ that defines the LOWER connection location in the K-direction. If set to zero or defaulted with 1* then the lowest most connection in the well is used.","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"IMBNUM","description":"An integer greater than or equal to zero and less than NTSFUN as declared on the TABDIMS keyword in the RUNSPEC, that defines the imbibition saturation table number to be used for flow between the reservoir grid block and the well connections. If IMBNUM is set to zero or defaulted with 1* then the inhibition saturation table allocated to the grid block that the connections are located within is used. If I, J, K1, K2 are all set to zero or defaulted to 1*, then IMBNUM is allocated to all connections in the well.","units":{},"default":"0","value_type":"INT"}],"example":"The following example defines the connections for two vertical oil wells using the COMPDAT keyword and then re-sets the imbibition saturation functions using the COMPIMP keyword.\n--\n-- WELL CONNECTION DATA\n--\n-- WELL --- LOCATION --- OPEN SAT CONN WELL KH SKIN D DIR\n-- NAME II JJ K1 K2 SHUT TAB FACT DIA FACT FACT FACT PEN\nCOMPDAT\nOP01 1* 1* 20 56 OPEN 1 1* 0.708 1* 0.0 1* 'Z' /\nOP01 1* 1* 75 100 SHUT 2 1* 0.708 1* 0.0 1* 'Z' /\nOP02 35 96 75 100 OPEN 1 1* 0.708 1* 0.0 1* 'Z' /\n--\n-- ASSIGN IMBIBITION SATURATION TABLES TO CONNECTIONS\n--\n-- WELL ---LOCATION--- SAT\n-- NAME II JJ K1 K2 TAB\nCOMPIMB\nOP01 1* 1* 20 56 11 /\nOP01 1* 1* 75 100 12 /\nOP02 1* 1* 1* 1* 11 /\n/\nWell OP01 has two sets of COMPIMB records to overwrite the imbibition saturation tables, one for connections (14, 13, 20) to (14, 13, 56) resetting the imbibition saturation table number from one to 11 and one for connections (14, 13, 75) to (14, 13, 100) that resets the imbibition table number from 2 to 12. Well OP02 has only one connection from cells (35, 96, 75) to cells (35, 96, 100), so all the default values for I, J, K1, and K2 can be used to set the imbibition table numbers from 2 to 11. Note in all cases the drainage saturation table retains the value as specified by the COMPDAT keyword, that is one, two and one.","expected_columns":6,"size_kind":"list"},"COMPINJK":{"name":"COMPINJK","sections":["SCHEDULE"],"supported":false,"summary":"The COMPINJK keyword assigns injection well relative permeability values to well connections.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"I","description":"","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"J","description":"","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"K_UPPER","description":"","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"K_LOWER","description":"","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"REL_PERM","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"1"}],"example":"","expected_columns":6,"size_kind":"list"},"COMPLMPL":{"name":"COMPLMPL","sections":["SCHEDULE"],"supported":false,"summary":"The COMPLMPL keyword assigns well connections in a LGR, as defined by the COMPDATL keyword in the SCHEDULE section, to completion intervals. This “lumping” of the connections to various completion intervals allows automatic workovers and economic criteria to be applied to the completions (that is a set of connections) as opposed to the connections. This allows for a more realistic approach for workovers operations.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well connection data are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"LGRNAME","description":"A character string of up to eight characters in length that defines the LGR name for which the well LGR connection data are being defined. Note that the well name (LGRNAME) must have been declared previously using the WELSPECL keyword in the SCHEDULE section, otherwise an error may occur. If defaulted with 1* the LGR on the WELSPECL keyword will be utilized.","units":{},"default":"Defined","value_type":"STRING"},{"index":3,"name":"I","description":"A positive integer greater than or equal to zero and less than or equal to NX that defines the connection location in the I-direction. If set to zero or defaulted with 1* then all connections in the I-direction that also satisfy J, K1 and K2 criteria are assigned the ICOMP completion number.","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"J","description":"A positive integer greater than or equal to zero and less than or equal to NY that defines the connection location in the J-direction. If set to zero or defaulted with 1* then all connections in the J-direction that also satisfy I, K1 and K2 criteria are assigned the ICOMP completion number.","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"K1","description":"A positive integer greater than or equal to one and less than or equal to NZ that defines the UPPER connection location in the K-direction. If set to zero or defaulted with 1* then the upper most connection in the well is used.","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"K2","description":"A positive integer greater than or equal to K1 and less than or equal to NZ that defines the LOWER connection location in the K-direction. If set to zero or defaulted with 1* then the low most connection in the well is used.","units":{},"default":"0","value_type":"INT"},{"index":7,"name":"ICOMP","description":"An integer greater than or equal to one and less than or equal to MXCONS as defined on the WELLDIMS keyword in the RUNSPEC section, that defines the completion number of the currently defined set of connections. If I, J, K1, K2 are all set to zero or defaulted to 1*, then all connections in the well have the same completion number of ICOMP.","units":{},"default":"None","value_type":"INT"}],"example":"The following example defines the connections for two vertical oil wells using the COMPDATL keyword and the re-allocation of the connections to completions intervals using the COMPLMPL keyword.\n--\n-- WELL CONNECTION DATA FOR LGR WELLS\n--\n-- WELL LGR --- LOCATION --- OPEN SAT CONN WELL D DIR\n-- NAME NAME II JJ K1 K2 SHUT TAB FACT DIA FACT PEN\nCOMPDATL\nOP01 OP01LGR 14 13 20 56 OPEN 1* 1* 0.708 3* Z /\nOP01 OP01LGR 14 13 75 100 SHUT 1* 1* 0.708 3* Z /\nOP02 OP02LGR 35 96 75 100 OPEN 1* 1* 0.708 3* Z /\n/\n--\n-- ASSIGN WELL CONNECTIONS TO COMPLETIONS\n--\n-- WELL LGR --- LOCATION --- COMPL\n-- NAME NAME II JJ K1 K2 NO. COMPLMPL OP01 OP01LGR 1* 1* 20 56 1 / COMPLETION NO. 01\nOP01 OP01LGR 1* 1* 75 100 2 / COMPLETION NO. 02\nOP02 OP02LGR 1* 1* 75 85 1 / COMPLETION NO. 01\nOP02 OP21LGR 1* 1* 86 100 2 / COMPLETION NO. 02\n/\nHere the well OP01 connections (14, 13, 20) to (14, 13, 56) are assigned to completion number one and connections (14, 13, 75) to (14, 13, 100) are assigned to completion number two. Well OP02 has only one set of connection data from cells (35, 96, 75) to cells (35, 96, 100), but they have split into two separate completion intervals, with connections (35. 96, 75) to (35. 96, 85) assigned to completion interval number one and (35, 96, 86) to (35, 96, 100) to completion number two.","expected_columns":7,"size_kind":"list"},"COMPLUMP":{"name":"COMPLUMP","sections":["SCHEDULE"],"supported":null,"summary":"The COMPLUMP keyword assigns connections, as defined by the COMPDAT keyword in the SCHEDULE section, to completion intervals. This “lumping” of the connections to various completion intervals allows automatic workovers and economic criteria to be applied to the completions (that is a set of connections) as opposed to the connections. This allows for a more realistic approach for workovers operations.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well connection data are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"I","description":"A positive integer greater than or equal to zero and less than or equal to NX that defines the connection location in the I-direction. If set to zero or defaulted with 1* then all connections in the I-direction that also satisfy J, K1 and K2 criteria are assigned the ICOMP completion number.","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"J","description":"A positive integer greater than or equal to zero and less than or equal to NY that defines the connection location in the J-direction. If set to zero or defaulted with 1* then all connections in the J-direction that also satisfy I, K1 and K2 criteria are assigned the ICOMP completion number.","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"K1","description":"A positive integer greater than or equal to one and less than or equal to NZ that defines the UPPER connection location in the K-direction. If set to zero or defaulted with 1* then the uppermost connection in the well is used.","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"K2","description":"A positive integer greater than or equal to K1 and less than or equal to NZ that defines the LOWER connection location in the K-direction. If set to zero or defaulted with 1* then the lowermost connection in the well is used.","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"ICOMP","description":"An integer greater than or equal to one and less than or equal to MXCONS as defined on the WELLDIMS keyword in the RUNSPEC section, that defines the completion number of the currently defined set of connections. If I, J, K1, K2 are all set to zero or defaulted to 1*, then all connections in the well have the same completion number of ICOMP.","units":{},"default":"None","value_type":"INT"}],"example":"The following example defines the connections for two vertical oil wells using the COMPDAT keyword and the re-allocation of the connections to completions intervals using the COMPLUMP keyword.\n--\n-- WELL CONNECTION DATA\n--\n-- WELL --- LOCATION --- OPEN SAT CONN WELL KH SKIN D DIR\n-- NAME II JJ K1 K2 SHUT TAB FACT DIA FACT FACT FACT PEN\nCOMPDAT\nOP01 14 13 20 56 OPEN 1* 1* 0.708 1* 0.0 1* 'Z' /\nOP01 14 13 75 100 SHUT 1* 1* 0.708 1* 0.0 1* 'Z' /\nOP02 35 96 75 100 OPEN 1* 1* 0.708 1* 0.0 1* 'Z' /\n/\n--\n-- ASSIGN WELL CONNECTIONS TO COMPLETIONS\n--\n-- WELL --- LOCATION --- COMPL\n-- NAME II JJ K1 K2 NO. COMPLUMP OP01 1* 1* 20 56 1 / COMPLETION NO. 01\nOP01 1* 1* 75 100 2 / COMPLETION NO. 02\nOP02 1* 1* 75 85 1 / COMPLETION NO. 01\nOP02 1* 1* 86 100 2 / COMPLETION NO. 02\n/\nHere the well OP01 connections (14, 13, 20) to (14, 13, 56) are assigned to completion number one and connections (14, 13, 75) to (14, 13, 100) are assigned to completion number two. Well OP02 has only one set of connection data from cells (35, 96, 75) to cells (35, 96, 100), but they have been split into two separate completion intervals, with connections (35, 96, 75) to (35. 96, 85) assigned to completion interval number one and (35, 96, 86) to (35, 96, 100) assigned to completion number two.","expected_columns":6,"size_kind":"list"},"COMPOFF":{"name":"COMPOFF","sections":["SCHEDULE"],"supported":false,"summary":"The COMPOFF keyword deactivates network automatic compressors defined via the GASFCOMP keyword in the SCHEDULE section.","parameters":[],"example":"","size_kind":"none","size_count":0},"COMPORD":{"name":"COMPORD","sections":["SCHEDULE"],"supported":true,"summary":"The COMPORD keyword defines how the well connection data entered on the COMPDAT keyword in the SCHEDULE section are to be ordered for a well.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well connection data are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"COMPORD","description":"A character string that defines the method for ordering the well connections given on the COMPDAT keyword, and should be set to DEPTH, INPUT, or TRACK. DEPTH: The connections are ordered by a connection’s true vertical depth from the shallowest to the deepest. If multiple connections are at the same depth then these connections are sub ordered by the sequence they were entered on the COMPDAT keyword. INPUT: This option results in the connections being ordered in the same sequence as entered via the COMPDAT keyword. In this case the connections should be declared in the correct sequence, starting with the connection nearest the well head and then working along the wellbore towards the bottom or toe of the well. Atgeirr Rasmussen\n 2017-09-20T11:54:43\n AFR\n This option is somewhat involved to explain precisely, should we insert an explanation of the algorithm used here? If not here, where?\n TRACK\n David Baxendale\n 2017-10-02T17:52:03.846000000\n DBx\n Reply to Atgeirr Rasmussen (09/20/2017, 11:54): \"...\"\n Yes, we need to document this but I think this can wait until we get the first release out, otherwise we will never finish. I’ll keep the comments so we can trackt it.\n : This option enables OPM Flow to trace the well connections through the grid to obtain the correct order for the connections. If the supplied COMPDAT indicates the well is vertical (via the DIRECT variable being equal to Z on the COMPDAT keyword) then the DEPTH option will be applied instead. This option is somewhat involved to explain precisely, should we insert an explanation of the algorithm used here? If not here, where? Reply to Atgeirr Rasmussen (09/20/2017, 11:54): \"...\" Yes, we need to document this but I think this can wait until we get the first release out, otherwise we will never finish. I’ll keep the comments so we can trackt it. All options are now supported by OPM Flow.","units":{},"default":"TRACK","value_type":"STRING"}],"example":"The following example defines the connections for two vertical oil wells using the COMPDAT keyword and the COMPORD to defined the connection ordering for the wells.\n--\n-- WELL CONNECTION DATA\n--\n-- WELL --- LOCATION --- OPEN SAT CONN WELL KH SKIN D DIR\n-- NAME II JJ K1 K2 SHUT TAB FACT DIA FACT FACT FACT PEN\nCOMPDAT\nOP01 1* 1* 20 56 OPEN 1* 1* 0.708 1* 0.0 1* 'Z' /\nOP01 1* 1* 75 100 SHUT 1* 1* 0.708 1* 0.0 1* 'Z' /\nOP02 35 96 75 100 OPEN 1* 1* 0.708 1* 0.0 1* 'Z' /\n--\n-- DEFINE WELL CONNECTION ORDERING\n--\n-- WELL COMPL\n-- NAME ORDER\nCOMPORD\nOP01 DEPTH /\nOP02 DEPTH /\n/\nThe DEPTH option has been chosen because both wells are vertical. Also one could use the following format instead for the COMPORD:\n--\n-- DEFINE WELL CONNECTION ORDERING\n--\n-- WELL COMPL\n-- NAME ORDER\nCOMPORD\n* DEPTH /\n/\nas both wells should utilize the DEPTH option. This version would set all wells in the model to DEPTH connection ordering.\n| Note If visual inspection of the well trajectories in the model indicate problematic or unrealistic well connections, the options on this keyword may be useful in correcting the issue. |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":2,"size_kind":"list"},"COMPRIV":{"name":"COMPRIV","sections":["SCHEDULE"],"supported":false,"summary":"The COMPRIV keyword defines grid cell connections to a river, for when the River option has been activated via the RIVRDIMS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"RIVER","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"I","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"J","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"K","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":4,"size_kind":"list"},"COMPRP":{"name":"COMPRP","sections":["SCHEDULE"],"supported":false,"summary":"The COPMPRP keyword re-scales the fluid saturations of a well’s connection to the grid block.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"I","description":"","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"J","description":"","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"K_UPPER","description":"","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"K_LOWER","description":"","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"SAT_TABLE_NUM","description":"","units":{},"default":"","value_type":"INT"},{"index":7,"name":"SWMIN","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":8,"name":"SWMAX","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":9,"name":"SGMIN","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":10,"name":"SGMAX","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"}],"example":"","expected_columns":10,"size_kind":"list"},"COMPRPL":{"name":"COMPRPL","sections":["SCHEDULE"],"supported":false,"summary":"The COPMPRPL keyword re-scales the fluid saturations of a well’s connection to an LGR grid block, for when the Local Grid Refinement (“LGR”) option has been activated by the LGR keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"LOCAL_GRID","description":"","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"I","description":"","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"J","description":"","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"K_UPPER","description":"","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"K_LOWER","description":"","units":{},"default":"0","value_type":"INT"},{"index":7,"name":"SAT_TABLE_NUM","description":"","units":{},"default":"","value_type":"INT"},{"index":8,"name":"SWMIN","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":9,"name":"SWMAX","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":10,"name":"SGMIN","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":11,"name":"SGMAX","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"}],"example":"","expected_columns":11,"size_kind":"list"},"COMPSEGL":{"name":"COMPSEGL","sections":["SCHEDULE"],"supported":false,"summary":"The COMSEGSL keyword defines how a multi-segment well is connected to the reservoir by defining or modifying existing well connections in an LGR. Note that well must have been previously define by the WELSPECL keyword in the SCHEDULE section and the well connections must have been previously defined via the COMPDATL keyword in the SCHEDULE section. The COMPSEGL keyword should be repeated for each multi-segment well in the model.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which a multi-segment well is being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECL keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","record":1,"value_type":"STRING"},{"index":1,"name":"LGRNAME","description":"A character string of up to eight characters in length that defines the name of the local grid refinement for which the well is assigned to.","units":{},"default":"None","record":2,"value_type":"STRING"},{"index":2,"name":"I","description":"A positive integer greater than or equal to one and less than or equal to NX that defines the connection location in the I-direction.","units":{},"default":"None","record":2,"value_type":"INT"},{"index":3,"name":"J","description":"A positive integer greater than or equal to zero and less than or equal to NY that defines the connection location in the J-direction.","units":{},"default":"None","record":2,"value_type":"INT"},{"index":4,"name":"K","description":"A positive integer greater than or equal to zero and less than or equal to NZ that defines the connection location in the K-direction.","units":{},"default":"None","record":2,"value_type":"INT"},{"index":5,"name":"IBRANCH","description":"A positive integer greater than or equal to one and less than or equal to MXBRAN on WSEGDIMS keyword in the RUNSPEC section that defines the branch number of the defined I, J and K connection.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","record":2,"value_type":"INT"},{"index":6,"name":"DISTANCE_START","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length","record":2},{"index":7,"name":"DEPTH2","description":"DEPTH2 is a real positive value that defines the length of the tubing from the tubing head or wellhead at the surface to the end of the connection in the I, J, K cell.","units":{},"default":"","record":2,"value_type":"DOUBLE","dimension":"Length"},{"index":8,"name":"DIRECT","description":"A one letter character string that defines the orientation of the connections and should be set to either X, Y, or Z. The direction of connections also determines the length of the connection The default value is for a vertical connection, that is DIRECT is defaulted to Z.","units":{},"default":"Z","record":2,"value_type":"STRING"},{"index":9,"name":"IEND","description":"IEND is positive or negative integer, that is not equal to zero that is set to one of the following: a value between -NX and +NX that is not equal to zero that defines the last connection location in the I-direction, a value between -NY and +NY that is not equal to zero that defines the last connection location in the J-direction, or a value between -NZ and +NZ that is not equal to zero that defines the last connection location in the K-direction, that defines the end of the range of the connections depending on the value of DIRECT. For example, if DIRECT is equal to Y or J then the IEND will be associated with the J-direction. The value may be positive or negative but must be calculated to remain within the grid. For example for NY is set 100 on the DIMENS keyword in the RUNSPEC section and J on this record set to 50, then IEND most range between -49 to +50. Currently this option is not supported by OPM Flow.","units":{},"default":"None","record":2,"value_type":"INT"},{"index":10,"name":"DEPTH3","description":"DEPTH3 is a real positive value that defines the datum depth for this set of connection, normally taken as the mid-point of the perforations associated with this set of connections. Currently this option is not supported by OPM Flow.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","record":2,"value_type":"DOUBLE","dimension":"Length"},{"index":11,"name":"LENGTH","description":"LENGTH is a real positive value that defines the length of the well for this set of completions that is used in thermal calculations.. Currently this option is not supported by OPM Flow.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","record":2,"value_type":"DOUBLE","dimension":"Length"},{"index":12,"name":"ISEG","description":"A real positive values equal to or greater than zero that defines the coordinate in the x-direction of the nodal point of this segment that is used for display purposes only. Currently this option is not supported by OPM Flow.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","record":2,"value_type":"INT"}],"example":"The following example defines the completions for two oil producing segment oil wells (OP01 and OP02) using the COMPSEGS keywords.\n-- COMPLETION SEGMENT SPECIFICATION DATA\n--\n-- WELL\n-- NAME\nCOMPSEGS\nOP01 /\n-- LGR --LOCATION-- BRAN TUBING NODAL DIR LOC MID COMP ISEG\n-- NAME II JJ K1 NO LENGTH DEPTH PEN I,J,K PERFS LENGTH\nLGR01 10 10 1 1 2512.5 2525.0 /\nLGR01 10 10 2 1 2525.0 2550.0 /\nLGR01 10 10 3 1 2550.0 2575.0 /\nLGR01 10 10 4 1 2575.0 2600.0 /\nLGR01 10 10 5 1 2600.0 2625.0 /\nLGR01 10 10 6 1 2625.0 2650.0 /\nLGR01 9 10 2 2 2637.5 2837.5 /\nLGR01 8 10 2 2 2837.5 3037.5 /\nLGR01 7 10 2 2 3037.5 3237.5 /\nLGR01 6 10 2 2 3237.5 3437.5 /\nLGR01 5 10 2 2 3437.5 3637.5 /\n/\nNote that the COMPDATL keyword in the SCHEDULE section must also be defines for this well.","records_meta":[{"expected_columns":1},{"expected_columns":12}],"size_kind":"list"},"COMPSEGS":{"name":"COMPSEGS","sections":["SCHEDULE"],"supported":false,"summary":"This keyword defines how a multi-segment well is connected to the reservoir by allocating each well connection to a well segement. Note that the well must have previously been defined as a multi-segment well using the WELSEGS keyword in the SCHEDULE section and the well connections must have previously been defined via the COMPDAT keyword in the SCHEDULE section.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which a multi-segment well is being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","record":1,"value_type":"STRING"},{"index":1,"name":"I","description":"A positive integer greater than or equal to one and less than or equal to NX that defines the connection location in the I-direction.","units":{},"default":"None","record":2,"value_type":"INT"},{"index":2,"name":"J","description":"A positive integer greater than or equal to one and less than or equal to NY that defines the connection location in the J-direction.","units":{},"default":"None","record":2,"value_type":"INT"},{"index":3,"name":"K","description":"A positive integer greater than or equal to one and less than or equal to NZ that defines the connection location in the K-direction.","units":{},"default":"None","record":2,"value_type":"INT"},{"index":4,"name":"IBRANCH","description":"A positive integer greater than or equal to one and less than or equal to MXBRAN on WSEGDIMS keyword in the RUNSPEC section that defines the branch number of the defined I, J and K connection.","units":{},"default":"None","record":2,"value_type":"INT"},{"index":5,"name":"LENGTH1","description":"A real positive value that defines the length of the tubing from the tubing reference point (for example Measure Depth Relative to Kelly Bushing, MDRKB) to the start of the connection in the I, J, K cell.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","record":2,"value_type":"DOUBLE","dimension":"Length"},{"index":6,"name":"LENGTH2","description":"A real positive value that defines the length of the tubing from the tubing reference point to the end of the connection in the I, J, K cell.","units":{},"default":"","record":2,"value_type":"DOUBLE","dimension":"Length"},{"index":7,"name":"DIRECT","description":"A one letter character string that defines the orientation of the connections and should be set to either X, Y or Z, or either I, J or K. The direction of connections may also determine the length of the connection. Currently this option is not supported by OPM Flow.","units":{},"default":"None","record":2,"value_type":"STRING"},{"index":8,"name":"IJKEND","description":"A positive integer that is set to one of the following depending on the orientation of the connections (DIRECT): X or I: A value between 1 and NX that defines the last connection location in the I-direction, Y or J: A value between 1 and NY that defines the last connection location in the J-direction, or Z or K: A value between 1 and NZ that defines the last connection location in the K-direction. For example, if DIRECT is equal to Y or J then the IJKEND will be associated with the J-direction. The value may be less than or greater than Y or J but must be between 1 and NY. Currently this option is not supported by OPM Flow.","units":{},"default":"None","record":2,"value_type":"INT"},{"index":9,"name":"DEPTH","description":"A real positive value that defines the datum depth for this set of connections, normally taken as the mid-point of the perforations associated with this set of connections. Currently this option is not supported by OPM Flow.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","record":2,"value_type":"DOUBLE","dimension":"Length"},{"index":10,"name":"THLEN","description":"A real positive value that defines the length of the well in the connection cells for this set of completions that is used in thermal calculations. If this value is defaulted then the thickness of the cell in the direction of the well orientation (DIRECT) is used. Currently this option is not supported by OPM Flow.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","record":2,"value_type":"DOUBLE","dimension":"Length"},{"index":11,"name":"ISEG","description":"A real positive value that defines the segment number to assign to this range of connections. If this value is defaulted then each connection is assigned to the segment with the nodal point nearest to the centre of the connection. Currently this option is not supported by OPM Flow.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","record":2,"value_type":"INT"}],"example":"The following example defines the completions for two multi-segment oil production wells (OP01 and OP02) using the COMPSEGS keyword.\n-- COMPLETION SEGMENT SPECIFICATION DATA\n--\n-- WELL\n-- NAME\nCOMPSEGS\nOP01 /\n-- --LOCATION-- BRAN START END DIR LOC MID COMP ISEG\n-- II JJ K1 NO LENGTH LENGTH PEN I,J,K PERFS LENGTH\n10 10 1 1 2512.5 2525.0 /\n10 10 2 1 2525.0 2550.0 /\n10 10 3 1 2550.0 2575.0 /\n10 10 4 1 2575.0 2600.0 /\n10 10 5 1 2600.0 2625.0 /\n10 10 6 1 2625.0 2650.0 /\n9 10 2 2 2637.5 2837.5 /\n8 10 2 2 2837.5 3037.5 /\n7 10 2 2 3037.5 3237.5 /\n6 10 2 2 3237.5 3437.5 /\n5 10 2 2 3437.5 3637.5 /\n/\n-- COMPLETION SEGMENT SPECIFICATION DATA\n--\n-- WELL\n-- NAME\nCOMPSEGS\nOP02 /\n-- --LOCATION-- BRAN START END DIR LOC MID COMP ISEG\n-- II JJ K1 NO LENGTH LENGTH PEN I,J,K PERFS LENGTH\n1 9 3 1 2662.5 2862.5 /\n1 8 3 1 2862.5 3062.5 /\n1 7 3 1 3062.5 3262.5 /\n1 6 3 1 3262.5 3462.5 /\n1 5 3 1 3462.5 3662.5 /\n2 10 5 2 2712.5 2912.5 /\n2 10 5 2 2912.5 3112.5 /\n4 10 5 2 3112.5 3312.5 /\n5 10 5 2 3312.5 3512.5 /\n6 10 5 2 3512.5 3712.5 /\n1 9 6 3 2737.5 2937.5 /\n1 8 6 3 2937.5 3137.5 /\n1 7 6 3 3137.5 3337.5 /\n1 6 6 3 3337.5 3537.5 /\n1 5 6 3 3537.5 3737.5 /\n/\nNote that the COMPDAT keyword in the SCHEDULE section must also be defined for these two wells.","records_meta":[{"expected_columns":1},{"expected_columns":11}],"size_kind":"list"},"COMPTRAJ":{"name":"COMPTRAJ","sections":["SCHEDULE"],"supported":true,"summary":"The COMPTRAJ keyword defines how a well that has been declared as a trajectory well, using the WELTRAJ keyword in the SCHEDULE section, is connected to the reservoir model by defining or modifying existing well perforation depths. The keyword can only be used for wells defined by the WELTRAJ keyword, and WELTRAJ defined wells must use the COMPTRAJ keyword to define the connections to the grid, that is one cannot use COMPDAT for these type of wells.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well connection data are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"IBRANCH","description":"A positive integer greater than or equal to one and less than or equal to MXBRAN on WSEGDIMS keyword in the RUNSPEC section that defines the branch number of a segment. All segments on the main stem must have IBRANCH set to one and lateral branches should have values between two and MXSEGS on the WSEGDIMS keyword in the RUNSPEC section. Only the default value of one is currently supported, that is only the main branch of a multi-segment well is supported, or a single trajectory for a conventional well.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"1","value_type":"INT"},{"index":3,"name":"PERF_TOP","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":4,"name":"PERF_BOT","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":5,"name":"REF","description":"REF is a defined character string that defines the reference depth type for TOP and BOT, and should be set to either: MD for the depths referencing Measured Depth, or TVD for depths referencing True Vertical Depth. Only measured depth is currently supported, that is MD.","units":{},"default":"MD","value_type":"STRING"},{"index":6,"name":"ICOMP","description":"An integer greater than or equal to one and less than or equal to MXCONS as defined on the WELLDIMS keyword in the RUNSPEC section, that defines the completion number of the currently defined perforation interval (connection interval). If defaulted with 1*, then ICOMP is set equal to one.","units":{},"default":"1","value_type":"INT"},{"index":7,"name":"STATUS","description":"A defined character string of length four that defines the connections’ operational status within the perforation interval, STATUS should be set to one of the following character strings: OPEN: the connections are open to flow. SHUT: the connections are closed to flow (shut-in). AUTO: the connection are initially closed, but may be opened automatically if an economic limit is violated. Currently this option is not supported by OPM Flow.","units":{},"default":"OPEN","value_type":"STRING","options":["OPEN","SHUT","AUTO"]},{"index":8,"name":"SATNUM","description":"An integer greater than or equal to zero and less than NTSFUN as declared on the TABDIMS keyword in the RUNSPEC, that defines the saturation table number to be used for flow between the reservoir grid block and the well connections. If SATNUM is set to zero or defaulted with 1* then: The saturation table allocated to the grid block that the connections are located within are used. If the hysteresis option has been activated via the HYSTER variable on the SATOPTS keyword in the RUNSPEC section, then both the imbibition and drainage saturation tables allocated to the grid block that the connections are located within are used. The imbibition table allocation can be changed by the COMPIMB keyword in the RUNSPEC section, provided it is entered after the COMPTRAJ keyword.","units":{},"default":"0","value_type":"INT"},{"index":9,"name":"CONFACT","description":"A real value greater than or equal to zero that defines the transmissibility connection factor between the well bore and the reservoir grid block. If set to zero or defaulted with 1* then items (10) through (13) are used to calculate CONFACT.","units":{"field":"cP.rb/day/psia 0","metric":"cP.rm3/day/bars 0","laboratory":"cP.rcc/hr/atm 0"},"default":"Defined","value_type":"DOUBLE","dimension":"Viscosity*ReservoirVolume/Time*Pressure"},{"index":10,"name":"DW","description":"A real positive value that defines the well bore diameter of the connections for the well. DW is used in calculating a well’s productivity or injectivity index; however the value will be ignored in calculating the connections CONFACT value if CONFAC has been directly entered.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":"Length"},{"index":11,"name":"KH","description":"A real value that defines the effective KH (permeability x length) for the connections within the perforation interval. If less than or equal to zero, or defaulted by 1*, then KH is calculated from the connected grid blocks. KH is ignored if CONFACT has been directly entered.","units":{"field":"mD.ft","metric":"mD.m","laboratory":"mD.cm"},"default":"Calculated from connected grid blocks","value_type":"DOUBLE","dimension":"Permeability*Length"},{"index":12,"name":"SKIN","description":"A real value that defines the connections dimensionless skin factor. SKIN is used in calculating a well’s productivity or injectivity index; however, the value will be ignored in calculating the connections CONFACT value if CONFACT has been directly entered.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.0","value_type":"DOUBLE","dimension":"1"},{"index":13,"name":"DFACT","description":"A real value that defines the non-Darcy D factor coefficient for gas wells. This value should be defaulted with 1* and the non-Darcy D factor coefficient for gas wells defined via the WDFAC keyword in the SCHEDULE section. Currently this option is not supported by OPM Flow.","units":{"field":"day/Mscf","metric":"day/m3","laboratory":"hour/sc"},"default":"1*","value_type":"DOUBLE","dimension":"1"}],"example":"The following example defines two trajectory wells oil wells, OP01 and OP02, using the WELTRAJ keyword, together with their perforations using the COMPTRAJ keyword.\n--\n-- WELL SPECIFICATION DATA\n--\n-- WELL GROUP LOCATION BHP PHASE DRAIN INFLOW OPEN CROSS PVT\n-- NAME NAME I J DEPTH FLUID AREA EQUANS SHUT FLOW TABLE\nWELSPECS\nOP01 PLATFORM 1* 1* 1* OIL 1* STD SHUT NO 1* /\nOP02 PLATFORM 1* 1* 1* OIL 1* STD SHUT NO 1* /\n/\n--\n-- WELL TRAJECTORY DATA\n--\n-- WELL BRAN XCORD YCORD TVDSS MD\n-- NAME NO DEPTH DEPTH\n-- ----- ---- ------------ ------------ ------------ ------------\nWELTRAJ\nOP01 1* 2.805445e+06 3.602948e+06 -100.000000 0.0 /\nOP01 1* 2.805445e+06 3.602948e+06 877.0000000 977.0 /\nOP01 1* 2.805445e+06 3.602948e+06 957.9950240 1058.0 /\nOP01 1* 2.805444e+06 3.602946e+06 1051.976081 1152.0 /\n…………………... /\nOP02 1* 2.810828e+06 3.604507e+06 9371.792711 11418.0 /\nOP02 1* 2.810885e+06 3.604525e+06 9443.657000 11511.0 /\nOP02 1* 2.810952e+06 3.604546e+06 9531.966162 11624.0 /\nOP02 1* 2.810973e+06 3.604553e+06 9560.411742 11660.0 /\n/\n--\n--\n-- WELL TRAJECTORY CONNECTION DATA\n--\n-- WELL BRAN -- PERFORATION -- COMPL OPEN SAT CONN WELL KH SKIN D\n-- NAME NO. TOP BOT REF NO. SHUT TAB FACT DIA FACT FACT FACT\nCOMPTRAJ\nOP01 1* 8230 8244 MD 1 SHUT 1* 1* 0.708 1* 0.0 1* /\nOP01 1* 8352 8380 MD 1 SHUT 1* 1* 0.708 1* 0.0 1* /\nOP01 1* 9070 9100 MD 1 SHUT 1* 1* 0.708 1* 0.0 1* /\nOP01 1* 9220 9250 MD 2 SHUT 1* 1* 0.708 1* 0.0 1* /\nOP01 1* 9266 9280 MD 2 SHUT 1* 1* 0.708 1* 0.0 1* /\nOP01 1* 9693 9703 MD 3 SHUT 1* 1* 0.708 1* 0.0 1* /\nOP01 1* 9940 9974 MD 3 SHUT 1* 1* 0.708 1* 0.0 1* /\nOP02 1* 9979 9985 TVD 1* SHUT 1* 1* 0.708 1* 0.0 1* /\nOP02 1* 10173 10183 TVD 1* SHUT 1* 1* 0.708 1* 0.0 1* /\nOP02 1* 10190 10204 TVD 1* SHUT 1* 1* 0.708 1* 0.0 1* /\nOP02 1* 10327 10333 TVD 1* SHUT 1* 1* 0.708 1* 0.0 1* /\nOP02 1* 10339 10345 TVD 1* SHUT 1* 1* 0.708 1* 0.0 1* /\nOP02 1* 11528 11538 TVD 1* SHUT 1* 1* 0.708 1* 0.0 1* /\n/\nWell OP01 has eight perforation intervals, with the intervals one to three grouped into one completion, perforation intervals four to five grouped into completion number two, and finally the bottom three perforations are grouped into completion number three. In contrast, OP02 has six perforated intervals with their completion interval defaulted to one.\n| Note This is an OPM Flow specific keyword and will therefore cause an error in the commercial simulator. |\n|----------------------------------------------------------------------------------------------------------|\n| Note The term well connection is used to describe individual connections from the wellbore to the reservoir grid, as opposed to well completions. A well completion is used to describe a set of connections, for example, a well may consist of several completions with each completion consisting of multiple connections. For wells defined using the WELTRAJ and COMPTRAJ keywords, the WELTRAJ keyword defines the trajectory of the well within the model, and the COMPTRAJ defines the perforation intervals in the well. A perforation interval will automatically generate various well connections to the grid, and in addition multiple perforation intervals may be grouped into a completion. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":13,"size_kind":"list"},"COMPVE":{"name":"COMPVE","sections":["SCHEDULE"],"supported":false,"summary":"The COMPVE keyword is used to re-define the well connection depths in the global grid.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"I","description":"","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"J","description":"","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"K_UPPER","description":"","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"K_LOWER","description":"","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"SAT_TABLE_NUM","description":"","units":{},"default":"","value_type":"INT"},{"index":7,"name":"CVEFRAC","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":8,"name":"DTOP","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":9,"name":"DBOT","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":10,"name":"FLAG","description":"","units":{},"default":"NO","value_type":"STRING"},{"index":11,"name":"S_D","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":12,"name":"GTOP","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":13,"name":"GBOT","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"}],"example":"","expected_columns":13,"size_kind":"list"},"COMPVEL":{"name":"COMPVEL","sections":["SCHEDULE"],"supported":false,"summary":"The COMPVEL keyword is used to re-define the well connection depths in a Local Grid Refinement (“LGR”) grid.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"LOCAL","description":"","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"I","description":"","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"J","description":"","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"K_UPPER","description":"","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"K_LOWER","description":"","units":{},"default":"0","value_type":"INT"},{"index":7,"name":"SAT_TABLE_NUM","description":"","units":{},"default":"","value_type":"INT"},{"index":8,"name":"CVEFRAC","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":9,"name":"DTOP","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":10,"name":"DBOT","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":11,"name":"FLAG","description":"","units":{},"default":"NO","value_type":"STRING"},{"index":12,"name":"S_D","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":13,"name":"GTOP","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":14,"name":"GBOT","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"}],"example":"","expected_columns":14,"size_kind":"list"},"CPIFACT":{"name":"CPIFACT","sections":["SCHEDULE"],"supported":false,"summary":"The CPIFACT keyword is used to define well connection transmissibility multipliers for well connections to the global grid.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"MULT","description":"","units":{},"default":"","value_type":"UDA"},{"index":3,"name":"I","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"J","description":"","units":{},"default":"","value_type":"INT"},{"index":5,"name":"K","description":"","units":{},"default":"","value_type":"INT"},{"index":6,"name":"C1","description":"","units":{},"default":"","value_type":"INT"},{"index":7,"name":"C2","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":7,"size_kind":"list"},"CPIFACTL":{"name":"CPIFACTL","sections":["SCHEDULE"],"supported":false,"summary":"The CPIFACT keyword is used to define well Local Grid Refinement (“LGR”) connection transmissibility multipliers for well connections to a LGR, for when the LGR option has been invoked by the LGR keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"MULT","description":"","units":{},"default":"","value_type":"UDA"},{"index":3,"name":"LGR","description":"","units":{},"default":"","value_type":"STRING"},{"index":4,"name":"I","description":"","units":{},"default":"","value_type":"INT"},{"index":5,"name":"J","description":"","units":{},"default":"","value_type":"INT"},{"index":6,"name":"K","description":"","units":{},"default":"","value_type":"INT"},{"index":7,"name":"C1","description":"","units":{},"default":"","value_type":"INT"},{"index":8,"name":"C2","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":8,"size_kind":"list"},"CSKIN":{"name":"CSKIN","sections":["SCHEDULE"],"supported":null,"summary":"This keyword, CSKIN, is used to re-define a well’s connection skin factors and as such will result in the well’s connection transmissibility factors being updated accordingly. The well connections must already be defined using the COMPDAT keyword in the SCHEDULE section before this keyword can be used.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well connection skin is being re-defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"I","description":"A positive integer greater than or equal to one and less than or equal to NX that defines the connection location in the I-direction. If set to zero or defaulted with 1* then connections in any I-direction location will be modified.","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"J","description":"A positive integer greater than or equal to one and less than or equal to NY that defines the connection location in the J-direction. If set to zero or defaulted with 1* then connections in any J-direction location will be modified.","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"K1","description":"A positive integer greater than or equal to one and less than or equal to K2 and NZ that defines the UPPER connection location in the K-direction. If set to zero or defaulted with 1* then this will be taken from the top connection of the well.","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"K2","description":"A positive integer greater than or equal to K1 and less than or equal to NZ that defines the LOWER connection location in the K-direction. If set to zero or defaulted with 1* then this will be taken from the bottom connection of the well.","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"SKIN","description":"A real value that defines the connections’ dimensionless skin factors.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.0","value_type":"DOUBLE","dimension":"1"}],"example":"The following example re-defines the skin factor for all well OP01 connections in layers 4 to 6.\n--\n-- CONNECTION SKIN DATA\n--\n-- WELL --- LOCATION --- SKIN\n-- NAME II JJ K1 K2 FACT\nCSKIN\nOP01 1* 1* 4 6 2.0 /\n/","expected_columns":6,"size_kind":"list"},"DATES":{"name":"DATES","sections":["SCHEDULE"],"supported":null,"summary":"This keyword advances the simulation to a given report date after which additional keywords may be entered to instruct OPM Flow to perform additional functions via the SCHEDULE section keywords, or further DATES data sets or keywords may be entered to advance the simulator to the next report date.","parameters":[{"index":1,"name":"DAY","description":"A positive integer that defines the day of the month for the data set, the value should be greater than or equal to one and less than or equal to 31.","units":{},"default":"None","value_type":"INT"},{"index":2,"name":"MONTH","description":"Character string for the month for the data set and should be one of the following 'JAN', 'FEB', 'MAR', 'APR', 'MAY', 'JUN', 'JUL' (or 'JLY'), 'AUG', 'SEP', 'OCT', 'NOV', or 'DEC'","units":{},"default":"None","value_type":"STRING"},{"index":3,"name":"YEAR","description":"A positive four digit integer value representing the year for the data set, which must be specified fully by four digits, that is 1986.","units":{},"default":"None","value_type":"INT"},{"index":4,"name":"TIME","description":"A numeric character string that defines the time for the data set in the form of: HH:MM:SS.SSSS The default value means in most cases this parameter can be defaulted. TIME is normally used when detailed DST matching is performed to enable the pressures and rates to be stated at specific dates and times.","units":{},"default":"00:00:00","value_type":"STRING"}],"example":"Given a start date of January 1, 2020 set via the START keyword in the RUNSPEC section, the following example advances the simulator from the start date of January 1, 2020 to January 1, 2021, using quarterly reporting time steps.\n-- ==============================================================================\n--\n-- SCHEDULE SECTION\n--\n-- ==============================================================================\nSCHEDULE\n-- ------------------------------------------------------------------------------\n-- SCHEDULE SECTION - 2020-01-01\n-- ------------------------------------------------------------------------------\nRPTSCHED\n'WELLS=2' 'WELSPECS' 'CPU=2' FIP=2' /\nDATES\n2 JAN 2020 /\n/\nRPTSCHED\n'NOTHING' /\nDATES\n1 APR 2020 /\n1 JLY 2020 /\n1 OCT 2020 /\n/\n-- ------------------------------------------------------------------------------\n-- SCHEDULE SECTION - 2021-01-01\n-- ------------------------------------------------------------------------------\nRPTSCHED\n'WELLS=2' 'WELSPECS' 'CPU=2' FIP=2' /\nDATES\n1 JAN 2021 /\n/\nRPTSCHED\n'NOTHING' /\nDATES\n1 APR 2021 /\n1 JLY 2021 /\n1 OCT 2021 /\n/\nThe above example writes out a series of report at the start of the run and then advances the simulation one day to January 2, 2020 and switches off the reporting. The simulation then advances to April 1, July 1 and October 1, 2020 with no further changes to the run. After October 1, 2020 reporting is switched on again to enable a report on January 1, 2021, which is then subsequently switched off after the January 1, 2021 report time step has been completed.\nNote if one wishes to terminate the run at the end of year (as opposes to the beginning of the year and get a final report for the year, then the next example demonstrates the keyword sequence to enable this.\n-- ------------------------------------------------------------------------------\n-- SCHEDULE SECTION - 2021-01-01\n-- ------------------------------------------------------------------------------\nRPTSCHED\n'WELLS=2' 'WELSPECS' 'CPU=2' FIP=2' /\nDATES\n2 JAN 2021 /\n/\nRPTSCHED\n'NOTHING' /\nDATES\n1 FEB 2021 /\n1 MAR 2021 /\n1 APR 2021 /\n1 MAY 2021 /\n1 JUN 2021 /\n1 JLY 2021 /\n1 AUG 2021 /\n1 SEP 2021 /\n1 OCT 2021 /\n1 NOV 2021 /\n1 DEC 2021 /\n/\n--\n-- FINAL REPORT AND RESTART AT YEAR END\n--\nRPTSCHED\n'WELLS=2' 'WELSPECS' 'CPU=2' FIP=2' /\nRPTRST\n'BASIC=2' /\nDATES\n31 DEC 2021 /\n/\nIn the above example monthly reporting time steps have been used instead of quarterly and report is requested after the December 1, 2021 time step and is therefore written out on December 31, 2021.","expected_columns":4,"size_kind":"list"},"DCQDEFN":{"name":"DCQDEFN","sections":["SCHEDULE"],"supported":false,"summary":"The DCQDEFN keyword defines the DCQ units to be rate or energy (calorific value) when using the Gas Field Operation model and the Gas Calorific Value control option. The gas DCQ rates are controlled by the GASYEAR, GASPERIO, GDCQ, GASFTARG or GASFDECR keywords in the SCHEDULE section.","parameters":[{"index":1,"name":"QUANTITY","description":"","units":{},"default":"GAS","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"DELAYACT":{"name":"DELAYACT","sections":["SCHEDULE"],"supported":false,"summary":"The DELAYACT keyword defines a series of keywords that should be executed after an ACTION keyword has been triggered by the ACTION, ACTIONG, ACTIONR, ACTIONW, ACTIONS, or ACTIONX keywords.","parameters":[{"index":1,"name":"ACTION_NAME","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"ACTION_TRIGGER","description":"","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"DELAY","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Time"},{"index":4,"name":"NUM_TIMES","description":"","units":{},"default":"1","value_type":"INT"},{"index":5,"name":"INCREMENT","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Time"}],"example":"","expected_columns":5,"size_kind":"fixed","size_count":1},"DIMPES":{"name":"DIMPES","sections":["SCHEDULE"],"supported":null,"summary":"This keyword, DIMPES, defines the Implicit in Pressure Explicit Saturation (“IMPES”) dynamic solution parameters and results in the simulator switching from the current solution formulation to the IMPES formulation. OPM Flow uses a different numerical scheme which makes this keyword redundant; hence, OPM Flow ignores this keyword. It is documented here for completeness.","parameters":[{"index":1,"name":"DSTARG","description":"","units":{},"default":"0.05","value_type":"DOUBLE","dimension":"1"},{"index":2,"name":"DSMAX","description":"","units":{},"default":"0.1","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"DPMAX","description":"","units":{},"default":"13.79","value_type":"DOUBLE","dimension":"Pressure"}],"example":"--\n-- ACTIVATE THE IMPES SOLUTION OPTION\n--\nDIMPES\nThe above example switches on the IMPES solution option; however, this has no effect in OPM Flow input decks.","expected_columns":3,"size_kind":"fixed","size_count":1},"DIMPLICT":{"name":"DIMPLICT","sections":["SCHEDULE"],"supported":null,"summary":"This keyword, DIMPLICT, activates the Fully Implicit Formulation and results in the simulator switching from the current solution formulation to the fully implicit formulation. OPM Flow uses a different numerical scheme which makes this keyword redundant; hence, OPM Flow ignores this keyword. It is documented here for completeness.","parameters":[],"example":"--\n-- ACTIVATES THE FULLY IMPLICIT SOLUTION OPTION\n--\nDIMPLICT\nThe above example switches on the fully implicit solution option; however, this has no effect in OPM Flow input decks.","size_kind":"none","size_count":0},"DRILPRI":{"name":"DRILPRI","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, DRILPRI, defines the prioritized drilling queue priority parameters used in the priority formulae for this type of drilling queue.","parameters":[{"index":1,"name":"INTERVAL","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Time"},{"index":2,"name":"A","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":3,"name":"B","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":4,"name":"C","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":5,"name":"D","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":6,"name":"E","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":7,"name":"F","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":8,"name":"G","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":9,"name":"H","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":10,"name":"LOOK_AHEAD","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Time"},{"index":11,"name":"CALCULATION","description":"","units":{},"default":"SINGLE","value_type":"STRING"}],"example":"","expected_columns":11,"size_kind":"fixed","size_count":1},"DRSDT":{"name":"DRSDT","sections":["SCHEDULE"],"supported":null,"summary":"DRSDT defines the maximum rate at which the solution gas-oil ratio (Rs) can be increased in a grid cell. The keyword is similar in functionality to the DRSDTR keyword, that defines the maximum rate at which Rs can be increased in a grid cell by region. Both keywords should only be used if the OIL, GAS, and DISGAS keywords in the RUNSPEC section have been invoked to allow oil, gas and dissolved gas to be present in the model. The keyword only affects the behavior of an increasing Rs, for example when gas is being injected into an oil reservoir, and is subject to the availability of free gas and the ability of the undersaturated oil to adsorb this gas.","parameters":[{"index":1,"name":"DRSDT1","description":"DRSDT1 is a real positive number that defines the maximum rate at which the solution gas-oil ratio is allowed to increase in a grid cell, that is the maximum rate the gas can dissolve into the available undersaturated oil. A value of zero means that Rs cannot increase and free gas cannot dissolve into the unsaturated oil in a grid cell. Alternatively a very large value of DRSDT1 allows Rs to increase rapidly until there is no free gas or the oil within the grid block is fully saturated. Note if the keyword is not present in the input deck then DRSDT1 is assumed to be a very large number resulting in complete re-solution of the gas into the available undersaturated oil.","units":{"field":"Mscf/stb/d","metric":"sm3/sm3/day","laboratory":"scc/scc/day"},"default":"None","value_type":"DOUBLE","dimension":"GasDissolutionFactor/Time"},{"index":2,"name":"DRSDT2","description":"DRSDT2 is a defined character string that defines whether the DRSDT1 is applied to either all grid blocks or just those grid blocks containing free gas: ALL: means the DRSDT1 maximum rate at which Rs is allowed to increase in a grid cell is applied to all grid blocks. FREE: means the DRSDT1 maximum rate at which Rs is allowed to increase in a grid cell is applied to grid blocks only containing free gas. Note if the keyword is not present in the input deck then DRSDT2 is set to the default value of ALL.","units":{},"default":"ALL","value_type":"STRING","options":["ALL","FREE"]}],"example":"The first example prevents the solution gas-oil ratio from increasing and applies this to all grid cells.\n--\n-- SOLUTION GAS (RS) MAXIMUM RATE OF INCREASE FOR MODEL --\nDRSDT\n-- MAX RS ALL/FREE\n-- DRSDT1 DRSDT2\n-- ------- --------\n0.000 ALL /\nAnd the second example below applies 0.0005 Mscf/stb/d as the maximum rate at which the solution gas-oil ratio is allowed to increase in a grid cell, and applies this to only cells containing free gas.\n--\n-- SOLUTION GAS (RS) MAXIMUM RATE OF INCREASE FOR MODEL --\nDRSDT\n-- MAX RS ALL/FREE\n-- DRSDT1 DRSDT2\n-- ------- --------\n0.0005 FREE /\nAgain, the keyword parameters when applied are subject to the availability of free gas and the ability of the undersaturated oil to adsorb this gas.","expected_columns":2,"size_kind":"fixed","size_count":1},"DRSDTCON":{"name":"DRSDTCON","sections":["SCHEDULE"],"supported":null,"summary":"The DRSDTCON keyword defines the parameters that control the convective dissolution of carbon dioxide (CO2) into the in-situ brine within a grid cell, as described by Mykkeltvedt et al.1\n Mykkeltvedt, T.S., Sandve, T.H. & Gasda, S.E. New Sub-grid Model for Convective Mixing in Field-Scale CO2 Storage Simulation. Transp Porous Med 152, 9 (2025). https://doi.org/10.1007/s11242-024-02141-5, based on an assumption of vertical equilibrium. The keyword internally causes the simulator to calculate the solution gas-oil ratio (Rs), normally controlled by the DRSDT1 parameter on the DRSDT keyword in the SCHEDULE section, making the DRSDT keyword redundant.","parameters":[{"index":1,"name":"CHI","description":"A real positive value () that defines the proportionality constant related to the maximum rate of increase of CO2 solution gas-oil ratio (Rs) in the Linear regime. A value of zero means that convective dissolution of CO2 into in-situ brine does not occur and free CO2 cannot dissolve into the brine. Alternatively, a non-zero value of CHI allows convective dissolution of CO2. Note if the CO2STORE keyword is present but the DRSDTCON keyword is absent from the input deck, then this results in instantaneous dissolution of CO2 into the available undersaturated in-situ brine.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.04","value_type":"DOUBLE","dimension":"1"},{"index":1,"name":"PSI","description":"A real positive value () that defines the normalised CO2 solution gas-oil ratio ([tilde X]) at the transition between the Linear and the Steady-State regimes.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.34","value_type":"DOUBLE","dimension":"1"},{"index":1,"name":"OMEGA","description":"A real positive value () that defines the maximum rate of increase in CO2 solution gas-oil ratio (Rs) in the Steady-State regime.","units":{"field":"1/s","metric":"1/s","laboratory":"1/s"},"default":"3.0e-9","value_type":"DOUBLE","dimension":"1"},{"index":1,"name":"OPTION","description":"A defined character string that specifies in which cells the convective dissolution rate limit is applied, and should be set to one of the following character strings: ALL: the limit is applied to all cells. FREE: the limit is only applied to cells with free gas.","units":{},"default":"ALL","value_type":"DOUBLE","dimension":"1"},{"index":2,"name":"PSI","description":"","units":{},"default":"0.34","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"OMEGA","description":"","units":{},"default":"3e-09","value_type":"DOUBLE","dimension":"1"},{"index":4,"name":"OPTION","description":"","units":{},"default":"ALL","value_type":"STRING"}],"example":"The example below is similar to that shown under the CO2STORE keyword in the RUNSPEC section. In the RUNSPEC section one declares that the carbon dioxide storage model is active for the run to account for both carbon dioxide and water phase solubility using OPM Flow’s CO2-Brine PVT model.\n-- ==============================================================================\n--\n-- RUNSPEC SECTION\n--\n-- ==============================================================================\nRUNSPEC\n-- ------------------------------------------------------------------------------\n-- FLUID TYPES AND TRACER OPTIONS\n-- ------------------------------------------------------------------------------\n--\n-- ACTIVATE CO2 STORAGE IN THE MODEL (OPM FLOW CO2 STORAGE KEYWORD)\n--\nCO2STORE\n--\n-- ACTIVATE GAS-WATER THE MODEL (OPM FLOW KEYWORD)\n--\nGASWAT\n--\n-- DISSOLVED GAS IN WATER IS PRESENT IN THE RUN (OPM FLOW KEYWORD)\n--\nDISGASW\n--\n-- VAPORIZED WATER IN DRY/WET GAS IS PRESENT IN THE RUN (OPM FLOW KEYWORD)\n--\nVAPWAT\nThe second part of the example sets the maximum dissolution rate for convective CO2 mixing via the DRSDTCON keyword in the SCHEDULE section using the base case parameters calculated by Mykkeltvedt et al from fine-scale simulations.\n-- ==============================================================================\n--\n-- SCHEDULE SECTION\n--\n-- ==============================================================================\nSCHEDULE\n--\n-- CO2 CONVECTIVE DISSOLUTION PARAMETERS\n--\nDRSDTCON\n-- CHI PSI OMEGA OPTION\n0.04 0.34 3.0E-09 ALL /\nSee also the CO2STORE keyword in the RUNSPEC section for further information on OPM Flow’s CO2 storage facility.\n| [R_s``>``R_{s,sat} S_o] | (12.3.53.1) |\n|-------------------------|-------------|\n| [F_lin\n``=`` %chi left({ R_{s,sat} K_z %DELTA %rho_c g } over {%mu_o S_o`D_z%phi}right )] | (12.3.53.2) |\n|--------------------------------------------------------------------------------------------|-------------|\n| [tilde X ``=`` {R_s - R_{s,sat} S_g} over {R_{s,sat} (1-S_g)}] | (12.3.53.3) |\n|----------------------------------------------------------------|-------------|\n| Note In the commercial simulator a constant or regional value for DRSDT can be given as an input parameter. This can be used to include the effect of convective mixing as shown by Thibeau and Dutin5\n Thibeau, S., & Dutin, A. (2011). Large scale CO2 storage in unstructured aquifers: Modeling study of the ultimate CO2 migration distance. Energy Procedia, 4, 4230-4237.. Thibeau, S., & Dutin, A. (2011). Large scale CO2 storage in unstructured aquifers: Modeling study of the ultimate CO2 migration distance. Energy Procedia, 4, 4230-4237. OPM Flow’s approach differs from this in that the DRSDT value is computed internally and is dependent on both the static and dynamic cell properties. |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":4,"size_kind":"fixed"},"DRSDTR":{"name":"DRSDTR","sections":["SCHEDULE"],"supported":false,"summary":"DRSDTR defines the maximum rate at which the solution gas-oil ratio (Rs) can be increased in a grid cell for various regions in the model. The keyword is similar in functionality to the DRSDT keyword, that defines the maximum rate at which Rs can be increased in a grid cell for all cells in the model. The number of DRSDTR vector data sets is defined by the NTPVT parameter on the TABDIMS keyword in the RUNSPEC section and the allocation of the DRSDTR records to different grid blocks in the model is done via the PVTNUM keyword in the REGION section. One data set consists of one record or line which is terminated by a “/”.","parameters":[{"index":1,"name":"DRSDT1","description":"DRSDT1 is a real positive number that defines the maximum rate at which the solution gas-oil ratio is allowed to increase in a grid cell, that is the maximum rate the gas can dissolve into the available undersaturated oil. A value of zero means that Rs cannot increase and free gas cannot dissolve into the unsaturated oil in a grid cell. Alternatively a very large value of DRSDT1 allows Rs to increase rapidly until there is no free gas or the oil within the grid block is fully saturated. Note if the keyword is not present in the input deck then DRSDT1 is assumed to be a very large number resulting in complete re-solution of the gas into the available undersaturated oil.","units":{"field":"Mscf/stb/d","metric":"sm3/sm3/day","laboratory":"scc/scc/day"},"default":"None","value_type":"DOUBLE","dimension":"GasDissolutionFactor/Time"},{"index":2,"name":"DRSDT2","description":"DRSDT2 is a defined character string that defines whether the DRSDT1 is applied to either all grid blocks or just those grid blocks containing free gas: ALL: means the DRSDT1 maximum rate at which Rs is allowed to increase in a grid cell is applied to all grid blocks. FREE: means the DRSDT1 maximum rate at which Rs is allowed to increase in a grid cell is applied to grid blocks only containing free gas. Note if the keyword is not present in the input deck then DRSDT2 is set to the default value of ALL.","units":{},"default":"ALL","value_type":"STRING","options":["ALL","FREE"]}],"example":"The first example prevents the solution gas-oil ratio from increasing and applies this to all regions for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set to three.\n--\n-- SOLUTION GAS (RS) MAXIMUM RATE OF INCREASE BY REGION --\nDRSDTR\n-- MAX RS ALL/FREE\n-- DRSDT1 DRSDT2\n-- ------- --------\n0.0000 ALL /\n0.0000 ALL /\n0.0000 ALL /\nThe second example below prevents the solution gas-oil ratio from increasing and applies this to all grid cells in PVTNUM region one. For PVTNUM regions one and two the keyword applies 0.0005 Mscf/stb/d as the maximum rate at which the solution gas-oil ratio is allowed to increase in a grid cell, and applies this to only cells containing free gas.\n--\n-- SOLUTION GAS (RS) MAXIMUM RATE OF INCREASE BY REGION --\nDRSDTR\n-- MAX RS ALL/FREE\n-- DRSDT1 DRSDT2\n-- ------- --------\n0.0000 ALL /\n0.0005 FREE /\n0.0005 FREE /\nAgain, the keyword parameters when applied are subject to the availability of free gas and the ability of the undersaturated oil to adsorb this gas.","expected_columns":2,"size_kind":"fixed"},"DRVDT":{"name":"DRVDT","sections":["SCHEDULE"],"supported":null,"summary":"DRVDT defines the maximum rate at which the vaporized oil-gas ratio or condensate-gas ratio (Rv) can be increased in a grid cell. The keyword is similar in functionality to the DRVDTR keyword, that defines the maximum rate at which Rv can be increased in a grid cell by region. Both keywords should only be used if the OIL, GAS, and VAPOIL (condensate) keywords in the RUNSPEC section have been invoked to allow oil, gas and condensate to be present in the model. The keyword only affects the behavior of an increasing Rv, for example when gas is being injected into a gas condensate reservoir as part of as gas re-cycling scheme, and is subject to the availability of free oil (condensate) and the ability of the undersaturated gas to adsorb this condensate.","parameters":[{"index":1,"name":"DRVDT1","description":"DRVDT1 is a real positive number that defines the maximum rate at which the vaporized oil-gas ratio is allowed to increase in a grid cell, that is the maximum rate at which the oil can dissolve into the available undersaturated gas. A value of zero means that Rv cannot increase and free oil cannot vaporize into the unsaturated gas in a grid cell. Alternatively a very large value of DRVDT1 allows Rv to increase rapidly until there is no free oil or the gas within the grid block is fully saturated. Note if the keyword is not present in the input deck then DRVDT1 is assumed to be a very large number resulting in complete re-vaporization of the oil into the available undersaturated gas.","units":{"field":"stb/Mscf/d","metric":"sm3/sm3/day","laboratory":"scc/scc/day"},"default":"None","value_type":"DOUBLE","dimension":"OilDissolutionFactor/Time"}],"example":"The example prevents the solution oil-gas ratio from increasing.\n--\n-- VAPORIZED OIL (RV) MAXIMUM RATE OF INCREASE FOR MODEL --\nDRVDT\n-- MAX RV\n-- DRVDT1\n-- -------\n0.000 /\nAgain, the keyword parameters when applied are subject to the availability of free oil and the ability of the undersaturated gas to adsorb this oil.","expected_columns":1,"size_kind":"fixed","size_count":1},"DRVDTR":{"name":"DRVDTR","sections":["SCHEDULE"],"supported":null,"summary":"DRVDTR defines the maximum rate at which the vaporized oil-gas ratio or condensate-gas ratio (Rv) can be increased in a grid cell for various regions in the model. The keyword is similar in functionality to the DRVDT keyword, that defines the maximum rate at which Rv can be increased in a grid cell for all cells in the model. The number of DRVDTR vector data sets is defined by the NTPVT parameter on the TABDIMS keyword in the RUNSPEC section and the allocation of the DRVDTR records to different grid blocks in the model is done via the PVTNUM keyword in the REGION section. One data set consists of one record or line which is terminated by a “/”.","parameters":[{"index":1,"name":"DRVDT1","description":"DRVDT1 is a real positive number that defines the maximum rate at which the vaporized oil-gas ratio is allowed to increase in a grid cell, that is the maximum rate at which the oil can vaporize into the available undersaturated gas. A value of zero means that Rv cannot increase and free oil cannot vaporize into the unsaturated gas in a grid cell. Alternatively a very large value of DRVDT1 allows Rv to increase rapidly until there is no free oil or the gas within the grid block is fully saturated. Note if the keyword is not present in the input deck then DRVDT1 is assumed to be a very large number resulting in complete re-vaporization of the oil into the available undersaturated gas.","units":{"field":"stb/Mscf/d","metric":"sm3/sm3/day","laboratory":"scc/scc/day"},"default":"None","value_type":"DOUBLE","dimension":"OilDissolutionFactor/Time"}],"example":"The first example prevents the vaporized oil-gas ratio from increasing and applies this to all regions for when NTPVT on the TABDIMS keyword in the RUNSPEC section is set to three.\n--\n-- VAPORIZED OIL (RV) MAXIMUM RATE OF INCREASE PARAMETERS BY REGION\n--\nDRVDTR\n-- MAX RV\n-- DRVDT1\n-- ------- -\n0.000 /\n0.000 /\n0.000 /\nThe second example below prevents the vaporized oil-gas ratio from increasing and applies this to all grid cells in PVTNUM region one. For PVTNUM regions one and two the keyword applies 0.005 stb//Mscf/d as the maximum rate at which the vaporized oil-gas ratio is allowed to increase in a grid cell,\n--\n-- VAPORIZED OIL (RV) MAXIMUM RATE OF INCREASE PARAMETERS BY REGION\n--\nDRVDTR\n-- MAX RV\n-- DRVDT1\n-- -------\n0.0000 /\n0.0005 /\n0.0005 /\nAgain, the keyword parameters when applied are subject to the availability of free oil and the ability of the undersaturated gas to adsorb this oil.","expected_columns":1,"size_kind":"fixed"},"DUMPCUPL":{"name":"DUMPCUPL","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, DUMPCUPL, activates output to the Reservoir Coupling file from the reservoir coupling file in the master run for when reservoir coupling is invoked by the GRUPMAST and SLAVES keywords in the SCHEDULE section.","parameters":[{"index":1,"name":"VALUE","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"ENDACTIO":{"name":"ENDACTIO","sections":["SCHEDULE"],"supported":null,"summary":"The ENDACTIO keyword defines the end of a series of conditions that invoke run time processing of the ACTION series of keywords, namely: ACTION, ACTIONG, ACTIONR, ACTIONS, ACTIONW and ACTIONX. Only the ACTIONX keyword is implemented in OPM Flow as this keyword implements the ACTION, ACTIONG, ACTIONR, ACTIONS, ACTIONW functionality with greater flexibility. See the ACTIONX keyword in the SCHEDULE section for a full description of the ACTION facility.","parameters":[],"example":"The example shows the use of the ACTIONX and ENDACTIO keywords to test if the field’s gas production rate is less than 600 MMscf/d after 2020 and to open up additional wells if this occurs.\n--\n-- START OF ACTIONX FIELD PHASE-2 DEVELOPMENT DEFINITION\n--\nACTIONX\nPHASE2 1 /\nGGPR 'FIELD' < 600E3 AND /\nYEAR > 2020 /\n/\n-- WELL PRODUCTION STATUS\n--\n-- WELL WELL --LOCATION-- COMPLETION\n-- NAME STAT I J K FIRST LAST\nWELOPEN\nGP10 OPEN /\nGP11 OPEN /\n/\n--\n-- END OF ACTIONX FIELD PHASE-2 DEVELOPMENT DEFINITION\n--\nENDACTIO","size_kind":"none","size_count":0},"EXCAVATE":{"name":"EXCAVATE","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, EXCAVATE, sets the status of global and LGR grid blocks to active or excavate. Excavated grid blocks have all the transmissibilities set to zero thus disabling flow between the surrounding grid blocks.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"INT"}],"example":"","size_kind":"fixed","size_count":1,"variadic_record":true},"EXIT":{"name":"EXIT","sections":["SCHEDULE"],"supported":null,"summary":"The EXIT keyword is part of OPM Flow’s ACTION facility that allows for terminating the simulation for when a condition within an ACTIONX definition is satisfied. Invoking the keyword within an ACTIONX definition will result in the simulation terminating with an exit status code. The ACTION facility allows the user to enter computational logic to the simulation run based on the how the simulation run is proceeding – see the ACTIONX keyword in the SCHEDULE section.","parameters":[{"index":1,"name":"EXITCODE","description":"An optional integer that sets the exit code printed to the *.PRT file, if not not defined the default value of zero will be used.","units":{},"default":"0","value_type":"INT"}],"example":"The first example uses the ACTIONX keyword to define a condition for when the Field Oil Production Rate (“FOPR) falls below 1,000 stb/d (or 1,000 m3) using the default value for the EXITCODE.\n--\n-- DEFINE START OF ACTIONX SECTION\n--\nACTIONX\n'CHECK_FOPR' 100000 /\nFOPR < 1000 /\n/\n--\n-- TERMINATE AND EXIT SIMULATION\n--\nEXIT\n/\nENDACTIO\nThe next example terminates the simulation with EXITCODE one when the Field Pressure (“FPR”) falls below 200 psia (or 200 barsa).\n--\n-- DEFINE START OF ACTIONX SECTION\n--\nACTIONX\n'CHECK_FPR' 100000 /\nFPR < 200 /\n/\n--\n-- TERMINATE AND EXIT SIMULATION\n--\nEXIT\n1 /\nENDACTIO\nNote is is probably good practice to always set the EXITCODE to be able to identify the reason for the simulation stopping.\n| Note This is an OPM Flow specific keyword for the simulator’s ACTION facility and will therefore cause an error if used in the commercial simulator. |\n|------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":1,"size_kind":"fixed","size_count":1},"FBHPDEF":{"name":"FBHPDEF","sections":["SCHEDULE"],"supported":null,"summary":"This keyword, FBHPDEF, defines the default well BHP target for production wells and the default BHP constraint for injection wells.","parameters":[{"index":1,"name":"TARGET_BHP","description":"A real positive value that defines the default well BHP target for production wells.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1.01325 barsa","value_type":"DOUBLE","dimension":"Pressure"},{"index":2,"name":"LIMIT_BHP","description":"A real positive value that defines the default well BHP limit for injection wells.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"6895 barsa","value_type":"DOUBLE","dimension":"Pressure"}],"example":"The following examples sets the default BHP target for production wells to 1.01325, and the default BHP limit for injection wells to 6895:\n--\n-- DEFAULT BHP TARGET AND CONSTRAINTS\n--\nFBHPDEF\n1.01325 6895. /","expected_columns":2,"size_kind":"fixed","size_count":1},"GASBEGIN":{"name":"GASBEGIN","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, GASBEGIN, defines the start of an Annual Scheduling section set of keywords used when the Gas Field Operations option has been activated by the GASFIELD keyword in the RUNSPEC section. An Annual Scheduling section starts with the GASBEGIN keyword and is terminated by the GASEND keyword, with keywords in between used to control and write reports at selected times between the start and end of a contract period. Only one Annual Scheduling section is activate at a time, that is, a subsequent Annual Scheduling section overwrites the previous set of entries. To clear the current Annual Schedule section enter the GASBEGIN keyword followed by the GASEND keyword word with no other keywords in between.","parameters":[],"example":"","size_kind":"none","size_count":0},"GASEND":{"name":"GASEND","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, GASEND, defines the end of an Annual Scheduling section set of keywords used when the Gas Field Operations option has been activated by the GASFIELD keyword in the RUNSPEC section. An Annual Scheduling section starts with the GASBEGIN keyword and is terminated by the GASEND keyword, with keywords in between used to control and write reports at selected times between the start and end of a contract period. Only one Annual Scheduling section is activate at a time, that is, a subsequent Annual Scheduling section overwrites the previous set of entries. To clear the current Annual Schedule section enter the GASBEGIN keyword followed by the GASEND keyword word with no other keywords in between.","parameters":[],"example":"","size_kind":"none","size_count":0},"GASFCOMP":{"name":"GASFCOMP","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, GASFCOMP, defines automatic gas compressors for when the Gas Field Operations option has been activated by the GASFIELD keyword in the RUNSPEC section and the Standard Network option has been specified by the GRUPTREE, GRUPNET and GNETINJE series of keywords in the SCHEDULE section. Automatic gas compressors are automatically switch on for a group if a group’s gas production target cannot be satisfied. In addition, if a group’s gas target is reduced then the automatic compressors are initially switch off to test that the reduced gas rate target can be met without compression, if not, compression is switched back on. Note that all automatic compressors are “switch on” when calculating a field’s gas deliverability.","parameters":[{"index":1,"name":"GROUP","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"VFP_TABLE_NUM","description":"","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"ARTFICIAL_LIFT_QNTY","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":4,"name":"GAS_CONSUMPTION_RATE","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"GasSurfaceVolume/Time"},{"index":5,"name":"COMPRESSION_LVL","description":"","units":{},"default":"1","value_type":"INT"},{"index":6,"name":"ACTION_SEQ_NUM","description":"","units":{},"default":"1","value_type":"INT"}],"example":"","expected_columns":6,"size_kind":"list"},"GASFDECR":{"name":"GASFDECR","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, GASFDECR, defines the field’s monthly reduction in the gas sales contract quantity for when the Gas Field Operations option has been activated by the GASFIELD keyword in the RUNSPEC section. Gas contracts are commonly based on a Daily Contract Quantity (“DCQ”) that determines the gas rate that the field should be produced at, which is normally expressed as a multiple of the DCQ, for example 1.33, and is often referred to as the “swing factor”. Some gas contracts also define a maximum DCQ (“Max DCQ”) and/or a minimum take or pay DCQ (“Min DCQ”), as well as seasonal demand characteristics. For example, gas rates may be set higher in the winter months in order to meet heating demand compared with summer months in colder climates, and the opposite in warmer climates where air conditioning demand is high.","parameters":[{"index":1,"name":"JAN","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":2,"name":"FEB","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":3,"name":"MAR","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":4,"name":"APR","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":5,"name":"MAY","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":6,"name":"JUN","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":7,"name":"JUL","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":8,"name":"AUG","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":9,"name":"SEP","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":10,"name":"OCT","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":11,"name":"NOV","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":12,"name":"DEC","description":"","units":{},"default":"0","value_type":"DOUBLE"}],"example":"| [Q sub{month}`=` DCQ times SWINGFAC sub{ month }] | (12.19) |\n|---------------------------------------------------|---------|\n| [Q sub{month}`=`left( DCQ times SWINGFAC sub{ month } right) `-`GASFDECR sub{ month}] | (12.20) |\n|---------------------------------------------------------------------------------------|---------|","expected_columns":12,"size_kind":"fixed","size_count":1},"GASFDELC":{"name":"GASFDELC","sections":["SCHEDULE"],"supported":false,"summary":"The GASFDELC keyword defines how the field’s gas deliverability calculation should be performed for when the Gas Field Operations option has been activated by the GASFIELD keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"VALUE","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"GASFTARG":{"name":"GASFTARG","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, GASFTARG, defines the field’s monthly gas sales contract quantity for when the Gas Field Operations option has been activated by the GASFIELD keyword in the RUNSPEC section. Gas contracts are commonly based on a Daily Contract Quantity (“DCQ”) that determines the gas rate that the field should be produced at, which is normally expressed as a multiple of the DCQ, for example 1.33, and is often referred to as the “swing factor”. Some gas contracts also define a maximum DCQ (“Max DCQ”) and/or a minimum take or pay DCQ (“Min DCQ”), as well as seasonal demand characteristics. For example, gas rates may be set higher in the winter months in order to meet heating demand compared with summer months in colder climates, and the opposite in warmer climates where air conditioning demand is high.","parameters":[{"index":1,"name":"JAN","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length*Length*Length/Time"},{"index":2,"name":"FEB","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length*Length*Length/Time"},{"index":3,"name":"MAR","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length*Length*Length/Time"},{"index":4,"name":"APR","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length*Length*Length/Time"},{"index":5,"name":"MAY","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length*Length*Length/Time"},{"index":6,"name":"JUN","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length*Length*Length/Time"},{"index":7,"name":"JUL","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length*Length*Length/Time"},{"index":8,"name":"AUG","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length*Length*Length/Time"},{"index":9,"name":"SEP","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length*Length*Length/Time"},{"index":10,"name":"OCT","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length*Length*Length/Time"},{"index":11,"name":"NOV","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length*Length*Length/Time"},{"index":12,"name":"DEC","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length*Length*Length/Time"}],"example":"| [Q sub{month}`=` DCQ times SWINGFAC sub{ month }] | (12.21) |\n|---------------------------------------------------|---------|\n| [Q sub{month}`=` Minimum `left( left(DCQ times SWINGFAC sub{ month } right) ,`GASFTARG sub{ month} right)] | (12.22) |\n|------------------------------------------------------------------------------------------------------------|---------|","expected_columns":12,"size_kind":"fixed","size_count":1},"GASMONTH":{"name":"GASMONTH","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, GASMONTH, states the month for which subsequent scheduling events take place within an Annual Schedule section for when the Gas Field Operations option has been activated by the GASFIELD keyword in the RUNSPEC section. The keyword must lie in between the GASBEGIN, that defines the start of an Annual Scheduling section and the GASEND keyword that ends the section. Optionally, the keyword can be used to write a report to the print file (*.PRT) at the requested month.","parameters":[{"index":1,"name":"MONTH","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"WRITE_REPORT","description":"","units":{},"default":"NO","value_type":"STRING"}],"example":"","expected_columns":2,"size_kind":"fixed","size_count":1},"GASPERIO":{"name":"GASPERIO","sections":["SCHEDULE"],"supported":false,"summary":"This keyword advances the simulation over one or more gas contract periods for when the Gas Field Operations option has been activated by the GASFIELD keyword in the RUNSPEC section. A contract period in this case is the period over which the Daily Contract Quantity is fixed, this can a be year or one or more months. If the contract period is a year then the GASYEAR keyword in the SCHEDULE section can be used instead of GASPERIOD.","parameters":[{"index":1,"name":"NUM_PERIODS","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"NUM_MONTHS","description":"","units":{},"default":"12","value_type":"INT"},{"index":3,"name":"INITIAL_DCQ","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":4,"name":"SWING_REQ","description":"","units":{},"default":"PER","value_type":"STRING"},{"index":5,"name":"LIMIT_TIMESTEPS","description":"","units":{},"default":"YES","value_type":"STRING"},{"index":6,"name":"LIMIT_DCQ_RED_FACTOR","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"1"},{"index":7,"name":"ANTICIPATED_DCQ_RED_FACTOR","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"},{"index":8,"name":"MAX_ITERATIONS","description":"","units":{},"default":"3","value_type":"INT"},{"index":9,"name":"DCQ_CONV_TOLERANCE","description":"","units":{},"default":"0.1","value_type":"DOUBLE","dimension":"1"}],"example":"","expected_columns":9,"size_kind":"fixed","size_count":1},"GASYEAR":{"name":"GASYEAR","sections":["SCHEDULE"],"supported":false,"summary":"This keyword advances the simulation over one or more gas contract years for when the Gas Field Operations option has been activated by the GASFIELD keyword in the RUNSPEC section. A contract year in this case is the period over which the Daily Contract Quantity is fixed, this can a be year, this keyword or the GASPERIO keyword in the SCHEDULE section, or one or more months. If the contract period is over one or more months then the GASPERIO keyword in the SCHEDULE section can be used instead of GASYEAR.","parameters":[{"index":1,"name":"NUM_YEARS","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"INITIAL_DCQ","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":3,"name":"SWING_REQ","description":"","units":{},"default":"YEAR","value_type":"STRING"},{"index":4,"name":"LIMIT_TIMESTEPS","description":"","units":{},"default":"YES","value_type":"STRING"},{"index":5,"name":"LIMIT_DCQ_RED_FACTOR","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"1"},{"index":6,"name":"ANTICIPATED_DCQ_RED_FACTOR","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"},{"index":7,"name":"MAX_ITERATIONS","description":"","units":{},"default":"3","value_type":"INT"},{"index":8,"name":"DCQ_CONV_TOLERANCE","description":"","units":{},"default":"0.1","value_type":"DOUBLE","dimension":"1"}],"example":"","expected_columns":8,"size_kind":"fixed","size_count":1},"GCALECON":{"name":"GCALECON","sections":["SCHEDULE"],"supported":false,"summary":"The GCALECON keyword defines economic criteria for production groups, including the field level group FIELD, that have previously been defined by the GCONPROD keyword in the SCHEDULE section and have had their rate targets and constraints set by calorific value via the GCONVAL keyword in the SCHEDULE section.","parameters":[{"index":1,"name":"GRPNAME","description":"A character string of up to eight characters in length that defines the group name for which the group target and constraints are being defined. The group named FIELD is the top most group and should be used to set targets and constraints for the field. Note that the group hierarchy should be defined by the GRUPTREE keyword when there is more than one level of groups, otherwise all the groups will sit directly under the FIELD group in the group tree hierarchy.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"ENEVAL","description":"A real positive value that defines the minimum economic surface energy production rate, below which an economic action of shutting in or stopping all the wells in the group, as requested by item (9) of the WELSPECS keyword. A value less than or equal to zero switches of this criteria.","units":{"field":"BTU/day","metric":"kJ/day","laboratory":"J/hour"},"default":"0.0","value_type":"DOUBLE","dimension":"Energy/Time"},{"index":3,"name":"CALVAL","description":"A real positive value that defines the minimum economic surface calorific value, below which an economic action of shutting in or stopping all the wells in the group, as requested by item (9) of the WELSPECS keyword. A value less than or equal to zero switches of this criteria,","units":{"field":"Btu/Mscf","metric":"kJ/sm3","laboratory":"J/scc"},"default":"0.0","value_type":"DOUBLE","dimension":"Energy/GasSurfaceVolume"},{"index":4,"name":"FLAG_END_RUN","description":"","units":{},"default":"NO","value_type":"STRING"},{"index":8,"name":"END","description":"A defined character string that defines if the simulation should terminate if all the producing wells in the group, including the FIELD group, are shut or stopped. END should be set to one of the following character strings: NO: no action is taken and the run continues. YES: terminate the run at the next report time step.","units":{},"default":"NO"}],"example":"The following example defines the economic criteria for the field with a minimum economic surface energy production rate of 5 x 109 BTU/day and a minimum economic surface calorific value of900 Btu/Mscf\n--\n-- GROUP ECONOMIC CRITERIA FOR PRODUCTION GROUPS UNDER CALORIFIC CONTROL\n--\n-- GRUP ENERGY CALORIFIC END\n-- NAME RATE VALUE RUN\nGCALECON\nFIELD 5E9 900.0 'YES' /\n/\nIf the economic limits are violated then the run will stop at the next report time step.","expected_columns":4,"size_kind":"list"},"GCONCAL":{"name":"GCONCAL","sections":["SCHEDULE"],"supported":false,"summary":"The GCONCAL keyword defines calorific production targets and constraints for groups, including the top most group in the group hierarchy known as the FIELD group. Wells are allocated to groups when the wells are specified by the WELSPECS keyword in the SCHEDULE section. Wells defined to be under group control will have their production rates controlled by the group to which they belong, in addition to any well constraints defined for the wells.","parameters":[{"index":1,"name":"GRPNAME","description":"A character string of up to eight characters in length that defines the group name for which the group’s target calorific value is being defined. The group named FIELD is the top most group and should be used to set targets and constraints for the field. Note that the group hierarchy should be defined by the GRUPTREE keyword when there is more than one level of groups, otherwise all the groups will sit directly under the FIELD group in the group tree hierarchy.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"CALVAL","description":"A real positive value that defines the target surface calorific value of the produced gas. The default value of 1 x 1020 switches off calorific control for the group.","units":{"field":"Btu/Mscf","metric":"kJ/sm3","laboratory":"J/hour"},"default":"1.0 x 1020","value_type":"DOUBLE","dimension":"Energy/GasSurfaceVolume"},{"index":3,"name":"ACTION","description":"A defined character string that defines the action to be taken if the CALVAL is violated. ACTION should be set to one of the following character strings: NONE: no action is taken and the group’s produced calorific value will therefore no longer meet CALVAL. RATE: scale back the gas rate of various wells under the group by the value of FACTOR until the calorific target (CALVAL) is satisfied. The corrective action takes places at the end of the time step in which the constraint is violated.","units":{},"default":"None","value_type":"STRING","options":["NONE","RATE"]},{"index":4,"name":"FACTOR","description":"A real positive value that is less than or equal to one that defines the amount wells can be scaled back in order to satisfy CALVAL. Note this assumes that there are wells within the group that are producing with higher and lower calorific values, and the simulator is thus able to fine a combination of wells that satisfy the group’s CALVAL target.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":"1"}],"example":"The following example defines the calorific production target for the field.\n---\n-- GROUP CALORIFIC PRODUCTION CONTROLS\n--\n-- GRUP CALORIFIC ACTION CUT\n-- NAME VALUE BACK\nGCONCAL\nFIELD 1010E3 RATE 0.95 /\n/\nHere the calorific production target has been set to 1,010 x 103 Btu/Mscf for the field and if the target cannot be met then the well rates are reduced by 0.95 at each iteration until the target is satisfied.","expected_columns":4,"size_kind":"list"},"GCONENG":{"name":"GCONENG","sections":["SCHEDULE"],"supported":false,"summary":"The GCONCAL keyword defines energy production targets and constraints for groups, including the top most group in the group hierarchy known as the FIELD group. Wells are allocated to groups when the wells are specified by the WELSPECS keyword in the SCHEDULE section. Wells defined to be under group control will have their production rates controlled by the group to which they belong, in addition to any well constraints defined for the wells.","parameters":[{"index":1,"name":"GRPNAME","description":"A character string of up to eight characters in length that defines the group name for which the group’s target calorific value is being defined. The group named FIELD is the top most group and should be used to set targets and constraints for the field. Note that the group hierarchy should be defined by the GRUPTREE keyword when there is more than one level of groups, otherwise all the groups will sit directly under the FIELD group in the group tree hierarchy.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"ENGVAL","description":"A real positive value that defines the surface energy target for the group. The default value of 1 x 1020 switches off the energy target for the group.","units":{"field":"BTU/day","metric":"kJ/day","laboratory":"J/hour"},"default":"1.0 x 1020","value_type":"DOUBLE","dimension":"Energy/Time"}],"example":"The following example defines the energy production target for the field.\n--\n-- GROUP ENERGY PRODUCTION CONTROLS\n--\n-- GRUP ENERGY\n-- NAME VALUE\nGCONENG\nFIELD 1010E9 /\n/\nHere the energy production target has been set to 1,010 x 109 Btu/day for the field.","expected_columns":2,"size_kind":"list"},"GCONINJE":{"name":"GCONINJE","sections":["SCHEDULE"],"supported":null,"summary":"The GCONINJE keyword defines injection targets and constraints for groups, including the top most group in the group hierarchy known as the FIELD group. Wells are allocated to groups when the wells are specified by the WELSPECS keyword in the SCHEDULE section. Wells defined to be under group control will have their injection rates controlled by the group to which they belong, in addition to any well constraints defined for the wells.","parameters":[{"index":1,"name":"GRPNAME","description":"A character string of up to eight characters in length that defines the group name for which the group target and constraints are being defined. The group named FIELD is the top most group and should be used to set targets and constraints for the whole field. Note that the group hierarchy should be defined by the GRUPTREE keyword in the SCHEDULE, when there is more than one level of groups, otherwise all the groups will sit directly under the FIELD group in the group tree hierarchy.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"TYPE","description":"A defined character string that defines the type of injection fluid. TYPE should be set to one of the following character strings: GAS: for a gas injection well. OIL: for a water injection well. WAT: for a water injection well.","units":{},"default":"None","value_type":"STRING","options":["GAS","OIL","WAT"]},{"index":3,"name":"TARGET","description":"A defined character string that sets the target injection control for the group, all the other phases will therefore act as constraints. The simulator will attempt to meet the TARGET based on the phase rate stated in items (4) to (7) on this keyword. TARGET should be set to one of the following character strings: NONE: the group has no target phase, but if entered, constraints are still defined and active. FLD: this group is controlled from a higher level group, including the FIELD group. RATE: the injection phase will be control by the surface fluid rate for the phase defined by the TYPE variable. For example, if TYPE has been set to WAT then this would mean the water injection rate as defined by item (4). RESV: the target is set to the in situ reservoir volume rate as defined by item (5). REIN: the target is set to the group's production of the phase defined by TYPE multiplied by the value on item (6). For example, if TYPE has been set to WAT then this would mean the group's water production multiplied by item (6). VREP: the target is set to the group's voidage replacement ratio as defined by item (7).","units":{},"default":"None","value_type":"STRING","options":["NONE","FLD","RATE","RESV","REIN","VREP"]},{"index":4,"name":"RATE","description":"A real positive value that defines the maximum surface injection rate target or constraint for the phase declared by the TYPE variable. This value may be specified using a User Defined Argument (UDA).","units":{"field":"Liquid stb/d Gas Mscf/d","metric":"Liquid sm3/day Gas sm3/day","laboratory":"Liquid scc/hour Gas scc/hour"},"default":"None","value_type":"UDA"},{"index":5,"name":"RESV","description":"A real positive value that defines the maximum reservoir volume injection rate target or constraint. This value may be specified using a User Defined Argument (UDA). Note setting a value here other than the default means that TYPE, item (2) will be the supplement or “make up” phase.","units":{"field":"rtb/d","metric":"rm3/day","laboratory":"rcc/hour"},"default":"None","value_type":"UDA","dimension":"ReservoirVolume/Time"},{"index":6,"name":"REIN","description":"A real positive value that defines the target or constraint re-injection fraction for the produced phase defined by the TYPE variable. This value may be specified using a User Defined Argument (UDA). For example, if TYPE is equal to GAS and REIN is equal to 0.85, then 85% of the produced gas will be re-injected.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"UDA","dimension":"1"},{"index":7,"name":"VREP","description":"A real positive value that defines the target or constraint of the voidage replacement ratio based on all the produced fluids. This value may be specified using a User Defined Argument (UDA). For example, if TYPE is equal to WAT and VREP is equal to 1.00, then 100% of the produced reservoir volume will be re-inject as an equivalent water volume. Note setting a value here other than the default means that TYPE, item (2) will be the supplement phase.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"UDA","dimension":"1"},{"index":8,"name":"GRPCNTL","description":"A defined character string that determines if this group is subject to higher level group control. YES: then this group is subject to a higher level group’s control and the flow rates for this group will be adjusted accordingly. NO: then this group is NOT subject to a higher level group’s control and the flow rates for this group will only be controlled by the parameters for this group. This variable is ignored if GRPNAME is equal to FIELD.","units":{},"default":"YES","value_type":"STRING","options":["YES","NO"]},{"index":9,"name":"GRPGUIDE","description":"A real positive value that defines a group's injection guide rate expressed as a dimensionless number. A group requires a value for GRPGUIDE only if it is required to produce a specified proportion of a higher level group’s rate. Defaulting GRPGUIDE results in the subordinate groups and wells under guide control having their rates dictated by any higher level groups under guide rate control. In other words the GRPNAME is masked out. Setting GRPGUIDE to a real positive value and GUIPHASE to either RATE or RESV will result in a constant injection guide rate.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE","dimension":"1"},{"index":10,"name":"GUIPHASE","description":"A defined character string that sets the guide phase to which the guide rate in item (9) applies. GUIPHASE should be set to one of the following character strings: NETV: the guide phase is set to production rate minus any injected reservoir rate from the other phases. The net volume is calculated at the beginning of a time step and the option should only be used for groups under voidage replacement control. Note that using this option means that TYPE, item (2) will be the supplement or “make up” phase and the value entered for the group's guide rate (GRPGUIDE) will be ignored with this option. RATE: the guide phase is set to the surface injection rate. Setting GUIPHASE to RATE and GRPGUIDE to a real positive value will result in a constant injection guide rate. RESV: the guide phase is set to the in situ reservoir volume rate. Setting GUIPHASE to RESV and GRPGUIDE to a real positive value will result in a constant injection guide rate. VOID: the guide rate is calculated at the beginning of each time step based on the group’s net voidage rate. OPM Flow now supports all guide rate options. The default value of 1* means that the group has no injection guide rate for this phase.","units":{},"default":"None","value_type":"STRING","options":["NETV","RATE","RESV","VOID"]},{"index":11,"name":"GRPREIN","description":"A character string of up to eight characters in length that defines the group name whose production rate should be used for applying the REIN quantity to be injected into GRPNAME. This variable is used to re-inject the REIN production faction from another group (GRPREIN) via this group (GRPNAME). If GRPREIN is defaulted then the re-injection quantity for GRPNAME will be based on the production from GRPNAME itself.","units":{},"default":"GRPNAME","value_type":"STRING"},{"index":12,"name":"GRPVREP","description":"A character string of up to eight characters in length that defines the group name whose production rate should be used for applying the VREP quantity to be injected into GRPNAME. This variable is used to re-inject the VREP production faction from another group (GRPVREP) via this group (GRPNAME). If GRPVREP is defaulted then the voidage quantity for GRPNAME will be based on the production from GRPNAME itself.","units":{},"default":"GRPNAME","value_type":"STRING"},{"index":13,"name":"WGASRATE","description":"Wet gas injection rate used in the commercial compositional simulator. Not used and should be defaulted with 1*.","units":{},"default":"1*","value_type":"DOUBLE","dimension":"GasSurfaceVolume/Time"}],"example":"The following example defines the injection targets and constraints for the field and two groups that are one level below the field group, since the GRUPTREE keyword has not been entered to define the group hierarchy.\n--\n-- GROUP INJECTION TARGETS AND CONSTRAINTS\n--\n-- GRUP FLUID CNTL SURF RESV REINJ VOID GRUP GUIDE GUIDE GRUP GRUP\n-- NAME TYPE MODE RATE RATE FRAC FRAC CNTL RATE DEF REINJ RESV\nGCONINJE\nFIELD WAT VREP 35E3 1* 1* 1* NO 1* 1* 1* 1* /\nGRP01 WAT VREP 1* 1* 1* 1.0 YES 1* 1* 1* 1* /\nGRPO2 WAT VREP 1* 1* 1* 1.0 YES 1* 1* 1* 1* /\n/\nIn this example, group GRP01 and GRP02 are injecting water via voidage replacement with a voidage replacement of one and are under the control on the field group, that imposes a 35,000 m3/day total water injection limit.","expected_columns":13,"size_kind":"list"},"GCONPRI":{"name":"GCONPRI","sections":["SCHEDULE"],"supported":false,"summary":"The GCONPRI keyword defines production targets and constraints for groups, including the top most group in the group hierarchy known as the FIELD group, for when groups and their associated wells are operating under priority control as oppose to guide rate control. Priority control is activated by the PRIORITY keyword in the SCHEDULE section. Wells are allocated to groups when the wells are specified by the WELSPECS keyword in the SCHEDULE section. Wells defined to be under group control will have their production rates controlled by the group to which they belong, in addition to any well constraints defined for the wells.","parameters":[{"index":1,"name":"GRPNAME","description":"A character string of up to eight characters in length that defines the group name for which the group target and constraints are being defined. The group named FIELD is the top most group and should be used to set targets and constraints for the field. Note that the group hierarchy should be defined by the GRUPTREE keyword when there is more than one level of groups, otherwise all the groups will sit directly under the FIELD group in the group tree hierarchy.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"ORAT","description":"A real positive value that defines the maximum surface oil production rate constraint. This value may be specified using a User Defined Argument (UDA).","units":{"field":"stb/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"None","value_type":"UDA","dimension":"LiquidSurfaceVolume/Time"},{"index":3,"name":"OILACT","description":"A defined character string that defines the action to be taken if ORAT is exceeded. OILACT should be set to one of the following character strings: NONE: no action is taken. CON: close the worst offending connection in the worst offending well. If connections have been grouped as completions then the worst offending completion in the worst offending well will be closed. +CON: close the worst offending connection and all below it in the worst offending well. If connections have been grouped as completions then the worst offending completion and all below it in the worst offending well will be closed. WELL: close the worst offending well. PLUG: plug back the worst offending well based on the plug back length and options defined on the WPLUG keyword in the SCHEDULE. PRI: control the group production rate using the first priority formulae defined by the PRIORITY keyword in the SCHEDULE section. PR2: control the group production rate using the second priority formulae defined by the PRIORITY keyword in the SCHEDULE section.","units":{},"default":"“NONE”","value_type":"STRING","options":["NONE","CON","WELL","PLUG","PRI","PR2"]},{"index":4,"name":"WRAT","description":"A real positive value that defines the maximum surface water production rate constraint. This value may be specified using a User Defined Argument (UDA).","units":{"field":"stb/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"None","value_type":"UDA","dimension":"LiquidSurfaceVolume/Time"},{"index":5,"name":"WATACT","description":"A defined character string that defines the action to be taken if WRAT is exceeded. WATACT should be set to a character string described by the OILACT parameter on this record.","units":{},"default":"None","value_type":"STRING"},{"index":6,"name":"GRAT","description":"A real positive value that defines the maximum surface gas production rate constraint This value may be specified using a User Defined Argument (UDA).","units":{"field":"Mscf/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"None","value_type":"UDA","dimension":"GasSurfaceVolume/Time"},{"index":7,"name":"GASACT","description":"A defined character string that defines the action to be taken if GRAT is exceeded. GASACT should be set to a character string described by the OILACT parameter on this record.","units":{},"default":"None","value_type":"STRING"},{"index":8,"name":"LRAT","description":"A real positive value that defines the maximum surface liquid (oil plus water) production rate constraint. This value may be specified using a User Defined Argument (UDA).","units":{"field":"stb/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"None","value_type":"UDA","dimension":"LiquidSurfaceVolume/Time"},{"index":9,"name":"LIQACT","description":"A defined character string that defines the action to be taken if LRAT is exceeded. LIQACT should be set to a character string described by the OILACT parameter on this record.","units":{},"default":"None","value_type":"STRING"},{"index":10,"name":"RESV","description":"A real positive value that defines the maximum reservoir volume production rate constraint. This value may be specified using a User Defined Argument (UDA).","units":{"field":"rb/d","metric":"rm3/day","laboratory":"rcc/hour"},"default":"None","value_type":"UDA","dimension":"ReservoirVolume/Time"},{"index":11,"name":"RESVFRAC","description":"A real positive value that defines a group's maximum production balancing fraction constraint. This value may be specified using a User Defined Argument (UDA).","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"UDA","dimension":"1"},{"index":12,"name":"","description":"Not used should be defaulted with 1*.","units":{},"default":"1*","value_type":"UDA","dimension":"GasSurfaceVolume/Time"},{"index":13,"name":"","description":"Not used should be defaulted with 1*.","units":{},"default":"1*","value_type":"STRING"},{"index":14,"name":"","description":"Not used should be defaulted with 1*.","units":{},"default":"1*","value_type":"UDA","dimension":"1"},{"index":15,"name":"","description":"Not used should be defaulted with 1*.","units":{},"default":"1*","value_type":"UDA","dimension":"1"},{"index":16,"name":"LINCOMB","description":"A real positive value that defines the linearly combined maximum surface target rate or constraint, as per the LINCOM keyword in the SCHEDULE section.","units":{},"default":"1*","value_type":"UDA"},{"index":17,"name":"LINACT","description":"A defined character string that defines the action to be taken if LINCOMB is exceeded. LINACT should be set to a character string described by the OILACT parameter on this record.","units":{},"default":"None","value_type":"STRING"}],"example":"The following example defines the production targets and constraints for the field and two groups that are one level below the field group, since the GRUPTREE keyword has not been entered to define the group hierarchy.\n--\n-- GROUP PRIORITY PRODUCTION CONTROLS\n--\n-- GRUP ORAT ORAT WRAT WRAT GRAT GRAT LRAT LRAT RVOL RVOL\n-- NAME LIMT ACTN LIMT ACTN LIMT ACTN LIMT ACTN LIMT ACTN\nGCONPRI\nFIELD 40E3 PRI 30E3 +CON 125E3 PRI 1* 1* 1* 1* /\nGRP01 25E3 PRI 1* 1* 1* 1* 1* 1* 1* 1* /\nGRP02 25E3 PRI 1* 1* 1* 1* 1* 1* 1* 1* /\n/\nAll groups are controlled by oil constraints, but only the field level has water and gas constraints to reflect the actual production facility constraints. The oil production constraint of 40,000, 25,000 and 25,000 stb/d are defined for the field, GRP01 and GRP02 groups, respectively. If the oil rate constraint is exceeded then the wells will be controlled using the priority formulae one, as defined on the PRIORITY keyword in the SCHEDULE section. Similarly for the field, for when the gas constraint is exceeded. Finally, if the field water constraint is surpassed then the worst offending connection and below in the worst offending well are shut.","expected_columns":17,"size_kind":"list"},"GCONPROD":{"name":"GCONPROD","sections":["SCHEDULE"],"supported":true,"summary":"The GCONPROD keyword defines production targets and constraints for groups, including the top most group in the group hierarchy known as the FIELD group. Wells are allocated to groups when the wells are specified by the WELSPECS keyword in the SCHEDULE section. Wells defined to be under group control will have their production rates controlled by the group to which they belong, in addition to any well constraints defined for the wells.","parameters":[{"index":1,"name":"GRPNAME","description":"A character string of up to eight characters in length that defines the group name for which the group target and constraints are being defined. The group named FIELD is the top most group and should be used to set targets and constraints for the field. Note that the group hierarchy should be defined by the GRUPTREE keyword in the SCHEDULE section, when there is more than one level of groups, otherwise all the groups will sit directly under the FIELD group in the group tree hierarchy.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"TARGET","description":"A defined character string that specifies the production rate control mode for the group. The simulator will attempt to meet the TARGET rate as defined by remaining items on this keyword. TARGET should be set to one of the following character strings: NONE: the group has no target rate, but if entered, constraints are still defined and active. FLD: this group is controlled by a higher level group (including the FIELD group) subject to its guide rate as defined by items (9) and (10). ORAT: the target is set to the surface oil production rate as defined by item (3). WRAT: the target is set to the surface water production rate as defined by item (4). GRAT: the target is set to the surface gas production rate as defined by item (5). LRAT: the target is set to the surface liquid (oil plus water) production rate as defined by item (6). RESV: the target is set to the in situ reservoir volume rate as defined by item (14). Note that the commercial simulator includes additional options (not listed above) that are not currently supported by OPM Flow.","units":{},"default":"None","value_type":"STRING","options":["NONE","FLD","ORAT","WRAT","GRAT","LRAT","RESV"]},{"index":3,"name":"ORAT","description":"A real positive value that defines the maximum surface oil production rate target or constraint. This value may be specified using a User Defined Argument (UDA).","units":{"field":"stb/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"None","value_type":"UDA","dimension":"LiquidSurfaceVolume/Time"},{"index":4,"name":"WRAT","description":"A real positive value that defines the maximum surface water production rate target or constraint. This value may be specified using a User Defined Argument (UDA).","units":{"field":"stb/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"None","value_type":"UDA","dimension":"LiquidSurfaceVolume/Time"},{"index":5,"name":"GRAT","description":"A real positive value that defines the maximum surface gas production rate target or constraint. This value may be specified using a User Defined Argument (UDA).","units":{"field":"Mscf/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"None","value_type":"UDA","dimension":"GasSurfaceVolume/Time"},{"index":6,"name":"LRAT","description":"A real positive value that defines the maximum surface liquid (oil plus water) production rate target or constraint. This value may be specified using a User Defined Argument (UDA).","units":{"field":"stb/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"None","value_type":"UDA","dimension":"LiquidSurfaceVolume/Time"},{"index":7,"name":"ACTION","description":"A defined character string that specifies the action to be taken if the constraints in (3) to (6) are violated. ACTION should be set to one of the following character strings: NONE: no action is taken. CON: close the worst offending connection in the worst offending well. If connections have been grouped as completions then the worst offending completion in the worst offending well will be closed. +CON: close the worst offending connection and all below it in the worst offending well. If connections have been grouped as completions then the worst offending completion and all below it in the worst offending well will be closed. WELL: close the worst offending well. PLUG: plug back the worst offending well. RATE: control the group production rate to equal the upper limit. This effectively changes the TARGET to be the violated phase constraint. The corrective action takes places at the end of the time step in which the constraint is violated. Note that only the NONE, WELL and RATE options are currently supported by OPM Flow.","units":{},"default":"None","value_type":"STRING","options":["NONE","CON","WELL","PLUG","RATE"]},{"index":8,"name":"GRPCNTL","description":"A defined character string that determines if this group is subject to higher level group control. YES: then this group is subject to a higher level group’s control and the flow rates for this group will be adjusted accordingly. NO: then this group is NOT subject to a higher level group’s control and the flow rates for this group will only be controlled by the parameters for this group. GRPCNTL will be ignored for the FIELD group.","units":{},"default":"None","value_type":"STRING","options":["YES","NO"]},{"index":9,"name":"GRPGUIDE","description":"A real positive value that defines a group's production guide rate expressed as a dimensionless number. A group requires a value for GRPGUIDE only if it is required to produce a specified proportion of a higher level group’s rate","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE"},{"index":10,"name":"GUIPHASE","description":"A defined character string that sets the guide phase to which the guide rate in item (9) applies. GUIPHASE should be set to one of the following character strings: OIL: the guide phase is set to oil. WAT: the guide phase is set to water. GAS: the guide phase is set to gas. LIQ: the guide phase is set to liquid (oil plus water). COMB: the guide phase is set to a linear combination of phases with the coefficients specified by the LINCOM keyword in the SCHEDULE section. INJV: the guide rate is set to the group’s reservoir volume injection rate at the start of each timestep. POTN: the guide rate is set to the group’s production potential at the start of each timestep. FORM: the guide rate will be based on the formulae defined via the GUIDERAT keyword in the SCHEDULE section. The formulae enables subordinate groups and wells to decrease their contribution from wells producing too much gas or too much water. ' ' or 1* : the group is not under guide rate control, and therefore superordinate group production targets will be pro-rated directly down to its subordinate groups and wells. Note that only the OIL, WAT, GAS, LIQ and default options are currently supported by OPM Flow.","units":{},"default":"1*","value_type":"STRING","options":["OIL","WAT","GAS","LIQ","COMB","INJV","POTN","FORM"]},{"index":11,"name":"ACTWAT","description":"A defined character string that defines the action to be taken if the WRAT constraint, item (4), is violated. ACTWAT should be set to one of the following character strings: NONE: no action is taken. CON: close the worst offending connection in the worst offending well. If connections have been grouped as completions then the worst offending completion in the worst offending well will be closed. +CON: close the worst offending connection and all below it in the worst offending well. If connections have been grouped as completions then the worst offending completion and all below it in the worst offending well will be closed. WELL: close the worst offending well. PLUG: plug back the worst offending well. This option is not implemented in OPM Flow. RATE: control the group production rate to equal the upper limit. This effectively changes the TARGET to be the violated phase constraint. If defaulted then procedure defined by ACTION, item (7), is applied. The corrective action takes places at the end of the time step in which the constraint is violated. Note that only the NONE and RATE options are currently supported by OPM Flow.","units":{},"default":"1*","value_type":"STRING","options":["NONE","CON","WELL","PLUG","RATE"]},{"index":12,"name":"ACTGAS","description":"A defined character string that defines the action to be taken if the GRAT constraint, item (5), is violated. ACTGAS should be set to one of the following character strings: NONE: no action is taken. CON: close the worst offending connection in the worst offending well. If connections have been grouped as completions then the worst offending completion in the worst offending well will be closed. +CON: close the worst offending connection and all below it in the worst offending well. If connections have been grouped as completions then the worst offending completion and all below it in the worst offending well will be closed. WELL: close the worst offending well. PLUG: plug back the worst offending well. RATE: control the group production rate to equal the upper limit. This effectively changes the TARGET to be the violated phase constraint. If defaulted then procedure defined by ACTION, item (7), is applied. The corrective action takes places at the end of the time step in which the constraint is violated Note that only the NONE and RATE options are currently supported by OPM Flow.","units":{},"default":"1*","value_type":"STRING","options":["NONE","CON","WELL","PLUG","RATE"]},{"index":13,"name":"ACTLIQ","description":"A defined character string that defines the action to be taken if the LRAT constraint, item (6), is violated. ACLIQT should be set to one of the following character strings: NONE: no action is taken. CON: close the worst offending connection in the worst offending well. If connections have been grouped as completions then the worst offending completion in the worst offending well will be closed. +CON: close the worst offending connection and all below it in the worst offending well. If connections have been grouped as completions then the worst offending completion and all below it in the worst offending well will be closed. WELL: close the worst offending well. PLUG: plug back the worst offending well. This option is not implemented in OPM Flow. RATE: control the group production rate to equal the upper limit. This effectively changes the TARGET to be the violated phase constraint. If defaulted then procedure defined by ACTION, item (7), is applied. The corrective action takes places at the end of the time step in which the constraint is violated. Note that only the NONE and RATE options are currently supported by OPM Flow.","units":{},"default":"1*","value_type":"STRING","options":["NONE","CON","WELL","PLUG","RATE"]},{"index":14,"name":"RESV","description":"A real positive value that defines the maximum reservoir volume production rate target or constraint. This value may be specified using a User Defined Argument (UDA).","units":{"field":"rb/d","metric":"rm3/day","laboratory":"rcc/hour"},"default":"None","value_type":"UDA","dimension":"ReservoirVolume/Time"},{"index":15,"name":"RESVFRAC","description":"A real positive value that defines the maximum reservoir volume production balancing fraction. Not used and should be defaulted with 1*.","units":{},"default":"1*","value_type":"DOUBLE","dimension":"1"},{"index":16,"name":"WGASRATE","description":"Wet gas production rate used in the commercial compositional simulator. Not used and should be defaulted with 1*.","units":{},"default":"1*","value_type":"DOUBLE","dimension":"1"},{"index":17,"name":"CALRATE","description":"Calorific production rate used in the commercial compositional simulator. Not used and should be defaulted with 1*.","units":{},"default":"1*","value_type":"DOUBLE"},{"index":18,"name":"GASFRAC","description":"Surface gas production fraction used in the commercial compositional simulator Not used and should be defaulted with 1*.","units":{},"default":"1*","value_type":"DOUBLE"},{"index":19,"name":"WATFRAC","description":"Surface water production fraction used in the commercial compositional simulator. Not used and should be defaulted with 1*.","units":{},"default":"1*","value_type":"DOUBLE"},{"index":20,"name":"COMBRATE","description":"Linearly combined production rate used in the commercial compositional simulator. Not used and should be defaulted with 1*.","units":{},"default":"1*","value_type":"DOUBLE"},{"index":21,"name":"COMBPROC","description":"Linearly combined procure for when exceeding COMBRATE, used in the commercial black-oil simulator. Not used and should be defaulted with 1*.","units":{},"default":"1*","value_type":"STRING"}],"example":"The following example defines the production targets and constraints for the field and two groups that are one level below the field group, since the GRUPTREE keyword has not been entered to define the group hierarchy.\n--\n-- GROUP PRODUCTION CONTROLS\n--\n-- GRUP CNTL OIL WAT GAS LIQ CNTL GRUP GUIDE GUIDE CNTL\n-- NAME MODE RATE RATE RATE RATE OPT CNTL RATE DEF WAT\nGCONPROD\nFIELD ORAT 40E3 60E3 300E3 60E3 1* 1* 1* 1* 1* /\nGRP01 FLD 25E3 1* 1* 1* 1* 1* 1* 1* 1* /\nGRP02 FLD 25E3 1* 1* 1* 1* 1* 1* 1* 1* /\n/\nAll groups are controlled by oil rate targets or constraints, but only the field level has water, gas and liquid constraints to reflect the actual production facility constraints. The wells under group control will be produced based on oil potential of each of the wells under group control, such that the field oil production target of 40,000 stb/d is honored and subject to the other phase fluid constraints. In addition, GRP01 and GRP02 oil rate values of 25,000 stb/d are constraints as these two groups are subject to the FIELD level targets and constraints.","expected_columns":21,"size_kind":"list"},"GCONSALE":{"name":"GCONSALE","sections":["SCHEDULE"],"supported":null,"summary":"GCONSALE defines group sales gas production targets and constraints for when the gas production from an oil field group is exported under a Gas Sales Agreement (“GSA”) and the oil field group also has oil production targets and constraints.","parameters":[{"index":1,"name":"GRPNAME","description":"A character string of up to eight characters in length that defines the group name for which the group gas sales target and constraints are being defined. The group named FIELD is the top most group and should be used to set the gas sales targets and constraints for the field. Note that the group hierarchy should be defined by the GRUPTREE keyword when there is more than one level of groups, otherwise all the groups will sit directly under the FIELD group in the group tree hierarchy.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"GSALE","description":"GSALE should either be set to: A real positive value that defines the gas sales rate for the group, or, A real negative value that switches off both gas sales and gas re-injection for the group. This value may be specified using a User Defined Argument (UDA). Note that if GSALE has been set to switch off both gas sales and gas re-injection, then the GCONINJE keyword in the SCHEDULE section may be used to re-enable gas re-injection again.","units":{"field":"Mscf/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"None","value_type":"UDA","dimension":"GasSurfaceVolume/Time"},{"index":3,"name":"GSALEMAX","description":"A real positive value that must be greater than GSALE that defines the maximum allowed gas sales rate. If GSALE exceeds GSALEMAX then the action defined by the ACTION variable on this keyword is implemented at the end of the current time step. This value may be specified using a User Defined Argument (UDA).","units":{"field":"Mscf/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"1 x 1020","value_type":"UDA","dimension":"GasSurfaceVolume/Time"},{"index":4,"name":"GSALEMIN","description":"A real positive value that must be less than GSALE that defines the minimum allowed gas sales rate. If GSALE is less than GSALEMIN then one of the following actions will be implemented at the end of the current time step: If the group’s maximum gas production rate constraint is constraining the gas rate, then reset the constraint to satisfy the group’s minimum gas sales rate (GSALEMIN), else: If the group has active subordinate dedicated gas producers, as defined by the WGASPROD keyword in the SCHEDULE section, then reset their gas target rates to satisfy GSALEMIN, else: If there are subordinate dedicated gas producers for the group in a drilling queue, open the next dedicated well and set the well’s gas rate to satisfy GSALEMIN. Note that only wells that are subordinate to the group and are not under gas rate control or group prioritization are considered for opening. If there are no appropriate subordinate dedicated gas producers for the group in a drilling queue, open the next non-dedicated well and set the well’s gas rate to satisfy GSALEMIN. Again, note that only wells that are subordinate to the group and are not under gas rate control or group prioritization are considered for opening. If none of the above actions can be implemented then the minimum gas sales rate will not be satisfied. This value may be specified using a User Defined Argument (UDA).","units":{},"default":"-1 x 1020","value_type":"UDA","dimension":"GasSurfaceVolume/Time"},{"index":5,"name":"ACTION","description":"A defined character string that defines the action to be taken if the maximum gas sales rate, GSALEMAX, is violated. ACTION should be set to one of the following character strings: NONE: no action is taken. CON: close the worst offending connection in the worst offending well. If connections have been grouped as completions then the worst offending completion in the worst offending well will be closed. +CON: close the worst offending connection and all below it in the worst offending well. If connections have been grouped as completions then the worst offending completion and all below it in the worst offending well will be closed. WELL: close the worst offending well. PLUG: plug back the worst offending well. This option is not implemented in OPM Flow. RATE: the group’s production rate target is reduced to equal GSALEMAX, after accounting for fuel gas (GCONSUMP keyword) and the current rate of re-injection. This will also place the group on gas production control. END: stop the simulation at the end of the report step. The corrective action takes places at the end of the time step in which the constraint is violated.","units":{},"default":"None","value_type":"STRING","options":["NONE","CON","WELL","PLUG","RATE","END"]}],"example":"The following examples sets the field gas sales target rate:\n--\n-- GROUP GAS SALES FOR OIL FIELDS\n--\n-- GRUP GAS MAX MIN CNTL\n-- NAME SALES RATE RATE ACTN\nGCONSALE\nFIELD 40E3 50E3 20E3 RATE /\n/\nHere the field has a gas sales target of 40 MMscf/d, with a maximum rate of 50 MMscf/d and a minimum of 20 MMscf/d. If the maximum gas sales rate is exceeded then the group’s gas production rate target is reduced to equal GSALEMAX, after accounting for fuel gas and the current rate of re-injection. This will also place the group on gas production control.\n| [\"Gas Sales Rate\" ~ = ~ \"Total Group Gas Production Rate\"\nnewline \n~~~~~~~~~~~~~~ - ` \"Group Gas Injection Rate\"\nnewline \n~~~~~~~~~~~~~~~~~~ + ` \"Total Group Gas Import Rate\" \nnewline \n~~~~~~~~~~~~~~~~~~~ - ` \"Total Group Gas Consumption\"] | (12.23) |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|","expected_columns":5,"size_kind":"list"},"GCONSUMP":{"name":"GCONSUMP","sections":["SCHEDULE"],"supported":false,"summary":"GCONSUMP defines the group gas consumption rate either as an actual rate or as a percentage of the group’s production. In both oil and gas fields produced gas is commonly used as fuel to support the processing and utility facilities needed to run the plant.","parameters":[{"index":1,"name":"GRPNAME","description":"A character string of up to eight characters in length that defines the group name for which the group gas consumption is being defined. The group named FIELD is the top most group and should be used to set the fuel consumption for the field. Note that the group hierarchy should be defined by the GRUPTREE keyword when there is more than one level of groups, otherwise all the groups will sit directly under the FIELD group in the group tree hierarchy.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"GASFUEL","description":"A real value that defines the gas consumption, that is the fuel gas consumed by the group, either defined as a volumetric rate or as a fraction of the group’s gas production. The two options are implemented by: Volumetric Rate Option: Setting GASFUEL to a value greater than zero will be interpreted as the actual fuel gas rate consumed by the group. Fraction of Produced Gas: Setting GASFUEL to a negative value between minus one and zero will be interpreted as a fraction of the groups production rate. For example, if GASFUEL is entered as -0.05, would mean 5% of the group’s produced gas will be consumed as fuel. This value may be specified using a User Defined Argument (UDA).","units":{"field":"Mscf/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"0.0","value_type":"UDA","dimension":"GasSurfaceVolume/Time"},{"index":3,"name":"GASIMP","description":"A real positive value greater than zero that defines the amount of gas to be imported into the group. This value may be specified using a User Defined Argument (UDA). This option is currently not supported by OPM Flow","units":{"field":"stb/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"0.0","value_type":"UDA","dimension":"GasSurfaceVolume/Time"},{"index":4,"name":"GASNODE","description":"A character string of up to eight characters in length that defines the network node in the Extended Network Model, for which the fuel gas should be removed (GASFUEL) or the imported gas (GASIMP) assigned. This option is currently not supported by OPM Flow","units":{},"default":"None","value_type":"STRING"}],"example":"The first example sets the fuel gas consumption to 3.0 MMscf/d for the field.\n--\n-- GROUP GAS CONSUMPTION (FUEL) AND IMPORT\n--\n-- GRUP GAS GAS\n-- NAME FUEL IMPORT\n-- ------ -------\nGCONSUMP\nFIELD 3.0E3 /\n/\nThe second example sets group PLAT-WST’s fuel consumption to be 5% of the platform’s produced gas and group PLAT-EST’s to a constant 1.0 MMscf/d.\n--\n-- GROUP GAS CONSUMPTION (FUEL) AND IMPORT\n--\n-- GRUP GAS GAS\n-- NAME FUEL IMPORT\n-- ------ -------\nGCONSUMP\nPLAT-WST -0.050 /\nPLAT-EST 1.0E3 /\n/\n| [\"Gas Sales Rate\" ~ = ~ \"Total Group Gas Production Rate\"\nnewline \n~~~~~~~~~~~~~~ - ` \"Group Gas Injection Rate\"\nnewline \n~~~~~~~~~~~~~~~~~~ + ` \"Total Group Gas Import Rate\" \nnewline \n~~~~~~~~~~~~~~~~~~~ - ` \"Total Group Gas Consumption\"] | (12.24) |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|\n| [{ \"Group Gas Injection Rate\" ~ = ~ \"Group Gas Injection Rate\" ` times ` \"Group Re-Injection Fraction\" } newline {~~~~ + ` \"Total Group Gas Import Rate\" } newline { ~~~~~ - ` \"Total Group Gas Consumption\" }] | (12.25) |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|\n| Note In oil fields with no gas compression typical values of fuel gas range from three to five percent. |\n|---------------------------------------------------------------------------------------------------------|","expected_columns":4,"size_kind":"list"},"GCONTOL":{"name":"GCONTOL","sections":["SCHEDULE"],"supported":false,"summary":"The GCONTOL keyword defines the tolerance and parameters used to control the accuracy of group targets and constraints, including the field’s targets and constraints. The keyword sets the tolerance and number of Newton iterations for each time step so that the wells under group control can match the desired group targets and constraints.","parameters":[{"index":1,"name":"GRPCNV","description":"GRPCNV is a real positive value less than one that sets the group tolerance criteria used to define if convergence has been satisfied for group’s under rate control. Here, GRPCNV is an acceptable fraction of the group’s rate target. Thus, the a numerical quantity 0.01 means that values must be with 0.01 (or 1.0%) of the groups’ production target. For groups under priority control, as per GCONPRI keyword in the SCHEDULE section, GRPCNV is ignored. Note that this criteria may not be satisfied if the number of Newton iterations used in updating the well targets, as set by the NUPCOL keyword in the RUNSPEC section, or the NUPCOL parameter on this keyword, is exceeded. In this case, and only if the well potentials allow, the well rates are re-calculated ignoring the NUPCOL limit. Group tolerance criteria can also be set by the GRPCNV parameter on the NETBALAN keyword in the SCHEDULE section. If both values of GRPCNV have been entered, then the minimum of the two is used. The default value means there is no convergence criteria.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0 x 1020","value_type":"DOUBLE"},{"index":2,"name":"NUPCOL","description":"A positive integer that defines the maximum number of Newton iterations used to update well targets within a time step. Wells under group control may suffer from some dependency with other wells in the same group that are under group control. This may cause some oscillation in the production and injection well rates within the group. In order to avoid this, after the number Newton iterations within a time step surpasses NUPCOL, the group well rates are frozen until the time step has converged. Reducing the potential of well rate oscillations within the time step may result in the group targets and limits not being exactly being met in this case. Increasing the value of NUPCOL will improve the accuracy of the group targets and limits at the expense of computational efficiency. NUPCOL can also be set by the NUPCOL keyword in the RUNSPEC section. A value entered on this keyword overwrites any previously entered values of NUPCOL, including the value set by the NUPCOL keyword. The default value of 1* invokes the last previously entered value of either by the NUPCOL keyword or this keyword.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1*","value_type":"INT"},{"index":3,"name":"GASCNV","description":"In the commercial compositional simulator GASCNV is a real positive value less than one that sets the tolerance criteria used to define if convergence has been satisfied for well gas injection rates. GASCNV is also used in conjunction with well availability gas fraction quantities in the commercial compositional simulator The value is ignored by OPM Flow.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0 x 10-3","value_type":"DOUBLE"},{"index":4,"name":"GASMXITE","description":"In the commercial compositional simulator GASMXITE is a positive integer value that defines the maximum number of iterations for the gas injection computation. The value is ignored by OPM Flow.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"5","value_type":"INT"}],"example":"The example sets the group target convergence criteria to 1% (0.01) with a maximum of four Newton iterations (NUPCOL).\n--\n-- GROUP CONSTRAINT TOLERANCE\n--\n-- GROUP NEWTON INJEC NEWTON\n-- TOL ITERS TOL ITERS\n-- ----- ----- ----- ------\nGCONTOL\n0.01 4 1* 1* /","expected_columns":4,"size_kind":"fixed","size_count":1},"GCUTBACK":{"name":"GCUTBACK","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, GCUTBACK, defines a production group’s cutback limits and parameters. See also the WCUTBACK keyword in the SCHEDULE section that provides similar functionality for wells.","parameters":[{"index":1,"name":"GROUP_NAME","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"WATER_CUT_UPPER_LIM","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"GAS_OIL_UPPER_LIM","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":4,"name":"GAS_LIQ_UPPER_LIM","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":5,"name":"WAT_GAS_UPPER_LIM","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":6,"name":"RATE_CUTBACK_FACTOR","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":7,"name":"CONTROL_PHASE","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":7,"size_kind":"list"},"GCUTBACT":{"name":"GCUTBACT","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, GCUTBACT, defines a production group’s cutback limits and parameters based on the named produced tracer from the group. See also the WCUTBACT keyword in the SCHEDULE section that provides similar functionality for groups.","parameters":[],"example":"","size_kind":"none","size_count":0},"GDCQ":{"name":"GDCQ","sections":["SCHEDULE"],"supported":false,"summary":"The GDCQ keyword defines the Daily Contract Quantities (“DCQ”) for when multiple group contracts are required when the Gas Field Operations model has been activated by the GASFIELD keyword in the RUNSPEC section, or the GWSINGF has been invoked to define multiple group contracts in the SCHEDULE section. The group contracts must first be defined by the GSWINGF keyword, followed by the GCDQ keyword, and then the GASYEAR or GASPERIO keywords. GCDQ may be repeated in the SCHEDULE section to reset group DCQs.","parameters":[{"index":1,"name":"GROUP_NAME","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"INIT_DCQ","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":3,"name":"DCQ_TYPE","description":"","units":{},"default":"VAR","value_type":"STRING"}],"example":"","expected_columns":3,"size_kind":"list"},"GDCQECON":{"name":"GDCQECON","sections":["SCHEDULE"],"supported":false,"summary":"The GDCQECON keyword defines economic criteria for DCQ production groups, including the field level group FIELD, that have previously been defined by the GCONPROD keywords in the SCHEDULE section. Note that wells are allocated to a group when they are specified by the WELSPECS keyword and wells can also have economic controls. Wells under group control are therefore subject to the economic criteria set via the GCONPROD and CECON keywords in the SCHEDULE section and the controls specified by the WECON keyword.","parameters":[{"index":1,"name":"GRPNAME","description":"A character string of up to eight characters in length that defines the group name for which the group target and constraints are being defined. The group named FIELD is the top most group and should be used to set targets and constraints for the field. Note that the group hierarchy should be defined by the GRUPTREE keyword when there is more than one level of groups, otherwise all the groups will sit directly under the FIELD group in the group tree hierarchy.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"DCQ","description":"A real positive value that defines the minimum economic DCQ gas production rate, below which an economic action of shutting in or stopping all the wells in the group, as requested by item (9) of the WELSPECS keyword. Note if GRPNAME is equal to FIELD then the run will be terminated. A value less than or equal to zero switches of this criteria.","units":{"field":"Mscf/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"0.0","value_type":"DOUBLE"}],"example":"The following example defines the minimum DCQ for the field to be 10 MMscf/d.\n--\n-- GROUP ECONOMIC CRITERIA FOR DCQ PRODUCTION GROUPS\n--\n-- GRUP GAS\n-- NAME DCQ\nGDCQECON\nFIELD 10E3 /\n/","expected_columns":2,"size_kind":"list"},"GDRILPOT":{"name":"GDRILPOT","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, GDRILPOT, defines the minimum group potential rate that will result in a well from the one of the automatic drilling queues, as defined by either the QDRILL or WDRILPRI keywords in the SCHEDULE section, to be drilled and placed on production. The advantage of using a group’s potential, as oppose to a minimum rate limit, is that setting the potential greater than the group’s minimum flow rate, will result in well being drilled in time to support the desired production rate.","parameters":[{"index":1,"name":"GROUP_NAME","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"QNTY_TYPE","description":"","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"MIN_POTENTIAL_RATE","description":"","units":{},"default":"0","value_type":"DOUBLE"}],"example":"","expected_columns":3,"size_kind":"list"},"GECON":{"name":"GECON","sections":["SCHEDULE"],"supported":true,"summary":"The GECON keyword defines economic criteria for production groups, including the top level FIELD group, that have been created by having wells assigned to them via the WELSPECS keyword in the SCHEDULE section.","parameters":[{"index":1,"name":"GRPNAME","description":"A character string of up to eight characters in length that defines the group name for which the group target and constraints are being defined. The group named FIELD is the top most group and should be used to set targets and constraints for the field. Note that the group hierarchy should be defined by the GRUPTREE keyword when there is more than one level of groups, otherwise all the groups will sit directly under the FIELD group in the group tree hierarchy.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"ORAT","description":"A real positive value that defines the minimum economic surface oil production rate, below which an economic action of shutting in or stopping all the wells in the group, as requested by the AUTO variable item (9) of the WELSPECS keyword. This value may be specified using a User Defined Argument (UDA). A value less than or equal to zero switches off this criteria.","units":{"field":"stb/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"0.0","value_type":"UDA","dimension":"LiquidSurfaceVolume/Time"},{"index":3,"name":"GRAT","description":"A real positive value that defines the minimum economic surface gas production rate, below which an economic action of shutting in or stopping all the wells in the group, as requested by the AUTO variable item (9) of the WELSPECS keyword. This value may be specified using a User Defined Argument (UDA). A value less than or equal to zero switches off this criteria,","units":{"field":"Mscf/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"0.0","value_type":"UDA","dimension":"GasSurfaceVolume/Time"},{"index":4,"name":"WCUT","description":"A real positive value that defines the maximum economic surface water cut, above which an economic action will take place. This value may be specified using a User Defined Argument (UDA). Water cut is defined as:[f sub w ~=~ {q sub w } over {q sub w `+` q sub o}], and the various actions that are available if the water cut limit is exceeded are described in item (7)., and the various actions that are available if the water cut limit is exceeded are described in item (7). A value less than or equal to zero switches off this criteria.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.0","value_type":"UDA"},{"index":5,"name":"GOR","description":"A real positive value that defines the maximum economic surface gas-oil ratio, above which an economic action will take place, as defined by item (7). This value may be specified using a User Defined Argument (UDA). A value less than or equal to zero switches off this criteria.","units":{"field":"Mscf/stb","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"0.0","value_type":"UDA"},{"index":6,"name":"WGR","description":"A real positive value that defines the maximum economic surface water-gas ratio, above which an economic action will take place, as defined by item (7). This value may be specified using a User Defined Argument (UDA). A value less than or equal to zero switches off this criteria.","units":{"field":"stb/Mscf","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"0.0","value_type":"UDA"},{"index":7,"name":"ACTION","description":"A defined character string that defines the action to be taken if the economic WCUT, GOR, or WGR limits are violated. ACTION should be set to one of the following character strings: NONE: no action is taken. CON: close the worst offending connection in the worst offending well. If connections have been grouped as completions then the worst offending completion will be closed. +CON: close the worst offending connection and all below it in the worst offending well. If connections have been grouped as completions then the worst offending completion and all below it will be closed. WELL: shut or stop the worst offending well as per the AUTO variable on the WELSPECS keyword. PLUG: plug back the worst offending well based on the plug back length and options defined on the WPLUG keyword in the SCHEDULE. The corrective action takes places at the end of the time step in which the constraint is violated. Only the NONE option is currently supported by the simulator.","units":{},"default":"None","value_type":"STRING","options":["NONE","CON","WELL","PLUG"]},{"index":8,"name":"END","description":"A defined character string that defines if the simulation should terminate if all the producing wells in the group, including the FIELD group, are shut or stopped. END should be set to one of the following character strings: NO: no action is taken and the run continues. YES: terminate the run at the next report time step. Only the NO option is currently supported by the simulator.","units":{},"default":"NO","value_type":"STRING","options":["NO","YES"]},{"index":9,"name":"MXWELS","description":"A positive integer defining the maximum number of producing and injecting wells for this this group and any subordinate groups. The default value of zero implies that there is no limit to the number of wells. This is not currently supported by the simulator and must be defaulted.","units":{},"default":"0","value_type":"INT"}],"example":"The following example defines the economic criteria for the field with a minimum oil rate of 2,000 m3/day and a maximum water cut of 95%.\n--\n-- GROUP ECONOMIC CRITERIA FOR PRODUCTION GROUPS\n--\n-- GRUP OIL GAS WCT GOR WGR WORK END MAX\n-- NAME MIN MIN MAX MAX MAX OVER RUN WELLS\nGECON\nFIELD 2E3 1* 0.95 1* 1* CON 'YES' 1* /\n/\nIf the economic limits are violated then the run will stop at the next report time step.","expected_columns":9,"size_kind":"list"},"GECONT":{"name":"GECONT","sections":["SCHEDULE"],"supported":false,"summary":"The GECONT keyword defines tracer economic criteria for production groups, including the field level group FIELD, that have previously been defined by the GCONPROD keywords in the SCHEDULE section, for tracers define by the TRACER keyword in the PROPS section.","parameters":[{"index":1,"name":"GRPNAME","description":"A character string of up to eight characters in length that defines the group name for which the group target and constraints are being defined. The group named FIELD is the top most group and should be used to set targets and constraints for the field. Note that the group hierarchy should be defined by the GRUPTREE keyword when there is more than one level of groups, otherwise all the groups will sit directly under the FIELD group in the group tree hierarchy.","units":{},"default":"None","record":1},{"index":2,"name":"ACTION","description":"A defined character string that defines the action to be taken if the economic WCUT, GOR, or WGR limits are violated. ACTION should be set to one of the following character strings: NONE: no action is taken. CON: close the worst offending connection in the worst offending. If connections have been grouped as completions then the worst offending completion will be closed. +CON: close the worst offending connection and all below it in the worst offending well. If connections have been grouped as completions then the worst offending completion and all below it in the worst offending well will be closed. WELL: shut or stop the well as per the AUTO variable on the WELSPECS keyword. PLUG: plug back the worst offending well based on the plug back length and options defined on the WPLUG keyword in the SCHEDULE. The corrective action takes places at the end of the time step in which the constraint is violated.","units":{},"default":"None","record":1},{"index":3,"name":"END","description":"A defined character string that defines if the simulation should terminate if all the producing wells in the group, including the FIELD group, are shut or stopped. END should be set to one of the following character strings: NO: no action is taken and the run continues. YES: terminate the run at the next report time step.","units":{},"default":"NO","record":1},{"index":4,"name":"MXWELS","description":"A positive integer defining the maximum number of producing and injecting wells for this group and any subordinate groups. The default value of zero implies that there is no limit to the number of wells.","units":{},"default":"0","record":1},{"index":1,"name":"NAME","description":"A three letter character string defining the tracer’s name. Note it is best to void names beginning with the letters F, S, and T as these names may create naming issues in post-processing software.","units":{},"default":"None","record":2},{"index":2,"name":"MXTOTAL","description":"A real positive value that defines the maximum total (free plus solution) tracer rate. Tracer units are per those defined by the carrying fluid, oil, gas, water, etc.","units":{},"default":"None","record":2},{"index":3,"name":"MXFREET","description":"A real positive value that defines the maximum total (free plus solution) tracer concentration. Tracer units are per those defined by the carrying fluid, oil, gas, water, etc.","units":{},"default":"None","record":2},{"index":4,"name":"MXFREEQ","description":"A real positive value that defines the maximum free tracer rate. Tracer units are per those defined by the carrying fluid, oil, gas, water, etc.","units":{},"default":"None","record":2},{"index":5,"name":"MXCONC","description":"A real positive value that defines the maximum free tracer concentration. Tracer units are per those defined by the carrying fluid, oil, gas, water, etc.","units":{},"default":"None","record":2},{"index":6,"name":"MXSOLNQ","description":"A real positive value that defines the maximum solution rate. Tracer units are per those defined by the carrying fluid, oil, gas, water, etc.","units":{},"default":"None","record":2},{"index":7,"name":"MXSOLNC","description":"A real positive value that defines the maximum solution concentration. Tracer units are per those defined by the carrying fluid, oil, gas, water, etc.","units":{},"default":"None","record":2}],"example":"The following example defines the tracer economic criteria for the field and two groups, FLTBLK1 and FLTBLK,.\n--\n-- GROUP TRACER ECONOMIC CRITERIA FOR PRODUCTION GROUPS\n--\n-- GRUP WORK END MAX\n-- NAME OVER RUN WELLS\nGECONT\nFIELD +CON 'YES' 1* / START OF GROUP\n--\n-- TRACER TRACER TRACER TRACER TRACER TRACER TRACER\n-- NAME TOTAL TOTAL FREE FREE SOLN SOLN\n-- RATE CONCEN RATE CONCEN RATE CONCEN\nPLY 1000.0 /\nBRI 1000.0 /\nTR1 1* 0.7500 /\n/\nFLTBLK1 +CON 'YES' 1* / START OF GROUP\n--\n-- TRACER TRACER TRACER TRACER TRACER TRACER TRACER\n-- NAME TOTAL TOTAL FREE FREE SOLN SOLN\n-- RATE CONCEN RATE CONCEN RATE CONCEN\nPLY 800.0 /\nBRI 800.0 /\n/\nFLTBLK2 +CON 'YES' 1* / START OF GROUP\n--\n-- TRACER TRACER TRACER TRACER TRACER TRACER TRACER\n-- NAME TOTAL TOTAL FREE FREE SOLN SOLN\n-- RATE CONCEN RATE CONCEN RATE CONCEN\nPLY 800.0 /\nBRI 800.0 / END OF GROUP\n/ END OF KEYWORD\nIf the economic limits are violated then the worst offending connection and all below it in the worst offending well will be closed, If connections have been grouped as completions then the worst offending completion and all below it in the worst offending well will be closed.","size_kind":"none","size_count":0},"GEFAC":{"name":"GEFAC","sections":["SCHEDULE"],"supported":null,"summary":"Defines a group’s efficiency or up-time factor as opposed to setting the efficiency factors for individual wells.","parameters":[{"index":1,"name":"GRPNAME","description":"A character string of up to eight characters in length that defines the group name for which the group efficiency factor is being defined. The group named FIELD is the top most group and cannot have an efficiency factor set. Note that the group hierarchy should be defined by the GRUPTREE keyword when there is more than one level of groups, otherwise all the groups will sit directly under the FIELD group in the group tree hierarchy.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"FACTOR","description":"A real positive value less than or equal to one that defines the efficiency factor for the group. If a group’s down time is 5% then FACTOR should be set to 0.95 (1.0 – 0.05).","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0","value_type":"DOUBLE"},{"index":3,"name":"GRPNETWK","description":"A defined character string that determines if the GRPNAME efficiency factor should be transferred to the equivalent Extended Network Model node, and should be set to either: NO:The group’s equivalent Extended Network Model node flow rates are not multiplied by the efficiency factor FACTOR. YES:The group’s equivalent Extended Network Model node flow rates are multiplied by the efficiency factor FACTOR This option is only applicable for the Extended Network Model. In the Standard Network Model groups' reported flow rates are always used in the calculation of pressure drops.","units":{},"default":"YES","value_type":"STRING"}],"example":"--\n-- GROUP EFFICIENCY FACTORS\n--\n-- GRUP EFF NETWK\n-- NAME FACT OPTN\n-- ------ ------\nGEFAC\nPLATFORM 0.950 /\nSUBSEA1 0.860 /\n/\nIn the above example the group PLATFORM has its up-time factor set to 95% and the subsea group SUBSEA1 has an up-time factor of 86%.","expected_columns":3,"size_kind":"list"},"GLIFTLIM":{"name":"GLIFTLIM","sections":["SCHEDULE"],"supported":false,"summary":"The GLIFTLIM keyword defines the maximum number of wells on artificial lift and the maximum amount of the artificial lift that is available for a group, including the top most group in the group hierarchy known as the FIELD group. Wells are allocated to groups when the wells are specified by the WELSPECS keyword in the SCHEDULE section. Wells defined to be under group control will have their production rates controlled by the group to which they belong, in addition to any well constraints defined for the wells.","parameters":[{"index":1,"name":"GRPNAME","description":"A character string of up to eight characters in length that defines the group name for which the group’s artificial lift constraints are being defined. The group named FIELD is the top most group and should be used to set targets and constraints for the field. Note that the group hierarchy should be defined by the GRUPTREE keyword when there is more than one level of groups, otherwise all the groups will sit directly under the FIELD group in the group tree hierarchy.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"MXLIFT","description":"A real positive value that defines the total amount of artificial lift available for this group and any subordinate groups. The units for MXLIFT are the same as that defined by the ALQ parameter on the VFPPROD keyword in the SCHEDULE section. For example, if ALQ has been set to GRAT on the VFPPROD keyword, then MXLIFT would be the maximum amount of gas lift gas available for this group and any subordinate groups, and the units would Mscf, assuming FIELD units had been activated in the RUNSPEC section. The default value of zero implies that there is no limit applied to the group and its subordinate groups.","units":{"field":"See VFPPROD (ALQ)","metric":"See VFPPROD (ALQ)","laboratory":"See VFPPROD (ALQ)"},"default":"0","value_type":"DOUBLE"},{"index":3,"name":"MXWELS","description":"A positive integer defining the maximum number of producing wells on artificial lift for this group and any subordinate groups. The default value of zero implies that there is no limit to the number of wells.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0","value_type":"INT"}],"example":"The following example defines the artificial lift constraints for the field, assuming all the wells are on gas lift.\n---\n-- GROUP ARTIFICIAL LIFT CONSTRAINTS\n--\n-- GRUP MAX MAX\n-- NAME ALQ WELLS\nGLIFTLIM\nFIELD 20E3 20 /\n/\nHere the maximum amount of gas lift gas for the field is set to 20.0 MMscf/f and a maximum of 20 wells can utilize gas lift at a time.","expected_columns":3,"size_kind":"list"},"GLIFTOPT":{"name":"GLIFTOPT","sections":["SCHEDULE"],"supported":null,"summary":"The GLIFTOPT keyword defines the maximum amount of gas lift gas available and the maximum amount of gas the group can produce, including the top most group in the group hierarchy known as the FIELD group, for when gas lift optimization has been activated via the LIFTOPT keyword in the SCHEDULE section. Note that the LIFTOPT keyword should precede the GLIFTOPT keyword in the SCHEDULE section in order to activate the gas lift optimization facility.","parameters":[{"index":1,"name":"GRPNAME","description":"A character string of up to eight characters in length that defines the group name for which the group’s gas lift optimization parameters are being defined. The group named FIELD is the top most group and should be used to set targets and constraints for the field. Note that the group hierarchy should be defined by the GRUPTREE keyword when there is more than one level of groups, otherwise all the groups will sit directly under the FIELD group in the group tree hierarchy.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"MXLIFT","description":"A real value that defines the total amount of gas lift gas available for this group and any subordinate groups, multiplied by their respective efficiency factors. The units for MXLIFT are the same as that defined by the ALQ parameter on the VFPPROD keyword in the SCHEDULE section. In this case ALQ should be GRAT on the VFPPROD keyword, as MXLIFT applies to the maximum amount of gas lift gas available. The default value of zero, or a negative value implies that there is no limit applied to the group and its subordinate groups.","units":{"field":"Mscf/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"0","value_type":"DOUBLE","dimension":"GasSurfaceVolume/Time"},{"index":3,"name":"MXGAS","description":"A real value that defines the total amount of gas the group can process. This is the sum of the gas lift gas plus the produced gas for this group and any subordinate groups, multiplied by their respective efficiency factors. The default value of zero, or a negative value implies that there is no limit applied to the group and its subordinate groups","units":{"field":"Mscf/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"0","value_type":"DOUBLE","dimension":"GasSurfaceVolume/Time"}],"example":"The following example first switches on gas lift optimization via the LIFTOPT keyword and then defines the artificial lift constraints for the field, assuming all the well are on gas lift, using the GLIFTOPT keyword.\n-- ACTIVATE GAS LIFT OPTIMIZATION AND PARAMETERS\n--\n-- INCR INCR TSTEP NEWTON\n-- GAS OIL INTVAL OPTN\nLIFTOPT\n12.5E3 5E-3 0.0 YES /\n/\n--\n-- GROUP GAS LIFT OPTIMIZATION CONSTRAINTS\n--\n-- GRUP MAX MAX\n-- NAME GAS ALQ TOTAL GAS\nGLIFTOPT\nFIELD 200E3 1* /\n/\nHere the LIFTOPT keyword defines the maximum incremental gas lift gas quantity to be 12.5 x 103 m3, the minimum incremental oil gain per m3 of gas lift gas is set to 5.0 x 10-3 m3, the time step interval is set to zero to perform the gas optimization every time step, and finally the gas lift optimization will be performed NUPCOL Newton iterations for the time step.\nThe GLIFTOPT sets the maximum amount of gas lift gas for the field to 200,000 m3 and there is no maximum limit for the total maximum amount of gas that the group can process.","expected_columns":3,"size_kind":"list"},"GNETDP":{"name":"GNETDP","sections":["SCHEDULE"],"supported":false,"summary":"The GNETDP keyword sets a group’s minimum and maximum network pressure and rate controls for when the either the Standard Network or the Extended Network options have been activated, and the group is part of a network. The keywords allows for the pressure of the group to vary in order to satisfy the rate conditions declared by this keyword. The Standard Network option is invoked if the GRUPTREE, GRUPNET, GNETINJE, GNETPUMP, etc. series of keywords have been used in the SCHEDULE section. Whereas, the Extended Network option is activated by the NETWORK keyword in the RUNSPEC section. Several keywords, including, GNETDP, can be used by both network options.","parameters":[{"index":1,"name":"FIXED_PRESSURE_GROUP","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"PHASE_TYPE","description":"","units":{},"default":"GA","value_type":"STRING"},{"index":3,"name":"MIN_RATE_TRIGGER","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":4,"name":"MAX_RATE_TRIGGER","description":"","units":{},"default":"1e+20","value_type":"DOUBLE"},{"index":5,"name":"PRESSURE_INCR_SUBTRACT","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Pressure"},{"index":6,"name":"PRESSURE_INCR_ADD","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Pressure"},{"index":7,"name":"MIN_ALLOW_PRESSURE","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Pressure"},{"index":8,"name":"MAX_ALLOW_PRESSURE","description":"","units":{},"default":"1e+20","value_type":"DOUBLE","dimension":"Pressure"}],"example":"","expected_columns":8,"size_kind":"list"},"GNETINJE":{"name":"GNETINJE","sections":["SCHEDULE"],"supported":false,"summary":"The GNETINJE keyword defines the configuration of a group injection network for when the either the Standard Network or the Extended Network options have been activated. The Standard Network option is invoked if the GRUPTREE, GRUPNET, GNETINJE, GNETPUMP, etc. series of keywords have been used in the SCHEDULE section. Whereas, the Extended Network option is activated by the NETWORK keyword in the RUNSPEC section. Several keywords, including, GNETINJE, can be used by both network options.","parameters":[{"index":1,"name":"GROUP","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"PHASE","description":"","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"PRESSURE","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":4,"name":"VFP_TABLE","description":"","units":{},"default":"0","value_type":"INT"}],"example":"","expected_columns":4,"size_kind":"list"},"GNETPUMP":{"name":"GNETPUMP","sections":["SCHEDULE"],"supported":false,"summary":"The GNETPUMP keyword defines the configuration of automatic compressors and pumps in a production Standard Network, for when the Standard Network option is invoked by the GRUPTREE, GRUPNET, GNETINJE, GNETPUMP, etc., series of keywords in the SCHEDULE section. Although several keywords can be used by both the Standard and Extended Network options, GNETPUMP can only be used with the Standard Network option. The equivalent keyword for the Extended Network option is the NETCOMPA keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"GROUP","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"PROD_RATE_SWITCH","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":3,"name":"PHASE_TYPE","description":"","units":{},"default":"OIL","value_type":"STRING"},{"index":4,"name":"NEW_VFT_TABLE_NUM","description":"","units":{},"default":"4","value_type":"INT"},{"index":5,"name":"NEW_ARTIFICIAL_LIFT_QNTY","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":6,"name":"NEW_GAS_CONUMPTION_RATE","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"GasSurfaceVolume/Time"}],"example":"","expected_columns":6,"size_kind":"list"},"GPMAINT":{"name":"GPMAINT","sections":["SCHEDULE"],"supported":null,"summary":"The GPMAINT keyword defines the groups under pressure maintenance control, the associated flow rate and pressure targets, and fluid in-place regions associated with pressure maintenance, as well as various pressure maintenance controls. GPMAINT allows for various regions, as defined by the FIPNUM or FIP keywords in the REGIONS section, to have their average reservoir pressure maintained at a specified value.","parameters":[{"index":0,"name":"","description":"","units":{},"default":""},{"index":0,"name":"","description":"","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":""},{"index":1,"name":"GRPNAME","description":"A character string of up to eight characters in length that defines the group name for which the group’s associated FIPNUM region will have a targeted average reservoir pressure maintained. The group named FIELD is the top most group and can also be used to set pressure target for the whole field. Note that the group hierarchy should be defined by the GRUPTREE keyword when there is more than one level of groups, otherwise all the groups will sit directly under the FIELD group in the group tree hierarchy.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"GRPCNTL","description":"A defined character string of length four, that sets the production or injection control for the group, used to maintain the average pressure for the FIPNUM region. GRPCNTL should be set to one of the following character strings: NONE: the group will no longer maintain the average reservoir pressure for the FIPNUM region by adjusting production and injection rates. GINJ: GRPNAME’s gas in situ reservoir volume injection rate (RESV) will be adjusted in order to maintain FIPNUM’s average reservoir pressure. GINS: GRPNAME’s gas surface rate (GRAT) will be used to maintain FIPNUM’s average reservoir pressure. OINJ: GRPNAME’s oil in situ reservoir volume injection rate (RESV) will be adjusted in order to maintain FIPNUM’s average reservoir pressure. OINS: GRPNAME’s oil surface rate (ORAT) will be used to maintain FIPNUM’s average reservoir pressure. PROD: GRPNAME’s total in situ reservoir volume production rate (RESV) will be adjusted in order to maintain FIPNUM’s average reservoir pressure. Note that group cannot be under prioritization group control, as per the GCONPRI keyword in the SCHEDULE section, with this option. WINJ: GRPNAME’s water in situ reservoir volume injection rate (RESV) will be adjusted in order to maintain FIPNUM’s average reservoir pressure WINS: GRPNAME’s water surface rate (WRAT) will be used to maintain FIPNUM’s average reservoir pressure.","units":{},"default":"None","value_type":"STRING"},{"index":3,"name":"REGION","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"FIPNAME","description":"A character string of up to five characters in length, defining the fluid in-place’s name, as defined by the FIP keyword in the REGIONS section. For example, if the FIP keyword has been used to define a FIP group or family, named FIPBLK-A, then FIPNAME would be set to BLK-A. The default value of 1* means that FIPNUM on this keyword applies to the standard FIPNUM array and not to the FIP defined group regions.","units":{},"default":"1*","value_type":"STRING"},{"index":5,"name":"PRESSURE_TARGET","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":6,"name":"ALPHA","description":"A real positive value that defines the proportionality constant used to control the flow rates in order to maintain/reach the TARGET average hydrocarbon pore volume pressure for the region. See equation (12.26). Larger values of ALPHA accelerate the time for the region’s pressure to satisfy the required target pressure (TARGET). However, ALPHA values that are too large may cause the region’s pressure to oscillate. Thus, the value of ALPHA should be a value that gives the expected steady state flow rate (TARGET) of the group divided by a reasonable transient pressure error.","units":{"field":"Liquid: stb/d/psi Gas: Mscf/d/psi RESV: rb/d/psi","metric":"Liquid: sm3/day/bars Gas: sm3/day/bars RESV: rm3/day/bars","laboratory":"Liquid: scc/hour/atm Gas: scc/hour/atm RESV: rcc/hour/atm"},"default":"None","value_type":"DOUBLE","dimension":"ReservoirVolume/Time*Pressure"},{"index":7,"name":"BETA","description":"A real positive value that defines the time interval used to control the flow rates in order to maintain the TARGET average hydrocarbon pore volume pressure for the region. See equation (12.26). Larger values of BETA reduce the tendency for the regional pressure to oscillate, but consequently decrease the rate at which the pressure reaches its target value. This is because the pressure error is measured at the end of the previous time step, resulting in a “delay” in the response. Also, the larger the time steps the greater the propensity for the pressure to oscillate for given ALPHA and BETA. As a guide BETA should be set to a value that is at least as large as the maximum time step size (see the TUNING keyword in the SCHEDULE section and section 2.2Running OPM Flow 2023-04 From The Command Linefor setting the maximum time step size).","units":{"field":"day","metric":"day","laboratory":"day"},"default":"1*","value_type":"DOUBLE","dimension":"Time"}],"example":"The first example uses the gas surface rate to maintain the fields’ average hydrocarbon pore volume pressure at 225 barsa, with the ALPHA and BETA parameters set to 40.0 and 70.0 respectively.\n--\n-- GROUP PRESSURE MAINTENANCE TARGETS AND CONTROLS\n--\n-- GRUP CNTL FIPNUM FIP PRESS ALPHA BETA\n-- NAME MODE REGION FIPNAME TARGET CONST CONST\nGPMAINT\nFIELD GINS 0 1* 225 40.0 70.0 /\n/\nThe second example uses group’s BLK-A gas surface rate to maintain the average hydrocarbon pore volume pressure at 200 barsa for FIPNUM regions one to four, with the ALPHA and BETA parameters set to 40.0 and 70.0 respectively.\n--\n-- GROUP PRESSURE MAINTENANCE TARGETS AND CONTROLS\n--\n-- GRUP CNTL FIPNUM FIP PRESS ALPHA BETA\n-- NAME MODE REGION FIPNAME TARGET CONST CONST\nGPMAINT\nBLK-A GINS 1 1* 200 40.0 70.0 /\nBLK-A GINS 2 1* 200 40.0 70.0 /\nBLK-A GINS 3 1* 200 40.0 70.0 /\nBLK-A GINS 4 1* 200 40.0 70.0 /\nBLK-B WINJ 1 FLT-B 215 30.0 65.0 /\nBLK-B WINJ 2 FLT-B 215 30.0 65.0 /\nBLK-B WINJ 3 FLT-B 215 30.0 65.0 /\nBLK-B WINJ 4 FLT-B 215 30.0 65.0 /\n/\nFor group BLK-B, water in situ reservoir volume injection rate (RESV) is used to maintain FIP group/family FLT-B’s average reservoir pressure at 215 barsa for FIPFLT-B regions one to four. Here the ALPHA and BETA parameters set to 30.0 and 65.0 respectively.\n| 0 |\n|---|\n| 0 |\n|---|\n| [Q~=~Q_i``+`` %alpha `` left( left(P_TARGET``-``P_{i-1} right)``+`` sum from{i=1} to{i-1} {left(P_TARGET``-``P_{i-1} right) times %DELTA t_i} over %beta right )] | (12.26) |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|","expected_columns":7,"size_kind":"list"},"GRADGRUP":{"name":"GRADGRUP","sections":["SCHEDULE"],"supported":false,"summary":"The GRADGRUP keyword defines the SUMMARY field and group vectors that should be written to the History Match Gradient output file, for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"MNENONIC","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"list"},"GRADRESV":{"name":"GRADRESV","sections":["SCHEDULE"],"supported":false,"summary":"The GRADRESV keyword defines the SOLUTION derivative arrays that should be written to the History Match Gradient output file, for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"MNENONIC","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"list"},"GRADRFT":{"name":"GRADRFT","sections":["SCHEDULE"],"supported":false,"summary":"The GRADRFT keyword defines the derivative well RFT data, the SOLUTION pressure and saturations at a well’s connected grid block, that should be written to the History Match Gradient output file, for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"MNENONIC","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"list"},"GRADWELL":{"name":"GRADWELL","sections":["SCHEDULE"],"supported":false,"summary":"The GRADWELL keyword defines the SUMMARY well vectors that should be written to the History Match Gradient output file, for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"MNENONIC","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"list"},"GRDREACH":{"name":"GRDREACH","sections":["SCHEDULE"],"supported":false,"summary":"The GRDREACH keyword defines the location of grid blocks connecting to a previously defined river, for when the River option has been activated via the RIVRDIMS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"RIVER","description":"","units":{},"default":"","value_type":"STRING","record":1},{"index":1,"name":"I","description":"","units":{},"default":"","value_type":"INT","record":2},{"index":2,"name":"J","description":"","units":{},"default":"","value_type":"INT","record":2},{"index":3,"name":"K","description":"","units":{},"default":"","value_type":"INT","record":2},{"index":4,"name":"BRANCH_NAME","description":"","units":{},"default":"","value_type":"STRING","record":2},{"index":5,"name":"DISTANCE_TO_START","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length","record":2},{"index":6,"name":"DISTANCE_TO_END","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length","record":2},{"index":7,"name":"RCH_CONNECT_TO","description":"","units":{},"default":"","value_type":"INT","record":2},{"index":8,"name":"PENETRATION_DIRECTION","description":"","units":{},"default":"","value_type":"STRING","record":2},{"index":9,"name":"GRID_BLOCK_COORD","description":"","units":{},"default":"","value_type":"INT","record":2},{"index":10,"name":"CONTACT_AREA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length*Length","record":2},{"index":11,"name":"TABLE_NUM","description":"","units":{},"default":"","value_type":"INT","record":2},{"index":12,"name":"PRODUCTIVITY_INDEX","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Length/Time*Pressure","record":2},{"index":13,"name":"LENGTH_DEAD_GRID_BLOCK","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length","record":2},{"index":14,"name":"OPTION_CONNECT_REACH","description":"","units":{},"default":"0","value_type":"INT","record":2},{"index":15,"name":"ADJUSTMENT_REACH","description":"","units":{},"default":"0","value_type":"INT","record":2},{"index":16,"name":"REMOVE_CAP_PRESSURE","description":"","units":{},"default":"NO","value_type":"STRING","record":2},{"index":17,"name":"INFILTR_EQ","description":"","units":{},"default":"0","value_type":"INT","record":2},{"index":18,"name":"HYDRAULIC_CONDUCTIVITY","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Length/Time","record":2},{"index":19,"name":"RIVER_BED_THICKNESS","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Length","record":2}],"example":"","records_meta":[{"expected_columns":1},{"expected_columns":19}],"size_kind":"list"},"GRUPMAST":{"name":"GRUPMAST","sections":["SCHEDULE"],"supported":false,"summary":"The GRUPMAST keyword defines master groups and their associated slave groups for when the Reservoir Coupling option as been activated by the GRUPMAST and SLAVES keywords in the SCHEDULE section. Reservoir coupling allows for independent reservoir simulation decks (SLAVES) to be controlled by a separate master run file. For example, if there are five separate reservoir models each representing one field, one of the four would be used as the master and the other four would be the subordinate SLAVES.","parameters":[{"index":1,"name":"MASTER_GROUP","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"SLAVE_RESERVOIR","description":"","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"SLAVE_GROUP","description":"","units":{},"default":"","value_type":"STRING"},{"index":4,"name":"LIMITING_FRACTION","description":"","units":{},"default":"1e+20","value_type":"DOUBLE","dimension":"1"}],"example":"","expected_columns":4,"size_kind":"list"},"GRUPNET":{"name":"GRUPNET","sections":["SPECIAL","SCHEDULE"],"supported":true,"summary":"I don’t think this is supported.","parameters":[{"index":1,"name":"GRPNAME","description":"A character string of up to eight characters in length that defines the group name for which the network parameters are being defined. The group named FIELD is the top most group and may be used as a GRPNAME.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"PRES","description":"A real value that defines the fixed pressure for this group when the group is a terminating group. If the group is not a terminating group then PRES should be defaulted with 1* or set to a negative number.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1*","value_type":"DOUBLE","dimension":"Pressure"},{"index":3,"name":"VFPTAB","description":"A positive integer greater than or equal to zero that defines the VFPPROD or VFPINJ vertical lift performance table to be used for calculating the pipeline pressures connecting the LOWER and HIGHER groups in the network. Note that: The default value of zero implies that there is no pipeline connecting the LOWER and HIGHER groups. If PRES is set to a real positive number then VFPTAB should be set to zero as this implies that GRPNAME is a terminating group and therefore there is no pipeline connecting GRPNAME to a HIGHER group. If PRES and VFPTAB are defaulted with 1* or zero, then GRPNAME is not part of the network. IF VFPTAB is set equal to 9999 then this implies that there is no pressure change between the LOWER and HIGHER group. If a non-zero value is entered then the vertical lift performance tables must be entered via the VFPPROD or VFPINJ keyword in the SCHEDULE section.","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"ALQ-PIPE","description":"A real positive value that defines the artificial lift quantity to be used in conjunction with the vertical lift performance table (VFPPROD) assigned to the group via VPFTAB variable. The vertical lift performance table and the artificial lift quantity ALQ-WELL are used with the pipeline fluid rates to calculate the pipeline change pressure between the LOWER and HIGHER groups. Note that the units for ALQ-PIPE are dependent on the associated variable on the VFPPROD keyword and may represent a pump or a compressor depending how the VFPPROD table was generated by an external program.","units":{},"default":"0.0","value_type":"DOUBLE"},{"index":5,"name":"OPTION1","description":"A defined character string that defines if a group’s production target should be achieved by adjusting the tubing pressure of the wells within the group or by the adjusting the well rates by their guide rate. OPTION1 should be set to one of the following character strings: YES: the group production target is achieved by adjusting the tubing pressure of the wells within the group, so that all wells flow at the same tubing head pressure. This is normally used for wells that flow into a common manifold, for example a sub-sea completion manifold. If a group is using this option and has a higher group with production targets or constraints, then this group should have it’s guide rate set via the GCONPROD keyword in the SCHEDULE section, to ensure that the well’s within this group operate at the same tubing head pressure. NO: the group production target is achieved by adjusting the guide rates of the wells within the group. This is the standard method in matching group targets and may result with the wells within the having different tubing head pressures. Only groups containing wells can use OPTION1 equal to YES or NO, a group without wells should set OPTION1 to NO. Numerical convergence controls and iteration limits for wells using OPTION1 set equal to YES are defined via the NETBALAN keyword in the SCHEDULE section. Only the NO option is currently supported by the simulator.","units":{},"default":"NO","value_type":"STRING","options":["YES","NO"]},{"index":6,"name":"OPTION2","description":"A defined character string that defines if well gas lift gas flows through the group’s pipeline. OPTION2 should be set to one of the following character strings: NO: no well gas lift gas is allowed to flow through the pipeline only produced reservoir gas is allowed to flow through the pipeline. FLO: the well gas lift gas is added to the gas flow along the pipeline. The well gas lift gas is the sum of the calculated ALQ-WELL values for all the subordinate wells multiplied by their efficiency factors. ALQ: the pipeline gas lift gas value (ALQ-PIPE) is the sum of the calculated ALQ-WELL values for all the subordinate wells multiplied by their efficiency factors. This means that the ALQ-PIPE gas lift gas value declared on item (4) is ignored. If either FLO or ALQ have been selected then artificial lift quantity for the pipeline (ALQ-PIPE) and the wells (ALQ-WELL) must be defined as gas lift gas on the VFPPROD tables. A well’s specific gas lift gas quantity is set via the ALQ-WELL variable on the WCONPROD keyword in the SCHEDULE section. Only the NO and FLO options are currently supported by the simulator.","units":{},"default":"NO","value_type":"STRING","options":["NO","FLO","ALQ"]},{"index":7,"name":"OPTION3","description":"A defined character string that defines if the ALQ-PIPE variable should be reset to an equivalent surface oil or gas density flowing along the pipeline. OPTION3 should be set to one of the following character strings: DENO: set ALQ-PIPE to the average surface density of the oil flowing along the pipeline. DENG: set ALQ-PIPE to the average surface density of the gas flowing along the pipeline. NONE: no change to ALQ-PIPE. If either DENO or DENG have been selected then artificial lift quantity on the VFPPROD tables must be based on the same density parameter. These options are normally used when a mixture of oil or gas with different surface densities flows into the network. Only the NONE option is currently supported by the simulator.","units":{},"default":"NONE","value_type":"STRING","options":["DENO","DENG","NONE"]}],"example":"The following example defines a network based on two groups\n--\n-- DEFINE GROUP STANDARD NETWORK PARAMETERS\n--\n-- GRUP CNTL VFP PUMP MANIFOLD INCLUDE ALQ\n-- NAME PRES TABLE POWER GROUP LIFT GAS DENS\nGRUPNET\nPROD-A 1200. 1* /\nPROD-B 1* 1 1* 'YES' 1* 1* /\n/\nThe next example is more complex and is taken form the Norne model.\n--\n-- DEFINE GROUP STANDARD NETWORK PARAMETERS\n--\n-- GRUP CNTL VFP PUMP MANIFOLD INCLUDE ALQ\n-- NAME PRES TABLE POWER GROUP LIFT GAS DENS\nGRUPNET\nFIELD 20.0 5* /\nPROD 20.0 5* /\nMANI-B2 1* 8 1* NO 2* /\nMANI-B1 1* 8 1* NO 2* /\nMANI-K1 1* 9999 4* /\nB1-DUMMY 1* 9999 4* /\nMANI-D1 1* 8 1* NO 2* /\nMANI-D2 1* 8 1* NO 2* /\nMANI-K2 1* 9999 4* /\nD2-DUMMY 1* 9999 4* /\nMANI-E1 1* 9 1* NO 2* /\nMANI-E2 1* 9 4* /\n/\nHere the FIELD controlling pressure is set at 20 barsa and the same limit is used for group PROD which sits directly under the FIELD group (see Figure 12.4).","expected_columns":7,"size_kind":"list"},"GRUPRIG":{"name":"GRUPRIG","sections":["SCHEDULE"],"supported":false,"summary":"Defines a groups drilling and workover specifications.","parameters":[{"index":1,"name":"GROUP","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"WORKOVER_RIG_NUM","description":"","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"DRILLING_RIG_NUM","description":"","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"ADD_OR_REMOVE","description":"","units":{},"default":"ADD","value_type":"STRING"}],"example":"","expected_columns":4,"size_kind":"list"},"GRUPSLAV":{"name":"GRUPSLAV","sections":["SCHEDULE"],"supported":false,"summary":"The GRUPSLAV keyword defines slave groups in a slave input deck and their associated master groups in the master run, for when the Reservoir Coupling option as been activated by the GRUPMAST and SLAVES keywords in the SCHEDULE section. This keyword is required for every slave input deck. Reservoir coupling allows for independent reservoir simulation decks (SLAVES) to be controlled by a separate master run file. For example, if there are five separate reservoir models each representing one field, one of the four would be used as the master and the other four would be the subordinate SLAVES.","parameters":[{"index":1,"name":"SLAVE_GROUP","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"MASTER_GROUP","description":"","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"OIL_PROD_CONSTRAINTS","description":"","units":{},"default":"MAST","value_type":"STRING"},{"index":4,"name":"WAT_PROD_CONSTRAINTS","description":"","units":{},"default":"MAST","value_type":"STRING"},{"index":5,"name":"GAS_PROD_CONSTRAINTS","description":"","units":{},"default":"MAST","value_type":"STRING"},{"index":6,"name":"FLUID_VOL_PROD_CONSTRAINTS","description":"","units":{},"default":"MAST","value_type":"STRING"},{"index":7,"name":"OIL_INJ_CONSTRAINTS","description":"","units":{},"default":"MAST","value_type":"STRING"},{"index":8,"name":"WAT_INJ_CONSTRAINTS","description":"","units":{},"default":"MAST","value_type":"STRING"},{"index":9,"name":"GAS_INJ_CONSTRAINTS","description":"","units":{},"default":"MAST","value_type":"STRING"}],"example":"","expected_columns":9,"size_kind":"list"},"GRUPTARG":{"name":"GRUPTARG","sections":["SCHEDULE"],"supported":false,"summary":"The GRUPTARG keyword modifies the target and constraints values of both rates and pressures for previously defined groups without having to define all the variables on the group control keywords: GCONPROD or GCONPRI keywords. Variables not changed by the GRUPTARG keyword remain the same as those previously entered via the group control keywords or previously entered GRUPTARG keywords. Note that the group must still be initially be fully defined using the GCONPROD or GCONPRI keywords. All the aforementioned keywords are described in the SCHEDULE section.","parameters":[{"index":1,"name":"GRPNAME","description":"A character string of up to eight characters in length that defines the group name for which the group target and constraints are being defined. The group named FIELD is the top most group and should be used to set targets and constraints for the field. Note that the group hierarchy should be defined by the GRUPTREE keyword when there is more than one level of groups, otherwise all the groups will sit directly under the FIELD group in the group tree hierarchy.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"TARGET","description":"A defined character string that sets the item to be changed for the group the value of the item is set by item (3). ORAT: reset the surface oil production rate value as defined by item (3). WRAT: reset the surface water production rate value as defined by item (3). GRAT: reset the surface gas production rate value as defined by item (3). LRAT: reset the surface liquid (oil plus water) production rate value as defined by (3). RESV: reset the in situ reservoir volume rate value as defined by (3). GUID: reset the guide rate value for wells operating under group control. Note TARGET only defines the variable to be changed, it does not change how a group is controlled. For example, if a group is operating on ORAT control, as defined by the previously entered GCONPROD keyword, entering TARGET equal to LRAT with a value, changes the liquid constraint but the group still remains on ORAT control. Use the GCONPROD or GCONPRI keywords in the SCHEDULE section to change the control mode of a well.","units":{},"default":"None","value_type":"STRING","options":["ORAT","WRAT","GRAT","LRAT","RESV","GUID"]},{"index":3,"name":"VALUE Liquid Gas Res Vol Pressure","description":"A real positive value that defines the value of the variable declared by TARGET","units":{"field":"stb/d Mscf/d rb/d psia","metric":"sm3/day sm3/day rm3/day barsa","laboratory":"scc/hour scc/hour rcc/hour atma"},"default":"None","value_type":"DOUBLE"}],"example":"The following example below shows the oil rates for the field at the start of the schedule section (January 1, 2000).\n-- ------------------------------------------------------------------------------\n-- 01 JAN 2000 START OF SCHEDULE SECTION\n-- ------------------------------------------------------------------------------\n--\n-- GROUP PRODUCTION CONTROLS\n--\n-- GRUP CNTL OIL WAT GAS LIQ CNTL GRUP GUIDE GUIDE CNTL\n-- NAME MODE RATE RATE RATE RATE OPT CNTL RATE DEF WAT\nGCONPROD\nFIELD ORAT 40E3 60E3 30E3 65E3 1* 1* 1* 1* 1* /\n/ DATES\n01 FEB 2000 /\n/\n--\n-- GROUP PRODUCTION AND INJECTION TARGETS\n--\n-- GROUP GROUP TARGET\n-- NAME TARG VALUE\nGRUPTARG\nFIELD ORAT 45E3 /\nFIELD LIQ 75E3 /\n/\nFrom January 1, 2000 to February 1, 2000 the field is on oil rate control and has a target oil rate of 40,000 stb/d, a maximum water handling capacity of 60,000 stb/d, a maximum liquid capacity of 65,000 stb/d, and a maximum gas constraint of 30 MMscf/d. After February 1, 2000 the field’s target oil rate is increased to 45,000 stb/d and the maximum liquid constraint is increased to 75,000 stb/s; all the other parameters remain unchanged.","expected_columns":3,"size_kind":"list"},"GRUPTREE":{"name":"GRUPTREE","sections":["SCHEDULE"],"supported":null,"summary":"GRUPTREE defines the group hierarchy of groups that have been created by having wells assigned to them via the WELSPECS keyword in the SCHEDULE section, By default three group levels are defined that sets the wells as level three, reporting directly to defined groups at level two, and the level two groups reporting to the FIELD group at level one. If a different configuration is required then the GRUPTREE keyword should be used to define the group hierarchy by defining a lower level group that reports directly to a higher level group.","parameters":[{"index":1,"name":"LOWER","description":"A character string of up to eight characters in length that defines the group name which belongs to the HIGHER group. The group named FIELD is the top most group and should NOT be used as as a group name for the LOWER group name. Undefined group relationships are automatically assigned to the FIELD group.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"HIGHER","description":"A character string of up to eight characters in length that defines the HIGHER group name that the LOWER group belongs to. The group named FIELD is the top most group and can be used as as the HIGHER group name. Undefined group relationships are automatically assigned to the FIELD group.","units":{},"default":"None","value_type":"STRING"}],"example":"The first example defines PLAT01 and PLAT03 reporting to the FIELD level (default if these records are omitted) and PLAT02 reporting to PLAT01.\n--\n-- DEFINE GROUP TREE HIERARCHY\n--\n-- LOWER HIGHER\n-- GROUP GROUP\nGRUPTREE\nPLAT01 FIELD /\nPLAT02 PLAT01 /\nPLAT03 FIELD /\n/\nThe next example is more complex and is taken form the Norne model.\n--\n-- DEFINE GROUP TREE HIERARCHY\n--\n-- LOWER HIGHER\n-- GROUP GROUP\nGRUPTREE\n'INJE' 'FIELD' /\n'PROD' 'FIELD' /\n'MANI-B2' 'PROD' /\n'MANI-B1' 'PROD' /\n'MANI-D1' 'PROD' /\n'MANI-D2' 'PROD' /\n'MANI-E1' 'PROD' /\n'MANI-E2' 'PROD' /\n'MANI-K1' 'MANI-B1' /\n'MANI-K2' 'MANI-D2' /\n'MANI-C' 'INJE' /\n'MANI-F' 'INJE' /\n'WI-GSEG' 'INJE' /\n'B1-DUMMY' 'MANI-B1' /\n'D2-DUMMY' 'MANI-D2' /\n/\nThe group hierarchy for this example is shown below.\n[formula]\n[formula]Figure 12.4: Norne Group Tree Hierarchy Example\nHere groups PROD, INJ, MAN-B1, and MAN-D2 report to higher level groups and the other remaining groups all have individual wells allocated to them instead.","expected_columns":2,"size_kind":"list"},"GSATINJE":{"name":"GSATINJE","sections":["SCHEDULE"],"supported":false,"summary":"The GSATINJE keyword defines a satellite group’s oil, gas and water injection rates in the model. Satellite groups are not connected to the reservoir model and therefore have no wells or subordinate groups associated with them, they are nevertheless connected to other higher level groups and higher level groupswithin a network model (if activated).Thus, they provide a means to “add-in” outside injection and production to the model without modeling the “add-in” reservoirs.","parameters":[{"index":1,"name":"GRPNAME","description":"A character string of up to eight characters in length that defines the satellite group name for which the group injection rates are being defined. The group named FIELD is the top most group and should not be used to define a satellite group. Note that the group hierarchy should be defined by the GRUPTREE keyword in the SCHEDULE section, when there is more than one level of groups, otherwise all the groups will sit directly under the FIELD group in the group tree hierarchy. Note that a satellite group cannot have subordinate groups or wells.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"TYPE","description":"A defined character string that specifies the type of injection fluid. TYPE should be set to one of the following character strings: GAS: for gas injection. OIL: for oil injection. WAT: for water injection. If the satellite group injects more than one phase then the rates should be specified in separate records.","units":{},"default":"None","value_type":"STRING","options":["GAS","OIL","WAT"]},{"index":3,"name":"RATE","description":"A positive real value that defines the surface injection rate for the phase declared by the TYPE variable.","units":{"field":"Liquid: stb/d Gas: Mscf/d","metric":"Liquid: sm3/day Gas: sm3/day","laboratory":"Liquid: scc/hour Gas: scc/hour"},"default":"0.0","value_type":"DOUBLE"},{"index":4,"name":"RESV","description":"A positive real value that defines the reservoir volume injection rate for the phase declared by the TYPE variable for the satellite group. Generally, RESV should be set to zero, unless one wishes to have the satellite reservoir volume rate added to the group’s superordinate groups. If RESV is set to zero for all satellite groups and if the superordinate group has a reservoir volume injection target, a voidage replacement target, or a production balancing fraction target, then only the non-satellite group volumes will be used. This item is not supported by OPM Flow and should be defaulted (1*) or set to zero.","units":{"field":"rb/d","metric":"rm3/day","laboratory":"rcc/hour"},"default":"0.0","value_type":"DOUBLE","dimension":"ReservoirVolume/Time"},{"index":5,"name":"CALRATE","description":"A positive real value that defines the calorific injection rate used in the commercial compositional simulator. This item is not supported by OPM Flow and should be defaulted (1*) or set to zero.","units":{},"default":"0.0","value_type":"DOUBLE","dimension":"Energy/GasSurfaceVolume"}],"example":"The example below is based on an oil field, with the main field FLD-A being modeled in the input deck with two groups (FLD-A1 and FLD-A2), combined with one satellite field supplementing oil production and water injection (FLD-B).\n-- ==============================================================================\n--\n-- SCHEDULE SECTION\n--\n-- ==============================================================================\nSCHEDULE\n--\n-- DEFINE GROUP TREE HIERARCHY\n-- LOWER HIGHER\n-- GROUP GROUP\nGRUPTREE\nFLD-A FIELD /\nFLD-A1 FLD-A /\nFLD-A2 FLD-A /\nFLD-B FIELD /\n/\n--\n-- GROUP PRODUCTION CONTROLS\n--\n-- GRUP CNTL OIL WAT GAS LIQ CNTL GRUP GUIDE GUIDE CNTL\n-- NAME MODE RATE RATE RATE RATE OPT CNTL RATE DEF WAT\nGCONPROD\nFIELD ORAT 20E3 30E3 50E3 1* 1* 1* /\nFLD-A FLD 20E3 30E3 50E3 1* 1* 1* /\n/ --\n-- LOAD INCLUDE FILE - LOAD ALL WELLS AND VFP TABLES\n--\nINCLUDE\n'FLD-A-P50-WELLS.INC' /\n--\n-- GROUP INJECTION TARGETS AND CONSTRAINTS\n--\n-- GRUP FLUID CNTL SURF RESV REINJ VOID GRUP GUIDE GUIDE GRUP GRUP\n-- NAME TYPE MODE RATE RATE FRAC FRAC CNTL RATE DEF REINJ RESV\nGCONINJE\nFIELD WAT REIN 35E3 1* 1* 1.0 NO 1* 1* 1* 1* /\n/ --\n-- SATELLITE GROUP PRODUCTION CONTROLS\n--\n-- GRUP OIL WAT GAS RESV GAS CALORIFIC\n-- NAME RATE RATE RATE RATE LIFT RATE\nGSATPROD\nFLD-B 5E3 0.00 2E3 1* 1* /\n/\n--\n-- SATELLITE GROUP INJECTION CONTROLS\n--\n-- GRUP FLUID SURF RESV CALORIFIC\n-- NAME TYPE RATE RATE RATEV\nGSATINJE\nFLD-B WAT 10E3 1* 1* /\n/\n--\n-- ADVANCE SIMULATION BY REPORTING DATE\n--\nDATES\n1 FEB 2021 /\n/\n--\n-- SATELLITE GROUP PRODUCTION CONTROLS\n--\n-- GRUP OIL WAT GAS RESV GAS CALORIFIC\n-- NAME RATE RATE RATE RATE LIFT RATE\nGSATPROD\nFLD-B 5E3 0.00 2E3 0.0 1* /\n/\n--\n-- SATELLITE GROUP INJECTION CONTROLS\n--\n-- GRUP FLUID SURF RESV CALORIFIC\n-- NAME TYPE RATE RATE RATEV\nGSATINJE\nFLD-B WAT 10E3 1* 1* /\n/\nHere FLD-B will supplement FLD-A’s water re-injection rate by 10,000 stb/d, subject to a maximum field water injection rate of 35,000 stb/d on the GCONINJE keyword. This means that FLD-A’s maximum water injection rate cannot exceed 25,000 stb/d. In terms of oil rates, GCONPROD defines a maximum oil rate of 20,000 stb/d of which 5,000 stb/d is from FLD-B. If any of the constraints on the GCONINJE and GCONPROD keywords are violated, then the appropriate action will occur only for FLD-A, in order to ensure the group constraints are honored.\n| Note Once a group has been defined to be a satellite group, via the GSATINJE and GSATPROD keywords, then the equivalent modeled group keywords, GCONINJE and GCONPROD in the SCHEDULE section, cannot be used to set the operating conditions for satellite groups, only the GSATINJE and GSATPROD keywords may be used. |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":5,"size_kind":"list"},"GSATPROD":{"name":"GSATPROD","sections":["SCHEDULE"],"supported":false,"summary":"The GSATPROD keyword defines a satellite group’s oil, water and gas production rates in the model. Satellite groups are not connected to the reservoir model and therefore have no wells or subordinate groups associated with them, they are nevertheless connected to other higher level groups and higher level groups within a network model (if activated).They provide a means to “add-in” outside injection and production to the model without modeling the “add-in” reservoirs.","parameters":[{"index":1,"name":"GRPNAME","description":"A character string of up to eight characters in length that defines the satellite group name for which the group production import rates are being defined. The group named FIELD is the top most group and should not be used with this keyword. Note that the group hierarchy should be defined by the GRUPTREE keyword in the SCHEDULE section when there is more than one level of groups, otherwise all the groups will sit directly under the FIELD group in the group tree hierarchy. Note that a satellite group cannot have subordinate groups or wells.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"ORAT","description":"A real value, greater than or equal to zero, that defines the satellite’s surface oil production rate to be imported into the model. This value may be specified using a User Defined Argument (UDA).","units":{"field":"stb/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"0.0","value_type":"UDA","dimension":"LiquidSurfaceVolume/Time"},{"index":3,"name":"WRAT","description":"A real value, greater than or equal to zero, that defines the satellite’s surface water production rate to be imported into the model. This value may be specified using a User Defined Argument (UDA).","units":{"field":"stb/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"0.0","value_type":"UDA","dimension":"LiquidSurfaceVolume/Time"},{"index":4,"name":"GRAT","description":"A real value, greater than or equal to zero, that defines the satellite’s surface gas production rate to be imported into the model. This value may be specified using a User Defined Argument (UDA).","units":{"field":"Mscf/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"0.0","value_type":"UDA","dimension":"GasSurfaceVolume/Time"},{"index":5,"name":"RESV","description":"A real value, greater than or equal to zero, that defines the satellite’s reservoir volume production rate to be imported into the model. This item is not supported by OPM Flow and should be defaulted (1*) or set to zero.","units":{"field":"rb/d","metric":"rm3/day","laboratory":"rcc/hour"},"default":"0.0","value_type":"UDA","dimension":"ReservoirVolume/Time"},{"index":6,"name":"GASLIFT","description":"A real value, greater than or equal to zero, that defines the satellite’s gas lift gas to be imported for this group. A value for GASLIFT is only required if externally supplied gas lift is being imported into the model, and: The Network Model is active in the input deck via the NETWORK keyword in the RUNSPEC section. Here, GASLIFT is applied to the production network in order to calculate the pressure drop through the network, for branches that have: OPTION2 set to FLO on the GRUPNET keyword in the SCHEDULE section, or the GASLIFT parameter on the NODEPROP keyword in the SCHEDULE section set to YES, for when the Extended Network Model is being used. as per the BRANPROP and NODEPROP keywords, in the SCHEDULE section. The Gas Lift Optimization Model is active in the deck via the LIFTOPT keyword in the SCHEDULE section. In this case GASLIFT is applied to GRPNAME’s superordinate group’s gas supply constraints based on the GLIFTOPT keyword in the SCHEDULE section. For clarity, GLIFTOPT constraint violations result in the groups being modeled having their rates adjusted, whereas satellite group rates are not affected. This item is not supported by OPM Flow and should be defaulted (1*) or set to zero.","units":{"field":"Mscf/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"0.0","value_type":"UDA","dimension":"GasSurfaceVolume/Time"},{"index":7,"name":"CALRATE","description":"A real value greater than or equal to zero that defines the satellite's calorific production rate. This item is not supported by OPM Flow and should be defaulted (1*) or set to zero.","units":{},"default":"0.0","value_type":"UDA","dimension":"1"}],"example":"The example below is based on a dry gas field, with the main field FLD-A being modeled in the input deck with two groups (FLD-A1 and FLD-A2), combined with two satellite gas fields, FLD-B and FLD-C.\n-- ==============================================================================\n--\n-- SCHEDULE SECTION\n--\n-- ==============================================================================\nSCHEDULE\n--\n-- DEFINE GROUP TREE HIERARCHY\n-- LOWER HIGHER\n-- GROUP GROUP\nGRUPTREE\nFLD-A FIELD /\nFLD-A1 FLD-A /\nFLD-A2 FLD-A /\nFLD-B FIELD /\nFLD-C FIELD /\n/\n--\n-- GROUP PRODUCTION CONTROLS\n--\n-- GRUP CNTL OIL WAT GAS LIQ CNTL GRUP GUIDE GUIDE CNTL\n-- NAME MODE RATE RATE RATE RATE OPT CNTL RATE DEF WAT\nGCONPROD\nFIELD GRAT 1* 1* 450E3 1* 1* 1* /\nFLD-A FLD 1* 1* 450E3 1* 1* 1* /\n/\n--\n-- LOAD INCLUDE FILE - LOAD ALL WELLS AND VFP TABLES\n--\nINCLUDE\n'FLD-A-P50-WELLS.INC' /\n--\n-- SATELLITE GROUP PRODUCTION CONTROLS\n--\n-- GRUP OIL WAT GAS RESV GAS CALORIFIC\n-- NAME RATE RATE RATE RATE LIFT RATE\nGSATPROD\nFLD-B 10.0 0.00 30E3 1* 1* /\nFLD-C 20.0 5.50 20E3 0.0 1* /\n/\n--\n-- ADVANCE SIMULATION BY REPORTING DATE\n--\nDATES\n1 FEB 2021 /\n/\n--\n-- SATELLITE GROUP PRODUCTION CONTROLS\n--\n-- GRUP OIL WAT GAS RESV GAS CALORIFIC\n-- NAME RATE RATE RATE RATE LIFT RATE\nGSATPROD\nFLD-B 10.0 0.00 30E3 0.0 1* /\nFLD-C 20.0 9.00 20E3 0.0 1* /\n/\nSince the field gas rate is set to 450 MMscf/d and the satellite production is 50 MMscf/d, then FLD-A will produce only 400 MMscf/d and not the stipulated 450 MMscf/d on the GCONPROD keyword.\n| Note Once a group has been defined to be a satellite group, via the GSATINJE and GSATPROD keywords, then the equivalent modeled group keywords, GCONINJE and GCONPROD in the SCHEDULE section, cannot be used to set the operating conditions for satellite groups, only the GSATINJE and GSATPROD keywords may be used. |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":7,"size_kind":"list"},"GSEPCOND":{"name":"GSEPCOND","sections":["SCHEDULE"],"supported":false,"summary":"The GSEPCOND keyword assigns previously defined separators to a group. Group separators are specified by the SEPVALS keyword in the SCHEDULE section. The facility is used in black-oil modeling to re-scale the PVT data entered via the PROPS section, based on the saturation point oil formation volume factor (Bob) and the initial saturated gas-oil ratio (Rsi) entered on the SEVPALS keyword.","parameters":[{"index":1,"name":"GROUP","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"SEPARATOR","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":2,"size_kind":"list"},"GSSCPTST":{"name":"GSSCPTST","sections":["SCHEDULE"],"supported":false,"summary":"The GSSCPTST keyword instructs the simulator to perform a sustainable capacity test. This causes the model to be saved in it’s current state via the RESTART file, and the test performed by running the simulation under the current conditions combine with the parameters on this keyword. After the test is perform, the simulator will restart from the point prior to the test by loading in the RESTART file. This type of testing is normally applied to gas fields for which the gas sales contracts stipulate that the gas sales rates are based on a sustainable capacity rate over a fixed period of time.","parameters":[{"index":1,"name":"GROUP","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"CONTROL_MODE","description":"","units":{},"default":"GRAT","value_type":"STRING"},{"index":3,"name":"TARGET_PROD_RATE","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":4,"name":"TARGET_PROD_PERIOD","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Time"},{"index":5,"name":"MAX_PROD_RATE_FLAG","description":"","units":{},"default":"1","value_type":"INT"},{"index":6,"name":"CONV_TOLERANCE","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":7,"name":"MAT_IT","description":"","units":{},"default":"6","value_type":"INT"},{"index":8,"name":"SUB_GRP_CONTROL_FLAG","description":"","units":{},"default":"1","value_type":"INT"}],"example":"","expected_columns":8,"size_kind":"fixed","size_count":1},"GSWINGF":{"name":"GSWINGF","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, GSWINGF, defines the gas contract parameters, swing factor and the monthly seasonal profile factor, for when there are multiple gas contracts being used in the model. The keyword is used with the Gas Field Operations option which is activated by the GASFIELD keyword in the RUNSPEC section. Gas contracts are commonly based on a Daily Contract Quantity (“DCQ”) that determines the gas rate that the field should be produced at, which is normally expressed as a multiple of the DCQ, for example 1.33, and is often referred to as the “swing factor”. Some gas contracts also define a maximum DCQ (“Max DCQ”) and/or a minimum take or pay DCQ (“Min DCQ”), as well as seasonal demand characteristics. For example, gas rates may be set higher in the winter months in order to meet heating demand compared with summer months in colder climates, and the opposite in warmer climates where air conditioning demand is high.","parameters":[{"index":1,"name":"GROUP","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"SWING_JAN","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"SWING_FEB","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":4,"name":"SWING_MAR","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":5,"name":"SWING_APR","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":6,"name":"SWING_MAY","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":7,"name":"SWING_JUN","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":8,"name":"SWING_JUL","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":9,"name":"SWING_AUG","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":10,"name":"SWING_SEP","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":11,"name":"SWING_OCT","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":12,"name":"SWING_NOV","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":13,"name":"SWING_DEC","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":14,"name":"PROFILE_JAN","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":15,"name":"PROFILE_FEB","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":16,"name":"PROFILE_MAR","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":17,"name":"PROFILE_APR","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":18,"name":"PROFILE_MAY","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":19,"name":"PROFILE_JUN","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":20,"name":"PROFILE_JUL","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":21,"name":"PROFILE_AUG","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":22,"name":"PROFILE_SEP","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":23,"name":"PROFILE_OCT","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":24,"name":"PROFILE_NOV","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":25,"name":"PROFILE_DEC","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"}],"example":"| [Q sub{month}`=` DCQ times SWINGFAC sub{ month }] | (12.27) |\n|---------------------------------------------------|---------|","expected_columns":25,"size_kind":"list"},"GTADD":{"name":"GTADD","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, GTADD, adds a numerical constant to a group’s target or constraint value. The group must have been initially fully defined using the GCONPROD or GCONPRI keywords for producers or GCONINJE for injectors. Variables not changed by the GTADD keyword remain the same as those previously entered via the group control keywords or previously entered GTADD keywords. See also the GRUPTARG keyword that sets the values for a group’s target and constraints and the GTMULT keyword that multiplies a group target or constraint by a constant. All the aforementioned keywords are described in the SCHEDULE section.","parameters":[{"index":1,"name":"GROUP","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"TARGET","description":"","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"QUANTITY","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":4,"name":"NUM_ADDITIONS","description":"","units":{},"default":"1","value_type":"INT"}],"example":"","expected_columns":4,"size_kind":"list"},"GTMULT":{"name":"GTMULT","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, GTMULT, multiplies a group’s target or constraint value by a numerical constant. The group must have been initially fully defined using the GCONPROD or GCONPRI keywords for producers or GCONINJE for injectors. Variables not changed by the GTMULT keyword remain the same as those previously entered via the group control keywords or previously entered GTMULT keywords. See also the GRUPTARG keyword that sets the values for a group’s target and constraints, and the GTADD keyword that adds a constant to a group’s target or constraint. All the aforementioned keywords are described in the SCHEDULE section.","parameters":[{"index":1,"name":"GROUP","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"TARGET","description":"","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"QUANTITY","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":4,"name":"NUM_MULT","description":"","units":{},"default":"1","value_type":"INT"}],"example":"","expected_columns":4,"size_kind":"list"},"GUIDECAL":{"name":"GUIDECAL","sections":["SCHEDULE"],"supported":false,"summary":"The GUIDECAL keyword defines a well or group’s guide rate as a function of their calorific values, for when the individual wells and groups are under guide rate control. Group and well guide rates that have not been directly defined are set equal to their production potentials at the start of each time step. In this case the GUIDECAL keyword can be used to specify the coefficients of a function that takes into account the calorific value of the produced gas, effectively scaling the guide rates based on the calorific value of the gas being produced.","parameters":[{"index":1,"name":"COEFF_A","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":2,"name":"COEFF_B","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","expected_columns":2,"size_kind":"fixed","size_count":1},"GUIDERAT":{"name":"GUIDERAT","sections":["SCHEDULE"],"supported":true,"summary":"This keyword defines a general formulae used to define a group’s and well’s guide rate as a function of the their potential. The default behavior, that is when this keyword is not invoked, is to set the target control mode and rate via the GCONPROD keyword in the SCHEDULE section. In this case the target rate is distributed between the group’s wells that are under group control using a well’s guide rate. If a well’s guide rate has not been defined, for example by this keyword, then the well potential of the group controlling phase at the beginning of the time step is used. For example, if the group target rate and phase is oil, then the well’s under group control will have their oil rates determined by their oil rate potential309\n Production and injection potentials are based on rates that are unrestricted. For wells this implies that well potential is calculated based on either the BHP or THP limit, which ever is the more constraining.. The GUIDERAT keyword substitutes the pote...","parameters":[{"index":1,"name":"TSTEP","description":"A real positive value that defines the minimum time interval to re-calculate the guide rates. The guide rates are calculated at the start of a time step and the default value of zero means that the guide rates are calculated for each time step. A non-zero value for TSTEP resets the minimum interval, for example setting TSTEP equal to 30 would mean the guide rates are calculate every 30 days, or to the nearest associated time step. Calculating guide rates every time step may cause issues due to the rate dependent behavior, for example gas cusping or water coning causing the well rates to oscillate. In this case using a non-zero value of TSTEP may eliminate this oscillating behavior.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"0.0","value_type":"DOUBLE","dimension":"Time"},{"index":2,"name":"PHASE","description":"A defined character string that sets the potential phase guide rate for the group and well, the resulting Phase Guide Rate in equation (12.28). PHASE should be set to one of the following character strings: OIL: is set as the potential phase guide rate and in this case the Potential Ratio1 variable is the water-oil ratio (“WOR”) and Potential Ratio2 refers to the gas-oil ratio (“GOR”) in equation (12.28). LIQ: is set as the potential phase guide rate and the Potential Ratio1 variable is the water cut (“WCT”) and Potential Ratio2 refers to the gas-liquid ratio (“GLR”) in equation (12.28). GAS: is set as the potential phase guide rate with the Potential Ratio1 variable being the water cut (“WCT”) and Potential Ratio2 referring to the oil-gas ratio (“OGR”) in equation (12.28). RES: here the potential phase guide rate is defined as the reservoir fluid volume rate and the Potential Ratio1 variable is the water-oil ratio (“WOR”) and Potential Ratio2 refers to the gas-oil ratio (“GOR”) in equation (12.28). COMB: this option uses the linearly combined phase guide rate based on the values entered on the LINCOM keyword in the SCHEDULE section. Here the Potential Ratio1 variable is the water divided by linearly combined phase and Potential Ratio2 refers to the gas divided by linearly combined phase in equation (12.28). This option is not available in OPM Flow. NONE: the Phase Guide Rate calculation is switched off and the well guide rates revert to the well potentials of their group target phase. For reference, the units for the various options is given below .","units":{"field":"WOR: dimensionless WCT: dimensionless WGR: stb/Mscf","metric":"dimensionless dimensionless dimensionless","laboratory":"dimensionless dimensionless dimensionless"},"default":"None","value_type":"STRING","options":["OIL","LIQ","GAS","RES","COMB","NONE"]},{"index":3,"name":"A","description":"A real value greater than or equal to -3 and less than or equal to 3, that defines coefficient A in equation (12.28).","units":{},"default":"0.0","value_type":"DOUBLE"},{"index":4,"name":"B","description":"B is a real positive value that defines coefficient B in equation (12.28).","units":{},"default":"0.0","value_type":"DOUBLE"},{"index":5,"name":"C","description":"C is a real value that defines coefficient C in equation (12.28).","units":{},"default":"0.0","value_type":"DOUBLE"},{"index":6,"name":"D","description":"D is a real value greater than or equal to -3 and less than or equal to 3, that defines coefficient D in equation (12.28).","units":{},"default":"0.0","value_type":"DOUBLE"},{"index":7,"name":"E","description":"E is a real value that defines coefficient E in equation (12.28).","units":{},"default":"0.0","value_type":"DOUBLE"},{"index":8,"name":"F","description":"F is a real value greater than or equal to -3 and less than or equal to 3, that defines coefficient F in equation (12.28).","units":{},"default":"0.0","value_type":"DOUBLE"},{"index":9,"name":"GROPT01","description":"A defined character string that determines if calculated phase guide rates should be allowed to increase (YES) or not (NO), and should be set to one of the following: NO: The phase guide rates calculated from equation (12.28)are not allowed to increase above the current value, and will be reset to the current value if the calculated value does exceed the current value. YES: The phase guide rates calculated from equation (12.28)are allowed to increase at each calculation. This may increase the propensity for oscillations in the rates if the water cut and GOR are rate dependent. Note only the default value is currently supported by OPM Flow.","units":{},"default":"YES","value_type":"STRING"},{"index":10,"name":"GROPT02","description":"A real positive value greater than or equal to zero and less than or equal to one that “dampens” the calculated phase guide rate based on the following formula: [( Phase`Guide`Rate )_t ^new``=``GROPT02 times ( Phase`Guide`Rate )_t``+` newline( 1`-`GROPT02) times (Phase`Guide`Rate )_(t-1)] The option is intended to have a similar effect as the GROPT01 NO option to reduce oscillations as a result of either the water cut or GOR being rate dependent. Values approaching one allows the calculated phase guide rates to change instantaneously with the phase potentials, whereas values approaching zero dampen the potential guide rates towards the previously calculated values, thereby reducing the potential for oscillating behavior.","units":{},"default":"1.0","value_type":"DOUBLE"},{"index":11,"name":"GROPT03","description":"A defined character string that determines if “free” gas potential rates for the Potential Ratio2 variable in equation (12.28)should be used (YES), or if “free and associated” gas should be used (NO), and should be set to one of the following: NO: Use “free and associated” gas, that is total gas in the Potential Ratio2 variable. YES: Only utilize “free” gas in the Potential Ratio2 variable.","units":{},"default":"NO","value_type":"STRING"},{"index":12,"name":"GROPT04","description":"A real positive value that sets the minimum potential guide rate. If the calculated potential guide is below this value it will be reset to GROPT04. The option is meant to avoid groups and wells being ignored due to the calculated potential guide rates being minuscule.","units":{},"default":"1.0 x10-6","value_type":"DOUBLE"}],"example":"The first example sets the guide phase to oil and the resulting Phase Guide Rate based on oil potential based on setting the A and B coefficients to to one, that is:\n[Phase Guide Rate``= { (Potental _Phase) ^A } over { B``+``C(Potential Ratio_1)^D``+`` E(Potential Ratio_2)^F} newline newline\n~=~{Oil Potential^1.0} over 1.0]\n(12.29)\nwith all the other parameters defaulted, except for the minimum time interval to re-calculate the guide rates which is set to 30 days.\n--\n-- SETS GUIDE RATES FOR GROUPS AND WELLS UNDER GUIDE RATE CONTROL\n--\n-- TIME GUIDE A B C D E F INCR DAMP FREE\n-- STEP PHASE POW CON CON POW CON POW OPTN OPTN GAS\nGUIDERAT\n30 'OIL' 1.0 1.0 1* 1* 1* 1* 1* 1* 1* /\nThe next example sets the Phase Guide Rate to the reservoir fluid volume rate, with preference given to low GOR wells and with high GOR wells penalized, based on setting A and B to one, C and D to zero, E equal to 10 and F equal to two, that is:\n[Phase Guide Rate``= { (Potental _Phase) ^A } over { B``+``C(Potential Ratio_1)^D``+`` E(Potential Ratio_2)^F}~newline newline\n~~~~~`` =~{Reservoir` Fluid `Volume` Potential^1.0} over {1.0`` + ``10 times (GOR)^2}]\n(12.30)\nwith all the other parameters defaulted.\n--\n-- SETS GUIDE RATES FOR GROUPS AND WELLS UNDER GUIDE RATE CONTROL\n--\n-- TIME GUIDE A B C D E F INCR DAMP FREE\n-- STEP PHASE POW CON CON POW CON POW OPTN OPTN GAS\nGUIDERAT\n1* 'RES' 1.0 1.0 1* 1* 10 2 1* 1* 1* /\nThe GUIDERAT keyword is very flexible but can also lead to unexpected results, thus it is probably useful to perform some manual calculations outside of the simulator before implementing the selected scheme in the input deck.\n| [Phase Guide Rate``= { (Potental _Phase) ^A } over { B``+``C(Potential Ratio_1)^D``+`` E(Potential Ratio_2)^F}] | (12.28) |\n|------------------------------------------------------------------------------------------------------------------|---------|\n| Note GUIDERAT can be used to penalize wells producing excessive water by utilizing the C and D coefficients in equation (12.28), and to discriminate against wells that are gassing out by setting the E and F coefficients. Note that the value range through which Potential Ratio1 and Potential Ratio2 vary is variable. For example, if Potential Ratio1 is water cut, then the value should be between zero and one, whereas for the water-oil ratio the value can vary between zero and infinity. The same applies to the units of Potential Ratio2 which are dependent on if the GOR, GLR or OGR ratio is used in the calculation. One can use the C and E coefficients to scale these terms to the required relative magnitudes in the denominator and the D and F powers to influence how quickly the penalty increases with increasing water and gas fractions. High positive value for D and F coefficients will make production fall off rapidly as the water or gas fraction increases, while a negative values will favor producing these type of wells. Note that the B coefficient should always be positive to prevent the denominator's going to zero. Finally, if one wishes each well to produce in proportion to its potential when the water fraction and gas fraction are equal (the usual case), then the A coefficient should be set to one. |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------","expected_columns":12,"size_kind":"fixed","size_count":1},"GUPFREQ":{"name":"GUPFREQ","sections":["SCHEDULE"],"supported":false,"summary":"The GUPFREQ keyword sets the update frequency of the Instantaneous Gradient option for when this option has been activated by the GDIMS keyword in the RUNSPEC section. The Instantaneous Gradient option calculates derivatives of solution quantities at the current time step with respect to variations in the variables at the current time step. This is different to Gradient option that calculates the derivatives of solution quantities at the current time step with respect to variations in the variables at the initial time step, that is a time equal to zero. Consequently, the Instantaneous Gradient option can be switched on and off by the GUPFREQ keyword in the SCHEDULE section, whereas the Gradient option cannot.","parameters":[{"index":1,"name":"UPDATE_FREQ_TYPE","description":"","units":{},"default":"ALL","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"GWRTWCV":{"name":"GWRTWCV","sections":["SCHEDULE"],"supported":false,"summary":"The GWRTWCV keyword defines the wells and instantaneous gradient parameters to be calculated and exported as SUMMARY vectors to the summary file, for when the Instantaneous Gradient option has been activated by the GDIMS keyword in the RUNSPEC section. The Instantaneous Gradient option calculates derivatives of solution quantities at the current time step with respect to variations in the variables at the current time step. This is different to Gradient option that calculates the derivatives of solution quantities at the current time step with respect to variations in the variables at the initial time step, that is a time equal to zero. Consequently, the Instantaneous Gradient option can be switched on and off by the GUPFREQ keyword in the SCHEDULE section, whereas the Gradient option cannot.","parameters":[{"index":1,"name":"WELLS","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","size_kind":"list","variadic_record":true},"HMWPIMLT":{"name":"HMWPIMLT","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, HMWPIMLT, defines the history match gradient parameters for well productiviity indices, for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section. Wells must be specified using the WELPSECS keyword in the SCHEDULE section and their connections defined by the COMPDAT and/or COMPDATL keywords, also in the SCHEDULE section","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"list"},"LGRFREE":{"name":"LGRFREE","sections":["SCHEDULE"],"supported":null,"summary":"The LGRFREE keyword activates the Local Grid Refinement (“LGR”) Independent Time Step option that allows the LGR to have solution time steps independent of the host grid for the stated LGR, and for when LGRs have been declared by the LGR keyword in the RUNSPEC section, and defined by the CARFIN (Cartesian LGR grid) or RADIN/RADIN4 (radial LGR grid) keywords in the GRID section. LGR independent solution time stepping can be deactivated by the LGRLOCK keyword in the SCHEDULE section.","parameters":[{"index":1,"name":"LGRNAME","description":"A character string of up to eight characters in length that defines the LGR name for which independent solution time stepping is to be activated. The LGR must have been previously defined by the CARFIN (Cartesian LGR grid) or RADIN/RADIN4 (radial LGR grid) keywords in the GRID section.","units":{},"default":"None","value_type":"STRING"}],"example":"The example below defines three oil LGRs(LGR-OP01,-OP02, and -OP03) and all the gas well LGRs (LGR-GP*) that should use independent solution time steps.\n--\n-- ACTIVATE LOCAL GRID REFINEMENT INDEPENDENT TIME STEPS\n--\n-- LGRNAME\nLGRFREE\nLGR-OP01 /\nLGR-OP02 /\nLGR-OP03 /\nLGR-GP* /\n/","expected_columns":1,"size_kind":"list"},"LGRLOCK":{"name":"LGRLOCK","sections":["SCHEDULE"],"supported":null,"summary":"The LGRLOCK keyword deactivates the Local Grid Refinement (“LGR”) Independent Time Step option that allows the LGR to have solution time steps independent of the host grid for the stated LGR, that is the LGR will now follow the global grid solution time steps. LGRs must have declared by the LGR keyword in the RUNSPEC section, and defined by the CARFIN (Cartesian LGR grid) or RADIN/RADIN4 (radial LGR grid) keywords in the GRID section. LGR independent solution time stepping can be activated by the LGRFREE keyword in the SCHEDULE section.","parameters":[{"index":1,"name":"LGRNAME","description":"A character string of up to eight characters in length that defines the LGR name for which independent solution time stepping is to be deactivated. The LGR must have been previously defined by the CARFIN (Cartesian LGR grid) or RADIN/RADIN4 (radial LGR grid) keywords in the GRID section.","units":{},"default":"None","value_type":"STRING"}],"example":"The example below defines three oil LGRs(LGR-OP01,-OP02, and -OP03) and all the gas well LGRs (LGR-GP*) that should have their independent solution time steps deactivated.\n--\n-- DEACTIVATE LOCAL GRID REFINEMENT INDEPENDENT TIME STEPS\n--\n-- LGRNAME\nLGRLOCK\nLGR-OP01 /\nLGR-OP02 /\nLGR-OP03 /\nLGR-GP* /\n/","expected_columns":1,"size_kind":"list"},"LGROFF":{"name":"LGROFF","sections":["SCHEDULE"],"supported":null,"summary":"The LGROFF keyword deactivates a stated Local Grid Refinement (“LGR”) and optionally sets the minimum number of wells below which the LGR will be automatically deactivated. LGRs must have declared by the LGR keyword in the RUNSPEC section, and defined by the CARFIN (Cartesian LGR grid) or RADIN/RADIN4 (radial LGR grid) keywords in the GRID section. LGRs can subsequently be activated by the LGRON keyword in the SCHEDULE section.","parameters":[{"index":1,"name":"LGRNAME","description":"A character string of up to eight characters in length that defines the LGR name for which the LGR is being deactivated. The LGR must have been previously defined by the CARFIN (Cartesian LGR grid) or RADIN/RADIN4 (radial LGR grid) keywords in the GRID section.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"MNWELLS","description":"A positive integer greater than or equal to zero that defines the minimum number of active wells, below which the LGR will be automatically deactivated. The default value of zero implies that there is no limit to the number of wells and results in the LGR being unconditionally being deactivated.","units":{},"default":"0","value_type":"INT"}],"example":"The example below unconditionally deactivates LGR-OP01, and sets the minimum number of active wells for deactivating LGR-OP02 and LGR-OP03 to one. For all the gas well LGRs (LGR-GP*) the minimum number of wells for deactivation is set to two.\n--\n-- DEACTIVATE LOCAL GRID REFINEMENTS\n--\n-- LGRNAME MNWELLS\nLGROFF\nLGR-OP01 /\nLGR-OP02 1 /\nLGR-OP03 1 /\nLGR-GP* 2 /\n/","expected_columns":2,"size_kind":"fixed","size_count":1},"LGRON":{"name":"LGRON","sections":["SCHEDULE"],"supported":null,"summary":"The LGRON keyword activates a stated Local Grid Refinement (“LGR”) and optionally sets the minimum number of wells above which the LGR will remain active. LGRs must have declared by the LGR keyword in the RUNSPEC section, and defined by the CARFIN (Cartesian LGR grid) or RADIN/RADIN4 (radial LGR grid) keywords in the GRID section. LGRs can subsequently be deactivated by the LGROFF keyword in the SCHEDULE section.","parameters":[{"index":1,"name":"LGRNAME","description":"A character string of up to eight characters in length that defines the LGR name for which the LGR is being activated. The LGR must have been previously defined by the CARFIN (Cartesian LGR grid) or RADIN/RADIN4 (radial LGR grid) keywords in the GRID section.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"MNWELLS","description":"A positive integer greater than or equal to zero that defines the minimum number of active wells, below which the LGR will be automatically deactivated. The default value of zero implies that there is no limit to the number of wells and results in the LGR being unconditionally being activated.","units":{},"default":"0","value_type":"INT"}],"example":"The example below unconditionally activates LGR-OP01, and sets the minimum number of active wells for activating LGR-OP02 and LGR-OP03 to one. For all the gas well LGRs (LGR-GP*) the minimum number of wells for activating these LGRs is set to two.\n--\n-- ACTIVATE LOCAL GRID REFINEMENTS\n--\n-- LGRNAME MNWELLS\nLGRON\nLGR-OP01 /\nLGR-OP02 1 /\nLGR-OP03 1 /\nLGR-GP* 2 /\n/","expected_columns":2,"size_kind":"fixed","size_count":1},"LIFTOPT":{"name":"LIFTOPT","sections":["SCHEDULE"],"supported":null,"summary":"The LIFTOPT keyword actives the gas lift optimization option and defines the gas lift gas increment size, the minimum incremental oil improvement, as well as the timing of the calculations. Note that the LIFTOPT keyword should precede any GLIFTOPT and WLIFTOPT keywords in the SCHEDULE section in order to activate the gas lift optimization facility.","parameters":[{"index":1,"name":"GASLIFT","description":"A real positive number that defines the gas lift gas size increment that is used to increase the gas lift size quantity in steps. For example, if GASLIFT is set to 0.5 MMscf/d then gas lift gas will be allocated in step of 0.5 MMscf/d to each well during the optimization process. A zero or negative value switches off gas lift optimization.","units":{"field":"Mscf/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"None","value_type":"DOUBLE","dimension":"GasSurfaceVolume/Time"},{"index":2,"name":"MINOIL","description":"MINOIL is a real positive value that defines the minimum increase in oil rate for a given quantity of gas lift gas, for when gas lift gas should be applied to a well. Additional GASLIFT will only be assigned to a well if: [{%DELTA Q_Oil ``times`` OPTWGT} over GASLIFT~ > ~MINOIL] Where ΔQOil is the incremental oil and OPTWGT is the well’s weighting factor defined by the OPTWGT variable on the WLIFTOPT keyword in the SCHEDULE section.","units":{"field":"stb/Mscf","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"None","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/GasSurfaceVolume"},{"index":3,"name":"TSTEP","description":"TSTEP is a real positive value that defines the frequency of the gas lift optimization calculations, for example setting TSTEP equal to 30 days would result in the gas lift optimization calculation being performed approximately every 30 days. The default value of zero will result in the calculations being performed every time step. Note if the group or well is part of a production network then gas lift optimization is performed at the same time as the network is being balance, that is this parameter is ignored in this scenario. See the NETBALAN keyword in the SCHEDULE section to set the network balancing frequency in this case.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"0.0","value_type":"DOUBLE","dimension":"Time"},{"index":4,"name":"OPTLIFT","description":"A defined character string that determines if the gas lift optimization iterations should be performed for the same number of Newton iterations within a time step as used to update well targets, or to just use the first Newton iteration only. The NUPCOL keyword in the RUNSPEC section determines the number of Newton iterations used to update well targets during a time step. OPTLIFT should be set to one of the following: NO: In this case the gas lift optimization is only performed for the first Newton iteration for a time step and the distributed gas lift gas is then held constant for the groups and wells through resultant Newton iterations during the time step. This leads to better numerical performance, but may lead to the targets and constraints not being exactly satisfied if the reservoir conditions change during the time step calculations. YES: Sets the number gas lift optimization iterations to the same number of Newton iterations within a time step as used to update well targets, as per the NUPCOL keyword in the RUNSPEC section. This results in greater target and constraint accuracy even if the reservoir conditions change during the time step calculations, but at the expense of numerical performance. Similar to the NO option, after the NUPCOL Newton iteration during the time step, the distributed gas lift gas is then held constant for the groups and wells in subsequent Newton iterations.","units":{},"default":"","value_type":"STRING"}],"example":"The following example activates gas lift optimization for the field and defines the optimization parameters.\n--\n-- ACTIVATE GAS LIFT OPTIMIZATION AND PARAMETERS\n--\n-- INCR INCR TSTEP NEWTON\n-- GAS OIL INTVAL OPTN\nLIFTOPT\n12.5E3 5E-3 0.0 YES /\nHere the maximum incremental gas lift gas quantity is set to 12.5 x 103 m3, the minimum incremental oil gain per m3 of gas lift gas is set to 5.0 x 10-3 m3, the time step interval is set to zero to perform the gas optimization every time step, and finally the gas lift optimization will be performed NUPCOL Newton iterations for the time step.","expected_columns":4,"size_kind":"fixed","size_count":1},"LINCOM":{"name":"LINCOM","sections":["SCHEDULE"],"supported":false,"summary":"The LINCOM keyword defines the oil, gas and water coefficients for the Linear Combination facility which allows for a linear combination of the aforementioned phase rates and volumes to be used as targets and constraints in controlling group and well production and injection data. See also the LCUNIT in the PROPS section that defines the units for linear combination equation.","parameters":[{"index":1,"name":"ALPHA","description":"","units":{},"default":"0","value_type":"UDA"},{"index":2,"name":"BETA","description":"","units":{},"default":"0","value_type":"UDA"},{"index":3,"name":"GAMMA","description":"","units":{},"default":"0","value_type":"UDA"}],"example":"","expected_columns":3,"size_kind":"fixed","size_count":1},"MATCORR":{"name":"MATCORR","sections":["SCHEDULE"],"supported":false,"summary":"The MATCORR keyword activates the Material Balance Correction option used to adjust the accumulated material balance error in the simulation.","parameters":[{"index":1,"name":"NEWTON_IT_NUM","description":"","units":{},"default":"12","value_type":"INT"},{"index":2,"name":"NON_LIN_CONV_ERR","description":"","units":{},"default":"0.01","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"MATERIAL_BALANCE_ERR","description":"","units":{},"default":"1e-06","value_type":"DOUBLE","dimension":"1"}],"example":"","expected_columns":3,"size_kind":"fixed","size_count":1},"MESSOPTS":{"name":"MESSOPTS","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, MESSOPTS, resets the severity level for time steps that are forced to be accepted by the simulator. The normal severity level for this type of simulator generated message is PROBLEM and this can result in the run stopping depending on the parameters entered on the MESSAGES keyword. MESSOPTS can be used to reset the severity level to MESSAGE, COMMENT, WARNING, or PROBLEM; for example, to avoid the run terminating due to too many PROBLEM messages.","parameters":[{"index":1,"name":"MNEMONIC","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"SEVERITY","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":2,"size_kind":"fixed","size_count":1},"MULSGGD":{"name":"MULSGGD","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, MULSGGD, defines a constant multiplier to modify the matrix-fracture coupling transmissibility for dual porosity and dual permeability models, for when the alternative matrix-fracture coupling transmissibilities for oil-gas gravity drainage has been selected. The alternative matrix-fracture coupling transmissibilities for oil-gas gravity drainage option is activated via the SIGMAGD or SIGMAGDV keywords in the GRID section, and the dual porosity or dual permeability models are activated by the DUALPORO or DUALPERM keywords in the RUNSPEC section, respectively.","parameters":[],"example":"","size_kind":"array"},"MULSGGDV":{"name":"MULSGGDV","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, MULSGGDV, defines a constant multiplier to modify the matrix-fracture coupling transmissibility for dual porosity and dual permeability models, for when the alternative matrix-fracture coupling transmissibilities for oil-gas gravity drainage has been selected. The alternative matrix-fracture coupling transmissibilities for oil-gas gravity drainage option is activated via the SIGMAGD or SIGMAGDV keywords in the GRID section, and the dual porosity or dual permeability models are activated by the DUALPORO or DUALPERM keywords in the RUNSPEC section, respectively.","parameters":[],"example":"","size_kind":"array"},"MULTSIG":{"name":"MULTSIG","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, MULTSIG, defines a constant multiplier to modify the matrix-fracture coupling transmissibility for dual porosity and dual permeability models, for when the matrix-fracture coupling transmissibilities have been specified via the SIGMAGD or SIGMAGDV keywords in the GRID section, and the dual porosity or dual permeability models have been activated by the DUALPORO or DUALPERM keywords in the RUNSPEC section, respectively.","parameters":[{"index":1,"name":"VALUE","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"MULTSIGV":{"name":"MULTSIGV","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, MULTSIGV, defines a constant multiplier to modify the matrix-fracture coupling transmissibility for dual porosity and dual permeability models, for when the matrix-fracture coupling transmissibilities have been specified via the SIGMAGD or SIGMAGDV keywords in the GRID section, and the dual porosity or dual permeability models have activated by the DUALPORO or DUALPERM keywords in the RUNSPEC section, respectively.","parameters":[],"example":"","size_kind":"array"},"NCONSUMP":{"name":"NCONSUMP","sections":["SCHEDULE"],"supported":false,"summary":"The NCONSUMP keyword defines an extended network node’s gas consumption rate, for when the Extended Network option has been activated by the NETWORK keyword in the RUNSPEC section. The keyword can also be used to attribute the gas consumption to a previously defined group. See also the GCONSUMP keyword in the SCHEDULE section that overs more flexibility and can also be used with the Extended Network option.","parameters":[{"index":1,"name":"NODE","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"GAS_CONSUMPTION_RATE","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"GasSurfaceVolume/Time"},{"index":3,"name":"REMOVAL_GROUP","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":3,"size_kind":"list"},"NEFAC":{"name":"NEFAC","sections":["SCHEDULE"],"supported":null,"summary":"The NEFAC keyword defines an extended network node’s efficiency factor, for when the Extended Network option has been activated by the NETWORK keyword in the RUNSPEC section. See also the GEFAC keyword in the SCHEDULE section that can also be used with the Extended Network option.","parameters":[{"index":1,"name":"NODE","description":"A character string of up to eight characters in length that defines the node name for which the node efficiency factor is being defined.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"FACTOR","description":"A real positive value that is less than or equal to one that defines the efficiency factor for the node. If a node’s down time is 5% then FACTOR should be set to 0.95 (1.0 – 0.05).","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0","value_type":"DOUBLE","dimension":"1"}],"example":"","expected_columns":2,"size_kind":"list"},"NETBALAN":{"name":"NETBALAN","sections":["SCHEDULE"],"supported":true,"summary":"NETBALAN keyword causes the simulator to perform a network balancing operation at the next time step. In addition, the keyword defines the network balancing parameters used to control how network balancing is performed on a network, as well as the frequency of the network balancing calculations. If any of the parameters on the keyword are defaulted, then either the previously entered values are used, or if there are no previously entered values, then the keyword default values are employed.","parameters":[{"index":1,"name":"NTSTEP","description":"NSTEP is a real value that defines the criteria for the network balancing interval, used to define the frequency of the network balancing algorithm. NSTEP may be a negative number, a value of zero, or a positive number, as described below: Negative Value: If NSTEP is any negative value then the time stepping interval for the network balancing is based on the number of Newton iterations used in updating the well targets, as set by the NUPCOL keyword in the RUNSPEC section, or the NUPCOL parameter on the GCONTOL keyword in the SCHEDULE section. If NUPCOL is defined on both keywords, then the GCONTOL value takes precedence. Thus, any negative value of NSTEP means the network will be balanced for the first NUPCOL Newton iterations for each time step. Consequently, if this option is used it may result in some oscillations as the THP of the wells are updated at each Newton network re-balance computation. Zero Value: Here the network is balanced at the beginning of every time step, and should result in small network balancing errors for the time step, provided of course the reservoir conditions are fairly constant over the time step. This is the default value. Positive Value: In this case NSTEP is a time interval between the previous network balance and the next schedule network balancing. For example, if NSTEP is set equal to 91.25 days (365/4), then network balancing will occur every quarter. Again, the balancing occurs at the beginning of the time step. Note only negative or zero values are currently supported.","units":{"field":"days or dimensionless","metric":"days or dimensionless","laboratory":"hours or dimensionless"},"default":"0.0"},{"index":2,"name":"NCNV","description":"NCNV is a real positive value that defines the nodal pressure convergence variance, used to define if convergence has been satisfied.","units":{"field":"psia 1.45","metric":"barsa 0.10","laboratory":"atma 0.09869"},"default":"Defined"},{"index":3,"name":"NMXITER","description":"A positive integer value that defines the maximum number of network balancing operations that may be performed during a network balancing computation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"10"},{"index":4,"name":"GRPCNV","description":"GRPCNV is a real positive value less than one that sets the group tolerance criteria used to define if convergence has been satisfied for: Wells in subsea completion manifold groups under rate control. In this case GRPCNV is applied to the THP values of the wells within the group. In the field, these type of wells must flow against a common manifold pressure, that is all the wells must flow at approximately the same THP, for a given group’s flow rate. Automatic chokes for group’s under rate control. Here, GRPCNV is applied to the pressure drop across the automatic chokes. In both cases GRPCNV is an acceptable fraction of the group’s rate target. Thus, the default value 0.01 means that network balance calculated rate must be within 0.01 (or 1.0%) of the groups’ production target. Note that this criteria may not be satisfied if the number of Newton iterations used in updating the well targets, as set by the NUPCOL keyword in the RUNSPEC section, or the NUPCOL parameter on the GCONTOL keyword in the SCHEDULE section, is exceeded. Group convergence criteria can also be set by the GRPCNV parameter on the GCONTOL keyword in the SCHEDULE section. If both values of GRPCNV have been entered, then the minimum of the two is used.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.01"},{"index":5,"name":"THPMXITE","description":"A positive integer value that defines the maximum number of well THP iterations for wells in subsea completion.anifold groups under rate control. There is no equivalent iteration maximum for automatic chokes in groups under rate control, as the pressure drop across the chokes is automatically calculated in the network balancing calculation. Thus, NMXITER is used for these calculations.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"10"},{"index":6,"name":"NTRGERR","description":"A real positive value that stipulates the maximum target branch error in a network balance calculation, at the end of the time step. NTRGERR is compared with the branch error (Error), where Error is the difference between the pressure drop along the branch from the previous network balance and the current calculation, again, at the end of the time step. Subject to existing targets and constraints, the simulator will attempt to adjust the time step size in order to roughly match NTRGERR. Note also that NTRGERR should be a value that is sufficient to allow convergence as defined by NCNV and GRPNCN parameters. The default value of 1.0 x 1020 means that this parameter has no effect in the selection of the time step size.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1.0 x 1020"},{"index":7,"name":"NMAXERR","description":"A real positive value that stipulates the maximum branch error in a network balance calculation, at the end of the time step. Again, NMAXERR is compared against the branch error (Error), where Error is the difference between the pressure drop along the branch from the previous network balance and the current calculation, at the end of the time step. If Error is greater than NMAXERR then the simulator will enforce a time step chop. Time step chops are computationally expensive and should therefore be minimized. Hence, care should be used in setting this value, which should be significantly greater than NTRGERR. The default value of 1.0 x 1020 means that this parameter has no effect in the selection of the time step size.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1.0 x 1020"},{"index":8,"name":"NTSMIN","description":"NTSMIN is a real positive value that sets the minimum time step size for when NTRGERR and NMAXERR have values. Large network balancing errors (Error) can take place for various reasons, a common occurrence is for wells producing near their operating limit which may shut in during a network balance operation. If NTRGERR and NMAXERR have values, then this will result in the simulator enforcing time step chops to perhaps very small time steps. NTSMIN can therefore be used to set the minimum time step size under, and only, these circumstances. The default value, TSMINZ, is taken from TSMINZ parameter on the TUNING keyword in the SCHEDULE section.","units":{"field":"days","metric":"days","laboratory":"hour"},"default":"TSMINZ"}],"example":"The first example sets network balancing to occur at the beginning of each time step using a 1.0 psia convergence criteria, and a maximum of 10 iterations. All the other parameters are defaulted.\n--\n-- NETWORK BALANCE CONTROL OPTIONS\n--\n-- BAL CONV MAX WTHP WTHP ERR ERR TSTEP\n-- INTV TOL ITRS TOL ITS TARG MAX MIN\nNETBALAN\n0.0 1.0 10 1* 1* 1* 1* 1* /\nThe next example sets network balancing to occur for the first NUPCOL Newton iterations for each time step. All the other parameters are defaulted.\n--\n-- NETWORK BALANCE CONTROL OPTIONS\n--\n-- BAL CONV MAX WTHP WTHP ERR ERR TSTEP\n-- INTV TOL ITRS TOL ITS TARG MAX MIN\nNETBALAN\n-1 1* 1* 1* 1* 1* 1* 1* /"},"NETCOMPA":{"name":"NETCOMPA","sections":["SCHEDULE"],"supported":false,"summary":"The NETCOMPA keyword defines automatic compressors in an extended network, for when the Extended Network option has been activated by the NETWORK keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"INLET","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"OUTLET","description":"","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"GROUP","description":"","units":{},"default":"","value_type":"STRING"},{"index":4,"name":"PHASE","description":"","units":{},"default":"GAS","value_type":"STRING"},{"index":5,"name":"VFT_TABLE_NUM","description":"","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"ALQ","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":7,"name":"GAS_CONSUMPTION_RATE","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"GasSurfaceVolume/Time"},{"index":8,"name":"EXTRACTION_GROUP","description":"","units":{},"default":"","value_type":"STRING"},{"index":9,"name":"COMPRESSOR_TYPE","description":"","units":{},"default":"","value_type":"STRING"},{"index":10,"name":"NUM_COMPRESSION_LEVELS","description":"","units":{},"default":"","value_type":"INT"},{"index":11,"name":"ALQ_LEVEL1","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":12,"name":"COMP_SWITCH_SEQ_NUM","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":12,"size_kind":"list"},"NEXT":{"name":"NEXT","sections":["SCHEDULE"],"supported":false,"summary":"This keyword defines the maximum time step size the simulator should take for the next time step. This keyword can be used to reset the time step for when known large changes to the model are taking place that may result in time step chops. For example, if the reporting time size is using monthly reporting steps via the DATES keyword in the SCHEDULE section, then if for example, a group of wells start production at a given date, then the NEXT keyword can be used to shorten the next step in order to avoid a time step chop.","parameters":[{"index":1,"name":"NSTEP1","description":"NSTEP1 is a real positive value that defines the maximum length of the next time step.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"None","value_type":"DOUBLE","dimension":"Time"},{"index":2,"name":"NSTEP2","description":"NSTEP2 is a character string that should be set to either NO or YES to state if the NSTEP1 should be applied to future reporting time steps. NO: Means that NSTEP1 should not be applied to subsequent reporting time steps. YES: Means that NSTEP1 should be applied to subsequent reporting time steps. The default value of NO means that NSTEP1 will only be applied once.","units":{},"default":"NO","value_type":"STRING"}],"example":"-- NEXT ALL\n-- STEP TIME\n-- ---- ----\nNEXT\n1 'NO' /\nHere the next step size is set to one day and should only be used once.","expected_columns":2,"size_kind":"fixed","size_count":1},"NEXTSTEP":{"name":"NEXTSTEP","sections":["SCHEDULE"],"supported":null,"summary":"This keyword defines the maximum time step size the simulator should take for the next time step. This keyword can be used to limit the time step size when known large changes to the model are taking place that may otherwise result in time step chops. For example, if the simulator is using monthly reporting steps defined by the DATES keyword in the SCHEDULE section, then if a group of wells start production at a given date, then the NEXTSTEP keyword can be used to limit the next time step in order to avoid a time step chop.","parameters":[{"index":1,"name":"NSTEP1","description":"A real positive value that defines the maximum length of the next time step.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"None","value_type":"DOUBLE","dimension":"Time"},{"index":2,"name":"NSTEP2","description":"A defined character string that should be set to either NO or YES to state if the NSTEP1 should be applied to future reporting time steps. NO: Means that NSTEP1 should not be applied to subsequent reporting time steps. YES: Means that NSTEP1 should be applied to subsequent reporting time steps. The default value of NO means that NSTEP1 will only be applied once.","units":{},"default":"NO","value_type":"STRING"}],"example":"The first example shows the direct use of the NEXTSTEP keyword. Here the next time step size is limited to one day for the first time step following the next report time only.\n-- NEXT ALL\n-- STEP TIME\n-- ---- ----\nNEXTSTEP\n1 'NO' /\nThe next example shows a more complete use of the keyword for when the field oil production has increased dramatically from 10,000 stb/d to 50,000 stb/d as indicated by the two GCONPROD keywords.\n-- ------------------------------------------------------------------------------\n-- SCHEDULE SECTION - 2021-01-01\n-- ------------------------------------------------------------------------------\n--\n-- GROUP PRODUCTION CONTROLS\n--\n-- GRUP CNTL OIL WAT GAS LIQ CNTL GRUP GUIDE GUIDE CNTL\n-- NAME MODE RATE RATE RATE RATE OPT CNTL RATE DEF WAT\nGCONPROD\n'FIELD' 'ORAT' 10E3 60E3 300E3 60E3 1* 1* 1* 1* 1* /\n/\nRPTSCHED\n'WELLS=2' 'WELSPECS' 'CPU=2' 'FIP=2' /\nDATES\n2 JAN 2021 /\n/\nRPTSCHED\n'NOTHING' /\nDATES\n1 FEB 2021 /\n1 MAR 2021 /\n/\n-- GROUP PRODUCTION CONTROLS\n--\n-- GRUP CNTL OIL WAT GAS LIQ CNTL GRUP GUIDE GUIDE CNTL\n-- NAME MODE RATE RATE RATE RATE OPT CNTL RATE DEF WAT\nGCONPROD\n'FIELD' 'ORAT' 50E3 90E3 300E3 90E3 1* 1* 1* 1* 1* /\n/\n--\n-- NEXT ALL\n-- STEP TIME\n-- ---- ----\nNEXTSTEP\n1 'NO' /\nDATES\n1 APR 2021 /\n1 MAY 2021 /\n1 JUN 2021 /\n1 JLY 2021 /\n1 AUG 2021 /\n1 SEP 2021 /\n1 OCT 2021 /\n1 NOV 2021 /\n1 DEC 2021 /\n/\nGiven a start date of January 1, 2020 set via the START keyword in the RUNSPEC section, the above example shows the initial oil production of 10,000 stb/d starting in January 1, 2020, and continuing up to March 1, 2021. At the March 1, 2021 report time the field oil production rate is increased to 50,000 stb/d and the maximum next time step is set to one day. After the one day time step is completed (March 2, 2012), the simulator will progressively in increase the time step size until a maximum of 31 days is reached. The 31 day maximum is a result of requesting monthly time steps via the DATES keyword. The intent of using the NEXTSTEP keyword in this case is to prevent time step chops occurring due to the “shock” to the system caused by the large increase in oil production.","expected_columns":2,"size_kind":"fixed","size_count":1},"NEXTSTPL":{"name":"NEXTSTPL","sections":["SCHEDULE"],"supported":false,"summary":"This keyword defines the maximum time step size the simulator should take for the next time step for all Local Grid Refinements (“LGR”). This keyword can be used to reset the time step for when known large changes to the model are taking place that may result in time step chops. For example, if the reporting time size is using monthly reporting steps via the DATES keyword in the SCHEDULE section, then if for example, a group of wells start production at a given date, then the NEXTSTPL keyword can be used to shorten the next step in all the LGRs in order to avoid a time step chop.","parameters":[{"index":1,"name":"NSTEP1","description":"NSTEP1 is a real positive value that defines the maximum length of the next time step.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"None","value_type":"DOUBLE","dimension":"Time"},{"index":2,"name":"NSTEP2","description":"NSTEP2 is a character string that should be set to either NO or YES to state if the NSTEP1 should be applied to future reporting time steps. NO: Means that NSTEP1 should not be applied to subsequent reporting time steps. YES: means that STEP1 should be applied to subsequent reporting time steps. The default value of NO means that NSTEP1 will only be applied once.","units":{},"default":"NO","value_type":"STRING"}],"example":"--\n-- NEXT ALL\n-- STEP TIME\n-- ---- ----\nNEXTSTEP\n1 'NO' /\nHere the next step size for all LGRs is set to one day and should only be used once.","expected_columns":2,"size_kind":"fixed","size_count":1},"NODEPROP":{"name":"NODEPROP","sections":["SCHEDULE"],"supported":true,"summary":"This keyword defines the network node properties for the extended network option for when the Extended Network Model has been invoked by the NETWORK keyword in the RUNSPEC section. There are two types of network facilities in the simulator, the Standard Network model, which is defined with the GRUPNET keyword in the SCHEDULE section and the Extended Network Model defined by the BRANPROP and NODEPROP keywords, again in the SCHEDULE section.","parameters":[{"index":1,"name":"NODE","description":"A character string of up to eight characters in length that defines the node name for the data on this keyword record.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"PRESS","description":"A real value that sets the terminal fixed pressure for the node, this should be set to: A real positive value to define the fixed pressure for the node if the node is a terminal node, otherwise: PRESS should be set to the default value of 1* or a real negative value if the node is not a terminal node.","units":{"field":"psia","metric":"bars","laboratory":"atm"},"default":"1*","value_type":"DOUBLE","dimension":"Pressure"},{"index":3,"name":"CHOKE","description":"CHOKE is a defined character string that sets if the downstream branch (or uptree branch, being the one closer towards the terminal node) from this node should have the capability to choke back the flow rate in order impose a flow constraint. Here the downstream branch is the node furthermost from the wells. Thus for a production network, this will be an outlet branch as the wells are exporting fluid from the branch node. Whereas for an injection node, this is an inlet branch as the wells are importing the injection fluid.","units":{},"default":"NO","value_type":"STRING"},{"index":4,"name":"GASLIFT","description":"A defined character string that sets if the associated subordinate well’s produced gas lift gas should be included in the node’s flow stream (YES), or not (NO). GASLIFT should be set to either: NO: Do not include gas lift gas in the node's production. This means that only the produced gas from the node's subordinate wells will be included in the node's production stream. YES: Include both gas lift gas and produced gas in the node's production. This means that all gas from the subordinate wells will be included in the node's production stream. If NODE does not have any subordinate wells or satellite groups (see the GSATPROD keyword in the SCHEDULE section) directly attached to the node, then GASLIFT should be defaulted (1*) or set to NO. The option is only valid for producing networks","units":{},"default":"NO","value_type":"STRING"},{"index":5,"name":"GROUP","description":"A character string of up to eight characters in length that defines the group for which the automatic choke will be applied in order to match the group’s target rate (the TARGET variable on the GCONPROD keyword in the SCHEDULE section). The target rate is matched by adjusting the pressure drops across the automatic choke. The default value of 1* uses NODE (item one) as the group if it exists in the run. In addition, if NODE is just connected to subordinate wells then GROUP should also be defaulted.","units":{},"default":"1*","value_type":"STRING"},{"index":6,"name":"GRPNAME","description":"GRPNAME defines the name of the source or sink group in the commercial compositional simulator; however, the variable is not used as sources and sinks nodes must have the same name as their comparable groups in the Extended Network Model in both OPM Flow and the commercial black-oil simulator.","units":{},"default":"1*","value_type":"STRING"},{"index":7,"name":"NETYPE","description":"NETYPE defines the network type in the commercial compositional simulator: PROD, WINJ or GINJ. However, the variable is not used as only production networks are supported in the Extended Network Model in both OPM Flow and the commercial black-oil simulator.","units":{},"default":"1*","value_type":"STRING"}],"example":"Given the following Extended Network model in Figure 12.5.\n[formula]\n[formula]\nFigure 12.5: Extend Network Example\nFirst the Extended Network model should be used invoked in the RUNSPEC section, and then the BRANPROP keyword should be used to define the branch network, and finally the NODEPROP keyword is used to describe the node properties with the network.\n-- ==============================================================================\n--\n-- RUNSPEC SECTION\n--\n-- ==============================================================================\nRUNSPEC\n--\n-- ACTIVATE THE EXTENDED NETWORK OPTION AND DEFINE PARAMETERS\n--\n-- MAX. MAX NOT\n-- NODE LINK USED\nNETWORK\n3 2 1* /\n…..…………..\n..……..…..\n-- ==============================================================================\n--\n-- SCHEDULE SECTION\n--\n-- ==============================================================================\nSCHEDULE\n--\n-- EXTENDED NETWORK BRANCH PROPERTIES\n--\n-- DOWN UP VFP VFP\n-- NODE NODE TABLE ALFQ\nBRANPROP\nB1 PLAT-A 5 1* /\nC1 PLAT-A 4 1* /\n/\n--\n-- EXTENDED NETWORK NODE PROPERTIES\n--\n-- NODE NODE CHOKE GAS CHOKE SOURCE NETWORK\n-- NAME PRESS OPTN LIFT GROUP SINK TYPE\nNODEPROP\nPLAT-A 21.0 NO NO /\nB1 1* NO NO /\nC1 1* NO NO /\n/\nHere the main platform for the field, PLAT-A, has a fixed 21 barsa pressure applied as an operating constraint.","expected_columns":7,"size_kind":"list"},"NWATREM":{"name":"NWATREM","sections":["SCHEDULE"],"supported":false,"summary":"The NWATREM keyword defines an extended network node as a point where water is removed from the network, for when the Extended Network option has been activated by the NETWORK keyword in the RUNSPEC section. The water to be removed can be specified as a rate or as a fraction of the total volume passing through the node.","parameters":[{"index":1,"name":"NODE","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"WAX_RATE","description":"","units":{},"default":"1e+100","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time"},{"index":3,"name":"MAX_FRAC_REMOVAL","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"}],"example":"","expected_columns":3,"size_kind":"list"},"PICOND":{"name":"PICOND","sections":["SCHEDULE"],"supported":false,"summary":"The PICOND keyword defines the Generalized Pseudo Pressure (“GPP”)310\n Whitson, C. H. and Fevang, Ø. “Generalised Pseudopressure Well Treatment in Reservoir Simulation,” Presented at the IBC Technical Services Conference on Optimisation of Gas Condensate Fields, Aberdeen, UK (June 26-27, 1997) and 311\n Whitson, C. H. and Fevang, Ø. “Modeling Gas Condensate Well Deliverability,” paper SPE 30714, SPE Reservoir Engineering (1996) 11, No. 4, 221-230; also presented at the SPE Annual Technical Conference and Exhibition, Dallas, Texas, USA (October 22-25, 1995).parameters used in a gas condensate well connection inflow equations. GPP accounts for both the impact of condensate drop out and compressibility in the mobility inflow term . If the keyword is absent from the input deck then the default values are applied.","parameters":[{"index":1,"name":"MAX_INTERVAL_BELOW_DEWPOINT","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":2,"name":"MAX_INTERVAL_ABOVE_DEWPOINT","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":3,"name":"D_F","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"},{"index":4,"name":"INCLUDE","description":"","units":{},"default":"NO","value_type":"STRING"},{"index":5,"name":"F_L","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"1"},{"index":6,"name":"F_U","description":"","units":{},"default":"1.1","value_type":"DOUBLE","dimension":"1"},{"index":7,"name":"DELTA_WAT_SAT","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":8,"name":"DELTA_PRESSURE","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":9,"name":"DELTA_FRAC_COMP","description":"","units":{},"default":"0.01","value_type":"DOUBLE","dimension":"1"},{"index":10,"name":"MAX_DELTA_TIME","description":"","units":{},"default":"-1","value_type":"DOUBLE","dimension":"Time"},{"index":11,"name":"ADAPTIVE_ORD_CONTROL","description":"","units":{},"default":"-1","value_type":"DOUBLE"},{"index":12,"name":"ADAPTIVE_ORD_MIN_SPACING","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"}],"example":"","expected_columns":12,"size_kind":"fixed","size_count":1},"PIMULTAB":{"name":"PIMULTAB","sections":["SCHEDULE"],"supported":false,"summary":"Not supported. (But perhaps it should be!)","parameters":[{"index":1,"name":"WCUT","description":"A real monotonically increasing positive columnar vector that defines the maximum surface water cut for the corresponding PIMULT vector. Water cut is defined as[f sub w ~=~ {q sub w } over {q sub w `+` q sub o}]..","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE"},{"index":2,"name":"PIMULT","description":"A real positive decreasing columnar vector that defines the productivity index multiplier used to scale a well’s connection factors, for the corresponding WCUT vector.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None"}],"example":"Given NTPIMT equals two and NRPIMT equals four on PIMTDIMS keyword in the RUNSPEC section, then:\n-- DEFINE WELL PRODUCTIVITY INDEX VERSUS WATER CUT TABLES\n--\n-- MAX PI\n-- WCUT MULT\n-- ------ ------\nPIMULTAB\n0.0000 1.0000\n0.2500 0.9500\n0.5000 0.8500\n0.7500 0.7500 /\n--\n--\n0.0000 1.0000\n0.2500 0.9500\n0.5000 0.8500\n0.7500 0.7500 /\nThe next example is summarized from the Norne model with NTPIMT equals one and NRPIMT equals to 51 on the PIMTDIMS keyword in the RUNSPEC section.\n--\n-- DEFINE WELL PRODUCTIVITY INDEX VERSUS WATER CUT TABLES\n-- The following is the reviewed model in Aug-2006, low-high case\n-- a=0.25, b=0.1; PIMULT=(1-a)/exp(fw/b)+a\n--\n-- MAX PI\n-- WCUT MULT\n-- ------ ------\nPIMULTAB\n0.000 1.0000\n0.025 0.8341\n0.050 0.7049\n0.075 0.6043\n0.100 0.5259\n0.125 0.4649\n0.150 0.4173\n0.175 0.3803\n0.200 0.3515\n0.225 0.3290\n0.250 0.3116\n0.275 0.2979\n0.300 0.2873\n0.325 0.2791\n0.350 0.2726\n0.375 0.2676\n0.400 0.2637\n0.425 0.2607\n0.450 0.2583\n0.475 0.2565\n0.500 0.2551\n0.525 0.2539\n0.550 0.2531\n0.575 0.2524\n0.600 0.2519\n0.625 0.2514\n0.650 0.2511\n0.675 0.2509\n0.700 0.2507\n0.725 0.2505\n0.750 0.2504\n0.775 0.2503\n0.800 0.2503\n0.825 0.2502\n0.850 0.2502\n0.875 0.2501\n0.900 0.2501\n0.925 0.2501\n0.950 0.2501\n0.975 0.2500\n1.000 0.2500 /","size_kind":"fixed","variadic_record":true},"PLYROCKM":{"name":"PLYROCKM","sections":["SCHEDULE"],"supported":false,"summary":"The PLYROCKM keyword modifies rock properties entered via the PLYCAMAX, PLYKRRF, PLYRMDEN, and PLYROCK keywords in the PROPS section, for when the Polymer option has been activated by the POLYMER keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"IPV","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":2,"name":"RRF","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"ROCK_DENSITY","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Density"},{"index":4,"name":"AI","description":"","units":{},"default":"1","value_type":"DOUBLE","dimension":"1"},{"index":5,"name":"MAX_ADSORPTION","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"}],"example":"","expected_columns":5,"size_kind":"fixed"},"PRIORITY":{"name":"PRIORITY","sections":["SCHEDULE"],"supported":false,"summary":"The PRIORITY keyword activates the Well Priority option and defines the coefficients in the well priority equation. Wells under group control are ranked based on their well potential in order to satisfy group controls. For example if a group’s oil target is exceeded, then the group may shut-in the lease productive oil wells based on their well potential. The Priority option is an alternative form of ranking the wells based on the following equation:","parameters":[{"index":1,"name":"TIME","description":"A real positive integer that defines the minimum time interval between executing the well priority calculation. The calculation is performed at the beginning of the time step that exceeds the previous calculation (t0) by a minimum of TIME, that is for when tn ≥ ( t0 + TIME). Note that the default value of zero means that the calculation is performed at each time step. As a consequence, this may result in some oscillation as well wells are switched on/off at subsequent time steps.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"0","value_type":"DOUBLE","dimension":"Time"},{"index":2,"name":"A1","description":"A real positive integer greater than or equal to zero that defines a1 priority coefficient in equation (12.31).","units":{},"default":"0","value_type":"DOUBLE"},{"index":3,"name":"A2","description":"A real positive integer greater than or equal to zero that defines a2 priority coefficient in equation (12.31).","units":{},"default":"0","value_type":"DOUBLE"},{"index":4,"name":"A3","description":"A real positive integer greater than or equal to zero that defines a3 priority coefficient in equation (12.31).","units":{},"default":"0","value_type":"DOUBLE"},{"index":5,"name":"A4","description":"A real positive integer greater than or equal to zero that defines a4 priority coefficient in equation (12.31).","units":{},"default":"0","value_type":"DOUBLE"},{"index":6,"name":"B1","description":"A real positive integer greater than or equal to zero that defines b1 priority coefficient in equation (12.31).","units":{},"default":"0","value_type":"DOUBLE"},{"index":7,"name":"B2","description":"A real positive integer greater than or equal to zero that defines b2 priority coefficient in equation (12.31).","units":{},"default":"0","value_type":"DOUBLE"},{"index":8,"name":"B3","description":"A real positive integer greater than or equal to zero that defines b3 priority coefficient in equation (12.31).","units":{},"default":"0","value_type":"DOUBLE"},{"index":9,"name":"B4","description":"A real positive integer greater than or equal to zero that defines b4 priority coefficient in equation (12.31).","units":{},"default":"0","value_type":"DOUBLE"},{"index":10,"name":"A2","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":11,"name":"B2","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":12,"name":"C2","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":13,"name":"D2","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":14,"name":"E2","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":15,"name":"F2","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":16,"name":"G2","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":17,"name":"H2","description":"","units":{},"default":"0","value_type":"DOUBLE"}],"example":"--\n-- SETS COEFFICIENTS FOR WELL PRIORITIZATION OPTION\n--\n-- TIME A B C D E F G H\n-- STEP Qo Qw Qg Qo Qw Qg\nPRIORITY\n0.0 0.0 1.0 0.0 0.0 1.0 0.0 0.0 0.0 / High Oil Pot\n-- 0.0 0.0 1.0 1.0 0.0 0.0 0.0 1.0 0.0 / Low Water Cut Pot\n-- 0.0 0.0 1.0 0.0 0.0 0.0 0.0 0.0 1.0 / Low GOR Pot\nThe above example defines the well priority calculation to be based on a well’s oil potential, with calculation to be performed at each time step. Note that the low water cut and low GOR options are given for reference but are commented out and therefore ignored by the simulator.\n| [\"Priority\"`=`{ a sub{1}`+`a sub{2}Q sub{oil}`+a sub{3}Q sub{water}`+a sub{4}Q sub{gas}} over { b sub{1}`+`b sub{2}Q sub{oil}`+b sub{3}Q sub{water}`+b sub{4}Q sub{gas} }] | (12.31) |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|","expected_columns":17,"size_kind":"fixed","size_count":1},"PRORDER":{"name":"PRORDER","sections":["SCHEDULE"],"supported":false,"summary":"PRORDER defines the order of group production rules to be implemented fore when a group’s target is not satisfied.","parameters":[{"index":1,"name":"NO1","description":"","units":{},"default":"","value_type":"STRING","record":1},{"index":2,"name":"NO2","description":"","units":{},"default":"","value_type":"STRING","record":1},{"index":3,"name":"NO3","description":"","units":{},"default":"","value_type":"STRING","record":1},{"index":4,"name":"NO4","description":"","units":{},"default":"","value_type":"STRING","record":1},{"index":5,"name":"NO5","description":"","units":{},"default":"","value_type":"STRING","record":1},{"index":1,"name":"OPT1","description":"","units":{},"default":"YES","value_type":"STRING","record":2},{"index":2,"name":"OPT2","description":"","units":{},"default":"YES","value_type":"STRING","record":2},{"index":3,"name":"OPT3","description":"","units":{},"default":"YES","value_type":"STRING","record":2},{"index":4,"name":"OPT4","description":"","units":{},"default":"YES","value_type":"STRING","record":2},{"index":5,"name":"OPT5","description":"","units":{},"default":"YES","value_type":"STRING","record":2}],"example":"","records_meta":[{"expected_columns":5},{"expected_columns":5}],"size_kind":"fixed","size_count":2},"PYACTION":{"name":"PYACTION","sections":["SCHEDULE"],"supported":true,"summary":"The PYACTION keyword is part of OPM Flow’s Python scripting facility that loads a standard Python script file that can be used to define a series of conditions and actions as the simulation proceeds through time. The “included” Python script file is executed by the standard Python interpreter. Thus, OPM Flow’s Python scripting facility offers greater flexibility compared to the commercial simulator’s ACTION series of keywords (ACTION, ACTIONG, ACTIONR, ACTIONS, ACTIONW and ACTIONX) that can apply Boolean conditional tests to variables at the field, group, region, well segment and well levels. Note that OPM Flow has also implemented the commercial simulator’s ACTIONX keyword, but not the ACTION, ACTIONG, ACTIONR, ACTIONS and ACTIONW keywords, as the ACTIONX keyword implements their functionality with greater flexibility. For a python class documentation and for further documentation and examples, also refer to the OPM Online Python Documentation.","parameters":[{"index":1,"name":"ACTNAME","description":"ACTNAME is a character sting of any length enclose in quotes that defines the name of this action definition.","units":{},"default":"None","record":1,"value_type":"STRING"},{"index":2,"name":"ACTNSTEP","description":"ACTNSTEP is a defined character string that indicates the number of times the action should be performed, and should be set to one of the following: SINGLE: Here the action script is run only once. UNLIMITED: If this option is selected then the action is run at the end of every time step. FIRST_TRUE: This option forces the action to be run at the end of every time step until the script returns a value of True. Note that the FIRST_TRUE option is only supported for back compatibility when using the deprecated run() function style Python scripts.","units":{},"default":"SINGLE","record":1,"value_type":"STRING"},{"index":1,"name":"FILENAME","description":"A character string enclosed in quotes that defines the Python module/script file to read in and to be processed by OPM Flow.","units":{},"default":"None","record":2,"value_type":"STRING"}],"example":"The first example checks if well OP01 has a water cut greater than 0.8 and if so then the well is shut in. In the input deck we would have:\n--\n-- START OF PYACTION SECTION\n--\n-- ACTNAME ACTNSTEP\nPYACTION\n'MAXWCUT' 'UNLIMITED' /\n'pthon/script/MAXWCUT.py' /\n--\n-- END OF PYACTION SECTION\n--\nAnd then in the Python module file 'pthon/script/MAXWCUT.py' one would have:\n#\n# OPM Flow PYACTION Module Script\n#\nimport opm_embedded\nschedule = opm_embedded.current_schedule\nsummary_state = opm_embedded.current_summary_state\nif (not 'setup_done' in locals()):\nexecuted = False\nsetup_done = True\nif (not executed and summary_state.well_var(\"OP1\", \"WWCT\") > 0.80):\nmessage = \"Well OP01 has been shut-in due to WWCT > 0.80\\n\"\nopm_embedded.OpmLog.info(message)\nschedule.shut_well(\"OP1\")\nexecuted = True\nNote how the 'executed' variable is used to ensure that the action is only executed once the first time the water cut is greater than 0.8.\nThe next example is based on the first example from the ACTIONX keyword (ACTIONX – Define Action Conditions and Command Processing). The Python script first checks if the field’s water production is greater than 30,000 stb/d, and if not returns control back to the simulator. If the field water production is greater than 30,000 stb/d then the script uses a Python variable count to keep track of the number of times the script has been executed, and then sorts the wells from high water cut to low, via the wct_list variable, and then shuts in the worst offending well. If a well is shut-in the count variable is increased by one and control is passed back to the simulator. The script is executed as maximum of ten times.\n--\n-- START OF PYACTION SECTION\n--\n-- ACTNAME ACTNSTEP\nPYACTION\n'WSHUTIN' 'UNLIMITED' /\n'pthon/script/WSHUTIN.py' /\n--\n-- END OF PYACTION SECTION\n--\nAnd then in the Python module file 'pthon/script/WSHUTIN.py' one would have:\n#\n# OPM Flow PYACTION Module Script\n#\nimport opm_embedded\nschedule = opm_embedded.current_schedule\nsummary_state = opm_embedded.current_summary_state\nif (not 'setup_done' in locals()):\nexecution_counter = 0\nsetup_done = True\nif (execution_counter < 10 and summary_state[\"FWPR\"] >= 30000):\n#\n# Get Sorted Well List\n#\nwct_list = sorted( [ (well, summary_state.well_var(well, \"WWCT\"))\nfor well in summary_state.wells], reverse=True )\n#\n# Shut-in Well with Highest Water Cut\n#\nwell, wwct = wct_list[0]\nif wwct > 0:\nschedule.shut_well(well)\nexecution_counter += 1\nNote that by using PYACTION it makes sense to combine the UDQ variable into the PYACTION statement, like shown in the example above, although this is not necessary, as one could in principle use a normal UDQ statement and then access the variables in the PYACTION script using the summary_state variable.\nThe final example checks to see if the field’s gas rate is below 600 MMscf/d and if the simulation time is greater that January 1, 2030. If it is, then compression is installed by re-setting all the gas producing well’s THP and BHP pressures to 450 psia and 300 psia respectively. In addition all gas wells currently shut-in are tested to see if they can be opened up under the new THP and BHP constraints.\n--\n-- START OF PYACTION SECTION\n--\n-- ACTNAME ACTNSTEP\nPYACTION\n'WSHUTIN' 'UNLIMITED' /\n'pthon/script/PHASE3.py' /\n--\n-- END OF PYACTION SECTION\n--\nAnd then in the Python module file 'pthon/script/PHASE3.py' one would have:\n#\n# OPM Flow PYACTION Module Script\n#\nimport datetime\nimport opm_embedded\nschedule = opm_embedded.current_schedule\nsummary_state = opm_embedded.current_summary_state\nif (not 'setup_done' in locals()):\nexecuted = False\nsetup_done = True\nif not executed:\nsim_time = schedule.start +\ndatetime.timedelta( seconds = summary_state.elapsed() )\nif (summary_state[\"FGPR\"] < 600000 and\nsim_time > datetime.datetime(2030, 1, 1)):\n#\n# Do WELTARG and WTEST action\n#\n...\nexecuted = True\nNote how the current simulation time (sim_time) is evaluated from the simulation start time (schedule.start) and elapsed time (summary_state.elapsed); an","records_meta":[{"expected_columns":2},{"expected_columns":1}],"size_kind":"fixed","size_count":2},"QDRILL":{"name":"QDRILL","sections":["SCHEDULE"],"supported":false,"summary":"The QDRILL keyword places previously defined wells in the Sequential Drilling Queue. Wells in this type of queue will be automatically drilled and completed in the sequence entered in order to satisfy group targets, as defined by the GCONPROD, GCONINJE and GCONSALE keywords. or a group’s production potential as per the GDRILLPOT keyword. All the previously mentioned keywords are in the SCHEDULE section.","parameters":[{"index":1,"name":"WELL_NAME","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","size_kind":"fixed","size_count":1,"variadic_record":true},"RCMASTS":{"name":"RCMASTS","sections":["SCHEDULE"],"supported":false,"summary":"RCMASTS is used when reservoir coupling is invoked by the GRUPMAST and SLAVES keywords in the SCHEDULE section. The keyword should be placed within the master file and it sets the minimum time step size for groups for when a group is being restricted by a group’s limiting flow rate fractional change (see the GRUPMAST keyword in the SCHEDULE section).","parameters":[{"index":1,"name":"MIN_TSTEP","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Time"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"REACHES":{"name":"REACHES","sections":["SCHEDULE"],"supported":false,"summary":"The REACHES keyword defines the reach structure of a previously characterized river system using the RIVERSYS keyword in the SCHEDULE section. The River option must be activated via the RIVRDIMS keyword in the RUNSPEC section in order to use these keywords.","parameters":[{"index":1,"name":"RIVER","description":"","units":{},"default":"","value_type":"STRING","record":1},{"index":2,"name":"XPOS","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length","record":1},{"index":3,"name":"YPOS","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length","record":1},{"index":4,"name":"ZPOS","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length","record":1},{"index":5,"name":"LENGTH1","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length","record":1},{"index":6,"name":"INPUT_TYPE","description":"","units":{},"default":"","value_type":"STRING","record":1},{"index":1,"name":"START_REACH","description":"","units":{},"default":"","value_type":"INT","record":2},{"index":2,"name":"END_REACH","description":"","units":{},"default":"","value_type":"INT","record":2},{"index":3,"name":"OUTLET_REACH","description":"","units":{},"default":"","value_type":"INT","record":2},{"index":4,"name":"BRANCH","description":"","units":{},"default":"","value_type":"STRING","record":2},{"index":5,"name":"LENGTH2","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length","record":2},{"index":6,"name":"DEPTH","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length","record":2},{"index":7,"name":"PROFILE","description":"","units":{},"default":"1","value_type":"INT","record":2},{"index":8,"name":"ROUGHNESS","description":"","units":{},"default":"","value_type":"DOUBLE","record":2},{"index":9,"name":"XLENGTH","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length","record":2},{"index":10,"name":"YLENGTH","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length","record":2},{"index":11,"name":"REACH_LENGTH","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Length","record":2},{"index":12,"name":"NUM_REACHES","description":"","units":{},"default":"1","value_type":"INT","record":2},{"index":13,"name":"DEPTH_SOMETHING","description":"","units":{},"default":"1","value_type":"INT","record":2}],"example":"","records_meta":[{"expected_columns":6},{"expected_columns":13}],"size_kind":"list"},"READDATA":{"name":"READDATA","sections":["SCHEDULE"],"supported":false,"summary":"The READDATA keyword enables the simulator to read SCHEDULE data files generated by external programs on the fly, that is as the run is progressing. The external program can “hold” the simulation by using a file lock, in order for the external program to evaluate the current simulation results, then write out a SCHEDULE data file for the next time step, and finally releasing the “hold” by deleting the file lock and continuing with newly written SCHEDULE data file. The mechanism can be repeated so that the external program is dictating how the simulation progresses through time,","parameters":[{"index":1,"name":"INPUT_METHOD","description":"","units":{},"default":"FILE","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"RIVDEBUG":{"name":"RIVDEBUG","sections":["SCHEDULE"],"supported":false,"summary":"This keyword defines the debug data associated with rivers to be written to the debug file (*.DBG), for when the River option has been activated via the RIVRDIMS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"RIVER","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"DEBUG_CONTROL","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":2,"size_kind":"list"},"RIVRPROP":{"name":"RIVRPROP","sections":["SCHEDULE"],"supported":false,"summary":"The RIVRPROP keyword modifies the individual reaches in a river structure of a previously characterized river system using the RIVERSYS and the REACHES keywords in the SCHEDULE section. The River option must be activated via the RIVRDIMS keyword in the RUNSPEC section in order to use this keyword. RIVRPROP is an alternative and a more concise way to changing the individual reaches in a river structure than the REACHES keyword.","parameters":[{"index":1,"name":"RIVER","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"REACH1","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"REACH2","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"ROUGHNESS","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","expected_columns":4,"size_kind":"list"},"RIVSALT":{"name":"RIVSALT","sections":["SCHEDULE"],"supported":false,"summary":"The RIVSALT keyword defines the injected salt concentration in individual river branches in a previously characterized river system using the RIVERSYS and the REACHES keywords in the SCHEDULE section. The River option must be activated via the RIVRDIMS keyword in the RUNSPEC section in order to use this keyword. In addition, the Brine option must also be enabled via the BRINE keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"RIVER","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"SALINITY","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Mass/LiquidSurfaceVolume"},{"index":3,"name":"BRANCH","description":"","units":{},"default":"","value_type":"STRING"},{"index":4,"name":"REACH","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":4,"size_kind":"list"},"RIVTRACE":{"name":"RIVTRACE","sections":["SCHEDULE"],"supported":false,"summary":"The RIVTRACE keyword defines the injected tracer concentration in individual river branches in a previously characterized river system using the RIVERSYS and the REACHES keywords in the SCHEDULE section. The River option must be activated via the RIVRDIMS keyword in the RUNSPEC section in order to use this keyword. In addition, the Tracer option must also be enabled by the TRACER keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"RIVER","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"TRACER","description":"","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"TC","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":4,"name":"TCUM","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1/LiquidSurfaceVolume"},{"index":5,"name":"BRANCH","description":"","units":{},"default":"","value_type":"STRING"},{"index":6,"name":"REACH","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":6,"size_kind":"list"},"RPTHMG":{"name":"RPTHMG","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, RPTHMG, either enables or disables history match output reporting to the history match file (*.HMD) for the named group, for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"GROUP","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"INCLUDE","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":2,"size_kind":"list"},"RPTHMW":{"name":"RPTHMW","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, RPTHMG, either enables or disables history match output reporting to the history match file (*.HMD) for the named well, for when the History Match Gradient option has been activated by the HMDIMS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"GROUP","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"INCLUDE","description":"","units":{},"default":"ON","value_type":"STRING"},{"index":3,"name":"INCLUDE_RFT","description":"","units":{},"default":"OFF","value_type":"STRING"}],"example":"","expected_columns":3,"size_kind":"list"},"RPTSCHED":{"name":"RPTSCHED","sections":["SCHEDULE"],"supported":true,"summary":"This keyword defines the data in the SCHEDULE section that is to be printed to the output print file in human readable format. The keyword has two distinct forms, the first of which consists of the keyword followed by a series of integers on the next line indicating the data to be printed (see the first example). This is the original format in the commercial simulator and was subsequently superseded by the second format. The second format consists of the keyword followed by a series of character strings that indicate the data to be printed. In most cases the character string is the keyword used to define the data in the OPM Flow input deck, for example WELSPECS to defined the basic well definitions.","parameters":[{"index":1,"name":"FIP","description":"Print the fluid in-place report. The parameter is assigned a value, OPTION, using the form FIP = OPTION, where OPTION is an integer variable set to: OPTION = 1 then the report is for the field only. OPTION = 2 then in addition to the field report, a report is produced for each FIPNUM region, as defined by the FIPNUM keyword in the REGIONS section. Note the commercial simulator also prints the flows to other regions as well as the flows from the wells. This additional reporting option has not been implemented in OPM Flow. OPTION = 3 then in addition to the above, a balance report is also produced for fluid in-place regions defined by the FIP keyword in the REGIONS section.","units":{},"default":"FIP=2","value_type":"STRING"},{"index":2,"name":"FIPRESV","description":"Print the reservoir volumes in-place report.","units":{},"default":"None"},{"index":3,"name":"NOTHING","description":"Switches off all printed reports in the SCHEDULE section.","units":{},"default":"N/A"},{"index":4,"name":"SALT","description":"Print grid block salt concentration values. Note this is an OPM Flow specific keyword.","units":{},"default":"N/A"},{"index":5,"name":"RESTART","description":"RESTART defines the frequency at which the restart data for restarting a run is written to the RESTART file. The parameter is assigned a value, OPTION, using the form RESTART = OPTION, where OPTION is an integer variable set to: OPTION = 1 then the restart files are written at every report time, but only the last one in the run is kept. This minimizes the restart file size but only the final results are stored, limiting the visualization in OPM ResInsight. OPTION = 2 then the phase inter-blocks are written to the restart files, in addition to the standard data. OPTION = 3 then the fluid in-place and phase potentials are also written to the restart file. OPTION = 6 then the restart files are written at every time step. See the RPTRST keyword in the SOLUTION section for a more flexible way to write out restart files.","units":{},"default":""},{"index":6,"name":"WELLS","description":"The WELLS option turns on production and injection rate and cumulative volume reporting for produced and injected fluids. The parameter has several levels of reporting details set by the assigned OPTION value, using the form WELLS = OPTION, where OPTION is an integer variable set to: OPTION = 1 report volumes at the well level. OPTION = 2 report volumes at the well and the well connection levels. OPTION = 3 report volumes for layer totals. OPTION = 4 report volumes for layer totals and for wells. OPTION = 5 report volumes for layer totals and for wells and well connections. Only OPTION equal to one is supported by OPM Flow.","units":{},"default":"WELLS=1"},{"index":7,"name":"WELSPECS","description":"WELSPECS switches on reporting of the well connections, wells and groups at each report time step. There are numerous reports associated with this option. Unlike the other reporting parameters that produce a report for each reporting time step, the WELSPECS report option only produces a report if an associated keyword has been activated at the current reporting time step. For example, if the reporting time steps are January, February, and March 2020, and the RPTSCHED WELSPECS option is activated in January, with wells OP01 and OP02 being declared via the WELSPECS and COMPDAT keywords, then a report will be printed for January for these two wells. If there are no further well activations until March, with well OP03 being declared, then there will be no report for February, and only well OP03 will reported at the March reporting time step.","units":{},"default":""}],"example":"The first example shows the original format of this keyword.\n--\n-- DEFINE SCHEDULE SECTION REPORT OPTION (ORIGINAL FORMAT)\n--\nRPTSCHED\n1 2*0 1 3*1 /\nThe next example shows the second format of the keyword.\n-- ==============================================================================\n--\n-- SCHEDULE SECTION\n--\n-- ==============================================================================\nSCHEDULE\n-- ------------------------------------------------------------------------------\n-- SCHEDULE SECTION - 2000-01-01\n-- ------------------------------------------------------------------------------\nRPTSCHED\n'WELLS=2' 'WELSPECS' 'CPU=2' 'FIP=2' /\nDATES\n1 JAN 2000 /\n/\nRPTSCHED\n'NOTHING' /\nDATES\n1 FEB 2000 /\n1 MAR 2000 /\n1 APR 2000 /\n1 MAY 2000 /\n1 JUN 2000 /\n1 JLY 2000 /\n1 AUG 2000 /\n1 SEP 2000 /\n1 OCT 2000 /\n1 NOV 2000 /\n1 DEC 2000 /\n/\nIn the above example monthly reporting time steps have been used with a SCHEDULE section report on the January 1, 2000; after which all reports are switched off for the subsequent reporting time steps.\n| Note Unlike the other reporting keywords in the RUNSPEC, GRID, EDIT, PROPS and SOLUTION keywords, the requested reports on the this keyword remain in effect until they are switched off by this keyword, that is, the reports are written out every report time step until requested to stop. Use the ‘NOTHING’ parameter to switch off all reporting. |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Note Note that the “PORV” quantity in the FIP (Balance) Report, as shown in Figure 12.6, is reported at reference conditions, meaning there is no pressure dependence involved. However, the “TOTAL PORE VOLUME” values in the Reservoir Volumes Report (Figure 12.7) are pressure dependent pore volumes. Thus, for region one the “PORV” value is 44,729,956 rm3 (Figure 12.6) and the “TOTAL PORE VOLUME” (Figure 12.7) is 44,719,142 rm3. This is the same as the commercial simulator. |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"fixed","size_count":1,"variadic_record":true},"SCDATAB":{"name":"SCDATAB","sections":["SCHEDULE"],"supported":false,"summary":"SCDATAB defines well connection Productivity Index (“PI”) reduction multipliers versus scale deposited per unit length of the perforated interval tables, for when the Scale Deposition option has been activated by declaring the dimensions of the scaling deposition tables using the SCDPDIMS keyword in the RUNSPEC section. The SCDATAB tables are allocated to individual wells using the WSCTAB keyword and the rate of scale accumulation around the well connections is given by the SCDPTAB keyword; both keywords are in the SCHEDULE section.","parameters":[{"index":1,"name":"SCALE_DATA","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":["1","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"SCDETAB":{"name":"SCDETAB","sections":["SCHEDULE"],"supported":false,"summary":"SCDETAB defines well connection karst314\n Karst is a topography formed from the dissolution of soluble rocks such as limestone, dolomite, and gypsum. Karst aquifers are characterized by a network of conduits and caves, with the conduits and caves draining the pore space between the limestone grains (intergranular or primary porosity) and the fractures (secondary porosity) formed by joints, bedding planes, and faults. aquifer properties for modeling scale deposited by dissolution of calcite from the aquifer water, for when the Scale Deposition option has been activated by declaring the dimensions of the scaling deposition tables using the SCDPDIMS keyword in the RUNSPEC section. The SCDETAB tables are allocated to individual wells using the WSCTAB keyword in the SCHEDULE section.","parameters":[{"index":1,"name":"SCALE_DATA","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":["1","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"SCDPTAB":{"name":"SCDPTAB","sections":["SCHEDULE"],"supported":false,"summary":"SCDATAB defines the well connection scale deposition rate as a function of sea water flow rate, for when the Scale Deposition option has been activated by declaring the dimensions of the scaling deposition tables using the SCDPDIMS keyword in the RUNSPEC section. The SCDATAB tables are allocated to individual wells using the WSCTAB keyword and the sea water fraction is based on a water tracer entered via the SCDPTRAC keyword; both keywords are in the SCHEDULE section.","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["1","1"]}],"example":"","size_kind":"fixed","variadic_record":true},"SCDPTRAC":{"name":"SCDPTRAC","sections":["SCHEDULE"],"supported":false,"summary":"The SCDPTRAC keyword is used to allocate an existing passive water tracer defined by the TRACER keyword in the PROPS section, to represent the sea water flowing into a well connection as a fraction of the total water influx. The keyword is used together with the SCDPTAB keyword in the SCHEDULE section to calculated the volume of scale deposited around the well connections.","parameters":[{"index":1,"name":"NAME","description":"A three letter character string defining the tracer’s name that has previously been defined by the TRACER keyword in the PROPS section","units":{},"default":"None","value_type":"STRING"}],"example":"In the PROPS section define a tracer in the water phase, for example:\n--\n-- DEFINE TRACER NAMES\n--\n-- TRACER TRACER\n-- NAME PHASE\n-- ------ ------\nTRACER\n'SEA' 'WAT' / SEA WATER TRACER\n/\nThen in the SCHEDULE section allocate the previously defined water tracer as a sea water tracer to be used with the scale deposition facility, that is:\n--\n-- ALLOCATE SEA WATER TRACER FOR SCALE DEPOSITION\n--\n-- TRACER\n-- NAME\n-- ------\nSCDPTRAC\n'SEA' / SEA WATER TRACER\n/","expected_columns":1,"size_kind":"fixed","size_count":1},"SCHEDULE":{"name":"SCHEDULE","sections":["SCHEDULE"],"supported":null,"summary":"The SCHEDULE activation keyword marks the end of the SUMMARY section and the start of the SCHEDULE section that defines the group and well definitions, operating and economic constraints, as well as how OPM Flow should advance through time. Numerical controls are also defined in this section and all parameters can be varied through time.","parameters":[],"example":"-- ==============================================================================\n--\n-- SCHEDULE SECTION\n--\n-- ==============================================================================\nSCHEDULE\nThe above example marks the end of the SUMMARY section and the start of the SCHEDULE section in the OPM Flow data input file.","size_kind":"none","size_count":0},"SEPVALS":{"name":"SEPVALS","sections":["SCHEDULE"],"supported":false,"summary":"The SEPVALS keyword defines the initial and subsequent separator oil formation volume factor (Bo) and Gas Oil Ratio (“GOR” or Rs). The facility is used in black-oil modeling to re-scale the PVT data entered via the PROPS section, based on the saturation point oil formation volume factor (Bob) and the initial saturated gas-oil ratio (Rsi) entered on the SEPVALS keyword. The first occurrence of this keyword sets the initial conditions and must be followed by the GSEPCOND keyword that assigns previously defined separators to a group.","parameters":[{"index":1,"name":"SEPARATOR","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"BO","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"RS","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"}],"example":"","expected_columns":3,"size_kind":"list"},"SIMULATE":{"name":"SIMULATE","sections":["SCHEDULE"],"supported":false,"summary":"SIMULATE switches the mode of the simulation to run simulation mode from the data input checking mode activated by the NOSIM keyword in the SCHEDULE section. Note that if NOSIM has been used in the RUNSPEC section then SIMULATE will have no effect.","parameters":[],"example":"The example below switches OPM Flow to no simulation mode for data checking of the input deck.\n--\n-- ACTIVATE SIMULATION MODE TO RUN THE MODEL\n--\nSIMULATE","size_kind":"none","size_count":0},"SKIPREST":{"name":"SKIPREST","sections":["SCHEDULE"],"supported":null,"summary":"This keyword turns on skipping of keywords up to the start of the restart point, as defined on the RESTART keyword in the RUNSPEC section. The RESTART keyword defines the parameters to restart the simulation from a previous run that has written a RESTART file out to disk. Activating the SKIPREST keyword causes the simulator to only read in data it requires for restarting the run up to the RESTART point (RSNUM on the RESTART keyword in the SOLUTION section). Note that certain keywords always need to be present in a restart run in the SCHEDULE section as the data is not stored on the RESTART file, for example the VFP tables (VFPPROD and VFPINJ keywords). The SKIPREST keyword automatically processes the input deck and reads the required data.","parameters":[],"example":"The example below defines a restart from the previously run NOR-OPM-A01 case at time step number 40.\n-- ==============================================================================\n--\n-- SOLUTION SECTION\n--\n-- ==============================================================================\nSOLUTION\n--\n-- FLEXIBLE RESTART FROM PREVIOUS SIMULATION RUN\n--\n-- FILE RESTART RESTART FILE\n-- NAME NUMBER TYPE FORMAT\nRESTART\n'NOR-OPM-A01' 40 1* 1* /\nThen in the SCHEDULE section the SKIPREST keyword is used to correctly read in the schedule data up to the RESTART point.\n-- ==============================================================================\n--\n-- SCHEDULE SECTION\n--\n-- ==============================================================================\nSCHEDULE\n--\n-- ACTIVATE SKIPREST OPTION TO AVOID MODIFYING SCHEDULE SECTION\n--\nSKIPREST","size_kind":"none","size_count":0},"SLAVES":{"name":"SLAVES","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, SLAVES, defines the name of the slave reservoirs and their associated simulation input files, for when the Reservoir Coupling option has been declared active by the GRUPMAST and SLAVES keywords in the SCHEDULE section.","parameters":[{"index":1,"name":"SLAVE_RESERVOIR","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"SLAVE_ECLBASE","description":"","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"HOST_NAME","description":"","units":{},"default":"","value_type":"STRING"},{"index":4,"name":"DIRECTORY","description":"","units":{},"default":"","value_type":"STRING"},{"index":5,"name":"NUM_PE","description":"","units":{},"default":"1","value_type":"INT"}],"example":"","expected_columns":5,"size_kind":"list"},"SOURCE":{"name":"SOURCE","sections":["SCHEDULE"],"supported":false,"summary":"The SOURCE keyword defines a mass and heat source term for a given pseudo component in the specified grid block.","parameters":[{"index":1,"name":"I","description":"A positive integer greater than zero and less than or equal to NX that defines the location of the source term in the I-direction.","units":{},"default":"None","value_type":"INT"},{"index":2,"name":"J","description":"A positive integer greater than zero and less than or equal to NY that defines the location of the source term in the J-direction.","units":{},"default":"None","value_type":"INT"},{"index":3,"name":"K","description":"A positive integer greater than zero and less than or equal to NZ that defines the location of the source term in the K-direction.","units":{},"default":"None","value_type":"INT"},{"index":4,"name":"COMP","description":"A defined character string that defines the pseudo component to be injected by the source term, COMP should be set to one of the following character strings: OIL: the source term will inject oil. GAS: the source term will inject gas. WATER: the source term will inject water. SOLVENT: the source term will inject solvent. POLYMER: the source term will inject polymer. MICR: the source term will inject microbes. OXYG: the source term will inject oxygen. UREA: the source term will inject urea. NONE: no pseudo component specified. The SOLVENT or POLYMER option should only be specified if the solvent or polymer model has been activated by the SOLVENT or POLYMER keyword respectively in the RUNSPEC section. MICR, OXYG, or UREA requires the MICP keyword. A pseudo component must be specified if the mass injection rate is non-zero.","units":{},"default":"NONE","value_type":"STRING","options":["OIL","GAS","WATER","SOLVENT","POLYMER","MICR","OXYG","UREA","NONE"]},{"index":5,"name":"RATE","description":"A real value that defines the source term’s mass injection rate of the specified component COMP.","units":{"field":"lb/day","metric":"kg/day","laboratory":"gm/hour"},"default":"0.0","value_type":"DOUBLE","dimension":"Mass/Time"},{"index":6,"name":"HRATE","description":"A real value that defines the source term’s heat injection rate1. The heat injection rate should only be specified if the thermal model has been activated by the THERMAL keyword in the RUNSPEC section.","units":{"field":"Btu/day","metric":"kJ/day","laboratory":"J/hour"},"default":"0.0","value_type":"DOUBLE","dimension":"Energy/Time"},{"index":7,"name":"TEMP","description":"A real value that defines the temperature of the injected component1. The temperature of the source term should only be specified if the thermal model has been activated by the THERMAL keyword in the RUNSPEC section.","units":{"field":"°F","metric":"°C","laboratory":"°C"},"default":"None","value_type":"DOUBLE","dimension":"Temperature"}],"example":"The first example adds two source terms to block (I=2, J=4, K=6) that inject gas at a mass flow rate of 25,000 lb/day and inject water at a mass flow rate of 1,000 lb/day respectively.\n--\n-- DEFINE SOURCE TERM\n--\n-- I J K COMP MASS HEAT TEMP\n-- -------------- RATE RATE\nSOURCE\n2 4 6 GAS 25000 1* 1* /\n2 4 6 WATER 1000 1* 1* /\n/\nThe second example adds a source term to block (I=2, J=4, K=6) that injects gas at a mass flow rate of 25,000 lb/day and a heat injection rate of 1.25 × 106 Btu/day in a thermal black-oil simulation.\n--\n-- DEFINE SOURCE TERM\n--\n-- I J K COMP MASS HEAT TEMP\n-- -------------- RATE RATE\nSOURCE\n2 4 6 GAS 25000 1.25E6 1* /\n/\nThe third example adds a source term to block (I=2, J=4, K=6) that injects gas at a mass flow rate of 25,000 lb/day and a temperature of 200°F in a thermal black-oil simulation.\n--\n-- DEFINE SOURCE TERM\n--\n-- I J K COMP MASS HEAT TEMP\n-- -------------- RATE RATE\nSOURCE\n2 4 6 GAS 25000 1* 200 /\n/","expected_columns":7,"size_kind":"list"},"SWINGFAC":{"name":"SWINGFAC","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, SWINGFAC, defines the gas contract parameters, swing factor and the monthly seasonal profile factor, for when there is a single gas contract being used in the model. The keyword is used with the Gas Field Operations option which is activated by the GASFIELD keyword in the RUNSPEC section. Gas contracts are commonly based on a Daily Contract Quantity (“DCQ”) that determines the gas rate that the field should be produced at, which is normally expressed as a multiple of the DCQ, for example 1.33, and is often referred to as the “swing factor”. Some gas contracts also define a maximum DCQ (“Max DCQ”) and/or a minimum take or pay DCQ (“Min DCQ”), as well as seasonal demand characteristics. For example, gas rates may be set higher in the winter months in order to meet heating demand compared with summer months in colder climates, and the opposite in warmer climates where air conditioning demand is high.","parameters":[{"index":1,"name":"SWING_FACTOR1","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":2,"name":"SWING_FACTOR2","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":3,"name":"SWING_FACTOR3","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":4,"name":"SWING_FACTOR4","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":5,"name":"SWING_FACTOR5","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":6,"name":"SWING_FACTOR6","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":7,"name":"SWING_FACTOR7","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":8,"name":"SWING_FACTOR8","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":9,"name":"SWING_FACTOR9","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":10,"name":"SWING_FACTOR10","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":11,"name":"SWING_FACTOR11","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":12,"name":"SWING_FACTOR12","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":13,"name":"PROFILE_FACTOR1","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":14,"name":"PROFILE_FACTOR2","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":15,"name":"PROFILE_FACTOR3","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":16,"name":"PROFILE_FACTOR4","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":17,"name":"PROFILE_FACTOR5","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":18,"name":"PROFILE_FACTOR6","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":19,"name":"PROFILE_FACTOR7","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":20,"name":"PROFILE_FACTOR8","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":21,"name":"PROFILE_FACTOR9","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":22,"name":"PROFILE_FACTOR10","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":23,"name":"PROFILE_FACTOR11","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":24,"name":"PROFILE_FACTOR12","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"| [Q sub{month}`=` DCQ times SWINGFAC sub{ month }] | (12.32) |\n|---------------------------------------------------|---------|","expected_columns":24,"size_kind":"fixed","size_count":1},"TIGHTEN":{"name":"TIGHTEN","sections":["SCHEDULE"],"supported":false,"summary":"The TIGHTEN keyword tightens up or slackens the numerical controls for the linear, non-linear and material balance convergence targets and also tightens or relaxes the maximum values for the aforementioned parameters. The keyword should be used with caution as it may result in significantly increasing the run times.","parameters":[{"index":1,"name":"FACTOR","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","expected_columns":1,"size_kind":"list"},"TIGHTENP":{"name":"TIGHTENP","sections":["SCHEDULE"],"supported":false,"summary":"The TIGHTENP keyword is similar to the TIGHTEN keyword in the SCHEDULE section, in that it tightens up or slackens the numerical controls for the linear, non-linear and material balance convergence targets and also tightens or relaxes the maximum values for the aforementioned parameters. However, TIGHTENP allows for greater flexibility as there are four parameters on this keyword, as opposed to just one on the TIGHTEN keyword, that can be used to modify the numerical controls. The keyword should be used with caution as it may result in significantly increasing the run times.","parameters":[{"index":1,"name":"LINEAR_FACTOR","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":2,"name":"MAX_LINEAR","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"NONLINEAR_FACTOR","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":4,"name":"MAX_NONLINEAR","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":4,"size_kind":"fixed","size_count":1},"TIME":{"name":"TIME","sections":["SCHEDULE"],"supported":false,"summary":"This keyword advances the simulation to a given cumulative report time after which additional keywords may be entered to instruct OPM Flow to perform additional functions via the SCHEDULE section keywords, or further TIME keywords may be entered to advance the simulator to the next report time.","parameters":[{"index":1,"name":"TIME","description":"A vector of real positive numbers that define the cumulative length of the of report times.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"None","value_type":"DOUBLE","dimension":"Time"}],"example":"The fist example shows how to advance the simulation three years using the TIME keyword, from the given start date of January 1, 2022 set via the START keyword in the RUNSPEC section.\n-- ==============================================================================\n--\n-- SCHEDULE SECTION\n--\n-- ==============================================================================\nSCHEDULE\n-- ------------------------------------------------------------------------------\n-- SCHEDULE SECTION - 2022-01-01\n-- ------------------------------------------------------------------------------\n--\n-- ADVANCE SIMULATION BY REPORTING TIME\n--\nTIME\n365.25 730.50 1095.75\n/\nThe second example shows the same advance but using the TSTEP keyword instead.\n Atgeirr Rasmussen\n 2017-09-22T12:22:06.652621000\n AFR\n Again, 2020 has 366 days.\n \n David Baxendale\n 2017-10-02T19:01:11.673000000\n DBx\n Reply to Atgeirr Rasmussen (09/22/2017, 12:22): \"...\"\n I changed the year to simplify the example.\nAgain, 2020 has 366 days.\nReply to Atgeirr Rasmussen (09/22/2017, 12:22): \"...\"\nI changed the year to simplify the example.\n-- ==============================================================================\n--\n-- SCHEDULE SECTION\n--\n-- ==============================================================================\nSCHEDULE\n-- ------------------------------------------------------------------------------\n-- SCHEDULE SECTION - 2022-01-01\n-- ------------------------------------------------------------------------------\nRPTSCHED\n'WELLS=2' 'WELSPECS' 'CPU=2' FIP=2' /\n--\n-- ADVANCE SIMULATION BY REPORTING TIME\n--\nTSTEP\n3*365.25\n/\nAgain, if the simulated production targets are actual production data or the results are going to be used in economic evaluations then the DATES keyword may be more useful in advancing the simulation via the reporting time steps, as the exact dates will be honored.","size_kind":"fixed","size_count":1,"variadic_record":true},"TSTEP":{"name":"TSTEP","sections":["SCHEDULE"],"supported":null,"summary":"This keyword advances the simulation to a given report time after which additional keywords may be entered to instruct OPM Flow to perform additional functions via the SCHEDULE section keywords, or further TSTEP keywords may be entered to advance the simulator to the next report time.","parameters":[{"index":1,"name":"TSTEP","description":"A vector of real positive numbers that define the length of the time intervals to subsequent report steps. Repeat counts may be used, for example 10*365.25.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"None","value_type":"DOUBLE","dimension":"Timestep"}],"example":"The first example shows how to advance the simulation via the reporting time steps from the given start date of January 1, 2022 set via the START keyword in the RUNSPEC section, to the next year, without any actions or reporting taking place.\n-- ==============================================================================\n--\n-- SCHEDULE SECTION\n--\n-- ==============================================================================\nSCHEDULE\n-- ------------------------------------------------------------------------------\n-- SCHEDULE SECTION - 2022-01-01\n-- ------------------------------------------------------------------------------\n--\n-- ADVANCE SIMULATION BY REPORTING TIME\n--\n-- JAN FEB MAR APR MAY JUN JLY AUG SEP OCT NOV DEC\nTSTEP\n31 28 31 30 31 30 31 31 30 31 30 31\n/\nThe second example is similar to the previous example but with quarterly reporting time steps used instead based on [365.25 over 4 = 91.3125]days per quarterdays per quarter\n-- ==============================================================================\n--\n-- SCHEDULE SECTION\n--\n-- ==============================================================================\nSCHEDULE\n-- ------------------------------------------------------------------------------\n-- SCHEDULE SECTION - 2022-01-01\n-- ------------------------------------------------------------------------------\nRPTSCHED\n'WELLS=2' 'WELSPECS' 'CPU=2' FIP=2' /\n--\n-- ADVANCE SIMULATION BY REPORTING TIME\n--\n-- QUARTERLY\nTSTEP\n4*91.3125\n/\nAgain, if the simulated production targets are actual production data or the results are going to be used in economic evaluations then the DATES keyword may be more useful in advancing the simulation via the reporting time steps, as the exact dates will be honored.","size_kind":"fixed","size_count":1,"variadic_record":true},"TUNING":{"name":"TUNING","sections":["SCHEDULE"],"supported":null,"summary":"The TUNING keyword defines the parameters used to control the commercial simulator’s time stepping and numerical convergence for the global grid. The keyword is similar to the TUNINGDP keyword in the SCHEDULE section that is optimized for high throughput runs. The keyword is mostly ignored by OPM Flow; however, the simulator can be instructed to read some parameters from the TUNING keyword if the appropriate command line parameter has been activated (see section 2.2Running OPM Flow 2023-04 From The Command Line).","parameters":[{"index":1,"name":"TSINIT","description":"TSINIT is a positive real value that defines the maximum length of the next time step. Note that whenever the keyword is used TSINIT is always set back to the default value of one, unless explicitly over written.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"1.0","record":1,"value_type":"DOUBLE","dimension":"Time"},{"index":2,"name":"TSMAXZ","description":"TSMAXZ is a positive real value that defines the maximum length of time steps following the next time step (TSINIT).","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"365.0","record":1,"value_type":"DOUBLE","dimension":"Time"},{"index":3,"name":"TSMINZ","description":"TSMINZ is a positive real value that defines the minimum length of all time steps.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"0.1","record":1,"value_type":"DOUBLE","dimension":"Time"},{"index":4,"name":"TSMCHP","description":"TSMCHP is a positive real value that sets the minimum time step length that can be chopped.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"0.15","record":1,"value_type":"DOUBLE","dimension":"Time"},{"index":5,"name":"TSFMAX","description":"TSFMAX is a positive real value that specifies the maximum growth rate a time step can be increased by, subject to the maximum allowable time step size set by TSMAXZ. For example, if the current time step has converged at 10 days and TSFMAX is set to the default value, then the next time step will be 3.0 x 10 days, that is 30 days provided it is less than TSMAXZ.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"3.0","record":1,"value_type":"DOUBLE"},{"index":6,"name":"TSFMIN","description":"TSFMIN is a positive real value that specifies the minimum decay rate a time step can be decreased by, subject to the minimum allowable time step size set by TSMINZ. For example, if the current time step has not converged at 10 days and TSFMIN is set to the default value, then the next time step will be 0.3 x 10 days, that is the maximum of 3 days and TSMINZ.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.3","record":1,"value_type":"DOUBLE"},{"index":7,"name":"TSFCNV","description":"TSFCNV is a positive real value that specifies the decay rate a time step can be decreased by after a convergence failure.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.1","record":1,"value_type":"DOUBLE"},{"index":8,"name":"TFDIFF","description":"TFDIFF is a positive real value that sets the time step growth factor of the time step after a convergence failure. For example, if the chopped current convergent time step is 10 days and TFDIFF is set to the default value, then the time step will be increased to 1.25 x 10 days, that is the minimum of 12.5 days and TSMAXZ.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.25","record":1,"value_type":"DOUBLE"},{"index":9,"name":"THRUPT","description":"THRURT is a positive real value that specifies the maximum throughput ratio over a time step.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0 x 1020","record":1,"value_type":"DOUBLE"},{"index":10,"name":"TMAXWC","description":"TMAXWC is a positive real value that defines maximum allowed time step after a well event; for example, when a well is opened or closed, etc.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"None","record":1,"value_type":"DOUBLE","dimension":"Time"},{"index":1,"name":"TRGTTE","description":"TRGTTE is a positive real value that sets the target time truncation error.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.1","record":2,"value_type":"DOUBLE"},{"index":2,"name":"TRGCNV","description":"TRGCNV is a positive real value that defines the target non-linear convergence error.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.001","record":2,"value_type":"DOUBLE"},{"index":3,"name":"TRGMBE","description":"TRGMBE is a positive real value that specifies the target material balance error.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0 x 10-7","record":2,"value_type":"DOUBLE"},{"index":4,"name":"TRGLCV","description":"TRGLCV is a positive real value that specifies the target linear convergence error.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.0001","record":2,"value_type":"DOUBLE"},{"index":5,"name":"XXXTTE","description":"XXXTTE is a positive real value that sets the maximum time truncation error.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"10.0","record":2,"value_type":"DOUBLE"},{"index":6,"name":"XXXCNV","description":"XXXCNV is a positive real value that defines the maximum non-linear convergence error.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.01","record":2,"value_type":"DOUBLE"},{"index":7,"name":"XXXMBE","description":"XXXMBE is a positive real value that specifies the maximum mass balance error, that is the tolerated mass balance error relative to total mass present.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0 x 10-6","record":2,"value_type":"DOUBLE"},{"index":8,"name":"XXXLCV","description":"XXXLCV is a positive real values that sets the maximum linear convergence error.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.0001","record":2,"value_type":"DOUBLE"},{"index":9,"name":"XXXWFL","description":"XXXWFL is a positive real values that fixes the maximum well flow convergence error.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.001","record":2,"value_type":"DOUBLE"},{"index":10,"name":"TRGFIP","description":"TRGFIP is a positive real value that stipulates the target fluid in-place error in Local Grid Refinements.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.025","record":2,"value_type":"DOUBLE"},{"index":11,"name":"TRGSFT","description":"TRGSFT is a positive real values that defines the target surfactant change when the Surfactant Model is active in the run.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","record":2,"value_type":"DOUBLE"},{"index":12,"name":"THIONX","description":"THIONX is a positive real value used to set the threshold for damping in the ion echange calculation for when the Brine Model is active in the run.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.01","record":2,"value_type":"DOUBLE"},{"index":13,"name":"TRWGHT","description":"TRWGHT is an integer that stipulates the implicitness for active tracer updates within the Newton iterations, and should be set to: The calculation is explicit, that is fully decoupled. The calculation is implicit, that is fully coupled.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1","record":2,"value_type":"INT"},{"index":1,"name":"NEWTMX","description":"NEWTMX is a positive integer greater or equal to NEWTMN that stipulates the maximum number of Newton iterations for a time step.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"12","record":3,"value_type":"INT"},{"index":2,"name":"NEWTMN","description":"NEWTMN is a positive integer that is less or equal to NEWTMX that defines the minimum number of Newton iterations for a time step.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1","record":3,"value_type":"INT"},{"index":3,"name":"LITMAX","description":"LITMAX is a positive integer greater or equal to LITMIN that sets the maximum number of linear iterations within a Newton iteration.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"25","record":3,"value_type":"INT"},{"index":4,"name":"LITMIN","description":"LITMIN is a positive integer less or equal to LITMAX that sets the minimum number of linear iterations within a Newton iteration.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1","record":3,"value_type":"INT"},{"index":5,"name":"MXWSIT","description":"MXWSIT is a positive integer that defines the maximum number of iterations within a well flow calculation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"8","record":3,"value_type":"INT"},{"index":6,"name":"MXWPIT","description":"MXWPIT is a positive integer that stipulates the maximum number of iterations for solving the bottom-hole pressure for wells under tubing head pressure control within a well flow calculation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"8","record":3,"value_type":"INT"},{"index":7,"name":"DDPLIM","description":"DDPLIM is a positive real value that stipulates the maximum pressure change at the last Newton iteration.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1.0 x 106","record":3,"value_type":"DOUBLE","dimension":"Pressure"},{"index":8,"name":"DDSLIM","description":"DDSLIM is a positive real value that sets the maximum saturation change at the last Newton iteration.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0 x 106","record":3,"value_type":"DOUBLE"},{"index":9,"name":"TRGDPR","description":"TRGDPR is a positive real value that defines the target maximum pressure change within a time step.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1.0 x 106","record":3,"value_type":"DOUBLE","dimension":"Pressure"},{"index":10,"name":"XXXDPR","description":"XXXDPR is a positive real value that stipulates the maximum tolerable pressure change within a time step.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","record":3,"value_type":"DOUBLE","dimension":"Pressure"},{"index":11,"name":"MNWRFP","description":"MNWRFP is a positive integer greater than one and less than NEWTMX that defines the minimum number of Newton iterations before invoking the bisection algorithm for when the polymer phase is active in the model via the POLYMER keyword in the RUNSPEC section.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"4","record":3,"value_type":"INT"}],"example":"--\n-- DEFAULT TUNING PARAMETERS\n--\nTUNING\n1.0 365.0 0.1 0.15 3 0.3 0.1 1.25 1E20 1* /\n/\n/\nThe above example explicitly sets the default parameters for OPM Flow for when the appropriate command line parameter has been activated (see section 2.2Running OPM Flow 2023-04 From The Command Line) to instruct the simulator to read the first record of the TUNING keyword.Alternatively one could just use the following to accomplish the same thing.\nTUNING\n/\n/\n/","records_meta":[{"expected_columns":10},{"expected_columns":13},{"expected_columns":11}],"size_kind":"fixed","size_count":3},"TUNINGDP":{"name":"TUNINGDP","sections":["SCHEDULE"],"supported":false,"summary":"The TUNINGDP keyword defines the parameters used for controlling the commercial simulator’s numerical convergence parameters. This keyword is similar to the TUNING keyword in the SCHEDULE section, but the defaults on this keyword are optimized for high throughput runs.","parameters":[{"index":1,"name":"TRGLCV","description":"TRGLCV is a positive real value that specifies the linear convergence error target. The default value is ten times lower than the default value on the TUNING keyword.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.00001","value_type":"DOUBLE"},{"index":2,"name":"XXXLCV","description":"XXXLCV is a positive real values that sets the maximum linear convergence error. The default value is ten times lower than the default value on the TUNING keyword.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.0001","value_type":"DOUBLE"},{"index":3,"name":"TRGDDP","description":"TRGDDP a positive real value that stipulates the maximum pressure change during a Newton iteration that enables the solution to be accepted when the residual pressure is still outside its convergence criteria.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1.0","value_type":"DOUBLE","dimension":"Pressure"},{"index":4,"name":"TRGDDS","description":"TRGDDS a positive real value that sets the maximum saturation change during a Newton iteration that enables the solution to be accepted when the residual saturation is still outside its convergence criteria.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.01","value_type":"DOUBLE"},{"index":5,"name":"TRGDDRS","description":"TRGDDRS a positive real value that sets the maximum gas dissolution factor change during a Newton iteration that enables the solution to be accepted when the residual gas dissolution factor is still outside its convergence criteria. This is an OPM Flow specific item that is not supported by the commercial simulator.","units":{"field":"Mscf/stb","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"0.0","value_type":"DOUBLE","dimension":"GasDissolutionFactor"},{"index":6,"name":"TRGDDRV","description":"TRGDDRV a positive real value that sets the maximum oil dissolution factor change during a Newton iteration that enables the solution to be accepted when the residual oil dissolution factor change is still outside its convergence criteria. This is an OPM Flow specific item that is not supported by the commercial simulator.","units":{"field":"stb/Mscf","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"0.0","value_type":"DOUBLE","dimension":"OilDissolutionFactor"}],"example":"--\n-- DEFAULT TUNINGDP PARAMETERS\n--\nTUNINGDP\n/\nThe above example explicitly sets the default parameters.","expected_columns":6,"size_kind":"fixed","size_count":1},"TUNINGH":{"name":"TUNINGH","sections":["SCHEDULE"],"supported":false,"summary":"Defines the parameters used for controlling the commercial simulator’s numerical convergence parameters. The keyword is similar to the TUNING keyword in the SCHEDULE section, but the defaults on this keyword are optimized for high throughput runs. See section 2.2Running OPM Flow 2023-04 From The Command Lineon how to invoke various numerical schemes via the OPM Flow command line interface.","parameters":[{"index":1,"name":"GRGLCV","description":"GRGLCV is a real positive value that specifies the linear convergence error target.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.0001","value_type":"DOUBLE"},{"index":2,"name":"GXXLCV","description":"GXXLCV is a real positive values that sets the maximum linear convergence error.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.001","value_type":"DOUBLE"},{"index":3,"name":"GMSLCV","description":"GMSLCV is a real positive value that specifies the linear convergence residual reduction.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0 x 10-20","value_type":"DOUBLE"},{"index":4,"name":"LGTMIN","description":"LGTMIN is a positive integer less or equal to LGTMAX that sets the minimum number of linear iterations within a Newton iteration.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1","value_type":"INT"},{"index":5,"name":"LGTMAX","description":"LGTMAX is a positive integer greater or equal to LGTMIN that sets the maximum number of linear iterations within a Newton iteration.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"25","value_type":"INT"}],"example":"--\n-- DEFAULT TUNINGH PARAMETERS\n--\nTUNINGH\n/\nThe above example explicitly sets the default parameters.","expected_columns":5,"size_kind":"fixed","size_count":1},"TUNINGL":{"name":"TUNINGL","sections":["SCHEDULE"],"supported":false,"summary":"TUNINGL defines the parameters used for controlling the commercial simulator’s numerical convergence parameters for all Local Grid Refinements (\"LGR\"). The keyword is the same as the TUNING keyword in the SCHEDULE section that applies the tuning parameters to the global grid. See section 2.2Running OPM Flow 2023-04 From The Command Lineon how to invoke various numerical schemes via the OPM Flow command line interface.","parameters":[{"index":1,"name":"TSINIT","description":"TSINT is a real positive value that defines the maximum length of the next time step. Note that whenever the keyword is used TSINIT is always set back to the default value of one, unless explicitly over written.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"1.0","record":1,"value_type":"DOUBLE","dimension":"Time"},{"index":2,"name":"TSMAXZ","description":"TSMAXZ is a real positive value that defines the maximum length of the next time step following TSINIT.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"365.0","record":1,"value_type":"DOUBLE","dimension":"Time"},{"index":3,"name":"TSMINZ","description":"TSMINZ is a real positive value that defines the minimum length of all time steps.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"0.1","record":1,"value_type":"DOUBLE","dimension":"Time"},{"index":4,"name":"TSMCHP","description":"TSMCHP is a real positive values that sets the minimum length of all chopped time steps.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"0.15","record":1,"value_type":"DOUBLE","dimension":"Time"},{"index":5,"name":"TSFMAX","description":"TSFMAX is a real positive value that specifies the maximum growth rate a time step can be increased by, subject to the maximum allowable time step size set by TSMAXZ. For example, if the current time step has converged at 10 days and TSFMAX is set to the default value, then the next time step will be 3.0 x 10 days, that is 30 days provided it is less than TSMAXZ.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"3.0","record":1,"value_type":"DOUBLE"},{"index":6,"name":"TSFMIN","description":"TSFMIN is a real positive value that specifies the minimum decay rate a time step can be decreased by, subject to the minimum allowable time step size set by TSMINZ. For example, if the current time step has not converged at 10 days and TSFMAX is set to the default value, then the next time step will be 0.3 x 10 days, that is the maximum of 0.3 days and TSMINZ.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.3","record":1,"value_type":"DOUBLE"},{"index":7,"name":"TSFCNV","description":"TSFCNV real positive value that specifies the decay rate a time step can be decreased by after the number of target iterations has been exceeded.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.1","record":1,"value_type":"DOUBLE"},{"index":8,"name":"TFDIFF","description":"TFDIFFA is a real positive value that sets the time step growth factor of the time step after a convergence failure. For example, if the chopped current convergent time step is 10 days and TFDIFF is set to the default value, then the time step will be increased to 1.25 x 10 days, that is the minimum of 11.25 days and TSMAXZ.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.25","record":1,"value_type":"DOUBLE"},{"index":9,"name":"THRURPT","description":"THRURPT is a real positive value that specifies the maximum throughput ratio over a time step.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0 x 1020","record":1,"value_type":"DOUBLE"},{"index":10,"name":"TMAXWC","description":"TMAXWC is a real double precision value that defines maximum allowed time step after a well event; for example, when a well is opened or closed, etc.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"None","record":1,"value_type":"DOUBLE","dimension":"Time"},{"index":1,"name":"TRGTTE","description":"TRGTTE is a real positive value that sets the time truncation error target.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.1","record":2,"value_type":"DOUBLE"},{"index":2,"name":"TRGCNV","description":"TRGCNV a real positive value that defines the non-linear convergence error.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.001","record":2,"value_type":"DOUBLE"},{"index":3,"name":"TRGMBE","description":"TRGMBE is a real positive value that specifies then target material balance error.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0 x 10-7","record":2,"value_type":"DOUBLE"},{"index":4,"name":"TRGLCV","description":"TRGLCV is a real positive value that specifies the linear convergence error target.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.00001","record":2,"value_type":"DOUBLE"},{"index":5,"name":"XXXTTE","description":"XXXTTE is a real positive value that sets the maximum time truncation error.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"10.0","record":2,"value_type":"DOUBLE"},{"index":6,"name":"XXXCNV","description":"XXXCNV is a real positive value that defines the maximum non-linear convergence error.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.01","record":2,"value_type":"DOUBLE"},{"index":7,"name":"XXXMBE","description":"XXXMBE is a real positive value that specifies the maximum mass balance error, that is the tolerated mass balance error relative to total mass present.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0 x 10-6","record":2,"value_type":"DOUBLE"},{"index":8,"name":"XXXLCV","description":"XXXLCV is a real positive values that sets the maximum linear convergence error.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.0001","record":2,"value_type":"DOUBLE"},{"index":9,"name":"XXXWFL","description":"XXXWFL is a real positive values that fixes the maximum well flow convergence error.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.001","record":2,"value_type":"DOUBLE"},{"index":10,"name":"TRGFIP","description":"TRGFIP is a real positive value that stipulates the target fluid in-place error in Local Grid Refinements.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.025","record":2,"value_type":"DOUBLE"},{"index":11,"name":"TRGSFT","description":"TRGSFT is a real positive values that defines the target surfactant change when the Surfactant Model is active in the run.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","record":2,"value_type":"DOUBLE"},{"index":12,"name":"THIONX","description":"THIONX is a positive real value used to set the threshold for damping in the ion echange calculation for when the Brine Model is active in the run.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.01","record":2,"value_type":"DOUBLE"},{"index":13,"name":"TRWGHT","description":"TRWGHT is a positive integer that stipulates the implicitness for active tracer updates within the Newton iterations, and should be set to: The calculation is explicit, that is fully decoupled. The calculation is implicit, that is fully coupled.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1","record":2,"value_type":"INT"},{"index":1,"name":"NEWTMX","description":"NEWTMX is a positive integer greater or equal to NEWTMN that stipulates the maximum number of Newton iterations for a time step.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"12","record":3,"value_type":"INT"},{"index":2,"name":"NEWTMN","description":"NEWTMN is a positive integer that is less or equal to NEWTMX that defines the minimum number of Newton iterations for a time step.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1","record":3,"value_type":"INT"},{"index":3,"name":"LITMAX","description":"LITMAX is a positive integer greater or equal to LITMIN that sets the maximum number of linear iterations within a Newton iteration.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"25","record":3,"value_type":"INT"},{"index":4,"name":"LITMIN","description":"LITMIN is a positive integer less or equal to LITMAX that sets the minimum number of linear iterations within a Newton iteration.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1","record":3,"value_type":"INT"},{"index":5,"name":"MXWSIT","description":"MXWSIT is a positive integer that defines the maximum number of iterations within a well flow calculation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"8","record":3,"value_type":"INT"},{"index":6,"name":"MXWPIT","description":"MXWPIT is a positive integer that stipulates the maximum number of iterations for solving the bottom-hole pressure for wells under tubing head pressure control within a well flow calculation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"8","record":3,"value_type":"INT"},{"index":7,"name":"DDPLIM","description":"DDPLIM a real positive value that stipulates the maximum pressure change at the last Newton iteration.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1.0 x 10-6","record":3,"value_type":"DOUBLE","dimension":"Pressure"},{"index":8,"name":"DDSLIM","description":"DDSLIM a real positive value that sets the maximum saturation change at the last Newton iteration.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0 x 10-6","record":3,"value_type":"DOUBLE"},{"index":9,"name":"TRGDPR","description":"TRGDP is a real positive value that defines the target pressure change within a time step.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1.0 x 10-6","record":3,"value_type":"DOUBLE","dimension":"Pressure"},{"index":10,"name":"XXXDPR","description":"XXXDPR is a real positive value that stipulates the maximum tolerable pressure change within a time step.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1.0 x 10-6","record":3,"value_type":"DOUBLE","dimension":"Pressure"},{"index":11,"name":"MNWRFP","description":"MNWRFP is a positive integer greater than one and less than NEWTMX that defines the minimum number of Newton iterations before invoking the bisection algorithm for when the polymer phase is active in the model via the POLYMER keyword in the RUNSPEC section.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"4","record":3,"value_type":"INT"}],"example":"-\n-- DEFAULT TUNINGL PARAMETERS\n--\nTUNINGL\n/\n/\n/\nThe above example explicitly sets the default parameters for all LGRs.","records_meta":[{"expected_columns":10},{"expected_columns":13},{"expected_columns":11}],"size_kind":"fixed","size_count":3},"TUNINGS":{"name":"TUNINGS","sections":["SCHEDULE"],"supported":false,"summary":"TUNINGS defines the parameters used for controlling the commercial simulator’s numerical convergence parameters for individual Local Grid Refinements (\"LGR\"). The keyword is similar to the TUNINGL keyword in the SCHEDULE section that applies the tuning parameters to the all LGRs, except for an additional first record that includes the LGR name.","parameters":[{"index":1,"name":"LGRNAME","description":"A character string of up to eight characters in length that defines the LGR name for which the tuning data is being being defined.","units":{},"default":"None","record":1,"value_type":"STRING"},{"index":1,"name":"TSINIT","description":"TSINT is a real positive value that defines the maximum length of the next time step. Note that whenever the keyword is used TSINIT is always set back to the default value of one, unless explicitly over written.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"1.0","record":2,"value_type":"DOUBLE","dimension":"Time"},{"index":2,"name":"TSMAXZ","description":"TSMAXZ is a real positive value that defines the maximum length of the next time step following TSINIT.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"365.0","record":2,"value_type":"DOUBLE","dimension":"Time"},{"index":3,"name":"TSMINZ","description":"TSMINZ is a real positive value that defines the minimum length of all time steps.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"0.1","record":2,"value_type":"DOUBLE","dimension":"Time"},{"index":4,"name":"TSMCHP","description":"TSMCHP is a real positive values that sets the minimum length of all chopped time steps.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"0.15","record":2,"value_type":"DOUBLE","dimension":"Time"},{"index":5,"name":"TSFMAX","description":"TSFMAX is a real positive value that specifies the maximum growth rate a time step can be increased by, subject to the maximum allowable time step size set by TSMAXZ. For example, if the current time step has converged at 10 days and TSFMAX is set to the default value, then the next time step will be 3.0 x 10 days, that is 30 days provided it is less than TSMAXZ.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"3.0","record":2,"value_type":"DOUBLE"},{"index":6,"name":"TSFMIN","description":"TSFMIN is a real positive value that specifies the minimum decay rate a time step can be decreased by, subject to the minimum allowable time step size set by TSMINZ. For example, if the current time step has not converged at 10 days and TSFMAX is set to the default value, then the next time step will be 0.3 x 10 days, that is the maximum of 0.3 days and TSMINZ.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.3","record":2,"value_type":"DOUBLE"},{"index":7,"name":"TSFCNV","description":"TSFCNV real positive value that specifies the decay rate a time step can be decreased by after the number of target iterations has been exceeded.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.1","record":2,"value_type":"DOUBLE"},{"index":8,"name":"TFDIFF","description":"TFDIFFA is a real positive value that sets the time step growth factor of the time step after a convergence failure. For example, if the chopped current convergent time step is 10 days and TFDIFF is set to the default value, then the time step will be increased to 1.25 x 10 days, that is the minimum of 11.25 days and TSMAXZ.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.25","record":2,"value_type":"DOUBLE"},{"index":9,"name":"THRURPT","description":"THRURPT is a real positive value that specifies the maximum throughput ratio over a time step.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0 x 1020","record":2,"value_type":"DOUBLE"},{"index":10,"name":"TMAXWC","description":"TMAXWC is a real double precision value that defines maximum allowed time step after a well event; for example, when a well is opened or closed, etc.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"None","record":2,"value_type":"DOUBLE","dimension":"Time"},{"index":1,"name":"TRGTTE","description":"TRGTTE is a real positive value that sets the time truncation error target.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.1","record":3,"value_type":"DOUBLE"},{"index":2,"name":"TRGCNV","description":"TRGCNV a real positive value that defines the non-linear convergence error.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.001","record":3,"value_type":"DOUBLE"},{"index":3,"name":"TRGMBE","description":"TRGMBE is a real positive value that specifies then target material balance error.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0 x 10-7","record":3,"value_type":"DOUBLE"},{"index":4,"name":"TRGLCV","description":"TRGLCV is a real positive value that specifies the linear convergence error target.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.00001","record":3,"value_type":"DOUBLE"},{"index":5,"name":"XXXTTE","description":"XXXTTE is a real positive value that sets the maximum time truncation error.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"10.0","record":3,"value_type":"DOUBLE"},{"index":6,"name":"XXXCNV","description":"XXXCNV is a real positive value that defines the maximum non-linear convergence error.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.01","record":3,"value_type":"DOUBLE"},{"index":7,"name":"XXXMBE","description":"XXXMBE is a real positive value that specifies the maximum mass balance error, that is the tolerated mass balance error relative to total mass present.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0 x 10-6","record":3,"value_type":"DOUBLE"},{"index":8,"name":"XXXLCV","description":"XXXLCV is a real positive values that sets the maximum linear convergence error.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.0001","record":3,"value_type":"DOUBLE"},{"index":9,"name":"XXXWFL","description":"XXXWFL is a real positive values that fixes the maximum well flow convergence error.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.001","record":3,"value_type":"DOUBLE"},{"index":10,"name":"TRGFIP","description":"TRGFIP is a real positive value that stipulates the target fluid in-place error in Local Grid Refinements.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.025","record":3,"value_type":"DOUBLE"},{"index":11,"name":"TRGSFT","description":"TRGSFT is a real positive values that defines the target surfactant change when the Surfactant Model is active in the run.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","record":3,"value_type":"DOUBLE"},{"index":12,"name":"THIONX","description":"THIONX is a positive real value used to set the threshold for damping in the ion echange calculation for when the Brine Model is active in the run.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.01","record":3,"value_type":"DOUBLE"},{"index":13,"name":"TRWGHT","description":"TRWGHT is a positive integer that stipulates the implicitness for active tracer updates within the Newton iterations, and should be set to: The calculation is explicit, that is fully decoupled. The calculation is implicit, that is fully coupled.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1","record":3,"value_type":"INT"},{"index":1,"name":"NEWTMX","description":"NEWTMX is a positive integer greater or equal to NEWTMN that stipulates the maximum number of Newton iterations for a time step.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"12","record":4,"value_type":"INT"},{"index":2,"name":"NEWTMN","description":"NEWTMN is a positive integer that is less or equal to NEWTMX that defines the minimum number of Newton iterations for a time step.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1","record":4,"value_type":"INT"},{"index":3,"name":"LITMAX","description":"LITMAX is a positive integer greater or equal to LITMIN that sets the maximum number of linear iterations within a Newton iteration.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"25","record":4,"value_type":"INT"},{"index":4,"name":"LITMIN","description":"LITMIN is a positive integer less or equal to LITMAX that sets the minimum number of linear iterations within a Newton iteration.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1","record":4,"value_type":"INT"},{"index":5,"name":"MXWSIT","description":"MXWSIT is a positive integer that defines the maximum number of iterations within a well flow calculation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"8","record":4,"value_type":"INT"},{"index":6,"name":"MXWPIT","description":"MXWPIT is a positive integer that stipulates the maximum number of iterations for solving the bottom-hole pressure for wells under tubing head pressure control within a well flow calculation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"8","record":4,"value_type":"INT"},{"index":7,"name":"DDPLIM","description":"DDPLIM a real positive value that stipulates the maximum pressure change at the last Newton iteration.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1.0 x 10-6","record":4,"value_type":"DOUBLE","dimension":"Pressure"},{"index":8,"name":"DDSLIM","description":"DDSLIM a real positive value that sets the maximum saturation change at the last Newton iteration.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0 x 10-6","record":4,"value_type":"DOUBLE"},{"index":9,"name":"TRGDPR","description":"TRGDP is a real positive value that defines the target pressure change within a time step.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1.0 x 10-6","record":4,"value_type":"DOUBLE","dimension":"Pressure"},{"index":10,"name":"XXXDPR","description":"XXXDPR is a real positive value that stipulates the maximum tolerable pressure change within a time step.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1.0 x 10-6","record":4,"value_type":"DOUBLE","dimension":"Pressure"},{"index":11,"name":"MNWRFP","description":"MNWRFP is a positive integer greater than one and less than NEWTMX that defines the minimum number of Newton iterations before invoking the bisection algorithm for when the polymer phase is active in the model via the POLYMER keyword in the RUNSPEC section.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"4","record":4,"value_type":"INT"}],"example":"--\n-- DEFAULT TUNINGS PARAMETERS\n--\nTUNINGS\nOP01-LGR\n/\n/\n/\nThe above example explicitly sets the default parameters for the LGR named OP01-LGR","records_meta":[{"expected_columns":1},{"expected_columns":10},{"expected_columns":13},{"expected_columns":11}],"size_kind":"fixed","size_count":4},"UDQ":{"name":"UDQ","sections":["SCHEDULE"],"supported":true,"summary":"This keyword starts the definition of a UDQ section that stipulates the variables and operations used to access the User Defined Quantities features in OPM Flow. UDQ variables can be constants, SUMMARY variables, as defined in the SUMMARY section,or a formula using various mathematical functions together with constants and SUMMARY variables. Available operations include the ASSIGN, DEFINE, UNITS and UPDATE commands that are sub-keywords to the UDQ section keyword.","parameters":[{"index":1,"name":"OPERATOR","description":"OPERATOR is a defined character string that specifies the type of operation to perform, and should be one of the following: ASSIGN: Assigns a constant numerical value to the UDQ defined by VARIABLE and sets the UPDATE status to OFF. DEFINE: Defines a mathematical formula and assigns it to the UDQ defined by VARIABLE. The UDQ is initialized with the formula and the UPDATE status is set to ON. UNITS: Sets the reporting units for the UDQ defined by VARIABLE. The units have no effect on the calculations. The UDQ must already have been defined prior to using this option. UPDATE: Stipulates when the UDQ defined by VARIABLE should be evaluated.","units":{},"default":"","value_type":"RAW_STRING"},{"index":2,"name":"VARIABLE","description":"VARIABLE is a character string of length eight that stipulates the name of the user defined variable that will processed by the OPERATOR command. The first two characters of VARIABLE must be set based on the type of variable being defined, that is: CU: For variables that are associated with connections, for example SUMMARY variable COFR (Connection Oil Flow Rate). FU: For variables that are associated with field data, for example SUMMARY variable FOPR (Field Oil Production Rate). GU: For variables that are associated with groups, for example SUMMARY variable GLPR (Group Liquid Production Rate). RU: For variables that are associated with regions, for example SUMMARY variable RPR (Region Pressure). SU: For variables that are associated with multi-segment wells, for example SUMMARY variable SOFR (Segment Oil Flow Rate). WU: For variables that are associated with wells, for example SUMMARY variable WWCT (Well Water Cut). AU: For variables that are associated with aquifers, for example SUMMARY variable AAQP (Analytical Aquifer Pressure). BU: For variables that are associated with blocks, for example SUMMARY variable BPR (Block oil phase Pressure). OPM Flow currently only supports field, group, segment and well variables (FU*, GU*, SU* and WU*).","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"EXPRESSION","description":"The data type for EXPRESSION is based on the OPERATOR option above, namely if OPERATOR is set to: ASSIGN:EXPRESSION should be a numerical value. DEFINE: EXPRESSION should be a mathematical expression. Allowable tokens for the expression include SUMMARY or UDQ variables, real numbers (can be integers or scientific notation), opening and closing brackets '(' and ')', and basic mathematical operators plus '+', minus '-', multiply '*', divide '/' and exponent '^'. UNITS: EXPRESSION should be a character string (enclosed in quotes if it contains blanks) with a maximum length of eight characters, that declares the units that will used when reporting the UDQ defined by VARIABLE. UPDATE: EXPRESSION should be a defined character string (ON, OFF or NEXT): ON to evaluate the UDQ defined by VARIABLE at all time steps, OFF to not evaluate the UDQ, or NEXT to evaluate the UDQ at the next time step.","units":{},"default":"","value_type":"RAW_STRING"}],"example":"The first example shows how to define some constant field variables used for calculating facilities corrected condensate and Liquefied Petroleum Gas315\n Liquefied Petroleum Gas or LPG consists mainly of propane, propylene, butane, and butylene in various mixtures. It is produced as a by-product of natural gas processing and petroleum refining. The components of LPG are gases at standard conditions. (“LPG “) yields in a wet gas model:\nLiquefied Petroleum Gas or LPG consists mainly of propane, propylene, butane, and butylene in various mixtures. It is produced as a by-product of natural gas processing and petroleum refining. The components of LPG are gases at standard conditions.\n--\n-- DEFINE START OF USER DEFINED QUANTITY SECTION\n--\nUDQ\n--\n-- OPERATOR VARIABLE EXPRESSION\n--\nASSIGN FUNGLYLD 1.100000 / -- Condensate Yield (stb/Mscf)\nASSIGN FUNGLSHK 0.000000 / Condensate Shrinkage Factor to Zero\nASSIGN FULPGYLD 0.065775 / -- LPG Sep Gas Yield (stb/Mscf)\nASSIGN FULPGSHK 0.080410 / LPG Shrinkage Factor\nASSIGN FUFACSHK 0.000935 / Facilities Shrinkage Factor\nASSIGN FUFULSHK 0.052924 / Fuel Utilization\nASSIGN FUDELTA 1E-10 / Value to avoid dividing by zero errors\n/ DEFINE END OF USER DEFINED QUANTITY SECTION\nThe next example is a continuation of this example by showing how one can calculate the adjusted field condensate and LPG rates. Note both examples could be merged into a single UDQ definition but have been stated separately for ease of reference.\n--\n-- DEFINE START OF USER DEFINED QUANTITY SECTION\n--\nUDQ\n--\n-- OPERATOR VARIABLE EXPRESSION\n--\nDEFINE FU_FNGLR FGPR * (FOGR * FUNGLYLD) / Calculate Condensate Rate Field\nUPDATE FU_FNGLR ON /\nUNITS FU_FNGLR STBD /\nDEFINE FU_FLPGR FU_FWGPR * FULPGYLD / Calculate LPG Rate Field\nUPDATE FU_FLPGR ON /\nUNITS FU_FLPGR STBD /\n/ DEFINE END OF USER DEFINED QUANTITY SECTION\nIn the above the DEFINE operator is use to define the equations to calculate the corrected condensate (FU_FNGLR) and LPG rates (FU_FLPGR) with the UPDATE operator set to ON so that the rates are calculate at every time step, and finally, the UNITS operator is used to set the units of the calculated rates.\nThe final example show the use of the UDADIMS and UDQDIMS keywords in the RUNSPEC section, followed by the keywords in the SCHEDULE section that define a UDQ definition that uses the DEFINE operator to calculate adjusted well rates based on an expression. The final set of keywords show how the UDQ defined variables are employed on the WCONPROD keyword to control the production constraints for several wells.\nRUNSPEC SECTION KEYWORDS\n------------------------\n--\n-- USER DEFINED ARGUMENT DIMENSIONS\n-- NO. NOT TOTAL\n-- ARGS USED UDQ\nUDADIMS\n10 1* 10 /\n--\n-- USER DEFINED ARGUMENT DIMENSIONS FACILITY\n-- MAX MAX MAX MAX MAX MAX MAX MAX MAX MAX RAND\n-- FUNCS ITEMS CONNS FIELD GROUP REGS SEGTM WELL AQUF BLCKS OPT\nUDQDIMS\n50 25 0 50 50 0 0 0 0 0 N /\nAnd the SCHEDULE section part of the example is shown below.\nSCHEDULE SECTION KEYWORDS\n--------------------------\n--\n-- DEFINE START OF USER DEFINED QUANTITY SECTION\n--\nUDQ\n--\n-- OPERATOR VARIABLE EXPRESSION\n--\nDEFINE WUOPRL (WOPR OPL01 - 150) * 0.90 / OIL & LIQ CAPACITIES\nDEFINE WULPRL (WLPR OPL01 - 200) * 0.90 / at GEFAC = 0.8995\nDEFINE WUOPRU (WOPR OPU01 - 250) * 0.80 /\nDEFINE WULPRU (WLPR OPU01 - 300) * 0.80 /\n--\nUNITS WUOPRL SM3/DAY / DEFINE REPORTING UNITS\nUNITS WULPRL SM3/DAY / FOR UDQ VARIABLES\nUNITS WUOPRU SM3/DAY /\nUNITS WULPRU SM3/DAY /\n/ DEFINE END OF USER DEFINED QUANTITY SECTION\n--\n-- WELL PRODUCTION WELL CONTROLS\n--\n-- WELL OPEN/ CNTL OIL WAT GAS LIQ RES BHP THP VFP VFP\n-- NAME SHUT MODE RATE RATE RATE RATE RATE PRES PRES TABLE ALFQ\nWCONPROD\nOP01 SHUT GRUP 1* 1* 1* 1* 1* 200.0 /\nOP02 SHUT GRUP 1* 1* 1* 1* 1* 200.0 /\n/\nDATES\n1 FEB 2020 /\n--\n-- WELL PRODUCTION WELL CONTROLS\n--\n-- WELL OPEN/ CNTL OIL WAT GAS LIQ RES BHP THP VFP VFP\n-- NAME SHUT MODE RATE RATE RATE RATE RATE PRES PRES TABLE ALFQ\nWCONPROD\nOP01 OPEN GRUP WUOPRL 1* 1* WULPRL 1* 60.0 /\nOP02 OPEN GRUP WUOPRL 1* 1*","size_kind":"list","variadic_record":true},"UDT":{"name":"UDT","sections":["SCHEDULE"],"supported":true,"summary":"The UDT keyword defines a single multi-dimensional User Defined Table (“UDT”).","parameters":[{"index":1,"name":"NAME","description":"A character string of up to eight characters in length beginning with ‘TU’ that defines the table name.","units":{},"default":"None","record":1},{"index":2,"name":"NDIMS","description":"An integer value between one and MXDIMS that defines the number of dimensions for the table. MXDIMS is the maximum number of UDT table dimensions defined using the UDTDIMS keyword in the RUNSPEC section. OPM Flow only supports one-dimensional tables (NDIMS = 1).","units":{},"default":"None","record":1},{"index":1,"name":"TYPE","description":"A defined character string that defines the type of interpolation for this dimension and must one of the following: ‘NV’ this dimension will use the nearest value. ‘LC’ this dimension will use linear interpolation within the table and clamp to the first or last value respectively for extrapolation. ‘LL’ this dimension will use linear interpolation within the table and linear extrapolation outside of the table. ‘ID’ this dimension will use a string or identifier to select the interpolation point. If no matching interpolation point is found then the lookup will return the value given to undefined UDQ variables as specifed by the DEFAULT value on the UDQPARAM keyword in the RUNSPEC section.","units":{},"default":"None","record":2},{"index":2,"name":"POINTS","description":"A monotonically increasing vector of real values that defines the numerical value of the interpolation points for this dimension if the specified type of interpolation TYPE is either ‘NV’, ‘LC’ or ‘LL’. Otherwise, a vector of character strings of up to eight characters in length defining the ‘ID’.","units":{},"default":"None","record":2},{"index":1,"name":"VALUES","description":"A vector of real values corresponding to each of the interpolations points POINTS in the first dimension.","units":{},"default":"None","record":3}],"example":"The following example shows a one-dimension User Defined Table that will linearly interpolate between values of 100 and 180 for values of FOPR between 100 and 500 and will clamp to the end points for values of FOPR outside this range.\n--\n-- DECLARE USER DEFINED TABLE\n--\nUDT\n-- NAME NDIMS\n'TU_FBHP' 1 /\n-- TYPE POINTS\n'LC' 100.0 500.0 / -- FOPR values\n-- VALUES\n100.0 180.0 / -- FBHP values\n/\n/\n--\n-- DECLARE USER DEFINED QUANTITIES\n--\nUDQ\nASSIGN FU_WBHP 0 /\nDEFINE FU_WBHP0 FU_WBHP /\nDEFINE FU_WBHP (TU_FBHP[FOPR] UMIN WBHP 'PROD') UMIN FU_WBHP0 /\n/\n--\n-- WELL PRODUCTION TARGETS AND CONSTRAINTS\n--\nWCONPROD\n'PROD' 'OPEN' ORAT 500.0 4* FU_WBHP /\n/\nIn the example above, the UDT specifies how the bottom hole pressure limit should reduce as the field oil production rate decreases (note the interpolation point values must be monotone increasing). The User Defined Quantity FU_WBHP uses a lookup value from the UDT in the form TU_BHP[FOPR].","size_kind":"none","size_count":0},"USECUPL":{"name":"USECUPL","sections":["SCHEDULE"],"supported":false,"summary":"The USECUPL keyword causes the simulator to read a Reservoir Coupling file that has been previously created in a master run using the DUMPCUPL keyword in the SCHEDULE section, for when reservoir coupling is invoked by the GRUPMAST and SLAVES keywords in the SCHEDULE section.","parameters":[{"index":1,"name":"BASE","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"FMT","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":2,"size_kind":"fixed","size_count":1},"VFPCHK":{"name":"VFPCHK","sections":["SCHEDULE"],"supported":false,"summary":"The VFPPROD keyword defines production Vertical Flow Performance (“VFP”) tables that are used to determine the outflow or downstream pressure based on the inlet or upstream pressure and the phases flowing through the system. For a well this means the table relates the flowing bottom-hole pressure (“BHP”) to the well’s tubing head pressure (“THP”) based on the oil, gas and water rates (and any artificial lift quantities like gas lift gas), or phases ratios, flowing up the wellbore.","parameters":[{"index":1,"name":"VFPCHK","description":"VFPCHK is a real positive value that defines the BHP pressure above which crossing VFP curves will be ignored. Setting VFPCHK to a large number like the default value number will cause all crossing curves to be checked. Also if the keyword is omitted from the input deck then the check is performed using the default value.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"1.010","value_type":"DOUBLE","dimension":"Pressure"}],"example":"Here the example sets the maximum BHP to be 1.0 x106 above which crossing VFP curves will be ignored.\n--\n-- DEFINE PRODUCTION VFP CHECK MAX BHP\n--\n-- MXBHP\nVFPCHK\n1.0E6\n/\n| Note One reason for external programs generating crossing VFP curves is that the curves have been generated with too much resolution. For example, if the GOR entries has been generated with values of 100, 150, 200, 250, 300, 350, 400, 450 and 500, then use a geometric spacing instead to generated the VFP table, that is: 100, 300, 900. This will enable the simulator to interpolate the curves consistently and avoid crossing VFP curves. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":1,"size_kind":"fixed","size_count":1},"VFPINJ":{"name":"VFPINJ","sections":["SCHEDULE"],"supported":null,"summary":"The VFPINJ keyword defines injection Vertical Flow Performance (“VFP”) tables that are used to determine the outflow or downstream pressure based on the inlet or upstream pressure and the phases being injected into the system. For an injection well this means the table relates the flowing bottom-hole pressure (“BHP”) to the well’s tubing head pressure (“THP”) based on the oil, gas or water injection rates. The table is also used to describe the pressure relationship when the network option is being used, although the Network option is not currently implemented in OPM Flow. In this case the table describes the pipeline pressure behavior from the HIGHER group (inlet node) to the LOWER group (outlet node) given the current flowing conditions (the group relationship is defined by the GRUPTREE keyword in SCHEDULE section).","parameters":[{"index":1,"name":"VFPTAB","description":"A positive integer greater than zero and less than or equal to the MXVFPTAB variable as defined on the VFPIDIMS keyword in the RUNSPEC section, that defines the vertical flow performance table number.","units":{},"default":"None","record":1,"value_type":"INT"},{"index":2,"name":"VFPREF","description":"A real positive value that defines the reference depth used to generate this VFPINJ table data set. OPM Flow automatically corrects any difference between VFPREF and the BHPREF on the WELSPECS and WPAVDEP keywords in the SCHEDULE section, using the current hydrostatic head.","units":{},"default":"None","record":1,"value_type":"DOUBLE","dimension":"Length"},{"index":3,"name":"FLO","description":"A defined character string that defines the injection phases, and should be set to one of the following character strings: OIL: for injecting phase being oil. GAS: for injecting phase being gas. WAT: for injecting phase being water.","units":{},"default":"None","record":1,"value_type":"STRING","options":["OIL","GAS","WAT"]},{"index":4,"name":"VFPTYPE","description":"A defined character string that should be defaulted or set equal to THP.","units":{},"default":"THP","record":1,"value_type":"STRING"},{"index":5,"name":"VFPUNITS","description":"A defined character string that specifies the units system for the VFP table. An error message is output if this is not the same as the model units.","units":{"field":"FIELD","metric":"METRIC","laboratory":"LAB"},"default":"Model units","record":1,"value_type":"STRING"},{"index":6,"name":"VFPVALUE","description":"A defined character string that defines the type of data in the VFP-DATA vector. This should be defaulted or set equal to BHP.","units":{},"default":"BHP","record":1,"value_type":"STRING"},{"index":1,"name":"FLO-DATA","description":"A real positive monotonically increasing vector that defines the numerical values of the injection phase declared by the FLO variable. The number of entries must greater than two and less than or equal to MXMFLO as defined on the VFPIDIMS keyword in the RUNSPEC section.","units":{"field":"Liquid: stb Gas: Mscf","metric":"Liquid: sm3 Gas: sm3","laboratory":"Liquid: scc Gas: scc"},"default":"None","record":2,"value_type":"DOUBLE"},{"index":1,"name":"THP-DATA","description":"A real positive monotonically increasing vector that defines the numerical values of the tubing head pressure values. The number of entries must be greater than two and less than or equal to MXMTHP as defined on the VFPIDIMS keyword in the RUNSPEC section.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","record":3,"value_type":"DOUBLE"},{"index":1,"name":"NTHP","description":"This data record consists of an integer value that defines the index of THP values entered via the THP-DATA records on this keyword. For example, if THP-DATA is equal to 1000, 2000, 3000 and 3500 and NTHP is equal to three then NTHP refers to third entry, that is THP equal to 3000.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"","record":4,"value_type":"INT"},{"index":2,"name":"VALUES","description":"","units":{},"default":"","value_type":"DOUBLE","record":4}],"example":"The following example shows the VFPINJ table for a water injection well and is taken from the Norne OPM Flow model.\nVFPINJ\n-- Table Datum Depth Rate Type\n-- ----- ----------- ---------\n12 2718.07 'WAT' /\n-- 'WAT' units - SM3/DAY\n500.0 1263.2 2026.3 2789.5 3552.6\n4315.8 5078.9 5842.1 6605.3 7368.4\n8131.6 8894.7 9657.9 10421.1 11184.2\n11947.4 12710.5 13473.7 14236.8 15000.0 /\n-- 'THP' units - BARSA\n21.01 63.24 105.46 147.68 189.90\n232.12 274.35 316.57 358.79 401.01 /\n1 254.51 253.95 252.27 249.83 246.69\n242.88 238.42 233.32 227.59 221.22\n214.23 206.62 198.38 189.53 180.06\n169.97 159.26 147.95 136.00 123.46\n/\n2 297.02 296.49 294.82 292.39 289.26\n285.47 281.01 275.92 270.20 263.84\n256.87 249.28 241.05 232.22 222.76\n212.70 202.01 190.71 178.79 166.27\n/\n……………………………………….………………………….……………………………………………………………………\n……………………………………….………………………….……………………………………………………………………\n9 594.67 594.29 592.70 590.34 587.29\n583.57 579.16 574.17 568.55 562.25\n555.40 547.92 539.79 531.09 521.74\n511.82 501.25 490.13 478.34 466.01\n/\n10 637.19 636.83 635.26 632.91 629.86\n626.16 621.76 616.78 611.17 604.89\n598.05 590.59 582.47 573.79 564.45\n554.56 544.01 532.91 521.14 508.83\n/\nThe example shows the first two and the last two records of the fourth kind, as the data is too voluminous to be included.\nNote\nThe VFPTAB variable defines the table number of the VFPINJ data set; if more then one VFPINJ keyword is entered with the same VFPTAB number then the VFPINJ data set will be overwritten by the last VFPINJ keyword with the same VFPTAB number.\nThe same comment is also applicable to the VFPPROD keyword.\n| Note The VFPTAB variable defines the table number of the VFPINJ data set; if more then one VFPINJ keyword is entered with the same VFPTAB number then the VFPINJ data set will be overwritten by the last VFPINJ keyword with the same VFPTAB number. The same comment is also applicable to the VFPPROD keyword. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","records_meta":[{"expected_columns":6},{},{},{}],"size_kind":"fixed","variadic_record":true,"size_count":4},"VFPPROD":{"name":"VFPPROD","sections":["SCHEDULE"],"supported":false,"summary":"The VFPPROD keyword defines production Vertical Flow Performance (“VFP”) tables that are used to determine the outflow or downstream pressure based on the inlet or upstream pressure and the phases flowing through the system. For a production well this means the table relates the flowing bottom-hole pressure (“BHP”) to the well’s tubing head pressure (“THP”) based on the oil, gas and water rates (and any artificial lift quantities (\"ALQ\") like gas lift gas), or phases ratios, flowing up the wellbore. The table is also used to describe the pressure relationship when the network option is being used. In this case the table describes the pipeline pressure behavior from the LOWER group (inlet node) to the HIGHER group (outlet node) given the current flowing conditions (the group relationship is defined by the GRUPTREE keyword in SCHEDULE section).","parameters":[{"index":1,"name":"VFPTAB","description":"A positive integer greater than zero and less than or equal to the MXVFPTAB variable as defined on the VFPPDIMS keyword in the RUNSPEC section, that defines the vertical lift performance table number.","units":{},"default":"None","record":1,"value_type":"INT"},{"index":2,"name":"VFPREF","description":"A real positive value that defines the reference depth used to generate this VFPPROD table data set. OPM Flow automatically corrects any difference between VFPREF and the BHPREF on the WELSPECS and WPAVEDEP keywords in the SCHEDULE section, using the current hydrostatic head.","units":{},"default":"None","record":1,"value_type":"DOUBLE","dimension":"Length"},{"index":3,"name":"FLO","description":"A defined character string that defines the flowing phases, and should be set to one of the following character strings: GAS: for flowing phase being the gas rate. OIL: for flowing phase being the oil rate. LIQ: for flowing phase being the liquid (oil plus water) rate.","units":{},"default":"None","record":1,"value_type":"STRING","options":["GAS","OIL","LIQ"]},{"index":4,"name":"WFR","description":"A defined character string that defines the flowing water fraction and should be set to one of the following character strings: WOR: for the water fraction being the water-oil ratio[{ q sub w } over{ q sub o }] and should be used if FLO is set to 'OIL' or 'LIQ' and should be used if FLO is set to 'OIL' or 'LIQ' WCT: for the water fraction being the water cut[{ q sub w } over{ q sub {o} + q sub{w} }]and should be used if FLO is set to 'OIL' or 'LIQ'and should be used if FLO is set to 'OIL' or 'LIQ' WGR: for the water fraction being the water-gas ratio[{ q sub w } over{ q sub {g}}]and should be used if FLO is set to 'GAS'.and should be used if FLO is set to 'GAS'.","units":{},"default":"None","record":1,"value_type":"STRING","options":["WOR","WCT","WGR"]},{"index":5,"name":"GFR","description":"A defined character string that defines the flowing gas fraction and should be set to one of the following character strings: GOR: for the gas fraction being the gas-oil ratio[{ q sub g } over{ q sub o }]and should be used if FLO is set to 'OIL' or 'LIQ' and should be used if FLO is set to 'OIL' or 'LIQ' GLR: for the gas fraction being the gas-liquid ratio[{ q sub g } over{ q sub {o} + q sub{w} }]and should be used if FLO is set to 'OIL' or 'LIQ'and should be used if FLO is set to 'OIL' or 'LIQ' OGR: for the gas fraction being the oil-gas ratio[{ q sub o } over{ q sub {g}}]and should be used if FLO is set to 'GAS'.and should be used if FLO is set to 'GAS'.","units":{},"default":"None","record":1,"value_type":"STRING","options":["GOR","GLR","OGR"]},{"index":6,"name":"VFPTYPE","description":"A defined character string that should be defaulted or set equal to THP.","units":{},"default":"THP","record":1,"value_type":"STRING"},{"index":7,"name":"ALQ","description":"A defined character string that defines the artificial lift quantity and should be set to one of the following character strings: GRAT: for the artificial lift quantity being the gas lift gas injection rate. IGLR: for the artificial lift quantity being the gas lift gas, injection gas-liquid ratio. TGLR: for the artificial lift quantity being the gas lift gas, total gas-liquid ratio. COMP: for the artificial lift quantity being the compressor power, for a compressor. PUMP: for the artificial lift quantity being the pump rating for a pump. DENO: for oil surface density. DENG: for gas surface density. BEAN: for multi-segment wells choke parameter. ' ': for undefined, that is for no ALQ data. The DENO and DENG options are not supported by OPM Flow. The ALQ parameter is just another variable used to interpolate the outflow pressure based on the inlet pressure, together with the phases flowing through the system. As such, ALQ can represent any parameter; however, the units should be consistent with that used to set the value. For example, if pump speed (Hz) is used to set a well’s artificial lift quantity via the WCONPROD(ALQ-WELL) parameter in the SCHEDULE section, then the ALQ-DATA should represent pump speed in Hz. The default value is' ' or undefined, that covers the case when the ALQ variable is not entered, except for when gas lift is employed in the model.When gas lift is active then the default value for ALQ is set to GRAT provided: Gas lift optimization is active via the LIFTOPT keyword, or The GLIFTLIM keyword in the SCHEDULE section is used to constrain the total amount of gas lift used within a group, or Gas lift flows are included in the network pressure loss calculations as determined by the GRUPNET(OPTION2), or the NODEPROP(GASLIFT) parameters in the SCHEDULE section. In addition, if any of the above is true than ALQ must be set to GRAT.","units":{},"default":"' '","record":1,"value_type":"STRING","options":["GRAT","IGLR","TGLR","COMP","PUMP","DENO","DENG","BEAN"]},{"index":8,"name":"VFPUNITS","description":"A defined character string that specifies the units system for the VFP table. An error message is output if this is not the same as the model units.","units":{"field":"FIELD","metric":"METRIC","laboratory":"LAB"},"default":"Model units","record":1,"value_type":"STRING"},{"index":9,"name":"VFPVALUE","description":"A defined character string that defines the type of data in the VFP-DATA vector. This should be set equal to BHP if the vector contains bottom-hole pressure data, or TEMP if the vector contains Tubing Head Temperature (THT) data. OPM Flow only supports the (default) BHP option.","units":{},"default":"BHP","record":1,"value_type":"STRING"},{"index":1,"name":"FLO-DATA","description":"A real positive monotonically increasing vector that defines the numerical values of the flowing phase declared by the FLO variable. The number of entries must greater than two and less than or equal to MXMFLO as defined on the VFPPDIMS keyword in the RUNSPEC section.","units":{"field":"Liquid: stb Gas: Mscf","metric":"Liquid: sm3 Gas: sm3","laboratory":"Liquid: scc Gas: scc"},"default":"None","record":2,"value_type":"DOUBLE"},{"index":1,"name":"THP-DATA","description":"A real positive monotonically increasing vector that defines the numerical values of the tubing head pressure values. The number of entries must greater than two and less than or equal to MXMTHP as defined on the VFPPDIMS keyword in the RUNSPEC section.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","record":3,"value_type":"DOUBLE"},{"index":1,"name":"WFR-DATA","description":"A real positive monotonically increasing vector that defines the numerical values of the flowing water fraction declared by the WFR variable. The number of entries must greater than two and less than or equal to MXMWFR as defined on the VFPPDIMS keyword in the RUNSPEC section.","units":{"field":"WOR: stb/stb WCT: stb/stb WGR: stb/Mscf","metric":"sm3/sm3 sm3/sm3 sm3/sm3","laboratory":"scc/scc scc/scc scc/scc"},"default":"None","record":4,"value_type":"DOUBLE"},{"index":1,"name":"GFR-DATA","description":"A real positive monotonically increasing vector that defines the numerical values of the flowing gas fraction declared by the GFR variable. The number of entries must greater than two and less than or equal to MXMGFR as defined on the VFPPDIMS keyword in the RUNSPEC section.","units":{"field":"GOR: Mscf/stb GLR: Mscf/stb OGR: stb/Mscf","metric":"sm3/sm3 sm3/sm3 sm3/sm3","laboratory":"scc/scc scc/scc scc/scc"},"default":"None","record":5,"value_type":"DOUBLE"},{"index":1,"name":"ALQ-DATA","description":"A real positive monotonically increasing vector that defines the numerical values of the artificial lift quantity declared by the ALQ variable. The number of entries must greater than two and less than or equal to MXMALQ as defined on the VFPPDIMS keyword in the RUNSPEC section.","units":{"field":"GRAT: Mscf/d IGLR: Mscf/stb TGLR: Mscf/stb DENO: lb/ft3 DENG: lb/ft3 BEAN: 1/64 inch","metric":"sm3/day sm3/sm3 sm3/sm3 kg/m3 kg/m3 mm","laboratory":"scc/hour scc/scc scc/scc gm/cc gm/cc mm"},"default":"None","record":6,"value_type":"DOUBLE"},{"index":1,"name":"NTHP","description":"This data record consists of a series of integer values that defines the index of THP, WFR, GFR, ALQ entered via the those records on this keyword. The first index, NTHP, is an integer value that defines the index of THP values entered via the THP-DATA records on this keyword. For example, if THP-DATA is equal to 100, 200, 300 and 350 and NTHP is equal to three then NTHP refers to third entry, that is THP equal to 300.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","record":7,"value_type":"INT"},{"index":2,"name":"WFR_INDEX","description":"","units":{},"default":"","value_type":"INT","record":7},{"index":3,"name":"GFR_INDEX","description":"","units":{},"default":"","value_type":"INT","record":7},{"index":4,"name":"ALQ_INDEX","description":"","units":{},"default":"","value_type":"INT","record":7},{"index":5,"name":"VALUES","description":"","units":{},"default":"","value_type":"DOUBLE","record":7}],"example":"The following example shows the VFPPROD table for a production gas well and is taken from the Norne OPM Flow model. Here WFR has been set to water-gas ratio and GFR has been set to the oil-gas ratio, and the ALQ value is defaulted.\nVFPPROD\n-- Table Datum Depth Rate Type WFR Type GFR Type\n-- ----- ----------- --------- -------- --------\n5 2623.39 'GAS' 'WGR' 'OGR' /\n-- 'GAS' units - SM3/DAY\n50000.0 100000.0 200000.0 400000.0 800000.0\n1200000.0 1600000.0 1999999.9 3000000.0 3999999.8\n5000000.5 /\n-- 'THP' units - BARSA\n10.00 20.00 40.00 80.00 120.00\n150.00 200.00 250.00 /\n-- 'WGR' units - SM3/SM3\n0 1e-9 1e-6 1e-5 0.0001\n0.001 0.01 0.1 /\n-- 'OGR' units - SM3/SM3\n1e-7 1e-6 1e-5 0.0001 0.001\n0.01 /\n-- 'ALQ' units -\n0 /\n1 1 1 1 11.93 12.22 13.35 17.24 27.93\n39.83 52.06 64.38 95.20 125.89\n156.52\n/\n1 1 2 1 11.93 12.22 13.35 17.24 27.94\n39.84 52.07 64.39 95.21 125.91\n156.55\n/\n……………………………………….………………………….……………………………………………………………………\n……………………………………….………………………….……………………………………………………………………\n8 8 5 1 483.75 511.15 614.09 1044.78 2757.56\n5592.55 9528.36 14567.24 32005.79 56375.24\n87684\n/\n8 8 6 1 487.68 516.24 624.74 1075.40 2860.16\n5803.92 9880.58 15093.76 33119.59 58297.57\n90639\n/\nThe example shows the first two and the last two records of type seven, as the data is too voluminous to be included.\nThe next example below shows an example oil producing well VFPPROD, again taken from Norne OPM Flow model. Here WFR has been set to water cut and GFR has been set to the gas-oil ratio, and the ALQ value is defaulted.\nVFPPROD\n-- Table Datum Depth Rate Type WFR Type GFR Type TAB Type\n-- ----- ----------- --------- -------- -------- --------\n-- 37 2641.02 'LIQ' 'WCT' 'GOR' /\n-- Prosper files are corrected from RKB to MSL depth. lmarr\n-- Table Datum Depth Rate Type WFR Type GFR Type TAB Type\n-- ----- ----------- --------- -------- -------- --------\n37 2617.02 'LIQ' 'WCT' 'GOR' /\n-- 'LIQ' units - SM3/DAY\n200.0 500.0 1000.0 1500.0 2000.0\n2500.0 3000.0 3500.0 4000.0 4500.0\n5000.0 5500.0 6000.0 6500.0 7000.0\n7500.0 8000.0 10000.0 14000.0 /\n-- 'THP' units - BARSA\n21.01 51.01 61.01 81.01 101.01\n121.01 141.01 161.01 181.01 201.01 /\n-- 'WCT' units - FRACTION\n0 0.1 0.2 0.3 0.4\n0.5 0.6 0.7 0.8 1 /\n-- 'GOR' units - SM3/SM3\n90 100 150 200 500\n1000 2000 /\n-- 'ALQ' units -\n0 /\n1 1 1 1 160.82 136.70 119.79 115.86 117.38\n121.16 126.08 131.56 137.48 143.74\n150.29 157.07 164.02 171.07 178.13\n185.11 192.09 220.38 280.86\n/\n1 1 2 1 155.63 129.40 112.32 108.64 110.44\n114.74 120.15 126.09 132.47 139.05\n146.02 153.41 160.67 167.91 175.13\n182.34 189.55 218.81 281.02\n/\n……………………………………….………………………….……………………………………………………………………\n……………………………………….………………………….……………………………………………………………………\n10 10 6 1 439.30 437.95 437.53 437.79 438.39\n439.26 440.36 441.67 443.19 444.92\n446.85 448.99 451.32 453.85 456.58\n459.51 462.64 477.11 515.47\n/\n10 10 7 1 439.30 437.95 437.53 437.79 438.39\n439.26 440.36 441.67 443.19 444.92\n446.85 448.99 451.32 453.85 456.58\n459.51 462.64 477.11 515.47\n/\nThe example shows the first two and the last two records of type seven, as the data is too voluminous to be included.\n| Note It is possible to have only the OIL and WATER keywords in the RUNSPEC section and to use gas lift for the wells, without declaring the GAS phase in the RUNSPEC section. In this case, the FLO parameter in Table 12.75must be set to either OIL or LIQ, WFR to either WCT or WOR, and GFR to GOR. In this case the ALQ parameter is optional, but if present must set to GRAT. If the ALQ and ALQ-DATA parameters are absent then the GFR-DATA will be used based on the flowing GOR plus the stipulated gas lift gas. |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------","records_meta":[{"expected_columns":9},{},{},{},{},{},{}],"size_kind":"fixed","variadic_record":true,"size_count":7},"VFPTABL":{"name":"VFPTABL","sections":["SCHEDULE"],"supported":false,"summary":"The VFPTABL keyword defines the interpolation method for production Vertical Flow Performance (“VFP”) tables for the Artificial Lift Quantity (“ALQ”). Production VFP data is entered via the VFPPROD keyword in the SCHEDULE section. By default the simulator interpolates all the variables in the VFP tables using linear interpolation, including the ALQ quantity. However, if the ALQ values represent gas lift, then linear interpolation may not be insufficient, as the gradient change between the tabulated ALQ values may result in sudden changes. This is particularly important in gas lift optimization studies where the available gas lift gas is being allocated to a group of wells in order to maximize oil production rates. To overcome this issue the VFPTABL keyword allows the ALQ values to be interpolated using cubic spline interpolation, and results in a smother transition between the various ALQ entries.","parameters":[{"index":1,"name":"VFPTABL","description":"VFPTABL is a defined positive integer that specifies the interpolation method to be used with the ALQ quantity in the VFP production tables, and should be set to one of the following: Apply linear interpolation to all VFPPROD variables. Apply linear interpolation to all VFPPROD variables, except for the ALQ variable, for which cubic spline interpolation should be used. If the keyword is absent from the input deck then linear interpolation will be used for all variables.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1","value_type":"INT"}],"example":"The example sets cubic spline interpolation for the ALQ quantity in the VFPPROD tables, with linear interpolation used for all the variables.\n--\n-- ALQ INTERPOLATION OPTION\n--\n-- OPTION\nVFPTABL\n2\n/","expected_columns":1,"size_kind":"fixed","size_count":1},"WAITBAL":{"name":"WAITBAL","sections":["SCHEDULE"],"supported":false,"summary":"This keyword sets the network balance option for all networks when networks are active in the model. Basically, the keyword either activates the PRORDER and GDRILPOT stipulated actions before or after the network has been balanced","parameters":[{"index":1,"name":"WAIT_NETWORK_BALANCE","description":"","units":{},"default":"NO","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"WALKALIN":{"name":"WALKALIN","sections":["SCHEDULE"],"supported":false,"summary":"WAKALIN keyword defines the water injection alkaline concentration for water injection wells for when the surfactant and/or polymer models have been activated by the SURFACT, SURFACTW, or the POLYMER keywords in the RUNSPEC section, combined with the ALKALINE keyword which is also in the RUNSPEC section.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"ALKALINE_CONCENTRAION","description":"","units":{},"default":"","value_type":"UDA","dimension":"Mass/LiquidSurfaceVolume"}],"example":"","expected_columns":2,"size_kind":"list"},"WALQCALC":{"name":"WALQCALC","sections":["SCHEDULE"],"supported":false,"summary":"The WALQCALC keyword defines the well VFP surface ALQ phase density use in the VFP table lookup and interpolation to be gas surface density, oil surface density, or neither. Note that the user should ensure that generated VFP tables have been generated consistent with the setting on this keyword.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"ALQ_DEF","description":"","units":{},"default":"NONE","value_type":"STRING"}],"example":"","expected_columns":2,"size_kind":"list"},"WAPI":{"name":"WAPI","sections":["SCHEDULE"],"supported":false,"summary":"This keyword defines an oil injection well’s API gravity for when API tracking has been made active via the API keyword in the RUNSPEC section. The American Petroleum Institute (API) classifies oils based on an API gravity (γAPI), or degrees API (oAPI), the relationship between relative density (γo) of oil and API gravity (γAPI) is given by:","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"API","description":"","units":{},"default":"","value_type":"UDA"}],"example":"| [%gamma SUB { API } ~ = ~ { 141.5 } OVER { %gamma SUB { o }}~-~ 131.5] | (12.33) |\n|------------------------------------------------------------------------|---------|","expected_columns":2,"size_kind":"list"},"WBHGLR":{"name":"WBHGLR","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, WBHGLR, defines a well’s bottom-hole Gas Liquid Ratio (“GLR”) constraint, where the GLR is the is the ratio of the “free” gas rate and liquid rate at bottom-hole conditions. The reference depth for bottom-hole conditions is given by the BHPREF variable on the WELSPECS keyword in the SCHEDULE section.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"MAX_GLR_CUTBACK","description":"","units":{},"default":"1e+20","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"MIN_GLR_CUTBACK_REVERSE","description":"","units":{},"default":"1e+20","value_type":"DOUBLE","dimension":"1"},{"index":4,"name":"RATE_CUTBACK_FACTOR","description":"","units":{},"default":"1","value_type":"DOUBLE"},{"index":5,"name":"PHASE","description":"","units":{},"default":"RESV","value_type":"STRING"},{"index":6,"name":"MAX_GLR_ELIMIT","description":"","units":{},"default":"1e+20","value_type":"DOUBLE","dimension":"1"},{"index":7,"name":"WORKOVER_ACTION","description":"","units":{},"default":"NONE","value_type":"STRING"},{"index":8,"name":"WORKOVER_REMOVE_CUTBACKS","description":"","units":{},"default":"NO","value_type":"STRING"}],"example":"","expected_columns":8,"size_kind":"list"},"WBOREVOL":{"name":"WBOREVOL","sections":["SCHEDULE"],"supported":false,"summary":"The WBOREVOL defines a well’s effective wellbore storage volume. The primary purpose of the keyword is to enable matching of the wellbore storage effects in well tests and the corresponding pressure response observed in the test. Normally, as part of well test interpretation, the pressure, permeability, effective wellbore storage, etc., are derived from the analytical interpretation of the test. This keyword therefore allows the engineer to enter the analytical derived effective wellbore storage.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"WELLBORE_VOL","description":"","units":{},"default":"1e-05","value_type":"DOUBLE","dimension":"Length*Length*Length"},{"index":3,"name":"START_BHP","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"}],"example":"","expected_columns":3,"size_kind":"list"},"WCALCVAL":{"name":"WCALCVAL","sections":["SCHEDULE"],"supported":false,"summary":"This keyword defines a gas well’s calorific value for when the Gas Calorific Value option has been activated by specifying a target calorific value for a group via the GCONCAL keyword in the SCHEDULE section. If this option is invoked then the gas calorific value must be set either by this keyword for a well by well allocation of the calorific value, or by using the Tracer Tracking option (activated by the TRACER keyword in the RUNSPEC section) combined with CALTRAC keyword in the SCHEDULE section that defines the tracer for the calorific value.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"CALORIFIC_GAS_VALUE","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Energy/GasSurfaceVolume"}],"example":"","expected_columns":2,"size_kind":"list"},"WCONHIST":{"name":"WCONHIST","sections":["SCHEDULE"],"supported":null,"summary":"The WCONHIST keyword defines production rates and pressures for wells that have been declared history matching wells by the use of this keyword. History matching wells are handled differently than ordinary wells that use the WCONPROD keyword for controlling their production targets and constraints. However, the wells still need to be defined like ordinary production wells using the WELSPECS keyword in the SCHEDULE section.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the wells observed production rates and pressures are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"STATUS","description":"A defined character string that declares the status of the well. STATUS should be set to one of the following character strings: OPEN: the well is open to flow and will attempt to produce the required production volumes. STOP: the well is “stopped” at the surface and will not produce any fluids to surface; however, if there any open connections then flow may occur within the wellbore and between the open connections depending on a connection’s potential with respect to all the other connections. Inter-connection flow (cross flow) can be prevented by setting the XFLOW variable on the WELSPECS keyword to NO. In this case the well’s behavior will be similar to the SHUT option described below. SHUT: the well is shut at the surface and downhole, this results in no flow at the surface and no cross flow downhole. Note a well’s STATUS should always be set either STOP or SHUT if the well’s production is to be set to zero. Just setting a well’s production rate to zero means that the well is open to flow with a zero rate.","units":{},"default":"OPEN","value_type":"STRING","options":["OPEN","STOP","SHUT"]},{"index":3,"name":"TARGET","description":"A defined character string that sets the observed target production phase for the well, all the other phases are calculated unconstrained and used for reporting only. The simulator will attempt to meet the TARGET based on the phase rate stated in items (4) to (6) and (10) on this keyword. TARGET should be set to one of the following character strings: ORAT: the target is set to the surface oil production rate as defined by item (4). WRAT: the target is set to the surface water production rate as defined by item (5). GRAT: the target is set to the surface gas production rate as defined by item (6). LRAT: the target is set to the surface liquid (oil plus water) production rate and is calculated by the simulator using (4) and (5). RESV: the target is set to the in situ reservoir volume rate and is calculated by the simulator using items (4), (5) and (6). BHP: the target rate is set to the bottom-hole pressure as defined by item (10). Note the TARGET control mode may be reset using the WHISTCTL keyword in the SCHEDULE section, from the time the WHISTCTL is invoked, thus avoiding changing the control mode on all subsequent WCONHIST keywords.","units":{},"default":"None","value_type":"STRING","options":["ORAT","WRAT","GRAT","LRAT","RESV","BHP"]},{"index":4,"name":"ORAT","description":"A real positive value that defines the observed surface oil production rate target or constraint. This value may be specified using a User Defined Argument (UDA).","units":{"field":"stb/d 0.0","metric":"sm3/day 0.0","laboratory":"scc/hour 0.0"},"default":"Defined","value_type":"UDA","dimension":"LiquidSurfaceVolume/Time"},{"index":5,"name":"WRAT","description":"A real positive value that defines the observed surface water production rate target or constraint. This value may be specified using a User Defined Argument (UDA).","units":{"field":"stb/d 0.0","metric":"sm3/day 0.0","laboratory":"scc/hour 0.0"},"default":"Defined","value_type":"UDA","dimension":"LiquidSurfaceVolume/Time"},{"index":6,"name":"GRAT","description":"A real positive value that defines the observed surface gas production rate target or constraint This value may be specified using a User Defined Argument (UDA).","units":{"field":"Mscf/d 0.0","metric":"sm3/day 0.0","laboratory":"scc/hour 0.0"},"default":"Defined","value_type":"UDA","dimension":"GasSurfaceVolume/Time"},{"index":7,"name":"VFPTAB","description":"A positive integer greater than or equal to zero that defines the vertical lift performance tables to be used for calculating the tubing head pressure for the well. If a non-zero value is entered then the vertical lift performance tables must be entered via the VFPPROD keyword in the SCHEDULE section and allocated to the well via this item. The default value of zero implies no vertical lift performance table initially. If this value is then reset to be greater than zero then the table will be used to calculate the well’s tubing head pressure. Subsequently, the default is to use the previously declared table number.","units":{},"default":"0","value_type":"INT"},{"index":8,"name":"ALQ-WELL","description":"A real positive value that defines the artificial lift quantity to be used in conjunction with the VFPPROD assigned to the well via that keyword's VFPTAB variable. This value may be specified using a User Defined Argument (UDA). VFPTAB vertical lift performance table and the artificial lift quantity ALQ-WELL are used with the well fluid rates to calculate the well’s tubing head pressures values from the bottom-hole pressure. Note that the units for ALQ-WELL is dependent on the associated variable on the VFPPROD keyword.","units":{},"default":"None","value_type":"UDA"},{"index":9,"name":"THP","description":"A real positive value that defines the observed tubing head pressure. This value may be specified using a User Defined Argument (UDA). This parameter is only used for comparing the actual tubing head pressure given here with those calculated by the simulator, that is history matching wells can only be controlled by either the surface injection rate or their bottom-hole pressure.","units":{"field":"psia 0.0","metric":"barsa 0.0","laboratory":"atma 0.0"},"default":"Defined","value_type":"UDA","dimension":"Pressure"},{"index":10,"name":"BHP","description":"A real positive value that defines the observed bottom-hole pressure. This value may be specified using a User Defined Argument (UDA).","units":{"field":"psia 0.0","metric":"barsa 0.0","laboratory":"atma 0.0"},"default":"Defined","value_type":"UDA","dimension":"Pressure"},{"index":11,"name":"WGRA","description":"A real positive value that defines the observed wet gas rate in the commercial compositional simulator. The parameter is ignored by OPM Flow and should be defaulted or set to the default value of zero.","units":{},"default":"0.0","value_type":"DOUBLE","dimension":"GasSurfaceVolume/Time"},{"index":12,"name":"NGL","description":"A real positive value that defines the observed Natural Gas Liquid (“NGL”) rate in the commercial compositional simulator. The parameter is ignored by OPM Flow and should be defaulted or set to the default value of zero.","units":{},"default":"0.0","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time"}],"example":"The following example below shows the observed production rates for the OP01 oil producer for the first quarter of 2000.\n-- ------------------------------------------------------------------------------\n-- 01 JAN 2000 START OF SCHEDULE SECTION\n-- ------------------------------------------------------------------------------\n--\n-- WELL HISTORICAL PRODUCTION CONTROLS\n--\n-- WELL OPEN/ CNTL OIL WAT GAS VFP VFP THP BHP\n-- NAME SHUT MODE RATE RATE RATE TABLE ALFQ PRES PRES\nWCONHIST OP01 OPEN ORAT 15.5E3 100.0 1550 10 1* 900.0 1* /\n/ DATES\n01 FEB 2000 /\n/\n--\n-- WELL HISTORICAL PRODUCTION CONTROLS\n--\n-- WELL OPEN/ CNTL OIL WAT GAS VFP VFP THP BHP\n-- NAME SHUT MODE RATE RATE RATE TABLE ALFQ PRES PRES\nWCONHIST OP01 OPEN ORAT 15.2E3 150.0 1520 1* 1* 875.0 3250.0 /\n/ DATES\n01 MAR 2000 /\n/\n--\n-- WELL HISTORICAL PRODUCTION CONTROLS\n--\n-- WELL OPEN/ CNTL OIL WAT GAS VFP VFP THP BHP\n-- NAME SHUT MODE RATE RATE RATE TABLE ALFQ PRES PRES\nWCONHIST OP01 OPEN ORAT 15.0E3 200.0 1500 1* 1* 850.0 1* /\n/\nFrom January 1, 2000 well OP01 is open and is on oil rate control, and produces 15,500 stb/d oil, with the observed rates of 100 stb/d of water and 15.5 MMscf/d of gas. The well uses VFPPROD vertical lift table number 10 so that OPM Flow can calculate the tubing head pressures based on the fluids produced and the calculated pressures in the simulator.\nThe next example illustrates how to convert OP01 from a history match well to a normal production well at the start for the forecast run at August 1, 2017 using the WELTARG keyword.\nDATES\n01 AUG 2017 /\n/\n--\n-- WELL PRODUCTION AND INJECTION TARGETS\n--\n-- WELL WELL TARGET\n-- NAME TARG VALUE\nWELTARG\nOP01 THP 1* /\n/\nHere by defaulting the bottom-hole pressure via 1* OPM Flow automatically applies the last bottom-hole pressure from the previous time step as the “constraining phase” together with the last historical rates as constraints. This ensures a smooth transition between history and prediction without having to resort to unreasonable changes to the model. This option is currently not implemented in OPM Flow but is expected to be incorporated in a future release.\n| Note One can use TARGET set to RESV in the initial history matching runs to get a “reasonable” pressure match, this ensures that the total reservoir withdrawals are correct, although the individual phase withdrawals will not match. Once a reasonable pressure match is achieved for the reservoir then one can reset TARGET to the sales phase, OIL or GAS, and continue with the matching of all the phases. In oil reservoirs some engineers prefer to use LIQ rather than OIL as the TARGET phase, although one should consider that as the water phase has no commercial value, the measurement accuracy is significantly less than the oil sales phase. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":12,"size_kind":"list"},"WCONINJ":{"name":"WCONINJ","sections":["SCHEDULE"],"supported":false,"summary":"The WCONINJ is a legacy keyword that is no longer used in the commercial simulator and is not supported by OPM Flow. Instead well injection targets and constraints should be defined using the WCONINJE keyword in the SCHEDULE section.","parameters":[],"example":"","size_kind":"none","size_count":0},"WCONINJE":{"name":"WCONINJE","sections":["SCHEDULE"],"supported":false,"summary":"The WCONINJE keyword defines injection targets and constraints for wells that have previously been defined by the WELSPECS keyword in the SCHEDULE section. Note that wells can be allocated to a group when they are specified by the WELSPECS keyword. Wells defined to be under group control will have their injection rates controlled by the group to which they belong, in addition to any well constraints defined for the wells using this keyword.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well injection targets and constraints data are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"TYPE","description":"A defined character string that defines the type of injection well. TYPE should be set to one of the following character strings: GAS: for a gas injection well. OIL: for an oil injection well. WAT: for a water injection well.","units":{},"default":"None","value_type":"STRING","options":["GAS","OIL","WAT"]},{"index":3,"name":"STATUS","description":"A defined character string that declares the status of the well. STATUS should be set to one of the following character strings: OPEN: the well is open for injection and will attempt to inject the required injection volumes. STOP: the well is “stopped” at the surface and will not inject any fluids; however, if there any open connections then flow may occur within the wellbore and between the open connections depending on a connection’s potential with respect to all the other connections. Inter-connection flow (cross flow) can be prevented by setting the XFLOW variable on the WELSPECS keyword to NO. In this case the well’s behavior will be similar to the SHUT option described below. SHUT: the well is shut at the surface and downhole, this results in no injection and no cross flow downhole. AUTO: the well is initially SHUT, but may be opened automatically if an economic limit is violated. This option is currently not supported by OPM Flow. Note a well’s STATUS should always be set either STOP or SHUT if the well’s injection is to be set to zero. Just setting a well’s injection rate to zero means that the well is open for injection with a zero rate, this will cause numerical issues especially for wells under THP control.","units":{},"default":"OPEN","value_type":"STRING","options":["OPEN","STOP","SHUT","AUTO"]},{"index":4,"name":"TARGET","description":"A defined character string that sets the target injection control mode for the well. TARGET should be set to one of the following character strings: RATE: the injection phase will be controlled by the surface fluid rate for the given well type as defined by the TYPE variable. For example, if TYPE has been set to WAT then this would mean the surface water injection rate as defined by item (5). RESV: the injection phase will be controlled by the in situ reservoir volume fluid rate for the given well type as defined by the TYPE variable. For example, if TYPE has been set to GAS then this would mean the gas reservoir volume injection rate as defined by item (6). BHP: the target rate is set according to the bottom-hole pressure as defined by item (7). THP: the target rate is set according to the tubing head pressure as defined by item (8). If this option is selected then the vertical lift performance tables must be entered via the VFPINJ keyword in the SCHEDULE section and allocated to the well via item (9). GRUP: the well is under group control and injects its share of the group's target as set using the GCONINJE keyword in the SCHEDULE section.","units":{},"default":"None","value_type":"STRING","options":["RATE","RESV","BHP","THP","GRUP"]},{"index":5,"name":"RATE","description":"A real positive value that defines the maximum surface injection rate target or constraint. This value may be specified using a User Defined Argument (UDA).","units":{"field":"Liquid stb/d Gas Mscf/d","metric":"Liquid sm3/day Gas sm3/day","laboratory":"Liquid scc/hour Gas scc/hour"},"default":"None","value_type":"UDA"},{"index":6,"name":"RESV","description":"A real positive value that defines the maximum reservoir volume injection rate target or constraint. This value may be specified using a User Defined Argument (UDA).","units":{"field":"rb/d","metric":"rm3/day","laboratory":"rcc/hour"},"default":"None","value_type":"UDA","dimension":"ReservoirVolume/Time"},{"index":7,"name":"BHP","description":"A real positive value that defines the maximum bottom-hole pressure target or constraint. This value may be specified using a User Defined Argument (UDA). Note the default value basically means unlimited injection or no constraint and should therefore be avoided as the BHP will result in unrealistic well potentials as well as optimistic injection forecasts for the well.","units":{"field":"psia 10,0000","metric":"barsa 6,895","laboratory":"atma 6,803"},"default":"Defined","value_type":"UDA","dimension":"Pressure"},{"index":8,"name":"THP","description":"A real positive value that defines the maximum tubing head pressure target or constraint. This value may be specified using a User Defined Argument (UDA).","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"UDA","dimension":"Pressure"},{"index":9,"name":"VFPTAB","description":"A positive integer greater than or equal to zero that defines the vertical lift performance tables to be used for calculating the tubing head pressure for the well. If a non-zero value is entered then the vertical lift performance tables must be entered via the VFPINJ keyword in the SCHEDULE section and allocated to the well via this item. The default value of zero implies no vertical lift performance tables and in this case TARGET cannot be set to THP and in addition item (10) should be defaulted or set to zero.","units":{},"default":"0","value_type":"INT"},{"index":10,"name":"RSRVINJ","description":"The dissolved gas-oil ratio in the injected oil, or the vaporized oil-gas ratio in the injected gas.","units":{"field":"Gas Injection: stb/Mscf Oil Injection: Mscf/stb","metric":"Gas Injection: sm3/sm3 Oil Injection: sm3/sm3","laboratory":"Gas Injection: scc/scc Oil Injection: scc/scc"},"default":"0.0","value_type":"DOUBLE","dimension":"OilDissolutionFactor"},{"index":11,"name":"RSSTEAM","description":"Thermal/Temperature gas-steam ratio for steam-gas injectors. The parameter is ignored by OPM Flow and should be defaulted or set to the default value of zero.","units":{},"default":"0.0","value_type":"DOUBLE"},{"index":12,"name":"OILFRAC","description":"Surface oil fraction in a multi-phase injector. The parameter is ignored by OPM Flow and should be defaulted or set to the default value of zero.","units":{},"default":"0.0","value_type":"DOUBLE"},{"index":13,"name":"WATFRAC","description":"Surface water fraction in a multi-phase injector. The parameter is ignored by OPM Flow and should be defaulted or set to the default value of zero.","units":{},"default":"0.0","value_type":"DOUBLE"},{"index":14,"name":"GASFRAC","description":"Surface gas fraction in a multi-phase injector. The parameter is ignored by OPM Flow and should be defaulted or set to the default value of zero.","units":{},"default":"0.0","value_type":"DOUBLE"},{"index":15,"name":"OILSTEAM","description":"Surface oil volume to steam volume ratio in a steam-oil injector. The parameter is ignored by OPM Flow and should be defaulted or set to the default value of zero.","units":{},"default":"0.0","value_type":"DOUBLE"}],"example":"The following example defines the injection targets and constraints for one gas injection well and one water injection well as follows:\n--\n-- WELL INJECTION CONTROLS\n--\n-- WELL FLUID OPEN/ CNTL SURF RESV BHP THP VFP\n-- NAME TYPE SHUT MODE RATE RATE PRSES PRES TABLE\nWCONINJE\nGI01 GAS OPEN GRUP 50E3 1* 1* 1* 1* /\nWI01 WAT OPEN RATE 25E3 1* 5000. 1* 1* /\n/\nWell GI01 is a gas injection well directly under group control constrained by a maximum surface gas injection rate of 50 MMscf/d and well WI01 is an open water injection well with a surface water injection rate target of 25,000 stb/d, subject to a maximum bottom-hole pressure constraint 5,000 psia.","expected_columns":15,"size_kind":"list"},"WCONINJH":{"name":"WCONINJH","sections":["SCHEDULE"],"supported":null,"summary":"The WCONINJH keyword defines injection rates and pressures for wells that have been declared history matching wells by the use of this keyword. History matching wells are handled differently then ordinary wells that use the WCONINJE keyword for controlling their injection targets and constraints. However, the wells still need to be defined like ordinary injection wells using the WELSPECS keyword in the SCHEDULE section.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the wells observed injection rates and pressures are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"TYPE","description":"A defined character string that defines the type of injection well. TYPE should be set to one of the following character strings: GAS: for a gas injection well. OIL: for an oil injection well. WAT: for a water injection well.","units":{},"default":"None","value_type":"STRING","options":["GAS","OIL","WAT"]},{"index":3,"name":"STATUS","description":"A defined character string that declares the status of the well. STATUS should be set to one of the following character strings: OPEN: the well is open for injection and will attempt to inject the observed injection volumes. STOP: the well is “stopped” at the surface and will not inject fluids; however, if there any open connections then flow may occur within the wellbore and between the open connections depending on a connection’s potential with respect to all the other connections. Inter-connection flow (cross flow) can be prevented by setting the XFLOW variable on the WELSPECS keyword to NO. In this case the well’s behavior will be similar to the SHUT option described below. SHUT: the well is shut at the surface and downhole, this results in no injection and no cross flow downhole. Note a well’s STATUS should always be set either STOP or SHUT if the well’s injection is to be set to zero. Just setting a well’s injection rate to zero means that the well is open to flow with a zero injection rate, this may cause numerical issues.","units":{},"default":"OPEN","value_type":"STRING","options":["OPEN","STOP","SHUT"]},{"index":4,"name":"RATE","description":"A real positive value that defines the observed surface injection rate.","units":{"field":"Liquid stb/d Gas Mscf/d","metric":"Liquid sm3/day Gas sm3/day","laboratory":"Liquid scc/hour Gas scc/hour"},"default":"0.0","value_type":"DOUBLE","dimension":"ContextDependent"},{"index":5,"name":"BHP","description":"A real positive value that defines the observed bottom-hole pressure.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"0.0","value_type":"DOUBLE","dimension":"Pressure"},{"index":6,"name":"THP","description":"A real positive value that defines the observed tubing head pressure. This parameter is only used for comparing the actual tubing head pressure given here with those calculated by the simulator, that is history matching wells can only be controlled by either the surface injection rate or their bottom-hole pressure.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":"Pressure"},{"index":7,"name":"VFPTAB","description":"A positive integer greater than or equal to zero that defines the vertical lift performance tables to be used for calculating the tubing head pressure for the well. If a non-zero value is entered then the vertical lift performance tables must be entered via the VFPINJ keyword in the SCHEDULE section and allocated to the well via this item. The default value of zero implies no vertical lift performance table initially. If this value is then reset to be greater than zero then the table will be used to calculate the well’s tubing head pressure. Subsequently, the default is to use the previously declared table number.","units":{},"default":"0","value_type":"INT"},{"index":8,"name":"RSRVINJ","description":"Dissolved gas fraction in injected oil or vaporized oil fraction in injected gas. The parameter is ignored by OPM Flow and should be defaulted or set to the default value of zero.","units":{},"default":"0.0","value_type":"DOUBLE","dimension":"OilDissolutionFactor"},{"index":9,"name":"OILFRAC","description":"Surface oil fraction in a multi-phase injector. The parameter is ignored by OPM Flow and should be defaulted or set to the default value of zero.","units":{},"default":"0.0","value_type":"DOUBLE"},{"index":10,"name":"WATFRAC","description":"Surface water fraction in a multi-phase injector. The parameter is ignored by OPM Flow and should be defaulted or set to the default value of zero.","units":{},"default":"0.0","value_type":"DOUBLE"},{"index":11,"name":"GASFRAC","description":"Surface gas fraction in a multi-phase injector. The parameter is ignored by OPM Flow and should be defaulted or set to the default value of zero.","units":{},"default":"0.0","value_type":"DOUBLE"},{"index":12,"name":"TARGET","description":"A defined character string that sets the target injection control mode for the well. TARGET should be set to one of the following character strings: RATE: the injection well will be controlled by the surface injection rate for the given well type as defined by the TYPE variable. For example, if TYPE has been set to WAT then this would mean the surface water injection rate as defined by item (4). BHP: the injection well will be controlled by the bottom-hole pressure as defined by item (5).","units":{},"default":"RATE","value_type":"STRING","options":["RATE","BHP"]}],"example":"The following example below shows the observed gas rates for the GI01 gas injector for the first quarter of 2000.\n-- ------------------------------------------------------------------------------\n-- 01 JAN 2000 START OF SCHEDULE SECTION\n-- ------------------------------------------------------------------------------\n--\n-- WELL HISTORICAL INJECTION CONTROLS\n--\n-- WELL FLUID OPEN/ SURF BHP THP VFP NOT CNTL\n-- NAME TYPE SHUT RATE PRES PRES TABLE USED MODE\nWCONINJH\nGI01 GAS OPEN 15.5E3 1* 5462 12 4* 1* /\n/ DATES\n01 FEB 2000 /\n/\n--\n-- WELL HISTORICAL INJECTION CONTROLS\n--\n-- WELL FLUID OPEN/ SURF BHP THP VFP NOT CNTL\n-- NAME TYPE SHUT RATE PRES PRES TABLE USED MODE\nWCONINJH\nGI01 GAS OPEN 15.9E3 1* 5468 1* 4* 1* /\n/ DATES\n01 MAR 2000 /\n/\n--\n-- WELL HISTORICAL INJECTION CONTROLS\n--\n-- WELL FLUID OPEN/ SURF BHP THP VFP NOT CNTL\n-- NAME TYPE SHUT RATE PRES PRES TABLE USED MODE\nWCONINJH\nGI01 GAS OPEN 17.2E3 1* 5489 1* 4* 1* /\n/\nWell GI01is declared as a gas injection well under gas rate control as TARGET variable is defaulted to rate control by using 1* (the last entry on the record). In addition, the well uses vertical lift table VFPINJ number 12 (as shown at January 1, 2000) to calculate the tubing head pressures for the well. Note that it is not necessary to declare the VFPINJ table number if it remains the same for subsequent time steps and thus the default 1* is used to indicate the last entry should be used.","expected_columns":12,"size_kind":"list"},"WCONINJP":{"name":"WCONINJP","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, WCONINJP, defines well injection targets and constraints for pattern flood wells. The keyword is similar to the WCONINJE keyword in the SCHEDULE section except that the injection control is applied to a group of wells defined by the first record of this keyword, combined with a second record that defines the wells in the pattern and their contribution to the pattern.","parameters":[{"index":1,"name":"PATTERN_WELL","description":"","units":{},"default":"","value_type":"STRING","record":1},{"index":2,"name":"INJECTOR_TYPE","description":"","units":{},"default":"","value_type":"STRING","record":1},{"index":3,"name":"STATUS","description":"","units":{},"default":"OPEN","value_type":"STRING","record":1},{"index":4,"name":"BHP_MAX","description":"","units":{},"default":"6895","value_type":"DOUBLE","dimension":"Pressure","record":1},{"index":5,"name":"THP_MAX","description":"","units":{},"default":"","value_type":"DOUBLE","record":1},{"index":6,"name":"VFP_TABLE","description":"","units":{},"default":"0","value_type":"INT","record":1},{"index":7,"name":"VOIDAGE_TARGET_MULTIPLIER","description":"","units":{},"default":"1","value_type":"DOUBLE","record":1},{"index":8,"name":"OIL_FRACTION","description":"","units":{},"default":"0","value_type":"DOUBLE","record":1},{"index":9,"name":"WATER_FRACTION","description":"","units":{},"default":"0","value_type":"DOUBLE","record":1},{"index":10,"name":"GAS_FRACTION","description":"","units":{},"default":"0","value_type":"DOUBLE","record":1},{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING","record":2},{"index":2,"name":"PROD_FRACTION","description":"","units":{},"default":"","value_type":"DOUBLE","record":2},{"index":3,"name":"FIPNUM_VALUE","description":"","units":{},"default":"0","value_type":"INT","record":2}],"example":"","records_meta":[{"expected_columns":10},{"expected_columns":3}],"size_kind":"list"},"WCONPROD":{"name":"WCONPROD","sections":["SCHEDULE"],"supported":false,"summary":"The WCONPROD keyword defines production targets and constraints for wells that have previously been defined by the WELSPECS keyword in the SCHEDULE section. Note that wells can be allocated to a group when they are specified by the WELSPECS keyword. Wells defined to be under group control will have their production rates controlled by the group to which they belong, in addition to any well constraints defined for the wells using this keyword.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well production targets and constraints data are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"STATUS","description":"A defined character string that declares the status of the well. STATUS should be set to one of the following character strings: OPEN: the well is open to flow and will attempt to produce the required production volumes. STOP: the well is “stopped” at the surface and will not produce any fluids to surface; however, if there any open connections then flow may occur within the wellbore and between the open connections depending on a connection’s potential with respect to all the other connections. Inter-connection flow (cross flow) can be prevented by setting the XFLOW variable on the WELSPECS keyword to NO. In this case the well’s behavior will be similar to the SHUT option described below. SHUT: the well is shut at the surface and downhole, this results in no flow at the surface and no cross flow downhole. AUTO: the well is initially SHUT, but may be opened automatically if an economic limit is violated. This option is currently not supported by OPM Flow. Note a well’s STATUS should always be set either STOP or SHUT if the well’s production is to be set to zero. Just setting a well’s production rate to zero means that the well is open to flow with a zero rate, this will cause numerical issues especially for wells under THP control.","units":{},"default":"OPEN","value_type":"STRING","options":["OPEN","STOP","SHUT","AUTO"]},{"index":3,"name":"TARGET","description":"A defined character string that sets the target production phase for the well, all the other phases will therefore act as constraints. The simulator will attempt to meet the TARGET based on the phase rate stated in items (4) to (10) on this keyword. TARGET should be set to one of the following character strings: ORAT: the target is set to the surface oil production rate as defined by item (4). WRAT: the target is set to the surface water production rate as defined by item (5). GRAT: the target is set to the surface gas production rate as defined by item (6). LRAT: the target is set to the surface liquid (oil plus water) production rate as defined by item (7). RESV: the target is set to the in situ reservoir volume rate as defined by item (8). BHP: the target rate is set to the bottom-hole pressure as defined by item (9). THP: the target rate is set to the tubing head pressure as defined by item (10). If this option is selected then the vertical lift performance tables must be entered via the VFPPROD keyword in the SCHEDULE section and allocated to the well via item (11). GRUP: the well is under group control and produces its share of the group's target as set using the GCONPROD keyword in the SCHEDULE section. Here the default tokens of 1* or '' may be used, and both default tokens behave in the same manner; however, the actual default value used when TARGET is defaulted is dependent on the data entered on this keyword as described below: If the well’s group parameters have not been defined via the GCONPROD keyword, in the SCHEDULE section, then TARGET is set to the first non-defaulted hydrocarbon rate (ORAT, GRAT, LRAT, or RESV). If all the rates are defaulted and a value for BHP is entered, then TARGET is set to BHP control. Similarly, if BHP is also defaulted, and THP has been entered, then TARGET is set to THP control. Finally, if all parameters are defaulted, then the default value for BHP, one atmosphere, will be used with BHP control. If, and only if, the well’s group parameters have been defined via the GCONPROD keyword, then TARGET is set equal to GRUP, and the remaining parameters on the WCONPROD keyword are used as well constraints. Note the default value of one atmosphere should be avoided as the BHP will result in unrealistic well potentials as well as optimistic production forecasts for the well.","units":{},"default":"1*","value_type":"STRING","options":["ORAT","WRAT","GRAT","LRAT","RESV","BHP","THP","GRUP"]},{"index":4,"name":"ORAT","description":"A real positive value that defines the maximum surface oil production rate target or constraint. This value may be specified using a User Defined Argument (UDA).","units":{"field":"stb/day","metric":"sm3/day","laboratory":"scc/hour"},"default":"None","value_type":"UDA","dimension":"LiquidSurfaceVolume/Time"},{"index":5,"name":"WRAT","description":"A real positive value that defines the maximum surface water production rate target or constraint. This value may be specified using a User Defined Argument (UDA).","units":{"field":"stb/day","metric":"sm3/day","laboratory":"scc/hour"},"default":"None","value_type":"UDA","dimension":"LiquidSurfaceVolume/Time"},{"index":6,"name":"GRAT","description":"A real positive value that defines the maximum surface gas production rate target or constraint This value may be specified using a User Defined Argument (UDA).","units":{"field":"Mscf/day","metric":"sm3/day","laboratory":"scc/hour"},"default":"None","value_type":"UDA","dimension":"GasSurfaceVolume/Time"},{"index":7,"name":"LRAT","description":"A real positive value that defines the maximum surface liquid (oil plus water) production rate target or constraint. This value may be specified using a User Defined Argument (UDA).","units":{"field":"stb/day","metric":"sm3/day","laboratory":"scc/hour"},"default":"None","value_type":"UDA","dimension":"LiquidSurfaceVolume/Time"},{"index":8,"name":"RESV","description":"A real positive value that defines the maximum reservoir volume production rate target or constraint. This value may be specified using a User Defined Argument (UDA).","units":{"field":"rtb/day","metric":"rm3/day","laboratory":"rcc/hour"},"default":"None","value_type":"UDA","dimension":"LiquidSurfaceVolume/Time"},{"index":9,"name":"BHP","description":"A real positive value that defines the minimum bottom-hole pressure target or constraint. This value may be specified using a User Defined Argument (UDA). Note the default value of one atmosphere should be avoided as the BHP will result in unrealistic well potentials as well as optimistic production forecasts for the well.","units":{"field":"psia 14.70","metric":"barsa 1.01325.","laboratory":"atma 1.0"},"default":"Defined","value_type":"UDA","dimension":"Pressure"},{"index":10,"name":"THP","description":"A real positive value that defines the minimum tubing head pressure target or constraint. This value may be specified using a User Defined Argument (UDA). Note the default value of zero should be avoided if the well’s control TARGET has been set to THP, as this will result in optimistic production forecasts for a well, since a well must flow against a back pressure imposed by the surface facilities.","units":{"field":"psia 0.0","metric":"barsa 0.0","laboratory":"atma 0.0"},"default":"Defined","value_type":"UDA","dimension":"Pressure"},{"index":11,"name":"VFPTAB","description":"A positive integer greater than or equal to zero that defines the vertical lift performance tables to be used for calculating the tubing head pressure for the well. If a non-zero value is entered then the vertical lift performance tables must be entered via the VFPPROD keyword in the SCHEDULE section and allocated to the well via this item. The default value of zero implies no vertical lift performance tables and in this case TARGET cannot be set to THP and in addition item (10) should be defaulted or set to zero.","units":{},"default":"0","value_type":"INT"},{"index":12,"name":"ALQ-WELL","description":"A real positive value that defines the artificial lift quantity to be used in conjunction with the VFPPROD assigned to the well via the VFPTAB variable. This value may be specified using a User Defined Argument (UDA). VFPTAB vertical lift performance table and the artificial lift quantity ALQ-WELL are used with the well fluid rates to calculate the well’s tubing head pressures values from the bottom-hole pressure. Note that the units for ALQ-WELL are dependent on the associated variable on the VFPPROD keyword.","units":{},"default":"0.0","value_type":"UDA"},{"index":13,"name":"WGASRATE","description":"Wet gas production rate used in the commercial compositional simulator. Not used and should be defaulted with 1*.","units":{},"default":"1*","value_type":"DOUBLE"},{"index":14,"name":"MOLARATE","description":"Total molar rate used in the commercial compositional simulator. Not used and should be defaulted with 1*.","units":{},"default":"1*","value_type":"DOUBLE"},{"index":15,"name":"STEAMRAT","description":"Thermal/Temperature steam rate (Cold Water Equivalent) for steam producers used in the commercial compositional simulator. Not used and should be defaulted with 1*.","units":{},"default":"1*","value_type":"DOUBLE"},{"index":16,"name":"DELTAP","description":"Thermal/Temperature delta pressure offset for steam producers used in the commercial compositional simulator. Not used and should be defaulted with 1*.","units":{},"default":"1*","value_type":"DOUBLE"},{"index":17,"name":"DELTAT","description":"Thermal/Temperature delta temperature offset for steam producer used in the commercial compositional simulator. Not used and should be defaulted with 1*.","units":{},"default":"1*","value_type":"DOUBLE"},{"index":18,"name":"CALRATE","description":"Calorific production rate used in the commercial compositional simulator. Not used and should be defaulted with 1*.","units":{},"default":"1*","value_type":"DOUBLE"},{"index":19,"name":"COMBPROC","description":"Linearly combined procedure for when exceeding COMBRATE, used in the commercial compositional simulator. Not used and should be defaulted with 1*.","units":{},"default":"1*","value_type":"DOUBLE"},{"index":20,"name":"NGL","description":"A real positive value that defines the observed Natural Gas Liquid (“NGL”) rate in the commercial compositional simulator. Not used and should be defaulted with 1*.","units":{},"default":"1*","value_type":"DOUBLE"}],"example":"The following example defines the production targets and constraints for five wells as follows:\n--\n-- WELL PRODUCTION WELL CONTROLS\n--\n-- WELL OPEN/ CNTL OIL WAT GAS LIQ RES BHP THP VFP VFP\n-- NAME SHUT MODE RATE RATE RATE RATE RATE PRES PRES TABLE ALFQ\nWCONPROD\nOP01 OPEN GRUP 5E3 1* 1* 1* 1* 500.0 /\nOP02 OPEN GRUP 10E3 1* 1* 1* 1* 200.0 500.0 2 0.0 /\nOP03 OPEN GRUP 15E3 1* 1* 1* 1* 200.0 500.0 3 10.0 /\nOP04 OPEN ORAT 20E3 1* 1* 1* 1* 500.0 /\nOP05 SHUT GRUP 20E3 1* 1* 1* 1* 500.0 /\n/\nWell OP01 is open and is on group control, subject to a maximum oil rate constraint of 5,000 stb/d and a minimum bottom-hole pressure of 500 psia. OP02 is also open and on group control but it’s maximum oil rate constraint has been set 10,000 stb/d, and is subject to a minimum bottom-hole pressure limit of 200 psia and a minimum tubing head pressure limit of 500 psia using VFPPROD vertical lift table number two. Well OP03 is very similar to OP02, but with a 15,000 stb/d maximum oil constraint and using VFPPROD vertical lift table number three with an artificial lift parameter of 10. The next well is not on group control. Well OP04 is open and has an oil rate target of 20,000 stb/d, subject to a minimum bottom-hole pressure of 500 psia. Finally, well OP05 is shut and will not be brought back on production despite being put under group control, as the well has been declared shut.\nThe next example defines the production targets and constraints for five wells, of which well OP01 is under group control as the well’s group target and constraints have been set with the GCONPROD keyword, and wells OP02 to OP05 belong to groups that have not had their group constraints set by GCONPROD.\n--\n-- GROUP PRODUCTION CONTROLS\n--\n-- GRUP CNTL OIL WAT GAS LIQ CNTL GRUP GUIDE GUIDE CNTL\n-- NAME MODE RATE RATE RATE RATE OPT CNTL RATE DEF WAT\nGCONPROD\nGRP01 SAT 25E3 1* 1* 1* 1* 1* 1* 1* 1* /\n/\n--\n-- WELL SPECIFICATION DATA\n--\n-- WELL GROUP LOCATION BHP PHASE DRAIN INFLOW OPEN CROSS PVT\n-- NAME NAME I J DEPTH FLUID AREA EQUANS SHUT FLOW TABLE\nWELSPECS\nOP01 SAT 14 13 1* OIL 1* P-P SHUT NO 1* /\n0P02 PLATFORM 64 80 1* OIL 1* GPP SHUT NO 1* /\nOP03 PLATFORM 24 110 1* OIL 1* STD SHUT NO 1* /\nOP04 PLATFORM 24 110 1* OIL 1* STD SHUT NO 1* /\nOP05 PLATFORM 24 110 1* OIL 1* STD SHUT NO 1* /\n/\n--\n-- WELL PRODUCTION WELL CONTROLS\n--\n-- WELL OPEN/ CNTL OIL WAT GAS LIQ RES BHP THP VFP VFP\n-- NAME SHUT MODE RATE RATE RATE RATE RATE PRES PRES TABLE ALFQ\nWCONPROD\nOP01 OPEN 1* 15E3 1* 1* 1* 1* 500.0 /\nOP02 OPEN 1* 1* 5E3* 15E6 1* 1* 200.0 500.0 2 0.0 /\nOP03 OPEN 1* 1* 1* 1* 1* 1* 1* 500.0 3 10.0 /\nOP04 OPEN '' 1* 1* 1* 1* 1* 1* 1* 1* 1* /\nOP05 SHUT 1* 1* 1* 1* 1* 1* 1* 1* 1* 1* /\n/\nHere, well OP01’s control mode, TARGET, will be set to group control (GRUP) and the well’s production parameters will all act as constraints. For well OP02, the well’s control mode is set to GRAT, and the other production parameters all act as constraints. Well OP03 control mode is set to THP and if the well’s BHP value has been previously defined then that value will be used as a constraint; otherwise the default value of one atmosphere will be used instead. Finally, wells OP04 and OP05 will have their control mode set to BHP control. Note in this case, OP04’s status has been set to OPEN; thus the well will produce at a target BHP of one atmosphere, which is unrealistic.","expected_columns":20,"size_kind":"list"},"WCUTBACK":{"name":"WCUTBACK","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, WCUTBACK, defines a well’s cutback limits and parameters for both production and injection wells. See also the GCUTBACK keyword in the SCHEDULE section that provides similar functionality for groups.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"WCT_LIMIT","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/LiquidSurfaceVolume"},{"index":3,"name":"GOR_LIMIT","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"GasDissolutionFactor"},{"index":4,"name":"GLR_LIMIT","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"GasDissolutionFactor"},{"index":5,"name":"WGR_LIMIT","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"OilDissolutionFactor"},{"index":6,"name":"RATE_CUTBACK","description":"","units":{},"default":"1","value_type":"DOUBLE"},{"index":7,"name":"PHASE","description":"","units":{},"default":"","value_type":"STRING"},{"index":8,"name":"PRESSURE_LIMIT","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Pressure"},{"index":9,"name":"PRESSURE_LIMIT_REVERSE","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Pressure"},{"index":10,"name":"WCT_LIMIT_REVERSE","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/LiquidSurfaceVolume"},{"index":11,"name":"GOR_LIMIT_REVERSE","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"GasDissolutionFactor"},{"index":12,"name":"GLR_LIMIT_REVERSE","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"GasDissolutionFactor"},{"index":13,"name":"WGR_LIMIT_REVERSE","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"OilDissolutionFactor"},{"index":14,"name":"WORKOVER_REMOVE","description":"","units":{},"default":"NO","value_type":"STRING"}],"example":"","expected_columns":14,"size_kind":"list"},"WCUTBACT":{"name":"WCUTBACT","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, WCUTBACT, defines a production well’s cutback limits and parameters based on the named produced tracer from the well. See also the GCUTBACT keyword in the SCHEDULE section that provides similar functionality for groups.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"RATE_CUTBACK","description":"","units":{},"default":"1","value_type":"DOUBLE"},{"index":3,"name":"PHASE","description":"","units":{},"default":"","value_type":"STRING"},{"index":4,"name":"WORKOVER_REMOVE","description":"","units":{},"default":"NO","value_type":"STRING"}],"example":"","expected_columns":4,"size_kind":"list"},"WCYCLE":{"name":"WCYCLE","sections":["SCHEDULE"],"supported":null,"summary":"The WCYCLE keyword defines automatic well opening and closing cycling parameters. These are used to model for example “Huff and Puff” cyclic steam injection in heavy oil reservoirs or Water-Alternating-Gas (“WAG”) processes in enhanced oil recovery modeling. The keyword defines specific time periods for automatically cycling wells on and off. For example in a WAG scheme the water injection wells would have one set of cycling parameters and the gas injection wells another, such that only one type of well is active at a time.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well automatic cycling parameters are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"ON_TIME","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Time"},{"index":3,"name":"OFF_TIME","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Time"},{"index":4,"name":"ONTIME","description":"A real positive value that defines the length of time for the on period. The well will be turned off at the beginning of the first time step after the on period has elapsed. If ONTIME is zero or negative then the well will not be turned on by the automatic well cycling.","units":{"field":"day","metric":"day","laboratory":"hour"},"default":"0.0","value_type":"DOUBLE","dimension":"Time"},{"index":5,"name":"OFFTIME","description":"A real positive value that defines the length of time for the off period. If the well was turned off by automatic cycling then it will be turned on at the beginning of the first time step after the off period has elasped. If the well was turned off other than by automatic cycling then the well will remain turned off. If OFFTIME is zero or negative then the well will not be turned on by the automatic well cycling.","units":{"field":"day","metric":"day","laboratory":"hour"},"default":"0.0","value_type":"DOUBLE","dimension":"Time"},{"index":6,"name":"STARTTIME","description":"A real positive value that defines the length of time for the start-up period during which the well efficiency factor will be ramped up. The start-up period begins at the start of the on period. The well’s efficiency factor is ramped up linearly from zero at the start of the on period to the value specified previously by the WEFAC keyword after the start-up period has elasped. The well efficiency factor to apply during each time step is linearly interpolated based on the time at the end of the time step. If the time step size is small compared with STARTTIME then the rate will be ramped up gradually. Whereas, if the time step size is greater than STARTTIME then the rate will ramp up instantaneously potentially causing convergence problems.","units":{"field":"day","metric":"day","laboratory":"hour"},"default":"0.0","value_type":"STRING"},{"index":7,"name":"MAXTS","description":"A real positive value that defines the maximum time step length when the well is turned on by automatic cycling. This overrides the standard maximum time step length. This can help to reduce potential convergence problems caused when a high rate well is opened. If MAXTS is zero then the standard maximum time step length applies.","units":{"field":"day","metric":"day","laboratory":"hour"},"default":"0.0"},{"index":13,"name":"CTRLTS","description":"A defined character string that specifies whether the time steps should be controlled to coincide exactly with the automatic cycling times for this well. CTRLTS should be set to one of the following: YES: time steps are controlled to coincide exactly with the automatic cycling times for this well. Note this will exactly match the specified on and off periods for this well. However, this is likely to reduce the time step size, especially if this option is set for a number automatic cycling wells that have different parameters. NO: time steps are not controlled to coincide exactly with the automatic cycling times for this well. Note this is unlikely to match the specified on and off periods for this well unless they coincide with the report steps. The next period will start at the next time step after the current on/off period has elasped. Therefore, the on/off periods are likely to be longer than specified.","units":{},"default":"NO"}],"example":"The following example defines the cycle lengths for a Water-Alternating-Gas injection scheme with a water-gas slug length ratio of 1:2, and initiates automatic cycling in the water injection well. A maximum time step of 5 days has been specified following the start of each injection period. The simulation then proceeds to the end of the first water injection cycle when automatic cycling is initiated in the gas injection well.\n--\n-- AUTOMATIC CYCLING OF WELLS ON AND OFF\n--\nWCYCLE\n--WELL ON OFF STARTUP STARTUP CTRL\n--NAME PERIOD PERIOD TIME MAXTS TIMESTEP\nI01W 30.0 60.0 1* 5.0 YES /\nI01G 60.0 30.0 1* 5.0 YES /\n--\n-- OPEN WELLS\n--\nWELOPEN\n--WELL OPEN\n--NAME SHUT\nI01W OPEN /\nI01G SHUT /\n/\n--\n-- REPORT STEPS\n--\nTSTEP\n30.0 /\n--\n-- OPEN WELLS\n--\nWELOPEN\n--WELL OPEN\n--NAME SHUT\nI01G OPEN /\n/\nNote that the wells initially need to be opened manually in order to start the automatic cycling. In addition, this needs to be done at the correct times to ensure that the water and gas injection wells are syncronised.","expected_columns":6,"size_kind":"list"},"WDFAC":{"name":"WDFAC","sections":["SCHEDULE"],"supported":null,"summary":"The WDFAC keyword defines a gas well’s D-factor (flow dependent skin factor), which is normally derived from well tests or calculated analytically based on the coefficient of inertial resistance, usually known as β, in Forchheimer’s flow equation,1\n Geertsma, J., 1974. Estimating the Coefficient of Inertial Resistance in Fluid Flow Through Porous Media. Soc.Pet.Eng.J., October: 445-450., 2\n Gewers, C.W.W. and Nichol, L.R., 1969. Gas Turbulence Factor in a Microvugular Carbonate. J.Can.Pet.Tech., April.and 3\n Wong, S.W., 1970. Effects of Liquid Saturation on Turbulence Factors for Gas Liquid Systems. J.Can.Pet.Tech., October.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well D-factor is being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"DFACTOR","description":"A real positive value greater than or equal to zero that defines the D-factor for the well.","units":{"field":"day/Mscf","metric":"day/m3","laboratory":"hour/scc"},"default":"0.0","value_type":"DOUBLE","dimension":"Time/GasSurfaceVolume"}],"example":"--\n-- WELL D-FACTORS\n--\n-- WELL D-\n-- NAME FACTOR\nWEFAC\nGP01 1.0E-03 /\n/\nIn the above example a well D-factor of 10-3 is specified for gas well GP01.","expected_columns":2,"size_kind":"list"},"WDFACCOR":{"name":"WDFACCOR","sections":["SCHEDULE"],"supported":null,"summary":"WDFACCOR keyword defines the parameters to calculate a gas well’s connection D-factors (flow dependent skin factor) for each connection based on a correlation for the coefficient of inertial resistance, usually known as β, in Forchheimer’s flow equation1\n Dake, L.P. Fundamentals of Reservoir Engineering, Amsterdam, The Netherlands, Elsevier Science BV (1978) Chapter 8.6, pages 252-257.,2\n Geertsma, J., 1974. Estimating the Coefficient of Inertial Resistance in Fluid Flow Through Porous Media. Soc.Pet.Eng.J., October: 445-450., 3\n Gewers, C.W.W. and Nichol, L.R., 1969. Gas Turbulence Factor in a Microvugular Carbonate. J.Can.Pet.Tech., April.and 4\n Wong, S.W., 1970. Effects of Liquid Saturation on Turbulence Factors for Gas Liquid Systems. J.Can.Pet.Tech., October. This keyword uses Dake’s correlation to calculate the D-factor.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well D-factor correlation is being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"A","description":"A real value greater than or equal to zero that defines the coefficient A in the D-factor correlation.","units":{"field":"cP.day.ft2/mD/Mscf","metric":"cP.day.m2/mD/sm3","laboratory":"cP.hour.cm2/mD/scc"},"default":"0.0","value_type":"DOUBLE","dimension":"Viscosity*Time*Area/Permeability*GasSurfaceVolume"},{"index":3,"name":"B","description":"A real value that defines the exponent B of the grid block permeability in the D-factor correlation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.0","value_type":"DOUBLE","dimension":"1"},{"index":4,"name":"C","description":"A real value that defines the exponent C of the grid block porosity in the D-factor correlation.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.0","value_type":"DOUBLE","dimension":"1"}],"example":"In the first example the connection D-factors for gas well GP01 are evaluated for correlation coefficients specified in field units based on the laboratory determined relationship between β and the absolute permeability presented by Dake in Fig. 8.8 (variation of β with porosity has been neglected).\n--\n-- WELL D-FACTOR CORRELATIONS\n--\n-- WELL\n-- NAME A B C\nWEFAC\nGP01 6.04E-05 -1.1045 0.0 /\n/\nIn the second example the same correlation coefficients are specified in metric units.\n--\n-- WELL D-FACTOR CORRELATIONS\n--\n-- WELL\n-- NAME A B C\nWEFAC\nGP01 1.20E-07 -1.1045 0.0 /\n/\n| [D``=``A K_e^B %phi^C K_e over h 1 over r_w { %gamma_g } over { %mu_g }] | (12.3.260.1) |\n|--------------------------------------------------------------------------|--------------|","expected_columns":4,"size_kind":"list"},"WDRILPRI":{"name":"WDRILPRI","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, WDRILPRI, adds wells to the Drilling Priority Drilling Queue and defines the well priority and drilling unit number or batch queue sequence for the well. The batch queue sequence number enables all wells with the same sequence number to drilled at the same time.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"PRIORITY","description":"","units":{},"default":"-1","value_type":"DOUBLE"},{"index":3,"name":"DRILLING_UNIT","description":"","units":{},"default":"0","value_type":"INT"}],"example":"","expected_columns":3,"size_kind":"list"},"WDRILRES":{"name":"WDRILRES","sections":["SCHEDULE"],"supported":false,"summary":"The WDRILRES keyword activates the prevention of multi-completions being completed in the same cell for wells in a drilling queue. Setting this option stops any well defined as a queued well via the QDRILL and WDRILLPRI keywords in the SCHEDULE section, or any wells set to automatic opening by setting the STATUS variable to AUTO on the WCONPROD keyword in the RUNSPEC section, from opening if there is an already existing active well connection to a cell.","parameters":[],"example":"","size_kind":"none","size_count":0},"WDRILTIM":{"name":"WDRILTIM","sections":["SCHEDULE"],"supported":false,"summary":"WDRILTIM defines the automatic drilling parameters used to describe the numbers of days taken to drill a well, the drilling status of the well, and status of other wells when drilling an automatically drilled well.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"DRILL_TIME","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Time"},{"index":3,"name":"WORKOVER_CLOSE","description":"","units":{},"default":"","value_type":"STRING"},{"index":4,"name":"COMPARTMENT","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":4,"size_kind":"list"},"WECON":{"name":"WECON","sections":["SCHEDULE"],"supported":true,"summary":"The WECON keyword defines the economic criteria for production wells that have previously been defined by the WELSPECS and WCONPROD keywords in the SCHEDULE section.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well economic criteria data is being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"ORAT","description":"A real positive value that defines the minimum economic surface oil production rate, below which an economic action will take place, as outlined below: If there are any remaining connections in the well with the STATUS variable set to AUTO on the COMPDAT keyword in the SCHEDULE section, then one of these connections (or completion) will be opened. If there are no remaining connections in the well with the STATUS variable set to AUTO on the COMPDAT keyword, then the well will be shut or stopped as requested by item (9) of the WELSPECS keyword. Only option (2) is supported by OPM Flow as STATUS equals AUTO on the COMPDAT keyword is currently not supported by the simulator. Hence, the well be either shut or stopped. A value less than or equal to zero switches off this criterion. This value may be specified using a User Defined Argument (UDA).","units":{"field":"stb/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"0.0","value_type":"UDA","dimension":"LiquidSurfaceVolume/Time"},{"index":3,"name":"GRAT","description":"A real positive value that defines the minimum economic surface gas production rate, below which an economic action will take place, as outlined below: If there are any remaining connections in the well with the STATUS variable set to AUTO on the COMPDAT keyword in the SCHEDULE section, then one of these connections (or completion) will be opened. If there are no remaining connections in the well with the STATUS variable set to AUTO on the COMPDAT keyword, then the well will be shut or stopped as requested by item (9) of the WELSPECS keyword. Only option (2) is supported by OPM Flow as STATUS equals AUTO on the COMPDAT keyword is currently not supported by the simulator. Hence, the well be either shut or stopped. A value less than or equal to zero switches off this criterion. This value may be specified using a User Defined Argument (UDA).","units":{"field":"Mscf/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"0.0","value_type":"UDA","dimension":"GasSurfaceVolume/Time"},{"index":4,"name":"WCUT","description":"A real positive value that defines the maximum economic surface water cut, above which an economic action will take place. This value may be specified using a User Defined Argument (UDA). Water cut is defined as:[f sub w ~=~ {q sub w } over {q sub w `+` q sub o}], and the various actions that are available if the water cut limit is exceeded are described in item (7)., and the various actions that are available if the water cut limit is exceeded are described in item (7). A value less than or equal to zero switches off this criterion.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.0","value_type":"UDA"},{"index":5,"name":"GOR","description":"A real positive value that defines the maximum economic surface gas-oil ratio, above which an economic action will take place, as defined by item (7). A value less than or equal to zero switches off this criterion. This value may be specified using a User Defined Argument (UDA).","units":{"field":"Mscf/stb","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"0.0","value_type":"UDA","dimension":"GasSurfaceVolume/LiquidSurfaceVolume"},{"index":6,"name":"WGR","description":"A real positive value that defines the maximum economic surface water-gas ratio, above which an economic action will take place, as defined by item (7). A value less than or equal to zero switches off this criterion. This value may be specified using a User Defined Argument (UDA).","units":{"field":"stb/Mscf","metric":"sm3/sm3","laboratory":"scc/scc"},"default":"0.0","value_type":"UDA","dimension":"LiquidSurfaceVolume/GasSurfaceVolume"},{"index":7,"name":"ACTION","description":"A defined character string that defines the action to be taken if the economic WCUT, GOR, or WGR limits are violated. ACTION should be set to one of the following character strings: NONE: no action is taken. CON: close the worst offending connection. If connections have been grouped as completions then the worst offending completion will be closed. +CON: close the worst offending connection and all below it. If connections have been grouped as completions then the worst offending completion and all below it will be closed. WELL: shut or stop the well as per the AUTO variable on the WELSPECS keyword. The corrective action takes places at the end of the time step in which the constraint is violated. The +CON option is not currently supported by OPM Flow.","units":{},"default":"NONE","value_type":"STRING","options":["NONE","CON","WELL"]},{"index":8,"name":"END","description":"A defined character string that defines if the simulation should terminate if the well is shut or stopped. END should be set to one of the following character strings: NO: no action is taken and the run continues. YES: terminate the run at the next report time step. The YES option is not currently supported by OPM Flow.","units":{},"default":"NO","value_type":"STRING","options":["NO","YES"]},{"index":9,"name":"WELOPEN","description":"A character string of up to eight characters in length that defines the name of the well, which will be opened when the current well (WELNAME) has been automatically closed/shut by the simulator. Wells closed manually do not invoke this opton. The well name (WELOPEN) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":10,"name":"ELTOPT","description":"A defined character string that defines the type of quantity used to test the economic limit, and should be set to one of the following character strings: POTN: The Economic Limit Test (“ELT”) is based on a well’s potential rate. A well’s potential rate is calculated using only the flowing bottom-hole pressure and tubing head pressure constraints, all other constraints are ignored, including group constraints. However, if the WELDRAW keyword in the SCHEDULE section has been used to limit a well’s pressure draw down, then this will also be considered in the potential calculation, as it influences the bottom-hole pressure constraint. RATE: The economic limit is based a well’s surface production rate as oppose to the potential rate, this is the default behavior. Wells under group control via the GCONPROD keyword in the SCHEDULE section will be subject to the ELT, except for when the group’s production target rate is set to zero. Wells under group control via the GCONPRI keyword in the SCHEDULE section will be subject to the ELT, except for when the group has curtailed a well’s production.","units":{},"default":"RATE","value_type":"STRING"},{"index":11,"name":"WCUT2","description":"A real positive value that defines the secondary maximum economic surface water cut, above which an economic action will take place. A value less than or equal to zero switches off this criterion. This item is not supported by OPM Flow and should be defaulted (1*) or set to zero.","units":{},"default":"0.0","value_type":"DOUBLE"},{"index":12,"name":"ACTION2","description":"A defined character string that defines the action to be taken if the secondary economic WCUT2 limits is violated. This item is not supported by OPM Flow and should be defaulted (1*).","units":{},"default":"1*","value_type":"STRING"},{"index":13,"name":"GLR","description":"A real positive value that defines the maximum economic surface gas-liquid ratio, above which an economic action will take place, as defined by item (7). A value less than or equal to zero switches off this criterion. This item is not supported by OPM Flow and should be defaulted (1*).","units":{},"default":"None","value_type":"DOUBLE"},{"index":14,"name":"LRAT","description":"A real positive value that defines the minimum liquid rate, below which the well (WELNAME) is shut-in. This item is not supported by OPM Flow and should be defaulted (1*).","units":{},"default":"0.0","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time"},{"index":15,"name":"TEMP","description":"A real positive value that defines the maximum economic temperature in the commercial compositional Thermal/Temperature model for a well. This item is not supported by OPM Flow and should be defaulted (1*).","units":{},"default":"None","value_type":"DOUBLE","dimension":"Temperature"},{"index":16,"name":"RESV","description":"A real positive value that defines the minimum reservoir volume rate, below which the well (WELNAME) is shut-in. This item is not supported by OPM Flow and should be defaulted (1*).","units":{},"default":"0.0","value_type":"DOUBLE","dimension":"ReservoirVolume/Time"}],"example":"The following example defines one oil well and one gas well using the WELSPECS keyword, together with their economic criteria.\n--\n-- WELL SPECIFICATION DATA\n--\n-- WELL GROUP LOCATION BHP PHASE DRAIN INFLOW SHUT CROSS PRESS\n-- NAME NAME I J DEPTH FLUID AREA EQUA. IN FLOW TABLE\nWELSPECS\nGP01 PLATFORM 14 13 1* GAS 1* GPP SHUT NO 1* /\nOP01 PLATFORM 28 96 1* OIL 1* STD SHUT NO 1* /\n/\n--\n-- WELL ECONOMIC CRITERIA FOR PRODUCTION WELLS\n-- WELL MIN MIN MAX MAX MAX CNTL END\n-- NAME ORAT GRAT WCUT GOR WGR MODE RUN\nWECON\nGP01 1* 5.0E3 1* 1* 1* 'WELL' 'NO' /\nOP01 500 1* 0.95 15 1* 'WELL' 'YES' /\n/\nWell GP01 has a minimum economic gas rate of 5 MMscf/d and will shut-in if the gas rate falls below this rate, but the simulation will continue even if this occurs. Well OP01 has a minimum economic oil rate of 500 stb/d, a maximum water cut limit of 95%, and a maximum GOR of 15 Mscf/stb, if any any of these limits are violated the well will be shut-in and the run should be terminated at the next reporting time step, however the option to end the run is not currently supported by OPM Flow.","expected_columns":16,"size_kind":"list"},"WECONINJ":{"name":"WECONINJ","sections":["SCHEDULE"],"supported":false,"summary":"The WECONINJ keyword defines economic criteria for injection wells that have previously been defined by the WELSPECS and WCONINJE keywords in the SCHEDULE section.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well economic injection criteria data is being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"MINVALUE","description":"A real positive value that defines the minimum economic injection value, below which an economic action will take place, as defined by the AUTO parameter on the WELSPECS keyword (SHUT or STOP). Note that TYPE determines if the minimum value is applied to the well’s actual injection rate or the well’s potential. A value less than or equal to zero switches off this criterion.","units":{"field":"Liquid stb/d Gas Mscf/d","metric":"Liquid sm3/day Gas sm3/day","laboratory":"Liquid scc/hour Gas scc/hour"},"default":"0.0","value_type":"DOUBLE"},{"index":3,"name":"TYPE","description":"A defined character string that determines if MINVALUE is applied to a well’s actual rate or potential, and should be set to one of the following: RATE: In this case the MINVALUE is applied to a well’s actual rate. POTN: Here, MINVALUE is applied to the well’s potential with only the BHP and THP constraints applied. The default value is RATE.","units":{},"default":"RATE","value_type":"STRING"}],"example":"The following example defines the economic injection parameters for all gas and water injection wells.\n--\n-- WELL ECONOMIC LIMIT DATA FOR INJECTION WELLS\n--\n-- WELL MIN RATE\n-- NAME VALUE POTN\nWECONINJ\nGI* 2.0E3 RATE /\nWI* 5.0E3 POTN /\n/\nHere all the gas injection wells have a minimum economic gas injection rate of 2 MMscf/d and the water injection wells have a minimum water potential rate of 5,000 stb/d. The AUTO parameter on the WELSPECS keyword will determine if the wells will be shut-in or stopped.","expected_columns":3,"size_kind":"list"},"WECONT":{"name":"WECONT","sections":["SCHEDULE"],"supported":false,"summary":"The WECONT keyword defines the tracer economic criteria for production wells that have previously been defined by the WELSPECS and WCONPROD keywords in the SCHEDULE section, for tracers define by the TRACER keyword in the PROPS section.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well target and constraints are being defined.","units":{},"default":"None","record":1,"value_type":"STRING"},{"index":1,"name":"NAME","description":"A three letter character string defining the tracer’s name. Note it is best to void names beginning with the letters F, S, and T as these names may create naming issues in post-processing software.","units":{},"default":"None","record":2,"value_type":"STRING"},{"index":2,"name":"ACTION","description":"A defined character string that defines the action to be taken if the economic WCUT, GOR, or WGR limits are violated. ACTION should be set to one of the following character strings: NONE: no action is taken. CON: close the worst offending connection in the worst offending. If connections have been welled as completions then the worst offending completion will be closed. +CON: close the worst offending connection and all below it in the worst offending well. If connections have been welled as completions then the worst offending completion and all below it in the worst offending well will be closed. WELL: shut or stop the well as per the AUTO variable on the WELSPECS keyword. PLUG: plug back the worst offending well based on the plug back length and options defined on the WPLUG keyword in the SCHEDULE. The corrective action takes places at the end of the time step in which the constraint is violated.","units":{},"default":"None","record":1,"value_type":"STRING","options":["NONE","CON","WELL","PLUG"]},{"index":2,"name":"MXTOTAL","description":"A real positive value that defines the maximum total (free plus solution) tracer rate. Tracer units are per those defined by the carrying fluid, oil, gas, water, etc.","units":{},"default":"None","record":2,"value_type":"STRING"},{"index":3,"name":"END","description":"A defined character string that defines if the simulation should terminate if the well is shut or stopped. END should be set to one of the following character strings: NO: no action is taken and the run continues. YES: terminate the run at the next report time step.","units":{},"default":"NO","record":1,"value_type":"STRING","options":["NO","YES"]},{"index":3,"name":"MXFREET","description":"A real positive value that defines the maximum total (free plus solution) tracer concentration. Tracer units are per those defined by the carrying fluid, oil, gas, water, etc.","units":{},"default":"None","record":2,"value_type":"STRING"},{"index":4,"name":"WELL","description":"A character string of up to eight characters in length that defines the well name of a fully defined well that will be “opened” when the well WELNAME is shut-in or stopped.","units":{},"default":"None","record":1,"value_type":"STRING"},{"index":4,"name":"MXFREEQ","description":"A real positive value that defines the maximum free tracer rate. Tracer units are per those defined by the carrying fluid, oil, gas, water, etc.","units":{},"default":"None","record":2,"value_type":"STRING"},{"index":5,"name":"MXCONC","description":"A real positive value that defines the maximum free tracer concentration. Tracer units are per those defined by the carrying fluid, oil, gas, water, etc.","units":{},"default":"None","record":2},{"index":6,"name":"MXSOLNQ","description":"A real positive value that defines the maximum solution rate. Tracer units are per those defined by the carrying fluid, oil, gas, water, etc.","units":{},"default":"None","record":2},{"index":7,"name":"MXSOLNC","description":"A real positive value that defines the maximum solution concentration. Tracer units are per those defined by the carrying fluid, oil, gas, water, etc.","units":{},"default":"","record":2}],"example":"The following example defines the tracer economic criteria for the field and two wells, OP01 and OP02.\n--\n-- WELL TRACER ECONOMIC CRITERIA FOR PRODUCTION WELLS\n--\n-- WELL WORK END MAX\n-- NAME OVER RUN WELLS\nWECONT\nOP01 +CON 'YES' 1* / START OF WELL\n--\n-- TRACER TRACER TRACER TRACER TRACER TRACER TRACER\n-- NAME TOTAL TOTAL FREE FREE SOLN SOLN\n-- RATE CONCEN RATE CONCEN RATE CONCEN\nPLY 800.0 /\nBRI 800.0 /\n/\nOP02 +CON 'YES' 1* / START OF WELL\n--\n-- TRACER TRACER TRACER TRACER TRACER TRACER TRACER\n-- NAME TOTAL TOTAL FREE FREE SOLN SOLN\n-- RATE CONCEN RATE CONCEN RATE CONCEN\nPLY 800.0 /\nBRI 800.0 / END OF WELL\n/ END OF KEYWORD\nIf the economic limits are violated then the worst offending connection and all below it in the worst offending well will be closed, If connections have been grouped as completions then the worst offending completion and all below it in the worst offending well will be closed","expected_columns":4,"size_kind":"list"},"WEFAC":{"name":"WEFAC","sections":["SCHEDULE"],"supported":null,"summary":"Defines a well’s efficiency or up-time as opposed to setting the efficiency at the group level.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well efficiency factor is being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"FACTOR","description":"A real positive value greater than zero and less than or equal to one that defines the efficiency factor for the well. If a well’s down time is 5% then FACTOR should be set to 0.95 (1.0 – 0.05). Note that well pressures and rates are calculated at their full flowing conditions but subject to any operating constraints, that is without the well efficiency being applied (FACTOR), in order to represent the actual flowing conditions in the field. The effective rates and volumes are calculated by applying FACTOR when summing individual well rates to their group level and higher, including summing to the top most group FIELD. In terms of a well’s cumulative production, FACTOR is applied to the well rate times the time interval for the time step. This ensures that correct effective volume is withdrawn from (or injected to) the reservoir. This approach means that wells are effectively arbitrarily offline for a period during a time step, as opposed to all wells going offline concurrently. And thus the group and field rates and volumes are the effective rates and volumes for the field.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0","value_type":"DOUBLE"},{"index":3,"name":"WELNETWK","description":"A defined character string that determines if the WELNAME efficiency factor should be applied when calculating the flows and pressure losses in the Extended Network Model, and should be set to either: NO: The well’s equivalent Extended Network Model node flow rates are not multiplied by the efficiency factor FACTOR. YES: The well’s equivalent Extended Network Model node flow rates are multiplied by the efficiency factor FACTOR This option is only applicable for the Extended Network Model, as in the Standard Network Model groups flow rates are always used in the calculation of pressure drops (this is equivalent to the default option, YES).","units":{},"default":"YES","value_type":"STRING"}],"example":"--\n-- WELL EFFICIENCY FACTORS\n--\n-- WELL EFF NETWK\n-- NAME FACT OPTN\nWEFAC\n'GP* ' 0.950 /\n'OP* ' 0.862 /\n/\nIn the above example the all the gas wells are are defined as having a well efficiency factor (up time) of 0.950 and all the oil wells have a lower efficiency factor of 0.862.\n| Note One can also apply plant efficiencies through the GEFAC keyword in the SCHEDULE section. If all the wells in a group are flowing through a facility that has an overall efficiency factor, then it is more appropriate to apply the efficiency factor at the group level. This of course does not preclude applying additional well efficiencies to individual wells. For example, subsea wells (wet trees) may have additional down time compared to platform wells (dry trees) even though both sets of well are flowing through the same platform. Another example would be gas lift wells and wells using electrical submersible pumps, as their artificial lift mechanisms. |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":3,"size_kind":"list"},"WELCNTL":{"name":"WELCNTL","sections":["SCHEDULE"],"supported":false,"summary":"The WELCNTL keyword modifies a well’s target control and value, both rates and pressures, for previously defined wells without having to define all the variables on the well control keywords: WCONPROD, WCONHIST, WCONINJE, or WCONINJH keywords. Variables not changed by the WELCNTL keyword remain the same as those previously entered via the well control keywords or previously entered WELCNTL keywords. Note that the well must still be initially be fully defined using the WCONPROD or WCONINJE keywords. All the aforementioned keywords are described in the SCHEDULE section.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well production rates and pressures data are being redefined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS and WCONPROD (or WCONINJE) keywords in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"TARGET","description":"A defined character string that sets the item to be changed for the well the value of the item is set by item (3). ORAT: reset the surface oil production rate value as defined by item (3). WRAT: reset the surface water production rate value as defined by item (3). GRAT: reset the surface gas production rate value as defined by item (3). LRAT: reset the surface liquid (oil plus water) production rate value as defined by (3). RESV: reset he in situ reservoir volume rate value as defined by (3). BHP: reset the bottom-hole pressure value as defined by item (3). THP: reset the tubing head pressure value for the well as defined by item (3). VFP: reset the vertical lift performance table number as defined by (3). LIFT: reset the artificial lift quantity for use with vertical lift performance tables. GUID: reset the guide rate value for wells operating under group control. Note TARGET redefines the target controlled for a well and the control value on item (4). For example, if a well is operating on ORAT control, as defined by the previously entered WCONPROD keyword, entering TARGET equal to LRAT with a value, sets the TARGET to liquid rate with the given value. That is the well will be targeting a liquid rate not the previously requested oil ratel. Use the WELTARG keyword in the SCHEDULE section to change the target and constraint values for a well.","units":{},"default":"None","value_type":"STRING","options":["ORAT","WRAT","GRAT","LRAT","RESV","BHP","THP","VFP","LIFT","GUID"]},{"index":3,"name":"VALUE Liquid Gas Res Vol Pressure VFP LIFT","description":"A real positive value that defines the value of the variable declared by TARGET","units":{"field":"stb/d Mscf/d rb/d psia dimensionless same as VFPPROD or VFPINJ","metric":"sm3/day sm3/day rm3/day barsa dimensionless same as VFPPROD or VFPINJ","laboratory":"scc/hour scc/hour rcc/hour atma dimensionless same as VFPPROD or VFPINJ"},"default":"None","value_type":"DOUBLE"}],"example":"The following example below shows the oil rates for the OP01 oil producer at the start of the schedule section (January 1, 2000).\n-- ------------------------------------------------------------------------------\n-- 01 JAN 2000 START OF SCHEDULE SECTION\n-- ------------------------------------------------------------------------------\n--\n-- WELL PRODUCTION WELL CONTROLS\n--\n-- WELL OPEN/ CNTL OIL WAT GAS LIQ RES BHP THP VFP VFP\n-- NAME SHUT MODE RATE RATE RATE RATE RATE PRES PRES TABLE ALFQ\nWCONPROD\nOP01 OPEN ORAT 3000 1* 1* 1* 1* 750.0 500. 9 1* /\n/ DATES\n01 FEB 2000 /\n/\n--\n-- WELL CONTROL MODE AND OPERATING TARGET\n--\n-- WELL WELL TARGET\n-- NAME CNTL VALUE WELCNTL\nOP01 LRAT 5000 /\n/\nFrom January 1, 2000 to February 1, 2000 well OP01 is open and is on oil rate control and has a target oil rate of 3,000 stb/d and uses VFPPROD vertical lift table number 9 with a minimum tubing head pressure constraint of 500 psia. After February 1, 2000 the well is changed to liquid control with a target rate of 5,000 stb/d of liquid and all the other parameters remain unchanged.","expected_columns":3,"size_kind":"list"},"WELDEBUG":{"name":"WELDEBUG","sections":["SCHEDULE"],"supported":false,"summary":"This keyword defines the well debug data to be written to the debug file (*.DBG). This keyword is not supported by OPM Flow but would change the results if supported so the simulation will be stopped.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"DEBUG_FLAG","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":2,"size_kind":"list"},"WELDRAW":{"name":"WELDRAW","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, WELDRAW, defines the maximum draw down for production wells The keyword may be useful in wells that are subject to fines or sand production to limit the draw down between the sand face and the well in order to limit or avoid sand production.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"MAX_DRAW","description":"","units":{},"default":"","value_type":"UDA","dimension":"Pressure"},{"index":3,"name":"PHASE","description":"","units":{},"default":"","value_type":"STRING"},{"index":4,"name":"USE_LIMIT","description":"","units":{},"default":"NO","value_type":"STRING"},{"index":5,"name":"GRID_BLOCKS","description":"","units":{},"default":"AVG","value_type":"STRING"}],"example":"","expected_columns":5,"size_kind":"list"},"WELEVNT":{"name":"WELEVNT","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, WELEVNT, defines an integer value to be assigned to an individual well’s WPWEM summary variable that is written to the SUMMARY file. The value is set to zero after the current time step.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"WPWEM_VALUE","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":2,"size_kind":"list"},"WELLSTRE":{"name":"WELLSTRE","sections":["SCHEDULE"],"supported":true,"summary":"The WELLSTRE keyword defines a well stream together with the compositional component mole factions, associated with the well stream, as such it should have the same number of entries as that declared via the COMPS keyword in the RUNSPEC section, and the NCOMPS keyword in the PROPS section. Once a gas well stream has been defined, it can be used with either the WINJGAS or GINJGAS keywords in the SCHEDULE section, to set the injected gas composition. Similarly, if an oil well stream has been defined by WELLSTRE, then the well stream can be used with the WINJOIL keyword in the SCHEDULE section, to specify the injected oil composition.","parameters":[{"index":1,"name":"STREAM","description":"STREAM is a character string of up to eight characters in length, representing the well stream name. The WELLDIMS(MXSTRMS) parameter in the RUNSPEC section determines the maximum number of well streams allowed in the model.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"ZCOMP","description":"A row vector, with each item representing a compositional component mole fraction for a given component. In addition, the sum of the compositional component mole fractions must sum to one, otherwise an error will occur. Note that the number ZCOMP values, should be the same as that entered via the NCOMPS keyword in the PROPS section, and the COMPS keyword in the RUNSPEC section. However, for a given ZCOMP component, the mole fraction may be defaulted with 1*, in which case the mole fraction is set to zero. Secondly, ZCOMP may be terminated early, in this case the undefined mole fractions will be set to zero. Finally, only the default value of two components are currently supported by OPM Flow.","units":{"field":"mole fraction","metric":"mole fraction","laboratory":"mole fraction"},"default":"None","value_type":"DOUBLE","dimension":"1"}],"example":"The following example defines how to specify a two component formulation, together with defining the names of the composition components, to be used with the CO2STORE and GASWAT options.\n-- ==============================================================================\n--\n-- PROPS SECTION\n--\n-- ==============================================================================\nPROPS --\n-- CONFIRM NUMBER OF COMPOSITIONAL COMPONENTS (OPM FLOW KEYWORD)\n--\nNCOMPS\n2 /\n--\n-- DEFINE COMPOSITIONAL COMPONENTS NAMES (OPM FLOW KEYWORD)\n--\nCNAMES\n'CO2'\n'H2O' /\nThe second part of the example, defines the well stream for the above two component CO2 water system.\n-- ==============================================================================\n--\n-- SCHEDULE SECTION\n--\n-- ==============================================================================\nSCHEDULE\n--\n-- WELL STREAM INJECTION COMPOSITION (OPM FLOW Keyword)\n--\n-- WELL -- WELL STREAM COMPOSITIONAL COMPONENT --\n-- STREAM -- MOLE FRACTIONS --\nWELLSTRE\n'C02STREAM' 1.000 0.000 /\n/\nHere the well stream consists of 100% CO2 and zero water.\n| Note This is an OPM Flow keyword used with OPM Flow’s CO2STORE and GASWAT keywords in the RUNSPEC section, and should not be confused with the more general version of the WELLSTRE keyword used in the commercial compositional simulator. Secondly, although OPM Flow parses the keyword, the simulator currently ignores the data for this keyword. |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","size_kind":"list","variadic_record":true},"WELMOVEL":{"name":"WELMOVEL","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, WELMOVEL, moves a previously defined gloabal well into a previously declared Local Grid Refinement (“LGR”), in a RESTART run. The keyword should only be used in RESTART runs.","parameters":[{"index":1,"name":"WELLNAME","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"LGRNAME","description":"","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"WELLHEAD_I","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"WELLHEAD_J","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":4,"size_kind":"list"},"WELOPEN":{"name":"WELOPEN","sections":["SCHEDULE"],"supported":null,"summary":"The WELOPEN keyword defines the status of wells and well connections, and is used to open and shut previously defined wells and well connections without having to re-specify all the data on the well control keywords: WCONPROD, WCONHIST, WCONINJE, or WCONINJH keywords. Note that the well must still be initially fully defined using the WCONPROD or WCONINJE keywords. All the aforementioned keywords are described in the SCHEDULE section.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well or well connection status data are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"STATUS","description":"A defined character string of length four that defines the well or well connection operational status, STATUS should be set to one of the following character strings: OPEN: the well or connections are open to flow. SHUT: the well or connections are closed to flow (shut-in). AUTO: the well or connections are initially closed, but may be opened automatically if an economic limit is violated.","units":{},"default":"OPEN","value_type":"STRING","options":["OPEN","SHUT","AUTO"]},{"index":3,"name":"I","description":"An integer less than or equal to NX that defines the connection location in the I-direction.","units":{},"default":"Negative","value_type":"INT"},{"index":4,"name":"J","description":"An integer less than or equal to NY that defines the connection location in the J-direction.","units":{},"default":"Negative","value_type":"INT"},{"index":5,"name":"K","description":"An integer less than or equal to NZ that defines the connection location in the K-direction.","units":{},"default":"Negative","value_type":"INT"},{"index":6,"name":"C1","description":"An integer less than or equal to the total number of completions that defines the first completion in the range.","units":{},"default":"Negative","value_type":"INT"},{"index":7,"name":"C2","description":"An integer less than or equal to the total number of completions that defines the last completion in the range.","units":{},"default":"Negative","value_type":"INT"}],"example":"The following example defines two vertical oil wells using the WELSPECS keyword and their associated connection data.\n-- WELL SPECIFICATION DATA\n--\n-- WELL GROUP LOCATION BHP PHASE DRAIN INFLOW SHUT CROSS PRESS\n-- NAME NAME I J DEPTH FLUID AREA EQUA. IN FLOW TABLE\nWELSPECS\nOP01 PLATFORM 14 13 1* OIL 1* STD OPEN NO 1* /\nOP02 PLATFORM 28 96 1* OIL 1* STD OPEN NO 1* /\n/\n--\n-- WELL PRODUCTION WELL CONTROLS\n--\n-- WELL OPEN/ CNTL OIL WAT GAS LIQ RES BHP THP VFP VFP\n-- NAME SHUT MODE RATE RATE RATE RATE RATE PRES PRES TABLE ALFQ\nWCONPROD\n‘*’ SHUT GRUP 1* 1* 1* 1* 1* 200.0 /\n/\n-- WELL CONNECTION DATA\n--\n-- WELL --- LOCATION --- OPEN SAT CONN WELL KH SKIN D DIR\n-- NAME II JJ K1 K2 SHUT TAB FACT DIA FACT FACT FACT PEN\nCOMPDAT\nOP01 1* 1* 1 10 SHUT 1* 1* 0.708 1* 0.0 1* 'Z' /\nOP01 1* 1* 15 30 SHUT 1* 1* 0.708 1* 0.0 1* 'Z' /\nOP01 1* 1* 35 90 SHUT 1* 1* 0.708 1* 0.0 1* 'Z' /\nOP02 1* 1* 1 10 SHUT 1* 1* 0.708 1* 0.0 1* 'Z' /\n/\n--\n-- DEFINE WELL AND WELL CONNECTIONS FLOWING STATUS\n--\n-- WELL WELL --LOCATION-- COMPLETION\n-- NAME STAT I J K FIRST LAST\nWELOPEN\nOP01 OPEN /\nOP01 OPEN 0 0 1 /\nOP01 OPEN 0 0 2 /\nOP01 OPEN 0 0 3 /\nOP01 OPEN 0 0 4 /\nOP02 OPEN /\nOP02 OPEN 0 0 0 /\n/\nIn this example the first record for each well in the WELOPEN keyword changes the well status from shut (as per the WCONPROD keyword) to open. Then for well OP01 well connections in layers one to four are opened for flow and all the connections for well OP02 are opened, that is the connections in layers one to ten.\nThe next example shows the use of the COMPLUMP keyword to group the well connections into well completions for wells OP01, OP02 and OP03, and then use the WELOPEN keyword to open the well and the well completions.\n--\n-- ASSIGN WELL CONNECTIONS TO COMPLETIONS\n--\n-- WELL --- LOCATION --- COMPL\n-- NAME II JJ K1 K2 NO.\nCOMPLUMP\nOP01 0 0 1 10 1 / COMPLETION NO. 01\nOP01 0 0 15 30 2 / COMPLETION NO. 02\nOP01 0 0 35 90 3 / COMPLETION NO. 03\nOP02 0 0 15 30 2 / COMPLETION NO. 02\nOP02 0 0 35 90 3 / COMPLETION NO. 03\nOP03 0 0 1 10 1 / COMPLETION NO. 01\nOP03 0 0 35 90 3 / COMPLETION NO. 03\n/\n--\n-- DEFINE WELL AND WELL CONNECTIONS FLOWING STATUS\n--\n-- WELL WELL --LOCATION-- COMPLETION\n-- NAME STAT I J K FIRST LAST\nWELOPEN\nOP01 OPEN /\nOP01 OPEN 0 0 0 3 3 /\nOP02 OPEN /\nOP02 OPEN 0 0 0 2 2 /\nOP03 OPEN /\nOP03 OPEN 0 0 0 0 0 /\n/\nAgain, the first record of each well WELOPEN keyword changes the well status from shut (as per the WCONPROD keyword) to open. Then for well OP01 well completion number three is opened (connections 35 to 90), completion two (connections 15 to 30) for well OP02 and completion numbers one to three (all the connections) for well OP03. Note that there is no completion number two for OP03 so connections 15 to 30 will not be opened.\nNote the last completion number for well OP03 was named completion number three, but it could have been named number two as well. The reason why it was named number three instead of two was because it was assumed (for the example) that layers 35 to 90 represent a particular reservoir, and therefore allowing for the tracking of completions for individual reservoirs, as shown in the example.\nThis example shows how one can open all the wells and well completions for a given reservoir.\n--\n-- DEFINE WELL AND WELL CONNECTIONS FLOWING STATUS\n--\n-- WELL WELL --LOCATION-- COMPLETION\n-- NAME STAT I J K FIRST LAST\nWELOPEN\n‘*’ OPEN /\n‘*’ OPEN 0 0 0 3 3 /\nOP02 SHUT 0 0 0 0 0 /\nOP02 OPEN 0 0 0 2 2 /\n/\nIn this case wells OP01, OP02 and OP03 are opened via completion number three. All the connections for OP02 are then shut, and the connections associated with completion two are opened instead for this well.","expected_columns":7,"size_kind":"list"},"WELOPENL":{"name":"WELOPENL","sections":["SCHEDULE"],"supported":false,"summary":"The WELOPENL keyword defines the status of wells and well connection in Local Grid Refinement Grids (“LGR”) and is used to open and shut previously defined well and well connections without having to re-specify all the data on the well control keywords: WCONPROD, WCONHIST, WCONINJE, or WCONINJH keywords. Note that the well must still be initially be fully defined using the WCONPROD or WCONINJE keywords. All the aforementioned keywords are described in the SCHEDULE section","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well and well connection status data is being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"LGRNAME","description":"A character string of up to eight characters in length that defines the LGR name for which the well LGR connection data are being defined. Note that the well name (LGRNAME) must have been declared previously using the WELSPECL keyword in the SCHEDULE section, otherwise an error may occur. If defaulted with 1* the LGR on the WELSPECL keyword will be utilized.","units":{},"default":"Defined","value_type":"STRING"},{"index":3,"name":"STATUS","description":"A character string of length four that defines the well and a well’s connections’ operational status, STATUS should be set to one of the following character strings: OPEN: the connections are open to flow. SHUT: the connections are closed to flow (shut-in). AUTO: the connection are initially closed, but may be opened automatically if an economic limit is violated.","units":{},"default":"OPEN","value_type":"STRING","options":["OPEN","SHUT","AUTO"]},{"index":4,"name":"I","description":"An integer less than or equal to NX that defines the connection location in the I-direction.","units":{},"default":"1*","value_type":"INT"},{"index":5,"name":"J","description":"An integer less than or equal to NY that defines the connection location in the J-direction.","units":{},"default":"1*","value_type":"INT"},{"index":6,"name":"K","description":"An integer less than or equal to NZ that defines the connection location in the K-direction.","units":{},"default":"1*","value_type":"INT"},{"index":7,"name":"K1","description":"An integer less than or equal to NZ that defines the UPPER completion location in the K-direction. Connections are lumped into completions via the COMPLUMP keyword, and K1 refers to the first completion number, as defined by the COMPLUMP keyword, and all the connections contained within the K1 completion.","units":{},"default":"1*","value_type":"INT"},{"index":8,"name":"K2","description":"An integer less than or equal to NZ that defines the LOWER completion location in the K-direction. Connections are lumped into completions via the COMPLUMP keyword, and K2 refers to the last completion number, as defined by the COMPLUMP keyword, and all the connections contained within the K2 completion.","units":{},"default":"1*","value_type":"INT"}],"example":"The following example shows the use of the COMPLMPL keyword to group the well connections into well completions for well OP01 and then use the WELOPEN keyword to open the well and the well connections.\n--\n-- ASSIGN WELL LGR CONNECTIONS TO COMPLETIONS\n--\n-- WELL LGR ---LOCATION--- COMPL\n-- NAME NAME II JJ K1 K2 NO.\nCOMPLMPL\nOP01 LGR1 26 58 1 3 1 /\nOP01 LGR1 26 58 4 10 2 /\nOP01 LGR1 26 58 11 12 3 /\n/\n--\n-- WELL PRODUCTION STATUS FOR LGR WELLS\n--\n-- WELL LGR WELL --LOCATION-- COMPLETION\n-- NAME NAME STAT I J K FIRST LAST\nWELOPENL\nOP01 LGR1 OPEN /\nOP01 LGR1 OPEN 0 0 0 1 2 /\nOP01 LGR2 SHUT 0 0 0 3 3 /\n/\nThe first record of the WELOPENL keyword changes the well status from shut (as per the WCONPROD keyword) to open, in case it has been shut-in. Then well completion number one and two are opened (connections 1 to 10), and completion number three shut-in (connections 11 to 12).","expected_columns":8,"size_kind":"list"},"WELPI":{"name":"WELPI","sections":["SCHEDULE"],"supported":null,"summary":"The WELPI keyword is used to define a well’s productivity or injectivity index at the time the keyword is activated. Productivity and injectivity indices are a function of both bottom-hole pressure and mobility and thus will vary in time as the bottom-hole pressure and fluids produce by the well are changing. Thus, the values enter on this keyword for a given well will override any previously calculated values, or values previously entered, using this keyword. This keyword should only be invoked after a well’s connection factors have been declared via the COMPDAT keyword in the SCHEDULE section.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well productivity index is being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"WELPI","description":"A real positive value that defines the productivity or injectivity of a well at the time the keyword is activated in the input deck. Subsequent use of the keyword for a given well will override all previously entered data, including the original productivity index calculated from the well’s COMPDAT connection data. Note that: Only the connections currently opened will have their connection factors re-scaled to honor the productivity and injectivity index. Connections not opened will remain unchanged. Additional, previously defined connections added to the well at a later time, will not be influenced by a previous WELPI keyword. It may therefore be necessary to add another WELPI keyword at the time the new connections are opened, if desired. However, re-defining connections via the COMPDAT keyword resets the calculated productivity and injectivity index for those re-defined connections in the well. Subsequent usage of the keyword for the same well may lead to unintended values; use the WPI series of variables in the SUMMARY section to output and verify that the values are consistent with the desired results.","units":{"field":"Liquid stb/d/psia Gas Mscf/d/psia","metric":"Liquid sm3/day/bars Gas sm3/day/bars","laboratory":"Liquid scc/hour/atm Gas scc/hour/atm"},"default":"1.0","value_type":"DOUBLE"}],"example":"--\n-- DEFINE WELL PRODUCTIVITY/INJECTIVITY INDEX\n--\n-- WELL PI\n-- NAME MULT\nWELPI\nOP01 1.250 /\nOP02 2.750 /\nOP03 1.100 /\n/\nIn the above example the oil wells are are defined as having a well productivity indices of 1.250, 2.750 and 1.100 for the OP01, OP02 and OP03 wells, respectively.\n| Note One should not modify the productivity and injectivity index of gas wells that use: Russell Goodrich326\n Russell, D.G., Goodrich, J.H., Perry, G.E and Bruskotter, J.F \"Methods of Predicting Gas Well Performance\", Transactions of the ASME, Journal of Petroleum Technology (1966) 99-108. pressure square inflow equation, as declared via 'R-G' or 'YES' for the INFLOW parameter on the WELSPECS keyword in the SCHEDULE section, or Russell, D.G., Goodrich, J.H., Perry, G.E and Bruskotter, J.F \"Methods of Predicting Gas Well Performance\", Transactions of the ASME, Journal of Petroleum Technology (1966) 99-108. the general dry gas pseudo pressure inflow equation, as declared via 'P-P' for the INFLOW parameter on the WELSPECS keyword in the SCHEDULE section, or the generalized gas pseudo pressure inflow equation, as declared via 'GPP' for the INFLOW parameter on the WELSPECS keyword in the SCHEDULE section, or those gas wells that use the non-Darcy D factor coefficient, as declared by the DFACT property on the COMPDAT and WDFAC keywords in the SCHEDULE section. |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":2,"size_kind":"list"},"WELPRI":{"name":"WELPRI","sections":["SCHEDULE"],"supported":false,"summary":"The WELPRI keyword is used to re-assign a priority number to a well for when the PRIORITY keyword has been used in the SCHEDULE section. The PRIORITY keyword activates the Well Priority option and defines the coefficients in the well priority equation; WELPRI keyword can be used to over write these calculated priority numbers","parameters":[{"index":1,"name":"WELL_NAME","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"PRI1","description":"","units":{},"default":"-1","value_type":"INT"},{"index":3,"name":"SCALING1","description":"","units":{},"default":"1","value_type":"DOUBLE"},{"index":4,"name":"PRI2","description":"","units":{},"default":"-1","value_type":"INT"},{"index":5,"name":"SCALING2","description":"","units":{},"default":"1","value_type":"DOUBLE"}],"example":"","expected_columns":5,"size_kind":"list"},"WELSEGS":{"name":"WELSEGS","sections":["SCHEDULE"],"supported":false,"summary":"The WELSEGS keyword defines a well to be a multi-segment well and defines the well’s segment structure. Note that the well must have previously been defined by the WELSPECS keyword in the SCHEDULE section and that the WELSEGS keyword should be repeated for each multi-segment well in the model.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which a multi-segment well is being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","record":1,"value_type":"STRING"},{"index":2,"name":"TOPDEP","description":"A real value that defines the depth of the nodal point of the top segment. This is used as the reference depth for reporting the bottom-hole pressure for the multi-segment well. If the keyword is entered multiple times for the same well, due to for example the well configuration changing through time, then it is only necessary to enter this data the first time the keyword is used for a well.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","record":1,"value_type":"DOUBLE","dimension":"Length"},{"index":3,"name":"TOPLEN","description":"A real positive value that defines the length of the tubing from the tubing reference point (for example Measured Depth Relative to Kelly Bushing, MDRKB) to the nodal point of the top segment. Tubing pressures between the nodal point of the top segment and the well head are not calculated by the multi-segment well option as these are taken into account by the VFP tables allocated to the well and entered via the VFPPROD and VFPINJ keywords in the SCHEDULE section. If TOPLEN is set to zero or defaulted then the tubing length is measured from the nodal point of the top segment.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"0","record":1,"value_type":"DOUBLE","dimension":"Length"},{"index":4,"name":"WBORVOL","description":"A real positive value that defines the effective wellbore volume for the top segment, that is from the tubing head or wellhead at the surface to the nodal point of the top segment. The default value of 1.0 x 10-5 results in minimal wellbore storage.","units":{"field":"ft3","metric":"m3","laboratory":"cm3"},"default":"1.0E-5","record":1,"value_type":"DOUBLE","dimension":"Length*Length*Length"},{"index":5,"name":"TUBOPT","description":"A defined character string that specifies the type of length and depth data entered for LENGTH and DEPTH on the second record and should be set to one of the following: INC: Incremental changes in values of length and depth for each segment. ABS: Absolute values of length and depth for each segment. As there is no default value for TUBOPT one of the above options must be explicitly defined.","units":{},"default":"None","record":1,"value_type":"STRING"},{"index":6,"name":"PRESOPT","description":"A defined character string that specifies the pressure drop calculation used for each well segment and should be set to one of the following: HFA: Sets the pressure calculation to include the hydrostatic, friction and acceleration terms. HF-: Sets the pressure calculation to include the hydrostatic and friction terms only. H--: Sets the pressure calculation to include the hydrostatic pressure drop term only. The default value for PRESOPT of HFA sets the pressure calculation to include the hydrostatic, friction and acceleration terms.","units":{},"default":"HFA","record":1,"value_type":"STRING"},{"index":7,"name":"FLOWOPT","description":"A defined character string that specifies the type of multi-phase calculation used for each well segment and should be set to one of the following: HO: Sets the multi-phase calculation to the homogeneous model, that is all phases flow at the same velocity. DF-: Sets the multi-phase calculation to the Drift Flux Slip model. OPM Flow only supports the default value of HO.","units":{},"default":"HO","record":1,"value_type":"STRING"},{"index":8,"name":"TOPX","description":"A real positive value equal to or greater than zero that defines the coordinate in the x-direction of the nodal point of the top segment that is used for display purposes only. Currently this option is not supported by OPM Flow.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","record":1,"value_type":"DOUBLE","dimension":"Length"},{"index":9,"name":"TOPY","description":"A real positive value equal to or greater than zero that defines the coordinate in the y-direction of the nodal point of the top segment that is used for display purposes only. Currently this option is not supported by OPM Flow.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","record":1,"value_type":"DOUBLE","dimension":"Length"},{"index":10,"name":"XAREATH","description":"A real positive value equal to or greater than zero that defines the cross-sectional area of the pipe wall used in thermal conductivity calculations for when the temperature calculation is activated by the TEMP keyword in the RUNSPEC section. Currently this option is not supported by OPM Flow.","units":{"field":"ft2","metric":"m2","laboratory":"cm2"},"default":"None","record":1},{"index":11,"name":"VHEATCAP","description":"A real positive value equal to or greater than zero that defines the volumetric heat capacity of the pipe wall used in thermal conductivity calculations for when the temperature calculation is activated by the TEMP keyword in the RUNSPEC section. Currently this option is not supported by OPM Flow.","units":{"field":"Btu/ft/day/°R","metric":"kJ/m/day/K","laboratory":"J/cm/hr/K"},"default":"None","record":1},{"index":12,"name":"THCON","description":"A real positive value equal to or greater than zero that defines the thermal conductivity of the pipe wall used in thermal conductivity calculations for when the temperature calculation is activated by the TEMP keyword in the RUNSPEC section. Currently this option is not supported by OPM Flow.","units":{"field":"Btu/ft/day/°R","metric":"kJ/m/day/K","laboratory":"J/cm/hr/K"},"default":"None","record":1},{"index":1,"name":"ISEG1","description":"A positive integer greater than or equal to two and less than or equal to MXSEGS on WSEGDIMS keyword in the RUNSPEC section that defines the start of the segment range.","units":{},"default":"None","record":2,"value_type":"INT"},{"index":2,"name":"ISEG2","description":"A positive integer greater than or equal to ISEG1 on this record and less than or equal to MXSEGS on the WSEGDIMS keyword in the RUNSPEC section that defines the end of the segment range.","units":{},"default":"None","record":2,"value_type":"INT"},{"index":3,"name":"IBRANCH","description":"A positive integer greater than or equal to one and less than or equal to MXBRAN on WSEGDIMS keyword in the RUNSPEC section that defines the branch number of a segment. All segments on the main stem must have IBRANCH set to one, and those on lateral branches should have IBRANCH set to between two and MXBRAN.","units":{},"default":"None","record":2,"value_type":"INT"},{"index":4,"name":"ISEG3","description":"A positive integer greater than or equal to one and less than or equal to MXSEGS on the WSEGDIMS keyword in the RUNSPEC section that defines the outlet segment for the segment at the start of the segment range (ISEG1).","units":{},"default":"None","record":2,"value_type":"INT"},{"index":5,"name":"LENGTH","description":"A real positive value that: If TUBOPT is set to INC then LENGTH is the incremental length of the tubing for each segment in the segment range. If TUBOPT is set to ABS then LENGTH is the length of the tubing from the tubing reference point to the last segment in the range. The length between the nodal point of the last segment and the outlet segment is divided equally between each of the segments in the segment range.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","record":2,"value_type":"DOUBLE","dimension":"Length"},{"index":6,"name":"DEPTH","description":"A real positive value that: If TUBOPT is set to INC then DEPTH is the incremental depth change of the tubing for each segment in the segment range. If TUBOPT is set to ABS then DEPTH defines the depth of the tubing at the nodal point of the last segment in the segment range. The depths for other segments in the segment range are obtained by linear interpolation.","units":{},"default":"","record":2,"value_type":"DOUBLE","dimension":"Length"},{"index":7,"name":"ID","description":"A real positive value that defines the tubing internal diameter of each segment in the segment range.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","record":2,"value_type":"DOUBLE","dimension":"Length"},{"index":8,"name":"EPSILON","description":"A real positive value that defines the tubing absolute roughness of each segment in the segment range.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","record":2,"value_type":"DOUBLE","dimension":"Length"},{"index":9,"name":"XAREA","description":"A real positive value equal to or greater than zero that defines the cross-sectional area for fluid flow. Currently this option is not supported by OPM Flow.","units":{"field":"ft2","metric":"m2","laboratory":"cm2"},"default":"None","record":2,"value_type":"DOUBLE","dimension":"Length*Length"},{"index":10,"name":"VOLSEG","description":"VOLSEG is a real positive value that defines the effective segment volume for the this segment. Currently this option is not supported by OPM Flow.","units":{"field":"ft3","metric":"m3","laboratory":"cm3"},"default":"None","record":2,"value_type":"DOUBLE","dimension":"Length*Length*Length"},{"index":11,"name":"XCORDS","description":"A real positive value that: If TUBOPT is set to INC then XCORDS is the incremental change in the x-coordinate of the tubing for each segment in the segment range. If TUBOPT is set to ABS then XCORDS defines the x-coordinate of the tubing at the nodal point of the last segment in the segment range. The x-coordinates for other segments in the segment range are obtained by linear interpolation. Currently this option is not supported by OPM Flow.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","record":2,"value_type":"DOUBLE","dimension":"Length"},{"index":12,"name":"YCORDS","description":"A real positive value that: If TUBOPT is set to INC then YCORDS is the incremental change in the y-coordinate of the tubing for each segment in the segment range. If TUBOPT is set to ABS then YCORDS defines the y-coordinate of the tubing at the nodal point of the last segment in the segment range. The y-coordinates for other segments in the segment range are obtained by linear interpolation. Currently this option is not supported by OPM Flow.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","record":2,"value_type":"DOUBLE","dimension":"Length"},{"index":13,"name":"XAREAS","description":"A real positive value equal to or greater than zero that defines the cross-sectional area of the pipe wall for this segment, that is used in thermal conductivity calculations for when the temperature calculation is activated by the TEMP keyword in the RUNSPEC section. Currently this option is not supported by OPM Flow.","units":{"field":"ft2","metric":"m2","laboratory":"cm2"},"default":"None","record":2},{"index":14,"name":"VHEATSEG","description":"A real positive value equal to or greater than zero that defines the volumetric heat capacity of the pipe wall for this segment, that is used in thermal conductivity calculations for when the temperature calculation is activated by the TEMP keyword in the RUNSPEC section. Currently this option is not supported by OPM Flow.","units":{"field":"Btu/ft/day/°R","metric":"kJ/m/day/K","laboratory":"J/cm/hr/K"},"default":"None","record":2},{"index":15,"name":"THCSEG","description":"A real positive value equal to or greater than zero that defines the thermal conductivity of the pipe wall for this segment, that is used in thermal conductivity calculations for when the temperature calculation is activated by the TEMP keyword in the RUNSPEC section. Currently this option is not supported by OPM Flow.","units":{"field":"Btu/ft/day/°R","metric":"kJ/m/day/K","laboratory":"J/cm/hr/K"},"default":"None","record":2}],"example":"The following example defines one multi-segment oil production well (OP01) using the WELSPECS, WELSEGS, COMPDAT and COMPSEGS keywords, and one standard water injection well (WI01) using the WELSPECS and COMPDAT keywords.\n--\n-- WELL SPECIFICATION DATA\n--\n-- WELL GROUP LOCATION BHP PHASE DRAIN INFLOW OPEN CROSS PVT\n-- NAME NAME I J DEPTH FLUID AREA EQUANS SHUT FLOW TABLE\nWELSPECS\nOP01 PLATFORM 10 10 1* OIL /\nWI01 PLATFORM 1 1 1* WATER /\n/\n--\n-- WELL CONNECTION DATA\n--\n-- WELL --- LOCATION --- OPEN SAT CONN WELL KH SKIN D DIR\n-- NAME II JJ K1 K2 SHUT TAB FACT DIA FACT FACT FACT PEN\nCOMPDAT\nOP01 10 10 1 1 OPEN 1* 200. 0.5 /\nOP01 10 10 2 2 OPEN 1* 200. 0.5 /\nOP01 10 10 3 3 OPEN 1* 200. 0.4 /\nOP01 10 10 4 4 OPEN 1* 200. 0.4 /\nOP01 10 10 5 5 OPEN 1* 200. 0.4 /\nOP01 10 10 6 6 OPEN 1* 200. 0.4 /\nOP01 9 10 2 2 OPEN 1* 200. 0.4 /\nOP01 8 10 2 2 OPEN 1* 200. 0.4 /\nOP01 7 10 2 2 OPEN 1* 200. 0.4 /\nOP01 6 10 2 2 OPEN 1* 200. 0.4 /\nOP01 5 10 2 2 OPEN 1* 200. 0.4 /\nOP01 10 9 3 3 OPEN 1* 200. 0.4 /\nOP01 10 8 3 3 OPEN 1* 200. 0.4 /\nOP01 10 7 3 3 OPEN 1* 200. 0.4 /\nOP01 10 6 3 3 OPEN 1* 200. 0.4 /\nOP01 10 5 3 3 OPEN 1* 200. 0.4 /\nOP01 9 10 5 5 OPEN 1* 200. 0.4 /\nOP01 8 10 5 5 OPEN 1* 200. 0.4 /\nOP01 7 10 5 5 OPEN 1* 200. 0.4 /\nOP01 6 10 5 5 OPEN 1* 200. 0.4 /\nOP01 5 10 5 5 OPEN 1* 200. 0.4 /\nOP01 10 9 6 6 OPEN 1* 200. 0.4 /\nOP01 10 8 6 6 OPEN 1* 200. 0.4 /\nOP01 10 7 6 6 OPEN 1* 200. 0.4 /\nOP01 10 6 6 6 OPEN 1* 200. 0.4 /\nOP01 10 5 6 6 OPEN 1* 200. 0.4 /\nWI01 1 1 7 9 OPEN 1* 200. 0.5 /\n/\n--\n-- WELL SEGMENT SPECIFICATION DATA\n--\n-- WELL NODAL LEN WELL DEPH PRESS FLOW\n-- NAME DEPTH TUBING VOLM OPTN CALC MODEL\nWELSEGS\nOP01 2512.5 2512.5 1.0E-5 ABS HFA HO /\n--\n-- SEG SEG BRAN SEG TUBING NODAL TUBE TUBE XSEC VOL\n-- ISTR IEND NO NO LENGTH DEPTH ID ROUGH AREA SEG\n2 2 1 1 2537.5 2534.5 0.3 0.00010 /\n3 3 1 2 2562.5 2560.5 0.3 0.00010 /\n4 4 1 3 2587.5 2593.5 0.3 0.00010 /\n5 5 1 4 2612.5 2614.5 0.3 0.00010 /\n6 6 1 5 2637.5 2635.5 0.3 0.00010 /\n7 7 2 2 2737.5 2538.5 0.2 0.00010 /\n8 8 2 7 2937.5 2537.5 0.2 0.00010 /\n9 9 2 8 3137.5 2539.5 0.2 0.00010 /\n10 10 2 9 3337.5 2535.5 0.2 0.00010 /\n11 11 2 10 3537.5 2536.5 0.2 0.00010 /\n12 12 3 3 2762.5 2563.5 0.2 0.00010 /\n13 13 3 12 2962.5 2562.5 0.1 0.00010 /\n14 14 3 13 3162.5 2562.5 0.1 0.00010 /\n15 15 3 14 3362.5 2564.5 0.1 0.00010 /\n16 16 3 15 3562.5 2562.5 0.1 0.00010 /\n17 17 4 5 2812.5 2613.5 0.2 0.00010 /\n18 18 4 17 3012.5 2612.5 0.1 0.00010 /\n19 19 4 18 3212.5 2612.5 0.1 0.00010 /\n20 20 4 19 3412.5 2612.5 0.1 0.00010 /\n21 21 4 20 3612.5 2613.5 0.1 0.00010 /\n22 22 5 6 2837.5 2634.5 0.2 0.00010 /\n23 23 5 22 3037.5 2637.5 0.2 0.00010 /\n24 24 5 23 3237.5 2638.5 0.2 0.00010 /\n25 25 5 24 3437.5 2639.5 0.1 0.00010 /\n26 26 5 25 3637.5 2639.5 0.1 0.00010 /\n/\n--\n-- COMPLETION SEGMENT SPECIFICATION DATA\n--\n-- WELL\n-- NAME\nCOMPSEGS\nOP01 /\n--\n-- --LOCATION-- BRAN START END DIR LOC MID COMP ISEG\n-- II JJ K1 NO LENGTH LENGTHPEN I,J,K PERFS LENGTH NO.\n10 10 1 1 2512.5 2525.0 /\n10 10 2 1 2525.0 2550.0 /\n10 10 3 1 2550.0 2575.0 /\n10 10 4 1 2575.0 2600.0 /\n10 10 5 1 2600.0 2625.0 /\n10 10 6 1 2625.0 2650.0 /\n9 10 2 2 2637.5 2837.5 /\n8 10 2 2 2837.5 3037.5 /\n7 10 2 2 3037.5 3237.5 /\n6 10 2 2 3237.5 3437.5 /\n5 10 2 2 3437.5 3637.5 /\n10 9 3 3 2662.5 2862.5 /\n10 8 3 3 2862.5 3062.5 /\n10 7 3 3 3062.5 3262.5 /\n10 6 3 3 3262.5 3462.5 /\n10 5 3 3 3462.5 3662.5 /\n9 10 5 4 2712.5 2912.5 /\n8 10 5 4 2912.5 3112.5 /\n7 10 5 4 3112.5 3312.5 /\n6 10 5 4 3312.5 3512.5 /\n5 10 5 4 3512.5 3712.5 /\n10 9 6 5 2737.5 2937.5 /\n10 8 6 5 2937.5 3137.5 /\n10 7 6 5 3137.5 3337.5 /\n10 6 6 5 3337.5 3537.5 /\n10 5 6 5 3537.5 3737.5 /\n/\nNote the use of both the COMPDAT and COMPSEGS keywords to fully define a multi-segment well’s completion.\nFinally, Figure 12.15depicts the resulting well configuration for both wells, with the conventional water injection well shown in blue and the multi-segment oil producer shown in green.\n[formula]\n[formula]Figure 12.15: Multi-Segment Well OP01 Completion 3D View","records_meta":[{"expected_columns":9},{"expected_columns":12}],"size_kind":"list"},"WELSOMIN":{"name":"WELSOMIN","sections":["SCHEDULE"],"supported":false,"summary":"WELSOMIN defines a minimum oil saturation for a well connection above which the connection will be opened automatically. If the grid block connection is below WELSOMIN then connection will not be automatically opened. Automatic opening of connection is controlled by the STATUS parameter on the COMPDAT keyword in the SCHEDULE section. Note that if the COMPLUMP keyword in the SCHEDULE section has been used to lump connections into completions then WELSOMIN is compared to the average oil saturation of the completion.","parameters":[{"index":1,"name":"SOMIN","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"WELSPECL":{"name":"WELSPECL","sections":["SCHEDULE"],"supported":false,"summary":"The WELSPECL keyword defines the general well specification data for all well types and must be used for all wells contained within a Local Grid Refinement (“LGR”) instead of the WELSPECS keyword. WELSPECL must declare wells first before any other LGR well specification keywords are used in the input file. The keyword declares the name of well, the group the well belongs to, the LGR the well is incorporated into, the wellhead location and other key parameters.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well specification data is being defined.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"GRPNAME","description":"A character string of up to eight characters in length that defines the group name for which the well is assigned to. The group named FIELD is the top most group and thus GRPNAME cannot be set to FIELD, although this is allowed in the commercial compositional simulator but not the commercial black-oil simulator. Note that the group hierarchy should be defined by the GRUPTREE keyword when there is more than one level of groups, otherwise all the groups will sit directly under the FIELD group in the group tree hierarchy. Secondly, groups defined by the GRUPTREE keyword cannot contain other groups and wells; that is, groups must either contain other groups or wells but not both. If necessary, wells can be re-allocated to a different group by re-entering a well's WELSPECS data together with a new value for GRPNAME.","units":{},"default":"None","value_type":"STRING"},{"index":3,"name":"LGRNAME","description":"A character string of up to eight characters in length that defines the name of the local grid refinement for which the well is assigned to.","units":{},"default":"None","value_type":"STRING"},{"index":4,"name":"I","description":"A positive integer greater than or equal to zero and less than or equal to NX on the CARFIN keyword for Cartesian grids, that defines the wellhead location for a vertical or deviated well, or the heel for a horizontal well in the I-direction within the LGR. For radial LGRs this parameter should be set to one.","units":{},"default":"None","value_type":"INT"},{"index":5,"name":"J","description":"A positive integer greater than or equal to zero and less than or equal to NY on the CARFIN keyword for Cartesian grids, that defines the wellhead location for a vertical or deviated well, or the heel for a horizontal well in the J-direction within the LGR. For radial LGRs this parameter should be set to one.","units":{},"default":"None","value_type":"INT"},{"index":6,"name":"BHPREF","description":"A real value that defines the reference depth for reporting the bottom-hole pressure for the well. Ideally this value should be set to the midpoint of the perforations as defined by the COMPDATL keyword in the SCHEDULE section. If defaulted by 1* or set to a value less than or equal to zero, then the mid-point of shallowest connection defined by the COMPDATL keyword will be used.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"Mid-point of shallowest connection defined by the COMPDATL keyword","value_type":"DOUBLE","dimension":"Length"},{"index":7,"name":"TYPE","description":"A defined character that defines the “main” phase for the well, and should be set to one of the following character strings: GAS: for a gas well. OIL: for an oil well. WAT: for a water injection well. LIQ: for an oil well when the liquid productivity index is required for the well. This parameter defines the phase used to calculate a well’s productivity or injectivity index and the type of well, or a well’s connection, to close when a group’s production constraints, as defined on the GCONPROD keyword in the SCHEDULE section, have been violated. For example, if the well is declared as an oil well, then excessive gas and water connections will be subject to closure.","units":{},"default":"None","value_type":"STRING","options":["GAS","OIL","WAT","LIQ"]},{"index":8,"name":"DRADIUS","description":"A real value that defines the well drainage radius for the well used to calculate a well’s productivity or injectivity index. A default of zero results in the pressure equivalent radius of the grid blocks containing the well connections are used.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"0.0","value_type":"DOUBLE","dimension":"Length"},{"index":9,"name":"INFLOW","description":"A defined character string that defines the inflow equation to be used for the well in calculating the well’s flow rates. INFLOW should be set to one of the following character strings: STD: the standard inflow equation will be used. This is normally used for wells that are primary oil or water wells. NO: an alias for STD. R-G: the Russell Goodrich1\n Russell, D.G., Goodrich, J.H., Perry, G.E and Bruskotter, J.F \"Methods of Predicting Gas Well Performance\", Transactions of the ASME, Journal of Petroleum Technology (1966) 99-108. pressure square inflow equation will used. This option can be used for dry gas wells. Russell, D.G., Goodrich, J.H., Perry, G.E and Bruskotter, J.F \"Methods of Predicting Gas Well Performance\", Transactions of the ASME, Journal of Petroleum Technology (1966) 99-108. YES: an alias for R-G. P-P: the general dry gas pseudo pressure inflow equation will be used. Normally used for dry gas wells. GPP: the generalized gas pseudo pressure inflow equation used with wet gas wells, that is condensate gas wells. This inflow equation is based on the formulation of Whitson et al.2\n Whitson, C. H. and Fevang, Ø. “Generalised Pseudopressure Well Treatment in Reservoir Simulation,” Presented at the IBC Technical Services Conference on Optimisation of Gas Condensate Fields, Aberdeen, UK (June 26-27, 1997). Whitson, C. H. and Fevang, Ø. “Generalised Pseudopressure Well Treatment in Reservoir Simulation,” Presented at the IBC Technical Services Conference on Optimisation of Gas Condensate Fields, Aberdeen, UK (June 26-27, 1997). For oil and water wells the INFLOW should be set to STD, why for dry gas wells INFLOW can be set to either R-G or P-P; however, the P-P option is preferred for dry gas wells due to the more rigorous treatment of gas flow. For wet gas wells, that is gas condensate wells, INFLOW should be set to GPP. Only INFLOW equal to STD and NO are currently implemented in OPM Flow.","units":{},"default":"STD","value_type":"STRING","options":["STD","NO","YES","GPP"]},{"index":10,"name":"AUTO","description":"A defined character string that defines the automatic action to be taken if the economic WCUT, GOR, or WGR limits are violated and the well is to cease production. AUTO should be set to one of the following character strings: STOP: the well is “stopped” at the surface and will not produce any fluids to surface; however, if there any open connections then flow may occur within the wellbore and between the open connections depending on a connection’s potential with respect to all the other connections. Inter-connection flow (cross flow) can be prevented by setting the XFLOW variable to NO. In this case the well’s behavior will be similar to the SHUT option described below. SHUT: the well is shut at the surface and downhole, this results in no flow at the surface and no cross flow downhole. The corrective action takes places at the end of the time step in which the constraint is violated.","units":{},"default":"SHUT","value_type":"STRING","options":["STOP","SHUT"]},{"index":11,"name":"XFLOW","description":"A defined character string that defines the if cross flow should occur within the wellbore, and should be set to either: YES: to allow cross flow in the wellbore through well connections. NO: to disallow cross flow within the wellbore, even if the flow potentials in the well connections would allow such flow to occur. In some cases numerical issues can occur if this variable is set to YES, and resetting it to NO may resolve the issue; however the results may not represent the physical process in this case.","units":{},"default":"YES","value_type":"STRING","options":["YES","NO"]},{"index":12,"name":"PVTNUM","description":"A positive integer greater than or equal to zero that defines the PVT table used to calculate the wellbore fluid properties that define the relationship between reservoir and surface volume rates. The default value of zero sets PVTNUM to be the PVT table of the deepest connection in the well.","units":{},"default":"0","value_type":"INT"},{"index":13,"name":"DENOPT","description":"A defined character string that sets the type of density calculation used in calculating the wellbore hydrostatic head, and should be set to one of the following character strings: SEG: sets the hydrostatic head density calculation to segmented. In this cases the density is calculated between neighboring well connections and the volumes flowing from the connections. This is the more accurate calculation if the fluid properties flowing from the well connections are variable. The density calculation itself is explicit, i.e. uses the flowing volumes of the last time step. AVG: sets the hydrostatic head density calculation to the average density calculation. Here the density is considered uniform across a given reservoir and is dependent on total inflow rates of each phase and the well’s bottom-hole pressure The default option of 1* invokes the SEG option and is the only option implemented in OPM Flow.","units":{},"default":"SEG","value_type":"STRING","options":["SEG","AVG"]},{"index":14,"name":"FIPNUM","description":"An integer value defines the FIPNUM region used to determine the reservoir conditions in calculating the well’s reservoir volumes. If set to a negative integer value then the FIPNUM region of the deepest connection in the well will be used. If set to zero, the default value, then the average properties for the field will be used. If set to an integer value greater than zero, then the FIPNUM indicated by this value will be used.","units":{},"default":"0","value_type":"INT"},{"index":15,"name":"","description":"Not used.","units":{},"default":"","value_type":"STRING"},{"index":16,"name":"","description":"Not used.","units":{},"default":"","value_type":"STRING"},{"index":17,"name":"","description":"Not used.","units":{},"default":"","value_type":"STRING"},{"index":18,"name":"","description":"Not used.","units":{},"default":"","value_type":"INT"}],"example":"The following example defines three wells using the WELSPECL keyword\n--\n-- WELL SPECIFICATION DATA FOR LGR WELLS\n--\n-- WELL GROUP LGR LOCATION BHP PHASE DRAIN INFLOW SHUT CROSS PVT\n-- NAME NAME NAME I J DEPTH FLUID AREA EQUA. IN FLOW TABLE\nWELSPECL\nGI01 PLATFORM LGR01 14 13 1* GAS 1* P-P SHUT NO 1* /\nGP01 PLATFORM LGR01 64 80 1* GAS 1* GPP SHUT NO 1* /\nOP01 PLATFORM LGR02 24 10 1* OIL 1* STD SHUT NO 1* /\n/\nHere, well GI01 and GP01 are in the same LGR named LGR01 and OP01 is in a separate LGR named LGR02. GI01 is a dry gas injection well that uses the dry gas pseudo inflow equation, GP01 is a gas condensate well that uses the generalized gas pseudo pressure inflow equation, and finally, OP01 is an oil well that uses the standard inflow equation. All wells: will be shut if they are required to cease production, all wells disallow cross flow, and the hydrostatic head calculation is defaulted to the segment option for all wells.","expected_columns":18,"size_kind":"list"},"WELSPECS":{"name":"WELSPECS","sections":["SCHEDULE"],"supported":false,"summary":"The WELSPECS keyword defines the general well specification data for all well types, and must be used for all wells before any other well specification keywords are used in the input file. The keyword declares the well, the name of the well, the group the well initial belongs to, the wellhead location and other key parameters.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well specification data are being defined.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"GRPNAME","description":"A character string of up to eight characters in length that defines the group name for which the well is assigned to. The group named FIELD is the top most group. GRPNAME can be set to FIELD although this is discouraged and a warning message will be issued. This is allowed in the commercial compositional simulator but not the commercial black-oil simulator. The FIELD group cannot contain both groups and wells. Note that the group hierarchy should be defined by the GRUPTREE keyword when there is more than one level of groups, otherwise all the groups will sit directly under the FIELD group in the group tree hierarchy. Secondly, groups defined by the GRUPTREE keyword cannot contain other groups and wells; that is, groups must either contain other groups or wells but not both. If necessary, wells can be re-allocated to a different group by re-entering a well's WELSPECS data together with a new value for GRPNAME.","units":{},"default":"None","value_type":"STRING"},{"index":3,"name":"I","description":"A positive integer greater than or equal to zero and less than or equal to NX that defines the wellhead location for a vertical or deviated well, or the heel for a horizontal well in the I-direction. For wells being specified with the COMPTRAJ and WELTRAJ keywords in SCHEDULE section, that allow for an alternative manner to define the well connections to the simulation grid blocks, this parameter should be defaulted with 1*. Since the simulator will calculate the wellhead location from the trajectory data on the WELTRAJ keyword. Note that the COMPTRAJ and WELTRAJ keywords are OPM Flow specific keywords, and will cause an error in the commercial simulator.","units":{},"default":"None","value_type":"INT"},{"index":4,"name":"J","description":"A positive integer greater than or equal to zero and less than or equal to NY that defines the wellhead location for a vertical or deviated well, or the heel for a horizontal well in the J-direction. For wells being specified with the COMPTRAJ and WELTRAJ keywords in SCHEDULE section, that allows for an alternative manner to define the well connections to the simulation grid blocks, this parameter should be defaulted with 1*. Since the simulator will calculate the wellhead location from the trajectory data on the WELTRAJ keyword. Note that the COMPTRAJ and WELTRAJ keywords are OPM Flow specific keywords, and will cause an error in the commercial simulator.","units":{},"default":"None","value_type":"INT"},{"index":5,"name":"BHPREF","description":"A real value that defines the reference depth for reporting the bottom-hole pressure for the well. Ideally this value should be set to the midpoint of the perforations as defined by the COMPDAT keyword in the SCHEDULE section. If defaulted by 1* or set to a value less than or equal to zero, then the mid-point of shallowest connection defined by the COMPDAT keyword will be used.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"Mid-point of shallowest connection defined by the COMPDAT keyword","value_type":"DOUBLE","dimension":"Length"},{"index":6,"name":"TYPE","description":"A defined character string that defines the “main” phase for the well, and should be set to one of the following character strings: GAS: for a gas well. OIL: for an oil well. WAT: for a water injection well. LIQ: for an oil well when the liquid productivity index is required for the well. This parameter defines the phase used to calculate a well’s productivity or injectivity index and the type of well, or a well’s connection, to close when a group’s production constraints, as defined on the GCONPROD keyword in the SCHEDULE section, have been violated. For example, if the well is declared as an oil well, then excessive gas and water connections will be subject to closure. Note OPM Flow only currently supports options one to three, that is option four (LIQ) is not supported. For producing wells this mostly matters if one plots the WPI summary vector (productivity index for well's preferred phase). In the current treatment WPI will not have contributions from the water phase if the declared preferred phase is LIQ. For injecting wells WELSPECS's preferred phase does not matter, since the preferred phase is (typically) reset to the injected phase via the WCONINJE and WCONINJH keywords.","units":{},"default":"None","value_type":"STRING","options":["GAS","OIL","WAT","LIQ"]},{"index":7,"name":"DRADIUS","description":"A real value that defines the well drainage radius for the well used to calculate a well’s productivity or injectivity index. A default of zero results in the pressure equivalent radius of the grid blocks containing the well connections are used.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"0.0","value_type":"DOUBLE","dimension":"Length"},{"index":8,"name":"INFLOW","description":"A defined character string that defines the inflow equation to be used for the well in calculating the well’s flow rates. INFLOW should be set to one of the following character strings: STD: the standard inflow equation will be used. This is normally used for wells that are primary oil or water wells. NO: an alias for STD. R-G: the Russell Goodrich1\n Russell, D.G., Goodrich, J.H., Perry, G.E and Bruskotter, J.F \"Methods of Predicting Gas Well Performance\", Transactions of the ASME, Journal of Petroleum Technology (1966) 99-108. pressure square inflow equation will used. This option can be used for dry gas wells. Russell, D.G., Goodrich, J.H., Perry, G.E and Bruskotter, J.F \"Methods of Predicting Gas Well Performance\", Transactions of the ASME, Journal of Petroleum Technology (1966) 99-108. YES: an alias for R-G. P-P: the general dry gas pseudo pressure inflow equation will be used. Normally used for dry gas wells. GPP: the generalized gas pseudo pressure inflow equation used with wet gas wells, that is condensate gas wells. This inflow equation is based on the formulation of Whitson et al.2\n Whitson, C. H. and Fevang, Ø. “Generalised Pseudopressure Well Treatment in Reservoir Simulation,” Presented at the IBC Technical Services Conference on Optimisation of Gas Condensate Fields, Aberdeen, UK (June 26-27, 1997). Whitson, C. H. and Fevang, Ø. “Generalised Pseudopressure Well Treatment in Reservoir Simulation,” Presented at the IBC Technical Services Conference on Optimisation of Gas Condensate Fields, Aberdeen, UK (June 26-27, 1997). For oil and water wells the INFLOW should be set to STD, whereas for dry gas wells INFLOW can be set to either R-G or P-P; however, the P-P option is preferred for dry gas wells due to the more rigorous treatment of gas flow. For wet gas wells, that is gas condensate wells, INFLOW should be set to GPP. Only INFLOW equal to STD and NO are currently implemented in OPM Flow.","units":{},"default":"STD","value_type":"STRING","options":["STD","NO","YES","GPP"]},{"index":9,"name":"AUTO","description":"A defined character string that specifies the action to be taken if the well is automatically closed/shut by the simulator, and should be set to one of the following: STOP: the well is “stopped” at the surface and will not produce any fluids to surface; however, if there any open connections then flow may occur within the wellbore and between the open connections depending on a connection’s potential with respect to all the other connections. Inter-connection flow (cross flow) can be prevented by setting the XFLOW variable to NO. In this case the well’s behavior will be similar to the SHUT option described below. SHUT: the well is shut at the surface and downhole, this results in no flow at the surface and no cross flow downhole. The corrective action takes places at the end of the time step in which the constraint is violated.","units":{},"default":"SHUT","value_type":"STRING","options":["STOP","SHUT"]},{"index":10,"name":"XFLOW","description":"A defined character string that defines the if cross flow should occur within the wellbore, and should be set to either: YES: to allow cross flow in the wellbore through well connections. NO: to disallow cross flow within the wellbore, even if the flow potentials in the well connections would allow such flow to occur. In some cases numerical issues can occur if this variable is set to YES, and resetting it to NO may resolve the issue; however, the results may not represent the physical down hole process in this case.","units":{},"default":"YES","value_type":"STRING","options":["YES","NO"]},{"index":11,"name":"PVTNUM","description":"A positive integer greater than or equal to zero that defines the PVT table used to calculate the wellbore fluid properties that define the relationship between reservoir and surface volume rates. The default value of zero sets PVTNUM to be the PVT table of the deepest connection in the well.","units":{},"default":"0","value_type":"INT"},{"index":12,"name":"DENOPT","description":"A defined character string that sets the type of density calculation used in calculating the wellbore hydrostatic head, and should be set to one of the following character strings: SEG: sets the hydrostatic head density calculation to segmented. In this cases the density is calculated between neighboring well connections and the volumes flowing from the connections. This is the more accurate calculation if the fluid properties flowing from the well connections are variable. The density calculation itself is explicit, i.e. uses the flowing volumes of the last time step. AVG: sets the hydrostatic head density calculation to the average density calculation. Here the density is considered uniform across a given reservoir and is dependent on total inflow rates of each phase and the well’s bottom-hole pressure The default option of 1* invokes the SEG option and is the only option implemented in OPM Flow.","units":{},"default":"SEG","value_type":"STRING","options":["SEG","AVG"]},{"index":13,"name":"FIPNUM","description":"An integer value defines the FIPNUM region used to determine the reservoir conditions in calculating the well’s reservoir volumes and is determined by: If set to a negative integer value then the FIPNUM region of the deepest connection in the well will be used. If set to zero, the default value, then the average properties for the field will be used. If set to an integer value greater than zero, then the FIPNUM indicated by this value will be used.","units":{},"default":"0","value_type":"INT"},{"index":14,"name":"STRMLIN1","description":"Not used and should be defaulted with 1*.","units":{},"default":"1*","value_type":"STRING"},{"index":15,"name":"STRMLIN2","description":"Not used and should be defaulted with 1*.","units":{},"default":"1*","value_type":"STRING"},{"index":16,"name":"TYPECOMP","description":"Commercial compositional simulator well type model option that is not used and should be defaulted with either STD or 1*.","units":{},"default":"STD","value_type":"STRING"},{"index":17,"name":"POLYTAB","description":"A positive integer greater than or equal to zero that defines the polymer mixing table, as defined by the PLMIXPAR and PLYMAX keywords, to be used in calculating the well’s well bore properties. The default value of zero means the table allocated via the PLMIXNUM array for the deepest connection in the well bore is utilized. Only the default value of zero is supported by OPM Flow.","units":{},"default":"0","value_type":"INT"}],"example":"The following example defines three wells using the WELSPECS keyword\n--\n-- WELL SPECIFICATION DATA\n--\n-- WELL GROUP LOCATION BHP PHASE DRAIN INFLOW OPEN CROSS PVT\n-- NAME NAME I J DEPTH FLUID AREA EQUANS SHUT FLOW TABLE\nWELSPECS\nGI01 PLATFORM 14 13 1* GAS 1* P-P SHUT NO 1* /\nGP01 PLATFORM 64 80 1* GAS 1* GPP SHUT NO 1* /\nOP01 PLATFORM 24 110 1* OIL 1* STD SHUT NO 1* /\n/\nHere, well GI01 is a dry gas injection well that uses the dry gas pseudo inflow equation, GP01 is a gas condensate well that uses the generalized gas pseudo pressure inflow equation, and finally, OP01 is an oil well that uses the standard inflow equation. All wells will be shut if they are required to cease production, all wells disallow cross flow, and the hydrostatic head calculation is defaulted to the segment option for all wells.\nIf the same three wells are using the COMPTRAJ and WELTRAJ keywords to specify the connections to the simulation grid, then the WELSPECS keyword should be;\n--\n-- WELL SPECIFICATION DATA\n--\n-- WELL GROUP LOCATION BHP PHASE DRAIN INFLOW OPEN CROSS PVT\n-- NAME NAME I J DEPTH FLUID AREA EQUANS SHUT FLOW TABLE\nWELSPECS\nGI01 PLATFORM 1* 1* 1* GAS 1* P-P SHUT NO 1* /\nGP01 PLATFORM 1* 1* 1* GAS 1* GPP SHUT NO 1* /\nOP01 PLATFORM 1* 1* 1* OIL 1* STD SHUT NO 1* /\n/\nNotice how the well location parameters have been defaulted with 1* in this case.\nThe following example illustrates how the WELSPECS keyword can be used to change the controlling group for oil production wells previously specified by the WELSPECS keyword that have an oil production rate less than 100.\n--\n-- ACTIONX BLOCK\n--\nACTIONX\nACT01 1 /\nWOPR 'OP*' < 100.0 /\n/\nWELSPECS\n'?' 'LOWPRESS' /\n/\nENDACTIO","expected_columns":17,"size_kind":"list"},"WELTARG":{"name":"WELTARG","sections":["SCHEDULE"],"supported":false,"summary":"The WELTARG keyword modifies the target and constraints values of both rates and pressures for previously defined wells without having to define all the variables on the well control keywords: WCONPROD, WCONHIST, WCONINJE, or WCONINJH. Variables not changed by the WELTARG keyword remain the same as those previously entered via the well control keywords or previously entered WELTARG keywords. Note that the well must still be initially fully defined using the WCONPROD or WCONINJE keywords. All the aforementioned keywords are described in the SCHEDULE section.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well production rates and pressures data are being redefined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS and WCONPROD (or WCONINJE) keywords in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"TARGET","description":"A defined character string that sets the item to be changed for the well the value of the item is set by item (3). ORAT: reset the surface oil production rate value as defined by item (3). WRAT: reset the surface water production rate value as defined by item (3). GRAT: reset the surface gas production rate value as defined by item (3). LRAT: reset the surface liquid (oil plus water) production rate value as defined by (3). CRAT: reset the linearly combined calculated rate value as defined by (3). This option is not supported. RESV: reset the in situ reservoir volume rate value as defined by (3). BHP: reset the bottom-hole pressure value as defined by item (3). THP: reset the tubing head pressure value for the well as defined by item (3). VFP: reset the vertical lift performance table number as defined by (3). LIFT: reset the artificial lift quantity for use with vertical lift performance tables. GUID: reset the guide rate value for wells operating under group control. The commercial compositional simulator options: WGRA, NGL, CVAL, REIN, STRA, SATP and SATT are not applicable. Note that TARGET only defines the variable to be changed, it does not change how a well is controlled. For example, if a well is operating on ORAT control, as defined by the previously entered WCONPROD keyword, entering TARGET equal to LRAT with a value, changes the liquid constraint but the well still remains on ORAT control. Use the WELCNTL keyword in the SCHEDULE section to change the control mode of a well.","units":{},"default":"None","value_type":"STRING","options":["ORAT","WRAT","GRAT","LRAT","CRAT","RESV","BHP","THP","VFP","LIFT","GUID"]},{"index":3,"name":"VALUE Liquid Gas Res Vol Pressure VFP LIFT","description":"A real positive value that defines the value of the variable declared by TARGET This value may be specified using a User Defined Argument (UDA).","units":{"field":"stb/d Mscf/d rb/d psia dimensionless same as VFPPROD or VFPINJ","metric":"sm3/day sm3/day rm3/day barsa dimensionless same as VFPPROD or VFPINJ","laboratory":"scc/hour scc/hour rcc/hour atma dimensionless same as VFPPROD or VFPINJ"},"default":"None","value_type":"UDA"}],"example":"The following example below shows the oil rates for the OP01 oil producer at the start of the schedule section (January 1, 2000).\n-- ------------------------------------------------------------------------------\n-- 01 JAN 2000 START OF SCHEDULE SECTION\n-- ------------------------------------------------------------------------------\n--\n-- WELL PRODUCTION WELL CONTROLS\n--\n-- WELL OPEN/ CNTL OIL WAT GAS LIQ RES BHP THP VFP VFP\n-- NAME SHUT MODE RATE RATE RATE RATE RATE PRES PRES TABLE ALFQ\nWCONPROD\nOP01 OPEN ORAT 3000 1* 1* 1* 1* 750.0 500. 9 1* /\n/ DATES\n01 FEB 2000 /\n/\n--\n-- WELL PRODUCTION AND INJECTION TARGETS\n--\n-- WELL WELL TARGET\n-- NAME TARG VALUE\nWELTARG\nOP01 ORAT 2000 /\n/\nFrom January 1, 2000 to February 1, 2000 well OP01 is open and is on oil rate control and has a target oil rate of 3,000 stb/d, and uses VFPPROD vertical lift table number 9 with a minimum tubing head pressure constraint of 500 psia. After February 1, 2000 the well’s oil rate is reduced to 2,000 stb/d and all the other parameters remain unchanged.","expected_columns":3,"size_kind":"list"},"WELTRAJ":{"name":"WELTRAJ","sections":["SCHEDULE"],"supported":true,"summary":"The WELTRAJ keyword defines a trajectory well together with the well trajectory data (simplified directional survey data), and is used in conjunction with the COMPTRAJ keyword in the SCHEDULE section to define the well connections to the simulation grid blocks. The keyword can only be used for trajectory wells that employ the COMPTRAJ keyword to define the connections to the grid, that is, one cannot use COMPDAT keyword in the SCHEDULE section for declaring the connections to the grid for these type of wells.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well trajectory data are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur. Secondly, the wellhead location parameters on the WELSPECS keyword, WELSPECS(I, J), should be defaulted with 1* for trajectory wells, as the well location will be calculated by the simulator.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"IBRANCH","description":"A positive integer greater than or equal to one and less than or equal to MXBRAN on WSEGDIMS keyword in the RUNSPEC section that defines the branch number of a segment. All segments on the main stem must have IBRANCH set to one and lateral branches should have values between two and MXSEGS on the WSEGDIMS keyword in the RUNSPEC section. Only the default value of one is currently supported, that is only the main branch of a multi-segment well is supported, or a single trajectory for a conventional well.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"1","value_type":"INT"},{"index":3,"name":"X","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":4,"name":"Y","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":5,"name":"TVD","description":"A real negative or positive value that defines the True Vertical Depth along the wellbore path at XCORD and YCORD. Normally, TVD is referenced to the subsea elevation, that is TVDSS.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":"Length"}],"example":"The following example defines two trajectory wells oil wells, OP01 and OP02, using the WELSPECS and WELTRAJ keywords, together with their perforations using the COMPTRAJ keyword.\n--\n-- WELL SPECIFICATION DATA\n--\n-- WELL GROUP LOCATION BHP PHASE DRAIN INFLOW OPEN CROSS PVT\n-- NAME NAME I J DEPTH FLUID AREA EQUANS SHUT FLOW TABLE\nWELSPECS\nOP01 PLATFORM 1* 1* 1* OIL 1* STD SHUT NO 1* /\nOP02 PLATFORM 1* 1* 1* OIL 1* STD SHUT NO 1* /\n/\n--\n-- WELL TRAJECTORY DATA\n--\n-- WELL BRAN XCORD YCORD TVDSS MD\n-- NAME NO DEPTH DEPTH\n-- ----- ---- ------------ ------------ ------------ ------------\nWELTRAJ\nOP01 1* 2.805445e+06 3.602948e+06 -100.000000 0.0 /\nOP01 1* 2.805445e+06 3.602948e+06 877.0000000 977.0 /\nOP01 1* 2.805445e+06 3.602948e+06 957.9950240 1058.0 /\nOP01 1* 2.805444e+06 3.602946e+06 1051.976081 1152.0 /\n…………………... /\nOP02 1* 2.810828e+06 3.604507e+06 9371.792711 11418.0 /\nOP02 1* 2.810885e+06 3.604525e+06 9443.657000 11511.0 /\nOP02 1* 2.810952e+06 3.604546e+06 9531.966162 11624.0 /\nOP02 1* 2.810973e+06 3.604553e+06 9560.411742 11660.0 /\n/\n--\n--\n-- WELL TRAJECTORY CONNECTION DATA\n--\n-- WELL BRAN -- PERFORATION -- COMPL OPEN SAT CONN WELL KH SKIN D\n-- NAME NO. TOP BOT REF NO. SHUT TAB FACT DIA FACT FACT FACT\nCOMPTRAJ\nOP01 1* 8230 8244 MD 1 SHUT 1* 1* 0.708 1* 0.0 1* /\nOP01 1* 8352 8380 MD 1 SHUT 1* 1* 0.708 1* 0.0 1* /\nOP01 1* 9070 9100 MD 1 SHUT 1* 1* 0.708 1* 0.0 1* /\nOP01 1* 9220 9250 MD 2 SHUT 1* 1* 0.708 1* 0.0 1* /\nOP01 1* 9266 9280 MD 2 SHUT 1* 1* 0.708 1* 0.0 1* /\nOP01 1* 9693 9703 MD 3 SHUT 1* 1* 0.708 1* 0.0 1* /\nOP01 1* 9940 9974 MD 3 SHUT 1* 1* 0.708 1* 0.0 1* /\nOP02 1* 9979 9985 TVD 1* SHUT 1* 1* 0.708 1* 0.0 1* /\nOP02 1* 10173 10183 TVD 1* SHUT 1* 1* 0.708 1* 0.0 1* /\nOP02 1* 10190 10204 TVD 1* SHUT 1* 1* 0.708 1* 0.0 1* /\nOP02 1* 10327 10333 TVD 1* SHUT 1* 1* 0.708 1* 0.0 1* /\nOP02 1* 10339 10345 TVD 1* SHUT 1* 1* 0.708 1* 0.0 1* /\nOP02 1* 11528 11538 TVD 1* SHUT 1* 1* 0.708 1* 0.0 1* /\nHere, well OP01 has eight perforation intervals, with the intervals one to three grouped into one completion, perforation intervals four to five grouped into completion number two, and finally the bottom three perforations are grouped into completion number three. In contrast, OP02 has six perforated intervals with their completion interval defaulted to one.\n| Note This is an OPM Flow specific keyword and will therefore cause an error in the commercial simulator. |\n|----------------------------------------------------------------------------------------------------------|","expected_columns":6,"size_kind":"list"},"WFOAM":{"name":"WFOAM","sections":["SCHEDULE"],"supported":null,"summary":"The WFOAM keyword defines an injection wells foam concentration. The foam option must be activated by the FOAM keyword in the RUNSPEC section in order to use this keyword. Note if a well’s foam concentration is not set with this keyword then default value of zero is assigned to a well.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well injection foam concentration is being defined.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"FOAMCON","description":"A real positive value that defines the well’s injection foam concentration. This value may be specified using a User Defined Argument (UDA). Units are dependent on the transport phase specified via the FOAMOPT1 variable on the FOAMOPTS keyword in the PROPS section. FOAMOPT1 should be set to either GAS or WATER. Currently OPM Flow only supports injecting foam via the GAS phase.","units":{"field":"Gas: lb/Mscf Water: lb/stb","metric":"Gas: kg/sm3 Water: kg/sm3","laboratory":"Gas: gm/scc Water: gm/scc"},"default":"None","value_type":"UDA","dimension":"FoamDensity"}],"example":"--\n-- WELL INJECTION FOAM CONCENTRATION\n--\n-- WELL FOAM\n-- NAME FOAMCON\nWFOAM\nGI01 0.020 /\nGI02 0.020 /\nGI03 0.020 /\n/\nHere three gas wells are given an injection foam concentration of 0.020 lb/Mscf, assuming field units.","expected_columns":2,"size_kind":"list"},"WFRICSEG":{"name":"WFRICSEG","sections":["SCHEDULE"],"supported":false,"summary":"WFRICSEG converts a previously defined friction well, as per the WFRICTN keyword in the SCHEDULE section, to a multi-segment well. The keyword thus acts as a replacement for the WELSEGS and COMPSEGS keywords for multi-segment wells. See also the WFRICSGL keyword in the SCHEDULE section that performs similar functionality for wells in Local Grid Refinements.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"TUBINGD","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":3,"name":"ROUGHNESS","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":4,"name":"FLOW_SCALING","description":"","units":{},"default":"1","value_type":"DOUBLE"}],"example":"","expected_columns":4,"size_kind":"list"},"WFRICSGL":{"name":"WFRICSGL","sections":["SCHEDULE"],"supported":false,"summary":"WFRICSGL converts a previously defined Local Grid Refinement (“LGR”) friction well, as per the WFRICTNL keyword in the SCHEDULE section, to a multi-segment LGR well. The keyword thus acts as a replacement for the WELSEGS and COMPSEGL keywords for LGR multi-segment wells. See also the WFRICSEG keyword in the SCHEDULE section that performs similar functionality for wells in the global grid.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"TUBINGD","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":3,"name":"ROUGHNESS","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":4,"name":"FLOW_SCALING","description":"","units":{},"default":"1","value_type":"DOUBLE"}],"example":"","expected_columns":4,"size_kind":"list"},"WFRICTN":{"name":"WFRICTN","sections":["SCHEDULE"],"supported":false,"summary":"The WFRICTN keyword is used to declare a previously defined well as a friction well and to set the characteristics for this type of well including: tubing size, pipe roughness, and the connections to the grid. Wellbore friction is important in horizontal and multi-lateral wells where the pressure loss along the pipe can effect a well’s performance. Note that unlike other SCHEDULE section well keywords, multiple wells cannot be entered with one WFRICTN keyword, that is, the keyword must be repeated for each well.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"TUBINGD","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":3,"name":"ROUGHNESS","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":4,"name":"FLOW_SCALING","description":"","units":{},"default":"1","value_type":"DOUBLE"}],"example":"","expected_columns":4,"size_kind":"list"},"WFRICTNL":{"name":"WFRICTNL","sections":["SCHEDULE"],"supported":false,"summary":"The WFRICTNL keyword is used to declare a previously defined Local Grid Refinement (“LGR”) well as a LGR friction well and to set the characteristics for this type of well including: tubing size, pipe roughness, and the connections to the grid. Wellbore friction is important in horizontal and multi-lateral wells where the pressure loss along the pipe can effect a well’s performance. Note that unlike other SCHEDULE section well keywords, multiple wells cannot be entered with one WFRICTNL keyword, that is, the keyword must be repeated for each well.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"TUBINGD","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":3,"name":"ROUGHNESS","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":4,"name":"FLOW_SCALING","description":"","units":{},"default":"1","value_type":"DOUBLE"}],"example":"","expected_columns":4,"size_kind":"list"},"WGASPROD":{"name":"WGASPROD","sections":["SCHEDULE"],"supported":false,"summary":"The WGASPROD keyword declares wells to be Sales Gas producers and sets the incremental gas rate for a well and the maximum number of increments that this rate can be increased. Wells must have been previously been defined via the WELSPECS and WCONPROD keywords in the SCHEDULE section and are subject to any targets or constraints on WCONPROD keyword.","parameters":[{"index":1,"name":"WELL_NAME","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"INCREMENTAL_GAS_PRODUCTION_RATE","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":3,"name":"MAX_INCREMENTS","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":3,"size_kind":"list"},"WGORPEN":{"name":"WGORPEN","sections":["SCHEDULE"],"supported":false,"summary":"The WGORPEN keyword defines a well’s Gas-Oil Ratio (“GOR”) penalty parameters used to calculate a well’s oil production target for the current month, as a function of the well’s previous month’s average GOR. The WGORPEN calculated oil rate overwrites any oil targets set by the WCONPROD and WELTARG keywords in the SCHEDULE section. In North American, it is common practice for the regulator to enforce GOR penalties, in order to control gas production in depletion drive oil reservoirs, with the stated intention to maximize oil recovery by limiting the energy loss from the reservoir by excessive gas production.","parameters":[{"index":1,"name":"WELL_NAME","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"BASE_GOR","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":3,"name":"MAX_OIL_RATE","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time"},{"index":4,"name":"AVG_GOR0","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","expected_columns":4,"size_kind":"list"},"WGRUPCON":{"name":"WGRUPCON","sections":["SCHEDULE"],"supported":false,"summary":"The WGRUPCON keyword defines a well’s production or injection guide rate for when a well is under group control. The guide rate is used to determine a well’s production target under group control in order to satisfy a group’s targets and constraints, including any higher level related groups as well as the FIELD group.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well production targets and constraints data are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"STATUS","description":"A defined character string that declares the status of the well to be under group control or not under group control. STATUS should be set to one of the following character strings: YES: the well is under group control and its production behavior will be influenced by its assigned group, including connecting higher level groups as well as the FIELD group. NO: the well is NOT under group control and its production behavior will only be influenced by its own targets and constraints. Note the default value of YES puts all wells under group control unless specified otherwise by the STATUS variable, or the TARGET variable on the WCONPROD and WCONINJE keywords in the SCHEDULE section.","units":{},"default":"YES","value_type":"STRING","options":["YES","NO"]},{"index":3,"name":"GUIDERAT","description":"A dimensionless real number that determines the well’s share of its group production (or injection) target rate. If GUIDERAT is a positive number then the guide rate for the well is fixed until modified by this keyword at a subsequent time. If TARGET variable on this keyword is not equal to the group’s controlling phase, then the GUIDERAT is converted into the groups’ controlling phase and is updated every time step. If GUIDERAT is less than or equal to zero then the well’s guide rate is based on the well’s potential (unrestricted flow) and the potential is calculated every time step.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"-1.0","value_type":"DOUBLE"},{"index":4,"name":"TARGET","description":"A defined character string that sets the well’s guide rate phase that the GUIDERAT value should be applied to. TARGET should be set to one of the following character strings: OIL: the well's guide rate applies to the surface oil production rate. WAT: the well's guide rate applies to the surface water production rate. GAS: the well's guide rate applies to the surface gas production rate. LIQ: the well's guide rate applies to the surface liquid (oil plus water) production rate. RES: the well's guide rate applies to the in situ reservoir volume rate. RAT: the well’s guide rate applies to the surface rate of the injection phase. This should only be used if the well has been declared an injection well via the WCONINJE keyword in the SCHEDULE section. COMB: the well’s guide rate applies to the linearly combined calculated rate. This option is not supported by OPM Flow. TARGET may be defaulted if GUIDERAT has been defaulted, either by 1* or a value less than or equal to zero.","units":{},"default":"None","value_type":"STRING","options":["OIL","WAT","GAS","LIQ","RES","RAT","COMB"]},{"index":5,"name":"SCALE","description":"A real value that is used to multiple the GUIDERAT or the calculated well potentials to determine the final GUIDERAT for the well.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0","value_type":"DOUBLE"}],"example":"The following example defines the guides rates for all oil and gas producers and the gas injectors as follows:\n--\n-- DEFINE WELL GUIDES FOR GROUP CONTROL\n--\n-- WELL GRUP GUIDE GUIDE SCALE\n-- NAME CNTL RATE PHASE FACT\nWGRUPCON\n'GI*' YES 0 RAT 1.0 /\n'GP*' YES 0 GAS 1.0 /\n'OP*' NO 2 OIL 1.0 /\n/\nBoth the gas producers (‘GP*’) and injectors (‘GI’*) are under group control with their guide rates based on their potentials. The gas injectors are controlled based on their potential surface gas injection rates and the gas producers on their potential surface gas production rates. In comparison, the oil wells (OP*) are controlled by their own targets and constraints.","expected_columns":5,"size_kind":"list"},"WHEDREFD":{"name":"WHEDREFD","sections":["SCHEDULE"],"supported":false,"summary":"The WHEDREFD keyword sets the hydraulic head reference depth for reporting the hydraulic head pressure for the well, for wells that have previously been defined by the WELSPECS keyword in the SCHEDULE section.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well hydraulic head reference depth data is being defined.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"HYDREF","description":"A real value that defines the hydraulic head reference depth for reporting the hydraulic head pressure for the well. HYDREF cannot be defaulted on the keyword; however if a well has not been set by this keyword HYDREF is set equal to the value on the HYDRHEAD keyword.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"None","value_type":"DOUBLE","dimension":"Length"}],"example":"The following example defines three wells hydraulic head reference depths for reporting, using the WHEDREFD keyword\n--\n-- WELL HYDRAULIC HEAD REFERENCE DEPTH\n--\n-- WELL HYDREF\n-- NAME DEPTH\nWHEDREFD\nOP01 150.0 /\nOP02 175.0 /\nOP03 150.0 /\n/\nHere, well OP01 and OP03 have their hydraulic head reference depths set to 150.0 ft and well OP02’s hydraulic head reference depth is set to 175.0 ft.","expected_columns":2,"size_kind":"list"},"WHISTCTL":{"name":"WHISTCTL","sections":["SCHEDULE"],"supported":true,"summary":"The WHISTCTL keyword changes the target control for wells declared as history match wells via the WCONHIST keyword in the SCHEDULE section. The target phase is set on the WCONHIST keyword and WHISTCTL overrides this value for all subsequent entries on the WCONHIST keyword.","parameters":[{"index":1,"name":"TARGET","description":"A defined character string that sets the observed target production phase for the well, all the other phases are calculated unconstrained and used for reporting only. The simulator will attempt to meet the TARGET based on the phase rate stated in items (4) to (6) and (10) on the WCONHIST keyword. TARGET should be set to one of the following character strings: ORAT: the target is set to the surface oil production rate as defined by item (4) on the WCONHIST keyword. WRAT: the target is set to the surface water production rate as defined by item (5) on the WCONHIST keyword. GRAT: the target is set to the surface gas production rate as defined by item (6) on the WCONHIST keyword. LRAT: the target is set to the surface liquid (oil plus water) production rate and is calculated by the simulator using (4) and (5) on the WCONHIST keyword. RESV: the target is set to the in situ reservoir volume rate and is calculated by the simulator using items (4), (5) and (6) on the WCONHIST keyword. BHP: the target rate is set to the bottom-hole pressure as defined by item (10) on the WCONHIST keyword. NONE: revert back to the TARGET control mode on the WCONHIST keyword. The TARGET control mode defined on this keyword resets the TARGET control mode on the WCONHIST keyword in the SCHEDULE section, from the time the WHISTCTL is invoked, thus avoiding changing the control model on all subsequent WCONHIST keywords.","units":{},"default":"None","value_type":"STRING","options":["ORAT","WRAT","GRAT","LRAT","RESV","BHP","NONE"]},{"index":2,"name":"END","description":"A defined character string that defines if the simulation should terminate if the well has switch to BHP control by the simulator, and should be set to one of the following character strings: NO: no action is taken and the run continues. YES: terminate the run at the next report time step. Wells set to BHP control via the WCONHIST or WHISCTL keywords are ignored. Only END equal to NO is currently supported in OPM Flow.","units":{},"default":"NO","value_type":"STRING","options":["NO","YES"]}],"example":"The example below shows the observed gas rates for the OP01 oil producer for the first quarter of 2000.\n-- ------------------------------------------------------------------------------\n-- 01 JAN 2000 START OF SCHEDULE SECTION\n-- ------------------------------------------------------------------------------\n--\n-- DEFINE WELL HISTORICAL TARGET PHASE\n--\n-- CNTL BHP\n-- MODE STOP\nWHISTCTL\nRESV NO /\n--\n-- WELL HISTORICAL PRODUCTION CONTROLS\n--\n-- WELL OPEN/ CNTL OIL WAT GAS VFP VFP THP BHP\n-- NAME SHUT MODE RATE RATE RATE TABLE ALFQ PRES PRES\nWCONHIST OP01 OPEN ORAT 15.5E3 100.0 1550 10 1* 900.0 1* /\n/ DATES\n01 FEB 2000 /\n/\n--\n-- WELL HISTORICAL PRODUCTION CONTROLS\n--\n-- WELL OPEN/ CNTL OIL WAT GAS VFP VFP THP BHP\n-- NAME SHUT MODE RATE RATE RATE TABLE ALFQ PRES PRES\nWCONHIST OP01 OPEN ORAT 15.2E3 150.0 1520 1* 1* 875.0 3250.0 /\n/ DATES\n01 MAR 2000 /\n/\n--\n-- WELL HISTORICAL PRODUCTION CONTROLS\n--\n-- WELL OPEN/ CNTL OIL WAT GAS VFP VFP THP BHP\n-- NAME SHUT MODE RATE RATE RATE TABLE ALFQ PRES PRES\nWCONHIST OP01 OPEN ORAT 15.0E3 200.0 1500 1* 1* 850.0 1* /\n/\nFrom January 1, 2000 the WCONHIST keyword defines well OP01, which is open and is on oil rate control, to produce 15,500 stb/d oil, with the observed rates of 100 stb/d of water and 15.5 MMscf/d of gas. However the WHISCTL keyword resets the target control to reservoir voidage from January 1, 2000 and onward. This is useful in initial history matching runs to get a “reasonable” pressure match, by ensuring that the total reservoir withdrawals are correct, although the individual phase withdrawals will not match. Once a reasonable pressure match is achieved for the reservoir then one can reset TARGET to the sales phase, OIL or GAS, and continue with the matching of all the phases.","expected_columns":2,"size_kind":"fixed","size_count":1},"WHTEMP":{"name":"WHTEMP","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, WHTEMP, sets the parameters for the Tubing Head Temperature calculation, which can either be a constant value, or from a table lookup using a VFPPROD table, via the VFPPROD keyword in the SCHEDULE section, containing tubing head temperature data.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well production targets and constraints data are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"VFPTAB","description":"A positive integer greater than or equal to zero that references the production vertical lift performance table (VFPPROD), containing the tubing head temperature data for the well. Note, a well must have both a VFPPROD pressure and a VFPPROD temperature table, if the tubing head temperatures are to be calculated. Alternatively, if a constant tubing head temperature for a production well is to be defined via the TEMP parameter, then VFPTAB should be defaulted with 1* instead.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"INT"},{"index":3,"name":"TEMP","description":"A real positive value greater than zero that defines a constant tubing head temperature for a production well. In this case the VFPTAB parameter should be defaulted with 1* if a constant tubing head temperature for a production well.","units":{"field":"oF","metric":"oC","laboratory":"oC"},"default":"None","value_type":"DOUBLE","dimension":"Temperature"}],"example":"The following example defines three wells tubing head temperature parameters using the WHTEMP keyword\n--\n-- DEFINE WELL TUBING HEAD TEMPERATURE PARAMETERS\n--\n-- WELL VFP TUB\n-- NAME TABLE TEMP\nWHTEMP\nOP01 5 /\nOP02 1* 150 /\nOP03 5 /\n/\nHere, well OP01 and OP03 used VFPPROD table number five to calculate the tubing head temperature, and well OP02’s uses a constant 150o tubing head temperature.","expected_columns":3,"size_kind":"list"},"WINJCLN":{"name":"WINJCLN","sections":["SCHEDULE"],"supported":null,"summary":"The WINJCLN keyword signals that a filter cake should be completely or partially cleaned – this effectively multiplies the accumulated filter cake skin.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the filter cake properties are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"FCLNFRAC","description":"A real positive value between 0 and 1 that defines the fraction of filter cake permeability (skin factor) to be removed. The accumulated filter cake skin factor for matching connections will be multiplied by (1 – FCLNFRAC), so the default value of 1 will completely clean the filter cake.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1","value_type":"DOUBLE","dimension":"1"},{"index":3,"name":"I","description":"An integer that defines the matching connection location in the I-direction. If set to < 1 then all connections in the I-direction that also satisfy J and K criteria are selected.","units":{},"default":"-1","value_type":"INT"},{"index":4,"name":"J","description":"An integer that defines the matching connection location in the J-direction. If set to < 1 then all connections in the J-direction that also satisfy I and K criteria are selected.","units":{},"default":"-1","value_type":"INT"},{"index":5,"name":"K","description":"An integer that defines the matching connection location in the K-direction. If set to < 1 then all connections in the K-direction that also satisfy I and J criteria are selected.","units":{},"default":"-1","value_type":"INT"}],"example":"The following example signals the filter cake clean up for water injection wells using WINJCLN:\n--\n-- WELL FILTER CAKE CLEAN UP\n--\n-- WELL CLEAN --LOCATION--\n-- NAME FRAC II JJ KK\nWINJDAM\nINJ-A1 0.4 0 0 3 /\nINJ-A1 0.4 0 0 4 /\nINJ-B* 0.9 /\n/\nIn well INJ-A1 forty percent of the filter cake is cleaned up in well connections in layers 3 and 4 (filter cake skin is multiplied by 0.6). In wells matching INJ-B* ninety percent of the filter cake is cleaned up in all well connections (filter cake skin is multiplied by 0.1).","expected_columns":5,"size_kind":"list"},"WINJDAM":{"name":"WINJDAM","sections":["SCHEDULE"],"supported":null,"summary":"The WINJDAM keyword defines filter cake properties for wells that have previously been defined by the WELSPECS keyword in the SCHEDULE section. This keyword must be accompanied by the WINJFCNC keyword to define the injected filtrate concentration.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the filter cake properties are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"GEOMETRY","description":"A defined character string that the filter cake geometry of the well. GEOMETRY must be set to one of the following character strings: LINEAR: the filter cake model will assume a linear geometry. RADIAL: the filter cake model will assume a radial geometry.","units":{},"default":"None","value_type":"STRING","options":["LINEAR","RADIAL"]},{"index":3,"name":"FCPERM","description":"A real positive value that defines the filter cake permeability.","units":{"field":"mD","metric":"mD","laboratory":"mD"},"default":"None","value_type":"DOUBLE","dimension":"Permeability"},{"index":4,"name":"FCPORO","description":"A real positive value that defines the filter cake porosity.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.3","value_type":"DOUBLE","dimension":"1"},{"index":5,"name":"FCRADIUS","description":"Well radius to use in skin factor calculations. If FCRADIUS is defaulted then half the diameter from the COMPDAT keyword item 9 will be used if it is defined otherwise 0.5 feet will be used.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"0.5 feet","value_type":"DOUBLE","dimension":"Length"},{"index":6,"name":"FCAOF","description":"A real positive value that defines the flow area for each connection. If FCAOF is defaulted then the value will be evaluated as 2πrwh, where rw is equal to FCRADIUS, and h is evaluated using the permeability thickness kh value from the COMPDAT keyword item 10 and the permeability FCPERM item 3 above.","units":{"field":"ft2","metric":"m2","laboratory":"cm2"},"default":"2πrwh","value_type":"DOUBLE","dimension":"Length*Length"},{"index":7,"name":"I","description":"An integer that defines the matching connection location in the I-direction. If set to < 1 then all connections in the I-direction that also satisfy J and K criteria are selected.","units":{},"default":"-1","value_type":"INT"},{"index":8,"name":"J","description":"An integer that defines the matching connection location in the J-direction. If set to < 1 then all connections in the J-direction that also satisfy I and K criteria are selected.","units":{},"default":"-1","value_type":"INT"},{"index":9,"name":"K","description":"An integer that defines the matching connection location in the K-direction. If set to < 1 then all connections in the K-direction that also satisfy I and J criteria are selected.","units":{},"default":"-1","value_type":"INT"}],"example":"The following example defines the filter cake properties for a water injection well using WINJDAM:\n--\n-- WELL FILTER CAKE PROPERTIES\n--\n-- WELL LINEAR/ PERM PORO WELL FLOW --LOCATION--\n-- NAME RADIAL RAD AREA II JJ KK\nWINJDAM\nINJ LINEAR 10 0.32 /\nINJ RADIAL 1 0.25 1* 1* 0 0 3 /\n/\nWell INJ initially has a linear filter cake model for all completions with permeability of 10 mD, porosity of 0.32, and default well radius and flow area based on data from the COMPDAT keyword. This is then overwritten for completions in layer 3 with a radial filter cake model with permeability of 1 mD and porosity of 0.25 (again with default well radius and flow area).","expected_columns":9,"size_kind":"list"},"WINJFCNC":{"name":"WINJFCNC","sections":["SCHEDULE"],"supported":null,"summary":"The WINJFCNC keyword defines the injected filtrate concentration for wells that have previously been defined by the WELSPECS keyword in the SCHEDULE section.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the filter cake properties are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"FCONCPPM","description":"A real positive value that defines the volumetric concentration of filtrate in the injected water. This value may be specified using a User Defined Argument (UDA).","units":{"field":"ppm","metric":"ppm","laboratory":"ppm"},"default":"0","value_type":"UDA","dimension":"PPM"}],"example":"The following example defines the filtrate injection concentration for a water injection well using WINJFCNC:\n--\n-- WELL FILTRATE INJECTION CONCENTRATION\n--\n-- WELL FILTRATE\n-- NAME CONC\nWINJFCNC\nINJ-A1 10 /\nINJ-B* 30 /\n/\nWell INJ-A1 has a filtrate concentration of 10 ppm in the injection water, and wells matching INJ-B* have a concentration of 30 ppm.","expected_columns":2,"size_kind":"list"},"WINJGAS":{"name":"WINJGAS","sections":["SCHEDULE"],"supported":true,"summary":"The WINJGAS keyword defines the properties of the injection gas stream, for a given well. Once a gas well stream has been defined via the WELLSTRE keyword in the RUNSPEC section, it can be used with either the WINJGAS or GINJGAS keywords, to set the injected gas composition. Similarly, if an oil well stream has been defined by WELLSTRE, then the well stream can be used with the WINJOIL keyword in the SCHEDULE section, to specify the injected oil composition. Note that, it is unnecessary to use WINJGAS for wells subordinate to a group having gas injection control, with the gas properties set by GINJGAS keyword in the RUNSPEC section. In this case the injection stream is defined by the GINJGAS keyword. However, if a gas injection well under group control users the WINJGAS keyword, then this fluid, and not the group's fluid will be injected instead, at a rate controlled by the group.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the injection well name, for which the gas injection properties are being specified. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"STREAM","description":"A defined character string that determines the properties of the injection gas, and as should be set to one of the following values: GAS: The field separator gas composition is used as the injected gas. GRUP: The well's group or upstream group injection fluid is used as the injected gas. GV: This option enables the vapor production of a group, as declared via the SOURCE parameter on this record, to be used as the injected gas composition. MIX: In this case, the gas injection composition is taken from either the WINJMIX or WINJORD keywords in the SCHEDULE section, with the name of injected fluid given by the SOURCE parameter on this record. STREAM: Here the gas injection composition is given by the WELLSTRE keyword in the SCHEDULE section, with the name of injected fluid given by the SOURCE parameter on this record. WV: This option enables the vapor production from a given well to be used as the injected gas, with the name of the well given by the SOURCE parameter on this record. Only the STREAM option is supported by OPM Flow.","units":{},"default":"GRUP","value_type":"STRING"},{"index":3,"name":"SOURCE","description":"A character string of up to eight characters in length, that defines the source of the gas injection stream, based on the value of STREAM. If STREAM equals GV, then source should be set to a group name. For STREAM equal to MIX or STREAM, then SOURCE should be set to the name of the gas stream, as defined by the WINJMIX, WINJORD, or WELLSTRE keywords.","units":{},"default":"None","value_type":"STRING"},{"index":4,"name":"MAKEUP","description":"The name of the well stream used for the make-up gas, if make-up gas is required for WELNAME to match the injection target for the well. This option is not supported by OPM Flow.","units":{},"default":"None","value_type":"STRING"},{"index":5,"name":"STAGE","description":"STAGE defines the separator stage from which the injection gas should be taken from. In this case, the vapor phase from any stage may be used, and the default value of zero users the total vapor phase from the separator. This option is not supported by OPM Flow.","units":{},"default":"0","value_type":"DOUBLE","dimension":"1"}],"example":"The following example defines how to specify a two component formulation, together with defining the names of the composition components, to be used with the CO2STORE and GASWAT options.\n-- ==============================================================================\n--\n-- PROPS SECTION\n--\n-- ==============================================================================\nPROPS --\n-- CONFIRM NUMBER OF COMPOSITIONAL COMPONENTS (OPM FLOW KEYWORD)\n--\nNCOMPS\n2 /\n--\n-- DEFINE COMPOSITIONAL COMPONENTS NAMES (OPM FLOW KEYWORD)\n--\nCNAMES\n'CO2'\n'H2O' /\nThe second part of the example, defines the well stream for the above two component CO2 water system.\n-- ==============================================================================\n--\n-- SCHEDULE SECTION\n--\n-- ==============================================================================\nSCHEDULE\n--\n-- WELL STREAM INJECTION COMPOSITION (OPM FLOW Keyword)\n--\n-- WELL -- WELL STREAM COMPOSITIONAL COMPONENT --\n-- STREAM -- MOLE FRACTIONS --\nWELLSTRE\n'C02STREAM' 1.000 0.000 /\n/\n--\n-- WELL GAS INJECTION PROPERTIES\n--\n-- WELL STREAM SOURCE MAKEUP SEP\n-- NAME OPTION DEPTH GAS STAGE\nWINJGAS\nGI01 STREAM C02STREAM 1* 1* /\n/\nHere the well stream consists of 100% CO2 and zero water, with well GI01 using the gas injection properties as defined by the WELLSTRE keyword and allocated via the WINJGAS keyword.\nFinally, the gas injection rate is set via the WCONINJE keyword as shown below.\n--\n-- WELL INJECTION CONTROLS\n--\n-- WELL FLUID OPEN/ CNTL SURF RESV BHP THP VFP\n-- NAME TYPE SHUT MODE RATE RATE PRES PRES TABLE\nWCONINJE\nGI01 GAS OPEN RATE 10E4 1* 300 1* 1* /\n/\nThus, gas injector GI01 will inject 10 x 104 m3 of CO2 per day, assuming metric units.\n| Note This is an OPM Flow keyword used with OPM Flow’s CO2STORE and GASWAT keywords in the RUNSPEC section, and should not be confused with the more general version of the WINJGAS keyword used in the commercial compositional simulator. Secondly, although OPM Flow parses the keyword, the simulator currently ignores the data for this keyword. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":5,"size_kind":"list"},"WINJMULT":{"name":"WINJMULT","sections":["SCHEDULE"],"supported":null,"summary":"The WINJMULT keyword defines pressure dependent injectivity multipliers for injection wells and can be used to approximate the increase or decrease in a well’s injectivity due to hydraulic fracturing in water injection wells. Only injection wells are processed by this keyword, even if production wells have been entered by the keyword.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well connection data are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"FRACPRES","description":"FRACPRES is the fracture opening pressure (Pfractue) used in equation 12.3.296.1.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":"Pressure"},{"index":3,"name":"ALPHA","description":"ALPHA is the multiplier gradient, α, in equation 12.3.296.1.","units":{"field":"1/psia 0.0","metric":"1/barsa 0.0","laboratory":"1/atma 0.0"},"default":"Defined","value_type":"DOUBLE","dimension":"1/Pressure"},{"index":4,"name":"OPTION","description":"A defined character string that determines how the data on this keyword is applied, and should be set to one of the following character strings: CIRR: The injectivity multiplier as applied to the selected connections (I, J, K) is irreversible, and the pressure at the connection’s sand face (Pwbhp) is used in equation 12.3.296.1, instead of the well’s flowing bottom-hole pressure. This option means that even if the pressures in the wellbore, and therefore the sand face pressures, later declines, injectivity remains unchanged for all the connections. CREV: The injectivity multiplier as applied to the selected connections (I, J, K) is reversible, and the pressure at the connection’s sand face is used in equation 12.3.296.1, The reversibility of this option means that if the pressures in the wellbore, and therefore the sand face pressures, later declines, injectivity will also decline for all the connections. WREV: The injectivity multiplier as applied to all connections in the well is reversible, and the wells’ flowing bottom-hole pressure (Pwbhp) is used in equation 12.3.296.1, instead of the pressure at the connection’s sand face. The connections stipulated by (I, J, K) are ignored. The reversibility of this option means that if the pressures in the wellbore, later declines, injectivity will also decline for all the connections.","units":{},"default":"WREV","value_type":"STRING"},{"index":5,"name":"I","description":"An integer value less than or equal to NX that defines the connection location in the I-direction. If set to zero, a negative value, or defaulted with 1* then all connections in the I-direction will be multiplied by ALPHA, depending on the selected OPTION value.","units":{},"default":"1*","value_type":"INT"},{"index":6,"name":"J","description":"An integer value less than or equal to NY that defines the connection location in the J-direction. If set to zero, a negative value, or defaulted with 1* then all connections in the J-direction will be multiplied by ALPHA, depending on the selected OPTION value.","units":{},"default":"1*","value_type":"INT"},{"index":7,"name":"K","description":"An integer value less than or equal to NZ that defines the connection location in the K-direction. If set to zero, a negative value, or defaulted with 1* then all connections in the K-direction will be multiplied by ALPHA, depending on the selected OPTION value.","units":{},"default":"1*","value_type":"INT"}],"example":"The example below show the WINJMULT keyword for three water injection wells.\n--\n-- DEFINE WELL CONNECTION MULTIPLIERS\n--\n-- WELL FRAC MULT FRAC --LOCATION--\n-- NAME PRES VALUE OPTN I J K\nWINJMULT\nWI01 4200 0.0250 1* 1* 1* 1* /\nWI02 4250 0.0025 CIRR 1* 1* 145 /\nWI02 4250 0.0025 CIRR 1* 1* 146 /\nWI02 4250 0.0025 CIRR 1* 1* 147 /\nWI03 4400 0.0055 CREV 1* 1* 160 /\nWI03 4400 0.0055 CREV 1* 1* 165 /\n/\nThe first well, WI01, uses the default value for OPTION, that is WREV, which means that the injectivity multiplier will be applied to all the connections in the well and the well’s bottom-hole pressure is used in the calculation. In this case the process is reversible. The second well, WI02, applies the injectivity multiplier to all connections in layers 145 to 147 using the sand face pressures in the calculation, and the process is irreversible. Finally for well WI03, the multiplier is applied to all connections in layers 160 and 165 using the sand face pressures in the calculation, and in this case the process is reversible.\n| [matrix{ \nalignr Multiplier {}={} # 1.0 `+` %alpha ` left( P_WBHP `` - `` P_fracture right) #alignl \" for \" {P sub WBHP} `>` {P sub fracture} \n##\nalignr Multiplier {}={} # 1.0 # alignl \" for \" {P sub WBHP} `<` {P sub fracture}\n}] | (12.3.296.1) |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|\n| Note If all the connection parameters (I, J, K) are defaulted, or OPTION is set equal to WREV, then the multiplier is applied to all connections in the well. If any of the connection parameters (I, J, K) have positive values and OPTION is set equal to CIRR or CREV, then the multiplier is applied to the selected connections as determined by the (I, J, K) parameters. |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":7,"size_kind":"list"},"WINJTEMP":{"name":"WINJTEMP","sections":["SCHEDULE"],"supported":true,"summary":"WINJTEMP defines the injection fluid thermal properties for when the thermal option has been activated by the THERMAL keyword in the RUNSPEC section. Only water and gas injection is supported.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well injection fluid thermal properties are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"STEAMQAL","description":"STEAMQAL is a real positive value greater than or equal to zero and less than or equal to one that defines the steam quality of the injected fluid for the defined well. This parameter should be defaulted using 1* as STEAMQAL is not used by OPM FLOW, as only water and gas injection is supported. This data is used by the commercial simulator’s THERMAL option and is not supported by OPM Flow’s THERMAL option.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1*","value_type":"DOUBLE"},{"index":3,"name":"TEMP","description":"TEMP is a real positive value that defines the temperature of the injected fluid for the defined well.","units":{"field":"oF","metric":"oC","laboratory":"oC"},"default":"None","value_type":"DOUBLE","dimension":"Temperature"},{"index":4,"name":"PRES","description":"PRES is a real positive value that defines the pressure of the injected fluid for the defined well.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"None","value_type":"DOUBLE","dimension":"Pressure"},{"index":5,"name":"ENTHALPY","description":"ENTHALPY is a real positive value that defines the specific enthalpy of the injected fluid for the defined well. This is data is used by the commercial simulator’s THERMAL option and is not supported by OPM Flow’s THERMAL option.","units":{"field":"Btu/lbs-M","metric":"kJ/kg-M","laboratory":"J/gm-M"},"default":"None","value_type":"DOUBLE","dimension":"Energy/Mass"}],"example":"The following example shows the WINJTEMP keyword for when OPM Flow’s temperature option has been activated by the THERMAL keyword in the RUNSPEC section.\n--\n-- INJECTION FLUID THERMAL PROPERTIES\n--\n-- WELL STEAM INJ INJ SPEC\n-- NAME QUAL TEMP PRES ENTH\nWINJTEMP\nWI01 1* 68.0 220.0 1* /\nWI02 1* 70.0 230.0 1* /\n/\nHere the water injection fluid’s temperature and pressure, in field units, for two water injections well are defined. Notice that both the steam quality and the specific enthalpy of the injected fluid for the defined wells are defaulted (or skipped), as OPM Flow’s THERMAL option does not support this data.","expected_columns":5,"size_kind":"list"},"WLIFT":{"name":"WLIFT","sections":["SCHEDULE"],"supported":null,"summary":"The WLIFT defines the automatic workovers parameters for changing out wellbore tubing, changing the THP limit (for example switching from the high stage pressure separator to the low stage pressure separator), or changing the artificial lift parameters, for wells.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"TRIGGER_LIMIT","description":"The dimension here depends on the phase - must be handled in the application","units":{},"default":"","value_type":"DOUBLE"},{"index":3,"name":"TRIGGRE_PHASE","description":"","units":{},"default":"","value_type":"STRING"},{"index":4,"name":"NEW_VFP_TABLE","description":"","units":{},"default":"","value_type":"INT"},{"index":5,"name":"NEW_ALQ_VALUE","description":"The dimension here depends on the phase - must be handled in the application","units":{},"default":"","value_type":"DOUBLE"},{"index":6,"name":"NEW_WEFAC","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":7,"name":"WWCT_LIMIT","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":8,"name":"NEW_THP_LIMIT","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":9,"name":"WGOR_LIMIT","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":10,"name":"ALQ_SHIFT","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":11,"name":"THP_SHIFT","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"}],"example":"","expected_columns":11,"size_kind":"list"},"WLIFTOPT":{"name":"WLIFTOPT","sections":["SCHEDULE"],"supported":null,"summary":"The WLIFTOPT defines which wells should use the Gas Lift Optimization facility in order to maximize oil production, as well as defining the associated gas lift optimization parameters for a given well. The keyword can also be used to switch off gas lift optimization for a well. Gas lift optimization is invoked via the LIFTOPT keyword in the SCHEDULE section. Note that the LIFTOPT keyword should precede the WLIFTOPT keyword in the SCHEDULE section in order to activate the gas lift optimization facility.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well gas lift optimization parameters are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"OPTLIFT","description":"A defined character string that sets if a well’s gas lift gas rate should be calculated by the gas lift optimization facility or not, and should be set to: NO: In this case the gas lift gas is a constant determined from the MXLIFT variable on this keyword, the ALQ-WELL variable on the WCONPROD keyword, or the TARGET and VALUE variables on the WELTARG keyword. YES: Activates the gas lift optimization for the given well.","units":{},"default":"None","value_type":"STRING"},{"index":3,"name":"MXLIFT","description":"A real value that defines the total amount of gas lift gas available for this well, multiplied by the well’s efficiency factor. If OPTLIFT is defined as NO then MXLIFT is considered a fixed gas lift gas rate. However, if MXLIFT is defaulted (1*) then MXLIFT is unchanged from the previously entered value. If OPTLIFT equals YES and MXLIFT is defaulted (1*), then MXLIFT is taken from the largest value of the ALQ variable on the well’s associated VFPPROD table. Note that the value entered here should be in the range entered in the VFPPROD table allocated to the well, otherwise errors may occur when optimizing the gas lift gas injection rate for the well.","units":{"field":"Mscf/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"1*","value_type":"DOUBLE","dimension":"GasSurfaceVolume/Time"},{"index":4,"name":"OPTWGT","description":"OPTWGT (βw) is real positive value that defines a weighting factor for allocating the available gas lift gas to a well. An increment of gas lift gas supply is allocated to a well based on the well’s current incremental gradient multiplied by OPTWGT using the following formulae: [Gradient`=` left ( left ( %beta _w times %DELTA Q_Oil right ) over left (%DELTA Q_GasLift``+`` %beta_g times %DELTA Q_Gas right) right)] Where: βw = is OPTWGT, the weighting factor for the preferential allocation of lift gas, βg = is the gas production rate weighting factor, ∆QOil = is the increment/decrement in oil production rate, ∆Qgas = is the increment/decrement in gas production rate, and ∆QGasLift = is the increment/decrement in gas lift gas rate. Note by default βg, the gas production rate weighting factor, is set to zero, and therefore the gradient equation simplifies to: [Gradient`=` left ( { %beta _w times %DELTA Q_Oil } over {%DELTA Q_GasLift} right)] OPTWGT is ignored if OPTLIFT is equal to NO.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1","value_type":"DOUBLE"},{"index":5,"name":"MINGAS","description":"A real value that defines the minimum amount of gas lift gas available to the well, multiplied by the well’s efficiency factor. The allocation of the gas lift gas is determined by: If MINGAS is a positive value then this value is allocated to the well unless the well is unable flow with this quantity of gas lift gas. Alternatively, if the well is able to meet it’s target rate without applying MINGAS, then the MINGAS rate is not applied to the well. If MINGAS is a negative value, then the well is supplied with sufficient gas lift gas to allow the well to flow, subject to the maximum allowed gas lift quantity, as per MXLIFT variable on this keyword. The negative value itself is not used in any calculations. If there is insufficient available gas lift gas, the wells are assigned values of MINGAS based on the decreasing order of their weighting factors as calculated per OPTWGT variable. Wells belonging to groups that can meet their production targets without gas lift, will have their MINGAS values not applied, that is no gas lift is applied. The exception is that if OPTWGT has been set to a value greater than or equal to one, then the well will use the MINGAS value for it’s gas lift gas, even if the group’s target can be satisfied without gas lift. However, if both the well’s group and the well can meet their production targets, then MINGAS will not be applied. This parameter is ignored if OPTLIFT is defined as NO.","units":{"field":"Mscf/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"0.0","value_type":"DOUBLE","dimension":"GasSurfaceVolume/Time"},{"index":6,"name":"OPTGAS","description":"OPTGAS (βg) is real positive value that defines the incremental gas weighting factor for allocating the available gas lift gas to a well. An increment of gas lift gas supply is allocated to a well based on the well’s current incremental gradient as described by the definition of the OPTWGT (βg) variable above, that is by the following formulae: [Gradient`=` left ( left ( %beta _w times %DELTA Q_Oil right ) over left (%DELTA Q_GasLift``+`` %beta_g times %DELTA Q_Gas right) right)] See OPTWGT for a definition of the variables in the equation. This parameter is ignored if OPTLIFT is defined as NO.","units":{"field":"dimensionless1","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.0","value_type":"DOUBLE"},{"index":7,"name":"OPTLIMIT","description":"A defined character string that defines if additional gas lift gas should be applied to the well, if the well’s group gas target has been satisfied but the group’s oil rate limit has not been achieved. NO: Additional gas lift gas is not available for the given well. YES: Additional gas lift gas is available for the given well. In cases where a well receiving additional gas lift may cause the well’s group to exceed the group’s gas target, normally the well will not be assigned the additional gas lift gas. However, if OPTLIMIT is set to YES, then this constraint is removed. This results in the gas lift optimization procedure continuing to maximize the oil rate, subject to available constraints. However, upon completion of the optimization process, applying the group controls may negate the gain from the gas lift optimization process. This parameter is ignored if OPTLIFT is defined as NO.","units":{},"default":"NO","value_type":"STRING"}],"example":"The following example first switches on gas lift optimization via the LIFTOPT keyword and then defines the artificial lift constraints for PLAT-A, using the GLIFTOPT keyword and sets the well gas lift parameters using the WLIFTOPT keyword.\n-- ACTIVATE GAS LIFT OPTIMIZATION AND PARAMETERS\n--\n-- INCR INCR TSTEP NEWTON\n-- GAS OIL INTVAL OPTN\nLIFTOPT\n12.5E3 5E-3 0.0 YES /\n/\n--\n-- GROUP GAS LIFT OPTIMIZATION CONSTRAINTS\n--\n-- GRUP MAX MAX\n-- NAME GAS ALQ TOTAL GAS\nGLIFTOPT\nPLAT-A 200E3 1* /\n/\n--\n-- WELL GAS LIFT OPTIMIZATION PARAMETERS\n--\n-- WELL OPTN MAX WEIGHT MIN GAS OPTN\n-- NAME LIFT LIFT FACTOR LIFT FACTOR LIMIT\nWLIFTOPT\nOP01 YES 150E3 1.01 -1.0 /\nOP02 YES 150E3 1.01 -1.0 /\nOPO3 YES 150E3 1.01 -1.0 /\nOP04 YES 150E3 1.01 -1.0 /\nOP05 YES 150E3 1.01 -1.0 /\n/\nHere the LIFTOPT keyword defines the maximum incremental gas lift gas quantity to be 12.5 x 103 m3, the minimum incremental oil gain per m3 of gas lift gas is set to 5.0 x 10-3 m3, the time step interval is set to zero to perform the gas optimization every time step, and finally the gas lift optimization will be performed NUPCOL Newton iterations for the time step.\nThe GLIFTOPT keyword sets the maximum amount of gas lift gas for PLAT-A to 200,000 m3 and there is no maximum limit for the total maximum amount of gas that the group can process. In addition, WLIFTOPT sets all five wells to have gas lift gas optimization implemented with a maximum gas lift gas value of 150,000 m3 per well, with equal weighting factors and all wells are supplied with sufficient gas lift gas to allow the wells to flow, (minimum lift set to a negative value) subject to the maximum allowed gas lift quantity for the well (150,000 m3).","expected_columns":7,"size_kind":"list"},"WLIMTOL":{"name":"WLIMTOL","sections":["SCHEDULE"],"supported":false,"summary":"WLIMTOL keyword defines the tolerance to be used for various constraints applied to connections, completions (if connections have been lumped via the COMPLUMP keyword in the SCHEDULE section), wells, and groups, including the field group. See also the GCONTOL keyword in the SCHEDULE section that sets the tolerance parameters for groups.","parameters":[{"index":1,"name":"TOLERANCE_FRACTION","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"WLIST":{"name":"WLIST","sections":["SCHEDULE"],"supported":null,"summary":"WLIST declares a group of wells to belong to a named static well list. Wells in a named well list are treated as a group of wells for which the standard well keywords can be applied. For example, instead of repeating a well keyword for each well, the keyword only needs to have the named well list instead, for the action to be applied to all wells in the named well list. In general any well keyword that allows well name roots as a well name, for example, PROD*, can use a named well list.","parameters":[{"index":1,"name":"WLIST","description":"A character string of up to eight characters in length, enclosed in quotes, that defines the well list name for the WELNAMES declared by this record. Note the first character must be asterisk (“*”) and the second character must be a letter, for example, *PROD.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"ACTION","description":"A defined character string that determines how the WELNAMES should be handled with respect to the named well list (WLIST). ACTION should be set to one of the following:: ADD: Add the WELNAMES to an existing WLIST. DEL; Delete WELNAMES from an existing WLIST. MOV: WELNAMES from another existing named well list and ADD them to WLIST. NEW: Define a new named well list and add the WELNAMES to WLIST.","units":{},"default":"","value_type":"STRING"},{"index":"3-52","name":"WELNAMES","description":"A character string of up to eight characters in length that defines the well name that belongs to the named well list (WLIST). A total of 50 well names can be added to WLIST at a time. If additional wells are needed to added then use the ADD option of ACTION to add additional wells. Well names roots may all be used in WELNAMES as long as they are enclosed in quotes and end with an asterisk (“*”). In this case all wells that match the specification will be added to the list. For example, wells named OP01, OP02 and OP03, can be added as group by using “OP*” as the well name. Note that the well names must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur","units":{},"default":"","value_type":"STRING"}],"example":"The following example defines two named well lists using the WLIST keyword.\n--\n-- WELL LIST SPECIFICATION\n--\n-- LIST OPER WELL NAME LIST\n-- NAME\nWLIST\n'*BLK-1' NEW WEL-01M WEL-02M WEL-03M WEL-04M WEL-05M WEL-06M WEL-07M /\n'*BLK-1' ADD WEL-08M WEL-09M WEL-10M WEL-11M WEL-12M WEL-13M WEL-14M /\n'*BLK-1' ADD WEL-15M WEL-16M WEL-17M WEL-18M WEL-19M WEL-20M WEL-23M /\n'*BLK-1' ADD WEL-24M WEL-25M WEL-26M WEL-28M /\n'*BLK-2' NEW WEL-03U WEL-05U WEL-06U WEL-10U WEL-11U WEL-13U WEL-14U /\n'*BLK-2' ADD WEL-15U WEL-16U WEL-17U WEL-18U WEL-19U WEL-25U WEL-27U /\n/\nDATES\n1 JAN 2020 /\n/\n--\n-- DEFINE WELL AND WELL CONNECTIONS FLOWING STATUS\n--\n-- WELL WELL --LOCATION-- COMPLETION\n-- NAME STAT I J K FIRST LAST\nWELOPEN\n'*BLK-1' OPEN /\n'*BLK-1' OPEN 0 0 0 0 0 /\n/\nDATES\n1 JAN 2021 /\n1 JLY 2021 /\n1 OCT 2021 /\n/\n--\n-- DEFINE WELL AND WELL CONNECTIONS FLOWING STATUS\n--\n-- WELL WELL --LOCATION-- COMPLETION\n-- NAME STAT I J K FIRST LAST\nWELOPEN\n'*BLK-2' OPEN /\n'*BLK-2' OPEN 0 0 0 0 0 /\n/\nIn this example the wells in named well list ‘’*BLK-1” are opened on January 1, 2020 and wells in named well list ’*BLK-2” are opened October 1, 2021.","size_kind":"list","variadic_record":true},"WLISTARG":{"name":"WLISTARG","sections":["SCHEDULE"],"supported":false,"summary":"The WLISTARG keyword modifies the target and constraint values of both rates and pressures for wells previously defined in a well list by the WLIST or WLISTNAM keywords. WLISTARG is similar to the WELTARG keyword in it that allows for modifying targets and constraints without having to define all the variables on the well control keywords: WCONPROD, WCONHIST, WCONINJE, or WCONINJH keywords. Variables not changed by the WLISTARG keyword remain the same as those previously entered via the well control keywords or previously entered WLISTARG keywords. Note that the well must still be initially be fully defined using the WCONPROD or WCONINJE keywords. All the aforementioned keywords are described in the SCHEDULE section.","parameters":[{"index":1,"name":"WLIST","description":"A character string of up to eight characters in length, enclosed in quotes, that defines the well list name declared by the WLIST keyword. Note the first character must be asterisk (“*”) and the second character must be a letter, for example, *PROD.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"TARGET","description":"A defined character string that sets the item to be changed for the well the value of the item is set by item (3). ORAT: reset the surface oil production rate value as defined by item (3). WRAT: reset the surface water production rate value as defined by item (3). GRAT: reset the surface gas production rate value as defined by item (3). LRAT: reset the surface liquid (oil plus water) production rate value as defined by (3). RESV: reset the in situ reservoir volume rate value as defined by (3). BHP: reset the bottom-hole pressure value as defined by item (3). THP: reset the tubing head pressure value for the well as defined by item (3). VFP: reset the vertical lift performance table number as defined by (3). LIFT: reset the artificial lift quantity for use with vertical lift performance tables. GUID: reset the guide rate value for wells operating under group control. Note TARGET only defines the variable to be changed, it does not change how a well is controlled. For example, if a well is operating on ORAT control, as defined by the previously entered WCONPROD keyword, entering TARGET equal to LRAT with a value, changes the liquid constraint but the well still remains on ORAT control. Use the WELCNTL keyword in the SCHEDULE section to change the control mode of a well.","units":{},"default":"None","value_type":"STRING","options":["ORAT","WRAT","GRAT","LRAT","RESV","BHP","THP","VFP","LIFT","GUID"]},{"index":3,"name":"VALUE Liquid Gas Res Vol Pressure VFP LIFT","description":"A real positive vector of values that defines the value of the variable declared by TARGET for all the wells contained in WLIST. For example if there are four wells in WLIST then there must four real numbers for VALUE. The vector should be terminated by a “/” as indicated in the notes below.","units":{"field":"stb/d Mscf/d rb/d psia dimensionless same as VFPPROD or VFPINJ","metric":"sm3/day sm3/day rm3/day barsa dimensionless same as VFPPROD or VFPINJ","laboratory":"scc/hour scc/hour rcc/hour atma dimensionless same as VFPPROD or VFPINJ"},"default":"None","value_type":"DOUBLE"}],"example":"The following example defines two named well lists using the WLIST keyword.\n--\n-- WELL LIST SPECIFICATION\n--\n-- LIST OPER WELL NAME LIST\n-- NAME\nWLIST\n'*BLK-1' NEW WEL-01M WEL-02M WEL-03M /\n'*BLK-2' NEW WEL-03U WEL-05U WEL-06U WEL-10U /\n/\n--\n-- WELL PRODUCTION AND INJECTION TARGETS\n--\n-- WELL WELL TARGET\n-- NAME TARG VALUE\nWLISTARG\n‘*BLK-1’ ORAT 2000.0 2000.00 2000.0 /\n‘*BLK-2’ ORAT 3000.0 3500.00 4000.0 2000.0 /\n/\nThe wells in the '*BLK-1' well list are all given an oil rate of 2,000 stb/d and wells in the '*BLK-2' well list are given rates of 3,000, 3,500, 4,000 and 2,000 stb/d.","size_kind":"list","variadic_record":true},"WLISTNAM":{"name":"WLISTNAM","sections":["SCHEDULE"],"supported":false,"summary":"WLISTNAM declares a group of wells to belong to a named WLISTARG well list for use with the WLISTARG keyword. Only the WLISTARG keyword can be used with this type of well list, and therefore it is better to use the WLIST keyword instead, that defines a static well list but offers more flexibility than a WLISTNAM well list.","parameters":[{"index":1,"name":"WLIST","description":"A character string of up to eight characters in length, enclosed in quotes, that defines the well list name for the WELLNAMES declared by this record. Note the first character must be asterisk (“*”) and the second character must be a letter, for example, *PROD.","units":{},"default":"None","value_type":"STRING"},{"index":"2-51","name":"WELNAMES","description":"A character string of up to eight characters in length that defines the well name that belongs to the named well list (WLIST). A total of 50 well names can be added to WLISTNAM at a time. If the first well name in the list is the default value (“*1”), then the list is first cleared of all wells, before adding the subsequent wells in WELLNAMES. Well names roots may all be used in WELLNAMES as long as they are enclosed in quotes and end with an asterisk (“*”). In this case all wells that match the specification will be added to the list. For example, wells named OP01, OP02 and OP03, can be added as group by using “OP*” as the well name. Note that the well names must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"1*","value_type":"STRING"}],"example":"The following example defines two named well lists using the WLISTNAM keyword.\n--\n-- WELL LIST SPECIFICATION\n--\n-- LIST WELL NAME LIST\n-- NAME\nWLISTNAM\n'*BLK-1' WEL-01M WEL-02M WEL-03M WEL-04M WEL-05M WEL-06M WEL-07M /\n'*BLK-1' WEL-08M WEL-09M WEL-10M WEL-11M WEL-12M WEL-13M WEL-14M /\n'*BLK-1' WEL-15M WEL-16M WEL-17M WEL-18M WEL-19M WEL-20M WEL-23M /\n'*BLK-1' WEL-24M WEL-25M WEL-26M WEL-28M /\n'*BLK-2' 1* WEL-03U WEL-05U WEL-06U WEL-10U WEL-11U WEL-13U WEL-14U /\n'*BLK-2' WEL-15U WEL-16U WEL-17U WEL-18U WEL-19U WEL-25U WEL-27U /\n/\nHere well list '’*BLK-1’ contains 28 wells, that is wells WEL-01M to WEL-28M. For the '*BLK-2' well list all wells are first deleted due to the “1*” default value and then wells WEL-03U to WEL-27U are added to the list.","size_kind":"list","variadic_record":true},"WMICP":{"name":"WMICP","sections":["SCHEDULE"],"supported":null,"summary":"The WMICP keyword defines a water injection well's microbial, growth, and cementation injection stream solutions, where the rate-limiting components are suspended microbes, oxygen, and urea concentrations respectively. These concentrations are used when the MICP keyword in the RUNSPEC section has been used to activate OPM Flow’s Microbially Induced Calcite Precipitation model. See Landa-Marbán et al331\n Landa-Marbán, D., Tveit, S., Kumar, K., Gasda, S.E., 2021. Practical approaches to study microbially induced calcite precipitation at the eld scale. Int. J. Greenh. Gas Control 106, 103256. https://doi.org/10.1016/j.ijggc.2021.103256. and 332\n Landa-Marbán, D., Kumar, K., Tveit, S., Gasda, S.E., 2021. Numerical studies of CO2 leakage remediation by micp-based plugging technology. In: Røkke, N.A. and Knuutila, H.K. (Eds) Short Papers from the 11th International Trondheim CCS conference, ISBN: 978-82-536-1714-5, 284-290.for a description of the model.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well connection data is being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"MICRCON","description":"MICRCON is a real positive value that defines the microbial concentration of the well’s injection stream.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"0.0","value_type":"DOUBLE","dimension":"Concentration"},{"index":3,"name":"OXYGCON","description":"A real positive value that defines the oxygen concentration of the well’s injection stream.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"0.0","value_type":"DOUBLE","dimension":"Concentration"},{"index":4,"name":"UREACON","description":"UREACON is a real positive value that defines the urea concentration of the well’s injection stream.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"0.0","value_type":"DOUBLE","dimension":"Concentration"}],"example":"--\n-- DEFINE WATER INJECTION WELL MICROBIAL, OXYGEN, AND UREA CONCENTRATIONS\n--\n-- WELL MICROBIAL OXYGEN UREA\n-- NAME MICRCON OXYGCON UREACON\n-- -------- -------- --------\nWMICP\nWI01 0.01 /\nWI02 1* 0.04 /\nWI03 1* 1* 60.0 /\nWI04 1* 0.04 60.0 /\n/\nHere the microbial concentration for well WI01 is set to 0.01, the oxygen concentration for well WI02 is set to 0.04, the urea concentration for well WI03 is set to 60, and the oxygen and urea concentrations for well WI04 are set to 0.04 and 60 respectively.\n| Note This is an OPM Flow specific keyword. |\n|--------------------------------------------|","expected_columns":4,"size_kind":"list"},"WNETCTRL":{"name":"WNETCTRL","sections":["SCHEDULE"],"supported":false,"summary":"The WNETCNTL keyword sets a well’s control mode that should remain fixed after each network balancing calculation, for when the either the Standard Network or the Extended Network options have been activated, and the well is part of a network. The keyword allows for a well’s Tubing Head Pressure (“THP”), oil, gas, liquid, or water rate to be selected as fixed after each network balance calculation. Normally this should be the THP, and if the keyword is absent from the input deck then THP will be used as the default value. The Standard Network option is invoked if the GRUPTREE, GRUPNET, GNETINJE, GNETPUMP, etc. series of keywords have been used in the SCHEDULE section. Whereas, the Extended Network option is activated by the NETWORK keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"CONTROL","description":"","units":{},"default":"THP","value_type":"STRING"}],"example":"","expected_columns":2,"size_kind":"list"},"WNETDP":{"name":"WNETDP","sections":["SCHEDULE"],"supported":false,"summary":"The WNETDP keyword allows for a constant pressure drop between a well’s Tubing Head Pressure (“THP”) and the well’s connecting network node, for when the either the Standard Network or the Extended Network options have been activated, and the well is part of a network. For production wells in a production network, WNETDP is added to the well’s connecting network node pressure to arrive at the well’s THP value. Whereas for injection wells in an injection network, WNETDP is subtracted from the well’s connecting network node pressure to arrive at the well’s THP value. The Standard Network option is invoked if the GRUPTREE, GRUPNET, GNETINJE, GNETPUMP, etc. series of keywords have been used in the SCHEDULE section. The Extended Network option is activated by the NETWORK keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"DP","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Pressure"}],"example":"","expected_columns":2,"size_kind":"list"},"WORKLIM":{"name":"WORKLIM","sections":["SCHEDULE"],"supported":false,"summary":"WORKLIM sets the numbers of days taken to complete a workover.","parameters":[{"index":1,"name":"LIMIT","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"WORKTHP":{"name":"WORKTHP","sections":["SCHEDULE"],"supported":false,"summary":"The WORKTHP keyword defines workover options for when a well dies, that is unable to produce at the current operating conditions, when under Tubing Head Pressure (“THP”) control. For example, if a well is producing to the high pressure separator and therefore has a high THP constraint, then the WORKTHP keyword can be used to switch the well to the lower pressure separator via re-setting the THP constraint.","parameters":[{"index":1,"name":"WELL_NAME","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"WORK_OVER_PROCEDURE","description":"","units":{},"default":"NONE","value_type":"STRING"}],"example":"","expected_columns":2,"size_kind":"list"},"WPAVE":{"name":"WPAVE","sections":["SCHEDULE"],"supported":false,"summary":"Not supported. It is used on Norne, but investigations showed no significant effect so we did not implement it.","parameters":[{"index":1,"name":"WPAVE1","description":"A real dimensionless value that defines the weighting factor between the inner block and the surrounding blocks used in the calculation of the connection factor weighted average pressure. If WPAVE1 is greater than or equal to zero and less than or equal to one, then the average pressure for each well connection is calculated based on this weighting factor. A value of zero indicates only the surrounding blocks should be used in the calculation; and a value of one indicates only the inner blocks should be used. If WPAVE1 is less than zero, then the average pressure for each well connection is weighted based on the pore volumes of the inner and surrounding blocks.","units":{},"default":"0.5","value_type":"DOUBLE"},{"index":2,"name":"WPAVE2","description":"A real dimensionless value greater than or equal to zero and less than or equal to one, that defines the weighting factor between the connection factor weighted average pressures and the pore volume weighted average pressures. If WPAVE2 is equal to one, then the average pressures are calculated based only on the connection factor weighted average pressures. If WPAVE2 is equal to zero, then average pressures are calculated based only on the pore volumes weighted average pressures.","units":{},"default":"1.0","value_type":"DOUBLE"},{"index":3,"name":"WPAVE3","description":"A defined character string that determines how the hydrostatic head calculation is performed in correcting the pressures to the BHP reference depth on the WELSPECS or WPAVEDEP keywords in the SCHEDULE section. WPAVE3 should be set to one of the following character strings: WELL: the hydrostatic head is calculated using the density of the fluid in the wellbore at the well connections. RES: he hydrostatic head is calculated using the density of the fluid in the reservoir with well connections and averaged over the connections. NONE: no hydrostatic correction is applied to the pressures.","units":{},"default":"WELL","value_type":"STRING","options":["WELL","RES","NONE"]},{"index":4,"name":"WPAVE4","description":"A defined character string that determines which connections should be used in the calculations, WPAVE4 should be set to one of the following character strings: OPEN: only open connections and associated grid blocks should be used in the calculations. This option may result in pressure discontinuities if connections are opened and closed during the run. ALL: all currently defined open and closed connections and associated grid blocks are used in the calculations. The pressure discontinuities issue mentioned above can be avoided with this option and defining all the well connections for a well at the beginning of the run. Only the OPEN option is currently supported by the simulator.","units":{},"default":"OPEN","value_type":"STRING","options":["OPEN","ALL"]}],"example":"The following example defines the default well block average pressure calculation parameters\n--\n-- DEFINE WELL BLOCK AVERAGE PRESSURE CALCULATION PARAMETERS\n--\n-- INNER PORV WELL OPEN\n-- OUTER CONN RES ALL\nWPAVE\n0.5 1.0 WELL ALL /\nAnd the next example shows the parameters used in the Norne model.\n--\n-- DEFINE WELL BLOCK AVERAGE PRESSURE CALCULATION PARAMETERS\n--\n-- INNER PORV WELL OPEN\n-- OUTER CONN RES ALL\nWPAVE\n1* 0.0 WELL ALL /\nHere only pore volume weighting is used instead of connection weighting.","expected_columns":4,"size_kind":"fixed","size_count":1},"WPAVEDEP":{"name":"WPAVEDEP","sections":["SCHEDULE"],"supported":null,"summary":"The WPAVEDEP keyword defines the reference depth to be used to calculate and report grid block average bottom-hole pressures for a well. This keyword can be used to override the values entered or defaulted on the WELSPECS keyword in the SCHEDULE section. The simulator corrects the grid block calculated pressures to a well’s reference depth using the hydrostatic well of the producing fluids.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well and well connection status data is being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"BHPREF","description":"A real value that defines the reference depth for reporting the bottom-hole pressure for the well. Ideally this value should be set to the midpoint of the perforations as defined by the COMPDAT keyword in the SCHEDULE section. If defaulted by 1* or set to a value less than or equal to zero, then the mid-point of shallowest connection defined by the COMPDAT keyword will be used.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"Mid-point of shallowest connection defined by the COMPDAT keyword","value_type":"DOUBLE","dimension":"Length"}],"example":"The following example illustrates how to set the bottom-hole reference depth for wells completed in different reservoirs that have different datum depths. Here it is assumed that all wells in a reservoir A have RES-A as part of their well name, and similarly for reservoirs B and C.\n--\n-- WELL SPECIFICATION DATA\n--\n-- WELL GROUP LOCATION BHP PHASE DRAIN INFLOW SHUT CROSS PRESS\n-- NAME NAME I J DEPTH FLUID AREA EQUA. IN FLOW TABLE\nWELSPECS\nRES-AOP1 PLATFORM 14 13 1* OIL 1* STD OPEN NO 1* /\nRES-AOP2 PLATFORM 17 16 1* OIL 1* STD OPEN NO 1* /\nRES-AOP3 PLATFORM 21 19 1* OIL 1* STD OPEN NO 1* /\nRES-BOP4 PLATFORM 28 96 1* OIL 1* STD OPEN NO 1* /\nRES-BOP5 PLATFORM 34 89 1* OIL 1* STD OPEN NO 1* /\nRES-COP6 PLATFORM 128 52 1* OIL 1* STD OPEN NO 1* /\nRES-COP7 PLATFORM 134 56 1* OIL 1* STD OPEN NO 1* /\nRES-COP8 PLATFORM 138 50 1* OIL 1* STD OPEN NO 1* /\nRES-COP9 PLATFORM 120 52 1* OIL 1* STD OPEN NO 1* /\n/\n--\n-- DEFINE WELL REFERENCE DEPTH FOR PRESSURE CALCULATIONS\n--\n-- WELL REF\n-- NAME DEPTH\n-- ---- ------\nWPAVEDEP\n'RES-A*’ 3100.0 /\n'RES-B*’ 3300.0 /\n'RES-C*’ 5909.0 /\n/\nIn the example the all wells dedicated to RES-A will have their bottom-hole reference depth set to 3,000 ft. TVDSS, RES-B wells to 3,300 ft. TVDSS and well RES-C wells to 5909 ft. TVDSS.\n| Note The keyword is normally used to reset a well’s bottom-hole pressure depth to match the pressure gauge depth for when observed pressure is available, for example when conducting a history match for a well test, or when attempting to match static bottom-hole surveys conducted on a well. |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":2,"size_kind":"list"},"WPIMULT":{"name":"WPIMULT","sections":["SCHEDULE"],"supported":null,"summary":"The WPIMULT keyword defines a well connection factor multiplier that scales the existing well connection factor values. The resulting effect is to scale the well’s productivity at the reporting time step the keyword is entered.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well and well connection status data is being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"PIMULT","description":"A real positive value that will be used to scale the well connection factors defined by I, J, K, C1 and C2 below.","units":{},"default":"1.0","value_type":"DOUBLE"},{"index":3,"name":"I","description":"An integer less than or equal to NX that defines the connection locations in the I-direction.","units":{},"default":"1*","value_type":"INT"},{"index":4,"name":"J","description":"An integer less than or equal to NY that defines the connection locations in the J-direction.","units":{},"default":"1*","value_type":"INT"},{"index":5,"name":"K","description":"An integer less than or equal to NZ that defines the connection locations in the K-direction.","units":{},"default":"1*","value_type":"INT"},{"index":6,"name":"C1","description":"An integer value that defines the first completion number in the range. Connections are lumped into completions via the COMPLUMP keyword, and C1 refers to the first completion number, as defined by the COMPLUMP keyword, and all the connections contained within the C1 completion.","units":{},"default":"1*","value_type":"INT"},{"index":7,"name":"C2","description":"An integer that defines the last completion in the range. Connections are lumped into completions via the COMPLUMP keyword, and C2 refers to the last completion number, as defined by the COMPLUMP keyword, and all the connections contained within the C2 completion.","units":{},"default":"1*","value_type":"INT"}],"example":"The following example defines three vertical oil wells using the WELSPECS keyword and their associated connection data.\n--\n-- WELL SPECIFICATION DATA\n--\n-- WELL GROUP LOCATION BHP PHASE DRAIN INFLOW SHUT CROSS PRESS\n-- NAME NAME I J DEPTH FLUID AREA EQUA. IN FLOW TABLE\nWELSPECS\nOP01 PLATFORM 14 13 1* OIL 1* STD OPEN NO 1* /\nOP02 PLATFORM 28 96 1* OIL 1* STD OPEN NO 1* /\nOP03 PLATFORM 128 56 1* OIL 1* STD OPEN NO 1* /\n/\n--\n-- WELL PRODUCTION WELL CONTROLS\n--\n-- WELL OPEN/ CNTL OIL WAT GAS LIQ RES BHP THP VFP VFP\n-- NAME SHUT MODE RATE RATE RATE RATE RATE PRES PRES TABLE ALFQ\nWCONPROD\n‘*’ SHUT GRUP 1* 1* 1* 1* 1* 200.0 /\n/\n--\n-- WELL CONNECTION DATA\n--\n-- WELL --- LOCATION --- OPEN SAT CONN WELL KH SKIN D DIR\n-- NAME II JJ K1 K2 SHUT TAB FACT DIA FACT FACT FACT PEN\nCOMPDAT\nOP01 1* 1* 1 10 OPEN 1* 1* 0.708 1* 0.0 1* 'Z' /\nOP01 1* 1* 15 30 OPEN 1* 1* 0.708 1* 0.0 1* 'Z' /\nOP01 1* 1* 35 90 OPEN 1* 1* 0.708 1* 0.0 1* 'Z' /\nOP02 1* 1* 1 10 OPEN 1* 1* 0.708 1* 0.0 1* 'Z' /\nOP03 1* 1* 35 90 OPEN 1* 1* 0.708 1* 0.0 1* 'Z' /\n/\n-- ASSIGN WELL CONNECTIONS TO COMPLETIONS\n--\n-- WELL --- LOCATION --- COMPL\n-- NAME II JJ K1 K2 NO. COMPLUMP OP03 1* 1* 35 45 1 / COMPLETION NO. 01\nOP03 1* 1* 50 90 2 / COMPLETION NO. 02\n/\n--\n-- DEFINE WELL CONNECTION MULTIPLIERS\n--\n-- WELL PI --LOCATION-- COMPLETION\n-- NAME MULT I J K FIRST LAST\nWPIMULT\nOP01 1.250 1* 1* 1* 1* 1* /\nOP02 0.750 1* 1* 10 1* 1* /\nOP03 1.100 1* 1* 1* 1 2 /\n/\nIn this example the WPIMULT scales the well productivity of well OP01 by 1.25, and scales all the well connection factors in layer 10 only by 0.75 for well OP02. For well OP03, WPIMULT scales all the connections in completions one and two by 1.1.","expected_columns":7,"size_kind":"list"},"WPIMULTL":{"name":"WPIMULTL","sections":["SCHEDULE"],"supported":false,"summary":"The WPIMULTL keyword defines a well connection factor multiplier that scales the existing well connection factor values, for a well in a Local Grid Refinement (“LGR”). The resulting effect is scale the well’s productivity at the reporting time step the keyword is entered.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well and well connection status data is being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECL keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"PIMULT","description":"A real positive value that will be used to scale the well connection factors defined by I, J, K, C1 and C2 below.","units":{},"default":"1.0","value_type":"DOUBLE"},{"index":3,"name":"LGRNAME","description":"A character string of up to eight characters in length that defines the LGR name for which the well LGR connection multiplier factor (PIMULT) is being defined. Note that LGRNAME must have been declared previously using the WELSPECL keyword in the SCHEDULE section, otherwise an error may occur. If defaulted with 1* the LGR on the WELSPECL keyword will be utilized.","units":{},"default":"Defined","value_type":"STRING"},{"index":3,"name":"I","description":"An integer less than or equal to NX that defines the connection location in the I-direction.","units":{},"default":"1*","value_type":"STRING"},{"index":4,"name":"J","description":"An integer less than or equal to NY that defines the connection location in the J-direction.","units":{},"default":"1*","value_type":"INT"},{"index":5,"name":"K","description":"An integer less than or equal to NZ that defines the connection location in the K-direction.","units":{},"default":"1*","value_type":"INT"},{"index":6,"name":"C1","description":"An integer value that defines the first completion in the range. Connections are lumped into completions via the COMPLUMP keyword, and C1 refers to the first completion number, as defined by the COMPLUMP keyword, and all the connections contained within the C1 completion","units":{},"default":"1*","value_type":"INT"},{"index":7,"name":"C2","description":"An integer value that defines the last completion in the range. Connections are lumped into completions via the COMPLUMP keyword, and C2 refers to the last completion number, as defined by the COMPLUMP keyword, and all the connections contained within the C2 completion","units":{},"default":"1*","value_type":"INT"},{"index":8,"name":"LAST","description":"","units":{},"default":"","value_type":"INT"}],"example":"The following example defines two vertical oil wells using the WELSPECL keyword and their associated connection data.\n--\n-- WELL LGR SPECIFICATION DATA\n--\n-- WELL GROUP LGR -LOCATION- BHP PHASE DRAIN INFLOW SHUT CROSS PVT\n-- NAME NAME NAME I J DEPTH FLUID AREA EQUA. IN FLOW TABLE\nWELSPECL\nOP01 PLAT OP01LGR 14 13 1* OIL 1* STD SHUT NO 1* /\nOP02 PLAT OP02LGR 28 96 1* OIL 1* STD SHUT NO 1* /\n/\n--\n-- WELL LGR CONNECTION DATA\n--\n-- WELL LGR ---LOCATION--- OPEN SAT CONN WELL KH SKIN D DIR\n-- NAME NAME II JJ K1 K2 SHUT TAB FACT DIA FACT FACT FACT PEN\nCOMPDATL\nOP01 OP01LGR 1* 1* 20 56 OPEN 1* 1* 0.708 1* 1* 1* Z /\nOP01 OP01LGR 1* 1* 75 100 SHUT 1* 1* 0.708 1* 1* 1* Z / OP02 OP02LGR 1* 1* 75 100 OPEN 1* 1* 0.708 1* 1* 1* Z /\nOP03 OP02LGR 1* 1* 75 100 OPEN 1* 1* 0.708 1* 1* 1* Z /\n/\n--\n-- ASSIGN WELL CONNECTIONS TO COMPLETIONS\n--\n-- WELL LGR --- LOCATION --- COMPL\n-- NAME NAME II JJ K1 K2 NO. COMPLMPL OP03 OP02LGR 1* 1* 75 85 1 / COMPLETION NO. 01\nOP03 OP21LGR 1* 1* 86 100 2 / COMPLETION NO. 02\n/\n--\n-- DEFINE WELL CONNECTION MULTIPLIERS\n--\n-- WELL PI LGR --LOCATION-- COMPLETION\n-- NAME MULT NAME I J K FIRST LAST\nWPIMULTL\nOP01 1.250 OP01LGR 1* 1* 1* 1* 1* /\nOP02 0.750 OP01LGR 1* 1* 10 1* 1* /\nOP03 1.100 OP02LGR 1* 1* 1* 1 2 /\n/\nIn this example the WPIMULTL keyword scales the well productivity of well OP01 by 1.25, scales all the well connection factors in layer 10 only by 0.75 for well OP02, and for OP03, scales all the connections in completions one and two by 1.100.","expected_columns":8,"size_kind":"list"},"WPITAB":{"name":"WPITAB","sections":["SCHEDULE"],"supported":false,"summary":"The WPITAB keyword assigns the well productivity index multiplier versus water cut tables, that are used to scaled a well’s connection factors based on the connection’s current producing water cut, to a well. The tables are defined via the PIMULTAB keyword in the SCHEDULE section.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well productivity index multiplier versus water cut table, PIMULTAB, is being assigned. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"PIMULTAB","description":"A positive integer value that defines the corresponding PIMULTAB table to be allocated to the well. A value less than or equal to zero means that no PIMULTAB table is allocated to the well","units":{},"default":"0","value_type":"DOUBLE"}],"example":"Given NTPIMT equals two on the PIMTDIMS keyword in the RUNSPEC section, then:\n--\n-- ASSIGN WELL PRODUCTIVITY INDEX VS WATER CUT TABLE\n--\n-- WELL PI\n-- NAME TABLE\nWPITAB\nOP01 1 /\nOP02 1 /\nOP03 2 /\n/\nAssigns PIMULTAB table one to wells OP01 and OP02 and table two to OP03.","expected_columns":2,"size_kind":"list"},"WPLUG":{"name":"WPLUG","sections":["SCHEDULE"],"supported":false,"summary":"Various keywords in the SCHEDULE section (WECON, GECON etc.) allow for a well to be automatically plugged back if the well violates a constraint, that is to close existing perforations (well connections). For example if the water cut exceeds 90%, then plug back the well. The WPLUG keyword defines for automatic plug backs the length of the perforations (length of connections) to be closed each time an automatic plug back is performed, together with various options on how the workover should be performed, top down, bottom up, etc.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"LENGTH_TOP","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":3,"name":"LENGTH_BOTTOM","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":4,"name":"SOURCE","description":"","units":{},"default":"WELL","value_type":"STRING"}],"example":"","expected_columns":4,"size_kind":"list"},"WPMITAB":{"name":"WPMITAB","sections":["SCHEDULE"],"supported":null,"summary":"The WPMITAB keyword assigns the well polymer molecular injection tables to water injection wells in OPM Flow's Polymer Molecular Weight Transport option, that uses the polymer molecular weight in calculating the polymer viscosity, as well as accounting for formation damage due to the water and polymer injection, by adjusting the wellbore skin pressure. This keyword should only be used if the POLYMER and POLYMW keywords in the RUNSPEC section are also activated. The keyword assigns the PLYMWINJ tables that are defined via the PLYMWINJ keyword in the PROPS section.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length, that defines the water injection well name, for which the well polymer molecular injection table, PLYMWINJ, is to be assigned. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"PLYMWINJ","description":"A positive integer value that defines the corresponding PLYMWINJ table to be allocated to the water injection well. A value less than or equal to zero means that no PLYMWIN table is allocated to the well","units":{},"default":"0","value_type":"INT"}],"example":"Given NTPMWINJ equals two on the PINTDIMS keyword in the RUNSPEC section, then:\n--\n-- ASSIGN WELL POLYMER MOLECULAR MODEL INJECTION TABLES\n--\n-- WELL PLYMWINJ\n-- NAME TABLE\nWPMITAB\nWI01 1 /\nWI02 1 /\nWI03 2 /\n/\nAssigns PLYMWINJ table one to wells WI01 and WI02 and table two to WI03.\n| Note This is an OPM Flow specific keyword that employs an alternative polymer flood model based on a Polymer Molecular Weight Transport equation, that is not available in the commercial simulator. |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":2,"size_kind":"list"},"WPOLYMER":{"name":"WPOLYMER","sections":["SCHEDULE"],"supported":false,"summary":"The WPOLYMER keyword defines a water injection well’s polymer and salt injection stream concentrations that are to be used for when the polymer and salt options have been activated by the POLYMER and BRINE keywords in the RUNSPEC section.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well connection data is being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"POLCON","description":"A real positive value that defines the polymer concentration of the well’s injection stream. This value may be specified using a User Defined Argument (UDA).","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None","value_type":"UDA","dimension":"Concentration"},{"index":3,"name":"SALTCON","description":"A real positive value that defines the salt concentration of the well’s injection stream. This value may be specified using a User Defined Argument (UDA). This keyword is not supported by OPM Flow but has no effect on the results so it will be ignored.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None","value_type":"UDA","dimension":"Concentration"},{"index":4,"name":"GRPPOL","description":"A character string of up to eight characters in length that defines the group name for which the group’s produced polymer concentration should be used instead of the well’s POLCON value stated on this keyword.","units":{},"default":"None","value_type":"STRING"},{"index":5,"name":"GRPSALT","description":"A character string of up to eight characters in length that defines the group name for which the group’s produced salt concentration should be used instead of the well’s SALTCON value stated on this keyword. This keyword is not supported by OPM Flow but has no effect on the results so it will be ignored.","units":{},"default":"None","value_type":"STRING"}],"example":"The following example defines the polymer and salt injection stream concentrations for three water injection wells for when the polymer option has been activated by the POLYMER keyword in the RUNSPEC section.\n--\n-- DEFINE WATER INJECTION WELL POLYMER AND SALT CONCENTRATIONS\n--\n-- WELL POLYMER SALT POLYMER SALT\n-- NAME POLCON SALTCON GROUP GROUP\n-- ------- -------- -------- --------\nWPOLYMER\nWI01 0.2500 /\nWI02 1* 1* GRPINJ1 /\nWI03 0.2500 1* GRPINJ1 /\n/\nThe polymer concentration for well WI01 is set to 0.25 and the stated polymer concentration for well WI02 will be ignored, as both WI02 and WI03 will re-inject the produced polymer from the GRPINJ1 group.","expected_columns":5,"size_kind":"list"},"WPOLYRED":{"name":"WPOLYRED","sections":["SCHEDULE"],"supported":false,"summary":"The WPOLYRED keyword defines the polymer-water reduction factor for injection wells, for when the polymer phase has been activated by the POLYMER keyword in the RUNSPEC section. WPOLYRED should be set to a value greater than or equal to zero and less than or equal to one that determines the injection mixture’s viscosity. A value of zero indicates for pure water injection and a value of one will use the simulator’s valuated mixture viscosity. A value between zero and one will use an interpolated mixture viscosity.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"POLYMER_VISCOSITY_RED","description":"","units":{},"default":"1","value_type":"DOUBLE"}],"example":"","expected_columns":2,"size_kind":"list"},"WREGROUP":{"name":"WREGROUP","sections":["SCHEDULE"],"supported":false,"summary":"WREGROUP defines the criteria to automatically re-assign wells to various other groups. This can be used, for example, to move wells on THP control flowing through a high pressure separator group to a low pressure separator group in order for the wells to be under different group controls for low pressure wells.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"QUANTITY","description":"","units":{},"default":" ","value_type":"STRING"},{"index":3,"name":"GROUP_UPPER","description":"","units":{},"default":"","value_type":"STRING"},{"index":4,"name":"UPPER_LIMIT","description":"","units":{},"default":"1e+20","value_type":"DOUBLE"},{"index":5,"name":"GROUP_LOWER","description":"","units":{},"default":"","value_type":"STRING"},{"index":6,"name":"LOWER_LIMIT","description":"","units":{},"default":"0","value_type":"DOUBLE"}],"example":"","expected_columns":6,"size_kind":"list"},"WRFT":{"name":"WRFT","sections":["SCHEDULE"],"supported":null,"summary":"This keyword activates reporting of a well’s pressure and saturation profile versus depth for the connected grid blocks, to the RFT file for the requested wells at the time the keyword is activated. Data written out by OPM Flow is used to match the field measured data collected from a Repeat Formation Tester (“RFT”) tool.","parameters":[{"index":1,"name":"WELNAME","description":"A columnar vector of character strings of up to eight characters in length for each item, that defines the well name for which the RFT data should be written to the RFT file. Note that the WELNAME must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur. If the WELNAME is left blank then the data is written out for all wells at the time they are first opened to flow. If the WELNAME is given, then the RFT data for the well at the time step the keyword is invoked is written out.","units":{},"default":"None","value_type":"STRING"}],"example":"The first example activates RFT reporting for all wells at the time a well is first opened to flow:\n--\n-- ACTIVATE WELL RFT REPORTING TO THE RFT FILE\n--\n-- WELL\n-- NAME\nWRFT\n/\nIdeally, this version of the keyword should be place at the beginning of the SCHEDULE section to obtain the data for the wells in the run before they are opened up through time.\nThe next example shows how to use the keyword to request the output for several wells at different reporting time steps.\n-- ------------------------------------------------------------------------------\n-- 01 JAN 2000 START OF SCHEDULE SECTION\n-- ------------------------------------------------------------------------------\nDATES\n15 JAN 2000 /\n/\n--\n-- WELL HISTORICAL PRODUCTION CONTROLS\n--\n-- WELL OPEN/ CNTL OIL WAT GAS VFP VFP THP BHP\n-- NAME SHUT MODE RATE RATE RATE TABLE ALFQ PRES PRES\nWCONHIST OP01 OPEN ORAT 15.5E3 0.0 1550 10 1* 900.0 1* /\nOP02 SHUT /\n/\n--\n-- ACTIVATE WELL RFT REPORTING TO THE RFT FILE\n--\n-- WELL\n-- NAME\nWRFT\nOP01 /\nOP02 /\n/\nDATES\n01 FEB 2000 /\n/\n--\n-- WELL HISTORICAL PRODUCTION CONTROLS\n--\n-- WELL OPEN/ CNTL OIL WAT GAS VFP VFP THP BHP\n-- NAME SHUT MODE RATE RATE RATE TABLE ALFQ PRES PRES\nWCONHIST OP01 OPEN ORAT 15.5E3 0.0 1550 10 1* 900.0 1* /\nOP02 SHUT /\n/ --\n-- ACTIVATE WELL RFT REPORTING TO THE RFT FILE\n--\n-- WELL\n-- NAME\nWRFT\nOP01 /\nOP02 /\n/\nDATES\n01 MAR 2000 /\n/\n--\n-- WELL HISTORICAL PRODUCTION CONTROLS\n--\n-- WELL OPEN/ CNTL OIL WAT GAS VFP VFP THP BHP\n-- NAME SHUT MODE RATE RATE RATE TABLE ALFQ PRES PRES\nWCONHIST OP01 OPEN ORAT 15.5E3 0.0 1550 10 1* 900.0 1* /\nOP02 OPEN ORAT 10.5E3 0.0 1000 10 1* 900.0 1* /\n/\nIn this example, both well’s have their RFT written out on February 1 and March 1 2000.","expected_columns":1,"size_kind":"list"},"WRFTPLT":{"name":"WRFTPLT","sections":["SCHEDULE"],"supported":null,"summary":"This keyword activates reporting of a well’s depth pressure and fluid rates profile to the RFT file for the requested wells at the time the keyword is activated. Data written out by the simulator is used to match the field measured data collected from both the Repeat Formation Tester (“RFT”) tool and various Production Logging Tools (“PLT”).","parameters":[{"index":1,"name":"WELNAME","description":"A columnar vector of character strings of up to eight characters in length for each item, that defines the well name for which the RFT data should be written to the RFT file. Note that the WELNAME must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur. If the WELNAME is left blank then the data is written out for all wells at the time they are first opened to flow. If the WELNAME is given, then the RFT data for the well at the time step the keyword is invoked is written out.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"RFT","description":"A defined character string that sets the RFT data set output options and should be set to one of the following character strings. NO: do not write RFT data for the well. YES: write out the RFT data at the current reporting time step. REPT: write out the RFT data at the current reporting time step and all subsequent reporting time steps. TIMESTEP: write out the RFT data at the current reporting time step and all subsequent time steps. FOPN: write out the RFT data at the current reporting time step for the well if it is opened, otherwise write the RFT data out the first time the named well is opened.","units":{},"default":"NO","value_type":"STRING","options":["NO","YES","REPT","TIMESTEP","FOPN"]},{"index":3,"name":"PLT","description":"A defined character string that sets the PLT data set output options and should be set to one of the following character strings. NO: do not write PLT data for the well. YES: write out the PLT data at the current reporting time step. REPT: write out the PLT data at the current reporting time step and all subsequent reporting time steps. TIMESTEP: write out the PLT data at the current reporting time step and all subsequent time steps.","units":{},"default":"NO","value_type":"STRING","options":["NO","YES","REPT","TIMESTEP"]},{"index":4,"name":"MULTISEG","description":"A defined character string that sets the output options for multi-segment wells, that is the flow rates and pressures through each well segment, and should be set to one of the following character strings. NO: do not write multi-segment well data for the well. YES: write out the multi-segment well data at the current reporting time step. REPT: write out the multi-segment well data at the current reporting time step and all subsequent reporting time steps. TIMESTEP: write out the multi-segment well data at the current reporting time step and all subsequent time steps. Note the commercial simulator also uses MULTISEG to control the output of “rivers” for when the RIVERS Model has been enabled via the RIVRDIMS keyword in the RUNSPEC section. OPM Flow does not support the RIVERS Model.","units":{},"default":"NO","value_type":"STRING","options":["NO","YES","REPT","TIMESTEP"]}],"example":"The first example activates RFT output at the current reporting time step for all the wells that are opened to flow, otherwise the RFT data is written out the first time a well is opened.\n--\n-- WELL RFT, PLT AND SEGMENT DATA\n--\n-- WELL RFT PLT SEGMENT\n-- NAME DATA DATA DATA\nWRFTPLT\n'*' FOPN /\n/\nThe next example writes out the RFT and PLT data for two wells at the current reporting time step.\n--\n-- WELL RFT, PLT AND SEGMENT DATA\n--\n-- WELL RFT PLT SEGMENT\n-- NAME DATA DATA DATA\nWRFTPLT\nOP01 YES YES /\nOP02 YES YES /\n/\nThe final example is shown below:\n--\n-- WELL RFT, PLT AND SEGMENT DATA\n--\n-- WELL RFT PLT SEGMENT\n-- NAME DATA DATA DATA\nWRFTPLT\nOP01 REPT NO /\nOP02 NO YES /\n/\nIn this case the RFT data for well OP01 is written out at the current reporting time step and all subsequent reporting time steps. For well OP02, no RFT is written out but the PLT data is written out for the current report time step only.","expected_columns":4,"size_kind":"list"},"WSALT":{"name":"WSALT","sections":["SCHEDULE"],"supported":true,"summary":"The WSALT keyword defines a water injection well’s salt injection stream concentration that is to be used for when the salt option has been activated by the BRINE keywords in the RUNSPEC section. Note that if the Polymer option has also been activated by the POLYMER keyword in the RUNSPEC section, then the WPOLYMER keyword in the SCHEDULE section should be used to enter both the polymer and salt concentrations.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the injection salt concentrations are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"SALTCON","description":"A real positive vector of values that defines the salt concentration of the well’s injection stream and consists of: If the Standard Brine model has been invoked by the BRINE keyword, then SALTCON consist of one value representing the injection salt concentration; If OPM Flow’s Water Vaporization and Salt Precipitation models have been activated by the VAPWAT and PRECSALT keywords in the RUNSPEC section, then SALTCON consist of one value representing the injection salt concentration; or, If the Multi-Component Brine option has been activated by the BRINE and ECLMC keywords in the RUNSPEC section, then SALTCON consists of a vector of values representing the salt concentration of each brine within the injected brine mixture. Only options (1) and (2) are currently supported. This value may be specified using a User Defined Argument (UDA). Note if SALTCON is defaulted (1*) then the well’s salt concentration will be equal to the well’s group salt concentration.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"1*","value_type":"UDA","dimension":"Concentration"}],"example":"The following example defines the salt injection stream concentration for three water injection wells for when the brine phase has been activated by the BRINE keyword in the RUNSPEC section.\n--\n-- DEFINE WATER INJECTION WELL SALT CONCENTRATIONS (STANDARD)\n--\n-- WELL SALT-1 SALT-2 SALT-3 SALT-4\n-- NAME SALTCON SALTCON SALTCON SALTCON\n-- ------- ------- ------- -------\nWSALT\nWI01 0.2500 /\nWI02 1* /\nWI03 0.2500 /\n/\nThe salt concentration for both well WI01 and WI03 is set to 0.25, and for well WI02 the salt concentration will be taken from the well’s group salt concentration.\nThe next example is based on using the Multi-Component Brine option, that is the BRINE and ECLMC keywords have been used in the RUNSPEC section, and assuming three salts.\n--\n-- DEFINE WATER INJECTION WELL SALT CONCENTRATIONS (MULTIPLE)\n--\n-- WELL SALT-1 SALT-2 SALT-3 SALT-4\n-- NAME SALTCON SALTCON SALTCON SALTCON\n-- ------- ------- ------- -------\nWSALT\nWI01 0.1500 0.0500 0.0500 /\nWI02 0.1500 0.0500 0.0500 /\nWI03 0.2000 0.0500 0.0600 /\n/\nHere the salt concentrations for both well WI01 and WI02 are set to 0.1500, 0.0500, 0.0500 for the three salts and for well WI03 the salt concentrations are 0.2000, 0.0500 and 0.0600.\nNote that OPM Flow does not currently support the Multi-Component brine model.","expected_columns":2,"size_kind":"list"},"WSCCLEAN":{"name":"WSCCLEAN","sections":["SCHEDULE"],"supported":false,"summary":"The WSCCLEAN keyword adjusts the amount of scale currently accumulated around a well’s well connections for wells located in the global grid. For example, if a workover has been performed on a well to remove (or reduce) the deposited scale over the perforations, then this keyword can be used to implement the effects of the workover. Scale deposits reduce the productivity of well and this relationship is defined in the SCDPTAB and SCDATAB keywords in SCHEDULE section. The tables are allocated to a well via the WSCTAB keyword, which is also in the SCHEDULE section. Note that the Scale Deposition option must have been activated by declaring the dimensions of the scaling deposition tables using the SCDPDIMS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"SCALE_MULTIPLIER","description":"","units":{},"default":"1","value_type":"DOUBLE"},{"index":3,"name":"I","description":"","units":{},"default":"-1","value_type":"INT"},{"index":4,"name":"J","description":"","units":{},"default":"-1","value_type":"INT"},{"index":5,"name":"K","description":"","units":{},"default":"-1","value_type":"INT"},{"index":6,"name":"C1","description":"","units":{},"default":"-1","value_type":"INT"},{"index":7,"name":"C2","description":"","units":{},"default":"-1","value_type":"INT"}],"example":"","expected_columns":7,"size_kind":"list"},"WSCCLENL":{"name":"WSCCLENL","sections":["SCHEDULE"],"supported":false,"summary":"The WSCCLENL keyword adjusts the amount of scale currently accumulated around a well’s well connections for wells located in a Local Grid Refinement (\"LGR\"). For example, if a workover has been performed on a well to remove (or reduce) the deposited scale over the perforations, then this keyword can be used to implement the effects of the workover. Scale deposits reduce the productivity of well and this relationship is defined in the SCDPTAB and SCDATAB keywords in SCHEDULE section. The tables are allocated to a well via the WSCTAB keyword, which is also in the SCHEDULE section. Note that the Scale Deposition option must have been activated by declaring the dimensions of the scaling deposition tables using the SCDPDIMS keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"SCALE_MULTIPLIER","description":"","units":{},"default":"1","value_type":"DOUBLE"},{"index":3,"name":"LGR","description":"","units":{},"default":"","value_type":"STRING"},{"index":4,"name":"I","description":"","units":{},"default":"-1","value_type":"INT"},{"index":5,"name":"J","description":"","units":{},"default":"-1","value_type":"INT"},{"index":6,"name":"K","description":"","units":{},"default":"-1","value_type":"INT"},{"index":7,"name":"C1","description":"","units":{},"default":"-1","value_type":"INT"},{"index":8,"name":"C2","description":"","units":{},"default":"-1","value_type":"INT"}],"example":"","expected_columns":8,"size_kind":"list"},"WSCTAB":{"name":"WSCTAB","sections":["SCHEDULE"],"supported":false,"summary":"WSCTAB assigns scale deposition and scale damage tables to a well, for when the Scale Deposition option has been activated by declaring the dimensions of the scaling deposition tables using the SCDPDIMS keyword in the RUNSPEC section. Scale deposits reduce the productivity of well and this relationship is defined in the SCDPTAB and SCDATAB keywords in the SCHEDULE section, and are allocated to a well by the WSCTAB keyword.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"SCALE_DEPOSITION_TABLE","description":"","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"SCALE_DAMAGE_TABLE","description":"","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"UNUSED","description":"","units":{},"default":"","value_type":"STRING"},{"index":5,"name":"SCALE_DISSOLUTION_TABLE","description":"","units":{},"default":"0","value_type":"INT"}],"example":"","expected_columns":5,"size_kind":"list"},"WSEGAICD":{"name":"WSEGAICD","sections":["SCHEDULE"],"supported":null,"summary":"The WSEGAICD keyword defines a multi-segment well segment to be an autonomous Inflow Control Device (“ICD”) as part of a completion for a multi-segment well. Note that the well must have been previously defined by the WELSPECS and WELSEGS keywords in the SCHEDULE section and that the data for the keyword should be repeated for each multi-segment completion that contains an autonomous ICD.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which a multi-segment well is being defined. Note that the well name (WELNAME) must have been declared previously using both the WELSPECS and WELSEGS keywords in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"ISEG1","description":"An integer greater than or equal to two and less than or equal to MXSEGS on the WSEGDIMS keyword in the RUNSPEC section that defines the start of the segment range.","units":{},"default":"None","value_type":"INT"},{"index":3,"name":"ISEG2","description":"An integer greater than or equal to two and not less then ISEG1 on this record and less than or equal to MXSEGS on the WSEGDIMS keyword in the RUNSPEC section, that defines the end of the segment range.","units":{},"default":"None","value_type":"INT"},{"index":4,"name":"ICDSTREN","description":"A positive real value that defines an empirical constant for the strength of the given ICD as determined from measurements using the calibrated fluid.","units":{"field":"psi/((lb/ft3)(rft3/day)2)","metric":"bars/((kg/m3)(rm3/day)2)","laboratory":"atm/((gm/cc)(rcc/hr)2)"},"default":"None","value_type":"DOUBLE","dimension":"Pressure*Time*Time/GeometricVolume*GeometricVolume*Density"},{"index":5,"name":"ICDLEN","description":"A real value that defines the length of the ICD used in conjunction with NSCALFAC to calculate a scaling factor to be applied to the reservoir flow to adjust the flow through each ICD, that is: If NSCALFAC equals zero: then the scale factor is equal to the length of the ICD (ICDLEN) divided by the length of the tubing section, that is the parent of the ICDs, then this allows for the case when the ICD segment may represent a number of ICDs in parallel. If NSCALFAC equals one: then the scale factor is equal to the absolute value of ICDLEN. If NSCALFAC equals two: then the scale factor is equal to the length of ICDLEN, divided by the total length of the completions which supply the ICD. NSCALFAC explicitly sets which of the above three options is used. If NSCALFAC is defaulted, then option 1) is used whenever ICDLEN is positive and option 2) when ICDLEN is negative.","units":{"field":"feet 39.37","metric":"m 12.00","laboratory":"cm 1,2000"},"default":"Defined","value_type":"DOUBLE","dimension":"Length"},{"index":6,"name":"CALDEN","description":"A positive real value that defines the density of the calibrating fluid at surface conditions.","units":{"field":"lb/ft3 62.416","metric":"kg/m3 1000.25","laboratory":"gm/cc 1.00025"},"default":"Defined","value_type":"DOUBLE","dimension":"Density"},{"index":7,"name":"CALVISC","description":"A positive real value that defines the viscosity of the calibrating fluid at surface conditions.","units":{"field":"cP","metric":"cP","laboratory":"cP"},"default":"1.45","value_type":"DOUBLE","dimension":"Viscosity"},{"index":8,"name":"EMLCRT","description":"A positive real value that defines the “local water” in liquid fraction used to determine whether the “water-in-oil” or “oil-in-water” emulsion viscosity equation should be applied.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.5","value_type":"DOUBLE","dimension":"1"},{"index":9,"name":"EMLTRANS","description":"A positive real value that defines the width of the transition zone around EMLCRT and is used to ensure that the calculated viscosity forms a continuous function of water in liquid fraction. Within this region, the emulsion viscosity is a linear interpolation between the “water-in-oil” and “oil-in-water” viscosity values either side of the region.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.05","value_type":"DOUBLE","dimension":"1"},{"index":10,"name":"EMLMAX","description":"A positive real value that defines the maximum emulsion viscosity to continuous phase viscosity (oil or water) ratio.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"5.0","value_type":"DOUBLE","dimension":"1"},{"index":11,"name":"NSCALFAC","description":"An integer value greater than or equal to zero, that specifies the method to be used when applying the scaling factor and should be set to one of the following: If NSCALFAC equals zero: then the scale factor is equal to the length of the ICD (ICDLEN) divided by the length of the tubing section, that is the parent of the ICDs, then this allows for the case when the ICD segment may represent a number of ICDs in parallel. If NSCALFAC equals one: then the scale factor is equal to the absolute value of ICDLEN. If NSCALFAC equals two: then the scale factor is equal to the length of ICDLEN, divided by the total length of the completions which supply the ICD. NSCALFAC explicitly sets which of the above three options is used. If NSCALFAC is negative, then option 1) is used whenever ICDLEN is positive and option 2) when ICDLEN is negative.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"-1","value_type":"INT"},{"index":12,"name":"CALRATE","description":"A positive real value that defines the maximum surface flow rate for which the ICD was calibrated. Values calculated greater than CALRATE will use linear extrapolation.","units":{"field":"scf/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"None","value_type":"DOUBLE","dimension":"GeometricVolume/Time"},{"index":13,"name":"RATEXP","description":"A real value greater than or equal to zero that defines the flow rate exponent in equation (12.35).","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE"},{"index":14,"name":"VISCEXP","description":"A real value that defines the viscosity exponent in equation (12.35).","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE"},{"index":15,"name":"STATUS","description":"A defined character string that specifies the ICD’s operational status, STATUS should be set to one of the following character strings: OPEN: the ICD connections are open to flow. SHUT: the ICD connections are closed to flow (shut-in).","units":{},"default":"OPEN","value_type":"STRING","options":["OPEN","SHUT"]},{"index":16,"name":"A1","description":"A real value that defines the density mixture OIL flowing fraction exponent in equation (12.36)","units":{},"default":"1.0","value_type":"DOUBLE"},{"index":17,"name":"A2","description":"A real value that defines the density mixture WATER flowing fraction exponent in equation (12.36)","units":{},"default":"1.0","value_type":"DOUBLE"},{"index":18,"name":"A3","description":"A real value that defines the density mixture GAS flowing fraction exponent in equation (12.36)","units":{},"default":"1.0","value_type":"DOUBLE"},{"index":19,"name":"B1","description":"A real value that defines the viscosity mixture OIL flowing fraction exponent in equation (12.37)","units":{},"default":"1.0","value_type":"DOUBLE"},{"index":20,"name":"B2","description":"A real value that defines the viscosity mixture WATER flowing fraction exponent in equation (12.37)","units":{},"default":"1.0","value_type":"DOUBLE"},{"index":21,"name":"B3","description":"A real value that defines the viscosity mixture GAS flowing fraction exponent in equation (12.37)","units":{},"default":"1.0","value_type":"DOUBLE"},{"index":22,"name":"DENEXP","description":"A real value that defines the density exponent in equation (12.35).","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0","value_type":"DOUBLE"}],"example":"The following example defines a multi-segment oil production well (OP01) using the WELSPECS, WELSEGS COMPDAT and COMPSEGS keywords, followed by the WSEGAICD keyword to define the autonomous inflow control devices for the well.\n--\n-- WELL SPECIFICATION DATA\n--\n-- WELL GROUP LOCATION BHP PHASE DRAIN INFLOW OPEN CROSS PVT DEN FIP\n-- NAME NAME I J DEPTH FLUID AREA EQUANS SHUT FLOW TABLE CAL NUM\nWELSPECS\nOP01 PLATFORM 14 8 1* OIL 0.0 STD SHUT YES 0 SEG 0 /\n/\n--\n-- WELL CONNECTION DATA\n--\n-- WELL --- LOCATION --- OPEN SAT CONN WELL KH SKIN D DIR\n-- NAME II JJ K1 K2 SHUT TAB FACT DIA FACT FACT FACT PEN\nCOMPDAT\nOP01 14 8 1 1 OPEN 1* 1.972960E+2 0.216 1* 0.00 1* 'Z' /\nOP01 14 7 1 1 OPEN 1* 1.619450E+2 0.216 1* 0.00 1* 'Z' /\nOP01 14 7 2 2 OPEN 1* 4.126449E+2 0.216 1* 0.00 1* 'Z' /\nOP01 14 7 3 3 OPEN 1* 2.033290E+1 0.216 1* 0.00 1* 'Z' /\nOP01 15 7 3 3 OPEN 1* 9.095613E+1 0.216 1* 0.00 1* 'Z' /\nOP01 15 6 3 3 OPEN 1* 2.090607E+2 0.216 1* 0.00 1* 'Y' /\nOP01 15 6 4 4 OPEN 1* 3.010669E+1 0.216 1* 0.00 1* 'Y' /\nOP01 16 6 4 4 OPEN 1* 7.123814E+1 0.216 1* 0.00 1* 'Y' /\nOP01 16 5 4 4 OPEN 1* 4.414386E+2 0.216 1* 0.00 1* 'Y' /\nOP01 16 4 4 4 OPEN 1* 4.345126E+2 0.216 1* 0.00 1* 'Y' /\nOP01 16 3 4 4 OPEN 1* 2.894573E+2 0.216 1* 0.00 1* 'Y' /\nOP01 17 3 4 4 OPEN 1* 1.329523E+2 0.216 1* 0.00 1* 'Y' /\nOP01 17 2 4 4 OPEN 1* 6.981252E+1 0.216 1* 0.00 1* 'Y' /\nOP01 17 2 5 5 OPEN 1* 1.392382E+2 0.216 1* 0.00 1* 'Y' /\n/\n--\n-- WELL SEGMENT SPECIFICATION DATA\n--\n-- WELL NODAL LEN WELL DEPH PRESS FLOW\n-- NAME DEPTH TUBING VOLM OPTN CALC MODEL\nWELSEGS\nOP01 2041.56259 0.0000 1* INC 'HF-' /\n--\n-- SEG SEG BRAN SEG TUBING NODAL TUBE TUBE XSEC VOL\n-- ISTR IEND NO NO LENGTH DEPTH ID ROUGH AREA SEG\n2 2 1 1 9.56005 0.61168 0.152 0.0000100 /\n3 3 1 2 17.40714 1.11376 0.152 0.0000100 /\n4 4 1 3 41.24996 2.38255 0.152 0.0000100 /\n5 5 1 4 38.35922 2.06899 0.152 0.0000100 /\n6 6 1 5 27.13029 1.02248 0.152 0.0000100 /\n7 7 1 6 73.45099 2.40389 0.152 0.0000100 /\n8 8 1 7 54.95304 1.64832 0.152 0.0000100 /\n9 9 1 8 12.37381 0.23781 0.152 0.0000100 /\n10 10 1 9 62.61459 0.73403 0.152 0.0000100 /\n11 11 1 10 106.9805 1.37749 0.152 0.0000100 /\n12 12 1 11 88.42739 0.90931 0.152 0.0000100 /\n13 13 1 12 51.59899 0.27327 0.152 0.0000100 /\n14 14 1 13 24.75582 0.30814 0.152 0.0000100 /\n15 15 1 14 29.77334 0.49371 0.152 0.0000100 /\n--\n-- PERFORATION VALVE SEGMENTS\n--\n-- SEG SEG BRAN SEG TUBING NODAL TUBE TUBE XSEC VOL\n-- ISTR IEND NO NO LENGTH DEPTH ID ROUGH AREA SEG\n16 16 2 2 0.10000 0 0.152 0.0000100 /\n17 17 3 3 0.10000 0 0.152 0.0000100 /\n18 18 4 4 0.10000 0 0.152 0.0000100 /\n19 19 5 5 0.10000 0 0.152 0.0000100 /\n20 20 6 6 0.10000 0 0.152 0.0000100 /\n21 21 7 7 0.10000 0 0.152 0.0000100 /\n22 22 8 8 0.10000 0 0.152 0.0000100 /\n23 23 9 9 0.10000 0 0.152 0.0000100 /\n24 24 10 10 0.10000 0 0.152 0.0000100 /\n25 25 11 11 0.10000 0 0.152 0.0000100 /\n26 26 12 12 0.10000 0 0.152 0.0000100 /\n27 27 13 13 0.10000 0 0.152 0.0000100 /\n28 28 14 14 0.10000 0 0.152 0.0000100 /\n29 29 15 15 0.10000 0 0.152 0.0000100 /\n/\n--\n-- MULTISEGMENT WELL COMPLETION SEGMENT SPECIFICATION DATA\n--\n-- WELL\n-- NAME\nCOMPSEGS\nOP01 /\n--\n-- --LOCATION-- BRAN TUBING NODAL DIR LOC MID COMP ISEG\n-- II JJ K1 NO LENGTH DEPTH PEN I,J,K PERFS LENGTH NO.\n14 8 1 2 0.000000 0.10000 /\n14 7 1 3 0.000000 0.10000 /\n14 7 2 4 0.000000 0.10000 /\n14 7 3 5 0.000000 0.10000 /\n15 7 3 6 0.000000 0.10000 /\n15 6 3 7 0.000000 0.10000 /\n15 6 4 8 0.000000 0.10000 /\n16 6 4 9 0.000000 0.10000 /\n16 5 4 10 46.76168 46.86168 /\n16 4 4 11 0.000000 0.10000 /\n16 3 4 12 0.000000 0.10000 /\n17 3 4 13 0.000000 0.10000 /\n17 2 4 14 0.000000 0.10000 /\n17 2 5 15 42.50573 42.60573 /\n/\n--\n-- MULTI-SEGMENT WELL ICD SEGMENT SPECIFICATION DATA\n--\n-- WELL SEG SEG ICD ICD CAL CAL EML EML EML SCAL CAL RATE VISC OPEN\n-- NAME ISTR IEND STREN LEN DEN VISC CRIT TRAN MAX FAC RAT EXP EXP CLOSE\nWSEGAICD\nOP01 16 16 7.5e-5 -0.028975 1020 0.48 0.7 1* 1* 1* 1* 2.2 0.5 7* /\nOP01 17 17 7.5e-5 -0.023783 1020 0.48 0.7 1* 1* 1* 1* 2.2 0.5 7* /\nOP01 18 18 7.5e-5 -0.101240 1020 0.48 0.7 1* 1* 1* 1* 2.2 ","expected_columns":22,"size_kind":"list"},"WSEGDFIN":{"name":"WSEGDFIN","sections":["SCHEDULE"],"supported":false,"summary":"The WSEGDFIN keyword defines a multi-segment well’s drift flux slip model parameters. A slip model333\n Shi, H., Holmes, J.A., Durlofsky, L. J., Aziz, K., Diaz, L. R., Alkaya, B., and Oddie, G. “Drift-Flux Modeling of Two-Phase Flow in Wellbores,” paper SPE 84228, Society of Petroleum Engineers Journal (2005) 10, No. 1, 24-33; also presented as “Drift-Flux Modeling of Multiphase Flow in Wellbores,” at the SPE Annual Technical Conference and Exhibition, Denver, Colorado, USA(October 5-8, 2003). and 334\n Shi, H., Holmes, J.A., Diaz, L. R., Durlofsky, L. J., and Aziz, K. “Drift-Flux Parameters for Three-Phase Steady-State Flow in Wellbores,” paper SPE 89836, Society of Petroleum Engineers Journal(2005) 10, No. 2, 130-137; also presented at the SPE Annual Technical Conference and Exhibition, Houston, Texas, USA (September 26-29, 2004).enables the different phases in the wellbore to flow at different velocities, for example gas will flow up the tubing at a higher velocity than...","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","size_kind":"fixed","size_count":1,"variadic_record":true},"WSEGDFMD":{"name":"WSEGDFMD","sections":["SCHEDULE"],"supported":false,"summary":"The WSEGDFMD keyword defines a multi-segment well’s drift flux slip model definition that sets the type of slip model to be used. A slip model335\n Shi, H., Holmes, J.A., Durlofsky, L. J., Aziz, K., Diaz, L. R., Alkaya, B., and Oddie, G. “Drift-Flux Modeling of Two-Phase Flow in Wellbores,” paper SPE 84228, Society of Petroleum Engineers Journal (2005) 10, No. 1, 24-33; also presented as “Drift-Flux Modeling of Multiphase Flow in Wellbores,” at the SPE Annual Technical Conference and Exhibition, Denver, Colorado, USA(October 5-8, 2003). and 336\n Shi, H., Holmes, J.A., Diaz, L. R., Durlofsky, L. J., and Aziz, K. “Drift-Flux Parameters for Three-Phase Steady-State Flow in Wellbores,” paper SPE 89836, Society of Petroleum Engineers Journal(2005) 10, No. 2, 130-137; also presented at the SPE Annual Technical Conference and Exhibition, Houston, Texas, USA (September 26-29, 2004).enables the different phases in the wellbore to flow at different velocities, for example gas will f...","parameters":[{"index":1,"name":"DRIFT_MODEL","description":"","units":{},"default":"ORIGINAL","value_type":"STRING"},{"index":2,"name":"INCLINATION_FACTOR","description":"","units":{},"default":"H-K","value_type":"STRING"},{"index":3,"name":"GAS_EFFECT","description":"","units":{},"default":"NO","value_type":"STRING"}],"example":"","expected_columns":3,"size_kind":"fixed","size_count":1},"WSEGDFPA":{"name":"WSEGDFPA","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, WSEGDFPA, enables modification of a multi-segment well’s drift flux slip model default parameters used by the WSEGDFMA keyword in the SCHEDULE section to define the model. A slip model337\n Shi, H., Holmes, J.A., Durlofsky, L. J., Aziz, K., Diaz, L. R., Alkaya, B., and Oddie, G. “Drift-Flux Modeling of Two-Phase Flow in Wellbores,” paper SPE 84228, Society of Petroleum Engineers Journal (2005) 10, No. 1, 24-33; also presented as “Drift-Flux Modeling of Multiphase Flow in Wellbores,” at the SPE Annual Technical Conference and Exhibition, Denver, Colorado, USA(October 5-8, 2003). and 338\n Shi, H., Holmes, J.A., Diaz, L. R., Durlofsky, L. J., and Aziz, K. “Drift-Flux Parameters for Three-Phase Steady-State Flow in Wellbores,” paper SPE 89836, Society of Petroleum Engineers Journal(2005) 10, No. 2, 130-137; also presented at the SPE Annual Technical Conference and Exhibition, Houston, Texas, USA (September 26-29, 2004).enables the different phases in the wellbore...","parameters":[{"index":1,"name":"GAS_LIQUID_VD_FACTOR","description":"","units":{},"default":"1","value_type":"DOUBLE"},{"index":2,"name":"A1","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":3,"name":"A2","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":4,"name":"C0_A","description":"","units":{},"default":"1.2","value_type":"DOUBLE"},{"index":5,"name":"C0_B","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":6,"name":"FV","description":"","units":{},"default":"1","value_type":"DOUBLE"},{"index":7,"name":"OIL_WATER_VD_FACTOR","description":"","units":{},"default":"-1","value_type":"DOUBLE"},{"index":8,"name":"A","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":9,"name":"B1","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":10,"name":"B2","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":11,"name":"N","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","expected_columns":11,"size_kind":"fixed","size_count":1},"WSEGEXSS":{"name":"WSEGEXSS","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, WSEGEXSS, enables the import or export of fluids from a segment in a multi-segment well. This can be used to, for example, model gas lift injection for oil wells under artificial lift, or to approximate the behavior of a down-hole separator. The import-export fluid volumes can either be expressed as rates or defined as a function of a segment’s pressure value.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"SEGMENT","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"TYPE","description":"","units":{},"default":"NONE","value_type":"STRING"},{"index":4,"name":"GAS_IMPORT_RATE","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"GasSurfaceVolume/Time"},{"index":5,"name":"R","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time*Pressure"},{"index":6,"name":"PEXT","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Pressure"}],"example":"","expected_columns":6,"size_kind":"list"},"WSEGFLIM":{"name":"WSEGFLIM","sections":["SCHEDULE"],"supported":false,"summary":"WSEGFLIM enables an artificial choke that chokes a given phase flow rate for a segment in a multi-segment well. This can be used, for example, to constraint unwanted production phase through a section of tubing, or to model a down-hole choke. The keyword provides coefficients that are applied to the frictional pressure drop across a multi-segment well’s segment in order to inhibit production from that particular zone or segment. As such, the keyword does not actually model a down-hole choke; hence, the term artificial.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"SEGMENT1","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"SEGMENT2","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"LIMITED_PHASE1","description":"","units":{},"default":"NONE","value_type":"STRING"},{"index":5,"name":"FLOW_LIMIT1","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time"},{"index":6,"name":"A1","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":7,"name":"LIMITED_PHASE2","description":"","units":{},"default":"NONE","value_type":"STRING"},{"index":8,"name":"FLOW_LIMIT2","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"LiquidSurfaceVolume/Time"},{"index":9,"name":"A2","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":10,"name":"STATUS","description":"","units":{},"default":"OPEN","value_type":"STRING"}],"example":"","expected_columns":10,"size_kind":"list"},"WSEGFMOD":{"name":"WSEGFMOD","sections":["SCHEDULE"],"supported":false,"summary":"The WSEGFMOD declares the multi-phase flow model to be used to calculate the pressure drop within an individual segment for multi-segment wells. The FLOWOPT parameter on the WELSEGS keyword in the SCHEDULE section sets the default multi-segment well model. FLOWOPT is a character string that can be set to HO that activates the homogeneous model, that is all phases flow at the same velocity, or DF that invokes the Drift Flux Slip model (note OPM Flow only supports the default value of HO for the homogeneous model). Here WSEGFMOD can be used to set the flow model for a segment to either the homogeneous model or the Drift Flux Slip model, and addition a: VLP table allocated via the WSEGTABL keyword, or a specific model as defined by the WSEGVALV, WSEGFLIM and WSEGLABY keywords. All the aforementioned keywords are in the SCHEDULE section.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"SEGMENT1","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"SEGMENT2","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"FLOW_MODEL","description":"","units":{},"default":"HO","value_type":"STRING"},{"index":5,"name":"GAS_LIQUID_VD_FACTOR","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":6,"name":"A","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":7,"name":"B","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":8,"name":"FV","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":9,"name":"B1","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":10,"name":"B2","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","expected_columns":10,"size_kind":"list"},"WSEGINIT":{"name":"WSEGINIT","sections":["SCHEDULE"],"supported":false,"summary":"Normally the simulator calculates the initial conditions for multi-segment wells, that is the pressure and fluid distributions in each segment. However, there are occasions when manually setting the pressures and phase distributions for each segment to investigate certain flow conditions may be useful. In this case the WSEGINIT keyword may be used to specify the initial conditions manually. Note that segments not initialized by this keyword will be automatically initialized by the simulator","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"SEGMENT1","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"SEGMENT2","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"P0","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":5,"name":"W0","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":6,"name":"G0","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":7,"name":"RS","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":8,"name":"RV","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":9,"name":"API","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":10,"name":"POLYMER","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Concentration"},{"index":11,"name":"BRINE","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Concentration"}],"example":"","expected_columns":11,"size_kind":"list"},"WSEGITER":{"name":"WSEGITER","sections":["SCHEDULE"],"supported":null,"summary":"The WSEGITER keyword defines the multi-segment well solution iteration sequence and solution controls.","parameters":[{"index":1,"name":"MAX_WELL_ITERATIONS","description":"","units":{},"default":"40","value_type":"INT"},{"index":2,"name":"MAX_TIMES_REDUCED","description":"","units":{},"default":"5","value_type":"INT"},{"index":3,"name":"REDUCTION_FACTOR","description":"","units":{},"default":"0.3","value_type":"DOUBLE"},{"index":4,"name":"INCREASING_FACTOR","description":"","units":{},"default":"2","value_type":"DOUBLE"}],"example":"","expected_columns":4,"size_kind":"fixed","size_count":1},"WSEGLABY":{"name":"WSEGLABY","sections":["SCHEDULE"],"supported":false,"summary":"The WSEGSICD keyword defines a multi-segment well segment to be a labyrinth Inflow Control Device. (“ICD”) as part of a completion for a multi-segment well. Note that the well must have been previously define by the WELSPECS and WELSEGS keywords in the SCHEDULE section and that the data for the keyword should be repeated for each multi-segment completion that contains a labyrinth ICD.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"SEGMENT1","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"SEGMENT2","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"NCONFIG","description":"","units":{},"default":"","value_type":"INT"},{"index":5,"name":"CHANNELS","description":"","units":{},"default":"2","value_type":"INT"},{"index":6,"name":"A","description":"","units":{},"default":"6e-05","value_type":"DOUBLE","dimension":"Length*Length"},{"index":7,"name":"L1","description":"","units":{},"default":"0.1863","value_type":"DOUBLE","dimension":"Length"},{"index":8,"name":"L2","description":"","units":{},"default":"0.2832","value_type":"DOUBLE","dimension":"Length"},{"index":9,"name":"D","description":"","units":{},"default":"0.006316","value_type":"DOUBLE","dimension":"Length"},{"index":10,"name":"R","description":"","units":{},"default":"1e-05","value_type":"DOUBLE","dimension":"Length"},{"index":11,"name":"GAMMA_INLET","description":"","units":{},"default":"0.35","value_type":"DOUBLE"},{"index":12,"name":"GAMMA_OUTLET","description":"","units":{},"default":"0.5","value_type":"DOUBLE"},{"index":13,"name":"GAMMA_LAB","description":"","units":{},"default":"0.5","value_type":"DOUBLE"},{"index":14,"name":"STATUS","description":"","units":{},"default":"OPEN","value_type":"STRING"}],"example":"","expected_columns":14,"size_kind":"list"},"WSEGLINK":{"name":"WSEGLINK","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, WSEGLINK, specifies multi-segment well looped flow paths as part of a completion for a multi-segment well. A looped segment results in the nodes of the two individual segments that are looped (or connected) having the same solution pressures and oil, water and gas flowing rates.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"SEGMENT1","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"SEGMENT2","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":3,"size_kind":"list"},"WSEGMULT":{"name":"WSEGMULT","sections":["SCHEDULE"],"supported":false,"summary":"WSEGMULT supplies a set of constants used to modify (or scale) a multi-segment well’s segment frictional pressure drop between connecting segments The constants enable either a constant pressure to be applied, or for the pressure drop to vary as a function of the Gas-Oil Ratio (“GOR”) or the Water-Oil Ratio (“WOR”). The simulator calculated pressure drop is multiplied by the following resulting value:","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"SEGMENT1","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"SEGMENT2","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"A","description":"","units":{},"default":"1","value_type":"DOUBLE"},{"index":5,"name":"B","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":6,"name":"C","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":7,"name":"D","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":8,"name":"E","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":9,"name":"GOR","description":"","units":{},"default":"0","value_type":"DOUBLE"}],"example":"| [Frictional`Loss` Multipler~=~min left ( x sub{1}`+`x sub{2}(WOR) sup{x sub{3}}`+`x sub{4} left( GOR over {GOR sub{min} }right) sup {x sup{5}},~ 1.0 right)] | (12.38) |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|","expected_columns":9,"size_kind":"list"},"WSEGPROP":{"name":"WSEGPROP","sections":["SCHEDULE"],"supported":false,"summary":"The WSEGPROP keyword allows for the editing of exiting multi-segment wells created by WELSEGS keyword in the SCHEDULE section without having to re-define all the information that is on the WELSEGS keyword. Note that the well must have been previously define by both the WELSPECS and WELSEGS keywords in the SCHEDULE section to use the WSEGPROP keyword.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which a multi-segment well is being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"ISEG1","description":"A positive integer greater than or equal to two and less than or equal to MXSEGS on WSEGDIMS keyword in the RUNSPEC section that defines the start of a segment","units":{},"default":"None","value_type":"INT"},{"index":3,"name":"ISEG2","description":"A positive integer greater than or equal to two and less than or equal to ISEG1 on this record and MXSEGS on the WSEGDIMS keyword in the RUNSPEC section that defines the end of a segment.","units":{},"default":"None","value_type":"INT"},{"index":4,"name":"ID","description":"A real positive value that defines the tubing internal diameter of the segment for the well.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"Previous Entered Value","value_type":"DOUBLE","dimension":"Length"},{"index":5,"name":"EPSILON","description":"A real positive value that defines the tubing absolute roughness of the segment for the well.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"Previous Entered Value","value_type":"DOUBLE","dimension":"Length"},{"index":6,"name":"XAREA","description":"XAREA is real positive value equal to or greater than zero that defines the cross sectional area for fluid flow. Currently this option is not supported by OPM Flow.","units":{"field":"ft2","metric":"m2","laboratory":"cm2"},"default":"Previous Entered Value","value_type":"DOUBLE","dimension":"Length*Length"},{"index":7,"name":"VOLSEG","description":"VOLSEG is a real positive value that defines the effective segment volume for the this segment. Currently this option is not supported by OPM Flow.","units":{"field":"ft3","metric":"m3","laboratory":"cm3"},"default":"Previous Entered Value","value_type":"DOUBLE","dimension":"Length*Length*Length"},{"index":8,"name":"XAREAS","description":"XAREAS is real positive value equal to or greater than zero that defines the cross sectional area of the pipe wall for this segment, that is used in thermal conductivity calculations for when the temperature calculation is activated by the TEMP keyword in the RUNSPEC section. Currently this option is not supported by OPM Flow.","units":{},"default":"Previous Entered Value","value_type":"DOUBLE","dimension":"Length*Length"},{"index":9,"name":"VHEATCAP","description":"VHEATCAP is real positive value equal to or greater than zero that defines the volumetric heat capacity of the pipe wall used in thermal conductivity calculations for when the temperature calculation is activated by the TEMP keyword in the RUNSPEC section. Currently this option is not supported by OPM Flow.","units":{"field":"Btu/ft/day/°R","metric":"kJ/m/day/K","laboratory":"J/cm/hr/K"},"default":"Previous Entered Value","value_type":"DOUBLE"},{"index":10,"name":"THCON","description":"THCON is real positive value equal to or greater than zero that defines the thermal conductivity of the pipe wall used in thermal conductivity calculations for when the temperature calculation is activated by the TEMP keyword in the RUNSPEC section. Currently this option is not supported by OPM Flow.","units":{"field":"Btu/ft/day/°R","metric":"kJ/m/day/K","laboratory":"J/cm/hr/K"},"default":"Previous Entered Value","value_type":"DOUBLE"}],"example":"The following example modifies two segments in well OP01 and one segment in well OP02.\n--\n-- WELL SEGMENT SPECIFICATION DATA\n--\n-- WELL SEG SEG TUBE TUBE XSEC VOL\n-- NAME ISTR IEND ID ROUGH AREA SEG\nWSEGPROP\nOPO1 12 14 0.3 0.00010 /\nOP01 13 15 0.275 0.00010 /\nOP02 14 14 0.275 0.00010 /\n/\nNote that the two multi-segment wells and their respective segments must have been previously defined by the WELSEGS keyword.","expected_columns":10,"size_kind":"list"},"WSEGPULL":{"name":"WSEGPULL","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, WSEGPULL, specifies a multi-segment well segment to be a pull-through pump for a down-hole water separator, defined by the WSEGSEP keyword in the SCHEDULE section, and defines the various parameters for this type of pump. Down-hole separators are used to separate water or free gas from the in situ fluid entering the wellbore in order to increase hydrocarbon recovery.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"SEGMENT1","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"SEGMENT2","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"P","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":5,"name":"DP","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":6,"name":"OIL_RATE_LIMIT","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Volume/Time"},{"index":7,"name":"GRADIENT_FACTOR","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Pressure*Time/Volume"}],"example":"","expected_columns":7,"size_kind":"list"},"WSEGSEP":{"name":"WSEGSEP","sections":["SCHEDULE"],"supported":false,"summary":"WSEGSEP specifies a multi-segment well segment to be a down-hole separator, that enables the separation of fluids down-hole. Down-hole separators are used to separate water or free gas from the in situ fluid entering the wellbore in order to increase hydrocarbon recovery. See also the WSEGPULL keyword in the SCHEDULE section that specifies a pull-through pump for a down-hole water separator.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"SEGMENT1","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"SEGMENT2","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"PHASE","description":"","units":{},"default":"NONE","value_type":"STRING"},{"index":5,"name":"EMAX","description":"","units":{},"default":"1","value_type":"DOUBLE"},{"index":6,"name":"HOLDUP_FRACTION","description":"","units":{},"default":"0.01","value_type":"DOUBLE"}],"example":"","expected_columns":6,"size_kind":"list"},"WSEGSICD":{"name":"WSEGSICD","sections":["SCHEDULE"],"supported":null,"summary":"The WSEGSICD keyword defines a multi-segment well segment to be a spiral Inflow Control Device (“ICD”) as part of a completion for a multi-segment well. Note that the well must have been previously defined by the WELSPECS and WELSEGS keywords in the SCHEDULE section and that the data for the keyword should be repeated for each multi-segment completion that contains a spiral ICD.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which a multi-segment well is being defined. Note that the well name (WELNAME) must have been declared previously using both the WELSPECS and WELSEGS keywords in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"ISEG1","description":"A positive integer greater than or equal to two and less than or equal to MXSEGS on the WSEGDIMS keyword in the RUNSPEC section that defines the start of a segment","units":{},"default":"None","value_type":"INT"},{"index":3,"name":"ISEG2","description":"A positive integer greater than or equal to two and not less then ISEG1 on this record and less than or equal to MXSEGS on the WSEGDIMS keyword in the RUNSPEC section, that defines the end of a segment","units":{},"default":"None","value_type":"INT"},{"index":4,"name":"ICDSTREN","description":"A real positive value greater than zero that defines an empirical constant for the strength of the given ICD as determined from measurements using the calibrated fluid.","units":{"field":"psia(rft3/day)2","metric":"barsa/(rm3/day)2","laboratory":"atma/(rcc/hr)2"},"default":"None","value_type":"DOUBLE","dimension":"Pressure*Time*Time/GeometricVolume*GeometricVolume"},{"index":5,"name":"ICDLEN","description":"A real value that defines the length of the ICD used in conjunction with NSCALFAC to calculate a scaling factor to be applied to the reservoir flow to adjust the flow through each ICD, that is: If NSCALFAC equals zero: then the scale factor is equal to the length of the ICD (ICDLEN) divided by the length of the tubing section, that is the parent of the ICDs, then this allows for the case when the ICD segment may represent a number of ICDs in parallel. If NSCALFAC equals one: then the scale factor is equal to the absolute value of ICDLEN. If NSCALFAC equals two: then the scale factor is equal to the length of ICDLEN, divided by the total length of the completions which supply the ICD. NSCALFAC explicitly sets which of the above three options is used. If NSCALFAC is defaulted, then option 1) is used whenever ICDLEN is positive and option 2) when ICDLEN is negative.","units":{"field":"feet 39.37","metric":"m 12.00","laboratory":"cm 1,2000"},"default":"Defined","value_type":"DOUBLE","dimension":"Length"},{"index":6,"name":"CALDEN","description":"CALDEN is a real positive value greater than zero that defines the density of the calibrating fluid at surface conditions.","units":{"field":"lb/ft3 62.416","metric":"kg/m3 1000.25","laboratory":"gm/cc 1.00025"},"default":"Defined","value_type":"DOUBLE","dimension":"Density"},{"index":7,"name":"CALVISC","description":"CALVISC is a real positive value greater than zero that defines the viscosity of the calibrating fluid at surface conditions.","units":{"field":"cP","metric":"cP","laboratory":"cP"},"default":"1.45","value_type":"DOUBLE","dimension":"Viscosity"},{"index":8,"name":"EMLCRT","description":"EMLCRT is a real positive value greater than zero that defines the “local water” in liquid fraction used to determine whether the “water-in-oil” or “oil-in-water” viscosity emulation equation should be applied.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.5","value_type":"DOUBLE","dimension":"1"},{"index":9,"name":"EMLTRANS","description":"EMLTRANS is a real positive value greater than zero that defines the width of the transition zone around EMLCRT and is used to ensure that the calculated viscosity forms a continuous function of water in liquid fraction. Within this region, the emulsion viscosity is a linear interpolation between the “water-in-oil” and “oil-in-water” viscosity values either side of the region.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"0.05","value_type":"DOUBLE","dimension":"1"},{"index":10,"name":"EMLMAX","description":"EMLMAX is a real positive value greater than zero that defines the maximum emulsion viscosity to continuous phase viscosity (oil or water) ratio.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"5.0","value_type":"DOUBLE","dimension":"1"},{"index":11,"name":"NSCALFAC","description":"NSCALFAC is a positive integer value that is greater than or equal to zero, that sets the method to be used when applying the scaling factor and should be set to one of the following: If NSCALFAC equals zero: then the scale factor is equal to the length of the ICD (ICDLEN) divided by the length of the tubing section, that is the parent of the ICDs, then this allows for the case when the ICD segment may represent a number of ICDs in parallel. If NSCALFAC equals one: then the scale factor is equal to the absolute value of ICDLEN. If NSCALFAC equals two: then the scale factor is equal to the length of ICDLEN, divided by the total length of the completions which supply the ICD. NSCALFAC explicitly sets which of the above three options is used. If NSCALFAC is defaulted, then option 1) is used whenever ICDLEN is positive and option 2) when ICDLEN is negative.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"-1","value_type":"INT"},{"index":12,"name":"CALRATE","description":"A real positive value that defines the maximum surface flow rate for which the ICD was calibrated.","units":{"field":"scf/d","metric":"sm3/day","laboratory":"scc/hour"},"default":"None","value_type":"DOUBLE","dimension":"GeometricVolume/Time"},{"index":13,"name":"STATUS","description":"A defined character string of length four that defines the ICD’s operational status, STATUS should be set to one of the following character strings: OPEN: the ICD connections are are open to flow. SHUT: the ICD connections are closed to flow (shut-in).","units":{},"default":"OPEN","value_type":"STRING","options":["OPEN","SHUT"]}],"example":"The following example defines one producing well segment oil well (OP01) using the WELSPECS, WELSEGS COMPDAT and COMPSEGS keywords, followed by the WSEGSICD keyword to define the spiral inflow control devices for the well.\n--\n-- WELL SPECIFICATION DATA\n--\n-- WELL GROUP LOCATION BHP PHASE DRAIN INFLOW OPEN CROSS PVT\n-- NAME NAME I J DEPTH FLUID AREA EQUANS SHUT FLOW TABLE\nWELSPECS\nOP01 PLATFORM 10 10 1* OIL /\n/\n--\n-- WELL CONNECTION DATA\n--\n-- WELL --- LOCATION --- OPEN SAT CONN WELL KH SKIN D DIR\n-- NAME II JJ K1 K2 SHUT TAB FACT DIA FACT FACT FACT PEN\nCOMPDAT\nOP01 10 10 1 1 OPEN 1* 200. 0.5 /\nOP01 10 10 2 2 OPEN 1* 200. 0.5 /\nOP01 10 10 3 3 OPEN 1* 200. 0.4 /\nOP01 10 10 4 4 OPEN 1* 200. 0.4 /\nOP01 10 10 5 5 OPEN 1* 200. 0.4 /\nOP01 10 10 6 6 OPEN 1* 200. 0.4 /\nOP01 9 10 2 2 OPEN 1* 200. 0.4 /\nOP01 8 10 2 2 OPEN 1* 200. 0.4 /\nOP01 7 10 2 2 OPEN 1* 200. 0.4 /\nOP01 6 10 2 2 OPEN 1* 200. 0.4 /\nOP01 5 10 2 2 OPEN 1* 200. 0.4 /\nOP01 10 9 3 3 OPEN 1* 200. 0.4 /\nOP01 10 8 3 3 OPEN 1* 200. 0.4 /\nOP01 10 7 3 3 OPEN 1* 200. 0.4 /\nOP01 10 6 3 3 OPEN 1* 200. 0.4 /\nOP01 10 5 3 3 OPEN 1* 200. 0.4 /\nOP01 9 10 5 5 OPEN 1* 200. 0.4 /\nOP01 8 10 5 5 OPEN 1* 200. 0.4 /\nOP01 7 10 5 5 OPEN 1* 200. 0.4 /\nOP01 6 10 5 5 OPEN 1* 200. 0.4 /\nOP01 5 10 5 5 OPEN 1* 200. 0.4 /\nOP01 10 9 6 6 OPEN 1* 200. 0.4 /\nOP01 10 8 6 6 OPEN 1* 200. 0.4 /\nOP01 10 7 6 6 OPEN 1* 200. 0.4 /\nOP01 10 6 6 6 OPEN 1* 200. 0.4 /\nOP01 10 5 6 6 OPEN 1* 200. 0.4 /\n/\n--\n-- WELL SEGMENT SPECIFICATION DATA\n--\n-- WELL NODAL LEN WELL DEPH PRESS FLOW\n-- NAME DEPTH TUBING VOLM OPTN CALC MODEL\nWELSEGS\nOP01 2512.5 2512.5 1.0E-5 ABS HFA HO /\n--\n-- SEG SEG BRAN SEG TUBING NODAL TUBE TUBE XSEC VOL\n-- ISTR IEND NO NO LENGTH DEPTH ID ROUGH AREA SEG\n2 2 1 1 2537.5 2534.5 0.3 0.00010 /\n3 3 1 2 2562.5 2560.5 0.3 0.00010 /\n4 4 1 3 2587.5 2593.5 0.3 0.00010 /\n5 5 1 4 2612.5 2614.5 0.3 0.00010 /\n6 6 1 5 2637.5 2635.5 0.3 0.00010 /\n7 7 2 2 2737.5 2538.5 0.2 0.00010 /\n8 8 2 7 2937.5 2537.5 0.2 0.00010 /\n9 9 2 8 3137.5 2539.5 0.2 0.00010 /\n10 10 2 9 3337.5 2535.5 0.2 0.00010 /\n11 11 2 10 3537.5 2536.5 0.2 0.00010 /\n12 12 3 3 2762.5 2563.5 0.2 0.00010 /\n13 13 3 12 2962.5 2562.5 0.1 0.00010 /\n14 14 3 13 3162.5 2562.5 0.1 0.00010 /\n15 15 3 14 3362.5 2564.5 0.1 0.00010 /\n16 16 3 15 3562.5 2562.5 0.1 0.00010 /\n17 17 4 5 2812.5 2613.5 0.2 0.00010 /\n18 18 4 17 3012.5 2612.5 0.1 0.00010 /\n19 19 4 18 3212.5 2612.5 0.1 0.00010 /\n20 20 4 19 3412.5 2612.5 0.1 0.00010 /\n21 21 4 20 3612.5 2613.5 0.1 0.00010 /\n22 22 5 6 2837.5 2634.5 0.2 0.00010 /\n23 23 5 22 3037.5 2637.5 0.2 0.00010 /\n24 24 5 23 3237.5 2638.5 0.2 0.00010 /\n25 25 5 24 3437.5 2639.5 0.1 0.00010 /\n26 26 5 25 3637.5 2639.5 0.1 0.00010 /\n/\n--\n-- COMPLETION SEGMENT SPECIFICATION DATA\n--\n-- WELL\n-- NAME\nCOMPSEGS\nOP01 /\n--\n-- --LOCATION-- BRAN TUBING NODAL DIR LOC MID COMP ISEG\n-- II JJ K1 NO LENGTH DEPTH PEN I,J,K PERFS LENGTH NO.\n10 10 1 1 2512.5 2525.0 /\n10 10 2 1 2525.0 2550.0 /\n10 10 3 1 2550.0 2575.0 /\n10 10 4 1 2575.0 2600.0 /\n10 10 5 1 2600.0 2625.0 /\n10 10 6 1 2625.0 2650.0 /\n9 10 2 2 2637.5 2837.5 /\n8 10 2 2 2837.5 3037.5 /\n7 10 2 2 3037.5 3237.5 /\n6 10 2 2 3237.5 3437.5 /\n5 10 2 2 3437.5 3637.5 /\n10 9 3 3 2662.5 2862.5 /\n10 8 3 3 2862.5 3062.5 /\n10 7 3 3 3062.5 3262.5 /\n10 6 3 3 3262.5 3462.5 /\n10 5 3 3 3462.5 3662.5 /\n9 10 5 4 2712.5 2912.5 /\n8 10 5 4 2912.5 3112.5 /\n7 10 5 4 3112.5 3312.5 /\n6 10 5 4 3312.5 3512.5 /\n5 10 5 4 3512.5 3712.5 /\n10 9 6 5 2737.5 2937.5 /\n10 8 6 5 2937.5 3137.5 /\n10 7 6 5 3137.5 3337.5 /\n10 6 6 5 3337.5 3537.5 /\n10 5 6 5 3537.5 3737.5 /\n--\n-- MULTI-SEGMENT WELL ICD SEGMENT SPECIFICATION DATA\n--\n-- WELL SEG SEG ICD ICD CAL CAL EML EML EML SCAL CAL OPEN\n-- NAME ISTR IEND STRNEN LEN DEN VISC CRIT TRANS MAX FAC RATE CLOSE\nWSEGSICD\nOP01 7 10 0.00025 1* 1.0 0.45 0.50 0.05 5.0 2 1* OPEN /\nOP01 12 15 0.00025 1* 1.0 0.45 0.50 0.05 5.0 2 1* OPEN /\nOP01 17 20 0.00025 1* 1.0 0.45 0.50 0.05 5.0 2 1* OPEN /\nOP01 22 22 0.00025 1* 1.0 0.45 0.50 0.05 5.0 2 1* OPEN /\nOP01 23 23 0.00025 1* 1.0 0.45 0.50 0.05 5.0 2 1* OPEN /\nOP01 24 24 0.0002","expected_columns":13,"size_kind":"list"},"WSEGSOLV":{"name":"WSEGSOLV","sections":["SCHEDULE"],"supported":false,"summary":"The WSEGSOLV keyword defines the numerical control parameters for the iterative linear solver for multi-segment well looped flow paths, as defined by the WSEGLINK keyword in the SCHEDULE section. A looped segment results in the nodes of the two individual segments that are looped (or connected) having the same solution pressures and oil, water and gas flowing rates.","parameters":[{"index":1,"name":"USE_ITERATIVE_SOLVER","description":"","units":{},"default":"NO","value_type":"STRING"},{"index":2,"name":"MAX_LINEAR_ITER","description":"","units":{},"default":"30","value_type":"INT"},{"index":3,"name":"CONVERGENCE_TARGET","description":"","units":{},"default":"1e-10","value_type":"DOUBLE"},{"index":4,"name":"PC_FILL","description":"","units":{},"default":"2","value_type":"INT"},{"index":5,"name":"DROP_TOL","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":6,"name":"P_LIMIT","description":"","units":{},"default":"1e-08","value_type":"DOUBLE"},{"index":7,"name":"LOOP_THRESHOLD","description":"","units":{},"default":"-1","value_type":"DOUBLE","dimension":"Length*Length*Length/Time"},{"index":8,"name":"LOOP_MULTIPLIER","description":"","units":{},"default":"-1","value_type":"DOUBLE"}],"example":"","expected_columns":8,"size_kind":"fixed","size_count":1},"WSEGTABL":{"name":"WSEGTABL","sections":["SCHEDULE"],"supported":false,"summary":"WSEGTABL assigns previously defined Vertical Lift Performance (“VLP”) tables as specified by the VFPPROD keyword in the SCHEDULE section, to multi-segment well segments, as well as stipulating how the tables are to be applied.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"SEGMENT1","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"SEGMENT2","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"VFP","description":"","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"VFP_COMPONENTS","description":"","units":{},"default":"FH","value_type":"STRING"},{"index":6,"name":"VFP_OUTLIER","description":"","units":{},"default":"","value_type":"STRING"},{"index":7,"name":"DP_SCALING","description":"","units":{},"default":"LEN","value_type":"STRING"},{"index":8,"name":"ALQ_VALUE","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":9,"name":"STATUS","description":"","units":{},"default":"OPEN","value_type":"STRING"}],"example":"","expected_columns":9,"size_kind":"list"},"WSEGVALV":{"name":"WSEGVALV","sections":["SCHEDULE"],"supported":null,"summary":"The WSEGVALV keyword defines a multi-segment well segment to be a sub-critical valve Inflow Control Device (“ICD”) as part of a completion for a multi-segment well. Note that the well must have been previously defined by the WELSPECS and WELSEGS keywords in the SCHEDULE section and that the data for the keyword should be repeated for each multi-segment completion that contains a sub-critical valve ICD.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which a multi-segment well is being defined. Note that the well name (WELNAME) must have been declared previously using both the WELSPECS and WELSEGS keywords in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"ISEG1","description":"A positive integer greater than or equal to two and less than or equal to MXSEGS on the WSEGDIMS keyword in the RUNSPEC section that defines the segment containing the sub-critical valve.","units":{},"default":"None","value_type":"INT"},{"index":3,"name":"ICDCV","description":"A real positive value greater than zero that defines the dimensionless flow coefficient for the valve (Cv). This a vendor specific value for a given vendor’s ICD.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"DOUBLE"},{"index":4,"name":"AREAREST","description":"A real positive value that defines the cross-sectional area of flow in the restricted section of the valve (Ar) and should have a minimum value of 1.0 x 10-10. This value may be specified using a User Defined Argument (UDA). AREAREST is used to convert the segment volumetric flow rate into the flow velocity at the constriction (υr).","units":{"field":"ft2","metric":"m2","laboratory":"cm2"},"default":"None","value_type":"UDA","dimension":"Length*Length"},{"index":5,"name":"SEGLEN","description":"A real positive value greater than or equal to zero that defines the additional pipe length for the frictional pressure drop (L). If set to zero then there is no additional pressure loss due to friction, whereas, if set to the default (1*), then the segment pipe length is calculated from the corresponding WELSEGS keyword.","units":{"field":"ft","metric":"m","laboratory":"cm"},"default":"Defined","value_type":"DOUBLE","dimension":"Length"},{"index":6,"name":"ID","description":"A real positive value that defines the pipe internal diameter of the segment used to calculate the pressure drop due to friction (D). The value is used to replace the segment pipe internal diameter defined on the WELSEGS keyword in record 2-7, also named ID. If ID is defaulted on this keyword then the equivalent value on the WELSEGS keyword will be used instead. Note for non-circular pipe segments use the equivalent diameter instead, that is: [Equivalent ID``=``{ 4.0 times (Cross-Sectional Area) } over Perimeter]","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"Defined","value_type":"DOUBLE","dimension":"Length"},{"index":7,"name":"EPSILON","description":"A real positive value that defines the pipe absolute roughness for this segment. The value is used to replace the segment pipe absolute roughness defined on the WELSEGS keyword in record 2-8, also named EPSILON. If EPSILON is defaulted on this keyword then the equivalent value on the WELSEGS keyword will be used instead.","units":{"field":"feet","metric":"m","laboratory":"cm"},"default":"Defined","value_type":"DOUBLE","dimension":"Length"},{"index":8,"name":"AREAPIPE","description":"A real positive value that defines the cross-sectional area of flow in the pipe (Ap), as opposed to the restricted section of the valve (Ar). AREAPIPE is used to convert the segment volumetric flow rate into the flow velocity through the pipe (υp). The value is used to replace the segment pipe cross-sectional area of flow defined on the WELSEGS keyword in record 2-9, named XAREA. If AREAPIPE is defaulted on this keyword then the equivalent value on the WELSEGS keyword will be used instead.","units":{"field":"ft2","metric":"m2","laboratory":"cm2"},"default":"Defined","value_type":"DOUBLE","dimension":"Length*Length"},{"index":9,"name":"STATUS","description":"A character string of length four that defines the ICD’s operational status, STATUS should be set to one of the following character strings: OPEN: the ICD connections are are open to flow. SHUT: the ICD connections are closed to flow (shut-in).","units":{},"default":"OPEN","value_type":"STRING","options":["OPEN","SHUT"]},{"index":10,"name":"AREAMAX","description":"A real positive value that defines the maximum cross-sectional area of flow in the restricted section of the valve (Amax). AREAMAX is used to convert the segment volumetric flow rate into the maximum flow velocity at the constriction (υr). If defaulted then AREAPIPE will be used if defined, otherwise XAREA (item 2-9) on the WELSEGS keyword will be used.","units":{"field":"ft2","metric":"m2","laboratory":"cm2"},"default":"Defined","value_type":"DOUBLE","dimension":"Length*Length"}],"example":"The following example is based on one producing well segment oil well (OP01) using the WELSPECS, WELSEGS COMPDAT and COMPSEGS keywords, as per the WSEGSICD keyword example (Example), and is therefore not repeated here.\n--\n-- MULTI-SEGMENT WELL ICD SEGMENT SPECIFICATION DATA\n--\n-- WELL SEG DEVICE AREA PIPE PIPE PIPE PIPE OPEN MAX\n-- NAME NO CV REST LENG ID EPSI AREA SHUT AREA\nWSEGVALV OP01 7 0.960 0.012 1* 1* 1* 1* OPEN 1* / DEFAULT VALUES\nOP01 12 0.960 0.012 1* 1* 1* 1* OPEN 1* / TAKEN FROM\nOP01 17 0.960 0.012 1* 1* 1* 1* OPEN 1* / WELSEGS KEYWORD\nOP01 22 0.850 0.100 1* 1* 1* 1* OPEN 1* /\nOP01 23 0.850 0.100 1* 1* 1* 1* OPEN 1* /\nOP01 24 0.850 0.100 1* 1* 1* 1* OPEN 1* /\nOP01 25 0.850 0.100 1* 1* 1* 1* OPEN 1* /\n/\nHere segments 7, 12 and 17 have the same type of sub-critical valves with their pipe properties taken from the WELSEGS keyword used to define well OP01 as a multi-segment well. Similarly, segments 22 to 25 have the same ICD properties, and again the pipe properties are taken from the WELSEGS keyword.\n| [%delta P ~=~ %delta P sub restriction ``+``%delta P sub friction newline\nnewline\nwhere newline\n%delta P sub restriction ``=``C sub 1 {%rho {%upsilon sup 2} sub r} over { 2{C sub v} }sup 2 newline\nnewline\n%delta P sub friction ``=`` 2C sub 2 f L over D %upsilon sup 2 sub p] | (12.42) |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|\n| Conversion Factor Constants and Variable Units | | | | | |\n|------------------------------------------------|-----------------|---------------|---------------|---------------|----------|\n| No. | Name | Field | Metric | Laboratory | Property |\n| 1 | C1 | 2.159 x 10-4 | 1.0 x 10-5 | 9.869 x 10-7 | Constant |\n| 2 | C2 | 2.892 x 10-14 | 1.340 x 10-15 | 7.615 x 10-14 | |\n| 3 | Density | lb/ft3 | kg/m3 | gm/cc | Units |\n| 4 | Pressure | psia | bars | atm | |\n| 5 | Velocity | ft/s | m/s | cm/s | |\n| 6 | Volumetric Flow | ft3/day | m3/day | cc/hour | |\n| [q ``=``%upsilon sub r A sub r ``=``%upsilon sub p A sub p] | (12.43) |\n|-------------------------------------------------------------|---------|\n| [%delta P sub restriction ``=``C sub 2 {%rho {q} sup 2} over {{ 2{C sub v} }sup 2 A sup 2 sub r}] | (12.44) |\n|---------------------------------------------------------------------------------------------------|---------|\n| [K ``=` {`C sub 2} over {{ 2{C sub v} }sup 2 A sup 2 sub r}] | (12.45) |\n|--------------------------------------------------------------|---------|\n| [Seting of Device ``=`` { A sub r } over { A sub max }] | (12.46) |\n|---------------------------------------------------------|---------|","expected_columns":10,"size_kind":"list"},"WSKPTAB":{"name":"WSKPTAB","sections":["SCHEDULE"],"supported":null,"summary":"The WSKPTAB keyword assigns the well polymer molecular water and polymer skin tables to water injection wells in OPM Flow's Polymer Molecular Weight Transport option, that uses the polymer molecular weight in calculating the polymer viscosity, as well as accounting for formation damage due to the water and polymer injection, by adjusting the wellbore skin pressure. This keyword should only be used if the POLYMER and POLYMW keywords in the RUNSPEC section are also activated. The keyword assigns the water SKPRWAT tables, that are defined via the SKPRWAT keyword in the PROPS section, that are used to calculable the wellbore skin pressure during water injection. As well as the polymer SKPRPOLY tables, that are defined via the SKPRPOLY keyword in the PROPS section, that are used to calculable the wellbore skin pressure during polymer injection.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length, that defines the water injection well name, for which the well water injection skin table, SKKPRWAT, and the polymer skin injection table, SKPRPOLY, are to be assigned. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"SKPRWAT","description":"A positive integer value that defines the corresponding SKPRWAT table to be allocated to the water injection well. A value less than or equal to zero means that no SKPRWAT table is allocated to the well","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"SKPRPOLY","description":"A positive integer value that defines the corresponding SKPRPOLY table to be allocated to the water injection well. A value less than or equal to zero means that no SKPRPOLY table is allocated to the well","units":{},"default":"0","value_type":"INT"}],"example":"Given NTSKWAT equals two and NTSKPOLY equals three on the PINTDIMS keyword in the RUNSPEC section, then:\n--\n-- ASSIGN WELL POLYMER MOLECULAR MODEL SKIN TABLES\n--\n-- WELL SKPRWAT SKPRPOLY\n-- NAME TABLE TABLE\nWSKPTAB\nWI01 1 1 /\nWI02 1 3 /\nWI03 2 2 /\n/\nAssigns SKPRWAT table one to wells WI01 and WI02 and table two to WI03, and SKPRPOLY tables one, two and three to wells WI01, WI03, and WI02, respectively.\n| Note This is an OPM Flow specific keyword that employs an alternative polymer flood model based on a Polymer Molecular Weight Transport equation, that is not available in the commercial simulator. |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|","expected_columns":3,"size_kind":"list"},"WSOLVENT":{"name":"WSOLVENT","sections":["SCHEDULE"],"supported":null,"summary":"WSOLVENT defines a gas injection well’s solvent fraction in the injection stream that is to be used when the Solvent option has been activated by the SOLVENT keyword in the RUNSPEC section.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name of a gas injection well for which the solvent fraction data is being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"SOLVENT_FRACTION","description":"","units":{},"default":"","value_type":"UDA","dimension":"1"},{"index":4,"name":"SOLFRA","description":"A real positive value greater than or equal to zero and less than or equal to one that defines the fraction of solvent in the gas well’s injection stream. This value may be specified using a User Defined Argument (UDA).","units":{"field":"fraction","metric":"fraction","laboratory":"fraction"},"default":"None"}],"example":"The following example defines the solvent fractions for three gas injection wells for when the solvent option has been activated by the SOLVENT keyword in the RUNSPEC section.\n--\n-- DEFINE GAS INJECTION WELL SOLVENT FRACTION\n--\n-- WELL SOLVENT\n-- NAME FRACTION\n-- --------\nWSOLVENT\nGI01 0.0000 /\nGI02 0.5000 /\nGI03 0.5000 /\n/\nThe solvent fraction for the GI01 gas injector is set to zero and both GI02 and GI03 gas injectors have solvent fraction values of 0.5 for their injection streams.","expected_columns":2,"size_kind":"list"},"WSURFACT":{"name":"WSURFACT","sections":["SCHEDULE"],"supported":false,"summary":"WSURFACT defines a water injection well’s surfactant concentration in the injection stream that is to be used when the Surfactant phase has been activated by either the SURFACT or SURFACTW keywords in the RUNSPEC section.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name of a gas injection well for which the solvent fraction data is being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"SURCON","description":"A real positive value that defines the surfactant concentration of the well’s injection stream.","units":{"field":"lb/stb","metric":"kg/sm3","laboratory":"gm/scc"},"default":"None","value_type":"UDA","dimension":"Concentration"}],"example":"The following example defines the surfactant concentrations for three water injection wells for when the surfactant phase option has been activated by either the SURFACT or SURFACTW keywords in the RUNSPEC section. Here the surfactant concentration has been set to 0.200 for all three wells.\n--\n-- DEFINE WATER INJECTION WELL SURFACTANT CONCENTRATION\n--\n-- WELL SURFACT\n-- NAME SURCON\n-- --------\nWSURFACT\nWI01 0.2000 /\nWI02 0.2000 /\nWI03 0.2000 /\n/","expected_columns":2,"size_kind":"list"},"WTADD":{"name":"WTADD","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, WTADD, adds a constant to a previously define well’s target or constraint, as stated on the WCONPROD, WCONINJE, or WELTARG keywords, but not for the history matching wells using the WCONHIST or WCONINJH keywords. All the aforementioned keywords are in the SCHEDULE section. The constant can be positive or negative.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"CONTROL","description":"The control mode seems to be a UDA??","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"SHIFT","description":"","units":{},"default":"","value_type":"UDA"},{"index":4,"name":"NUM","description":"","units":{},"default":"1","value_type":"INT"}],"example":"","expected_columns":4,"size_kind":"list"},"WTEMP":{"name":"WTEMP","sections":["SCHEDULE"],"supported":null,"summary":"The WTEMP keyword defines the temperature of the injection fluid being injected by an injection well.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for an injection well for which the injection well fluid’s temperature data is being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"TEMP","description":"A real positive value greater than zero that defines the temperature of the injected fluid.","units":{"field":"oF","metric":"oC","laboratory":"oC"},"default":"None","value_type":"DOUBLE","dimension":"Temperature"}],"example":"The following example defines the injected fluid temperatures for three water injection wells for when the thermal option has been activated by the THERMAL keyword in the RUNSPEC section.\n--\n-- DEFINE INJECTION WELL FLUID TEMPERATURE\n--\n-- WELL FLUID\n-- NAME TEMP.\n-- --------\nWTEMP\nWI01 39.00 /\nWI02 37.00 /\nWI03 39.00 /\n/\nHere wells WI01 and WI03 inject water with a water temperature of 39 oF and well WI02’s injection water temperature is 37 oF.","expected_columns":2,"size_kind":"list"},"WTEMPQ":{"name":"WTEMPQ","sections":["SCHEDULE"],"supported":false,"summary":"The WTEMPQ prints out a user defined selected list of currently defined wells and well lists to the print file (*.PRT). The keyword allows for sub-setting the well names etc., using the normal well and well list naming conventions. For example to list all wells beginning with the characters “OP” then one would use “OP*” as the well name on this keyword.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"LGR","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":2,"size_kind":"list"},"WTEST":{"name":"WTEST","sections":["SCHEDULE"],"supported":false,"summary":"The WTEST keyword outlines the testing procedures to be applied to wells that are closed for various reasons to see if the wells are capable flowing under the current operating conditions. The keyword can be applied to single wells or groups of wells.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name of the well to be tested. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"TIME","description":"A real value greater than zero that defines the minimum period of time that must elapse between well tests. The next well test is performed at the beginning of the next time step after the specified period of time has elapsed since the previous well test, for example if TIME is set equal to 365.25 (days), the test is performed approximately every year.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"None","value_type":"DOUBLE","dimension":"Time"},{"index":3,"name":"TEST","description":"A character string of up to five characters in length that defines a list of reasons why a well could have been closed. If a well was closed for one of the specified reasons then the well is tested to see if it can be put back on production. The characters that can be used to define TEST are as follows: P: meaning the well was closed due to a bottom-hole or tubing head pressure limit, or other physical limit then the well is tested to see if it can flow, if it can, then it is put back on production, otherwise it remains closed. E: meaning the well was closed due to a well or a well connection economic constraint then the well is tested to see if it can flow, if it can then it is put back on production, otherwise it remains closed. Here, if the well has at least one connection open then the well is opened. If a well has no open connections, then those connections that have been closed due to an economic limit test (\"ELT\"), are all individually tested and reopened if they meet the ELT criteria as defined by the WECON, CECON and WECONINJ keywords in the SCHEDULE section. And the well is opened if it has at least one open connection. Where the ELT applies to ORAT, GRAT, WCUT, GOR and WGR etc. G: meaning the well was closed due to a group economic constraint, as per the GECON, GECONT, GCONCAL, GCONPRI, GCONPROD, and GCONSALE, keywords in the SCHEDULE section, then the well is tested to see if it can flow, if it can, then it is put back on production, otherwise it remains closed. D: not supported by OPM Flow. C: not supported by OPM Flow. The default value is an empty string “ ” that switches off testing. Note that only the P, E and G options are currently supported in OPM Flow.","units":{},"default":"“ ”","value_type":"STRING"},{"index":4,"name":"NTIME","description":"A positive integer greater than or equal to zero that define the number of times a well can be tested. The default value of zero means an infinite number of times.","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"START","description":"A real positive value that defines the start up time used to prorate the rate at which the well is put back on production. If START is large compared to the time step size, then the well is brought on gradually, if it is less than the time step size, then the well is opened faster. The rate is prorated based on the following: [Q_i~=~Q_final times left({T_{End of Time Step}`- `T_opened} over START right)] The default value of 0.0 means the well is opened immediately.","units":{"field":"days","metric":"days","laboratory":"hours"},"default":"0.0","value_type":"DOUBLE","dimension":"Time"}],"example":"The following example defines test criteria for all gas wells (‘GP*’) and three oil wells (OP01, OP02, and OP03).\n--\n--\n-- WELL TESTING CRITERIA FOR RE-OPENING CLOSED WELLS\n--\n-- WELL TST TST NO. STRT\n-- NAME INTV TYPE TSTS TIME\n-- ---- ---- ---- ---- ----\nWTEST\n‘GP*’ 365.25 P 5 0.0\nOP01 30.0 PEG 0 0.0 /\nOP02 30.0 PEG 0 0.0 /\nOPO3 30.0 PEG 0 0.0 /\n/\nAll the gas wells are test annually if they have been shut-in due to a bottom-hole or tubing head pressure limit, are tested five times after they have been closed, and are opened up immediately. The oil wells are tested every 30 days if they have been closed due to a bottom-hole or tubing head pressure limit, a well economic limit or a group economic limit. All the oil wells are tested an infinite amount of times and are opened up immediately. Note that only the P, E and G options are currently supported in OPM Flow.","expected_columns":5,"size_kind":"list"},"WTHPMAX":{"name":"WTHPMAX","sections":["SCHEDULE"],"supported":false,"summary":"WTHPMAX stipulates a well’s maximum flowing Tubing Head Pressure (“THP”), above which the well will be shut-in. The facility is useful if the THP exceeds the wellhead maximum design pressure, which can occur if excessive gas invades the wellbore. In addition to setting the maximum THP, the keyword defines the criteria for re-testing the well to see if the THP has fallen below the maximum value.","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"MAX_THP_DESIGN_LIMIT","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":3,"name":"CONTROL","description":"","units":{},"default":"ORAT","value_type":"STRING"},{"index":4,"name":"CONTROL_LIMIT","description":"","units":{},"default":"","value_type":"DOUBLE"},{"index":5,"name":"THP_OPEN_LIMIT","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"}],"example":"","expected_columns":5,"size_kind":"list"},"WTMULT":{"name":"WTMULT","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, WTMULT, multiplies a defined well’s target or constraint by a constant, for the target and constraints previously stipulated on the WCONPROD, WCONINJE, or WELTARG keywords, but not for the history matching wells using the WCONHIST or WCONINJH keywords. All the aforementioned keywords are in the SCHEDULE section. The constant should be positive value.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well target or constraint (CONTROL) is being adjusted by the multipler (FACTOR). Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"CONTROL","description":"A defined character string that declares the well target or constraint that will be adjusted by multiplying its current value by the FACTOR defined in (3). CONTROL should be set to one of the following character strings: ORAT: the well’s surface oil production rate will be adjusted. WRAT: the well’s surface water production rate will be adjusted. GRAT: the well’s surface gas production rate will be adjusted. LRAT: the well’s surface liquid (oil plus water) production rate will be adjusted. CRAT: the well’s linearly combined maximum surface rate, as per the LINCOM keyword in the SCHEDULE section, will be adjusted. RESV: the well’s in situ reservoir volume rate will be adjusted. BHP: the well’s bottom-hole pressure will be adjusted. THP: the well’s tubing head pressure will be adjusted. In this case a vertical performance table must have been previously assigned to the well via the WCONPROD or WCONINJE keywords. The tables are entered via the VFPINJ or the VFPPROD keywords. All the keywords are in the SCHEDULE section. LIFT: the well’s artificial lift quantity will be adjusted. Again, as for the THP, a vertical performance table must have been assigned to the well. GUID: the well’s guide rate will be adjusted. Only wells under group control and have a guide rate stipulated by the WGRUPCON keyword in the SCHEDULE section, may use this option. CVAL: the well’s calorific rate will be adjusted. NGL: the well’s natural gas liquid rate will be adjusted. Note that the CRAT, CVAL and the NGL options are not available in OPM Flow and should not be used.","units":{},"default":"None","value_type":"STRING","options":["ORAT","WRAT","GRAT","LRAT","CRAT","RESV","BHP","THP","LIFT","GUID","CVAL","NGL"]},{"index":3,"name":"FACTOR","description":"A postive real value that defines the FACTOR that is used to multiply the CONTROL specified in (2). This value may be specified using a User Defined Argument (UDA).","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"None","value_type":"UDA"},{"index":4,"name":"NTIME","description":"A positive integer greater than or equal to one that defines the number of report time steps for which the well target or constraint (CONTROL) is multiplied by the FACTOR. This is only applied when the FACTOR is specified by a User Defined Argument (UDA). The default value of one means that the multiplication is applied only at the current time step for the UDA variable. This option is not supported by OPM Flow.","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1","value_type":"INT"}],"example":"The example shows three oil wells having the flow streams adjusted.\n--\n-- WELL TARGET/LIMIT MULTIPLIER\n--\n-- WELL WELL MULT REPORT\n-- NAME CNTL FACTOR TIMES\nWTMULT\nOP01 ORAT 0.90 /\nOP02 BHP 0.95 /\nOP03 LIFT 1.25 /\n/\nWell OP01 has its current oil rate target multiplied by 0.90, well OP02 has its bottom-hole pressure constraint multiplied by 0.95, and well OP03 has its artificial lift quantity increased by 1.25 times.","expected_columns":4,"size_kind":"list"},"WTRACER":{"name":"WTRACER","sections":["SCHEDULE"],"supported":false,"summary":"The WTRACER keyword defines the tracer concentration of the injection fluid being injected by an injection well. This keyword should only be used if the Tracer option has been invoked by the TRACERS keyword in the RUNSPEC section and the tracers have be declared via the TRACER keyword in the PROPS section.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name of an injection well for which the tracer fraction data is being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"NAME","description":"A three letter character string defining the tracer’s name which has previously been defined via the TRACER keyword in the PROPS section. Note it is best to avoid names beginning with the letters F, S, and T as these names may create naming issues in post-processing software.","units":{},"default":"None","value_type":"STRING"},{"index":3,"name":"TRCON","description":"A real positive value that defines the tracer concentration of the well’s injection stream. This value may be specified using a User Defined Argument (UDA).","units":{"field":"Liquid: 1/stb Gas: 1/Mscf","metric":"Liquid: 1/sm3 Gas: 1/sm3","laboratory":"Liquid: 1/scc Gas: 1/scc"},"default":"None","value_type":"UDA"},{"index":4,"name":"TRCUM","description":"A real positive value that defines the cumulative tracer concentration factor of the well’s injection stream. This value may be specified using a User Defined Argument (UDA). This feature is currently not supported by OPM Flow.","units":{"field":"Liquid: 1/stb Gas: 1/Mscf","metric":"Liquid: 1/sm3 Gas: 1/sm3","laboratory":"Liquid: 1/scc Gas: 1/scc"},"default":"None","value_type":"UDA"},{"index":5,"name":"GRPNAME","description":"A character string of up to eight characters in length that defines the group from which the produced tracer concentration should be used for the well’s injection stream. GRPNAME must have been previously defined via the GCONPROD keyword in the SCHEDULE section, unless the FIELD group has been specified here. Note if GRPNAME is not defined then TRCON will be used for the tracer concentration of the well’s injection stream. This feature is currently not supported by OPM Flow.","units":{},"default":"None","value_type":"STRING"}],"example":"The following example defines the tracer concentrations for two gas injectors and three water injection wells, with water injection well WI02 having no ‘WAT’ tracer injected in the water phase.\n--\n-- DEFINE CONCENTRATION OF TRACERS IN THE INJECTION STREAMS,\n-- INJECTION TRACER CONCENTRATIONS NOT DEFINED USING THE WTRACER\n-- KEYWORD ARE ASSUMED TO BE ZERO.\n--\n-- WELL NAME TRACER TRACER TRACER\n-- NAME TRACER CONC CUM GROUP\nWTRACER\nGI01 'GAS' 1.0 /\nGI02 'GAS' 1.0 /\nWI01 'WAT' 1.0 /\nWI02 'WAT' 0.0 /\nWI03 'WAT' 1.0 /\n/\nNote the terminating “/” for the keyword.","expected_columns":5,"size_kind":"list"},"WVFPDP":{"name":"WVFPDP","sections":["SCHEDULE"],"supported":null,"summary":"The WVFPDP keyword modifies a well’s Bottom-Hole Pressure (“BHP”) estimated by the simulator by interpolation of the Vertical Flow Performance (“VFP”) tables. The production VFP tables are entered via the VFPPROD keyword and the injection tables by the VFPINJ keyword; both keywords are in the SCHEDULE section.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which VFP interpolated BHP adjustment is to be applied. Note that the well name (WELNAME) must have been declared previously using the WELSPECS and WCONPROD (or WCONINJE) keywords in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"DELTAP","description":"A real positive or negative value that is added to the VFP interpolated BHP value (BHPVFP). A positive value of DELTAP increases the BHP and therefore makes a production well less productive; whereas, a negative value is subtracted from the BHP and therefore increases the productivity of a production well. Consequently, the opposite effect occurs for injection wells, that is, a positive value of BHPVFP increases the BHP and therefore increases an injection well’s injectivity; whereas, a negative value is subtracted from the BHP and therefore decreases the injectivity of an injection well.","units":{"field":"psia","metric":"barsa","laboratory":"atma"},"default":"0.0","value_type":"DOUBLE","dimension":"Pressure"},{"index":3,"name":"MULTP","description":"MULTP is a real positive or negative value that scales the tubing pressure loss by the following equation; [BHP sub {Adjusted}~=~THP`+`MULTP left( BHP sub {VFP} `-`THP right)] Thus, a MULTP value greater then 1.0 increases the BHP and therefore makes a production well less productive; whereas, a value less than 1.0 increases the productivity of a production well. Consequently, the opposite effect occurs for injection wells","units":{"field":"dimensionless","metric":"dimensionless","laboratory":"dimensionless"},"default":"1.0","value_type":"DOUBLE"}],"example":"The following example below shows three oils operating under THP control.\n-- ------------------------------------------------------------------------------\n-- 01 JAN 2000 START OF SCHEDULE SECTION\n-- ------------------------------------------------------------------------------\n--\n-- WELL PRODUCTION WELL CONTROLS\n--\n-- WELL OPEN/ CNTL OIL WAT GAS LIQ RES BHP THP VFP VFP\n-- NAME SHUT MODE RATE RATE RATE RATE RATE PRES PRES TABLE ALFQ\nWCONPROD\nOP01 OPEN THP 1* 1* 1* 5000 1* 750.0 500. 9 1* /\nOP02 OPEN THP 1* 1* 1* 5000 1* 750.0 500. 9 1* /\nOP03 OPEN THP 1* 1* 1* 5000 1* 750.0 500. 9 1* /\n/\n--\n-- WELL VFP BHP-THP CORRECTION DATA\n--\n-- WELL BHP BHP\n-- NAME DELTAP MULTP\nWVFPDP\nOP01 20.O 1* /\nOP01 -5.O 1* /\nOP01 0.O 1.10 /\n/\nWell OP01 has a delta pressure correction of 20 psia applied to it’s BHP resulting in a reduction in the well’s productivity for the given 500.0 psia THP operating target. For well OP02, the well’s productivity is increased by subtracting 5.0 psia from the BHP. And finally for well OP03, the MULTP value of 1.10 decreases the well’s productivity by increasing the pressure loss between the THP and BHP by 10%.","expected_columns":3,"size_kind":"list"},"WVFPEXP":{"name":"WVFPEXP","sections":["SCHEDULE"],"supported":false,"summary":"This keyword, WVFPEXP, defines how Vertical Flow Performance (“VFP”) tables are interpolated and can be used to resolve certain issues with wells operating under tubing head pressure control. For example, setting the VFP table to interpolate explicitly, that is using the previous time step results of the gas and water ratios for an oil well, may improve convergence. The default is to use implicit interpolation that uses the current time step values and may result in solution convergence oscillations in solving the linear equations. The WCONPROD keyword is used to allocate the VFPPROD tables to specific production wells. Note that one VFP table can be allocated to one or more wells; however, WVFPEXP is applied to a well’s allocated VFP table, not to all wells that use the same table, unless specifically requested. All the aforementioned keywords are in the SCHEDULE section.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well’s VFP interpolation options are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"IMPEXP","description":"A defined character string of length three that defines the how the well’s VFPPROD tables are to be interpolated and should be set to one of the following character strings: IMP: For this option the simulator interpolates a well’s VFP table implicitly, that is the latest gas fraction (GOR, GLR, etc.), water fraction (WCUT, WOR etc.), and ALQ is used to determine the required pressure. This is the most accurate option but may lead to oscillating behavior during the Newton/Linear iterations. This is the default behavior. EXP: This options forces the simulator to use the previous time step values of a well’s gas fraction, water fraction, and ALQ to interpolate a well’s VFP table in order to determine the required pressure. This is less accurate than the IMP option but minimizes any oscillating behavior during the Newton/Linear iterations. If a well's WCUT and GOR is varying as a function of BHP inside a Newton/Linear iteration (as for example when gas cusping or water coning is occurring), the implicit lookup of the VFP tables might indicate that the well has died, due to the interpolation/extrapolation. If a well dies using implicit WCUT and GOR VFP lookup then the simulator automatically switches to explicit (previous time step) VFP lookup to prevent the well from premature closure, and writes a message to the screen and print file stating the fact. Note the explicit treatment is just for the VFP lookup only. Using the IMPEXP option allows one to select wells that should use either the implicit or explicit lookup option, which may be useful in improving run time performance. Note that if the default value of IMP is used, the simulator will still switch to explicit VFP lookup to prevent a well from premature closure if the condition occurs.","units":{},"default":"IMP","value_type":"STRING"},{"index":3,"name":"STATUS","description":"A defined character string that defines if the well’s operating condition should be checked to see if the VFP table lookup indicates if the well is operating on the flat or horizontal part of stabilized portion of the VLP table (curve), and should be set to one of the following character strings: NO: For this option the check is not performed. YES: In this case the check is performed. Hence, if a well under THP control is found to operating on the horizontal stabilized portion of the VLP curve, then the well is SHUT or STOPPED depending on the AUTO parameter on the WELSPECS keyword. This option is specific to the commercial simulator’s VFPi program that can generate VFPF tables where the unstable part of the VFP curves to the left of the minimum is replaced with a horizontal line at the minimum BHP value. This option is not supported by OPM Flow.","units":{},"default":"NO","value_type":"STRING"},{"index":4,"name":"CONTROL","description":"A defined character string that defines the behavior of rate control wells operating on the unstabilized portion of the VFP table, and should be set to one of the following character strings: NO: This option does not prevent changes to a well’s operating mode when the well is constrained to be operating on the unstabilized portion of the VFP table. This option may cause the well control to oscillate between rate and THP control during the Newton/Linear iterations. YES1: For this option the well is prevented from changing from rate control to THP control provided it can produce at a higher rate under THP control. In this case the well will continue to produce at the required rate even though the calculated THP may be below the well’s minimum THP value. Note however, the well will still be allowed to die if the IPR does not intersect the VFP curve. In the commercial simulator this option will also print a message the first time a well is prevented from changing its control mode, whereas OPM Flow always prints a message every time a well is prevented from changing its control mode. YES2: This option behaves the same as the YES1 option, except a message is printed every time a well is prevented from changing its control mode. The default value of NO allows wells to die when they are constrained by a lower rate that forces them to operate on the unstable section of the VFP curve. This can occur if a well’s rate is being set to match its group target rate or constraint limit. Using either the YES1 or YES2 option will help prevent the \"hunting between control modes\" issue or the well prematurely being shut-in.","units":{},"default":"NO","value_type":"STRING"},{"index":5,"name":"EXTRAP","description":"The EXTRAP parameter is a defined character string in the commercial composition simulator that declares how the extrapolation of a well’s gas fraction, water fraction, and ALQ values is to be conducted. This option is not supported by OPM Flow.","units":{},"default":"WG","value_type":"STRING"}],"example":"The following example defines two oil wells using the WELSPECS and WCONPROD keywords, together with the WVFPEXP keyword that declares how the VFPPROD table lookup should be performed.\n--\n-- WELL SPECIFICATION DATA\n--\n-- WELL GROUP LOCATION BHP PHASE DRAIN INFLOW SHUT CROSS PRESS\n-- NAME NAME I J DEPTH FLUID AREA EQUA. IN FLOW TABLE\nWELSPECS\nOP01 PLATFORM 14 13 1* OIL 1* STD SHUT NO 1* /\nOP02 PLATFORM 28 96 1* OIL 1* STD SHUT NO 1* /\n/\n--\n-- WELL PRODUCTION WELL CONTROLS\n--\n-- WELL OPEN/ CNTL OIL WAT GAS LIQ RES BHP THP VFP VFP\n-- NAME SHUT MODE RATE RATE RATE RATE RATE PRES PRES TABLE ALFQ\nWCONPROD\nOP01 SHUT GRUP 1* 1* 1* 1* 1* 500.0 100.0 1 /\nOP02 SHUT GRUP 1* 1* 1* 1* 1* 500.0 100.0 1 /\n/\n--\n-- WELL OPTIONS FOR PROBLEMATIC THP CONTROLLED WELLS\n--\n-- WELL IMP CLSE RATE VFP\n-- NAME EXP WELL CNTL EXT\nWVFPEXP\n'OP* ' 1* 1* YES1 1* /\n/\nHere both wells are declared as initially shut on the WELSPECS keyword and use VFPPROD table number one as declared on the WCONPROD keyword. The WVFPEXP keyword declares all wells with a name beginning with OP to use implicit lookup and the wells are prevented from changing from rate control to THP control provided they can produce at a higher rate under THP control.","expected_columns":5,"size_kind":"list"},"WWPAVE":{"name":"WWPAVE","sections":["SCHEDULE"],"supported":true,"summary":"The WWPAVE keyword defines the method and parameters for calculating a well’s block average pressures for individual wells that can be written to the SUMMARY and RSM files via the WBP, WBP4, WBP5 and WBP9 vectors in the SUMMARY section. The resulting average pressure can be written out to the summary file in order to compared with field observed data. The keyword is similar to the WPAVE keyword in the SCHEDULE section that has similar functionality, but is applied to all wells in the model.","parameters":[{"index":1,"name":"WELNAME","description":"A character string of up to eight characters in length that defines the well name for which the well average pressure calculation parameters are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur.","units":{},"default":"None","value_type":"STRING"},{"index":2,"name":"WPAVE1","description":"A real dimensionless value that defines the weighting factor between the inner block and the surrounding blocks used in the calculation of the connection factor weighted average pressure. If WPAVE1 is greater than or equal to zero and less than or equal to one, then the average pressure for each well connection is calculated based on this weighting factor. A value of zero indicates only the surrounding blocks should be used in the calculation; and a value of one indicates only the inner blocks should be used. If WPAVE1 is less than zero, then the average pressure for each well connection is weighted based on the pore volumes of the inner and surrounding blocks.","units":{},"default":"0.5","value_type":"DOUBLE"},{"index":3,"name":"WPAVE2","description":"A real dimensionless value greater than or equal to zero and less than or equal to one, that defines the weighting factor between the connection weighted average pressures and the pore volume weighted average pressures. If WPAVE2 is equal to one, then the average pressures are calculate based only using the connection factor calculated pressures. If WPAVE2 is equal to zero, then average pressures are calculate based on only using the pore volumes calculated pressures.","units":{},"default":"1.0","value_type":"DOUBLE"},{"index":4,"name":"WPAVE3","description":"A defined character string that determines how the hydrostatic head calculation is performed in correcting the pressures to the BHP reference depth on the WELSPECS or WPAVEDEP keywords in the SCHEDULE section. WPAVE3 should be set to one of the following character strings: WELL: the hydrostatic head is calculated using the density of the fluid in the wellbore at the well connections. RES: he hydrostatic head is calculated using the density of the fluid in the reservoir with well connections and averaged over the connections. NONE: no hydrostatic correction is applied to the pressures.","units":{},"default":"WELL","value_type":"STRING","options":["WELL","RES","NONE"]},{"index":5,"name":"WPAVE4","description":"A defined character string that determines which connections should be used in the calculations, WPAVE4 should be set to one of the following character strings: OPEN: only open connections and associated grid blocks should be used in the calculations. This option may result in pressure discontinuities if connections are opened and closed during the run. ALL: all currently defined open and closed connections and associated grid blocks are used in the calculations. The pressure discontinuities issue mentioned above can be avoided with this option and defining all the well connections for a well at the beginning of the run. Only the OPEN option is currently supported by the simulator.","units":{},"default":"OPEN","value_type":"STRING","options":["OPEN","ALL"]}],"example":"The following example defines the default well block average pressure calculation parameters for three oil wells: OP01, OP02 and OP03.\n--\n-- DEFINE WELL BLOCK AVERAGE PRESSURE CALCULATION PARAMETERS\n--\n-- WELL INNER PORV WELL OPEN\n-- NAME OUTER CONN RES ALL\nWWPAVE\nOP01 0.5 1.0 WELL ALL /\nOP02 0.5 1.0 WELL ALL /\nOP03 0.5 1.0 1* 1* /\nAnd the next example shows the parameters used in the Norne model.\n--\n-- DEFINE WELL BLOCK AVERAGE PRESSURE CALCULATION PARAMETERS\n--\n-- WELL INNER PORV WELL OPEN\n-- NAME OUTER CONN RES ALL\nWPAVE\nOP01 1* 0.0 WELL ALL /\nOP02 1* 0.0 WELL ALL /\nOP03 1* 0.0 WELL ALL /\nHere only pore volume weighting is used instead of connection weighting.","expected_columns":5,"size_kind":"list"},"ZIPP2OFF":{"name":"ZIPP2OFF","sections":["SCHEDULE"],"supported":false,"summary":"The ZIPP2OFF keyword deactivates the commercial simulator’s alternative automatic time step selection algorithm that assumes no prior knowledge of the problem, as opposed to the standard time step algorithm that is controlled via the TUNING keyword in the SCHEDULE section, combined with posterior knowledge gained from previous time steps.","parameters":[],"example":"","size_kind":"none","size_count":0},"ZIPPY2":{"name":"ZIPPY2","sections":["SCHEDULE"],"supported":false,"summary":"The ZIPPY2 keyword activates the commercial simulator’s alternative automatic time step selection algorithm that assumes no prior knowledge of the problem, as opposed to the standard time step algorithm that is controlled via the TUNNING keyword in the SCHEDULE section, combined with posterior knowledge gained from previous time steps.","parameters":[{"index":1,"name":"SETTINGS","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","size_kind":"fixed","size_count":1,"variadic_record":true},"FAQR":{"name":"FAQR","sections":["SUMMARY"],"supported":null,"summary":"Aquifer Influx Rate (Water Aquifers)","parameters":[],"example":"","size_kind":"none"},"AAQR":{"name":"AAQR","sections":["SUMMARY"],"supported":null,"summary":"Aquifer Influx Rate (Water Aquifers)","parameters":[],"example":"","size_kind":"array","optional_body":true},"ALQR":{"name":"ALQR","sections":["SUMMARY"],"supported":null,"summary":"Aquifer Influx Rate (Water Aquifers)","parameters":[],"example":"","size_kind":"array","optional_body":true},"ANQR":{"name":"ANQR","sections":["SUMMARY"],"supported":null,"summary":"Aquifer Influx Rate (Water Aquifers)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FAQT":{"name":"FAQT","sections":["SUMMARY"],"supported":null,"summary":"Aquifer Influx Total (Water Aquifers)","parameters":[],"example":"","size_kind":"none"},"AAQT":{"name":"AAQT","sections":["SUMMARY"],"supported":null,"summary":"Aquifer Influx Total (Water Aquifers)","parameters":[],"example":"","size_kind":"array","optional_body":true},"ALQT":{"name":"ALQT","sections":["SUMMARY"],"supported":null,"summary":"Aquifer Influx Total (Water Aquifers)","parameters":[],"example":"","size_kind":"array","optional_body":true},"ANQT":{"name":"ANQT","sections":["SUMMARY"],"supported":null,"summary":"Aquifer Influx Total (Water Aquifers)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FAQRG":{"name":"FAQRG","sections":["SUMMARY"],"supported":null,"summary":"Aquifer Influx Rate (Gas Aquifers)","parameters":[],"example":"","size_kind":"none"},"AAQRG":{"name":"AAQRG","sections":["SUMMARY"],"supported":null,"summary":"Aquifer Influx Rate (Gas Aquifers)","parameters":[],"example":"","size_kind":"array","optional_body":true},"ALQRG":{"name":"ALQRG","sections":["SUMMARY"],"supported":null,"summary":"Aquifer Influx Rate (Gas Aquifers)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FAQTG":{"name":"FAQTG","sections":["SUMMARY"],"supported":null,"summary":"Aquifer Influx Total (Gas Aquifers)","parameters":[],"example":"","size_kind":"none"},"AAQTG":{"name":"AAQTG","sections":["SUMMARY"],"supported":null,"summary":"Aquifer Influx Total (Gas Aquifers)","parameters":[],"example":"","size_kind":"array","optional_body":true},"ALQTG":{"name":"ALQTG","sections":["SUMMARY"],"supported":null,"summary":"Aquifer Influx Total (Gas Aquifers)","parameters":[],"example":"","size_kind":"array","optional_body":true},"AAQP":{"name":"AAQP","sections":["SUMMARY"],"supported":null,"summary":"Aquifer Pressure. Water pore volume weighted average","parameters":[],"example":"","size_kind":"array","optional_body":true},"ANQP":{"name":"ANQP","sections":["SUMMARY"],"supported":null,"summary":"Aquifer Pressure. Water pore volume weighted average","parameters":[],"example":"","size_kind":"array","optional_body":true},"AAQPD":{"name":"AAQPD","sections":["SUMMARY"],"supported":null,"summary":"Aquifer Carter-Tracy Dimensionless Pressure","parameters":[],"example":"","size_kind":"array","optional_body":true},"AAQTD":{"name":"AAQTD","sections":["SUMMARY"],"supported":null,"summary":"Aquifer Carter-Tracy Dimensionless Time","parameters":[],"example":"","size_kind":"array","optional_body":true},"WALQ":{"name":"WALQ","sections":["SUMMARY"],"supported":null,"summary":"Artificial Lift Quantity","parameters":[],"example":"","size_kind":"array","optional_body":true},"WMVFP":{"name":"WMVFP","sections":["SUMMARY"],"supported":null,"summary":"Artificial Lift and VFP Table Number. Well VFP table number.","parameters":[],"example":"","size_kind":"array","optional_body":true},"GEFF":{"name":"GEFF","sections":["SUMMARY"],"supported":null,"summary":"Efficiency Factor","parameters":[],"example":"","size_kind":"array","optional_body":true},"WEFF":{"name":"WEFF","sections":["SUMMARY"],"supported":null,"summary":"Efficiency Factor","parameters":[],"example":"","size_kind":"array","optional_body":true},"WEFFG":{"name":"WEFFG","sections":["SUMMARY"],"supported":null,"summary":"Efficiency Factor Product. Efficiency factor of the well times the product of all the groups above the well.","parameters":[],"example":"","size_kind":"array","optional_body":true},"FEPR":{"name":"FEPR","sections":["SUMMARY"],"supported":null,"summary":"Energy Production Rate","parameters":[],"example":"","size_kind":"none"},"GEPR":{"name":"GEPR","sections":["SUMMARY"],"supported":null,"summary":"Energy Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WEPR":{"name":"WEPR","sections":["SUMMARY"],"supported":null,"summary":"Energy Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FEPT":{"name":"FEPT","sections":["SUMMARY"],"supported":null,"summary":"Energy Production Total","parameters":[],"example":"","size_kind":"none"},"GEPT":{"name":"GEPT","sections":["SUMMARY"],"supported":null,"summary":"Energy Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"WEPT":{"name":"WEPT","sections":["SUMMARY"],"supported":null,"summary":"Energy Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGCR":{"name":"FGCR","sections":["SUMMARY"],"supported":null,"summary":"Gas Consumption Rate","parameters":[],"example":"","size_kind":"none"},"GGCR":{"name":"GGCR","sections":["SUMMARY"],"supported":null,"summary":"Gas Consumption Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGCT":{"name":"FGCT","sections":["SUMMARY"],"supported":null,"summary":"Gas Consumption Total","parameters":[],"example":"","size_kind":"none"},"GGCT":{"name":"GGCT","sections":["SUMMARY"],"supported":null,"summary":"Gas Consumption Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CGFR":{"name":"CGFR","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow Rate. Positive for production and negative for injection.","parameters":[],"example":"","size_kind":"array","optional_body":true},"CGFRL":{"name":"CGFRL","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow Rate. Positive for production and negative for injection.","parameters":[],"example":"","size_kind":"array","optional_body":true},"CGFRF":{"name":"CGFRF","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow Rate (Free)","parameters":[],"example":"","size_kind":"array","optional_body":true},"CGFRS":{"name":"CGFRS","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow Rate (Solution)","parameters":[],"example":"","size_kind":"array","optional_body":true},"CGFRU":{"name":"CGFRU","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow Rate (Upstream). Sum of connection gas flow rates upstream of, and including, this connection.","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGIMR":{"name":"FGIMR","sections":["SUMMARY"],"supported":null,"summary":"Gas Import Rate","parameters":[],"example":"","size_kind":"none"},"GGIMR":{"name":"GGIMR","sections":["SUMMARY"],"supported":null,"summary":"Gas Import Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGIMT":{"name":"FGIMT","sections":["SUMMARY"],"supported":null,"summary":"Gas Import Total","parameters":[],"example":"","size_kind":"none"},"GGIMT":{"name":"GGIMT","sections":["SUMMARY"],"supported":null,"summary":"Gas Import Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"GGIGR":{"name":"GGIGR","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Guide Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WGIGR":{"name":"WGIGR","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Guide Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGIR":{"name":"FGIR","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Rate","parameters":[],"example":"","size_kind":"none"},"GGIR":{"name":"GGIR","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WGIR":{"name":"WGIR","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"CGIR":{"name":"CGIR","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"CGIRL":{"name":"CGIRL","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGIRH":{"name":"FGIRH","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Rate History","parameters":[],"example":"","size_kind":"none"},"GGIRH":{"name":"GGIRH","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Rate History","parameters":[],"example":"","size_kind":"array","optional_body":true},"WGIRH":{"name":"WGIRH","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Rate History","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGIRT":{"name":"FGIRT","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Rate Target/Limit","parameters":[],"example":"","size_kind":"none"},"GGIRT":{"name":"GGIRT","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Rate Target/Limit","parameters":[],"example":"","size_kind":"array","optional_body":true},"WGIRT":{"name":"WGIRT","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Rate Target/Limit","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGIT":{"name":"FGIT","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Total","parameters":[],"example":"","size_kind":"none"},"GGIT":{"name":"GGIT","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"WGIT":{"name":"WGIT","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CGIT":{"name":"CGIT","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CGITL":{"name":"CGITL","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGITH":{"name":"FGITH","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Total History","parameters":[],"example":"","size_kind":"none"},"GGITH":{"name":"GGITH","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Total History","parameters":[],"example":"","size_kind":"array","optional_body":true},"WGITH":{"name":"WGITH","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Total History","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGLIR":{"name":"FGLIR","sections":["SUMMARY"],"supported":null,"summary":"Gas Lift Injection Rate. Gas lift gas with group and field total rates based on well efficiency.","parameters":[],"example":"","size_kind":"none"},"GGLIR":{"name":"GGLIR","sections":["SUMMARY"],"supported":null,"summary":"Gas Lift Injection Rate. Gas lift gas with group and field total rates based on well efficiency.","parameters":[],"example":"","size_kind":"array","optional_body":true},"WGLIR":{"name":"WGLIR","sections":["SUMMARY"],"supported":null,"summary":"Gas Lift Injection Rate. Gas lift gas with group and field total rates based on well efficiency.","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGLIT":{"name":"FGLIT","sections":["SUMMARY"],"supported":null,"summary":"Gas Lift Injection Total. Gas lift gas with group and field total rates based on well efficiency.","parameters":[],"example":"","size_kind":"none"},"GGLIT":{"name":"GGLIT","sections":["SUMMARY"],"supported":null,"summary":"Gas Lift Injection Total. Gas lift gas with group and field total rates based on well efficiency.","parameters":[],"example":"","size_kind":"array","optional_body":true},"WGLIT":{"name":"WGLIT","sections":["SUMMARY"],"supported":null,"summary":"Gas Lift Injection Total. Gas lift gas with group and field total rates based on well efficiency.","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGPI":{"name":"FGPI","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Injection Rate. Also WGIP for WGPI.","parameters":[],"example":"","size_kind":"none"},"GGPI":{"name":"GGPI","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Injection Rate. Also WGIP for WGPI.","parameters":[],"example":"","size_kind":"array","optional_body":true},"WGPI":{"name":"WGPI","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Injection Rate. Also WGIP for WGPI.","parameters":[],"example":"","size_kind":"array","optional_body":true},"CGPI":{"name":"CGPI","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Injection Rate. Also WGIP for WGPI.","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGPI2":{"name":"FGPI2","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Injection Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"none"},"GGPI2":{"name":"GGPI2","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Injection Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"array","optional_body":true},"WGPI2":{"name":"WGPI2","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Injection Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGPP":{"name":"FGPP","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Production Rate","parameters":[],"example":"","size_kind":"none"},"GGPP":{"name":"GGPP","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WGPP":{"name":"WGPP","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"CGPP":{"name":"CGPP","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGPP2":{"name":"FGPP2","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Production Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"none"},"GGPP2":{"name":"GGPP2","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Production Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"array","optional_body":true},"WGPP2":{"name":"WGPP2","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Production Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGPPF":{"name":"FGPPF","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Production Rate (Free)","parameters":[],"example":"","size_kind":"none"},"GGPPF":{"name":"GGPPF","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Production Rate (Free)","parameters":[],"example":"","size_kind":"array","optional_body":true},"WGPPF":{"name":"WGPPF","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Production Rate (Free)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGPPF2":{"name":"FGPPF2","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Production Rate (Free). Including shut and stopped wells.","parameters":[],"example":"","size_kind":"none"},"GGPPF2":{"name":"GGPPF2","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Production Rate (Free). Including shut and stopped wells.","parameters":[],"example":"","size_kind":"array","optional_body":true},"WGPPF2":{"name":"WGPPF2","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Production Rate (Free). Including shut and stopped wells.","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGPPS":{"name":"FGPPS","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Production Rate (Soln)","parameters":[],"example":"","size_kind":"none"},"GGPPS":{"name":"GGPPS","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Production Rate (Soln)","parameters":[],"example":"","size_kind":"array","optional_body":true},"WGPPS":{"name":"WGPPS","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Production Rate (Soln)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGPPS2":{"name":"FGPPS2","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Production Rate (Soln). Including shut and stopped wells.","parameters":[],"example":"","size_kind":"none"},"GGPPS2":{"name":"GGPPS2","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Production Rate (Soln). Including shut and stopped wells.","parameters":[],"example":"","size_kind":"array","optional_body":true},"WGPPS2":{"name":"WGPPS2","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential Production Rate (Soln). Including shut and stopped wells.","parameters":[],"example":"","size_kind":"array","optional_body":true},"GGPGR":{"name":"GGPGR","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Guide Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WGPGR":{"name":"WGPGR","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Guide Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGPR":{"name":"FGPR","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Rate. Produced reservoir gas only, gas lift gas excluded.","parameters":[],"example":"","size_kind":"none"},"GGPR":{"name":"GGPR","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Rate. Produced reservoir gas only, gas lift gas excluded.","parameters":[],"example":"","size_kind":"array","optional_body":true},"WGPR":{"name":"WGPR","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Rate. Produced reservoir gas only, gas lift gas excluded.","parameters":[],"example":"","size_kind":"array","optional_body":true},"CGPR":{"name":"CGPR","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Rate. Produced reservoir gas only, gas lift gas excluded.","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGPRF":{"name":"FGPRF","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Rate (Free)","parameters":[],"example":"","size_kind":"none"},"GGPRF":{"name":"GGPRF","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Rate (Free)","parameters":[],"example":"","size_kind":"array","optional_body":true},"WGPRF":{"name":"WGPRF","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Rate (Free)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGPRS":{"name":"FGPRS","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Rate (Solution)","parameters":[],"example":"","size_kind":"none"},"GGPRS":{"name":"GGPRS","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Rate (Solution)","parameters":[],"example":"","size_kind":"array","optional_body":true},"WGPRS":{"name":"WGPRS","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Rate (Solution)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGPRH":{"name":"FGPRH","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Rate History","parameters":[],"example":"","size_kind":"none"},"GGPRH":{"name":"GGPRH","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Rate History","parameters":[],"example":"","size_kind":"array","optional_body":true},"WGPRH":{"name":"WGPRH","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Rate History","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGPRT":{"name":"FGPRT","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Rate Target/Limit","parameters":[],"example":"","size_kind":"none"},"GGPRT":{"name":"GGPRT","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Rate Target/Limit","parameters":[],"example":"","size_kind":"array","optional_body":true},"WGPRT":{"name":"WGPRT","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Rate Target/Limit","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGPT":{"name":"FGPT","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Total","parameters":[],"example":"","size_kind":"none"},"GGPT":{"name":"GGPT","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"WGPT":{"name":"WGPT","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CGPT":{"name":"CGPT","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CGPTL":{"name":"CGPTL","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGPTF":{"name":"FGPTF","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Total (Free)","parameters":[],"example":"","size_kind":"none"},"GGPTF":{"name":"GGPTF","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Total (Free)","parameters":[],"example":"","size_kind":"array","optional_body":true},"WGPTF":{"name":"WGPTF","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Total (Free)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGPTS":{"name":"FGPTS","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Total (Solution)","parameters":[],"example":"","size_kind":"none"},"GGPTS":{"name":"GGPTS","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Total (Solution)","parameters":[],"example":"","size_kind":"array","optional_body":true},"WGPTS":{"name":"WGPTS","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Total (Solution)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGPTH":{"name":"FGPTH","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Total History","parameters":[],"example":"","size_kind":"none"},"GGPTH":{"name":"GGPTH","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Total History","parameters":[],"example":"","size_kind":"array","optional_body":true},"WGPTH":{"name":"WGPTH","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Total History","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGSR":{"name":"FGSR","sections":["SUMMARY"],"supported":null,"summary":"Gas Sales Rate","parameters":[],"example":"","size_kind":"none"},"GGSR":{"name":"GGSR","sections":["SUMMARY"],"supported":null,"summary":"Gas Sales Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FSGR":{"name":"FSGR","sections":["SUMMARY"],"supported":null,"summary":"Gas Sales Rate. Same as GSR.","parameters":[],"example":"","size_kind":"none"},"GSGR":{"name":"GSGR","sections":["SUMMARY"],"supported":null,"summary":"Gas Sales Rate. Same as GSR.","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGST":{"name":"FGST","sections":["SUMMARY"],"supported":null,"summary":"Gas Sales Total","parameters":[],"example":"","size_kind":"none"},"GGST":{"name":"GGST","sections":["SUMMARY"],"supported":null,"summary":"Gas Sales Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"FSGT":{"name":"FSGT","sections":["SUMMARY"],"supported":null,"summary":"Gas Sales Total. Same as GST.","parameters":[],"example":"","size_kind":"none"},"GSGT":{"name":"GSGT","sections":["SUMMARY"],"supported":null,"summary":"Gas Sales Total. Same as GST.","parameters":[],"example":"","size_kind":"array","optional_body":true},"WGVIR":{"name":"WGVIR","sections":["SUMMARY"],"supported":null,"summary":"Gas Voidage Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WGVPR":{"name":"WGVPR","sections":["SUMMARY"],"supported":null,"summary":"Gas Voidage Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"CLFR":{"name":"CLFR","sections":["SUMMARY"],"supported":null,"summary":"Liquid Flow Rate. Positive for production and negative for injection.","parameters":[],"example":"","size_kind":"array","optional_body":true},"CLFRL":{"name":"CLFRL","sections":["SUMMARY"],"supported":null,"summary":"Liquid Flow Rate. Positive for production and negative for injection.","parameters":[],"example":"","size_kind":"array","optional_body":true},"FLPR":{"name":"FLPR","sections":["SUMMARY"],"supported":null,"summary":"Liquid Production Rate","parameters":[],"example":"","size_kind":"none"},"GLPR":{"name":"GLPR","sections":["SUMMARY"],"supported":null,"summary":"Liquid Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WLPR":{"name":"WLPR","sections":["SUMMARY"],"supported":null,"summary":"Liquid Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"CLPR":{"name":"CLPR","sections":["SUMMARY"],"supported":null,"summary":"Liquid Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FLPRH":{"name":"FLPRH","sections":["SUMMARY"],"supported":null,"summary":"Liquid Production Rate History","parameters":[],"example":"","size_kind":"none"},"GLPRH":{"name":"GLPRH","sections":["SUMMARY"],"supported":null,"summary":"Liquid Production Rate History","parameters":[],"example":"","size_kind":"array","optional_body":true},"WLPRH":{"name":"WLPRH","sections":["SUMMARY"],"supported":null,"summary":"Liquid Production Rate History","parameters":[],"example":"","size_kind":"array","optional_body":true},"FLPRT":{"name":"FLPRT","sections":["SUMMARY"],"supported":null,"summary":"Liquid Production Rate Target/Limit","parameters":[],"example":"","size_kind":"none"},"GLPRT":{"name":"GLPRT","sections":["SUMMARY"],"supported":null,"summary":"Liquid Production Rate Target/Limit","parameters":[],"example":"","size_kind":"array","optional_body":true},"WLPRT":{"name":"WLPRT","sections":["SUMMARY"],"supported":null,"summary":"Liquid Production Rate Target/Limit","parameters":[],"example":"","size_kind":"array","optional_body":true},"FLPT":{"name":"FLPT","sections":["SUMMARY"],"supported":null,"summary":"Liquid Production Total","parameters":[],"example":"","size_kind":"none"},"GLPT":{"name":"GLPT","sections":["SUMMARY"],"supported":null,"summary":"Liquid Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"WLPT":{"name":"WLPT","sections":["SUMMARY"],"supported":null,"summary":"Liquid Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CLPT":{"name":"CLPT","sections":["SUMMARY"],"supported":null,"summary":"Liquid Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CLPTL":{"name":"CLPTL","sections":["SUMMARY"],"supported":null,"summary":"Liquid Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"FLPTH":{"name":"FLPTH","sections":["SUMMARY"],"supported":null,"summary":"Liquid Production Total History","parameters":[],"example":"","size_kind":"none"},"GLPTH":{"name":"GLPTH","sections":["SUMMARY"],"supported":null,"summary":"Liquid Production Total History","parameters":[],"example":"","size_kind":"array","optional_body":true},"WLPTH":{"name":"WLPTH","sections":["SUMMARY"],"supported":null,"summary":"Liquid Production Total History","parameters":[],"example":"","size_kind":"array","optional_body":true},"COFR":{"name":"COFR","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow Rate. Positive for production and negative for injection.","parameters":[],"example":"","size_kind":"array","optional_body":true},"COFRL":{"name":"COFRL","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow Rate. Positive for production and negative for injection.","parameters":[],"example":"","size_kind":"array","optional_body":true},"COFRF":{"name":"COFRF","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow Rate (Free)","parameters":[],"example":"","size_kind":"array","optional_body":true},"COFRS":{"name":"COFRS","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow Rate (Solution)","parameters":[],"example":"","size_kind":"array","optional_body":true},"COFRU":{"name":"COFRU","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow Rate (Upstream). Sum of connection oil flow rates upstream of, and including this connection.","parameters":[],"example":"","size_kind":"array","optional_body":true},"GOIGR":{"name":"GOIGR","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Guide Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WOIGR":{"name":"WOIGR","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Guide Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FOIR":{"name":"FOIR","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Rate","parameters":[],"example":"","size_kind":"none"},"GOIR":{"name":"GOIR","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WOIR":{"name":"WOIR","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"COIR":{"name":"COIR","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"COIRL":{"name":"COIRL","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FOIRH":{"name":"FOIRH","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Rate History","parameters":[],"example":"","size_kind":"none"},"GOIRH":{"name":"GOIRH","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Rate History","parameters":[],"example":"","size_kind":"array","optional_body":true},"WOIRH":{"name":"WOIRH","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Rate History","parameters":[],"example":"","size_kind":"array","optional_body":true},"FOIRT":{"name":"FOIRT","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Rate Target/Limit","parameters":[],"example":"","size_kind":"none"},"GOIRT":{"name":"GOIRT","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Rate Target/Limit","parameters":[],"example":"","size_kind":"array","optional_body":true},"WOIRT":{"name":"WOIRT","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Rate Target/Limit","parameters":[],"example":"","size_kind":"array","optional_body":true},"FOIT":{"name":"FOIT","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Total","parameters":[],"example":"","size_kind":"none"},"GOIT":{"name":"GOIT","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"WOIT":{"name":"WOIT","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"COIT":{"name":"COIT","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"COITL":{"name":"COITL","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"FOITH":{"name":"FOITH","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Total History","parameters":[],"example":"","size_kind":"none"},"GOITH":{"name":"GOITH","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Total History","parameters":[],"example":"","size_kind":"array","optional_body":true},"WOITH":{"name":"WOITH","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Total History","parameters":[],"example":"","size_kind":"array","optional_body":true},"FOPI":{"name":"FOPI","sections":["SUMMARY"],"supported":null,"summary":"Oil Potential Injection Rate","parameters":[],"example":"","size_kind":"none"},"GOPI":{"name":"GOPI","sections":["SUMMARY"],"supported":null,"summary":"Oil Potential Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WOPI":{"name":"WOPI","sections":["SUMMARY"],"supported":null,"summary":"Oil Potential Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FOPI2":{"name":"FOPI2","sections":["SUMMARY"],"supported":null,"summary":"Oil Potential Injection Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"none"},"GOPI2":{"name":"GOPI2","sections":["SUMMARY"],"supported":null,"summary":"Oil Potential Injection Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"array","optional_body":true},"WOPI2":{"name":"WOPI2","sections":["SUMMARY"],"supported":null,"summary":"Oil Potential Injection Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"array","optional_body":true},"FOPP":{"name":"FOPP","sections":["SUMMARY"],"supported":null,"summary":"Oil Potential Production Rate","parameters":[],"example":"","size_kind":"none"},"GOPP":{"name":"GOPP","sections":["SUMMARY"],"supported":null,"summary":"Oil Potential Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WOPP":{"name":"WOPP","sections":["SUMMARY"],"supported":null,"summary":"Oil Potential Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"COPP":{"name":"COPP","sections":["SUMMARY"],"supported":null,"summary":"Oil Potential Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FOPP2":{"name":"FOPP2","sections":["SUMMARY"],"supported":null,"summary":"Oil Potential Production Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"none"},"GOPP2":{"name":"GOPP2","sections":["SUMMARY"],"supported":null,"summary":"Oil Potential Production Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"array","optional_body":true},"WOPP2":{"name":"WOPP2","sections":["SUMMARY"],"supported":null,"summary":"Oil Potential Production Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"array","optional_body":true},"GOPGR":{"name":"GOPGR","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Guide Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WOPGR":{"name":"WOPGR","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Guide Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FOPR":{"name":"FOPR","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Rate","parameters":[],"example":"","size_kind":"none"},"GOPR":{"name":"GOPR","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WOPR":{"name":"WOPR","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"COPR":{"name":"COPR","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FOPRF":{"name":"FOPRF","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Rate (Free)","parameters":[],"example":"","size_kind":"none"},"GOPRF":{"name":"GOPRF","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Rate (Free)","parameters":[],"example":"","size_kind":"array","optional_body":true},"WOPRF":{"name":"WOPRF","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Rate (Free)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FOPRS":{"name":"FOPRS","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Rate (Solution)","parameters":[],"example":"","size_kind":"none"},"GOPRS":{"name":"GOPRS","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Rate (Solution)","parameters":[],"example":"","size_kind":"array","optional_body":true},"WOPRS":{"name":"WOPRS","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Rate (Solution)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FOPRH":{"name":"FOPRH","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Rate History","parameters":[],"example":"","size_kind":"none"},"GOPRH":{"name":"GOPRH","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Rate History","parameters":[],"example":"","size_kind":"array","optional_body":true},"WOPRH":{"name":"WOPRH","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Rate History","parameters":[],"example":"","size_kind":"array","optional_body":true},"FOPRT":{"name":"FOPRT","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Rate Target/Limit","parameters":[],"example":"","size_kind":"none"},"GOPRT":{"name":"GOPRT","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Rate Target/Limit","parameters":[],"example":"","size_kind":"array","optional_body":true},"WOPRT":{"name":"WOPRT","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Rate Target/Limit","parameters":[],"example":"","size_kind":"array","optional_body":true},"FOPT":{"name":"FOPT","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total","parameters":[],"example":"","size_kind":"none"},"GOPT":{"name":"GOPT","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"WOPT":{"name":"WOPT","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"FOPTF":{"name":"FOPTF","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total (Free)","parameters":[],"example":"","size_kind":"none"},"GOPTF":{"name":"GOPTF","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total (Free)","parameters":[],"example":"","size_kind":"array","optional_body":true},"WOPTF":{"name":"WOPTF","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total (Free)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FOPTS":{"name":"FOPTS","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total (Solution)","parameters":[],"example":"","size_kind":"none"},"GOPTS":{"name":"GOPTS","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total (Solution)","parameters":[],"example":"","size_kind":"array","optional_body":true},"WOPTS":{"name":"WOPTS","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total (Solution)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FOPTH":{"name":"FOPTH","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total History","parameters":[],"example":"","size_kind":"none"},"GOPTH":{"name":"GOPTH","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total History","parameters":[],"example":"","size_kind":"array","optional_body":true},"WOPTH":{"name":"WOPTH","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total History","parameters":[],"example":"","size_kind":"array","optional_body":true},"CVFR":{"name":"CVFR","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Flow Rate. Positive for production and negative for injection.","parameters":[],"example":"","size_kind":"array","optional_body":true},"CVFRL":{"name":"CVFRL","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Flow Rate. Positive for production and negative for injection.","parameters":[],"example":"","size_kind":"array","optional_body":true},"CVFRF":{"name":"CVFRF","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Flow Rate (Free)","parameters":[],"example":"","size_kind":"array","optional_body":true},"GVIGR":{"name":"GVIGR","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Injection Guide Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WVIGR":{"name":"WVIGR","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Injection Guide Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FVIR":{"name":"FVIR","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Injection Rate","parameters":[],"example":"","size_kind":"none"},"GVIR":{"name":"GVIR","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WVIR":{"name":"WVIR","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"CVIR":{"name":"CVIR","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"CVIRL":{"name":"CVIRL","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FVIRT":{"name":"FVIRT","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Injection Rate Target/Limit","parameters":[],"example":"","size_kind":"none"},"GVIRT":{"name":"GVIRT","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Injection Rate Target/Limit","parameters":[],"example":"","size_kind":"array","optional_body":true},"WVIRT":{"name":"WVIRT","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Injection Rate Target/Limit","parameters":[],"example":"","size_kind":"array","optional_body":true},"FVIT":{"name":"FVIT","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Injection Total","parameters":[],"example":"","size_kind":"none"},"GVIT":{"name":"GVIT","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"WVIT":{"name":"WVIT","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CVIT":{"name":"CVIT","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CVITL":{"name":"CVITL","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"FVPI":{"name":"FVPI","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Potential Injection Rate","parameters":[],"example":"","size_kind":"none"},"GVPI":{"name":"GVPI","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Potential Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WVPI":{"name":"WVPI","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Potential Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FVPI2":{"name":"FVPI2","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Potential Injection Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"none"},"GVPI2":{"name":"GVPI2","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Potential Injection Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"array","optional_body":true},"WVPI2":{"name":"WVPI2","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Potential Injection Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"array","optional_body":true},"FVPP":{"name":"FVPP","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Potential Production Rate","parameters":[],"example":"","size_kind":"none"},"GVPP":{"name":"GVPP","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Potential Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WVPP":{"name":"WVPP","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Potential Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"CVPP":{"name":"CVPP","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Potential Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FVPP2":{"name":"FVPP2","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Potential Production Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"none"},"GVPP2":{"name":"GVPP2","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Potential Production Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"array","optional_body":true},"WVPP2":{"name":"WVPP2","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Potential Production Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"array","optional_body":true},"GVPGR":{"name":"GVPGR","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Production Guide Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WVPGR":{"name":"WVPGR","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Production Guide Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FVPR":{"name":"FVPR","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Production Rate","parameters":[],"example":"","size_kind":"none"},"GVPR":{"name":"GVPR","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WVPR":{"name":"WVPR","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"CVPR":{"name":"CVPR","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FVPRT":{"name":"FVPRT","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Production Rate Target/Limit","parameters":[],"example":"","size_kind":"none"},"GVPRT":{"name":"GVPRT","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Production Rate Target/Limit","parameters":[],"example":"","size_kind":"array","optional_body":true},"WVPRT":{"name":"WVPRT","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Production Rate Target/Limit","parameters":[],"example":"","size_kind":"array","optional_body":true},"FVPT":{"name":"FVPT","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Production Total","parameters":[],"example":"","size_kind":"none"},"GVPT":{"name":"GVPT","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"WVPT":{"name":"WVPT","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CVPT":{"name":"CVPT","sections":["SUMMARY"],"supported":null,"summary":"Res. Vol. Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CWFR":{"name":"CWFR","sections":["SUMMARY"],"supported":null,"summary":"Water Flow Rate. Positive for production and negative for injection.","parameters":[],"example":"","size_kind":"array","optional_body":true},"CWFRL":{"name":"CWFRL","sections":["SUMMARY"],"supported":null,"summary":"Water Flow Rate. Positive for production and negative for injection.","parameters":[],"example":"","size_kind":"array","optional_body":true},"CWFRU":{"name":"CWFRU","sections":["SUMMARY"],"supported":null,"summary":"Water Flow Rate (Upstream). Sum of connection water flow rates upstream of, and including, this connection.","parameters":[],"example":"","size_kind":"array","optional_body":true},"GWIGR":{"name":"GWIGR","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Guide Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WWIGR":{"name":"WWIGR","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Guide Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FWIR":{"name":"FWIR","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Rate","parameters":[],"example":"","size_kind":"none"},"GWIR":{"name":"GWIR","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WWIR":{"name":"WWIR","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"CWIR":{"name":"CWIR","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"CWIRL":{"name":"CWIRL","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FWIRH":{"name":"FWIRH","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Rate History","parameters":[],"example":"","size_kind":"none"},"GWIRH":{"name":"GWIRH","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Rate History","parameters":[],"example":"","size_kind":"array","optional_body":true},"WWIRH":{"name":"WWIRH","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Rate History","parameters":[],"example":"","size_kind":"array","optional_body":true},"FWIRT":{"name":"FWIRT","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Rate Target/Limit","parameters":[],"example":"","size_kind":"none"},"GWIRT":{"name":"GWIRT","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Rate Target/Limit","parameters":[],"example":"","size_kind":"array","optional_body":true},"WWIRT":{"name":"WWIRT","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Rate Target/Limit","parameters":[],"example":"","size_kind":"array","optional_body":true},"FWIT":{"name":"FWIT","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Total","parameters":[],"example":"","size_kind":"none"},"GWIT":{"name":"GWIT","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"WWIT":{"name":"WWIT","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CWIT":{"name":"CWIT","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CWITL":{"name":"CWITL","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"FWITH":{"name":"FWITH","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Total History","parameters":[],"example":"","size_kind":"none"},"GWITH":{"name":"GWITH","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Total History","parameters":[],"example":"","size_kind":"array","optional_body":true},"WWITH":{"name":"WWITH","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Total History","parameters":[],"example":"","size_kind":"array","optional_body":true},"FWPI":{"name":"FWPI","sections":["SUMMARY"],"supported":null,"summary":"Water Potential Injection Rate. Also WWIP for WWPI.","parameters":[],"example":"","size_kind":"none"},"GWPI":{"name":"GWPI","sections":["SUMMARY"],"supported":null,"summary":"Water Potential Injection Rate. Also WWIP for WWPI.","parameters":[],"example":"","size_kind":"array","optional_body":true},"WWPI":{"name":"WWPI","sections":["SUMMARY"],"supported":null,"summary":"Water Potential Injection Rate. Also WWIP for WWPI.","parameters":[],"example":"","size_kind":"array","optional_body":true},"FWPI2":{"name":"FWPI2","sections":["SUMMARY"],"supported":null,"summary":"Water Potential Injection Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"none"},"GWPI2":{"name":"GWPI2","sections":["SUMMARY"],"supported":null,"summary":"Water Potential Injection Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"array","optional_body":true},"WWPI2":{"name":"WWPI2","sections":["SUMMARY"],"supported":null,"summary":"Water Potential Injection Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"array","optional_body":true},"FWPP":{"name":"FWPP","sections":["SUMMARY"],"supported":null,"summary":"Water Potential Production Rate","parameters":[],"example":"","size_kind":"none"},"GWPP":{"name":"GWPP","sections":["SUMMARY"],"supported":null,"summary":"Water Potential Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WWPP":{"name":"WWPP","sections":["SUMMARY"],"supported":null,"summary":"Water Potential Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"CWPP":{"name":"CWPP","sections":["SUMMARY"],"supported":null,"summary":"Water Potential Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FWPP2":{"name":"FWPP2","sections":["SUMMARY"],"supported":null,"summary":"Water Potential Production Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"none"},"GWPP2":{"name":"GWPP2","sections":["SUMMARY"],"supported":null,"summary":"Water Potential Production Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"array","optional_body":true},"WWPP2":{"name":"WWPP2","sections":["SUMMARY"],"supported":null,"summary":"Water Potential Production Rate. Including shut and stopped wells.","parameters":[],"example":"","size_kind":"array","optional_body":true},"FWPIR":{"name":"FWPIR","sections":["SUMMARY"],"supported":null,"summary":"Water Produce/Injected Ratio. Reported as a percent.","parameters":[],"example":"","size_kind":"none"},"GWPIR":{"name":"GWPIR","sections":["SUMMARY"],"supported":null,"summary":"Water Produce/Injected Ratio. Reported as a percent.","parameters":[],"example":"","size_kind":"array","optional_body":true},"WWPIR":{"name":"WWPIR","sections":["SUMMARY"],"supported":null,"summary":"Water Produce/Injected Ratio. Reported as a percent.","parameters":[],"example":"","size_kind":"array","optional_body":true},"GWPGR":{"name":"GWPGR","sections":["SUMMARY"],"supported":null,"summary":"Water Production Guide Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WWPGR":{"name":"WWPGR","sections":["SUMMARY"],"supported":null,"summary":"Water Production Guide Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FWPR":{"name":"FWPR","sections":["SUMMARY"],"supported":null,"summary":"Water Production Rate","parameters":[],"example":"","size_kind":"none"},"GWPR":{"name":"GWPR","sections":["SUMMARY"],"supported":null,"summary":"Water Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WWPR":{"name":"WWPR","sections":["SUMMARY"],"supported":null,"summary":"Water Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"CWPR":{"name":"CWPR","sections":["SUMMARY"],"supported":null,"summary":"Water Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FWPRH":{"name":"FWPRH","sections":["SUMMARY"],"supported":null,"summary":"Water Production Rate History","parameters":[],"example":"","size_kind":"none"},"GWPRH":{"name":"GWPRH","sections":["SUMMARY"],"supported":null,"summary":"Water Production Rate History","parameters":[],"example":"","size_kind":"array","optional_body":true},"WWPRH":{"name":"WWPRH","sections":["SUMMARY"],"supported":null,"summary":"Water Production Rate History","parameters":[],"example":"","size_kind":"array","optional_body":true},"FWPRT":{"name":"FWPRT","sections":["SUMMARY"],"supported":null,"summary":"Water Production Rate Target/Limit","parameters":[],"example":"","size_kind":"none"},"GWPRT":{"name":"GWPRT","sections":["SUMMARY"],"supported":null,"summary":"Water Production Rate Target/Limit","parameters":[],"example":"","size_kind":"array","optional_body":true},"WWPRT":{"name":"WWPRT","sections":["SUMMARY"],"supported":null,"summary":"Water Production Rate Target/Limit","parameters":[],"example":"","size_kind":"array","optional_body":true},"FWPT":{"name":"FWPT","sections":["SUMMARY"],"supported":null,"summary":"Water Production Total","parameters":[],"example":"","size_kind":"none"},"GWPT":{"name":"GWPT","sections":["SUMMARY"],"supported":null,"summary":"Water Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"WWPT":{"name":"WWPT","sections":["SUMMARY"],"supported":null,"summary":"Water Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CWPT":{"name":"CWPT","sections":["SUMMARY"],"supported":null,"summary":"Water Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CWPTL":{"name":"CWPTL","sections":["SUMMARY"],"supported":null,"summary":"Water Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"FWPTH":{"name":"FWPTH","sections":["SUMMARY"],"supported":null,"summary":"Water Production Total History","parameters":[],"example":"","size_kind":"none"},"GWPTH":{"name":"GWPTH","sections":["SUMMARY"],"supported":null,"summary":"Water Production Total History","parameters":[],"example":"","size_kind":"array","optional_body":true},"WWPTH":{"name":"WWPTH","sections":["SUMMARY"],"supported":null,"summary":"Water Production Total History","parameters":[],"example":"","size_kind":"array","optional_body":true},"WWVIR":{"name":"WWVIR","sections":["SUMMARY"],"supported":null,"summary":"Water Voidage Injection Guide Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WWVIT":{"name":"WWVIT","sections":["SUMMARY"],"supported":null,"summary":"Water Voidage Injection Guide Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"FAMIR":{"name":"FAMIR","sections":["SUMMARY"],"supported":null,"summary":"Water Mass Injection Rate","parameters":[],"example":"","size_kind":"none"},"GAMIR":{"name":"GAMIR","sections":["SUMMARY"],"supported":null,"summary":"Water Mass Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WAMIR":{"name":"WAMIR","sections":["SUMMARY"],"supported":null,"summary":"Water Mass Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"CAMIR":{"name":"CAMIR","sections":["SUMMARY"],"supported":null,"summary":"Water Mass Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"CAMIRL":{"name":"CAMIRL","sections":["SUMMARY"],"supported":null,"summary":"Water Mass Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FAMIT":{"name":"FAMIT","sections":["SUMMARY"],"supported":null,"summary":"Water Mass Injection Total","parameters":[],"example":"","size_kind":"none"},"GAMIT":{"name":"GAMIT","sections":["SUMMARY"],"supported":null,"summary":"Water Mass Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"WAMIT":{"name":"WAMIT","sections":["SUMMARY"],"supported":null,"summary":"Water Mass Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CAMIT":{"name":"CAMIT","sections":["SUMMARY"],"supported":null,"summary":"Water Mass Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CAMITL":{"name":"CAMITL","sections":["SUMMARY"],"supported":null,"summary":"Water Mass Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"FAMPR":{"name":"FAMPR","sections":["SUMMARY"],"supported":null,"summary":"Water Mass Production Rate","parameters":[],"example":"","size_kind":"none"},"GAMPR":{"name":"GAMPR","sections":["SUMMARY"],"supported":null,"summary":"Water Mass Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WAMPR":{"name":"WAMPR","sections":["SUMMARY"],"supported":null,"summary":"Water Mass Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"CAMPR":{"name":"CAMPR","sections":["SUMMARY"],"supported":null,"summary":"Water Mass Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"CAMPRL":{"name":"CAMPRL","sections":["SUMMARY"],"supported":null,"summary":"Water Mass Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FAMPT":{"name":"FAMPT","sections":["SUMMARY"],"supported":null,"summary":"Water Mass Production Total","parameters":[],"example":"","size_kind":"none"},"GAMPT":{"name":"GAMPT","sections":["SUMMARY"],"supported":null,"summary":"Water Mass Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"WAMPT":{"name":"WAMPT","sections":["SUMMARY"],"supported":null,"summary":"Water Mass Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CAMPT":{"name":"CAMPT","sections":["SUMMARY"],"supported":null,"summary":"Water Mass Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CAMPTL":{"name":"CAMPTL","sections":["SUMMARY"],"supported":null,"summary":"Water Mass Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"FMWIA":{"name":"FMWIA","sections":["SUMMARY"],"supported":null,"summary":"Number of abandoned injection wells","parameters":[],"example":"","size_kind":"none"},"GMWIA":{"name":"GMWIA","sections":["SUMMARY"],"supported":null,"summary":"Number of abandoned injection wells","parameters":[],"example":"","size_kind":"array","optional_body":true},"FMWPA":{"name":"FMWPA","sections":["SUMMARY"],"supported":null,"summary":"Number of abandoned production wells","parameters":[],"example":"","size_kind":"none"},"GMWPA":{"name":"GMWPA","sections":["SUMMARY"],"supported":null,"summary":"Number of abandoned production wells","parameters":[],"example":"","size_kind":"array","optional_body":true},"FMWDT":{"name":"FMWDT","sections":["SUMMARY"],"supported":null,"summary":"Number of drilling events in total","parameters":[],"example":"","size_kind":"none"},"GMWDT":{"name":"GMWDT","sections":["SUMMARY"],"supported":null,"summary":"Number of drilling events in total","parameters":[],"example":"","size_kind":"array","optional_body":true},"FMWDR":{"name":"FMWDR","sections":["SUMMARY"],"supported":null,"summary":"Number of drilling events this timestep","parameters":[],"example":"","size_kind":"none"},"GMWDR":{"name":"GMWDR","sections":["SUMMARY"],"supported":null,"summary":"Number of drilling events this timestep","parameters":[],"example":"","size_kind":"array","optional_body":true},"FMWIN":{"name":"FMWIN","sections":["SUMMARY"],"supported":null,"summary":"Number of injection wells currently flowing","parameters":[],"example":"","size_kind":"none"},"GMWIN":{"name":"GMWIN","sections":["SUMMARY"],"supported":null,"summary":"Number of injection wells currently flowing","parameters":[],"example":"","size_kind":"array","optional_body":true},"FMWIG":{"name":"FMWIG","sections":["SUMMARY"],"supported":null,"summary":"Number of injectors on group control","parameters":[],"example":"","size_kind":"none"},"GMWIG":{"name":"GMWIG","sections":["SUMMARY"],"supported":null,"summary":"Number of injectors on group control","parameters":[],"example":"","size_kind":"array","optional_body":true},"FMWIV":{"name":"FMWIV","sections":["SUMMARY"],"supported":null,"summary":"Number of injectors on own reservoir volume rate limit control","parameters":[],"example":"","size_kind":"none"},"GMWIV":{"name":"GMWIV","sections":["SUMMARY"],"supported":null,"summary":"Number of injectors on own reservoir volume rate limit control","parameters":[],"example":"","size_kind":"array","optional_body":true},"FMWIS":{"name":"FMWIS","sections":["SUMMARY"],"supported":null,"summary":"Number of injectors on own surface rate limit control","parameters":[],"example":"","size_kind":"none"},"GMWIS":{"name":"GMWIS","sections":["SUMMARY"],"supported":null,"summary":"Number of injectors on own surface rate limit control","parameters":[],"example":"","size_kind":"array","optional_body":true},"FMWIP":{"name":"FMWIP","sections":["SUMMARY"],"supported":null,"summary":"Number of injectors on pressure control","parameters":[],"example":"","size_kind":"none"},"GMWIP":{"name":"GMWIP","sections":["SUMMARY"],"supported":null,"summary":"Number of injectors on pressure control","parameters":[],"example":"","size_kind":"array","optional_body":true},"FMWPO":{"name":"FMWPO","sections":["SUMMARY"],"supported":null,"summary":"Number of producers controlled by own oil rate limit","parameters":[],"example":"","size_kind":"none"},"GMWPO":{"name":"GMWPO","sections":["SUMMARY"],"supported":null,"summary":"Number of producers controlled by own oil rate limit","parameters":[],"example":"","size_kind":"array","optional_body":true},"FMWPG":{"name":"FMWPG","sections":["SUMMARY"],"supported":null,"summary":"Number of producers on group control","parameters":[],"example":"","size_kind":"none"},"GMWPG":{"name":"GMWPG","sections":["SUMMARY"],"supported":null,"summary":"Number of producers on group control","parameters":[],"example":"","size_kind":"array","optional_body":true},"FMWPV":{"name":"FMWPV","sections":["SUMMARY"],"supported":null,"summary":"Number of producers on own reservoir volume rate limit control","parameters":[],"example":"","size_kind":"none"},"GMWPV":{"name":"GMWPV","sections":["SUMMARY"],"supported":null,"summary":"Number of producers on own reservoir volume rate limit control","parameters":[],"example":"","size_kind":"array","optional_body":true},"FMWPS":{"name":"FMWPS","sections":["SUMMARY"],"supported":null,"summary":"Number of producers on own surface rate limit control","parameters":[],"example":"","size_kind":"none"},"GMWPS":{"name":"GMWPS","sections":["SUMMARY"],"supported":null,"summary":"Number of producers on own surface rate limit control","parameters":[],"example":"","size_kind":"array","optional_body":true},"FMWPP":{"name":"FMWPP","sections":["SUMMARY"],"supported":null,"summary":"Number of producers on pressure control","parameters":[],"example":"","size_kind":"none"},"GMWPP":{"name":"GMWPP","sections":["SUMMARY"],"supported":null,"summary":"Number of producers on pressure control","parameters":[],"example":"","size_kind":"array","optional_body":true},"FMWPL":{"name":"FMWPL","sections":["SUMMARY"],"supported":null,"summary":"Number of producers using artificial lift (with ALQ > 0.0)","parameters":[],"example":"","size_kind":"none"},"GMWPL":{"name":"GMWPL","sections":["SUMMARY"],"supported":null,"summary":"Number of producers using artificial lift (with ALQ > 0.0)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FMWPR":{"name":"FMWPR","sections":["SUMMARY"],"supported":null,"summary":"Number of production wells currently flowing","parameters":[],"example":"","size_kind":"none"},"GMWPR":{"name":"GMWPR","sections":["SUMMARY"],"supported":null,"summary":"Number of production wells currently flowing","parameters":[],"example":"","size_kind":"array","optional_body":true},"FMWIU":{"name":"FMWIU","sections":["SUMMARY"],"supported":null,"summary":"Number of unused injection wells","parameters":[],"example":"","size_kind":"none"},"GMWIU":{"name":"GMWIU","sections":["SUMMARY"],"supported":null,"summary":"Number of unused injection wells","parameters":[],"example":"","size_kind":"array","optional_body":true},"FMWPU":{"name":"FMWPU","sections":["SUMMARY"],"supported":null,"summary":"Number of unused production wells","parameters":[],"example":"","size_kind":"none"},"GMWPU":{"name":"GMWPU","sections":["SUMMARY"],"supported":null,"summary":"Number of unused production wells","parameters":[],"example":"","size_kind":"array","optional_body":true},"FMWWT":{"name":"FMWWT","sections":["SUMMARY"],"supported":null,"summary":"Number of workover events in total","parameters":[],"example":"","size_kind":"none"},"GMWWT":{"name":"GMWWT","sections":["SUMMARY"],"supported":null,"summary":"Number of workover events in total","parameters":[],"example":"","size_kind":"array","optional_body":true},"FMWWO":{"name":"FMWWO","sections":["SUMMARY"],"supported":null,"summary":"Number of workover events this time step.","parameters":[],"example":"","size_kind":"none"},"GMWWO":{"name":"GMWWO","sections":["SUMMARY"],"supported":null,"summary":"Number of workover events this time step.","parameters":[],"example":"","size_kind":"array","optional_body":true},"WMCON":{"name":"WMCON","sections":["SUMMARY"],"supported":null,"summary":"The number of connections capable of flowing in the well","parameters":[],"example":"","size_kind":"array","optional_body":true},"FMWIT":{"name":"FMWIT","sections":["SUMMARY"],"supported":null,"summary":"Total number of injection wells","parameters":[],"example":"","size_kind":"none"},"GMWIT":{"name":"GMWIT","sections":["SUMMARY"],"supported":null,"summary":"Total number of injection wells","parameters":[],"example":"","size_kind":"array","optional_body":true},"FMWPT":{"name":"FMWPT","sections":["SUMMARY"],"supported":null,"summary":"Total number of production wells","parameters":[],"example":"","size_kind":"none"},"GMWPT":{"name":"GMWPT","sections":["SUMMARY"],"supported":null,"summary":"Total number of production wells","parameters":[],"example":"","size_kind":"array","optional_body":true},"CCDBF":{"name":"CCDBF","sections":["SUMMARY"],"supported":null,"summary":"Blocking Factor (GPP)","parameters":[],"example":"","size_kind":"array","optional_body":true},"WBHP":{"name":"WBHP","sections":["SUMMARY"],"supported":null,"summary":"Bottom-Hole Pressure","parameters":[],"example":"","size_kind":"array","optional_body":true},"WBP5":{"name":"WBP5","sections":["SUMMARY"],"supported":null,"summary":"Bottom-Hole Pressure (Five Point","parameters":[],"example":"","size_kind":"array","optional_body":true},"WBP4":{"name":"WBP4","sections":["SUMMARY"],"supported":null,"summary":"Bottom-Hole Pressure (Four Point)","parameters":[],"example":"","size_kind":"array","optional_body":true},"WBP9":{"name":"WBP9","sections":["SUMMARY"],"supported":null,"summary":"Bottom-Hole Pressure (Nine Point)","parameters":[],"example":"","size_kind":"array","optional_body":true},"WBP":{"name":"WBP","sections":["SUMMARY"],"supported":null,"summary":"Bottom-Hole Pressure (One Point)","parameters":[],"example":"","size_kind":"array","optional_body":true},"WBHPH":{"name":"WBHPH","sections":["SUMMARY"],"supported":null,"summary":"Bottom-Hole Pressure History","parameters":[],"example":"","size_kind":"array","optional_body":true},"WBHPT":{"name":"WBHPT","sections":["SUMMARY"],"supported":null,"summary":"Bottom-Hole Pressure Target/Limit","parameters":[],"example":"","size_kind":"array","optional_body":true},"CPRL":{"name":"CPRL","sections":["SUMMARY"],"supported":null,"summary":"Connection Pressure. Completion pressure is an average pressure for the completion.","parameters":[],"example":"","size_kind":"array","optional_body":true},"CDFAC":{"name":"CDFAC","sections":["SUMMARY"],"supported":null,"summary":"Connection D-Factor","parameters":[],"example":"","size_kind":"array","optional_body":true},"CTFAC":{"name":"CTFAC","sections":["SUMMARY"],"supported":null,"summary":"Connection Transmissibility Factor","parameters":[],"example":"","size_kind":"array","optional_body":true},"WPIG":{"name":"WPIG","sections":["SUMMARY"],"supported":null,"summary":"Productivity (Gas Phase)","parameters":[],"example":"","size_kind":"array","optional_body":true},"WPIL":{"name":"WPIL","sections":["SUMMARY"],"supported":null,"summary":"Productivity (Liquid Phase)","parameters":[],"example":"","size_kind":"array","optional_body":true},"WPIO":{"name":"WPIO","sections":["SUMMARY"],"supported":null,"summary":"Productivity (Oil Phase)","parameters":[],"example":"","size_kind":"array","optional_body":true},"WPI5":{"name":"WPI5","sections":["SUMMARY"],"supported":null,"summary":"Productivity (Preferred Phase – Five Point)","parameters":[],"example":"","size_kind":"array","optional_body":true},"WPI4":{"name":"WPI4","sections":["SUMMARY"],"supported":null,"summary":"Productivity (Preferred Phase – Four Point)","parameters":[],"example":"","size_kind":"array","optional_body":true},"WPI9":{"name":"WPI9","sections":["SUMMARY"],"supported":null,"summary":"Productivity (Preferred Phase – Nine Point)","parameters":[],"example":"","size_kind":"array","optional_body":true},"WPI1":{"name":"WPI1","sections":["SUMMARY"],"supported":null,"summary":"Productivity (Preferred Phase – One Point)","parameters":[],"example":"","size_kind":"array","optional_body":true},"WPI":{"name":"WPI","sections":["SUMMARY"],"supported":null,"summary":"Productivity (Preferred Phase)","parameters":[],"example":"","size_kind":"array","optional_body":true},"CPI":{"name":"CPI","sections":["SUMMARY"],"supported":null,"summary":"Productivity (Preferred Phase)","parameters":[],"example":"","size_kind":"array","optional_body":true},"WPIW":{"name":"WPIW","sections":["SUMMARY"],"supported":null,"summary":"Productivity (Water Phase)","parameters":[],"example":"","size_kind":"array","optional_body":true},"WTHP":{"name":"WTHP","sections":["SUMMARY"],"supported":null,"summary":"Tubing Head Pressure","parameters":[],"example":"","size_kind":"array","optional_body":true},"WTHPH":{"name":"WTHPH","sections":["SUMMARY"],"supported":null,"summary":"Tubing Head Pressure History","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGLR":{"name":"FGLR","sections":["SUMMARY"],"supported":null,"summary":"Gas-Liquid Ratio","parameters":[],"example":"","size_kind":"none"},"GGLR":{"name":"GGLR","sections":["SUMMARY"],"supported":null,"summary":"Gas-Liquid Ratio","parameters":[],"example":"","size_kind":"array","optional_body":true},"WGLR":{"name":"WGLR","sections":["SUMMARY"],"supported":null,"summary":"Gas-Liquid Ratio","parameters":[],"example":"","size_kind":"array","optional_body":true},"CGLR":{"name":"CGLR","sections":["SUMMARY"],"supported":null,"summary":"Gas-Liquid Ratio","parameters":[],"example":"","size_kind":"array","optional_body":true},"CGLRL":{"name":"CGLRL","sections":["SUMMARY"],"supported":null,"summary":"Gas-Liquid Ratio","parameters":[],"example":"","size_kind":"array","optional_body":true},"WBGLR":{"name":"WBGLR","sections":["SUMMARY"],"supported":null,"summary":"Gas-Liquid Ratio (Bottom-Hole)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGLRH":{"name":"FGLRH","sections":["SUMMARY"],"supported":null,"summary":"Gas-Liquid Ratio History","parameters":[],"example":"","size_kind":"none"},"GGLRH":{"name":"GGLRH","sections":["SUMMARY"],"supported":null,"summary":"Gas-Liquid Ratio History","parameters":[],"example":"","size_kind":"array","optional_body":true},"WGLRH":{"name":"WGLRH","sections":["SUMMARY"],"supported":null,"summary":"Gas-Liquid Ratio History","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGOR":{"name":"FGOR","sections":["SUMMARY"],"supported":null,"summary":"Gas-Oil Ratio","parameters":[],"example":"","size_kind":"none"},"GGOR":{"name":"GGOR","sections":["SUMMARY"],"supported":null,"summary":"Gas-Oil Ratio","parameters":[],"example":"","size_kind":"array","optional_body":true},"WGOR":{"name":"WGOR","sections":["SUMMARY"],"supported":null,"summary":"Gas-Oil Ratio","parameters":[],"example":"","size_kind":"array","optional_body":true},"CGOR":{"name":"CGOR","sections":["SUMMARY"],"supported":null,"summary":"Gas-Oil Ratio","parameters":[],"example":"","size_kind":"array","optional_body":true},"CGORL":{"name":"CGORL","sections":["SUMMARY"],"supported":null,"summary":"Gas-Oil Ratio","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGORH":{"name":"FGORH","sections":["SUMMARY"],"supported":null,"summary":"Gas-Oil Ratio History","parameters":[],"example":"","size_kind":"none"},"GGORH":{"name":"GGORH","sections":["SUMMARY"],"supported":null,"summary":"Gas-Oil Ratio History","parameters":[],"example":"","size_kind":"array","optional_body":true},"WGORH":{"name":"WGORH","sections":["SUMMARY"],"supported":null,"summary":"Gas-Oil Ratio History","parameters":[],"example":"","size_kind":"array","optional_body":true},"FOGR":{"name":"FOGR","sections":["SUMMARY"],"supported":null,"summary":"Oil-Gas Ratio","parameters":[],"example":"","size_kind":"none"},"GOGR":{"name":"GOGR","sections":["SUMMARY"],"supported":null,"summary":"Oil-Gas Ratio","parameters":[],"example":"","size_kind":"array","optional_body":true},"WOGR":{"name":"WOGR","sections":["SUMMARY"],"supported":null,"summary":"Oil-Gas Ratio","parameters":[],"example":"","size_kind":"array","optional_body":true},"COGR":{"name":"COGR","sections":["SUMMARY"],"supported":null,"summary":"Oil-Gas Ratio","parameters":[],"example":"","size_kind":"array","optional_body":true},"COGRL":{"name":"COGRL","sections":["SUMMARY"],"supported":null,"summary":"Oil-Gas Ratio","parameters":[],"example":"","size_kind":"array","optional_body":true},"FOGRH":{"name":"FOGRH","sections":["SUMMARY"],"supported":null,"summary":"Oil-Gas Ratio History","parameters":[],"example":"","size_kind":"none"},"GOGRH":{"name":"GOGRH","sections":["SUMMARY"],"supported":null,"summary":"Oil-Gas Ratio History","parameters":[],"example":"","size_kind":"array","optional_body":true},"WOGRH":{"name":"WOGRH","sections":["SUMMARY"],"supported":null,"summary":"Oil-Gas Ratio History","parameters":[],"example":"","size_kind":"array","optional_body":true},"FWGR":{"name":"FWGR","sections":["SUMMARY"],"supported":null,"summary":"Water -Gas Ratio","parameters":[],"example":"","size_kind":"none"},"GWGR":{"name":"GWGR","sections":["SUMMARY"],"supported":null,"summary":"Water -Gas Ratio","parameters":[],"example":"","size_kind":"array","optional_body":true},"WWGR":{"name":"WWGR","sections":["SUMMARY"],"supported":null,"summary":"Water -Gas Ratio","parameters":[],"example":"","size_kind":"array","optional_body":true},"CWGR":{"name":"CWGR","sections":["SUMMARY"],"supported":null,"summary":"Water -Gas Ratio","parameters":[],"example":"","size_kind":"array","optional_body":true},"CWGRL":{"name":"CWGRL","sections":["SUMMARY"],"supported":null,"summary":"Water -Gas Ratio","parameters":[],"example":"","size_kind":"array","optional_body":true},"FWCT":{"name":"FWCT","sections":["SUMMARY"],"supported":null,"summary":"Water Cut","parameters":[],"example":"","size_kind":"none"},"GWCT":{"name":"GWCT","sections":["SUMMARY"],"supported":null,"summary":"Water Cut","parameters":[],"example":"","size_kind":"array","optional_body":true},"WWCT":{"name":"WWCT","sections":["SUMMARY"],"supported":null,"summary":"Water Cut","parameters":[],"example":"","size_kind":"array","optional_body":true},"CWCT":{"name":"CWCT","sections":["SUMMARY"],"supported":null,"summary":"Water Cut","parameters":[],"example":"","size_kind":"array","optional_body":true},"CWCTL":{"name":"CWCTL","sections":["SUMMARY"],"supported":null,"summary":"Water Cut","parameters":[],"example":"","size_kind":"array","optional_body":true},"FWCTH":{"name":"FWCTH","sections":["SUMMARY"],"supported":null,"summary":"Water Cut History","parameters":[],"example":"","size_kind":"none"},"GWCTH":{"name":"GWCTH","sections":["SUMMARY"],"supported":null,"summary":"Water Cut History","parameters":[],"example":"","size_kind":"array","optional_body":true},"WWCTH":{"name":"WWCTH","sections":["SUMMARY"],"supported":null,"summary":"Water Cut History","parameters":[],"example":"","size_kind":"array","optional_body":true},"FWGRH":{"name":"FWGRH","sections":["SUMMARY"],"supported":null,"summary":"Water-Gas Ratio History","parameters":[],"example":"","size_kind":"none"},"GWGRH":{"name":"GWGRH","sections":["SUMMARY"],"supported":null,"summary":"Water-Gas Ratio History","parameters":[],"example":"","size_kind":"array","optional_body":true},"WWGRH":{"name":"WWGRH","sections":["SUMMARY"],"supported":null,"summary":"Water-Gas Ratio History","parameters":[],"example":"","size_kind":"array","optional_body":true},"FMCTP":{"name":"FMCTP","sections":["SUMMARY"],"supported":null,"summary":"Production Group.","parameters":[],"example":"","size_kind":"none"},"GMCTP":{"name":"GMCTP","sections":["SUMMARY"],"supported":null,"summary":"Production Group.","parameters":[],"example":"","size_kind":"array","optional_body":true},"FMCTW":{"name":"FMCTW","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Group.","parameters":[],"example":"","size_kind":"none"},"GMCTW":{"name":"GMCTW","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Group.","parameters":[],"example":"","size_kind":"array","optional_body":true},"FMCTG":{"name":"FMCTG","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Group.","parameters":[],"example":"","size_kind":"none"},"GMCTG":{"name":"GMCTG","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Group.","parameters":[],"example":"","size_kind":"array","optional_body":true},"WSTAT":{"name":"WSTAT","sections":["SUMMARY"],"supported":null,"summary":"Well Status indicator.","parameters":[],"example":"","size_kind":"array","optional_body":true},"WMCTL":{"name":"WMCTL","sections":["SUMMARY"],"supported":null,"summary":"Well Mode of Control indicator.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BFLOGI":{"name":"BFLOGI","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow (Inter-Block in I+ Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BFLOGI-":{"name":"BFLOGI-","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow (Inter-Block in I- Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BFLOGJ":{"name":"BFLOGJ","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow (Inter-Block in J+ Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BFLOGJ-":{"name":"BFLOGJ-","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow (Inter-Block in J- Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BFLOGK":{"name":"BFLOGK","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow (Inter-Block in K+ Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BFLOGK-":{"name":"BFLOGK-","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow (Inter-Block in K- Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"RGFR":{"name":"RGFR","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow Rate Inter-Region. OPM Flow implementation.","parameters":[],"example":"","size_kind":"array","optional_body":true},"RGFR+":{"name":"RGFR+","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow Rate Inter-Region (Positive Contribution)","parameters":[],"example":"","size_kind":"array","optional_body":true},"RGFR-":{"name":"RGFR-","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow Rate Inter-Region (Negative Contribution)","parameters":[],"example":"","size_kind":"array","optional_body":true},"RGFT":{"name":"RGFT","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow Total Inter-Region (Liquid and Gas Phases)","parameters":[],"example":"","size_kind":"array","optional_body":true},"RGFT+":{"name":"RGFT+","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow Total Inter-Region (+VE Liquid and Gas Phases). OPM Flow Implementation","parameters":[],"example":"","size_kind":"array","optional_body":true},"RGFT-":{"name":"RGFT-","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow Total Inter-Region (-VE Liquid and Gas Phases)","parameters":[],"example":"","size_kind":"array","optional_body":true},"RGFTG":{"name":"RGFTG","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow Total Inter-Region (Gas Phase)","parameters":[],"example":"","size_kind":"array","optional_body":true},"RGFTL":{"name":"RGFTL","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow Total Inter-Region (Liquid Phase)","parameters":[],"example":"","size_kind":"array","optional_body":true},"RGIR":{"name":"RGIR","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"RGIT":{"name":"RGIT","sections":["SUMMARY"],"supported":null,"summary":"Gas Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"FPPG":{"name":"FPPG","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential","parameters":[],"example":"","size_kind":"none"},"RPPG":{"name":"RPPG","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential","parameters":[],"example":"","size_kind":"array","optional_body":true},"BPPG":{"name":"BPPG","sections":["SUMMARY"],"supported":null,"summary":"Gas Potential","parameters":[],"example":"","size_kind":"array","optional_body":true},"RGPR":{"name":"RGPR","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"RGPRF":{"name":"RGPRF","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Rate (Free)","parameters":[],"example":"","size_kind":"array","optional_body":true},"RGPRS":{"name":"RGPRS","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Rate (Solution)","parameters":[],"example":"","size_kind":"array","optional_body":true},"RGPT":{"name":"RGPT","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Total. Liquid and gas phases","parameters":[],"example":"","size_kind":"array","optional_body":true},"RGPTF":{"name":"RGPTF","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Total (Free)","parameters":[],"example":"","size_kind":"array","optional_body":true},"RGP":{"name":"RGP","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Total (Net From Region). Minus injected gas.","parameters":[],"example":"","size_kind":"array","optional_body":true},"RGPTS":{"name":"RGPTS","sections":["SUMMARY"],"supported":null,"summary":"Gas Production Total (Solution)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BVELGI":{"name":"BVELGI","sections":["SUMMARY"],"supported":null,"summary":"Gas Velocity (Inter-Block in I+ Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BVELGI-":{"name":"BVELGI-","sections":["SUMMARY"],"supported":null,"summary":"Gas Velocity (Inter-Block in I- Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BVELGJ":{"name":"BVELGJ","sections":["SUMMARY"],"supported":null,"summary":"Gas Velocity (Inter-Block in J+ Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BVELGJ-":{"name":"BVELGJ-","sections":["SUMMARY"],"supported":null,"summary":"Gas Velocity (Inter-Block in J- Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BVELGK":{"name":"BVELGK","sections":["SUMMARY"],"supported":null,"summary":"Gas Velocity (Inter-Block in K+ Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BVELGK-":{"name":"BVELGK-","sections":["SUMMARY"],"supported":null,"summary":"Gas Velocity (Inter-Block in K- Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BFLOOI":{"name":"BFLOOI","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow (Inter-Block in I+ Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BFLOOI-":{"name":"BFLOOI-","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow (Inter-Block in I- Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BFLOOJ":{"name":"BFLOOJ","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow (Inter-Block in J+ Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BFLOOJ-":{"name":"BFLOOJ-","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow (Inter-Block in J- Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BFLOOK":{"name":"BFLOOK","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow (Inter-Block in K+ Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BFLOOK-":{"name":"BFLOOK-","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow (Inter-Block in K- Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"ROFR":{"name":"ROFR","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow Rate Inter-Region. OPM Flow implementation.","parameters":[],"example":"","size_kind":"array","optional_body":true},"ROFR+":{"name":"ROFR+","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow Rate Inter-Region (Positive Contribution)","parameters":[],"example":"","size_kind":"array","optional_body":true},"ROFR-":{"name":"ROFR-","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow Rate Inter-Region (Negative Contribution)","parameters":[],"example":"","size_kind":"array","optional_body":true},"ROFT":{"name":"ROFT","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow Total Inter-Region (Liquid and Gas Phases)","parameters":[],"example":"","size_kind":"array","optional_body":true},"ROFT+":{"name":"ROFT+","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow Total Inter-Region (+VE Liquid and Gas Phases). OPM Flow implementation.","parameters":[],"example":"","size_kind":"array","optional_body":true},"ROFT-":{"name":"ROFT-","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow Total Inter-Region (-VE Liquid and Gas Phases)","parameters":[],"example":"","size_kind":"array","optional_body":true},"ROFTG":{"name":"ROFTG","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow Total Inter-Region (Gas Phase)","parameters":[],"example":"","size_kind":"array","optional_body":true},"ROFTL":{"name":"ROFTL","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow Total Inter-Region (Liquid Phase)","parameters":[],"example":"","size_kind":"array","optional_body":true},"ROIR":{"name":"ROIR","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"ROIT":{"name":"ROIT","sections":["SUMMARY"],"supported":null,"summary":"Oil Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"FPPO":{"name":"FPPO","sections":["SUMMARY"],"supported":null,"summary":"Oil Potential","parameters":[],"example":"","size_kind":"none"},"RPPO":{"name":"RPPO","sections":["SUMMARY"],"supported":null,"summary":"Oil Potential","parameters":[],"example":"","size_kind":"array","optional_body":true},"BPPO":{"name":"BPPO","sections":["SUMMARY"],"supported":null,"summary":"Oil Potential","parameters":[],"example":"","size_kind":"array","optional_body":true},"ROPR":{"name":"ROPR","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"ROPT":{"name":"ROPT","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"ROP":{"name":"ROP","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total (Net From Region)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BVELOI":{"name":"BVELOI","sections":["SUMMARY"],"supported":null,"summary":"Oil Velocity (Inter-Block in I+ Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BVELOI-":{"name":"BVELOI-","sections":["SUMMARY"],"supported":null,"summary":"Oil Velocity (Inter-Block in I- Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BVELOJ":{"name":"BVELOJ","sections":["SUMMARY"],"supported":null,"summary":"Oil Velocity (Inter-Block in J+ Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BVELOJ-":{"name":"BVELOJ-","sections":["SUMMARY"],"supported":null,"summary":"Oil Velocity (Inter-Block in J- Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BVELOK":{"name":"BVELOK","sections":["SUMMARY"],"supported":null,"summary":"Oil Velocity (Inter-Block in K+ Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BVELOK-":{"name":"BVELOK-","sections":["SUMMARY"],"supported":null,"summary":"Oil Velocity (Inter-Block in K- Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BFLOWI":{"name":"BFLOWI","sections":["SUMMARY"],"supported":null,"summary":"Water Flow (Inter-Block in I+ Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BFLOWI-":{"name":"BFLOWI-","sections":["SUMMARY"],"supported":null,"summary":"Water Flow (Inter-Block in I- Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BFLOWJ":{"name":"BFLOWJ","sections":["SUMMARY"],"supported":null,"summary":"Water Flow (Inter-Block in J+ Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BFLOWJ-":{"name":"BFLOWJ-","sections":["SUMMARY"],"supported":null,"summary":"Water Flow (Inter-Block in J- Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BFLOWK":{"name":"BFLOWK","sections":["SUMMARY"],"supported":null,"summary":"Water Flow (Inter-Block in K+ Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BFLOWK-":{"name":"BFLOWK-","sections":["SUMMARY"],"supported":null,"summary":"Water Flow (Inter-Block in K- Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"RWFR":{"name":"RWFR","sections":["SUMMARY"],"supported":null,"summary":"Water Flow Rate Inter-Region. OPM Flow implementation.","parameters":[],"example":"","size_kind":"array","optional_body":true},"RWFR+":{"name":"RWFR+","sections":["SUMMARY"],"supported":null,"summary":"Water Flow Rate Inter-Region","parameters":[],"example":"","size_kind":"array","optional_body":true},"RWFR-":{"name":"RWFR-","sections":["SUMMARY"],"supported":null,"summary":"Water Flow Rate Inter-Region","parameters":[],"example":"","size_kind":"array","optional_body":true},"RWFT":{"name":"RWFT","sections":["SUMMARY"],"supported":null,"summary":"Water Flow Total Inter-Region","parameters":[],"example":"","size_kind":"array","optional_body":true},"RWFT+":{"name":"RWFT+","sections":["SUMMARY"],"supported":null,"summary":"Water Flow Total Inter-Region. OPM Flow implementation.","parameters":[],"example":"","size_kind":"array","optional_body":true},"RWFT-":{"name":"RWFT-","sections":["SUMMARY"],"supported":null,"summary":"Water Flow Total Inter-Region","parameters":[],"example":"","size_kind":"array","optional_body":true},"RWIR":{"name":"RWIR","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"RWIT":{"name":"RWIT","sections":["SUMMARY"],"supported":null,"summary":"Water Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"FPPW":{"name":"FPPW","sections":["SUMMARY"],"supported":null,"summary":"Water Potential","parameters":[],"example":"","size_kind":"none"},"RPPW":{"name":"RPPW","sections":["SUMMARY"],"supported":null,"summary":"Water Potential","parameters":[],"example":"","size_kind":"array","optional_body":true},"BPPW":{"name":"BPPW","sections":["SUMMARY"],"supported":null,"summary":"Water Potential","parameters":[],"example":"","size_kind":"array","optional_body":true},"RWPR":{"name":"RWPR","sections":["SUMMARY"],"supported":null,"summary":"Water Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"RWPT":{"name":"RWPT","sections":["SUMMARY"],"supported":null,"summary":"Water Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"RWP":{"name":"RWP","sections":["SUMMARY"],"supported":null,"summary":"Water Production Total (Net From Region)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BVELWI":{"name":"BVELWI","sections":["SUMMARY"],"supported":null,"summary":"Water Velocity (Inter-Block in I+ Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BVELWI-":{"name":"BVELWI-","sections":["SUMMARY"],"supported":null,"summary":"Water Velocity (Inter-Block in I- Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BVELWJ":{"name":"BVELWJ","sections":["SUMMARY"],"supported":null,"summary":"Water Velocity (Inter-Block in J+ Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BVELWJ-":{"name":"BVELWJ-","sections":["SUMMARY"],"supported":null,"summary":"Water Velocity (Inter-Block in J- Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BVELWK":{"name":"BVELWK","sections":["SUMMARY"],"supported":null,"summary":"Water Velocity (Inter-Block in K+ Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BVELWK-":{"name":"BVELWK-","sections":["SUMMARY"],"supported":null,"summary":"Water Velocity (Inter-Block in K- Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FAMIP":{"name":"FAMIP","sections":["SUMMARY"],"supported":null,"summary":"Water In-place","parameters":[],"example":"","size_kind":"none"},"RAMIP":{"name":"RAMIP","sections":["SUMMARY"],"supported":null,"summary":"Water In-place","parameters":[],"example":"","size_kind":"array","optional_body":true},"BAMIP":{"name":"BAMIP","sections":["SUMMARY"],"supported":null,"summary":"Water In-place","parameters":[],"example":"","size_kind":"array","optional_body":true},"BGPR":{"name":"BGPR","sections":["SUMMARY"],"supported":null,"summary":"Gas Phase Pressure","parameters":[],"example":"","size_kind":"array","optional_body":true},"FPR":{"name":"FPR","sections":["SUMMARY"],"supported":null,"summary":"Oil Phase Pressure. Field and Region HCPV weighted.","parameters":[],"example":"","size_kind":"none"},"RPR":{"name":"RPR","sections":["SUMMARY"],"supported":null,"summary":"Oil Phase Pressure. Field and Region HCPV weighted.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BPR":{"name":"BPR","sections":["SUMMARY"],"supported":null,"summary":"Oil Phase Pressure. Field and Region HCPV weighted.","parameters":[],"example":"","size_kind":"array","optional_body":true},"FPRH":{"name":"FPRH","sections":["SUMMARY"],"supported":null,"summary":"Oil Phase Pressure. Field and Region HCPV weighted.","parameters":[],"example":"","size_kind":"none"},"RPRH":{"name":"RPRH","sections":["SUMMARY"],"supported":null,"summary":"Oil Phase Pressure. Field and Region HCPV weighted.","parameters":[],"example":"","size_kind":"array","optional_body":true},"FPRP":{"name":"FPRP","sections":["SUMMARY"],"supported":null,"summary":"Oil Phase Pressure (PV Weighted). Field and Region PV weighted.","parameters":[],"example":"","size_kind":"none"},"RPRP":{"name":"RPRP","sections":["SUMMARY"],"supported":null,"summary":"Oil Phase Pressure (PV Weighted). Field and Region PV weighted.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BWPR":{"name":"BWPR","sections":["SUMMARY"],"supported":null,"summary":"Water Phase Pressure","parameters":[],"example":"","size_kind":"array","optional_body":true},"BSTATE":{"name":"BSTATE","sections":["SUMMARY"],"supported":null,"summary":"Block Hydrocarbon Phase State. Gas (1), Gas & Oil (2), and Oil (3).","parameters":[],"example":"","size_kind":"array","optional_body":true},"BPBUB":{"name":"BPBUB","sections":["SUMMARY"],"supported":null,"summary":"Bubble Point Pressure","parameters":[],"example":"","size_kind":"array","optional_body":true},"BGPC":{"name":"BGPC","sections":["SUMMARY"],"supported":null,"summary":"Capillary Pressure (Gas-Oil)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BWPC":{"name":"BWPC","sections":["SUMMARY"],"supported":null,"summary":"Capillary Pressure (Water-Oil)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BPDEW":{"name":"BPDEW","sections":["SUMMARY"],"supported":null,"summary":"Dew Point","parameters":[],"example":"","size_kind":"array","optional_body":true},"FPRGZ":{"name":"FPRGZ","sections":["SUMMARY"],"supported":null,"summary":"Gas P/Z","parameters":[],"example":"","size_kind":"none"},"RPRGZ":{"name":"RPRGZ","sections":["SUMMARY"],"supported":null,"summary":"Gas P/Z","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGDEN":{"name":"FGDEN","sections":["SUMMARY"],"supported":null,"summary":"Gas Reservoir Density","parameters":[],"example":"","size_kind":"none"},"RGDEN":{"name":"RGDEN","sections":["SUMMARY"],"supported":null,"summary":"Gas Reservoir Density","parameters":[],"example":"","size_kind":"array","optional_body":true},"BGDEN":{"name":"BGDEN","sections":["SUMMARY"],"supported":null,"summary":"Gas Reservoir Density","parameters":[],"example":"","size_kind":"array","optional_body":true},"BDENG":{"name":"BDENG","sections":["SUMMARY"],"supported":null,"summary":"Gas Reservoir Density. Same as BGDEN.","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGSAT":{"name":"FGSAT","sections":["SUMMARY"],"supported":null,"summary":"Gas Saturation. Also BSGAS.","parameters":[],"example":"","size_kind":"none"},"RGSAT":{"name":"RGSAT","sections":["SUMMARY"],"supported":null,"summary":"Gas Saturation. Also BSGAS.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BGSAT":{"name":"BGSAT","sections":["SUMMARY"],"supported":null,"summary":"Gas Saturation. Also BSGAS.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BGSHY":{"name":"BGSHY","sections":["SUMMARY"],"supported":null,"summary":"Gas Saturation (Drainage to Imbibition). Leaving gas saturation for gas capillary pressure hysteresis.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BGTPD":{"name":"BGTPD","sections":["SUMMARY"],"supported":null,"summary":"Gas Saturation (Dynamically Trapped). WAG hysteresis only.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BGSTRP":{"name":"BGSTRP","sections":["SUMMARY"],"supported":null,"summary":"Gas Saturation (Trapped Critical). For gas capillary pressure hysteresis.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BGTRP":{"name":"BGTRP","sections":["SUMMARY"],"supported":null,"summary":"Gas Saturation (Trapped). WAG hysteresis only.","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGVIS":{"name":"FGVIS","sections":["SUMMARY"],"supported":null,"summary":"Gas Viscosity","parameters":[],"example":"","size_kind":"none"},"RGVIS":{"name":"RGVIS","sections":["SUMMARY"],"supported":null,"summary":"Gas Viscosity","parameters":[],"example":"","size_kind":"array","optional_body":true},"BGVIS":{"name":"BGVIS","sections":["SUMMARY"],"supported":null,"summary":"Gas Viscosity","parameters":[],"example":"","size_kind":"array","optional_body":true},"BRSSAT":{"name":"BRSSAT","sections":["SUMMARY"],"supported":null,"summary":"Gas-Oil Ratio (Saturated)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FPPC":{"name":"FPPC","sections":["SUMMARY"],"supported":null,"summary":"Initial Contact Corrected Potential","parameters":[],"example":"","size_kind":"none"},"RPPC":{"name":"RPPC","sections":["SUMMARY"],"supported":null,"summary":"Initial Contact Corrected Potential","parameters":[],"example":"","size_kind":"array","optional_body":true},"BPPC":{"name":"BPPC","sections":["SUMMARY"],"supported":null,"summary":"Initial Contact Corrected Potential","parameters":[],"example":"","size_kind":"array","optional_body":true},"FODEN":{"name":"FODEN","sections":["SUMMARY"],"supported":null,"summary":"Oil Reservoir Density","parameters":[],"example":"","size_kind":"none"},"RODEN":{"name":"RODEN","sections":["SUMMARY"],"supported":null,"summary":"Oil Reservoir Density","parameters":[],"example":"","size_kind":"array","optional_body":true},"BODEN":{"name":"BODEN","sections":["SUMMARY"],"supported":null,"summary":"Oil Reservoir Density","parameters":[],"example":"","size_kind":"array","optional_body":true},"BDENO":{"name":"BDENO","sections":["SUMMARY"],"supported":null,"summary":"Oil Reservoir Density. Same as BODEN.","parameters":[],"example":"","size_kind":"array","optional_body":true},"FOSAT":{"name":"FOSAT","sections":["SUMMARY"],"supported":null,"summary":"Oil Saturation. Also BSOIL.","parameters":[],"example":"","size_kind":"none"},"ROSAT":{"name":"ROSAT","sections":["SUMMARY"],"supported":null,"summary":"Oil Saturation. Also BSOIL.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BOSAT":{"name":"BOSAT","sections":["SUMMARY"],"supported":null,"summary":"Oil Saturation. Also BSOIL.","parameters":[],"example":"","size_kind":"array","optional_body":true},"FOVIS":{"name":"FOVIS","sections":["SUMMARY"],"supported":null,"summary":"Oil Viscosity. Also BVOIL.","parameters":[],"example":"","size_kind":"none"},"ROVIS":{"name":"ROVIS","sections":["SUMMARY"],"supported":null,"summary":"Oil Viscosity. Also BVOIL.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BOVIS":{"name":"BOVIS","sections":["SUMMARY"],"supported":null,"summary":"Oil Viscosity. Also BVOIL.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BRVSAT":{"name":"BRVSAT","sections":["SUMMARY"],"supported":null,"summary":"Oil-Gas Ratio (Saturated)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BGKRR-":{"name":"BGKRR-","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Gas in the R- Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BGKRR":{"name":"BGKRR","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Gas in the R+ Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BGKRT-":{"name":"BGKRT-","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Gas in the Theta- Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BGKRT":{"name":"BGKRT","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Gas in the Theta+ Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BGKRX-":{"name":"BGKRX-","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Gas in the X- Direction). Also BGKRI-.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BGKRX":{"name":"BGKRX","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Gas in the X+ Direction). Also BGKRI.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BGKRY-":{"name":"BGKRY-","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Gas in the Y- Direction). Also BGKRJ-.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BGKRY":{"name":"BGKRY","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Gas in the Y+ Direction). Also BGKRJ.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BGKRZ-":{"name":"BGKRZ-","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Gas in the Z- Direction). Also BGKRK-.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BGKRZ":{"name":"BGKRZ","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Gas in the Z+ Direction). Also BGKRK.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BKRG":{"name":"BKRG","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Gas). Also BGWR.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BRK":{"name":"BRK","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Krw Reduction Factor). Due to Polymer.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BKROG":{"name":"BKROG","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Oil Two Phase to Gas)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BKROW":{"name":"BKROW","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Oil Two Phase to Water)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BOKRR-":{"name":"BOKRR-","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Oil in the R- Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BOKRR":{"name":"BOKRR","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Oil in the R+ Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BOKRT-":{"name":"BOKRT-","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Oil in the Theta- Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BOKRT":{"name":"BOKRT","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Oil in the Theta+ Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BOKRX-":{"name":"BOKRX-","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Oil in the X- Direction). Also BOKRI-.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BOKRX":{"name":"BOKRX","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Oil in the X+ Direction). Also BOKRI.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BOKRY-":{"name":"BOKRY-","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Oil in the Y- Direction). Also BOKRJ-.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BOKRY":{"name":"BOKRY","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Oil in the Y+ Direction). Also BOKRJ.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BOKRZ-":{"name":"BOKRZ-","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Oil in the Z- Direction). Also BOKRK-.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BOKRZ":{"name":"BOKRZ","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Oil in the Z+ Direction). Also BOKRK.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BKRO":{"name":"BKRO","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Oil). Also BOKR.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BWKRR-":{"name":"BWKRR-","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Water in the R- Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BWKRR":{"name":"BWKRR","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Water in the R+ Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BWKRT-":{"name":"BWKRT-","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Water in the Theta- Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BWKRT":{"name":"BWKRT","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Water in the Theta+ Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BWKRX-":{"name":"BWKRX-","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Water in the X- Direction). Also BWKRI-.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BWKRX":{"name":"BWKRX","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Water in the X+ Direction). Also BWKRI.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BWKRY-":{"name":"BWKRY-","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Water in the Y- Direction). Also BWKRJ-.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BWKRY":{"name":"BWKRY","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Water in the Y+ Direction). Also BWKRJ.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BWKRZ-":{"name":"BWKRZ-","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Water in the Z- Direction). Also BWKRK-.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BWKRZ":{"name":"BWKRZ","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Water in the Z+ Direction). Also BWKRK.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BKRW":{"name":"BKRW","sections":["SUMMARY"],"supported":null,"summary":"Relative Permeability (Water). Also BWKR.","parameters":[],"example":"","size_kind":"array","optional_body":true},"FWDEN":{"name":"FWDEN","sections":["SUMMARY"],"supported":null,"summary":"Water Reservoir Density","parameters":[],"example":"","size_kind":"none"},"RWDEN":{"name":"RWDEN","sections":["SUMMARY"],"supported":null,"summary":"Water Reservoir Density","parameters":[],"example":"","size_kind":"array","optional_body":true},"BWDEN":{"name":"BWDEN","sections":["SUMMARY"],"supported":null,"summary":"Water Reservoir Density","parameters":[],"example":"","size_kind":"array","optional_body":true},"BDENW":{"name":"BDENW","sections":["SUMMARY"],"supported":null,"summary":"Water Reservoir Density. Same as BWDEN.","parameters":[],"example":"","size_kind":"array","optional_body":true},"FWSAT":{"name":"FWSAT","sections":["SUMMARY"],"supported":null,"summary":"Water Saturation. Also BSWAT.","parameters":[],"example":"","size_kind":"none"},"RWSAT":{"name":"RWSAT","sections":["SUMMARY"],"supported":null,"summary":"Water Saturation. Also BSWAT.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BWSAT":{"name":"BWSAT","sections":["SUMMARY"],"supported":null,"summary":"Water Saturation. Also BSWAT.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BWSHY":{"name":"BWSHY","sections":["SUMMARY"],"supported":null,"summary":"Water Saturation (Drainage to Imbibition). Leaving water saturation for gas capillary pressure hysteresis.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BWSMA":{"name":"BWSMA","sections":["SUMMARY"],"supported":null,"summary":"Water Saturation (Maximum Wetting). Capillary pressure hysteresis maximum water saturation.","parameters":[],"example":"","size_kind":"array","optional_body":true},"FWVIS":{"name":"FWVIS","sections":["SUMMARY"],"supported":null,"summary":"Water Viscosity","parameters":[],"example":"","size_kind":"none"},"RWVIS":{"name":"RWVIS","sections":["SUMMARY"],"supported":null,"summary":"Water Viscosity","parameters":[],"example":"","size_kind":"array","optional_body":true},"BWVIS":{"name":"BWVIS","sections":["SUMMARY"],"supported":null,"summary":"Water Viscosity","parameters":[],"example":"","size_kind":"array","optional_body":true},"FRS":{"name":"FRS","sections":["SUMMARY"],"supported":null,"summary":"Gas-Oil Ratio","parameters":[],"example":"","size_kind":"none"},"RRS":{"name":"RRS","sections":["SUMMARY"],"supported":null,"summary":"Gas-Oil Ratio","parameters":[],"example":"","size_kind":"array","optional_body":true},"BRS":{"name":"BRS","sections":["SUMMARY"],"supported":null,"summary":"Gas-Oil Ratio","parameters":[],"example":"","size_kind":"array","optional_body":true},"FRV":{"name":"FRV","sections":["SUMMARY"],"supported":null,"summary":"Oil-Gas Ratio","parameters":[],"example":"","size_kind":"none"},"RRV":{"name":"RRV","sections":["SUMMARY"],"supported":null,"summary":"Oil-Gas Ratio","parameters":[],"example":"","size_kind":"array","optional_body":true},"BRV":{"name":"BRV","sections":["SUMMARY"],"supported":null,"summary":"Oil-Gas Ratio","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGIP":{"name":"FGIP","sections":["SUMMARY"],"supported":null,"summary":"Gas In-Place. Liquid and gas phases.","parameters":[],"example":"","size_kind":"none"},"RGIP":{"name":"RGIP","sections":["SUMMARY"],"supported":null,"summary":"Gas In-Place. Liquid and gas phases.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BGIP":{"name":"BGIP","sections":["SUMMARY"],"supported":null,"summary":"Gas In-Place. Liquid and gas phases.","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGIPG":{"name":"FGIPG","sections":["SUMMARY"],"supported":null,"summary":"Gas In-Place (Gas Phase)","parameters":[],"example":"","size_kind":"none"},"RGIPG":{"name":"RGIPG","sections":["SUMMARY"],"supported":null,"summary":"Gas In-Place (Gas Phase)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BGIPG":{"name":"BGIPG","sections":["SUMMARY"],"supported":null,"summary":"Gas In-Place (Gas Phase)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGIPL":{"name":"FGIPL","sections":["SUMMARY"],"supported":null,"summary":"Gas In-Place (Liquid Phase). Only for cases that have dissolved gas in the water phase.","parameters":[],"example":"","size_kind":"none"},"RGIPL":{"name":"RGIPL","sections":["SUMMARY"],"supported":null,"summary":"Gas In-Place (Liquid Phase). Only for cases that have dissolved gas in the water phase.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BGIPL":{"name":"BGIPL","sections":["SUMMARY"],"supported":null,"summary":"Gas In-Place (Liquid Phase). Only for cases that have dissolved gas in the water phase.","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGIPR":{"name":"FGIPR","sections":["SUMMARY"],"supported":null,"summary":"Gas In-Place (Reservoir Conditions). Compositional vector implemented in OPM Flow.","parameters":[],"example":"","size_kind":"none"},"FOIP":{"name":"FOIP","sections":["SUMMARY"],"supported":null,"summary":"Oil In-Place. Liquid and gas phases.","parameters":[],"example":"","size_kind":"none"},"ROIP":{"name":"ROIP","sections":["SUMMARY"],"supported":null,"summary":"Oil In-Place. Liquid and gas phases.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BOIP":{"name":"BOIP","sections":["SUMMARY"],"supported":null,"summary":"Oil In-Place. Liquid and gas phases.","parameters":[],"example":"","size_kind":"array","optional_body":true},"FOIPG":{"name":"FOIPG","sections":["SUMMARY"],"supported":null,"summary":"Oil In-Place (Gas Phase)","parameters":[],"example":"","size_kind":"none"},"ROIPG":{"name":"ROIPG","sections":["SUMMARY"],"supported":null,"summary":"Oil In-Place (Gas Phase)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BOIPG":{"name":"BOIPG","sections":["SUMMARY"],"supported":null,"summary":"Oil In-Place (Gas Phase)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FOIPL":{"name":"FOIPL","sections":["SUMMARY"],"supported":null,"summary":"Oil In-Place (Liquid Phase)","parameters":[],"example":"","size_kind":"none"},"ROIPL":{"name":"ROIPL","sections":["SUMMARY"],"supported":null,"summary":"Oil In-Place (Liquid Phase)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BOIPL":{"name":"BOIPL","sections":["SUMMARY"],"supported":null,"summary":"Oil In-Place (Liquid Phase)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FOIPR":{"name":"FOIPR","sections":["SUMMARY"],"supported":null,"summary":"Oil In-Place (Reservoir Conditions). Compositional vector implemented in OPM Flow.","parameters":[],"example":"","size_kind":"none"},"FGPV":{"name":"FGPV","sections":["SUMMARY"],"supported":null,"summary":"Pore Volume (Gas)","parameters":[],"example":"","size_kind":"none"},"RGPV":{"name":"RGPV","sections":["SUMMARY"],"supported":null,"summary":"Pore Volume (Gas)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BGPV":{"name":"BGPV","sections":["SUMMARY"],"supported":null,"summary":"Pore Volume (Gas)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FHPV":{"name":"FHPV","sections":["SUMMARY"],"supported":null,"summary":"Pore Volume (HCPV)","parameters":[],"example":"","size_kind":"none"},"RHPV":{"name":"RHPV","sections":["SUMMARY"],"supported":null,"summary":"Pore Volume (HCPV)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BHPV":{"name":"BHPV","sections":["SUMMARY"],"supported":null,"summary":"Pore Volume (HCPV)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FOPV":{"name":"FOPV","sections":["SUMMARY"],"supported":null,"summary":"Pore Volume (Oil)","parameters":[],"example":"","size_kind":"none"},"ROPV":{"name":"ROPV","sections":["SUMMARY"],"supported":null,"summary":"Pore Volume (Oil)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BOPV":{"name":"BOPV","sections":["SUMMARY"],"supported":null,"summary":"Pore Volume (Oil)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FRPV":{"name":"FRPV","sections":["SUMMARY"],"supported":null,"summary":"Pore Volume (Reservoir Conditions). Also BPORV.","parameters":[],"example":"","size_kind":"none"},"RRPV":{"name":"RRPV","sections":["SUMMARY"],"supported":null,"summary":"Pore Volume (Reservoir Conditions). Also BPORV.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BRPV":{"name":"BRPV","sections":["SUMMARY"],"supported":null,"summary":"Pore Volume (Reservoir Conditions). Also BPORV.","parameters":[],"example":"","size_kind":"array","optional_body":true},"FWPV":{"name":"FWPV","sections":["SUMMARY"],"supported":null,"summary":"Pore Volume (Water)","parameters":[],"example":"","size_kind":"none"},"RWPV":{"name":"RWPV","sections":["SUMMARY"],"supported":null,"summary":"Pore Volume (Water)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BWPV":{"name":"BWPV","sections":["SUMMARY"],"supported":null,"summary":"Pore Volume (Water)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BPERMMDX":{"name":"BPERMMDX","sections":["SUMMARY"],"supported":null,"summary":"Rock Compaction (Trans. Multiplier X Direction). Also BPERMOD.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BPERMMDY":{"name":"BPERMMDY","sections":["SUMMARY"],"supported":null,"summary":"Rock Compaction (Trans. Multiplier Y Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BPERMMDZ":{"name":"BPERMMDZ","sections":["SUMMARY"],"supported":null,"summary":"Rock Compaction (Trans. Multiplier Z Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FRTM":{"name":"FRTM","sections":["SUMMARY"],"supported":null,"summary":"Rock Compaction (Trans. Multiplier)","parameters":[],"example":"","size_kind":"none"},"RRTM":{"name":"RRTM","sections":["SUMMARY"],"supported":null,"summary":"Rock Compaction (Trans. Multiplier)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BRTM":{"name":"BRTM","sections":["SUMMARY"],"supported":null,"summary":"Rock Compaction (Trans. Multiplier)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BSIGMMOD":{"name":"BSIGMMOD","sections":["SUMMARY"],"supported":null,"summary":"Rock Compaction (Dual Porosity SIGMA Multiplier)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BPORVMOD":{"name":"BPORVMOD","sections":["SUMMARY"],"supported":null,"summary":"Rock Compaction (PV Multiplier)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FWIP":{"name":"FWIP","sections":["SUMMARY"],"supported":null,"summary":"Water In-Place","parameters":[],"example":"","size_kind":"none"},"RWIP":{"name":"RWIP","sections":["SUMMARY"],"supported":null,"summary":"Water In-Place","parameters":[],"example":"","size_kind":"array","optional_body":true},"BWIP":{"name":"BWIP","sections":["SUMMARY"],"supported":null,"summary":"Water In-Place","parameters":[],"example":"","size_kind":"array","optional_body":true},"FWIPR":{"name":"FWIPR","sections":["SUMMARY"],"supported":null,"summary":"Water In-Place (Reservoir Conditions). Compositional vector implemented in OPM Flow.","parameters":[],"example":"","size_kind":"none"},"FOE":{"name":"FOE","sections":["SUMMARY"],"supported":null,"summary":"Oil Recovery Efficiency (STOIIP). Based on STOIIP.","parameters":[],"example":"","size_kind":"none"},"ROE":{"name":"ROE","sections":["SUMMARY"],"supported":null,"summary":"Oil Recovery Efficiency (STOIIP). Based on STOIIP.","parameters":[],"example":"","size_kind":"array","optional_body":true},"FOEW":{"name":"FOEW","sections":["SUMMARY"],"supported":null,"summary":"Oil Recovery Efficiency (Wells). Based on well production and STOIIP.","parameters":[],"example":"","size_kind":"none"},"ROEW":{"name":"ROEW","sections":["SUMMARY"],"supported":null,"summary":"Oil Recovery Efficiency (Wells). Based on well production and STOIIP.","parameters":[],"example":"","size_kind":"array","optional_body":true},"FOEIW":{"name":"FOEIW","sections":["SUMMARY"],"supported":null,"summary":"Oil Recovery Efficiency (STOIIP Mobile with Respect to Water). Based on STOIIP and initial mobile oil saturate with respect to water.","parameters":[],"example":"","size_kind":"none"},"ROEIW":{"name":"ROEIW","sections":["SUMMARY"],"supported":null,"summary":"Oil Recovery Efficiency (STOIIP Mobile with Respect to Water). Based on STOIIP and initial mobile oil saturate with respect to water.","parameters":[],"example":"","size_kind":"array","optional_body":true},"FOEWW":{"name":"FOEWW","sections":["SUMMARY"],"supported":null,"summary":"Oil Recovery Efficiency Wells Mobile with Respect to Water). Based on well production and initial mobile oil saturate with respect to water.","parameters":[],"example":"","size_kind":"none"},"ROEWW":{"name":"ROEWW","sections":["SUMMARY"],"supported":null,"summary":"Oil Recovery Efficiency Wells Mobile with Respect to Water). Based on well production and initial mobile oil saturate with respect to water.","parameters":[],"example":"","size_kind":"array","optional_body":true},"FOEIG":{"name":"FOEIG","sections":["SUMMARY"],"supported":null,"summary":"Oil Recovery Efficiency (STOIIP Mobile with Respect to Gas). Based on STOIIP and initial mobile oil saturate with respect to gas.","parameters":[],"example":"","size_kind":"none"},"ROEIG":{"name":"ROEIG","sections":["SUMMARY"],"supported":null,"summary":"Oil Recovery Efficiency (STOIIP Mobile with Respect to Gas). Based on STOIIP and initial mobile oil saturate with respect to gas.","parameters":[],"example":"","size_kind":"array","optional_body":true},"FOEWG":{"name":"FOEWG","sections":["SUMMARY"],"supported":null,"summary":"Oil Recovery Efficiency (Wells Mobile with Respect to Gas). Based on well production and initial mobile oil saturate with respect to gas.","parameters":[],"example":"","size_kind":"none"},"ROEWG":{"name":"ROEWG","sections":["SUMMARY"],"supported":null,"summary":"Oil Recovery Efficiency (Wells Mobile with Respect to Gas). Based on well production and initial mobile oil saturate with respect to gas.","parameters":[],"example":"","size_kind":"array","optional_body":true},"FOTMF":{"name":"FOTMF","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total (Free Gas Gas). Volumes reported at stock tank conditions.","parameters":[],"example":"","size_kind":"none"},"ROTMF":{"name":"ROTMF","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total (Free Gas Gas). Volumes reported at stock tank conditions.","parameters":[],"example":"","size_kind":"array","optional_body":true},"FORMG":{"name":"FORMG","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total (Gas Influx)","parameters":[],"example":"","size_kind":"none"},"RORMG":{"name":"RORMG","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total (Gas Influx)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FORME":{"name":"FORME","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total (Oil Expansion)","parameters":[],"example":"","size_kind":"none"},"RORME":{"name":"RORME","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total (Oil Expansion)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FORMR":{"name":"FORMR","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total (Rock Compaction)","parameters":[],"example":"","size_kind":"none"},"RORMR":{"name":"RORMR","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total (Rock Compaction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FORMS":{"name":"FORMS","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total (Solution Gas)","parameters":[],"example":"","size_kind":"none"},"RORMS":{"name":"RORMS","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total (Solution Gas)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FORMW":{"name":"FORMW","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total (Water Influx)","parameters":[],"example":"","size_kind":"none"},"RORMW":{"name":"RORMW","sections":["SUMMARY"],"supported":null,"summary":"Oil Production Total (Water Influx)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FAPI":{"name":"FAPI","sections":["SUMMARY"],"supported":null,"summary":"Oil API","parameters":[],"example":"","size_kind":"none"},"GAPI":{"name":"GAPI","sections":["SUMMARY"],"supported":null,"summary":"Oil API","parameters":[],"example":"","size_kind":"array","optional_body":true},"CAPI":{"name":"CAPI","sections":["SUMMARY"],"supported":null,"summary":"Oil API","parameters":[],"example":"","size_kind":"array","optional_body":true},"RAPI":{"name":"RAPI","sections":["SUMMARY"],"supported":null,"summary":"Oil API","parameters":[],"example":"","size_kind":"array","optional_body":true},"BAPI":{"name":"BAPI","sections":["SUMMARY"],"supported":null,"summary":"Oil API","parameters":[],"example":"","size_kind":"array","optional_body":true},"CTFR":{"name":"CTFR","sections":["SUMMARY"],"supported":null,"summary":"Tracer Flow Rate","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"RTFTT":{"name":"RTFTT","sections":["SUMMARY"],"supported":null,"summary":"Tracer Flow Total (Inter Region)","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"RTFTF":{"name":"RTFTF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Flow Total (Free Inter Region)","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"RTFTS":{"name":"RTFTS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Flow Total (Solution Inter Region)","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"FTIC":{"name":"FTIC","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Concentration","parameters":[],"example":"","size_kind":"none","templated":true},"GTIC":{"name":"GTIC","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Concentration","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"WTIC":{"name":"WTIC","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Concentration","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"CTIC":{"name":"CTIC","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Concentration","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"FTICF":{"name":"FTICF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Concentration (Free)","parameters":[],"example":"","size_kind":"none","templated":true},"GTICF":{"name":"GTICF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Concentration (Free)","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"WTICF":{"name":"WTICF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Concentration (Free)","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"CTICF":{"name":"CTICF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Concentration (Free)","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"FTICS":{"name":"FTICS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Concentration (Solution)","parameters":[],"example":"","size_kind":"none","templated":true},"GTICS":{"name":"GTICS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Concentration (Solution)","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"WTICS":{"name":"WTICS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Concentration (Solution)","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"CTICS":{"name":"CTICS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Concentration (Solution)","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"FTIR":{"name":"FTIR","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Rate","parameters":[],"example":"","size_kind":"none","templated":true},"GTIR":{"name":"GTIR","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Rate","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"WTIR":{"name":"WTIR","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Rate","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"CTIR":{"name":"CTIR","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Rate","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"FTIRF":{"name":"FTIRF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Rate (Free)","parameters":[],"example":"","size_kind":"none","templated":true},"GTIRF":{"name":"GTIRF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Rate (Free)","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"WTIRF":{"name":"WTIRF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Rate (Free)","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"CTIRF":{"name":"CTIRF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Rate (Free)","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"FTIRS":{"name":"FTIRS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Rate (Solution)","parameters":[],"example":"","size_kind":"none","templated":true},"GTIRS":{"name":"GTIRS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Rate (Solution)","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"WTIRS":{"name":"WTIRS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Rate (Solution)","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"CTIRS":{"name":"CTIRS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Rate (Solution)","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"FTIT":{"name":"FTIT","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Total","parameters":[],"example":"","size_kind":"none","templated":true},"GTIT":{"name":"GTIT","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Total","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"WTIT":{"name":"WTIT","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Total","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"CTIT":{"name":"CTIT","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Total","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"FTITF":{"name":"FTITF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Total (Free)","parameters":[],"example":"","size_kind":"none","templated":true},"GTITF":{"name":"GTITF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Total (Free)","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"WTITF":{"name":"WTITF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Total (Free)","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"CTITF":{"name":"CTITF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Total (Free)","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"FTITS":{"name":"FTITS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Total (Solution)","parameters":[],"example":"","size_kind":"none","templated":true},"GTITS":{"name":"GTITS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Total (Solution)","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"WTITS":{"name":"WTITS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Total (Solution)","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"CTITS":{"name":"CTITS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Injection Total (Solution)","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"FTPC":{"name":"FTPC","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Concentration","parameters":[],"example":"","size_kind":"none","templated":true},"GTPC":{"name":"GTPC","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Concentration","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"WTPC":{"name":"WTPC","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Concentration","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"CTPC":{"name":"CTPC","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Concentration","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"FTPCF":{"name":"FTPCF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Concentration (Free)","parameters":[],"example":"","size_kind":"none","templated":true},"GTPCF":{"name":"GTPCF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Concentration (Free)","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"WTPCF":{"name":"WTPCF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Concentration (Free)","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"CTPCF":{"name":"CTPCF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Concentration (Free)","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"FTPCS":{"name":"FTPCS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Concentration (Solution)","parameters":[],"example":"","size_kind":"none","templated":true},"GTPCS":{"name":"GTPCS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Concentration (Solution)","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"WTPCS":{"name":"WTPCS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Concentration (Solution)","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"CTPCS":{"name":"CTPCS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Concentration (Solution)","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"FTPR":{"name":"FTPR","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Rate","parameters":[],"example":"","size_kind":"none","templated":true},"GTPR":{"name":"GTPR","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Rate","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"WTPR":{"name":"WTPR","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Rate","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"CTPR":{"name":"CTPR","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Rate","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"FTPRF":{"name":"FTPRF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Rate (Free)","parameters":[],"example":"","size_kind":"none","templated":true},"GTPRF":{"name":"GTPRF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Rate (Free)","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"WTPRF":{"name":"WTPRF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Rate (Free)","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"CTPRF":{"name":"CTPRF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Rate (Free)","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"FTPRS":{"name":"FTPRS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Rate (Solution)","parameters":[],"example":"","size_kind":"none","templated":true},"GTPRS":{"name":"GTPRS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Rate (Solution)","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"WTPRS":{"name":"WTPRS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Rate (Solution)","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"CTPRS":{"name":"CTPRS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Rate (Solution)","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"FTPT":{"name":"FTPT","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Total","parameters":[],"example":"","size_kind":"none","templated":true},"GTPT":{"name":"GTPT","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Total","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"WTPT":{"name":"WTPT","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Total","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"CTPT":{"name":"CTPT","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Total","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"FTPTF":{"name":"FTPTF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Total (Free)","parameters":[],"example":"","size_kind":"none","templated":true},"GTPTF":{"name":"GTPTF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Total (Free)","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"WTPTF":{"name":"WTPTF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Total (Free)","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"CTPTF":{"name":"CTPTF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Total (Free)","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"FTPTS":{"name":"FTPTS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Total (Solution)","parameters":[],"example":"","size_kind":"none","templated":true},"GTPTS":{"name":"GTPTS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Total (Solution)","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"WTPTS":{"name":"WTPTS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Total (Solution)","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"CTPTS":{"name":"CTPTS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Production Total (Solution)","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"BTCN":{"name":"BTCN","sections":["SUMMARY"],"supported":null,"summary":"Tracer Concentration","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"BTCNF":{"name":"BTCNF","sections":["SUMMARY"],"supported":null,"summary":"Tracer Concentration (Free)","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"BTCNS":{"name":"BTCNS","sections":["SUMMARY"],"supported":null,"summary":"Tracer Concentration (Solution)","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"FTIPT":{"name":"FTIPT","sections":["SUMMARY"],"supported":null,"summary":"Tracer In-Place","parameters":[],"example":"","size_kind":"none","templated":true},"RTIPT":{"name":"RTIPT","sections":["SUMMARY"],"supported":null,"summary":"Tracer In-Place","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"BTIPT":{"name":"BTIPT","sections":["SUMMARY"],"supported":null,"summary":"Tracer In-Place","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"FTIPF":{"name":"FTIPF","sections":["SUMMARY"],"supported":null,"summary":"Tracer In-Place (Free)","parameters":[],"example":"","size_kind":"none","templated":true},"RTIPF":{"name":"RTIPF","sections":["SUMMARY"],"supported":null,"summary":"Tracer In-Place (Free)","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"BTIPF":{"name":"BTIPF","sections":["SUMMARY"],"supported":null,"summary":"Tracer In-Place (Free)","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"FTIPS":{"name":"FTIPS","sections":["SUMMARY"],"supported":null,"summary":"Tracer In-Place (Solution)","parameters":[],"example":"","size_kind":"none","templated":true},"RTIPS":{"name":"RTIPS","sections":["SUMMARY"],"supported":null,"summary":"Tracer In-Place (Solution)","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"BTIPS":{"name":"BTIPS","sections":["SUMMARY"],"supported":null,"summary":"Tracer In-Place (Solution)","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"CSFR":{"name":"CSFR","sections":["SUMMARY"],"supported":null,"summary":"Salt Flow Rate. Brine and Salt Precipitation Models.","parameters":[],"example":"","size_kind":"array","optional_body":true},"FSIR":{"name":"FSIR","sections":["SUMMARY"],"supported":null,"summary":"Salt Injection Rate","parameters":[],"example":"","size_kind":"none"},"GSIR":{"name":"GSIR","sections":["SUMMARY"],"supported":null,"summary":"Salt Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WSIR":{"name":"WSIR","sections":["SUMMARY"],"supported":null,"summary":"Salt Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"CSIR":{"name":"CSIR","sections":["SUMMARY"],"supported":null,"summary":"Salt Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FSIT":{"name":"FSIT","sections":["SUMMARY"],"supported":null,"summary":"Salt Injection Total","parameters":[],"example":"","size_kind":"none"},"GSIT":{"name":"GSIT","sections":["SUMMARY"],"supported":null,"summary":"Salt Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"WSIT":{"name":"WSIT","sections":["SUMMARY"],"supported":null,"summary":"Salt Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CSIT":{"name":"CSIT","sections":["SUMMARY"],"supported":null,"summary":"Salt Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"FSPR":{"name":"FSPR","sections":["SUMMARY"],"supported":null,"summary":"Salt Production Rate","parameters":[],"example":"","size_kind":"none"},"GSPR":{"name":"GSPR","sections":["SUMMARY"],"supported":null,"summary":"Salt Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WSPR":{"name":"WSPR","sections":["SUMMARY"],"supported":null,"summary":"Salt Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"CSPR":{"name":"CSPR","sections":["SUMMARY"],"supported":null,"summary":"Salt Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FSPT":{"name":"FSPT","sections":["SUMMARY"],"supported":null,"summary":"Salt Production Total","parameters":[],"example":"","size_kind":"none"},"GSPT":{"name":"GSPT","sections":["SUMMARY"],"supported":null,"summary":"Salt Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"WSPT":{"name":"WSPT","sections":["SUMMARY"],"supported":null,"summary":"Salt Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CSPT":{"name":"CSPT","sections":["SUMMARY"],"supported":null,"summary":"Salt Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"BEMV_SAL":{"name":"BEMV_SAL","sections":["SUMMARY"],"supported":null,"summary":"Salt Corrected Water Viscosity","parameters":[],"example":"","size_kind":"array","optional_body":true},"BSCN":{"name":"BSCN","sections":["SUMMARY"],"supported":null,"summary":"Salt Concentration (Block)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FSIC":{"name":"FSIC","sections":["SUMMARY"],"supported":null,"summary":"Salt Concentration (Injection)","parameters":[],"example":"","size_kind":"none"},"GSIC":{"name":"GSIC","sections":["SUMMARY"],"supported":null,"summary":"Salt Concentration (Injection)","parameters":[],"example":"","size_kind":"array","optional_body":true},"WSIC":{"name":"WSIC","sections":["SUMMARY"],"supported":null,"summary":"Salt Concentration (Injection)","parameters":[],"example":"","size_kind":"array","optional_body":true},"CSIC":{"name":"CSIC","sections":["SUMMARY"],"supported":null,"summary":"Salt Concentration (Injection)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FSPC":{"name":"FSPC","sections":["SUMMARY"],"supported":null,"summary":"Salt Concentration (Production)","parameters":[],"example":"","size_kind":"none"},"GSPC":{"name":"GSPC","sections":["SUMMARY"],"supported":null,"summary":"Salt Concentration (Production)","parameters":[],"example":"","size_kind":"array","optional_body":true},"WSPC":{"name":"WSPC","sections":["SUMMARY"],"supported":null,"summary":"Salt Concentration (Production)","parameters":[],"example":"","size_kind":"array","optional_body":true},"CSPC":{"name":"CSPC","sections":["SUMMARY"],"supported":null,"summary":"Salt Concentration (Production)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FSIP":{"name":"FSIP","sections":["SUMMARY"],"supported":null,"summary":"Salt In-Place","parameters":[],"example":"","size_kind":"none"},"RSIP":{"name":"RSIP","sections":["SUMMARY"],"supported":null,"summary":"Salt In-Place","parameters":[],"example":"","size_kind":"array","optional_body":true},"BSIP":{"name":"BSIP","sections":["SUMMARY"],"supported":null,"summary":"Salt In-Place","parameters":[],"example":"","size_kind":"array","optional_body":true},"BTCNFANI":{"name":"BTCNFANI","sections":["SUMMARY"],"supported":null,"summary":"Anion Concentration (Block). Multi-Component Brine Model.","parameters":[],"example":"","size_kind":"array","optional_body":true},"CTFRANI":{"name":"CTFRANI","sections":["SUMMARY"],"supported":null,"summary":"Anion Flow Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FTIRANI":{"name":"FTIRANI","sections":["SUMMARY"],"supported":null,"summary":"Anion Injection Rate","parameters":[],"example":"","size_kind":"none"},"GTIRANI":{"name":"GTIRANI","sections":["SUMMARY"],"supported":null,"summary":"Anion Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WTIRANI":{"name":"WTIRANI","sections":["SUMMARY"],"supported":null,"summary":"Anion Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FTITANI":{"name":"FTITANI","sections":["SUMMARY"],"supported":null,"summary":"Anion Injection Total","parameters":[],"example":"","size_kind":"none"},"GTITANI":{"name":"GTITANI","sections":["SUMMARY"],"supported":null,"summary":"Anion Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"WTITANI":{"name":"WTITANI","sections":["SUMMARY"],"supported":null,"summary":"Anion Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CTITANI":{"name":"CTITANI","sections":["SUMMARY"],"supported":null,"summary":"Anion Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"FTPRANI":{"name":"FTPRANI","sections":["SUMMARY"],"supported":null,"summary":"Anion Production Rate","parameters":[],"example":"","size_kind":"none"},"GTPRANI":{"name":"GTPRANI","sections":["SUMMARY"],"supported":null,"summary":"Anion Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WTPRANI":{"name":"WTPRANI","sections":["SUMMARY"],"supported":null,"summary":"Anion Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FTPTANI":{"name":"FTPTANI","sections":["SUMMARY"],"supported":null,"summary":"Anion Production Total","parameters":[],"example":"","size_kind":"none"},"GTPTANI":{"name":"GTPTANI","sections":["SUMMARY"],"supported":null,"summary":"Anion Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"WTPTANI":{"name":"WTPTANI","sections":["SUMMARY"],"supported":null,"summary":"Anion Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CTPTANI":{"name":"CTPTANI","sections":["SUMMARY"],"supported":null,"summary":"Anion Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CTFRCAT":{"name":"CTFRCAT","sections":["SUMMARY"],"supported":null,"summary":"Cation Flow Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FTIRCAT":{"name":"FTIRCAT","sections":["SUMMARY"],"supported":null,"summary":"Cation Injection Rate","parameters":[],"example":"","size_kind":"none"},"GTIRCAT":{"name":"GTIRCAT","sections":["SUMMARY"],"supported":null,"summary":"Cation Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WTIRCAT":{"name":"WTIRCAT","sections":["SUMMARY"],"supported":null,"summary":"Cation Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FTITCAT":{"name":"FTITCAT","sections":["SUMMARY"],"supported":null,"summary":"Cation Injection Total","parameters":[],"example":"","size_kind":"none"},"GTITCAT":{"name":"GTITCAT","sections":["SUMMARY"],"supported":null,"summary":"Cation Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"WTITCAT":{"name":"WTITCAT","sections":["SUMMARY"],"supported":null,"summary":"Cation Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CTITCAT":{"name":"CTITCAT","sections":["SUMMARY"],"supported":null,"summary":"Cation Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"FTPRCAT":{"name":"FTPRCAT","sections":["SUMMARY"],"supported":null,"summary":"Cation Production Rate","parameters":[],"example":"","size_kind":"none"},"GTPRCAT":{"name":"GTPRCAT","sections":["SUMMARY"],"supported":null,"summary":"Cation Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WTPRCAT":{"name":"WTPRCAT","sections":["SUMMARY"],"supported":null,"summary":"Cation Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FTPTCAT":{"name":"FTPTCAT","sections":["SUMMARY"],"supported":null,"summary":"Cation Production Total","parameters":[],"example":"","size_kind":"none"},"GTPTCAT":{"name":"GTPTCAT","sections":["SUMMARY"],"supported":null,"summary":"Cation Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"WTPTCAT":{"name":"WTPTCAT","sections":["SUMMARY"],"supported":null,"summary":"Cation Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CTPTCAT":{"name":"CTPTCAT","sections":["SUMMARY"],"supported":null,"summary":"Cation Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"BESALPLY":{"name":"BESALPLY","sections":["SUMMARY"],"supported":null,"summary":"Effective Salinity (Polymer)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BESALSUR":{"name":"BESALSUR","sections":["SUMMARY"],"supported":null,"summary":"Effective Salinity (Surfactant)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BTCNFCAT":{"name":"BTCNFCAT","sections":["SUMMARY"],"supported":null,"summary":"Cation Concentration (Block)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BTRADCAT":{"name":"BTRADCAT","sections":["SUMMARY"],"supported":null,"summary":"Cation Concentration (Rock Associated)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BTSADCAT":{"name":"BTSADCAT","sections":["SUMMARY"],"supported":null,"summary":"Cation Concentration (Surfactant Associated)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGMIR":{"name":"FGMIR","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mass Injection Rate","parameters":[],"example":"","size_kind":"none"},"GGMIR":{"name":"GGMIR","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mass Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WGMIR":{"name":"WGMIR","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mass Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"CGMIR":{"name":"CGMIR","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mass Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGMIT":{"name":"FGMIT","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mass Injection Total","parameters":[],"example":"","size_kind":"none"},"GGMIT":{"name":"GGMIT","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mass Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"WGMIT":{"name":"WGMIT","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mass Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CGMIT":{"name":"CGMIT","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mass Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGMPR":{"name":"FGMPR","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mass Production Rate","parameters":[],"example":"","size_kind":"none"},"GGMPR":{"name":"GGMPR","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mass Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WGMPR":{"name":"WGMPR","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mass Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"CGMPR":{"name":"CGMPR","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mass Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGMPT":{"name":"FGMPT","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mass Production Total","parameters":[],"example":"","size_kind":"none"},"GGMPT":{"name":"GGMPT","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mass Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"WGMPT":{"name":"WGMPT","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mass Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CGMPT":{"name":"CGMPT","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mass Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGMIP":{"name":"FGMIP","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 In-place","parameters":[],"example":"","size_kind":"none"},"RGMIP":{"name":"RGMIP","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 In-place","parameters":[],"example":"","size_kind":"array","optional_body":true},"BGMIP":{"name":"BGMIP","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 In-place","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGMGP":{"name":"FGMGP","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 In-place (Gas Phase)","parameters":[],"example":"","size_kind":"none"},"RGMGP":{"name":"RGMGP","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 In-place (Gas Phase)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BGMGP":{"name":"BGMGP","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 In-place (Gas Phase)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGMDS":{"name":"FGMDS","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 In-place (Liquid Phase)","parameters":[],"example":"","size_kind":"none"},"RGMDS":{"name":"RGMDS","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 In-place (Liquid Phase)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BGMDS":{"name":"BGMDS","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 In-place (Liquid Phase)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGMST":{"name":"FGMST","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Effectively Residual Trapped ('Stranded') in the gas phase","parameters":[],"example":"","size_kind":"none"},"RGMST":{"name":"RGMST","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Effectively Residual Trapped ('Stranded') in the gas phase","parameters":[],"example":"","size_kind":"array","optional_body":true},"BGMST":{"name":"BGMST","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Effectively Residual Trapped ('Stranded') in the gas phase","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGMUS":{"name":"FGMUS","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Effectively Residual Untrapped ('Unstranded') in the gas phase","parameters":[],"example":"","size_kind":"none"},"RGMUS":{"name":"RGMUS","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Effectively Residual Untrapped ('Unstranded') in the gas phase","parameters":[],"example":"","size_kind":"array","optional_body":true},"BGMUS":{"name":"BGMUS","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Effectively Residual Untrapped ('Unstranded') in the gas phase","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGMTR":{"name":"FGMTR","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Maximum Potential Residual Trapped in the gas phase","parameters":[],"example":"","size_kind":"none"},"RGMTR":{"name":"RGMTR","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Maximum Potential Residual Trapped in the gas phase","parameters":[],"example":"","size_kind":"array","optional_body":true},"BGMTR":{"name":"BGMTR","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Maximum Potential Residual Trapped in the gas phase","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGMMO":{"name":"FGMMO","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Maximum Potential Residual Untrapped in the gas phase","parameters":[],"example":"","size_kind":"none"},"RGMMO":{"name":"RGMMO","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Maximum Potential Residual Untrapped in the gas phase","parameters":[],"example":"","size_kind":"array","optional_body":true},"BGMMO":{"name":"BGMMO","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Maximum Potential Residual Untrapped in the gas phase","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGKTR":{"name":"FGKTR","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Immobile in the gas phase (Non-wetting relative permeability equals zero)","parameters":[],"example":"","size_kind":"none"},"RGKTR":{"name":"RGKTR","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Immobile in the gas phase (Non-wetting relative permeability equals zero)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BGKTR":{"name":"BGKTR","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Immobile in the gas phase (Non-wetting relative permeability equals zero)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGKMO":{"name":"FGKMO","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mobile in the gas phase (Non-wetting relative permeability greater than zero)","parameters":[],"example":"","size_kind":"none"},"RGKMO":{"name":"RGKMO","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mobile in the gas phase (Non-wetting relative permeability greater than zero)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BGKMO":{"name":"BGKMO","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mobile in the gas phase (Non-wetting relative permeability greater than zero)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGCDI":{"name":"FGCDI","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Immobile in the gas phase","parameters":[],"example":"","size_kind":"none"},"RGCDI":{"name":"RGCDI","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Immobile in the gas phase","parameters":[],"example":"","size_kind":"array","optional_body":true},"BGCDI":{"name":"BGCDI","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Immobile in the gas phase","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGCDM":{"name":"FGCDM","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mobile in the gas phase","parameters":[],"example":"","size_kind":"none"},"RGCDM":{"name":"RGCDM","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mobile in the gas phase","parameters":[],"example":"","size_kind":"array","optional_body":true},"BGCDM":{"name":"BGCDM","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mobile in the gas phase","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGKDI":{"name":"FGKDI","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Immobile in the gas phase (Non-wetting relative permeability equals zero)","parameters":[],"example":"","size_kind":"none"},"RGKDI":{"name":"RGKDI","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Immobile in the gas phase (Non-wetting relative permeability equals zero)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BGKDI":{"name":"BGKDI","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Immobile in the gas phase (Non-wetting relative permeability equals zero)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FGKDM":{"name":"FGKDM","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mobile in the gas phase (Non-wetting relative permeability greater than zero)","parameters":[],"example":"","size_kind":"none"},"RGKDM":{"name":"RGKDM","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mobile in the gas phase (Non-wetting relative permeability greater than zero)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BGKDM":{"name":"BGKDM","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Mobile in the gas phase (Non-wetting relative permeability greater than zero)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FWCD":{"name":"FWCD","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Dissolved in the water phase","parameters":[],"example":"","size_kind":"none"},"RWCD":{"name":"RWCD","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Dissolved in the water phase","parameters":[],"example":"","size_kind":"array","optional_body":true},"BWCD":{"name":"BWCD","sections":["SUMMARY"],"supported":null,"summary":"CO2/H2 Dissolved in the water phase","parameters":[],"example":"","size_kind":"array","optional_body":true},"FWIPG":{"name":"FWIPG","sections":["SUMMARY"],"supported":null,"summary":"Water in the gas phase","parameters":[],"example":"","size_kind":"none"},"RWIPG":{"name":"RWIPG","sections":["SUMMARY"],"supported":null,"summary":"Water in the gas phase","parameters":[],"example":"","size_kind":"array","optional_body":true},"BWIPG":{"name":"BWIPG","sections":["SUMMARY"],"supported":null,"summary":"Water in the gas phase","parameters":[],"example":"","size_kind":"array","optional_body":true},"FWIPL":{"name":"FWIPL","sections":["SUMMARY"],"supported":null,"summary":"Water in the water phase","parameters":[],"example":"","size_kind":"none"},"RWIPL":{"name":"RWIPL","sections":["SUMMARY"],"supported":null,"summary":"Water in the water phase","parameters":[],"example":"","size_kind":"array","optional_body":true},"BWIPL":{"name":"BWIPL","sections":["SUMMARY"],"supported":null,"summary":"Water in the water phase","parameters":[],"example":"","size_kind":"array","optional_body":true},"WINFC":{"name":"WINFC","sections":["SUMMARY"],"supported":null,"summary":"Filtrate Injection Concentration","parameters":[],"example":"","size_kind":"array","optional_body":true},"WINJFVR":{"name":"WINJFVR","sections":["SUMMARY"],"supported":null,"summary":"Filtrate Volume Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"CINJFVR":{"name":"CINJFVR","sections":["SUMMARY"],"supported":null,"summary":"Filtrate Volume Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WINJFVT":{"name":"WINJFVT","sections":["SUMMARY"],"supported":null,"summary":"Filtrate Volume Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CINJFVT":{"name":"CINJFVT","sections":["SUMMARY"],"supported":null,"summary":"Filtrate Volume Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CFCAOF":{"name":"CFCAOF","sections":["SUMMARY"],"supported":null,"summary":"Filter Cake Area Of Flow","parameters":[],"example":"","size_kind":"array","optional_body":true},"CFCPERM":{"name":"CFCPERM","sections":["SUMMARY"],"supported":null,"summary":"Filter Cake Permeability","parameters":[],"example":"","size_kind":"array","optional_body":true},"CFCPORO":{"name":"CFCPORO","sections":["SUMMARY"],"supported":null,"summary":"Filter Cake Porosity","parameters":[],"example":"","size_kind":"array","optional_body":true},"CFCRAD":{"name":"CFCRAD","sections":["SUMMARY"],"supported":null,"summary":"Filter Cake Radius","parameters":[],"example":"","size_kind":"array","optional_body":true},"CFCSKIN":{"name":"CFCSKIN","sections":["SUMMARY"],"supported":null,"summary":"Filter Cake Skin","parameters":[],"example":"","size_kind":"array","optional_body":true},"CFCWIDTH":{"name":"CFCWIDTH","sections":["SUMMARY"],"supported":null,"summary":"Filter Cake Width","parameters":[],"example":"","size_kind":"array","optional_body":true},"CTFRFOA":{"name":"CTFRFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Flow Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FTIRFOA":{"name":"FTIRFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Injection Rate","parameters":[],"example":"","size_kind":"none"},"GTIRFOA":{"name":"GTIRFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WTIRFOA":{"name":"WTIRFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FTITFOA":{"name":"FTITFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Injection Total","parameters":[],"example":"","size_kind":"none"},"GTITFOA":{"name":"GTITFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"WTITFOA":{"name":"WTITFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CTITFOA":{"name":"CTITFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"FTPRFOA":{"name":"FTPRFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Production Rate","parameters":[],"example":"","size_kind":"none"},"GTPRFOA":{"name":"GTPRFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WTPRFOA":{"name":"WTPRFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FTPTFOA":{"name":"FTPTFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Production Total","parameters":[],"example":"","size_kind":"none"},"GTPTFOA":{"name":"GTPTFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"WTPTFOA":{"name":"WTPTFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CTPTFOA":{"name":"CTPTFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"FTADSFOA":{"name":"FTADSFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Adsorption Total. Block is current value.","parameters":[],"example":"","size_kind":"none"},"CTADSFOA":{"name":"CTADSFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Adsorption Total. Block is current value.","parameters":[],"example":"","size_kind":"array","optional_body":true},"RTADSFOA":{"name":"RTADSFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Adsorption Total. Block is current value.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BTADSFOA":{"name":"BTADSFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Adsorption Total. Block is current value.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BTCNMFOA":{"name":"BTCNMFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Capillary Number","parameters":[],"example":"","size_kind":"array","optional_body":true},"BTHLFFOA":{"name":"BTHLFFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Decayed Half Life","parameters":[],"example":"","size_kind":"array","optional_body":true},"FTDCYFOA":{"name":"FTDCYFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Decayed Tracer","parameters":[],"example":"","size_kind":"none"},"RTDCYFOA":{"name":"RTDCYFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Decayed Tracer","parameters":[],"example":"","size_kind":"array","optional_body":true},"BTDCYFOA":{"name":"BTDCYFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Decayed Tracer","parameters":[],"example":"","size_kind":"array","optional_body":true},"FTMOBFOA":{"name":"FTMOBFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Gas Mobility Factor. Excluding shear.","parameters":[],"example":"","size_kind":"none"},"FTIPTFOA":{"name":"FTIPTFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam in Solution","parameters":[],"example":"","size_kind":"none"},"CTIPTFOA":{"name":"CTIPTFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam in Solution","parameters":[],"example":"","size_kind":"array","optional_body":true},"RTIPTFOA":{"name":"RTIPTFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam in Solution","parameters":[],"example":"","size_kind":"array","optional_body":true},"BTIPTFOA":{"name":"BTIPTFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam in Solution","parameters":[],"example":"","size_kind":"array","optional_body":true},"BTCNFFOA":{"name":"BTCNFFOA","sections":["SUMMARY"],"supported":null,"summary":"Foam Concentration","parameters":[],"example":"","size_kind":"array","optional_body":true},"WOGLR":{"name":"WOGLR","sections":["SUMMARY"],"supported":null,"summary":"Incremental oil rate per unit of incremental gas lift gas quantity, that is the well’s gradient as defined by equation (11.2.7)below","parameters":[],"example":"","size_kind":"array","optional_body":true},"FMMIR":{"name":"FMMIR","sections":["SUMMARY"],"supported":null,"summary":"Microbial Mass Injection Rate","parameters":[],"example":"","size_kind":"none"},"GMMIR":{"name":"GMMIR","sections":["SUMMARY"],"supported":null,"summary":"Microbial Mass Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WMMIR":{"name":"WMMIR","sections":["SUMMARY"],"supported":null,"summary":"Microbial Mass Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"CMMIR":{"name":"CMMIR","sections":["SUMMARY"],"supported":null,"summary":"Microbial Mass Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"CMMIRL":{"name":"CMMIRL","sections":["SUMMARY"],"supported":null,"summary":"Microbial Mass Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FMOIR":{"name":"FMOIR","sections":["SUMMARY"],"supported":null,"summary":"Oxygen Mass Injection Rate","parameters":[],"example":"","size_kind":"none"},"GMOIR":{"name":"GMOIR","sections":["SUMMARY"],"supported":null,"summary":"Oxygen Mass Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WMOIR":{"name":"WMOIR","sections":["SUMMARY"],"supported":null,"summary":"Oxygen Mass Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"CMOIR":{"name":"CMOIR","sections":["SUMMARY"],"supported":null,"summary":"Oxygen Mass Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"CMOIRL":{"name":"CMOIRL","sections":["SUMMARY"],"supported":null,"summary":"Oxygen Mass Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FMUIR":{"name":"FMUIR","sections":["SUMMARY"],"supported":null,"summary":"Urea Mass Injection Rate","parameters":[],"example":"","size_kind":"none"},"GMUIR":{"name":"GMUIR","sections":["SUMMARY"],"supported":null,"summary":"Urea Mass Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WMUIR":{"name":"WMUIR","sections":["SUMMARY"],"supported":null,"summary":"Urea Mass Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"CMUIR":{"name":"CMUIR","sections":["SUMMARY"],"supported":null,"summary":"Urea Mass Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"CMUIRL":{"name":"CMUIRL","sections":["SUMMARY"],"supported":null,"summary":"Urea Mass Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FMMIT":{"name":"FMMIT","sections":["SUMMARY"],"supported":null,"summary":"Microbial Mass Injection Total","parameters":[],"example":"","size_kind":"none"},"GMMIT":{"name":"GMMIT","sections":["SUMMARY"],"supported":null,"summary":"Microbial Mass Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"WMMIT":{"name":"WMMIT","sections":["SUMMARY"],"supported":null,"summary":"Microbial Mass Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CMMIT":{"name":"CMMIT","sections":["SUMMARY"],"supported":null,"summary":"Microbial Mass Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CMMITL":{"name":"CMMITL","sections":["SUMMARY"],"supported":null,"summary":"Microbial Mass Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"FMOIT":{"name":"FMOIT","sections":["SUMMARY"],"supported":null,"summary":"Oxygen Mass Injection Total","parameters":[],"example":"","size_kind":"none"},"GMOIT":{"name":"GMOIT","sections":["SUMMARY"],"supported":null,"summary":"Oxygen Mass Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"WMOIT":{"name":"WMOIT","sections":["SUMMARY"],"supported":null,"summary":"Oxygen Mass Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CMOIT":{"name":"CMOIT","sections":["SUMMARY"],"supported":null,"summary":"Oxygen Mass Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CMOITL":{"name":"CMOITL","sections":["SUMMARY"],"supported":null,"summary":"Oxygen Mass Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"FMUIT":{"name":"FMUIT","sections":["SUMMARY"],"supported":null,"summary":"Urea Mass Injection Total","parameters":[],"example":"","size_kind":"none"},"GMUIT":{"name":"GMUIT","sections":["SUMMARY"],"supported":null,"summary":"Urea Mass Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"WMUIT":{"name":"WMUIT","sections":["SUMMARY"],"supported":null,"summary":"Urea Mass Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CMUIT":{"name":"CMUIT","sections":["SUMMARY"],"supported":null,"summary":"Urea Mass Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CMUITL":{"name":"CMUITL","sections":["SUMMARY"],"supported":null,"summary":"Urea Mass Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"FMMPR":{"name":"FMMPR","sections":["SUMMARY"],"supported":null,"summary":"Microbial Mass Production Rate","parameters":[],"example":"","size_kind":"none"},"GMMPR":{"name":"GMMPR","sections":["SUMMARY"],"supported":null,"summary":"Microbial Mass Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WMMPR":{"name":"WMMPR","sections":["SUMMARY"],"supported":null,"summary":"Microbial Mass Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"CMMPR":{"name":"CMMPR","sections":["SUMMARY"],"supported":null,"summary":"Microbial Mass Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"CMMPRL":{"name":"CMMPRL","sections":["SUMMARY"],"supported":null,"summary":"Microbial Mass Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FMOPR":{"name":"FMOPR","sections":["SUMMARY"],"supported":null,"summary":"Oxygen Mass Production Rate","parameters":[],"example":"","size_kind":"none"},"GMOPR":{"name":"GMOPR","sections":["SUMMARY"],"supported":null,"summary":"Oxygen Mass Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WMOPR":{"name":"WMOPR","sections":["SUMMARY"],"supported":null,"summary":"Oxygen Mass Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"CMOPR":{"name":"CMOPR","sections":["SUMMARY"],"supported":null,"summary":"Oxygen Mass Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"CMOPRL":{"name":"CMOPRL","sections":["SUMMARY"],"supported":null,"summary":"Oxygen Mass Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FMUPR":{"name":"FMUPR","sections":["SUMMARY"],"supported":null,"summary":"Urea Mass Production Rate","parameters":[],"example":"","size_kind":"none"},"GMUPR":{"name":"GMUPR","sections":["SUMMARY"],"supported":null,"summary":"Urea Mass Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WMUPR":{"name":"WMUPR","sections":["SUMMARY"],"supported":null,"summary":"Urea Mass Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"CMUPR":{"name":"CMUPR","sections":["SUMMARY"],"supported":null,"summary":"Urea Mass Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"CMUPRL":{"name":"CMUPRL","sections":["SUMMARY"],"supported":null,"summary":"Urea Mass Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FMMPT":{"name":"FMMPT","sections":["SUMMARY"],"supported":null,"summary":"Microbial Mass Production Total","parameters":[],"example":"","size_kind":"none"},"GMMPT":{"name":"GMMPT","sections":["SUMMARY"],"supported":null,"summary":"Microbial Mass Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"WMMPT":{"name":"WMMPT","sections":["SUMMARY"],"supported":null,"summary":"Microbial Mass Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CMMPT":{"name":"CMMPT","sections":["SUMMARY"],"supported":null,"summary":"Microbial Mass Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CMMPTL":{"name":"CMMPTL","sections":["SUMMARY"],"supported":null,"summary":"Microbial Mass Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"FMOPT":{"name":"FMOPT","sections":["SUMMARY"],"supported":null,"summary":"Oxygen Mass Production Total","parameters":[],"example":"","size_kind":"none"},"GMOPT":{"name":"GMOPT","sections":["SUMMARY"],"supported":null,"summary":"Oxygen Mass Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"WMOPT":{"name":"WMOPT","sections":["SUMMARY"],"supported":null,"summary":"Oxygen Mass Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CMOPT":{"name":"CMOPT","sections":["SUMMARY"],"supported":null,"summary":"Oxygen Mass Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CMOPTL":{"name":"CMOPTL","sections":["SUMMARY"],"supported":null,"summary":"Oxygen Mass Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"FMUPT":{"name":"FMUPT","sections":["SUMMARY"],"supported":null,"summary":"Urea Mass Production Total","parameters":[],"example":"","size_kind":"none"},"GMUPT":{"name":"GMUPT","sections":["SUMMARY"],"supported":null,"summary":"Urea Mass Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"WMUPT":{"name":"WMUPT","sections":["SUMMARY"],"supported":null,"summary":"Urea Mass Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CMUPT":{"name":"CMUPT","sections":["SUMMARY"],"supported":null,"summary":"Urea Mass Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CMUPTL":{"name":"CMUPTL","sections":["SUMMARY"],"supported":null,"summary":"Urea Mass Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"FMMIP":{"name":"FMMIP","sections":["SUMMARY"],"supported":null,"summary":"Microbes In-place","parameters":[],"example":"","size_kind":"none"},"RMMIP":{"name":"RMMIP","sections":["SUMMARY"],"supported":null,"summary":"Microbes In-place","parameters":[],"example":"","size_kind":"array","optional_body":true},"BMMIP":{"name":"BMMIP","sections":["SUMMARY"],"supported":null,"summary":"Microbes In-place","parameters":[],"example":"","size_kind":"array","optional_body":true},"FMOIP":{"name":"FMOIP","sections":["SUMMARY"],"supported":null,"summary":"Oxygen In-place","parameters":[],"example":"","size_kind":"none"},"RMOIP":{"name":"RMOIP","sections":["SUMMARY"],"supported":null,"summary":"Oxygen In-place","parameters":[],"example":"","size_kind":"array","optional_body":true},"BMOIP":{"name":"BMOIP","sections":["SUMMARY"],"supported":null,"summary":"Oxygen In-place","parameters":[],"example":"","size_kind":"array","optional_body":true},"FMUIP":{"name":"FMUIP","sections":["SUMMARY"],"supported":null,"summary":"Urea In-place","parameters":[],"example":"","size_kind":"none"},"RMUIP":{"name":"RMUIP","sections":["SUMMARY"],"supported":null,"summary":"Urea In-place","parameters":[],"example":"","size_kind":"array","optional_body":true},"BMUIP":{"name":"BMUIP","sections":["SUMMARY"],"supported":null,"summary":"Urea In-place","parameters":[],"example":"","size_kind":"array","optional_body":true},"FMBIP":{"name":"FMBIP","sections":["SUMMARY"],"supported":null,"summary":"Biofilm In-place","parameters":[],"example":"","size_kind":"none"},"RMBIP":{"name":"RMBIP","sections":["SUMMARY"],"supported":null,"summary":"Biofilm In-place","parameters":[],"example":"","size_kind":"array","optional_body":true},"BMBIP":{"name":"BMBIP","sections":["SUMMARY"],"supported":null,"summary":"Biofilm In-place","parameters":[],"example":"","size_kind":"array","optional_body":true},"FMCIP":{"name":"FMCIP","sections":["SUMMARY"],"supported":null,"summary":"Calcite In-place","parameters":[],"example":"","size_kind":"none"},"RMCIP":{"name":"RMCIP","sections":["SUMMARY"],"supported":null,"summary":"Calcite In-place","parameters":[],"example":"","size_kind":"array","optional_body":true},"BMCIP":{"name":"BMCIP","sections":["SUMMARY"],"supported":null,"summary":"Calcite In-place","parameters":[],"example":"","size_kind":"array","optional_body":true},"SALQ":{"name":"SALQ","sections":["SUMMARY"],"supported":null,"summary":"Artificial Lift Quantity. See keyword WSEGTABL.","parameters":[],"example":"","size_kind":"array","optional_body":true},"SFR":{"name":"SFR","sections":["SUMMARY"],"supported":null,"summary":"Brine Flow Rate. Surfactant and Polymer model.","parameters":[],"example":"","size_kind":"array","optional_body":true},"SGFR":{"name":"SGFR","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"SGFRF":{"name":"SGFRF","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow Rate (Free)","parameters":[],"example":"","size_kind":"array","optional_body":true},"SGFRS":{"name":"SGFRS","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow Rate (Solution)","parameters":[],"example":"","size_kind":"array","optional_body":true},"SGFTA":{"name":"SGFTA","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow Total (Absolute)","parameters":[],"example":"","size_kind":"array","optional_body":true},"SGFT":{"name":"SGFT","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"SGFV":{"name":"SGFV","sections":["SUMMARY"],"supported":null,"summary":"Gas Flow Velocity","parameters":[],"example":"","size_kind":"array","optional_body":true},"SGHF":{"name":"SGHF","sections":["SUMMARY"],"supported":null,"summary":"Gas Holdup Fraction","parameters":[],"example":"","size_kind":"array","optional_body":true},"SGIMR":{"name":"SGIMR","sections":["SUMMARY"],"supported":null,"summary":"Gas Import Rate. See keyword WSEGEXSS.","parameters":[],"example":"","size_kind":"array","optional_body":true},"SGIMT":{"name":"SGIMT","sections":["SUMMARY"],"supported":null,"summary":"Gas Import Total. See keyword WSEGEXSS.","parameters":[],"example":"","size_kind":"array","optional_body":true},"SOFTA":{"name":"SOFTA","sections":["SUMMARY"],"supported":null,"summary":"Oil Absolute Flow Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"SOFR":{"name":"SOFR","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"SOFRF":{"name":"SOFRF","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow Rate (Free)","parameters":[],"example":"","size_kind":"array","optional_body":true},"SOFRS":{"name":"SOFRS","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow Rate (Solution)","parameters":[],"example":"","size_kind":"array","optional_body":true},"SOFT":{"name":"SOFT","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"SOFV":{"name":"SOFV","sections":["SUMMARY"],"supported":null,"summary":"Oil Flow Velocity","parameters":[],"example":"","size_kind":"array","optional_body":true},"SOHF":{"name":"SOHF","sections":["SUMMARY"],"supported":null,"summary":"Oil Holdup Fraction","parameters":[],"example":"","size_kind":"array","optional_body":true},"SCFR":{"name":"SCFR","sections":["SUMMARY"],"supported":null,"summary":"Polymer Flow Rate. Polymer model.","parameters":[],"example":"","size_kind":"array","optional_body":true},"STFR":{"name":"STFR","sections":["SUMMARY"],"supported":null,"summary":"Tracer Flow Rate. Tracer model.","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"SWFR":{"name":"SWFR","sections":["SUMMARY"],"supported":null,"summary":"Water Flow Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"SWFT":{"name":"SWFT","sections":["SUMMARY"],"supported":null,"summary":"Water Flow Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"SWFTA":{"name":"SWFTA","sections":["SUMMARY"],"supported":null,"summary":"Water Flow Total (Absolute)","parameters":[],"example":"","size_kind":"array","optional_body":true},"SWFV":{"name":"SWFV","sections":["SUMMARY"],"supported":null,"summary":"Water Flow Velocity","parameters":[],"example":"","size_kind":"array","optional_body":true},"SWHF":{"name":"SWHF","sections":["SUMMARY"],"supported":null,"summary":"Water Holdup Fraction","parameters":[],"example":"","size_kind":"array","optional_body":true},"SWIMR":{"name":"SWIMR","sections":["SUMMARY"],"supported":null,"summary":"Water Import Rate. See keyword WSEGEXSS.","parameters":[],"example":"","size_kind":"array","optional_body":true},"SWIMT":{"name":"SWIMT","sections":["SUMMARY"],"supported":null,"summary":"Water Import Total. See keyword WSEGEXSS.","parameters":[],"example":"","size_kind":"array","optional_body":true},"SPR":{"name":"SPR","sections":["SUMMARY"],"supported":null,"summary":"Pressure","parameters":[],"example":"","size_kind":"array","optional_body":true},"SPRD":{"name":"SPRD","sections":["SUMMARY"],"supported":null,"summary":"Pressure Drop","parameters":[],"example":"","size_kind":"array","optional_body":true},"SPRDF":{"name":"SPRDF","sections":["SUMMARY"],"supported":null,"summary":"Pressure Drop Component due to Friction","parameters":[],"example":"","size_kind":"array","optional_body":true},"SPRDH":{"name":"SPRDH","sections":["SUMMARY"],"supported":null,"summary":"Pressure Drop Component due to Hydrostatic head","parameters":[],"example":"","size_kind":"array","optional_body":true},"SPRDA":{"name":"SPRDA","sections":["SUMMARY"],"supported":null,"summary":"Pressure Drop due to Acceleration head","parameters":[],"example":"","size_kind":"array","optional_body":true},"SPRDM":{"name":"SPRDM","sections":["SUMMARY"],"supported":null,"summary":"Pressure Drop Frictional Multiplier. See keyword WSEGMULT.","parameters":[],"example":"","size_kind":"array","optional_body":true},"SAPI":{"name":"SAPI","sections":["SUMMARY"],"supported":null,"summary":"API. API model.","parameters":[],"example":"","size_kind":"array","optional_body":true},"SDENM":{"name":"SDENM","sections":["SUMMARY"],"supported":null,"summary":"Fluid Mixture Density (Excludes Exponents). Excludes exponents of flowing fractions.","parameters":[],"example":"","size_kind":"array","optional_body":true},"SMDEN":{"name":"SMDEN","sections":["SUMMARY"],"supported":null,"summary":"Fluid Mixture Density (Includes Exponents). Includes exponents of flowing fractions.","parameters":[],"example":"","size_kind":"array","optional_body":true},"SMVIS":{"name":"SMVIS","sections":["SUMMARY"],"supported":null,"summary":"Fluid Mixture Viscosity (Includes Exponents). Includes exponents of flowing fractions.","parameters":[],"example":"","size_kind":"array","optional_body":true},"SEMVIS":{"name":"SEMVIS","sections":["SUMMARY"],"supported":null,"summary":"Fluid Viscosity (Effective Mixture). Water/polymer fluid.","parameters":[],"example":"","size_kind":"array","optional_body":true},"SGDEN":{"name":"SGDEN","sections":["SUMMARY"],"supported":null,"summary":"Gas Density","parameters":[],"example":"","size_kind":"array","optional_body":true},"SGVIS":{"name":"SGVIS","sections":["SUMMARY"],"supported":null,"summary":"Gas Viscosity","parameters":[],"example":"","size_kind":"array","optional_body":true},"SGLVD":{"name":"SGLVD","sections":["SUMMARY"],"supported":null,"summary":"Gas-Liquid Drift Velocity (Vd). Drift flux slip model.","parameters":[],"example":"","size_kind":"array","optional_body":true},"SGLPP":{"name":"SGLPP","sections":["SUMMARY"],"supported":null,"summary":"Gas-Liquid Profile Parameter (C0). Drift flux slip model.","parameters":[],"example":"","size_kind":"array","optional_body":true},"SODEN":{"name":"SODEN","sections":["SUMMARY"],"supported":null,"summary":"Oil Density","parameters":[],"example":"","size_kind":"array","optional_body":true},"SOVIS":{"name":"SOVIS","sections":["SUMMARY"],"supported":null,"summary":"Oil Viscosity","parameters":[],"example":"","size_kind":"array","optional_body":true},"SOWVD":{"name":"SOWVD","sections":["SUMMARY"],"supported":null,"summary":"Oil-Water Drift Velocity (Vd). Drift flux slip model.","parameters":[],"example":"","size_kind":"array","optional_body":true},"SOWPP":{"name":"SOWPP","sections":["SUMMARY"],"supported":null,"summary":"Oil-Water Profile Parameter (C0). Drift flux slip model.","parameters":[],"example":"","size_kind":"array","optional_body":true},"SPPOW":{"name":"SPPOW","sections":["SUMMARY"],"supported":null,"summary":"Pump Working Power. See keyword WSEGPULL.","parameters":[],"example":"","size_kind":"array","optional_body":true},"SFD":{"name":"SFD","sections":["SUMMARY"],"supported":null,"summary":"Scale Deposition Diameter (Karst Conduit Calcite Dissolution). Scale Deposition model.","parameters":[],"example":"","size_kind":"array","optional_body":true},"SFOPN":{"name":"SFOPN","sections":["SUMMARY"],"supported":null,"summary":"Setting of Segment. See keywords WSEGVALV, WSEGAICD, WSEGSICD, WSEGTABL, WSEGLABY, and WSEGFLIM.","parameters":[],"example":"","size_kind":"array","optional_body":true},"SSTR":{"name":"SSTR","sections":["SUMMARY"],"supported":null,"summary":"Strength of ICD on Segment. See keywords WSEGVALV, WSEGAICD, and WSEGSICD.","parameters":[],"example":"","size_kind":"array","optional_body":true},"SWDEN":{"name":"SWDEN","sections":["SUMMARY"],"supported":null,"summary":"Water Density (Pure Water)","parameters":[],"example":"","size_kind":"array","optional_body":true},"SWVIS":{"name":"SWVIS","sections":["SUMMARY"],"supported":null,"summary":"Water Viscosity (Pure Water)","parameters":[],"example":"","size_kind":"array","optional_body":true},"SGOR":{"name":"SGOR","sections":["SUMMARY"],"supported":null,"summary":"Gas-Oil Ratio","parameters":[],"example":"","size_kind":"array","optional_body":true},"SOGR":{"name":"SOGR","sections":["SUMMARY"],"supported":null,"summary":"Oil-Gas Ratio","parameters":[],"example":"","size_kind":"array","optional_body":true},"SWCT":{"name":"SWCT","sections":["SUMMARY"],"supported":null,"summary":"Water Cut","parameters":[],"example":"","size_kind":"array","optional_body":true},"SWGR":{"name":"SWGR","sections":["SUMMARY"],"supported":null,"summary":"Water Gas Ratio","parameters":[],"example":"","size_kind":"array","optional_body":true},"SSCN":{"name":"SSCN","sections":["SUMMARY"],"supported":null,"summary":"Brine Concentration. Surfactant and Polymer model","parameters":[],"example":"","size_kind":"array","optional_body":true},"SCCN":{"name":"SCCN","sections":["SUMMARY"],"supported":null,"summary":"Polymer Concentration. Polymer model","parameters":[],"example":"","size_kind":"array","optional_body":true},"STFC":{"name":"STFC","sections":["SUMMARY"],"supported":null,"summary":"Tracer Concentration. Tracer model","parameters":[],"example":"","size_kind":"array","templated":true,"optional_body":true},"GNETPR":{"name":"GNETPR","sections":["SUMMARY"],"supported":null,"summary":"Group/Node pressure in a production network based on rates at end of timestep (OPM Flow specific). An alias for NPR.","parameters":[],"example":"","size_kind":"array","optional_body":true},"GPR":{"name":"GPR","sections":["SUMMARY"],"supported":null,"summary":"Group/Node pressure in a production network.","parameters":[],"example":"","size_kind":"array","optional_body":true},"GPRG":{"name":"GPRG","sections":["SUMMARY"],"supported":null,"summary":"Group /Node pressure in a gas injection network.","parameters":[],"example":"","size_kind":"array","optional_body":true},"GPRW":{"name":"GPRW","sections":["SUMMARY"],"supported":null,"summary":"Group/Node pressure in a water injection network.","parameters":[],"example":"","size_kind":"array","optional_body":true},"GPRB":{"name":"GPRB","sections":["SUMMARY"],"supported":null,"summary":"Pressure drop along the group’s or node’s outlet branch in a production network.","parameters":[],"example":"","size_kind":"array","optional_body":true},"GPRBG":{"name":"GPRBG","sections":["SUMMARY"],"supported":null,"summary":"Pressure drop along the group’s or node’s inlet branch in a gas injection network.","parameters":[],"example":"","size_kind":"array","optional_body":true},"GPRBW":{"name":"GPRBW","sections":["SUMMARY"],"supported":null,"summary":"Pressure drop along the group’s or node’s inlet branch in a water injection network.","parameters":[],"example":"","size_kind":"array","optional_body":true},"NPR":{"name":"NPR","sections":["SUMMARY"],"supported":null,"summary":"Group/Node pressure in a production network based on rates at end of timestep (OPM Flow specific).","parameters":[],"example":"","size_kind":"array","optional_body":true},"GALQ":{"name":"GALQ","sections":["SUMMARY"],"supported":null,"summary":"Artificial Lift Quantity (“ALQ”) in the group’s or node’s outlet branch in a production network. Note no units are stated as ALQ units are variable, for example Hz for ESP or rate for gas lift gas.","parameters":[],"example":"","size_kind":"array","optional_body":true},"GOPRNB":{"name":"GOPRNB","sections":["SUMMARY"],"supported":null,"summary":"Oil flow rate along the group’s or node’s outlet branch in a production network.","parameters":[],"example":"","size_kind":"array","optional_body":true},"GWPRNB":{"name":"GWPRNB","sections":["SUMMARY"],"supported":null,"summary":"Water flow rate along the group’s or node’s outlet branch in a production network.","parameters":[],"example":"","size_kind":"array","optional_body":true},"GGPRNB":{"name":"GGPRNB","sections":["SUMMARY"],"supported":null,"summary":"Gas flow rate along the group’s or node’s outlet branch in a production network.","parameters":[],"example":"","size_kind":"array","optional_body":true},"GLPRNB":{"name":"GLPRNB","sections":["SUMMARY"],"supported":null,"summary":"Liquid flow rate along the group’s or node’s outlet branch in a production network.","parameters":[],"example":"","size_kind":"array","optional_body":true},"GWIRNB":{"name":"GWIRNB","sections":["SUMMARY"],"supported":null,"summary":"Water flow rate along the group’s or node’s inlet branch in water injection network.","parameters":[],"example":"","size_kind":"array","optional_body":true},"GGIRNB":{"name":"GGIRNB","sections":["SUMMARY"],"supported":null,"summary":"Gas flow rate along the group’s or node’s inlet branch in gas injection network.","parameters":[],"example":"","size_kind":"array","optional_body":true},"DTMWAIT":{"name":"DTMWAIT","sections":["SUMMARY"],"supported":null,"summary":"Elapsed - Cumulative waiting time per process in seconds.","parameters":[],"example":"","size_kind":"none"},"ELAPSED":{"name":"ELAPSED","sections":["SUMMARY"],"supported":null,"summary":"Elapsed - Elapsed time in seconds.","parameters":[],"example":"","size_kind":"none"},"HLINEARS":{"name":"HLINEARS","sections":["SUMMARY"],"supported":null,"summary":"Iterations - Number of linear iterations for each gradient calculation (Gradient Option).","parameters":[],"example":"","size_kind":"none"},"HSUMLINS":{"name":"HSUMLINS","sections":["SUMMARY"],"supported":null,"summary":"Iterations - Total number of linear iterations for each gradient pressure (Gradient Option).","parameters":[],"example":"","size_kind":"none"},"MAXCFL":{"name":"MAXCFL","sections":["SUMMARY"],"supported":null,"summary":"Maximum Courant-Friedrichs-Lewy value for each time step. (Compositional keyword.)","parameters":[],"example":"","size_kind":"none"},"MAXDE":{"name":"MAXDE","sections":["SUMMARY"],"supported":null,"summary":"Maximum variation in energy for each time step. (Compositional keyword.)","parameters":[],"example":"","size_kind":"none"},"MAXDPR":{"name":"MAXDPR","sections":["SUMMARY"],"supported":null,"summary":"Maximum variation in pressure for each time step.","parameters":[],"example":"","size_kind":"none"},"MAXDSG":{"name":"MAXDSG","sections":["SUMMARY"],"supported":null,"summary":"Maximum variation in gas saturation for each time step.","parameters":[],"example":"","size_kind":"none"},"MAXDSO":{"name":"MAXDSO","sections":["SUMMARY"],"supported":null,"summary":"Maximum variation in oil saturation for each time step.","parameters":[],"example":"","size_kind":"none"},"MAXDSW":{"name":"MAXDSW","sections":["SUMMARY"],"supported":null,"summary":"Maximum variation in water saturation for each time step.","parameters":[],"example":"","size_kind":"none"},"MAXDT":{"name":"MAXDT","sections":["SUMMARY"],"supported":null,"summary":"Maximum variation in temperature for each time step. (Compositional keyword.)","parameters":[],"example":"","size_kind":"none"},"MEMORYTS":{"name":"MEMORYTS","sections":["SUMMARY"],"supported":null,"summary":"Memory - Operating system reported maximum current memory usage across all processors.","parameters":[],"example":"","size_kind":"none"},"MLINEARP":{"name":"MLINEARP","sections":["SUMMARY"],"supported":null,"summary":"CPR Solver - Number of pressure iterations for each time step.","parameters":[],"example":"","size_kind":"none"},"MLINEARS":{"name":"MLINEARS","sections":["SUMMARY"],"supported":null,"summary":"Iterations - Number of linear iterations for each time step.","parameters":[],"example":"","size_kind":"none"},"MSUMBUG":{"name":"MSUMBUG","sections":["SUMMARY"],"supported":null,"summary":"Messages - Cumulative number of BUG messages.","parameters":[],"example":"","size_kind":"none"},"MSUMCOMM":{"name":"MSUMCOMM","sections":["SUMMARY"],"supported":null,"summary":"Messages - Cumulative number of COMMENT messages.","parameters":[],"example":"","size_kind":"none"},"MSUMERR":{"name":"MSUMERR","sections":["SUMMARY"],"supported":null,"summary":"Messages - Cumulative number of ERROR messages.","parameters":[],"example":"","size_kind":"none"},"MSUMLINP":{"name":"MSUMLINP","sections":["SUMMARY"],"supported":null,"summary":"CPR Solver - Cumulative number of pressure iterations.","parameters":[],"example":"","size_kind":"none"},"MSUMLINS":{"name":"MSUMLINS","sections":["SUMMARY"],"supported":null,"summary":"Iterations - Cumulative number of linear iterations.","parameters":[],"example":"","size_kind":"none"},"MSUMMESS":{"name":"MSUMMESS","sections":["SUMMARY"],"supported":null,"summary":"Messages - Cumulative number of MESSAGES messages.","parameters":[],"example":"","size_kind":"none"},"MSUMNEWT":{"name":"MSUMNEWT","sections":["SUMMARY"],"supported":null,"summary":"Iterations - Cumulative number of Newton iterations.","parameters":[],"example":"","size_kind":"none"},"MSUMPROB":{"name":"MSUMPROB","sections":["SUMMARY"],"supported":null,"summary":"Messages - Cumulative number of PROBLEM messages.","parameters":[],"example":"","size_kind":"none"},"MSUMWARN":{"name":"MSUMWARN","sections":["SUMMARY"],"supported":null,"summary":"Messages - Cumulative number of WARNING messages.","parameters":[],"example":"","size_kind":"none"},"NBAKFL":{"name":"NBAKFL","sections":["SUMMARY"],"supported":null,"summary":"Number of flash calculations for each time step (Compositional keyword.)","parameters":[],"example":"","size_kind":"none"},"NBYTOT":{"name":"NBYTOT","sections":["SUMMARY"],"supported":null,"summary":"Memory - Peak usage of dynamically allocated memory reported by OPM Flow. For parallel cases this is the maximum across all processors.","parameters":[],"example":"","size_kind":"none"},"NCPRLINS":{"name":"NCPRLINS","sections":["SUMMARY"],"supported":null,"summary":"CPR Solver - Average number of pressure iterations per linear iteration for each time step.","parameters":[],"example":"","size_kind":"none"},"NEWTFL":{"name":"NEWTFL","sections":["SUMMARY"],"supported":null,"summary":"Iterations – Cumulative average number of Newton iterations per cell in flash calculations.. (Compositional keyword.)","parameters":[],"example":"","size_kind":"none"},"NLINEARP":{"name":"NLINEARP","sections":["SUMMARY"],"supported":null,"summary":"CPR Solver - Average number of pressure iterations per Newton iteration per time step.","parameters":[],"example":"","size_kind":"none"},"NLINEARS":{"name":"NLINEARS","sections":["SUMMARY"],"supported":null,"summary":"Iterations - Average number of linear iterations per Newton iteration for each time step. (For runs with LGRs, LLINEARS will automatically be exported for each LGR.)","parameters":[],"example":"","size_kind":"none"},"NLINSMAX":{"name":"NLINSMAX","sections":["SUMMARY"],"supported":null,"summary":"Iterations - Maximum number of linear iterations in the Newton iterations per time step.","parameters":[],"example":"","size_kind":"none"},"NLINSMIN":{"name":"NLINSMIN","sections":["SUMMARY"],"supported":null,"summary":"Iterations - Minimum number of linear iterations in the Newton iterations per time step.","parameters":[],"example":"","size_kind":"none"},"NNUMFL":{"name":"NNUMFL","sections":["SUMMARY"],"supported":null,"summary":"Cumulative number of flash calculations. (Compositional keyword.)","parameters":[],"example":"","size_kind":"none"},"NNUMST":{"name":"NNUMST","sections":["SUMMARY"],"supported":null,"summary":"Cumulative number of stability tests. (Compositional keyword.)","parameters":[],"example":"","size_kind":"none"},"NLRESSUM":{"name":"NLRESSUM","sections":["SUMMARY"],"supported":null,"summary":"Non-linear residual total. (Compositional keyword.)","parameters":[],"example":"","size_kind":"none"},"NLRESMAX":{"name":"NLRESMAX","sections":["SUMMARY"],"supported":null,"summary":"Non-linear residual maximum value. (Compositional keyword.)","parameters":[],"example":"","size_kind":"none"},"NTS":{"name":"NTS","sections":["SUMMARY"],"supported":null,"summary":"Number of time steps – taken. (Compositional keyword.)","parameters":[],"example":"","size_kind":"none"},"NTSPCL":{"name":"NTSPCL","sections":["SUMMARY"],"supported":null,"summary":"Number of time steps – pressure converged. (Compositional keyword.)","parameters":[],"example":"","size_kind":"none"},"NTSMCL":{"name":"NTSMCL","sections":["SUMMARY"],"supported":null,"summary":"Number of time steps – molar density converged. (Compositional keyword.)","parameters":[],"example":"","size_kind":"none"},"NTSECL":{"name":"NTSECL","sections":["SUMMARY"],"supported":null,"summary":"Number of time steps – energy density converged. (Compositional keyword.)","parameters":[],"example":"","size_kind":"none"},"STEPTYPE":{"name":"STEPTYPE","sections":["SUMMARY"],"supported":null,"summary":"Time Step – Criteria used to select the length of the time step, set to one of the following:","parameters":[],"example":"","size_kind":"none"},"TRNC":{"name":"TRNC","sections":["SUMMARY"],"supported":null,"summary":"2 (Controlled via time truncation error.)","parameters":[],"example":"","size_kind":"none"},"MINF":{"name":"MINF","sections":["SUMMARY"],"supported":null,"summary":"3 (Minimum ratio between one time step and the next.)","parameters":[],"example":"","size_kind":"none"},"MAXF":{"name":"MAXF","sections":["SUMMARY"],"supported":null,"summary":"4 (Maximum ratio between one time step and the next.)","parameters":[],"example":"","size_kind":"none"},"MINS":{"name":"MINS","sections":["SUMMARY"],"supported":null,"summary":"5 (Minimum permitted time step.)","parameters":[],"example":"","size_kind":"none"},"MAXS":{"name":"MAXS","sections":["SUMMARY"],"supported":null,"summary":"6 (Maximum permitted time step.)","parameters":[],"example":"","size_kind":"none"},"REPT":{"name":"REPT","sections":["SUMMARY"],"supported":null,"summary":"7 (Report time step.)","parameters":[],"example":"","size_kind":"none"},"HALF":{"name":"HALF","sections":["SUMMARY"],"supported":null,"summary":"8 (Half of the time set to reach the next report time step.)","parameters":[],"example":"","size_kind":"none"},"CHOP":{"name":"CHOP","sections":["SUMMARY"],"supported":null,"summary":"9 (Time step chopped due non-convergence of non-linear equations.)","parameters":[],"example":"","size_kind":"none"},"SATM":{"name":"SATM","sections":["SUMMARY"],"supported":null,"summary":"10 (Maximum saturation change.)","parameters":[],"example":"","size_kind":"none"},"PCHP":{"name":"PCHP","sections":["SUMMARY"],"supported":null,"summary":"11 (Time step chopped due to maximum pressure change in IMPES formulation.)","parameters":[],"example":"","size_kind":"none"},"DIFF":{"name":"DIFF","sections":["GRID"],"supported":null,"summary":"12 (Difficult time step after a time step CHOP.)","parameters":[],"example":"","size_kind":"array"},"LGRC":{"name":"LGRC","sections":["SUMMARY"],"supported":null,"summary":"13 (Determined by LGR fluid in-place error targets.)","parameters":[],"example":"","size_kind":"none"},"NETW":{"name":"NETW","sections":["SUMMARY"],"supported":null,"summary":"15 (Time step determined by network balancing controls.)","parameters":[],"example":"","size_kind":"none"},"THRP":{"name":"THRP","sections":["SUMMARY"],"supported":null,"summary":"16 (Time step controlled by maximum through put ratio.)","parameters":[],"example":"","size_kind":"none"},"EMTH":{"name":"EMTH","sections":["SUMMARY"],"supported":null,"summary":"17 (Time step selected to match the end of a month.)","parameters":[],"example":"","size_kind":"none"},"MAXP":{"name":"MAXP","sections":["SUMMARY"],"supported":null,"summary":"18 (Set by maximum expected grid block pressure change.)","parameters":[],"example":"","size_kind":"none"},"WCYC":{"name":"WCYC","sections":["SUMMARY"],"supported":null,"summary":"19 (Determined by well cycling on/off time.)","parameters":[],"example":"","size_kind":"none"},"MAST":{"name":"MAST","sections":["SUMMARY"],"supported":null,"summary":"20 (Chosen by the master simulation in a reservoir coupling run.)","parameters":[],"example":"","size_kind":"none"},"SLVR":{"name":"SLVR","sections":["SUMMARY"],"supported":null,"summary":"21 (Selected by a slave simulation to match a slave reporting time step, in a reservoir coupling run.)","parameters":[],"example":"","size_kind":"none"},"SLVC":{"name":"SLVC","sections":["SUMMARY"],"supported":null,"summary":"22 (Time step selected by a slave simulation due to a slave’s expected flow rate change in a reservoir coupling run.)","parameters":[],"example":"","size_kind":"none"},"MAXW":{"name":"MAXW","sections":["SUMMARY"],"supported":null,"summary":"23 (Maximum time step size after a well control event.)","parameters":[],"example":"","size_kind":"none"},"EFF+":{"name":"EFF+","sections":["SUMMARY"],"supported":null,"summary":"24 (Selected by ZIPPY optimum time selection algorithm.)","parameters":[],"example":"","size_kind":"none"},"EFF-":{"name":"EFF-","sections":["SUMMARY"],"supported":null,"summary":"25","parameters":[],"example":"","size_kind":"none"},"NLTR":{"name":"NLTR","sections":["SUMMARY"],"supported":null,"summary":"26","parameters":[],"example":"","size_kind":"none"},"EFFT":{"name":"EFFT","sections":["SUMMARY"],"supported":null,"summary":"27","parameters":[],"example":"","size_kind":"none"},"DLYA":{"name":"DLYA","sections":["SUMMARY"],"supported":null,"summary":"28","parameters":[],"example":"","size_kind":"none"},"ACTN":{"name":"ACTN","sections":["SUMMARY"],"supported":null,"summary":"29","parameters":[],"example":"","size_kind":"none"},"RAIN":{"name":"RAIN","sections":["SUMMARY"],"supported":null,"summary":"30","parameters":[],"example":"","size_kind":"none"},"TCPU":{"name":"TCPU","sections":["SUMMARY"],"supported":null,"summary":"CPU - Current CPU usage in seconds. (It does not consider the time taken by inter-process communications in parallel runs, whereas ELAPSED does. Thus, for parallel jobs, ELAPSED is the most relevant time measurement.)","parameters":[],"example":"","size_kind":"none"},"TCPUDAY":{"name":"TCPUDAY","sections":["SUMMARY"],"supported":null,"summary":"CPU - CPU time per day (or hour in lab units depending on run units system).","parameters":[],"example":"","size_kind":"none"},"TCPUH":{"name":"TCPUH","sections":["SUMMARY"],"supported":null,"summary":"CPU – Cumulative CPU time for each gradient calculation (Gradient Option).","parameters":[],"example":"","size_kind":"none"},"TCPUHT":{"name":"TCPUHT","sections":["SUMMARY"],"supported":null,"summary":"CPU - Cumulative CPU time for all gradient calculations (Gradient Option).","parameters":[],"example":"","size_kind":"none"},"TCPUSCH":{"name":"TCPUSCH","sections":["SUMMARY"],"supported":null,"summary":"CPU - Cumulative CPU time used in SCHEDULE section.","parameters":[],"example":"","size_kind":"none"},"TCPUTS":{"name":"TCPUTS","sections":["SUMMARY"],"supported":null,"summary":"CPU - CPU time per time step in seconds.","parameters":[],"example":"","size_kind":"none"},"TCPUTSH":{"name":"TCPUTSH","sections":["SUMMARY"],"supported":null,"summary":"CPU - CPU time per time step for each gradient calculation (Gradient Option).","parameters":[],"example":"","size_kind":"none"},"TCPUTSHT":{"name":"TCPUTSHT","sections":["SUMMARY"],"supported":null,"summary":"CPU - CPU time per time step for all gradient calculations (Gradient Option).","parameters":[],"example":"","size_kind":"none"},"TCPUTR":{"name":"TCPUTR","sections":["SUMMARY"],"supported":null,"summary":"CPU – Cumulative Tracer CPU time. (Compositional keyword.)","parameters":[],"example":"","size_kind":"none"},"TCPUTRSV":{"name":"TCPUTRSV","sections":["SUMMARY"],"supported":null,"summary":"CPU – Cumulative Tracer implicit CPU time. (Compositional keyword.)","parameters":[],"example":"","size_kind":"none"},"TCPULGTR":{"name":"TCPULGTR","sections":["SUMMARY"],"supported":null,"summary":"CPU – Cumulative Tracer Lagrangian tracer stramline CPU time. (Compositional keyword.)","parameters":[],"example":"","size_kind":"none"},"TCPULGSV":{"name":"TCPULGSV","sections":["SUMMARY"],"supported":null,"summary":"CPU – Cumulative Tracer Lagrangian tracer solver CPU time. (Compositional keyword.)","parameters":[],"example":"","size_kind":"none"},"TELAPDAY":{"name":"TELAPDAY","sections":["SUMMARY"],"supported":null,"summary":"Elapsed - Elapsed time per day (or hour in lab units).","parameters":[],"example":"","size_kind":"none"},"TELAPLIN":{"name":"TELAPLIN","sections":["SUMMARY"],"supported":null,"summary":"Elapsed - Elapsed time per linear iteration in seconds.","parameters":[],"example":"","size_kind":"none"},"TELAPTS":{"name":"TELAPTS","sections":["SUMMARY"],"supported":null,"summary":"Elapsed - Elapsed time per time step in seconds.","parameters":[],"example":"","size_kind":"none"},"TIMESTEP":{"name":"TIMESTEP","sections":["SUMMARY"],"supported":null,"summary":"Time Step - Length of time step.","parameters":[],"example":"","size_kind":"none"},"WNEWTON":{"name":"WNEWTON","sections":["SUMMARY"],"supported":null,"summary":"Iterations - Number of well Newton iterations taken in the last global Newton iteration. A negative value indicates that the well failed to converge.","parameters":[],"example":"","size_kind":"none"},"ZIPEFF":{"name":"ZIPEFF","sections":["SUMMARY"],"supported":null,"summary":"Time Step - Predicted efficiency of the time step (developer use).","parameters":[],"example":"","size_kind":"none"},"ZIPEFFC":{"name":"ZIPEFFC","sections":["SUMMARY"],"supported":null,"summary":"Time Step - Predicted efficiency of the time step divided by the actual efficiency (developer use).","parameters":[],"example":"","size_kind":"none"},"CCFR":{"name":"CCFR","sections":["SUMMARY"],"supported":null,"summary":"Polymer Flow Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"RCFT":{"name":"RCFT","sections":["SUMMARY"],"supported":null,"summary":"Polymer Flow Total (Inter-Region)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FCIR":{"name":"FCIR","sections":["SUMMARY"],"supported":null,"summary":"Polymer Injection Rate","parameters":[],"example":"","size_kind":"none"},"GCIR":{"name":"GCIR","sections":["SUMMARY"],"supported":null,"summary":"Polymer Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WCIR":{"name":"WCIR","sections":["SUMMARY"],"supported":null,"summary":"Polymer Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"CCIR":{"name":"CCIR","sections":["SUMMARY"],"supported":null,"summary":"Polymer Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FCIT":{"name":"FCIT","sections":["SUMMARY"],"supported":null,"summary":"Polymer Injection Total","parameters":[],"example":"","size_kind":"none"},"GCIT":{"name":"GCIT","sections":["SUMMARY"],"supported":null,"summary":"Polymer Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"WCIT":{"name":"WCIT","sections":["SUMMARY"],"supported":null,"summary":"Polymer Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CCIT":{"name":"CCIT","sections":["SUMMARY"],"supported":null,"summary":"Polymer Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"FCPR":{"name":"FCPR","sections":["SUMMARY"],"supported":null,"summary":"Polymer Production Rate","parameters":[],"example":"","size_kind":"none"},"GCPR":{"name":"GCPR","sections":["SUMMARY"],"supported":null,"summary":"Polymer Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WCPR":{"name":"WCPR","sections":["SUMMARY"],"supported":null,"summary":"Polymer Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"CCPR":{"name":"CCPR","sections":["SUMMARY"],"supported":null,"summary":"Polymer Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FCPT":{"name":"FCPT","sections":["SUMMARY"],"supported":null,"summary":"Polymer Production Total","parameters":[],"example":"","size_kind":"none"},"GCPT":{"name":"GCPT","sections":["SUMMARY"],"supported":null,"summary":"Polymer Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"WCPT":{"name":"WCPT","sections":["SUMMARY"],"supported":null,"summary":"Polymer Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CCPT":{"name":"CCPT","sections":["SUMMARY"],"supported":null,"summary":"Polymer Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"BCABnnn":{"name":"BCABnnn","sections":["SUMMARY"],"supported":null,"summary":"Polymer Adsorbed (PLYTRRFA). The highest temperature band at which residual resistance factor was calculated, see keyword PLYTRRFA. The band number nnn can range from 001 to 999, but must be less than or equal to the argument on the PLYTRRFA keyword.","parameters":[],"example":"","size_kind":"array","optional_body":true},"FCAD":{"name":"FCAD","sections":["SUMMARY"],"supported":null,"summary":"Polymer Adsorption Total. Block is concentration.","parameters":[],"example":"","size_kind":"none"},"RCAD":{"name":"RCAD","sections":["SUMMARY"],"supported":null,"summary":"Polymer Adsorption Total. Block is concentration.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BCAD":{"name":"BCAD","sections":["SUMMARY"],"supported":null,"summary":"Polymer Adsorption Total. Block is concentration.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BEPVIS":{"name":"BEPVIS","sections":["SUMMARY"],"supported":null,"summary":"Polymer Solution (Effective Viscosity). Also BVPOLY.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BSHWVISI":{"name":"BSHWVISI","sections":["SUMMARY"],"supported":null,"summary":"Polymer Solution Shear Viscosity (Inter-Block I+ Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BSHWVISJ":{"name":"BSHWVISJ","sections":["SUMMARY"],"supported":null,"summary":"Polymer Solution Shear Viscosity (Inter-Block J+ Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BSHWVISK":{"name":"BSHWVISK","sections":["SUMMARY"],"supported":null,"summary":"Polymer Solution Shear Viscosity (Inter-Block K+ Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BCDCS":{"name":"BCDCS","sections":["SUMMARY"],"supported":null,"summary":"Polymer Thermal Degradation. Total mass degraded in previous time step.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BCDCR":{"name":"BCDCR","sections":["SUMMARY"],"supported":null,"summary":"Polymer Thermal Degradation Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"BCDCA":{"name":"BCDCA","sections":["SUMMARY"],"supported":null,"summary":"Polymer Thermal Degradation Rate (Adsorbed)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BCDCP":{"name":"BCDCP","sections":["SUMMARY"],"supported":null,"summary":"Polymer Thermal Degradation Rate (Solution)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BEMVIS":{"name":"BEMVIS","sections":["SUMMARY"],"supported":null,"summary":"Polymer Water (Effective Viscosity). Based on block center properties.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BFLOW0I":{"name":"BFLOW0I","sections":["SUMMARY"],"supported":null,"summary":"Water Flow Rate Times Shear Multiplier (Inter-Block I+ Direction). Multiplied by the corresponding shear multiplier (PLYSHLOG and PLYSHEAR options only).","parameters":[],"example":"","size_kind":"array","optional_body":true},"BFLOW0J":{"name":"BFLOW0J","sections":["SUMMARY"],"supported":null,"summary":"Water Flow Rate Times Shear Multiplier (Inter-Block J+ Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BFLOW0K":{"name":"BFLOW0K","sections":["SUMMARY"],"supported":null,"summary":"Water Flow Rate Times Shear Multiplier (Inter-Block K+ Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BSRTWI":{"name":"BSRTWI","sections":["SUMMARY"],"supported":null,"summary":"Water Shear Rate After Shear Effects (Inter-Block I+ Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BSRTWJ":{"name":"BSRTWJ","sections":["SUMMARY"],"supported":null,"summary":"Water Shear Rate After Shear Effects (Inter-Block J+ Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BSRTWK":{"name":"BSRTWK","sections":["SUMMARY"],"supported":null,"summary":"Water Shear Rate After Shear Effects (Inter-Block K+ Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BSRTW0I":{"name":"BSRTW0I","sections":["SUMMARY"],"supported":null,"summary":"Water Shear Rate Prior to Shear Effects (Inter-Block I+ Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BSRTW0J":{"name":"BSRTW0J","sections":["SUMMARY"],"supported":null,"summary":"Water Shear Rate Prior to Shear Effects (Inter-Block J+ Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BSRTW0K":{"name":"BSRTW0K","sections":["SUMMARY"],"supported":null,"summary":"Water Shear Rate Prior to Shear Effects (Inter-Block K+ Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BVELW0I":{"name":"BVELW0I","sections":["SUMMARY"],"supported":null,"summary":"Water Velocity (Inter-Block I+ Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BVELW0J":{"name":"BVELW0J","sections":["SUMMARY"],"supported":null,"summary":"Water Velocity (Inter-Block J+ Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BVELW0K":{"name":"BVELW0K","sections":["SUMMARY"],"supported":null,"summary":"Water Velocity (Inter-Block K+ Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BEWV_POL":{"name":"BEWV_POL","sections":["SUMMARY"],"supported":null,"summary":"Water Viscosity (Effective)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BPSHLZI":{"name":"BPSHLZI","sections":["SUMMARY"],"supported":null,"summary":"Water Viscosity Sheared Factor (Inter-Block I+ Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BPSHLZJ":{"name":"BPSHLZJ","sections":["SUMMARY"],"supported":null,"summary":"Water Viscosity Sheared Factor (Inter-Block J+ Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BPSHLZK":{"name":"BPSHLZK","sections":["SUMMARY"],"supported":null,"summary":"Water Viscosity Sheared Factor (Inter-Block K+ Direction)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BCCN":{"name":"BCCN","sections":["SUMMARY"],"supported":null,"summary":"Polymer Concentration (Block)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FCIC":{"name":"FCIC","sections":["SUMMARY"],"supported":null,"summary":"Polymer Concentration (Injection)","parameters":[],"example":"","size_kind":"none"},"GCIC":{"name":"GCIC","sections":["SUMMARY"],"supported":null,"summary":"Polymer Concentration (Injection)","parameters":[],"example":"","size_kind":"array","optional_body":true},"WCIC":{"name":"WCIC","sections":["SUMMARY"],"supported":null,"summary":"Polymer Concentration (Injection)","parameters":[],"example":"","size_kind":"array","optional_body":true},"CCIC":{"name":"CCIC","sections":["SUMMARY"],"supported":null,"summary":"Polymer Concentration (Injection)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FCPC":{"name":"FCPC","sections":["SUMMARY"],"supported":null,"summary":"Polymer Concentration (Production)","parameters":[],"example":"","size_kind":"none"},"GCPC":{"name":"GCPC","sections":["SUMMARY"],"supported":null,"summary":"Polymer Concentration (Production)","parameters":[],"example":"","size_kind":"array","optional_body":true},"WCPC":{"name":"WCPC","sections":["SUMMARY"],"supported":null,"summary":"Polymer Concentration (Production)","parameters":[],"example":"","size_kind":"array","optional_body":true},"CCPC":{"name":"CCPC","sections":["SUMMARY"],"supported":null,"summary":"Polymer Concentration (Production)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FCIP":{"name":"FCIP","sections":["SUMMARY"],"supported":null,"summary":"Polymer Solution (In Solution)","parameters":[],"example":"","size_kind":"none"},"RCIP":{"name":"RCIP","sections":["SUMMARY"],"supported":null,"summary":"Polymer Solution (In Solution)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BCIP":{"name":"BCIP","sections":["SUMMARY"],"supported":null,"summary":"Polymer Solution (In Solution)","parameters":[],"example":"","size_kind":"array","optional_body":true},"RSFT":{"name":"RSFT","sections":["SUMMARY"],"supported":null,"summary":"Salt inter-region Flow Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CNFR":{"name":"CNFR","sections":["SUMMARY"],"supported":null,"summary":"Solvent Flow Rate. Field, group, and well gas rates and cumulative volumes include the solvent gas.","parameters":[],"example":"","size_kind":"array","optional_body":true},"RNFT":{"name":"RNFT","sections":["SUMMARY"],"supported":null,"summary":"Solvent Flow Total (Inter-Region)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FNIR":{"name":"FNIR","sections":["SUMMARY"],"supported":null,"summary":"Solvent Injection Rate","parameters":[],"example":"","size_kind":"none"},"GNIR":{"name":"GNIR","sections":["SUMMARY"],"supported":null,"summary":"Solvent Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WNIR":{"name":"WNIR","sections":["SUMMARY"],"supported":null,"summary":"Solvent Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FNIT":{"name":"FNIT","sections":["SUMMARY"],"supported":null,"summary":"Solvent Injection Total","parameters":[],"example":"","size_kind":"none"},"GNIT":{"name":"GNIT","sections":["SUMMARY"],"supported":null,"summary":"Solvent Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"WNIT":{"name":"WNIT","sections":["SUMMARY"],"supported":null,"summary":"Solvent Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CNIT":{"name":"CNIT","sections":["SUMMARY"],"supported":null,"summary":"Solvent Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"FNPR":{"name":"FNPR","sections":["SUMMARY"],"supported":null,"summary":"Solvent Production Rate","parameters":[],"example":"","size_kind":"none"},"GNPR":{"name":"GNPR","sections":["SUMMARY"],"supported":null,"summary":"Solvent Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WNPR":{"name":"WNPR","sections":["SUMMARY"],"supported":null,"summary":"Solvent Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FNPT":{"name":"FNPT","sections":["SUMMARY"],"supported":null,"summary":"Solvent Production Total","parameters":[],"example":"","size_kind":"none"},"GNPT":{"name":"GNPT","sections":["SUMMARY"],"supported":null,"summary":"Solvent Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"WNPT":{"name":"WNPT","sections":["SUMMARY"],"supported":null,"summary":"Solvent Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"CNPT":{"name":"CNPT","sections":["SUMMARY"],"supported":null,"summary":"Solvent Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"BNKR":{"name":"BNKR","sections":["SUMMARY"],"supported":null,"summary":"Solvent Relative Permeability","parameters":[],"example":"","size_kind":"array","optional_body":true},"FNIP":{"name":"FNIP","sections":["SUMMARY"],"supported":null,"summary":"Solvent In-Place","parameters":[],"example":"","size_kind":"none"},"RNIP":{"name":"RNIP","sections":["SUMMARY"],"supported":null,"summary":"Solvent In-Place","parameters":[],"example":"","size_kind":"array","optional_body":true},"BNIP":{"name":"BNIP","sections":["SUMMARY"],"supported":null,"summary":"Solvent In-Place","parameters":[],"example":"","size_kind":"array","optional_body":true},"BNSAT":{"name":"BNSAT","sections":["SUMMARY"],"supported":null,"summary":"Solvent Saturation","parameters":[],"example":"","size_kind":"array","optional_body":true},"FTIRHEA":{"name":"FTIRHEA","sections":["SUMMARY"],"supported":null,"summary":"Energy Injection Rate","parameters":[],"example":"","size_kind":"none"},"GTIRHEA":{"name":"GTIRHEA","sections":["SUMMARY"],"supported":null,"summary":"Energy Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WTIRHEA":{"name":"WTIRHEA","sections":["SUMMARY"],"supported":null,"summary":"Energy Injection Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FTITHEA":{"name":"FTITHEA","sections":["SUMMARY"],"supported":null,"summary":"Energy Injection Total","parameters":[],"example":"","size_kind":"none"},"GTITHEA":{"name":"GTITHEA","sections":["SUMMARY"],"supported":null,"summary":"Energy Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"WTITHEA":{"name":"WTITHEA","sections":["SUMMARY"],"supported":null,"summary":"Energy Injection Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"FTPRHEA":{"name":"FTPRHEA","sections":["SUMMARY"],"supported":null,"summary":"Energy Production Rate","parameters":[],"example":"","size_kind":"none"},"GTPRHEA":{"name":"GTPRHEA","sections":["SUMMARY"],"supported":null,"summary":"Energy Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"WTPRHEA":{"name":"WTPRHEA","sections":["SUMMARY"],"supported":null,"summary":"Energy Production Rate","parameters":[],"example":"","size_kind":"array","optional_body":true},"FTPTHEA":{"name":"FTPTHEA","sections":["SUMMARY"],"supported":null,"summary":"Energy Production Total","parameters":[],"example":"","size_kind":"none"},"GTPTHEA":{"name":"GTPTHEA","sections":["SUMMARY"],"supported":null,"summary":"Energy Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"WTPTHEA":{"name":"WTPTHEA","sections":["SUMMARY"],"supported":null,"summary":"Energy Production Total","parameters":[],"example":"","size_kind":"array","optional_body":true},"BTCNFHEA":{"name":"BTCNFHEA","sections":["SUMMARY"],"supported":null,"summary":"Temperature (Block)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FTICHEA":{"name":"FTICHEA","sections":["SUMMARY"],"supported":null,"summary":"Temperature (Injection)","parameters":[],"example":"","size_kind":"none"},"GTICHEA":{"name":"GTICHEA","sections":["SUMMARY"],"supported":null,"summary":"Temperature (Injection)","parameters":[],"example":"","size_kind":"array","optional_body":true},"WTICHEA":{"name":"WTICHEA","sections":["SUMMARY"],"supported":null,"summary":"Temperature (Injection)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FTPCHEA":{"name":"FTPCHEA","sections":["SUMMARY"],"supported":null,"summary":"Temperature (Production)","parameters":[],"example":"","size_kind":"none"},"GTPCHEA":{"name":"GTPCHEA","sections":["SUMMARY"],"supported":null,"summary":"Temperature (Production)","parameters":[],"example":"","size_kind":"array","optional_body":true},"WTPCHEA":{"name":"WTPCHEA","sections":["SUMMARY"],"supported":null,"summary":"Temperature (Production)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BTPCHEA":{"name":"BTPCHEA","sections":["SUMMARY"],"supported":null,"summary":"Temperature (Production)","parameters":[],"example":"","size_kind":"array","optional_body":true},"FTIPTHEA":{"name":"FTIPTHEA","sections":["SUMMARY"],"supported":null,"summary":"Energy In-Place Difference. Difference in energy in- place from start of run to current time.","parameters":[],"example":"","size_kind":"none"},"RTIPTHEA4":{"name":"RTIPTHEA4","sections":["SUMMARY"],"supported":null,"summary":"Energy In-Place Difference. Difference in energy in- place from start of run to current time.","parameters":[],"example":"","size_kind":"array","optional_body":true},"BTIPTHEA":{"name":"BTIPTHEA","sections":["SUMMARY"],"supported":null,"summary":"Energy In-Place Difference. Difference in energy in- place from start of run to current time.","parameters":[],"example":"","size_kind":"array","optional_body":true},"FU":{"name":"FU","sections":["SUMMARY"],"supported":null,"summary":"UDQ Variable","parameters":[],"example":"","size_kind":"none","templated":true},"GU":{"name":"GU","sections":["SUMMARY"],"supported":null,"summary":"UDQ Variable","parameters":[],"example":"","size_kind":"array","optional_body":true,"templated":true},"WU":{"name":"WU","sections":["SUMMARY"],"supported":null,"summary":"UDQ Variable","parameters":[],"example":"","size_kind":"array","optional_body":true,"templated":true},"CU":{"name":"CU","sections":["SUMMARY"],"supported":null,"summary":"UDQ Variable","parameters":[],"example":"","size_kind":"array","optional_body":true,"templated":true},"RU":{"name":"RU","sections":["SUMMARY"],"supported":null,"summary":"UDQ Variable","parameters":[],"example":"","size_kind":"array","optional_body":true,"templated":true},"SU":{"name":"SU","sections":["SUMMARY"],"supported":null,"summary":"UDQ Variable","parameters":[],"example":"","size_kind":"array","optional_body":true,"templated":true},"AQUIFER_PROBE_ANALYTIC":{"name":"AQUIFER_PROBE_ANALYTIC","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array","optional_body":true},"AQUIFER_PROBE_ANALYTIC_NAMED":{"name":"AQUIFER_PROBE_ANALYTIC_NAMED","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array","optional_body":true},"AQUIFER_PROBE_NUMERIC":{"name":"AQUIFER_PROBE_NUMERIC","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array","optional_body":true},"BLOCK_PROBE":{"name":"BLOCK_PROBE","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"I","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"J","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"K","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":3,"size_kind":"list"},"COMPDATX":{"name":"COMPDATX","sections":["SCHEDULE"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"LGR","description":"","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"I","description":"","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"J","description":"","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"K1","description":"","units":{},"default":"","value_type":"INT"},{"index":6,"name":"K2","description":"","units":{},"default":"","value_type":"INT"},{"index":7,"name":"STATE","description":"","units":{},"default":"OPEN","value_type":"STRING"},{"index":8,"name":"SAT_TABLE","description":"","units":{},"default":"0","value_type":"INT"},{"index":9,"name":"CONNECTION_TRANSMISSIBILITY_FACTOR","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Viscosity*ReservoirVolume/Time*Pressure"},{"index":10,"name":"DIAMETER","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":11,"name":"Kh","description":"","units":{},"default":"-1","value_type":"DOUBLE","dimension":"Permeability*Length"},{"index":12,"name":"SKIN","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"1"},{"index":13,"name":"D_FACTOR","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"1"},{"index":14,"name":"DIR","description":"","units":{},"default":"Z","value_type":"STRING"},{"index":15,"name":"PR","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"}],"example":"","expected_columns":15,"size_kind":"list"},"CONNECTION_PROBE":{"name":"CONNECTION_PROBE","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"I","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"J","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"K","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":4,"size_kind":"list"},"DEBUG_":{"name":"DEBUG_","sections":["RUNSPEC","GRID","EDIT","PROPS","REGIONS","SOLUTION","SUMMARY","SCHEDULE"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"Item1","description":"","units":{},"default":"0","value_type":"INT"},{"index":2,"name":"Item2","description":"","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"Item3","description":"","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"Item4","description":"","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"Item5","description":"","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"Item6","description":"","units":{},"default":"0","value_type":"INT"},{"index":7,"name":"Item7","description":"","units":{},"default":"0","value_type":"INT"},{"index":8,"name":"Item8","description":"","units":{},"default":"0","value_type":"INT"},{"index":9,"name":"Item9","description":"","units":{},"default":"0","value_type":"INT"},{"index":10,"name":"Item10","description":"","units":{},"default":"0","value_type":"INT"},{"index":11,"name":"Item11","description":"","units":{},"default":"0","value_type":"INT"},{"index":12,"name":"Item12","description":"","units":{},"default":"0","value_type":"INT"},{"index":13,"name":"Item13","description":"","units":{},"default":"0","value_type":"INT"},{"index":14,"name":"Item14","description":"","units":{},"default":"0","value_type":"INT"},{"index":15,"name":"Item15","description":"","units":{},"default":"0","value_type":"INT"},{"index":16,"name":"Item16","description":"","units":{},"default":"0","value_type":"INT"},{"index":17,"name":"Item17","description":"","units":{},"default":"0","value_type":"INT"},{"index":18,"name":"Item18","description":"","units":{},"default":"0","value_type":"INT"},{"index":19,"name":"Item19","description":"","units":{},"default":"0","value_type":"INT"},{"index":20,"name":"Item20","description":"","units":{},"default":"0","value_type":"INT"},{"index":21,"name":"Item21","description":"","units":{},"default":"0","value_type":"INT"},{"index":22,"name":"Item22","description":"","units":{},"default":"0","value_type":"INT"},{"index":23,"name":"Item23","description":"","units":{},"default":"0","value_type":"INT"},{"index":24,"name":"Item24","description":"","units":{},"default":"0","value_type":"INT"},{"index":25,"name":"Item25","description":"","units":{},"default":"0","value_type":"INT"},{"index":26,"name":"Item26","description":"","units":{},"default":"0","value_type":"INT"},{"index":27,"name":"Item27","description":"","units":{},"default":"0","value_type":"INT"},{"index":28,"name":"Item28","description":"","units":{},"default":"0","value_type":"INT"},{"index":29,"name":"Item29","description":"","units":{},"default":"0","value_type":"INT"},{"index":30,"name":"Item30","description":"","units":{},"default":"0","value_type":"INT"},{"index":31,"name":"Item31","description":"","units":{},"default":"0","value_type":"INT"},{"index":32,"name":"Item32","description":"","units":{},"default":"0","value_type":"INT"},{"index":33,"name":"Item33","description":"","units":{},"default":"0","value_type":"INT"},{"index":34,"name":"Item34","description":"","units":{},"default":"0","value_type":"INT"},{"index":35,"name":"Item35","description":"","units":{},"default":"0","value_type":"INT"},{"index":36,"name":"Item36","description":"","units":{},"default":"0","value_type":"INT"},{"index":37,"name":"Item37","description":"","units":{},"default":"0","value_type":"INT"},{"index":38,"name":"Item38","description":"","units":{},"default":"0","value_type":"INT"},{"index":39,"name":"Item39","description":"","units":{},"default":"0","value_type":"INT"},{"index":40,"name":"Item40","description":"","units":{},"default":"0","value_type":"INT"},{"index":41,"name":"Item41","description":"","units":{},"default":"0","value_type":"INT"},{"index":42,"name":"Item42","description":"","units":{},"default":"0","value_type":"INT"},{"index":43,"name":"Item43","description":"","units":{},"default":"0","value_type":"INT"},{"index":44,"name":"Item44","description":"","units":{},"default":"0","value_type":"INT"},{"index":45,"name":"Item45","description":"","units":{},"default":"0","value_type":"INT"},{"index":46,"name":"Item46","description":"","units":{},"default":"0","value_type":"INT"},{"index":47,"name":"Item47","description":"","units":{},"default":"0","value_type":"INT"},{"index":48,"name":"Item48","description":"","units":{},"default":"0","value_type":"INT"},{"index":49,"name":"Item49","description":"","units":{},"default":"0","value_type":"INT"},{"index":50,"name":"Item50","description":"","units":{},"default":"0","value_type":"INT"},{"index":51,"name":"Item51","description":"","units":{},"default":"0","value_type":"INT"},{"index":52,"name":"Item52","description":"","units":{},"default":"0","value_type":"INT"},{"index":53,"name":"Item53","description":"","units":{},"default":"0","value_type":"INT"},{"index":54,"name":"Item54","description":"","units":{},"default":"0","value_type":"INT"},{"index":55,"name":"Item55","description":"","units":{},"default":"0","value_type":"INT"},{"index":56,"name":"Item56","description":"","units":{},"default":"0","value_type":"INT"},{"index":57,"name":"Item57","description":"","units":{},"default":"0","value_type":"INT"},{"index":58,"name":"Item58","description":"","units":{},"default":"0","value_type":"INT"},{"index":59,"name":"Item59","description":"","units":{},"default":"0","value_type":"INT"},{"index":60,"name":"Item60","description":"","units":{},"default":"0","value_type":"INT"},{"index":61,"name":"Item61","description":"","units":{},"default":"0","value_type":"INT"},{"index":62,"name":"Item62","description":"","units":{},"default":"0","value_type":"INT"},{"index":63,"name":"Item63","description":"","units":{},"default":"0","value_type":"INT"},{"index":64,"name":"Item64","description":"","units":{},"default":"0","value_type":"INT"},{"index":65,"name":"Item65","description":"","units":{},"default":"0","value_type":"INT"},{"index":66,"name":"Item66","description":"","units":{},"default":"0","value_type":"INT"},{"index":67,"name":"Item67","description":"","units":{},"default":"0","value_type":"INT"},{"index":68,"name":"Item68","description":"","units":{},"default":"0","value_type":"INT"},{"index":69,"name":"Item69","description":"","units":{},"default":"0","value_type":"INT"},{"index":70,"name":"Item70","description":"","units":{},"default":"0","value_type":"INT"},{"index":71,"name":"Item71","description":"","units":{},"default":"0","value_type":"INT"},{"index":72,"name":"Item72","description":"","units":{},"default":"0","value_type":"INT"},{"index":73,"name":"Item73","description":"","units":{},"default":"0","value_type":"INT"},{"index":74,"name":"Item74","description":"","units":{},"default":"0","value_type":"INT"},{"index":75,"name":"Item75","description":"","units":{},"default":"0","value_type":"INT"},{"index":76,"name":"Item76","description":"","units":{},"default":"0","value_type":"INT"},{"index":77,"name":"Item77","description":"","units":{},"default":"0","value_type":"INT"},{"index":78,"name":"Item78","description":"","units":{},"default":"0","value_type":"INT"},{"index":79,"name":"Item79","description":"","units":{},"default":"0","value_type":"INT"},{"index":80,"name":"Item80","description":"","units":{},"default":"0","value_type":"INT"},{"index":81,"name":"Item81","description":"","units":{},"default":"0","value_type":"INT"},{"index":82,"name":"Item82","description":"","units":{},"default":"0","value_type":"INT"},{"index":83,"name":"Item83","description":"","units":{},"default":"0","value_type":"INT"},{"index":84,"name":"Item84","description":"","units":{},"default":"0","value_type":"INT"},{"index":85,"name":"Item85","description":"","units":{},"default":"0","value_type":"INT"},{"index":86,"name":"Item86","description":"","units":{},"default":"0","value_type":"INT"},{"index":87,"name":"Item87","description":"","units":{},"default":"0","value_type":"INT"}],"example":"","expected_columns":87,"size_kind":"fixed","size_count":1},"DEPTHZ":{"name":"DEPTHZ","sections":["GRID"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"ENDPOINT_SPECIFIERS":{"name":"ENDPOINT_SPECIFIERS","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"FIELD_PROBE":{"name":"FIELD_PROBE","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"none","size_count":0},"FIP_PROBE":{"name":"FIP_PROBE","sections":["REGIONS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"FIPSEP":{"name":"FIPSEP","sections":["SOLUTION"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"FLUID_IN_PLACE_REGION","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"STAGE_INDEX","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"STAGE_TEMPERATURE","description":"","units":{},"default":"15.56","value_type":"DOUBLE","dimension":"Temperature"},{"index":4,"name":"STAGE_PRESSURE","description":"","units":{},"default":"1.01325","value_type":"DOUBLE","dimension":"Pressure"},{"index":5,"name":"DESTINATION_OUPUT","description":"","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"DESTINATION_STAGE","description":"","units":{},"default":"0","value_type":"INT"},{"index":7,"name":"K_VAL_TABLE_NUM","description":"","units":{},"default":"0","value_type":"INT"},{"index":8,"name":"GAS_PLANT_TABLE_NUM","description":"","units":{},"default":"0","value_type":"INT"},{"index":9,"name":"SURF_EQ_STATE_NUM","description":"","units":{},"default":"","value_type":"INT"},{"index":10,"name":"DENSITY_EVAL_GAS_TEMP","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Temperature"},{"index":11,"name":"DENSITY_EVAL_PRESSURE_TEMP","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"}],"example":"","expected_columns":11,"size_kind":"list"},"GROUP_PROBE":{"name":"GROUP_PROBE","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"GROUPS","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","size_kind":"fixed","size_count":1},"HAxxxxxx":{"name":"HAxxxxxx","sections":["PROPS","REGIONS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"HMMULTxx":{"name":"HMMULTxx","sections":["GRID","EDIT"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"HMxxxxxx":{"name":"HMxxxxxx","sections":["REGIONS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"MSUM_PROBE":{"name":"MSUM_PROBE","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"none","size_count":0},"MULT_XYZ":{"name":"MULT_XYZ","sections":["GRID","EDIT","SCHEDULE"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"PEGTABX":{"name":"PEGTABX","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Pressure","Pressure"]}],"example":"","size_kind":"fixed"},"PEKTABX":{"name":"PEKTABX","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Pressure","Pressure"]}],"example":"","size_kind":"fixed"},"PERFORMANCE_PROBE":{"name":"PERFORMANCE_PROBE","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"none","size_count":0},"PERMXY":{"name":"PERMXY","sections":["GRID"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"PERMYZ":{"name":"PERMYZ","sections":["GRID"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"PERMZX":{"name":"PERMZX","sections":["GRID"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"PLYOPTS":{"name":"PLYOPTS","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"MIN_SWAT","description":"","units":{},"default":"1e-06","value_type":"DOUBLE"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"PSWRG":{"name":"PSWRG","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"PSWRO":{"name":"PSWRO","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"PVT_M":{"name":"PVT_M","sections":["RUNSPEC"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"none","size_count":0},"REGION2REGION_PROBE":{"name":"REGION2REGION_PROBE","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"REGION1","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"REGION2","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":2,"size_kind":"list"},"REGION_PROBE":{"name":"REGION_PROBE","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array","optional_body":true},"ROCKV":{"name":"ROCKV","sections":["EDIT"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"SEGMENT_PROBE":{"name":"SEGMENT_PROBE","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"Well","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"Segment","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":2,"size_kind":"list"},"SIGMATH":{"name":"SIGMATH","sections":["GRID"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"SOLWNUM":{"name":"SOLWNUM","sections":["GRID"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"SURFOPTS":{"name":"SURFOPTS","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"MIN_SWAT","description":"","units":{},"default":"1e-06","value_type":"DOUBLE"},{"index":2,"name":"SMOOTHING","description":"","units":{},"default":"1e-06","value_type":"DOUBLE"}],"example":"","expected_columns":2,"size_kind":"fixed","size_count":1},"WELL_COMPLETION_PROBE":{"name":"WELL_COMPLETION_PROBE","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"COMPLETION","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":2,"size_kind":"list"},"WELL_PROBE":{"name":"WELL_PROBE","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"WELLS","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","size_kind":"fixed","size_count":1},"BLOCK_PROBE300":{"name":"BLOCK_PROBE300","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"I","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"J","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"K","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":3,"size_kind":"list"},"CIRCLE":{"name":"CIRCLE","sections":["GRID"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"none","size_count":0},"CREF":{"name":"CREF","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"COMPRESSIBILITY","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["1/Pressure"]}],"example":"","size_kind":"fixed"},"CREFW":{"name":"CREFW","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"COMPRESSIBILITY","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["1/Pressure"]}],"example":"","size_kind":"fixed"},"CREFWS":{"name":"CREFWS","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"COMPRESSIBILITY","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["1/Pressure"]}],"example":"","size_kind":"fixed"},"DREF":{"name":"DREF","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"DENSITY","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Density"]}],"example":"","size_kind":"fixed"},"DREFS":{"name":"DREFS","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"DENSITY","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Density"]}],"example":"","size_kind":"fixed"},"FIELDSEP":{"name":"FIELDSEP","sections":["SOLUTION"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"STAGE","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"TEMPERATURE","description":"","units":{},"default":"15.56","value_type":"DOUBLE","dimension":"Temperature"},{"index":3,"name":"PRESSURE","description":"","units":{},"default":"1.01325","value_type":"DOUBLE","dimension":"Pressure"},{"index":4,"name":"LIQ_DESTINATION","description":"","units":{},"default":"","value_type":"INT"},{"index":5,"name":"VAP_DESTINATION","description":"","units":{},"default":"","value_type":"INT"},{"index":6,"name":"KVALUE","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"1"},{"index":7,"name":"TABLE_NUM","description":"","units":{},"default":"0","value_type":"INT"},{"index":8,"name":"EOS_NUM","description":"","units":{},"default":"","value_type":"INT"},{"index":9,"name":"REF_TEMP","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Temperature"},{"index":10,"name":"REF_PRESS","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"}],"example":"","expected_columns":10,"size_kind":"list"},"HWELLS":{"name":"HWELLS","sections":["RUNSPEC"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"none","size_count":0},"MWS":{"name":"MWS","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"MOLAR_WEIGHT","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Mass/Moles"}],"example":"","size_kind":"fixed"},"OILCOMPR":{"name":"OILCOMPR","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"COMPRESSIBILITY","description":"","units":{},"default":"0","value_type":"DOUBLE"},{"index":2,"name":"EXPANSION_COEFF_LINEAR","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"1/AbsoluteTemperature"},{"index":3,"name":"EXPANSION_COEFF_QUADRATIC","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"1/AbsoluteTemperature*AbsoluteTemperature"}],"example":"","expected_columns":3,"size_kind":"fixed"},"OILMW":{"name":"OILMW","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"MOLAR_WEIGHT","description":"","units":{},"default":"","value_type":"DOUBLE"}],"example":"","expected_columns":1,"size_kind":"fixed"},"OILVTIM":{"name":"OILVTIM","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"INTERPOLATION_METHOD","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":1,"size_kind":"list"},"OPTIONS3":{"name":"OPTIONS3","sections":["RUNSPEC","SCHEDULE"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"ITEM1","description":"","units":{},"default":"0","value_type":"INT"},{"index":2,"name":"ITEM2","description":"","units":{},"default":"0","value_type":"INT"},{"index":3,"name":"ITEM3","description":"","units":{},"default":"0","value_type":"INT"},{"index":4,"name":"ITEM4","description":"","units":{},"default":"0","value_type":"INT"},{"index":5,"name":"ITEM5","description":"","units":{},"default":"0","value_type":"INT"},{"index":6,"name":"ITEM6","description":"","units":{},"default":"0","value_type":"INT"},{"index":7,"name":"ITEM7","description":"","units":{},"default":"0","value_type":"INT"},{"index":8,"name":"ITEM8","description":"","units":{},"default":"0","value_type":"INT"},{"index":9,"name":"ITEM9","description":"","units":{},"default":"0","value_type":"INT"},{"index":10,"name":"ITEM10","description":"","units":{},"default":"0","value_type":"INT"},{"index":11,"name":"ITEM11","description":"","units":{},"default":"0","value_type":"INT"},{"index":12,"name":"ITEM12","description":"","units":{},"default":"0","value_type":"INT"},{"index":13,"name":"ITEM13","description":"","units":{},"default":"0","value_type":"INT"},{"index":14,"name":"ITEM14","description":"","units":{},"default":"0","value_type":"INT"},{"index":15,"name":"ITEM15","description":"","units":{},"default":"0","value_type":"INT"},{"index":16,"name":"ITEM16","description":"","units":{},"default":"0","value_type":"INT"},{"index":17,"name":"ITEM17","description":"","units":{},"default":"0","value_type":"INT"},{"index":18,"name":"ITEM18","description":"","units":{},"default":"0","value_type":"INT"},{"index":19,"name":"ITEM19","description":"","units":{},"default":"0","value_type":"INT"},{"index":20,"name":"ITEM20","description":"","units":{},"default":"0","value_type":"INT"},{"index":21,"name":"ITEM21","description":"","units":{},"default":"0","value_type":"INT"},{"index":22,"name":"ITEM22","description":"","units":{},"default":"0","value_type":"INT"},{"index":23,"name":"ITEM23","description":"","units":{},"default":"0","value_type":"INT"},{"index":24,"name":"ITEM24","description":"","units":{},"default":"0","value_type":"INT"},{"index":25,"name":"ITEM25","description":"","units":{},"default":"0","value_type":"INT"},{"index":26,"name":"ITEM26","description":"","units":{},"default":"0","value_type":"INT"},{"index":27,"name":"ITEM27","description":"","units":{},"default":"0","value_type":"INT"},{"index":28,"name":"ITEM28","description":"","units":{},"default":"0","value_type":"INT"},{"index":29,"name":"ITEM29","description":"","units":{},"default":"0","value_type":"INT"},{"index":30,"name":"ITEM30","description":"","units":{},"default":"0","value_type":"INT"},{"index":31,"name":"ITEM31","description":"","units":{},"default":"0","value_type":"INT"},{"index":32,"name":"ITEM32","description":"","units":{},"default":"0","value_type":"INT"},{"index":33,"name":"ITEM33","description":"","units":{},"default":"0","value_type":"INT"},{"index":34,"name":"ITEM34","description":"","units":{},"default":"0","value_type":"INT"},{"index":35,"name":"ITEM35","description":"","units":{},"default":"0","value_type":"INT"},{"index":36,"name":"ITEM36","description":"","units":{},"default":"0","value_type":"INT"},{"index":37,"name":"ITEM37","description":"","units":{},"default":"0","value_type":"INT"},{"index":38,"name":"ITEM38","description":"","units":{},"default":"0","value_type":"INT"},{"index":39,"name":"ITEM39","description":"","units":{},"default":"0","value_type":"INT"},{"index":40,"name":"ITEM40","description":"","units":{},"default":"0","value_type":"INT"},{"index":41,"name":"ITEM41","description":"","units":{},"default":"0","value_type":"INT"},{"index":42,"name":"ITEM42","description":"","units":{},"default":"0","value_type":"INT"},{"index":43,"name":"ITEM43","description":"","units":{},"default":"0","value_type":"INT"},{"index":44,"name":"ITEM44","description":"","units":{},"default":"0","value_type":"INT"},{"index":45,"name":"ITEM45","description":"","units":{},"default":"0","value_type":"INT"},{"index":46,"name":"ITEM46","description":"","units":{},"default":"0","value_type":"INT"},{"index":47,"name":"ITEM47","description":"","units":{},"default":"0","value_type":"INT"},{"index":48,"name":"ITEM48","description":"","units":{},"default":"0","value_type":"INT"},{"index":49,"name":"ITEM49","description":"","units":{},"default":"0","value_type":"INT"},{"index":50,"name":"ITEM50","description":"","units":{},"default":"0","value_type":"INT"},{"index":51,"name":"ITEM51","description":"","units":{},"default":"0","value_type":"INT"},{"index":52,"name":"ITEM52","description":"","units":{},"default":"0","value_type":"INT"},{"index":53,"name":"ITEM53","description":"","units":{},"default":"0","value_type":"INT"},{"index":54,"name":"ITEM54","description":"","units":{},"default":"0","value_type":"INT"},{"index":55,"name":"ITEM55","description":"","units":{},"default":"0","value_type":"INT"},{"index":56,"name":"ITEM56","description":"","units":{},"default":"0","value_type":"INT"},{"index":57,"name":"ITEM57","description":"","units":{},"default":"0","value_type":"INT"},{"index":58,"name":"ITEM58","description":"","units":{},"default":"0","value_type":"INT"},{"index":59,"name":"ITEM59","description":"","units":{},"default":"0","value_type":"INT"},{"index":60,"name":"ITEM60","description":"","units":{},"default":"0","value_type":"INT"},{"index":61,"name":"ITEM61","description":"","units":{},"default":"0","value_type":"INT"},{"index":62,"name":"ITEM62","description":"","units":{},"default":"0","value_type":"INT"},{"index":63,"name":"ITEM63","description":"","units":{},"default":"0","value_type":"INT"},{"index":64,"name":"ITEM64","description":"","units":{},"default":"0","value_type":"INT"},{"index":65,"name":"ITEM65","description":"","units":{},"default":"0","value_type":"INT"},{"index":66,"name":"ITEM66","description":"","units":{},"default":"0","value_type":"INT"},{"index":67,"name":"ITEM67","description":"","units":{},"default":"0","value_type":"INT"},{"index":68,"name":"ITEM68","description":"","units":{},"default":"0","value_type":"INT"},{"index":69,"name":"ITEM69","description":"","units":{},"default":"0","value_type":"INT"},{"index":70,"name":"ITEM70","description":"","units":{},"default":"0","value_type":"INT"},{"index":71,"name":"ITEM71","description":"","units":{},"default":"0","value_type":"INT"},{"index":72,"name":"ITEM72","description":"","units":{},"default":"0","value_type":"INT"},{"index":73,"name":"ITEM73","description":"","units":{},"default":"0","value_type":"INT"},{"index":74,"name":"ITEM74","description":"","units":{},"default":"0","value_type":"INT"},{"index":75,"name":"ITEM75","description":"","units":{},"default":"0","value_type":"INT"},{"index":76,"name":"ITEM76","description":"","units":{},"default":"0","value_type":"INT"},{"index":77,"name":"ITEM77","description":"","units":{},"default":"0","value_type":"INT"},{"index":78,"name":"ITEM78","description":"","units":{},"default":"0","value_type":"INT"},{"index":79,"name":"ITEM79","description":"","units":{},"default":"0","value_type":"INT"},{"index":80,"name":"ITEM80","description":"","units":{},"default":"0","value_type":"INT"},{"index":81,"name":"ITEM81","description":"","units":{},"default":"0","value_type":"INT"},{"index":82,"name":"ITEM82","description":"","units":{},"default":"0","value_type":"INT"},{"index":83,"name":"ITEM83","description":"","units":{},"default":"0","value_type":"INT"},{"index":84,"name":"ITEM84","description":"","units":{},"default":"0","value_type":"INT"},{"index":85,"name":"ITEM85","description":"","units":{},"default":"0","value_type":"INT"},{"index":86,"name":"ITEM86","description":"","units":{},"default":"0","value_type":"INT"},{"index":87,"name":"ITEM87","description":"","units":{},"default":"0","value_type":"INT"},{"index":88,"name":"ITEM88","description":"","units":{},"default":"0","value_type":"INT"},{"index":89,"name":"ITEM89","description":"","units":{},"default":"0","value_type":"INT"},{"index":90,"name":"ITEM90","description":"","units":{},"default":"0","value_type":"INT"},{"index":91,"name":"ITEM91","description":"","units":{},"default":"0","value_type":"INT"},{"index":92,"name":"ITEM92","description":"","units":{},"default":"0","value_type":"INT"},{"index":93,"name":"ITEM93","description":"","units":{},"default":"0","value_type":"INT"},{"index":94,"name":"ITEM94","description":"","units":{},"default":"0","value_type":"INT"},{"index":95,"name":"ITEM95","description":"","units":{},"default":"0","value_type":"INT"},{"index":96,"name":"ITEM96","description":"","units":{},"default":"0","value_type":"INT"},{"index":97,"name":"ITEM97","description":"","units":{},"default":"0","value_type":"INT"},{"index":98,"name":"ITEM98","description":"","units":{},"default":"0","value_type":"INT"},{"index":99,"name":"ITEM99","description":"","units":{},"default":"0","value_type":"INT"},{"index":100,"name":"ITEM100","description":"","units":{},"default":"0","value_type":"INT"},{"index":101,"name":"ITEM101","description":"","units":{},"default":"0","value_type":"INT"},{"index":102,"name":"ITEM102","description":"","units":{},"default":"0","value_type":"INT"},{"index":103,"name":"ITEM103","description":"","units":{},"default":"0","value_type":"INT"},{"index":104,"name":"ITEM104","description":"","units":{},"default":"0","value_type":"INT"},{"index":105,"name":"ITEM105","description":"","units":{},"default":"0","value_type":"INT"},{"index":106,"name":"ITEM106","description":"","units":{},"default":"0","value_type":"INT"},{"index":107,"name":"ITEM107","description":"","units":{},"default":"0","value_type":"INT"},{"index":108,"name":"ITEM108","description":"","units":{},"default":"0","value_type":"INT"},{"index":109,"name":"ITEM109","description":"","units":{},"default":"0","value_type":"INT"},{"index":110,"name":"ITEM110","description":"","units":{},"default":"0","value_type":"INT"},{"index":111,"name":"ITEM111","description":"","units":{},"default":"0","value_type":"INT"},{"index":112,"name":"ITEM112","description":"","units":{},"default":"0","value_type":"INT"},{"index":113,"name":"ITEM113","description":"","units":{},"default":"0","value_type":"INT"},{"index":114,"name":"ITEM114","description":"","units":{},"default":"0","value_type":"INT"},{"index":115,"name":"ITEM115","description":"","units":{},"default":"0","value_type":"INT"},{"index":116,"name":"ITEM116","description":"","units":{},"default":"0","value_type":"INT"},{"index":117,"name":"ITEM117","description":"","units":{},"default":"0","value_type":"INT"},{"index":118,"name":"ITEM118","description":"","units":{},"default":"0","value_type":"INT"},{"index":119,"name":"ITEM119","description":"","units":{},"default":"0","value_type":"INT"},{"index":120,"name":"ITEM120","description":"","units":{},"default":"0","value_type":"INT"},{"index":121,"name":"ITEM121","description":"","units":{},"default":"0","value_type":"INT"},{"index":122,"name":"ITEM122","description":"","units":{},"default":"0","value_type":"INT"},{"index":123,"name":"ITEM123","description":"","units":{},"default":"0","value_type":"INT"},{"index":124,"name":"ITEM124","description":"","units":{},"default":"0","value_type":"INT"},{"index":125,"name":"ITEM125","description":"","units":{},"default":"0","value_type":"INT"},{"index":126,"name":"ITEM126","description":"","units":{},"default":"0","value_type":"INT"},{"index":127,"name":"ITEM127","description":"","units":{},"default":"0","value_type":"INT"},{"index":128,"name":"ITEM128","description":"","units":{},"default":"0","value_type":"INT"},{"index":129,"name":"ITEM129","description":"","units":{},"default":"0","value_type":"INT"},{"index":130,"name":"ITEM130","description":"","units":{},"default":"0","value_type":"INT"},{"index":131,"name":"ITEM131","description":"","units":{},"default":"0","value_type":"INT"},{"index":132,"name":"ITEM132","description":"","units":{},"default":"0","value_type":"INT"},{"index":133,"name":"ITEM133","description":"","units":{},"default":"0","value_type":"INT"},{"index":134,"name":"ITEM134","description":"","units":{},"default":"0","value_type":"INT"},{"index":135,"name":"ITEM135","description":"","units":{},"default":"0","value_type":"INT"},{"index":136,"name":"ITEM136","description":"","units":{},"default":"0","value_type":"INT"},{"index":137,"name":"ITEM137","description":"","units":{},"default":"0","value_type":"INT"},{"index":138,"name":"ITEM138","description":"","units":{},"default":"0","value_type":"INT"},{"index":139,"name":"ITEM139","description":"","units":{},"default":"0","value_type":"INT"},{"index":140,"name":"ITEM140","description":"","units":{},"default":"0","value_type":"INT"},{"index":141,"name":"ITEM141","description":"","units":{},"default":"0","value_type":"INT"},{"index":142,"name":"ITEM142","description":"","units":{},"default":"0","value_type":"INT"},{"index":143,"name":"ITEM143","description":"","units":{},"default":"0","value_type":"INT"},{"index":144,"name":"ITEM144","description":"","units":{},"default":"0","value_type":"INT"},{"index":145,"name":"ITEM145","description":"","units":{},"default":"0","value_type":"INT"},{"index":146,"name":"ITEM146","description":"","units":{},"default":"0","value_type":"INT"},{"index":147,"name":"ITEM147","description":"","units":{},"default":"0","value_type":"INT"},{"index":148,"name":"ITEM148","description":"","units":{},"default":"0","value_type":"INT"},{"index":149,"name":"ITEM149","description":"","units":{},"default":"0","value_type":"INT"},{"index":150,"name":"ITEM150","description":"","units":{},"default":"0","value_type":"INT"},{"index":151,"name":"ITEM151","description":"","units":{},"default":"0","value_type":"INT"},{"index":152,"name":"ITEM152","description":"","units":{},"default":"0","value_type":"INT"},{"index":153,"name":"ITEM153","description":"","units":{},"default":"0","value_type":"INT"},{"index":154,"name":"ITEM154","description":"","units":{},"default":"0","value_type":"INT"},{"index":155,"name":"ITEM155","description":"","units":{},"default":"0","value_type":"INT"},{"index":156,"name":"ITEM156","description":"","units":{},"default":"0","value_type":"INT"},{"index":157,"name":"ITEM157","description":"","units":{},"default":"0","value_type":"INT"},{"index":158,"name":"ITEM158","description":"","units":{},"default":"0","value_type":"INT"},{"index":159,"name":"ITEM159","description":"","units":{},"default":"0","value_type":"INT"},{"index":160,"name":"ITEM160","description":"","units":{},"default":"0","value_type":"INT"},{"index":161,"name":"ITEM161","description":"","units":{},"default":"0","value_type":"INT"},{"index":162,"name":"ITEM162","description":"","units":{},"default":"0","value_type":"INT"},{"index":163,"name":"ITEM163","description":"","units":{},"default":"0","value_type":"INT"},{"index":164,"name":"ITEM164","description":"","units":{},"default":"0","value_type":"INT"},{"index":165,"name":"ITEM165","description":"","units":{},"default":"0","value_type":"INT"},{"index":166,"name":"ITEM166","description":"","units":{},"default":"0","value_type":"INT"},{"index":167,"name":"ITEM167","description":"","units":{},"default":"0","value_type":"INT"},{"index":168,"name":"ITEM168","description":"","units":{},"default":"0","value_type":"INT"},{"index":169,"name":"ITEM169","description":"","units":{},"default":"0","value_type":"INT"},{"index":170,"name":"ITEM170","description":"","units":{},"default":"0","value_type":"INT"},{"index":171,"name":"ITEM171","description":"","units":{},"default":"0","value_type":"INT"},{"index":172,"name":"ITEM172","description":"","units":{},"default":"0","value_type":"INT"},{"index":173,"name":"ITEM173","description":"","units":{},"default":"0","value_type":"INT"},{"index":174,"name":"ITEM174","description":"","units":{},"default":"0","value_type":"INT"},{"index":175,"name":"ITEM175","description":"","units":{},"default":"0","value_type":"INT"},{"index":176,"name":"ITEM176","description":"","units":{},"default":"0","value_type":"INT"},{"index":177,"name":"ITEM177","description":"","units":{},"default":"0","value_type":"INT"},{"index":178,"name":"ITEM178","description":"","units":{},"default":"0","value_type":"INT"},{"index":179,"name":"ITEM179","description":"","units":{},"default":"0","value_type":"INT"},{"index":180,"name":"ITEM180","description":"","units":{},"default":"0","value_type":"INT"},{"index":181,"name":"ITEM181","description":"","units":{},"default":"0","value_type":"INT"},{"index":182,"name":"ITEM182","description":"","units":{},"default":"0","value_type":"INT"},{"index":183,"name":"ITEM183","description":"","units":{},"default":"0","value_type":"INT"},{"index":184,"name":"ITEM184","description":"","units":{},"default":"0","value_type":"INT"},{"index":185,"name":"ITEM185","description":"","units":{},"default":"0","value_type":"INT"},{"index":186,"name":"ITEM186","description":"","units":{},"default":"0","value_type":"INT"},{"index":187,"name":"ITEM187","description":"","units":{},"default":"0","value_type":"INT"},{"index":188,"name":"ITEM188","description":"","units":{},"default":"0","value_type":"INT"},{"index":189,"name":"ITEM189","description":"","units":{},"default":"0","value_type":"INT"},{"index":190,"name":"ITEM190","description":"","units":{},"default":"0","value_type":"INT"},{"index":191,"name":"ITEM191","description":"","units":{},"default":"0","value_type":"INT"},{"index":192,"name":"ITEM192","description":"","units":{},"default":"0","value_type":"INT"},{"index":193,"name":"ITEM193","description":"","units":{},"default":"0","value_type":"INT"},{"index":194,"name":"ITEM194","description":"","units":{},"default":"0","value_type":"INT"},{"index":195,"name":"ITEM195","description":"","units":{},"default":"0","value_type":"INT"},{"index":196,"name":"ITEM196","description":"","units":{},"default":"0","value_type":"INT"},{"index":197,"name":"ITEM197","description":"","units":{},"default":"0","value_type":"INT"},{"index":198,"name":"ITEM198","description":"","units":{},"default":"0","value_type":"INT"},{"index":199,"name":"ITEM199","description":"","units":{},"default":"0","value_type":"INT"},{"index":200,"name":"ITEM200","description":"","units":{},"default":"0","value_type":"INT"},{"index":201,"name":"ITEM201","description":"","units":{},"default":"0","value_type":"INT"},{"index":202,"name":"ITEM202","description":"","units":{},"default":"0","value_type":"INT"},{"index":203,"name":"ITEM203","description":"","units":{},"default":"0","value_type":"INT"},{"index":204,"name":"ITEM204","description":"","units":{},"default":"0","value_type":"INT"},{"index":205,"name":"ITEM205","description":"","units":{},"default":"0","value_type":"INT"},{"index":206,"name":"ITEM206","description":"","units":{},"default":"0","value_type":"INT"},{"index":207,"name":"ITEM207","description":"","units":{},"default":"0","value_type":"INT"},{"index":208,"name":"ITEM208","description":"","units":{},"default":"0","value_type":"INT"},{"index":209,"name":"ITEM209","description":"","units":{},"default":"0","value_type":"INT"},{"index":210,"name":"ITEM210","description":"","units":{},"default":"0","value_type":"INT"},{"index":211,"name":"ITEM211","description":"","units":{},"default":"0","value_type":"INT"},{"index":212,"name":"ITEM212","description":"","units":{},"default":"0","value_type":"INT"},{"index":213,"name":"ITEM213","description":"","units":{},"default":"0","value_type":"INT"},{"index":214,"name":"ITEM214","description":"","units":{},"default":"0","value_type":"INT"},{"index":215,"name":"ITEM215","description":"","units":{},"default":"0","value_type":"INT"},{"index":216,"name":"ITEM216","description":"","units":{},"default":"0","value_type":"INT"},{"index":217,"name":"ITEM217","description":"","units":{},"default":"0","value_type":"INT"},{"index":218,"name":"ITEM218","description":"","units":{},"default":"0","value_type":"INT"},{"index":219,"name":"ITEM219","description":"","units":{},"default":"0","value_type":"INT"},{"index":220,"name":"ITEM220","description":"","units":{},"default":"0","value_type":"INT"},{"index":221,"name":"ITEM221","description":"","units":{},"default":"0","value_type":"INT"},{"index":222,"name":"ITEM222","description":"","units":{},"default":"0","value_type":"INT"},{"index":223,"name":"ITEM223","description":"","units":{},"default":"0","value_type":"INT"},{"index":224,"name":"ITEM224","description":"","units":{},"default":"0","value_type":"INT"},{"index":225,"name":"ITEM225","description":"","units":{},"default":"0","value_type":"INT"},{"index":226,"name":"ITEM226","description":"","units":{},"default":"0","value_type":"INT"},{"index":227,"name":"ITEM227","description":"","units":{},"default":"0","value_type":"INT"},{"index":228,"name":"ITEM228","description":"","units":{},"default":"0","value_type":"INT"},{"index":229,"name":"ITEM229","description":"","units":{},"default":"0","value_type":"INT"},{"index":230,"name":"ITEM230","description":"","units":{},"default":"0","value_type":"INT"},{"index":231,"name":"ITEM231","description":"","units":{},"default":"0","value_type":"INT"},{"index":232,"name":"ITEM232","description":"","units":{},"default":"0","value_type":"INT"},{"index":233,"name":"ITEM233","description":"","units":{},"default":"0","value_type":"INT"},{"index":234,"name":"ITEM234","description":"","units":{},"default":"0","value_type":"INT"},{"index":235,"name":"ITEM235","description":"","units":{},"default":"0","value_type":"INT"},{"index":236,"name":"ITEM236","description":"","units":{},"default":"0","value_type":"INT"},{"index":237,"name":"ITEM237","description":"","units":{},"default":"0","value_type":"INT"},{"index":238,"name":"ITEM238","description":"","units":{},"default":"0","value_type":"INT"},{"index":239,"name":"ITEM239","description":"","units":{},"default":"0","value_type":"INT"},{"index":240,"name":"ITEM240","description":"","units":{},"default":"0","value_type":"INT"},{"index":241,"name":"ITEM241","description":"","units":{},"default":"0","value_type":"INT"},{"index":242,"name":"ITEM242","description":"","units":{},"default":"0","value_type":"INT"},{"index":243,"name":"ITEM243","description":"","units":{},"default":"0","value_type":"INT"},{"index":244,"name":"ITEM244","description":"","units":{},"default":"0","value_type":"INT"},{"index":245,"name":"ITEM245","description":"","units":{},"default":"0","value_type":"INT"},{"index":246,"name":"ITEM246","description":"","units":{},"default":"0","value_type":"INT"},{"index":247,"name":"ITEM247","description":"","units":{},"default":"0","value_type":"INT"},{"index":248,"name":"ITEM248","description":"","units":{},"default":"0","value_type":"INT"},{"index":249,"name":"ITEM249","description":"","units":{},"default":"0","value_type":"INT"},{"index":250,"name":"ITEM250","description":"","units":{},"default":"0","value_type":"INT"},{"index":251,"name":"ITEM251","description":"","units":{},"default":"0","value_type":"INT"},{"index":252,"name":"ITEM252","description":"","units":{},"default":"0","value_type":"INT"},{"index":253,"name":"ITEM253","description":"","units":{},"default":"0","value_type":"INT"},{"index":254,"name":"ITEM254","description":"","units":{},"default":"0","value_type":"INT"},{"index":255,"name":"ITEM255","description":"","units":{},"default":"0","value_type":"INT"},{"index":256,"name":"ITEM256","description":"","units":{},"default":"0","value_type":"INT"},{"index":257,"name":"ITEM257","description":"","units":{},"default":"0","value_type":"INT"},{"index":258,"name":"ITEM258","description":"","units":{},"default":"0","value_type":"INT"},{"index":259,"name":"ITEM259","description":"","units":{},"default":"0","value_type":"INT"},{"index":260,"name":"ITEM260","description":"","units":{},"default":"0","value_type":"INT"},{"index":261,"name":"ITEM261","description":"","units":{},"default":"0","value_type":"INT"},{"index":262,"name":"ITEM262","description":"","units":{},"default":"0","value_type":"INT"},{"index":263,"name":"ITEM263","description":"","units":{},"default":"0","value_type":"INT"},{"index":264,"name":"ITEM264","description":"","units":{},"default":"0","value_type":"INT"},{"index":265,"name":"ITEM265","description":"","units":{},"default":"0","value_type":"INT"},{"index":266,"name":"ITEM266","description":"","units":{},"default":"0","value_type":"INT"},{"index":267,"name":"ITEM267","description":"","units":{},"default":"0","value_type":"INT"},{"index":268,"name":"ITEM268","description":"","units":{},"default":"0","value_type":"INT"},{"index":269,"name":"ITEM269","description":"","units":{},"default":"0","value_type":"INT"},{"index":270,"name":"ITEM270","description":"","units":{},"default":"0","value_type":"INT"},{"index":271,"name":"ITEM271","description":"","units":{},"default":"0","value_type":"INT"},{"index":272,"name":"ITEM272","description":"","units":{},"default":"0","value_type":"INT"},{"index":273,"name":"ITEM273","description":"","units":{},"default":"0","value_type":"INT"},{"index":274,"name":"ITEM274","description":"","units":{},"default":"0","value_type":"INT"},{"index":275,"name":"ITEM275","description":"","units":{},"default":"0","value_type":"INT"},{"index":276,"name":"ITEM276","description":"","units":{},"default":"0","value_type":"INT"},{"index":277,"name":"ITEM277","description":"","units":{},"default":"0","value_type":"INT"},{"index":278,"name":"ITEM278","description":"","units":{},"default":"0","value_type":"INT"},{"index":279,"name":"ITEM279","description":"","units":{},"default":"0","value_type":"INT"},{"index":280,"name":"ITEM280","description":"","units":{},"default":"0","value_type":"INT"},{"index":281,"name":"ITEM281","description":"","units":{},"default":"0","value_type":"INT"},{"index":282,"name":"ITEM282","description":"","units":{},"default":"0","value_type":"INT"},{"index":283,"name":"ITEM283","description":"","units":{},"default":"0","value_type":"INT"},{"index":284,"name":"ITEM284","description":"","units":{},"default":"0","value_type":"INT"},{"index":285,"name":"ITEM285","description":"","units":{},"default":"0","value_type":"INT"},{"index":286,"name":"ITEM286","description":"","units":{},"default":"0","value_type":"INT"},{"index":287,"name":"ITEM287","description":"","units":{},"default":"0","value_type":"INT"},{"index":288,"name":"ITEM288","description":"","units":{},"default":"0","value_type":"INT"}],"example":"","expected_columns":288,"size_kind":"fixed","size_count":1},"PREF":{"name":"PREF","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"PRESSURE","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Pressure"]}],"example":"","size_kind":"fixed"},"PREFS":{"name":"PREFS","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"PRESSURE","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Pressure"]}],"example":"","size_kind":"fixed"},"REGION2REGION_PROBE_E300":{"name":"REGION2REGION_PROBE_E300","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"REGION1","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"REGION2","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":2,"size_kind":"list"},"SOLID":{"name":"SOLID","sections":["RUNSPEC"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"none","size_count":0},"STCOND":{"name":"STCOND","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"TEMPERATURE","description":"","units":{},"default":"15.56","value_type":"DOUBLE","dimension":"Temperature"},{"index":2,"name":"PRESSURE","description":"","units":{},"default":"1.01325","value_type":"DOUBLE","dimension":"Pressure"}],"example":"","expected_columns":2,"size_kind":"fixed","size_count":1},"TREF":{"name":"TREF","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"TEMPERATURE","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["AbsoluteTemperature"]}],"example":"","size_kind":"fixed"},"TREFS":{"name":"TREFS","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"TEMPERATURE","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["AbsoluteTemperature"]}],"example":"","size_kind":"fixed"},"WECONCMF":{"name":"WECONCMF","sections":["SCHEDULE"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"COMPONENT_INDEX","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"MAXIMUM_MOLE_FRACTION","description":"","units":{},"default":"","value_type":"UDA"},{"index":4,"name":"WORKOVER_PROCEDURE","description":"","units":{},"default":"NONE","value_type":"STRING"},{"index":5,"name":"END_RUN_FLAG","description":"","units":{},"default":"NO","value_type":"STRING"}],"example":"","expected_columns":5,"size_kind":"list"},"WELL_PROBE_COMP":{"name":"WELL_PROBE_COMP","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"WELLS","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"COMP_NUM","description":"","units":{},"default":"","value_type":"INT"}],"example":"","size_kind":"list"},"XMF":{"name":"XMF","sections":["SOLUTION"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"YMF":{"name":"YMF","sections":["SOLUTION"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"ZFACT1":{"name":"ZFACT1","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"Z0","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["1"]}],"example":"","size_kind":"fixed"},"ZFACT1S":{"name":"ZFACT1S","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"Z0","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["1"]}],"example":"","size_kind":"fixed"},"ZFACTOR":{"name":"ZFACTOR","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"Z0","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["1"]}],"example":"","size_kind":"fixed"},"ZFACTORS":{"name":"ZFACTORS","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"Z0","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["1"]}],"example":"","size_kind":"fixed"},"ZMF":{"name":"ZMF","sections":["SOLUTION"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"NOGRAV":{"name":"NOGRAV","sections":["RUNSPEC"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"none","size_count":0},"BIOTCOEF":{"name":"BIOTCOEF","sections":["GRID"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"BLOCK_PROBE900":{"name":"BLOCK_PROBE900","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"I","description":"","units":{},"default":"","value_type":"INT"},{"index":2,"name":"J","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"K","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":3,"size_kind":"list"},"CO2STOR":{"name":"CO2STOR","sections":["RUNSPEC"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"none","size_count":0},"CONNECTION_PROBE_OPM":{"name":"CONNECTION_PROBE_OPM","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"I","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"J","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"K","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":4,"size_kind":"list"},"CSTRESS":{"name":"CSTRESS","sections":["GRID"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"FIELD_PROBE_OPM":{"name":"FIELD_PROBE_OPM","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"none","size_count":0},"FRAC":{"name":"FRAC","sections":["RUNSPEC"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"none","size_count":0},"GCOMPIDX":{"name":"GCOMPIDX","sections":["RUNSPEC"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"GAS_COMPONENT_INDEX","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"GEOCHEM":{"name":"GEOCHEM","sections":["RUNSPEC"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"INIT_FILE_NAME","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"MBAL_TOL","description":"","units":{},"default":"1e-07","value_type":"DOUBLE"},{"index":3,"name":"PH_TOL","description":"","units":{},"default":"1e-08","value_type":"DOUBLE"},{"index":4,"name":"ENFORCE_CHARGE_BALANCE","description":"","units":{},"default":"NOCHARGE","value_type":"STRING"},{"index":5,"name":"SPLAY_TREE","description":"","units":{},"default":"0","value_type":"INT"}],"example":"","expected_columns":5,"size_kind":"fixed","size_count":1},"GROUP_PROBE_OPM":{"name":"GROUP_PROBE_OPM","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"GROUPS","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","size_kind":"fixed","size_count":1},"IBLK":{"name":"IBLK","sections":["SOLUTION"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"IONEX":{"name":"IONEX","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"IVDP":{"name":"IVDP","sections":["SOLUTION"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Length","1"]}],"example":"","size_kind":"fixed"},"LAME":{"name":"LAME","sections":["GRID"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"MBLK":{"name":"MBLK","sections":["SOLUTION"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"MECH":{"name":"MECH","sections":["RUNSPEC"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"none","size_count":0},"MECHSOLV":{"name":"MECHSOLV","sections":["RUNSPEC"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"SOLVER","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"COUPLING","description":"","units":{},"default":"LAGGED","value_type":"STRING"},{"index":3,"name":"FIXED_STRESS_MIN_ITER","description":"","units":{},"default":"1","value_type":"INT"},{"index":4,"name":"FIXED_STRESS_MAX_ITER","description":"","units":{},"default":"5","value_type":"INT"}],"example":"","expected_columns":4,"size_kind":"fixed","size_count":1},"MINERAL":{"name":"MINERAL","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"MVDP":{"name":"MVDP","sections":["SOLUTION"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Length","1"]}],"example":"","size_kind":"fixed"},"NETWORK_PROBE":{"name":"NETWORK_PROBE","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"NETWORK_NODES","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","size_kind":"fixed","size_count":1},"OCOMPIDX":{"name":"OCOMPIDX","sections":["RUNSPEC"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"OIL_COMPONENT_INDEX","description":"","units":{},"default":"","value_type":"INT"}],"example":"","expected_columns":1,"size_kind":"fixed","size_count":1},"POELCOEF":{"name":"POELCOEF","sections":["GRID"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"PRATIO":{"name":"PRATIO","sections":["GRID"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"REGION_PROBE_OPM":{"name":"REGION_PROBE_OPM","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array","optional_body":true},"RHO":{"name":"RHO","sections":["GRID"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"SBLK":{"name":"SBLK","sections":["SOLUTION"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"SMODULUS":{"name":"SMODULUS","sections":["GRID"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"SPECIES":{"name":"SPECIES","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"STREQUIL":{"name":"STREQUIL","sections":["SOLUTION"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"DATUM_DEPTH","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Length"},{"index":2,"name":"DATUM_POSX","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Length"},{"index":3,"name":"DATUM_POSY","description":"","units":{},"default":"0","value_type":"DOUBLE","dimension":"Length"},{"index":4,"name":"STRESSXX","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":5,"name":"STRESSXXGRAD","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure/Length"},{"index":6,"name":"STRESSYY","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":7,"name":"STRESSYYGRAD","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure/Length"},{"index":8,"name":"STRESSZZ","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":9,"name":"STRESSZZGRAD","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure/Length"},{"index":10,"name":"STRESSXY","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":11,"name":"STRESSXYGRAD","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure/Length"},{"index":10,"name":"STRESSXZ","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":11,"name":"STRESSXZGRAD","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure/Length"},{"index":12,"name":"STRESSYZ","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure"},{"index":13,"name":"STRESSYZGRAD","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Pressure/Length"}],"example":"","expected_columns":15,"size_kind":"list"},"STRESSEQUILNUM":{"name":"STRESSEQUILNUM","sections":["REGIONS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"SVDP":{"name":"SVDP","sections":["SOLUTION"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Length","1"]}],"example":"","size_kind":"fixed"},"THELCOEF":{"name":"THELCOEF","sections":["GRID"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"THERMEXR":{"name":"THERMEXR","sections":["GRID"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"},"TLPMIXPA":{"name":"TLPMIXPA","sections":["PROPS"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"DATA","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":["Pressure","1"]}],"example":"","size_kind":"fixed"},"WELL_PROBE_OPM":{"name":"WELL_PROBE_OPM","sections":["SUMMARY"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"WELLS","description":"","units":{},"default":"","value_type":"STRING"}],"example":"","size_kind":"fixed","size_count":1},"WSEED":{"name":"WSEED","sections":["SCHEDULE"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"I","description":"","units":{},"default":"","value_type":"INT"},{"index":3,"name":"J","description":"","units":{},"default":"","value_type":"INT"},{"index":4,"name":"K","description":"","units":{},"default":"","value_type":"INT"},{"index":5,"name":"NORMAL_X","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":6,"name":"NORMAL_Y","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":7,"name":"NORMAL_Z","description":"","units":{},"default":"","value_type":"DOUBLE","dimension":"Length"},{"index":8,"name":"SIZE_Z","description":"","units":{},"default":"0.3","value_type":"DOUBLE","dimension":"Length"},{"index":9,"name":"SIZE_H","description":"","units":{},"default":"0.3","value_type":"DOUBLE","dimension":"Length"},{"index":10,"name":"WIDTH","description":"","units":{},"default":"0.0001","value_type":"DOUBLE","dimension":"Length"}],"example":"","expected_columns":10,"size_kind":"list"},"WSPECIES":{"name":"WSPECIES","sections":["SCHEDULE"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[{"index":1,"name":"WELL","description":"","units":{},"default":"","value_type":"STRING"},{"index":2,"name":"SPECIES","description":"","units":{},"default":"","value_type":"STRING"},{"index":3,"name":"CONCENTRATION","description":"","units":{},"default":"","value_type":"UDA"},{"index":4,"name":"CUM_SPECIES_FACTOR","description":"","units":{},"default":"","value_type":"UDA"},{"index":5,"name":"PRODUCTION_GROUP","description":"Defaulted means: use the concentration from the CONCENTRATION item","units":{},"default":"","value_type":"STRING"}],"example":"","expected_columns":5,"size_kind":"list"},"YMODULE":{"name":"YMODULE","sections":["GRID"],"supported":true,"summary":"(OPM Flow keyword — no reference-manual entry)","parameters":[],"example":"","size_kind":"array"}} \ No newline at end of file diff --git a/vscode-extension/package.json b/vscode-extension/package.json index a2d16b1..a0b4eaf 100644 --- a/vscode-extension/package.json +++ b/vscode-extension/package.json @@ -54,27 +54,38 @@ "extensions": [ ".data", ".DATA", + ".dat", ".inc", ".INC", + ".incl", ".include", ".sch", ".SCH", + ".sched", ".schedule", ".grdecl", ".GRDECL", + ".grid", + ".gridopts", ".vfp", ".VFP", + ".vfpprod", ".prop", + ".prpecl", ".Ecl", ".ecl", ".summary", + ".smry", ".aqucon", ".aqunum", ".dimens", + ".eqldims", ".eqlnum", ".equil", ".fault", + ".faults", ".fipnum", + ".fipzon", ".multnum", ".multregp", ".multregt", @@ -82,13 +93,19 @@ ".ntg", ".opernum", ".perm", + ".permx", ".poro", ".pvt", + ".pvtnum", + ".regdims", ".rocknum", + ".rxvd", ".satnum", ".sattab", + ".swatinit", ".tabdims", - ".thpres" + ".thpres", + ".trans" ], "configuration": "./language-configuration.json" } diff --git a/vscode-extension/src/analysis.test.ts b/vscode-extension/src/analysis.test.ts index fe4ef74..011d3a7 100644 --- a/vscode-extension/src/analysis.test.ts +++ b/vscode-extension/src/analysis.test.ts @@ -646,6 +646,31 @@ describe('computeDiagnostics — unquoted string values', () => { expect(diags.some(d => d.message.includes('INCLUDE is not a recognised'))).toBe(false); }); + it('treats an indented known-keyword name as a record value (EQLOPTS / THPRES)', () => { + // THPRES is both a real SOLUTION keyword *and* a valid EQLOPTS + // option name. Indented (not in column 1) under an open EQLOPTS + // block it must be parsed as the EQLOPTS record value, not as a + // misplaced THPRES keyword declaration. + const eqloptsIndex: Record = { + ...stringIndex, + EQLOPTS: { + name: 'EQLOPTS', + sections: ['RUNSPEC'], + size_kind: 'fixed', + size_count: 1, + expected_columns: 4, + }, + THPRES: { + name: 'THPRES', + sections: ['SOLUTION'], + size_kind: 'list', + expected_columns: 3, + }, + }; + const lines = ['RUNSPEC', 'EQLOPTS', ' THPRES /']; + expect(computeDiagnostics(lines, eqloptsIndex)).toEqual([]); + }); + it('still flags a typo once the block is finished', () => { // After INCFIX's single record terminates with '/', the block is done. // A subsequent unknown identifier IS a typo, not a string value. @@ -820,6 +845,245 @@ describe('computeDiagnostics — templated tracer mnemonics', () => { }); }); +// --------------------------------------------------------------------------- +// User-defined FIP region templates — FIP + resolves to FIP +// --------------------------------------------------------------------------- + +describe('computeDiagnostics — templated FIP region keywords', () => { + // FIP is documented in the OPM manual as a base name to which users + // append a 1-5 character region label (FIPZON, FIPGL, FIPNL, FIPUNIT, + // FIPHC, …). The build script tags FIP as templated so any + // FIP+[A-Z0-9]+ deck token resolves to the FIP entry. + const fipIndex: Record = { + ...index, + FIP: { name: 'FIP', sections: ['REGIONS'], templated: true }, + FIPNUM: { name: 'FIPNUM', sections: ['REGIONS'], size_kind: 'array' }, + }; + + it('accepts a user-defined FIPZON region keyword (issue example)', () => { + const lines = ['REGIONS', 'FIPZON', ' 1 1 1 1 1', ' 1 /']; + expect(computeDiagnostics(lines, fipIndex)).toEqual([]); + }); + + it('still routes FIPNUM through its direct entry, not the FIP template', () => { + // Direct lookup wins over the template fallback, so FIPNUM keeps + // its own (array-shape) entry and isn't misclassified as a FIP. + const lines = ['REGIONS', 'FIPNUM', ' 1 2 3 /']; + expect(computeDiagnostics(lines, fipIndex)).toEqual([]); + }); +}); + +// --------------------------------------------------------------------------- +// SUMMARY mnemonic body — list of names spread across multiple lines +// --------------------------------------------------------------------------- + +describe('computeDiagnostics — SUMMARY mnemonic list bodies', () => { + // W/G/C/L/R/B/A/N/S-prefixed SUMMARY mnemonics take a list of names + // closed by a single '/'. The names can sit on one line or be spread + // across many; only the closing '/' completes the block. Modelled as + // `size_kind: 'array'` so per-line missing-'/' checks are suppressed + // but a missing block-end '/' is still flagged. + const summaryIndex: Record = { + ...index, + WOPR: { name: 'WOPR', sections: ['SUMMARY'], size_kind: 'array' }, + }; + + it('accepts names spread across multiple lines with a closing /', () => { + // The exact case from the user's report. + const lines = ['SUMMARY', 'WOPR', " 'PROD'", '/']; + expect(computeDiagnostics(lines, summaryIndex)).toEqual([]); + }); + + it('accepts the inline form with a trailing /', () => { + const lines = ['SUMMARY', 'WOPR', " 'PROD1' 'PROD2' /"]; + expect(computeDiagnostics(lines, summaryIndex)).toEqual([]); + }); + + it('accepts a bare / meaning "all wells"', () => { + const lines = ['SUMMARY', 'WOPR', '/']; + expect(computeDiagnostics(lines, summaryIndex)).toEqual([]); + }); + + it('still flags a block with no terminating /', () => { + const lines = ['SUMMARY', 'WOPR', " 'PROD'"]; + const diags = computeDiagnostics(lines, summaryIndex); + expect(diags.some(d => /WOPR.*missing terminating/.test(d.message))).toBe(true); + }); + + it('accepts back-to-back bare mnemonics closed by one trailing /', () => { + // The widely-used GMWPR / GMWIN pattern: stack bare optional-body + // mnemonics and close the lot with a single '/'. + const optionalIndex: Record = { + ...index, + GMWPR: { name: 'GMWPR', sections: ['SUMMARY'], size_kind: 'array', optional_body: true }, + GMWIN: { name: 'GMWIN', sections: ['SUMMARY'], size_kind: 'array', optional_body: true }, + }; + const lines = ['SUMMARY', 'GMWPR', 'GMWIN', '/']; + expect(computeDiagnostics(lines, optionalIndex)).toEqual([]); + }); + + it('accepts a single bare optional-body mnemonic with no body and no /', () => { + const optionalIndex: Record = { + ...index, + GMWPR: { name: 'GMWPR', sections: ['SUMMARY'], size_kind: 'array', optional_body: true }, + }; + const lines = ['SUMMARY', 'GMWPR']; + expect(computeDiagnostics(lines, optionalIndex)).toEqual([]); + }); + + it('still flags a missing / once values have been listed (optional_body)', () => { + // optional_body only relaxes the empty-body case; once names appear + // the missing-/ diagnostic must still fire. + const optionalIndex: Record = { + ...index, + GMWPR: { name: 'GMWPR', sections: ['SUMMARY'], size_kind: 'array', optional_body: true }, + }; + const lines = ['SUMMARY', 'GMWPR', " 'PROD'"]; + const diags = computeDiagnostics(lines, optionalIndex); + expect(diags.some(d => /GMWPR.*missing terminating/.test(d.message))).toBe(true); + }); +}); + +// --------------------------------------------------------------------------- +// UDQ SUMMARY mnemonics — WU, FU, … resolve via +// scope-prefix templates (WU, FU, GU, CU, RU, SU) +// --------------------------------------------------------------------------- + +describe('computeDiagnostics — UDQ SUMMARY mnemonic templates', () => { + // UDQ summary mnemonics are documented in the manual under placeholder + // names FUXXXXXX/WUXXXXXX/etc. The build script strips the trailing X's + // and marks the prefix entry templated so deck tokens like WUWI1 or + // FUOIL resolve through the standard +[A-Z0-9]+ fallback. + const udqIndex: Record = { + ...index, + FU: { name: 'FU', sections: ['SUMMARY'], size_kind: 'none', templated: true }, + WU: { name: 'WU', sections: ['SUMMARY'], size_kind: 'array', optional_body: true, templated: true }, + }; + + it('recognises WUWI1 (issue example) as a templated WU mnemonic', () => { + const lines = ['SUMMARY', 'WUWI1']; + expect(computeDiagnostics(lines, udqIndex)).toEqual([]); + }); + + it('recognises FUOIL as a templated FU mnemonic', () => { + const lines = ['SUMMARY', 'FUOIL']; + expect(computeDiagnostics(lines, udqIndex)).toEqual([]); + }); + + it('accepts a WU body of wells closed by /', () => { + const lines = ['SUMMARY', 'WUWI1', " 'PROD1' 'PROD2' /"]; + expect(computeDiagnostics(lines, udqIndex)).toEqual([]); + }); +}); + +// --------------------------------------------------------------------------- +// MESSAGES — single 13-value record canonically split across multiple lines +// --------------------------------------------------------------------------- + +describe('computeDiagnostics — MESSAGES variadic record', () => { + // MESSAGES is a single record with 13 INT parameters, but real decks + // routinely split it as print-limits then stop-limits across two lines + // with the trailing '/' closing the whole record. Tagged variadic_record + // so per-line missing-/ diagnostics are suppressed. + const messagesIndex: Record = { + ...index, + MESSAGES: { + name: 'MESSAGES', + sections: ['RUNSPEC'], + size_kind: 'fixed', + size_count: 1, + expected_columns: 13, + variadic_record: true, + }, + }; + + it('accepts the print-limits / stop-limits split form (issue example)', () => { + const lines = [ + 'RUNSPEC', + 'MESSAGES', + '-- mess comm warn prob err bug ', + ' 80000 10000 5000000 5000 300 1 ', + '-- mess comm warn prob err bug ', + ' 80000 10000 5000000 80000 10 1 /', + ]; + expect(computeDiagnostics(lines, messagesIndex)).toEqual([]); + }); + + it('also accepts a heavily-decorated single-line form', () => { + const lines = [ + 'RUNSPEC', + 'MESSAGES', + ' 80000 10000 5000000 5000 300 1 80000 10000 5000000 80000 10 1 /', + ]; + expect(computeDiagnostics(lines, messagesIndex)).toEqual([]); + }); +}); + +// --------------------------------------------------------------------------- +// VFPPROD / VFPINJ — multi-record tables with multi-line records and no +// standalone closing '/' +// --------------------------------------------------------------------------- + +describe('computeDiagnostics — VFPPROD multi-line record bodies', () => { + // VFPPROD: header record + 5 axis records + repeating BHP-table record. + // Each axis and BHP record spans many lines and ends with '/'. The block + // itself does NOT end with a standalone '/' — the trailing record's '/' + // is the natural end. Reclassified to 'fixed' so closeKw doesn't demand + // a list terminator, plus variadic_record so per-line missing-/ checks + // are suppressed on the multi-line axis/BHP rows. + const vfpIndex: Record = { + ...index, + VFPPROD: { + name: 'VFPPROD', + sections: ['SCHEDULE'], + size_kind: 'fixed', + size_count: 7, + variadic_record: true, + records_meta: [ + { expected_columns: 9 }, {}, {}, {}, {}, {}, {}, + ], + }, + }; + + it('accepts the user-reported header + LIQ + THP form', () => { + const lines = [ + 'SCHEDULE', + 'VFPPROD', + '-- Table Datum Depth Rate Type WFR Type GFR Type THP Type ALQ Type UNITS TAB Type', + ' 1 1535 LIQ WCT GOR THP PUMP METRIC BHP /', + '-- LIQ units', + ' 100.0 123.0 151.0 185.0 228.0', + ' 280.0 344.0 423.0 519.0 638.0', + ' 784.0 963.0 1183.0 1454.0 1786.0', + ' 2194.0 2696.0 3312.0 4070.0 5000.0 /', + '-- THP units', + ' 2.00 18.00 35.00 51.00 68.00', + ' 84.00 101.00 117.00 134.00 150.00 /', + ]; + expect(computeDiagnostics(lines, vfpIndex)).toEqual([]); + }); + + it('does not demand a standalone closing / on the block', () => { + // The next keyword (WELSPECS) ends the VFPPROD block naturally; + // closeKw must not emit a list-terminator diagnostic. + const lines = [ + 'SCHEDULE', + 'VFPPROD', + ' 1 1535 LIQ WCT GOR THP PUMP METRIC BHP /', + ' 100 200 300 /', + ' 1 2 /', + ' 0.4 /', + ' 0.5 /', + ' 100 /', + ' 1 1 1 1 12.5 /', + 'WELSPECS', + '/', + ]; + const diags = computeDiagnostics(lines, vfpIndex); + expect(diags.some(d => /VFPPROD.*missing terminating/.test(d.message))).toBe(false); + }); +}); + // --------------------------------------------------------------------------- // TITLE — free-form text on the next line, no '/' terminator // --------------------------------------------------------------------------- diff --git a/vscode-extension/src/analysis.ts b/vscode-extension/src/analysis.ts index b84003b..b69c50c 100644 --- a/vscode-extension/src/analysis.ts +++ b/vscode-extension/src/analysis.ts @@ -61,6 +61,22 @@ export interface AnalysisEntry { * must not trigger a missing-terminator diagnostic. */ variadic_record?: boolean; + /** + * True when the keyword's record body is optional — i.e. the bare + * keyword on a line by itself (no values, no '/') is a valid usage. + * Used by non-F SUMMARY mnemonics that may either list names or be + * written bare to mean "all", and that can be stacked back-to-back + * with no intervening '/': + * + * GMWPR + * GMWIN + * / + * + * When ``recordCount === 0`` the close-block terminator check is + * skipped; once any value tokens appear, the usual array/list rules + * apply so a forgotten closing '/' still gets flagged. + */ + optional_body?: boolean; } export type AnalysisIndex = Record; @@ -200,9 +216,17 @@ export function computeDiagnostics( const closeKw = (): void => { if (!activeKw) return; + // Optional-body keywords (non-F SUMMARY mnemonics) may appear bare + // and stacked, so a block that consumed no records doesn't need a + // closing '/'. Once values are present the normal array/list rule + // applies again. + const bareOptionalBody = activeKw.optional_body && recordCount === 0; const needsTerminator = - (activeKw.size_kind === 'list' && !listTerminatorSeen) || - (activeKw.size_kind === 'array' && !arrayTerminatorSeen); + !bareOptionalBody + && ( + (activeKw.size_kind === 'list' && !listTerminatorSeen) || + (activeKw.size_kind === 'array' && !arrayTerminatorSeen) + ); if (needsTerminator) { // Anchor the squiggle at the end of the last record when we have one, // otherwise at the keyword name itself. @@ -288,14 +312,17 @@ export function computeDiagnostics( } // A single uppercase identifier mid-block is more plausibly an - // unquoted string value (e.g. `INCLUDE` `PATH`) than a new - // keyword. If the active keyword's block is still expecting records - // and the token is not itself a known keyword (or excluded), fall - // through to record parsing instead of starting a new keyword. + // unquoted string value (e.g. `INCLUDE` `PATH`, or + // `EQLOPTS` ` THPRES /`) than a new keyword. Treat it + // as a record when the active block still expects records and + // either (a) the token is not a known keyword, or (b) it is + // indented — OPM Flow only recognises keywords in column 1, so + // an indented uppercase token cannot start a new keyword even + // if its name happens to be in the index (THPRES, INCLUDE, …). const entry = lookupEntry(index, kw); const treatAsRecord = activeKw !== null - && !entry + && (!entry || indent > 0) && !excludedKeywords.has(kw) && expectsMoreRecords(activeKw, recordCount, listTerminatorSeen, arrayTerminatorSeen); diff --git a/vscode-extension/src/extension.ts b/vscode-extension/src/extension.ts index 03fc968..18b56da 100644 --- a/vscode-extension/src/extension.ts +++ b/vscode-extension/src/extension.ts @@ -9,7 +9,7 @@ import { RecordLine, parseRecordLine, isCommentLine, - KEYWORD_LINE_RE, + KEYWORD_LINE_COL1_RE, SECTION_KEYWORDS, SECTION_KEYWORD_SET, formatRecordGroup, @@ -93,7 +93,7 @@ function findActiveKeyword(document: vscode.TextDocument, position: vscode.Posit for (let lineNum = position.line; lineNum >= 0; lineNum--) { const text = document.lineAt(lineNum).text; if (text.trim().startsWith('--')) continue; - const m = text.match(KEYWORD_LINE_RE); + const m = text.match(KEYWORD_LINE_COL1_RE); if (m) return m[1]; } return null; @@ -110,7 +110,7 @@ function findActiveKeywordLine( for (let lineNum = position.line; lineNum >= 0; lineNum--) { const text = document.lineAt(lineNum).text; if (text.trim().startsWith('--')) continue; - if (KEYWORD_LINE_RE.test(text)) return lineNum; + if (KEYWORD_LINE_COL1_RE.test(text)) return lineNum; } return -1; } @@ -162,17 +162,12 @@ function findCurrentSection(document: vscode.TextDocument, position: vscode.Posi for (let lineNum = position.line; lineNum >= 0; lineNum--) { const text = document.lineAt(lineNum).text; if (text.trim().startsWith('--')) continue; - const m = text.match(KEYWORD_LINE_RE); + const m = text.match(KEYWORD_LINE_COL1_RE); if (m && SECTION_KEYWORD_SET.has(m[1])) return m[1]; } return null; } -function wordAtPosition(document: vscode.TextDocument, position: vscode.Position): string { - const range = document.getWordRangeAtPosition(position, /[A-Z][A-Z0-9_-]*/); - return range ? document.getText(range) : ''; -} - const TEMPLATE_SUFFIX_RE = /^[A-Z0-9]+$/; /** @@ -684,7 +679,7 @@ class OpmFlowFoldingRangeProvider implements vscode.FoldingRangeProvider { const text = document.lineAt(i).text; if (text.trim().startsWith('--')) continue; - const m = text.match(KEYWORD_LINE_RE); + const m = text.match(KEYWORD_LINE_COL1_RE); if (!m) continue; const kw = m[1]; @@ -796,9 +791,15 @@ export function activate(context: vscode.ExtensionContext): void { const pos = editor.selection.active; const line = editor.document.lineAt(pos).text; - const word = wordAtPosition(editor.document, pos); + // Only treat the word at the cursor as a keyword *declaration* when it + // starts in column 1. OPM Flow only recognises keywords there, so an + // indented uppercase token (e.g. `THPRES` on ` THPRES /` under EQLOPTS) + // is a record value, not the THPRES keyword — fall through to the + // active-keyword + column lookup below. + const wordRange = editor.document.getWordRangeAtPosition(pos, /[A-Z][A-Z0-9_-]*/); + const word = wordRange ? editor.document.getText(wordRange) : ''; const wordEntry = word ? resolveKeyword(index, word) : undefined; - if (wordEntry) { + if (wordEntry && wordRange?.start.character === 0) { docsProvider.update(wordEntry); return; } @@ -944,10 +945,15 @@ export function activate(context: vscode.ExtensionContext): void { provideHover(document: vscode.TextDocument, position: vscode.Position): vscode.Hover | undefined { const line = document.lineAt(position).text; - const word = wordAtPosition(document, position); + // Same column-1 discipline as the docs panel: an indented uppercase + // token is a record value, not a keyword declaration, even when its + // name happens to match an index entry (THPRES under EQLOPTS, …). + const wordRange = document.getWordRangeAtPosition(position, /[A-Z][A-Z0-9_-]*/); + const word = wordRange ? document.getText(wordRange) : ''; + const wordAtCol1 = wordRange?.start.character === 0; const excluded = getExcludedKeywords(document.uri); const wordEntry = word ? resolveKeyword(index, word) : undefined; - if (word && wordEntry) { + if (word && wordEntry && wordAtCol1) { const currentSection = findCurrentSection(document, position); return new vscode.Hover( buildKeywordHover(wordEntry, currentSection, excluded.has(word)), @@ -956,7 +962,7 @@ export function activate(context: vscode.ExtensionContext): void { // Excluded keyword not in the index: still show a short notice so the // user knows why no diagnostics or docs appear on it. - if (word && excluded.has(word)) { + if (word && wordAtCol1 && excluded.has(word)) { const md = new vscode.MarkdownString(); md.supportHtml = true; md.appendMarkdown(`## \`${word}\`\n\n`); diff --git a/vscode-extension/src/formatting.ts b/vscode-extension/src/formatting.ts index de4d50d..00262b8 100644 --- a/vscode-extension/src/formatting.ts +++ b/vscode-extension/src/formatting.ts @@ -86,9 +86,21 @@ export const NUMERIC_TOKEN_RE = /^(\*|\d+\*|[-+]?(\d+\.?\d*|\.\d+)([eE][-+]?\d+) export const KEYWORD_TOKEN_RE = /^[A-Z][A-Z0-9_+-]*$/; /** Matches a line that is just a keyword declaration (with optional trailing - * comment or `/`), as opposed to a record line. */ + * comment or `/`), as opposed to a record line. Permissive: accepts leading + * whitespace so diagnostics can flag indented keywords. Cursor-driven + * features (active-keyword lookup, docs panel, folding) should prefer the + * stricter `KEYWORD_LINE_COL1_RE` instead — OPM Flow only recognises a + * keyword when it starts in column 1, and an indented uppercase token is + * more plausibly an unquoted string value than a misplaced keyword. */ export const KEYWORD_LINE_RE = /^\s*([A-Z][A-Z0-9_+-]{1,})\s*(?:--|\/\s*(?:--|$)|$)/; +/** Column-1-anchored form of `KEYWORD_LINE_RE`. Use this for editor + * features (docs panel, hover, folding, active-keyword scan) so they + * agree with OPM Flow's parser: only column-1 declarations are real + * keywords. An indented `THPRES /` under EQLOPTS, for example, is a + * record value — not a new THPRES block. */ +export const KEYWORD_LINE_COL1_RE = /^([A-Z][A-Z0-9_+-]{1,})\s*(?:--|\/\s*(?:--|$)|$)/; + /** Same shape as KEYWORD_LINE_RE but accepts lowercase letters too — used by * diagnostics to detect keywords typed in non-uppercase form, which OPM Flow * itself silently fails to recognise. */ diff --git a/vscode-extension/syntaxes/opm-flow.tmLanguage.json b/vscode-extension/syntaxes/opm-flow.tmLanguage.json index c9620dd..4187c70 100644 --- a/vscode-extension/syntaxes/opm-flow.tmLanguage.json +++ b/vscode-extension/syntaxes/opm-flow.tmLanguage.json @@ -11,7 +11,8 @@ { "include": "#variables" }, { "include": "#defaults" }, { "include": "#numbers" }, - { "include": "#terminators" } + { "include": "#terminators" }, + { "include": "#unquoted-strings" } ], "repository": { "comments": { @@ -28,7 +29,7 @@ }, "keywords": { "name": "keyword.control.opm-flow", - "match": "^\\s*[A-Z][A-Z0-9_+-]*\\s*$|^\\s*[A-Z][A-Z0-9_+-]*(?=\\s)" + "match": "^[A-Z][A-Z0-9_+-]*(?=\\s*(?:--|/|$))" }, "strings": { "name": "string.quoted.single.opm-flow", @@ -56,6 +57,10 @@ "1": { "name": "punctuation.terminator.opm-flow" }, "2": { "name": "comment.line.terminator-trailing.opm-flow" } } + }, + "unquoted-strings": { + "name": "string.unquoted.opm-flow", + "match": "(?